Common questions about GitBook and the new version
Yes, you can login using the same credentials you used on legacy.gitbook.com (email/password, Google or GitHub login).
Yes, see the detailed page:
Bugs should be reported using the messaging widget available from your dashboard or by sending an email to firstname.lastname@example.org. In order to get the best help possible, please provide as much context on how you encountered the bug. Steps to reproduce the issue are even better.
If you think a feature is missing or should be improved, head to https://gitbook.canny.io/feature-requests. Search for an existing request for the same feature and upvote it, or create a request. Providing relevant use-cases, or user-stories, with screenshots is the best way to make your feature accepted.
For now, we only support GitHub synchronization. We do not support other git hosting services, like GitLab. The content on GitBook is still always backed-up and versioned. Your content is always available to export, so it is never locked on our platform.
We are no longer versioning your books as a Git repository. We have shifted to a GitBook specific versioning system. As a consequence, we no longer offer git hosting services for your books. If you need your documentation to be accessible as a Git repository, you can always use the GitHub synchronization.
GitBook v2 does not officially support exporting to PDFs or ebook-formats.
We have implemented an experimental GitBook PDF (as a "labs" project), it only works on public content for now (contact us if you want to try it out).
We would love to hear from you if you have a use-case that requires PDFs.
All user data and content is stored in the US on Google Cloud.
Some content (e.g: HTML pages) may be cached by our CDN in other countries to improve end-user performance.
The new version of GitBook does not have the same "Explore" feature than the legacy version, since it now focuses on products, teams and companies documentation. Public documentations are still indexed by search engines though and can be found there.
To create and confirm your account, you may be requested to verify your phone number with a verification code sent on your mobile phone.
This extra security step has been set up for several reasons, but the most important one is probably to limit spam and scam content on GitBook. Unfortunately, malicious users and bots are trying to use GitBook to host unauthorized content on our platform. To limit this behavior, we need to verify that you are a real human.
Your phone number will only be used for this security step and you WON'T receive ANY further communication on this channel.
The new GitBook doesn't offer a way to edit documents in their Markdown form. We no longer store Markdown or HTML, instead we store rich JSON data structures. Markdown can still be used as shortcuts or through the GitHub integration. For more details about the reasoning, have a look at "Editing Markdown source".
We're aware of some issues between Google Services and some providers in China that could limit or block your access to GitBook. Most of our users were able to find a solution, using a VPN but we're still monitoring closely the situation.
We have RTL support in mind, but it's not yet ready. For now, only paragraphs and headings will automatically detect RTL text and adapt their layout. Lists and other content blocks are not aligned properly. Also, you may have noticed a poor font quality being used for your language. We have plans for potential custom fonts support, so you should be able to use the appropriate font for your usage.