PDF Export (and other formats?)
Would be good to be able to export one or section or entire book to PDF or some other format?
Hide GitBook trademark "Powered by GitBook"
The trademark visible to visitors of a GitBook space could be hidden as an option. This option would probably be reserved to non-free plans.
When using GitBook for reading code documentation, it's quite glaring to be forced to switch to a bright screen when going back and forth between a code editor (usually dark) and the documentation. I made a quick mockup of what it could look like. This could come as a dark mode toggle on the user end, as an option for the book editors, or in the form of further style customisations that allow something like this to be done.
Currently an image covers the whole width. Instead let the user control the image's width and allow them to arrange in grid.
It's frustrating to be stuck with the stock gitbook styles when paying for a premium product.
Support for footers
Ability to include a footer at the bottom of every page. Links, copyrights, texts, you name it!
Landing page for a space
Can you implement a landing page for the organizations and spaces ? This feature gives a project all what it needs, like a landing page and it's space contents Landing page could be html, css, and js. User can put his own. I don't know if makdown support for landing page could help or not.
Action to duplicate pages
Very useful, if you've many api methods to clone pages and change the parameters.
It would be great to be able to edit a space while offline. For example, using a desktop app. The legacy desktop Editor app allowed to edit your content while offline. This is no longer possible, unless you're using the GitHub synchronization and you are manually editing your git repository clone locally. Related topics: - Offline access https://docs.gitbook.com/what-is-new/important-differences#desktop-app - Desktop app https://docs.gitbook.com/what-is-new/important-differences#desktop-app
HTTP API to access and update content
Currently, developer.gitbook.com is restricted to the Legacy gitbook. We have a need to use the API in order to automate the display of some pages from our books into an external system (a Discord Bot). Our needs for our own project is simple: - Listing all pages of a book in a hierarchical format JSON file, including the title, slug (path), and Description (the part between the title and contents). Of course, one would expect that the feature set currently documented on developer.gitbook.com be implemented. Additionally, I'd see the following could be implemented: - Generate branch from trunk or branch. - Delete branch - Rename branch (name/path) - Get page info (like my "list all pages" but for only one page) - Edit page info (change path, description, title) - set page parent/position ("move" a page) Editing a page's content might be beyond the scope of this API, but I'm sure some would find it useful. Though tbh it can be done through git.