Reader/editor toggle on every page
Gitbook users with writer or admin privileges should be able to toggle between reading and viewing on any given page. If a true toggle/switch is prohibitively complex to implement, this would work: A link to edit on every page in the reader view ( A link to read on every page in the editor view Clicking the link opens a new tab so the reader/editor* can have both views open *On our team, most of us are both readers and editors…. That’s why we’re using a wiki and not a CMS. ;) This is broader than but overlaps with several existing feature requests: “Reader view toggle” “Preview option for private space” “Edit this page link”
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.
Hide "last updated X days ago" text
Ability to hide the "last updated X days ago" text. My customers don't feel comfortable seeing that we are changing the documentation often (even if it's a very small format change).
Restrict merge ability of writers
Option to restrict the abilities of writers, or a whole new permissions group, allowing the ability to send a sort of "pull request" to the maintainers. This would allow public modification of a wiki without worrying about unsolicited changes being published.
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
Allow fixed-widths on table columns
It'd be nice to be able to set a fixed column width on tables, so they could be used as the "column heading". An example would be https://help.flumeapp.com/misc/keyboard-shortcuts.html where the keyboard combination and descriptions differ in length between page sections.
API blocks long-term improvements
We have received a lot of feedback about GitBook's API methods blocks. It's one of the most controversial feature of the new GitBook. A lot of you love it, and at the same time, it has a lot of flaws. This post serves as an announcement that we are looking to improve API blocks in the long-term, and it could result in a complete redesign of the feature. It also serves to gather and summarize all your feedback, and discuss possible solutions with you. ---------------- Long term and capability issues ---------------- Integration with standard formats (Swagger, OpenAPI) This could be a great long-term improvement for API blocks. Description should support rich blocks Like hints, quotes, code blocks, links, bold etc. It could be especially useful for deprecation warnings Parameters descriptions should support richer formatting Such as links, bold, inline code. Or even lists and code blocks. Float types for request parameters We should be able to add examples of request parameters For example for request body. Missing standard way to document response headers ---------------- Usability issues ---------------- Description lines height is too small Reordering parameters New parameters are added to top of their categories It's not obvious how to add specific response code Some people only discover the "+ Add Response Example" button, but they don't see that they can edit the code name directly. Copying API methods or part of them is hard Pasting inside API methods does not work sometimes