Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The TOC in handbook_content/README.md links to .md files. Accordingly, these links doesn't work anymore when these files are transformed to .html. Can we move to a structure where every chapter is contained in its own folder (as it is already the case with the large "open science basics" chapter), and then link to the folder names? This way, it should resolve always to README as the "entry page" of the respective chapter, both in Github as well as in Gitbook. This is basically what the Gitbook documentation seems to suggest: https://toolchain.gitbook.com/pages.html #4

Open
lambo opened this issue Mar 24, 2018 · 0 comments
Open

The TOC in handbook_content/README.md links to .md files. Accordingly, these links doesn't work anymore when these files are transformed to .html. Can we move to a structure where every chapter is contained in its own folder (as it is already the case with the large "open science basics" chapter), and then link to the folder names? This way, it should resolve always to README as the "entry page" of the respective chapter, both in Github as well as in Gitbook. This is basically what the Gitbook documentation seems to suggest: https://toolchain.gitbook.com/pages.html #4

lambo opened this issue Mar 24, 2018 · 0 comments
Assignees
@lambo @mcancellieri @helenebr

Comments

@lambo
Copy link
Contributor

lambo commented Mar 24, 2018

No description provided.

@lambo lambo changed the title The TOC in handbook_content/README.md links to .md files. Accordingly, these links doesn't work anymore when these files are transformed to .html. Can we move to a structure where every chapter is contained in its own folder (as it is already the case with the large "open science basics" chapter), and then link to the folder names? This way, it should resolve always to README as the "entry page" of the respective chapter, both in Github as well as in Github. This is basically what the Gitbook documentation seems to suggest: https://toolchain.gitbook.com/pages.html The TOC in handbook_content/README.md links to .md files. Accordingly, these links doesn't work anymore when these files are transformed to .html. Can we move to a structure where every chapter is contained in its own folder (as it is already the case with the large "open science basics" chapter), and then link to the folder names? This way, it should resolve always to README as the "entry page" of the respective chapter, both in Github as well as in Gitbook. This is basically what the Gitbook documentation seems to suggest: https://toolchain.gitbook.com/pages.html Mar 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lambo lambo

@mcancellieri mcancellieri

@helenebr helenebr

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lambo @mcancellieri @helenebr