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 Intercom messenger widget available from your dashboard or from www.gitbook.com. 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.
The new version of GitBook no longer supports exporting to PDF and other ebooks format. A lot of rich-content does not translate well from the Web to PDF. GitBook will expose a developer API for people to consume and extend their content. It is not excluded that someone build a PDF export tool using the API, but it will not be officially supported.
Offline access is a different matter, and if relevant, we might implement it officially in the future. It will just not be in the form of a PDF export.
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.