How to make all markdown files be built into a GitBook site #685
-
I'm using GitBook on a GitLab repo with a CI/CD pipeline. I was wanting all of my markdown files to be transformed into the site, even if not directly linked on the side panel. However, GitBook only seems to be building markdown into html if the page appears in the SUMMARY.md file and thus appear on the side panel. Is there a setting or way to flag all markdown pages to be transformed into site pages, regardless on whether they appear in the SUMMARY.md file? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 18 replies
-
GitBook should automatically index and generate summary.md based on the structure of your folder/repo - are there many markdown files that don't get uploaded? |
Beta Was this translation helpful? Give feedback.
-
No, they're all in the repository and I can navigate to the .md files manually on the site, but they aren't built into pages |
Beta Was this translation helpful? Give feedback.
-
Thanks - and do you have a link to your published gitbook space? |
Beta Was this translation helpful? Give feedback.
-
Ah - can you let me know the steps you're using to generate your portfolio? I believe you're using an old, now deprecated version of GitBook and the Are you using the new version of GitBook? |
Beta Was this translation helpful? Give feedback.
The current version and the one you're using (deprecated/old version) are two separate applications. The CLI is no loner a part of the current GitBook tool.
In order to use the newest GitBook, please sign up for an account at app.gitbook.com/join. You'll be able to import your repository from GitLab via Git Sync. You can find more information on that here: https://www.youtube.com/watch?v=Ly2zQD0I9bY and https://docs.gitbook.com/integrations/git-sync