A Git workflow to create, publish and maintain documentation with your team. Minimal time to ship, beautiful out-of-the-box. Centralize technical knowledge, connect to your codebase and collaborate through change requests.
@jessethanley This update includes improvements to our editor but not much for copy/pasting. We have upcoming work planned in our next cycle to continue improving the core editing experience (copy/pasting, performances, multi-language support, etc.).
We'll keep you posted when these improvements are shipped!
I absolutely *love* the UI. Its simplicity makes the reading experience easy — and delightful. Definitely worth the try if you care about developer experience.
@sara_tandowsky1@samypesse Been using Gitbook for a while, great product. Can you please fix the drop downs not closing on click out? Drives me mad. Have to purposely re-click the button to close it. (Macbook, Chrome)
I feel GitBook is the easiest and professional way to document and publish. Such simple, clean and worry free solution.
I was able to setup a new project, link a domain and publish, all with in half hour.
Thank you and Goodluck.
Great product -- always impressed with the SEO performances & ease of workflow management!
Exciting to see the new feature updates, looking forward to trying the new content blocks.😃
I'm sharing this with my team to take a look! We need better ways or organizing documentation and this seems like a cool solution! How does it integrate with my current codebase? Ie, are these docs living in a branch or folder in my repo? Or totally separate? And also does anything happen on PRs when someone merges in new code to check if the docs need updating?
@britt_joiner Good to hear :) When using the GitHub/GitLab integrations, the documentation can be stored either as a directory in the repository or as a branch.
When using PR on GitHub/GitLab, we currently don't check the code to see if the docs need updating (it's definitely something we want to explore in the future ;) ), but we provide preview links to access the visual documentation from the PR.
This has been my favorite tool to publish documentation without any headaches. It's been great so far and I'll keep using it over other documentation tools.
Congrats on the launch :)
Hi ProductHunt 👋
It's been 6 years since we first released GitBook as an open-source project, and today we are excited to launch the 3rd major update to the platform.
From day one, we built GitBook to empower developers and technical teams to embed knowledge and documentation into their daily workflow. Providing a Git workflow with change requests to edit and collaborate on documents and powerful GitHub / GitLab integrations to keep documentation in sync with code. Since then, we've been proud to see over 1.5M docs hosted on GitBook, reaching a collective 70M page views per month.
The major focus of this release has been expanding on that core foundation and delivering a first set of integrations. Here's a quick overview of what's new:
🔌 10 first integrations to connect GitBook to developer and collaboration software like Linear, Sentry, Jira, Arcade, and Figma. With more amazing integrations and custom blocks coming from the community in the next months.
🌈 Fresh new look for documentation published on GitBook, with a stronger focus on accessibility and performance.
🎨 New customization features to empower content creators to publish documentations that perfectly aligns with their brand.
🧩 New content blocks, like cards, expandable blocks, diagrams, and drawings to create advanced interactive content.
We've come a long way in 6 years, and GitBook is now a team of 35 and still hosting some of the world's largest open source documentation. As always, thanks so much for all your support! We are excited about what is coming next for GitBook.
We'll be hanging out in the comments all day to chat ✌️
Read the full announcement on our blog: https://blog.gitbook.com/product...
@samypesse@danielvouch Yeah, we do support OpenAPI. There are blocks dedicated to documenting APIs. You can plug in an OpenAPI specification file, pick the endpoints you'd like to document and we'll make it look pretty. In the future we're probably going to add a full integration for OpenAPI which would build an entire site based on an OpenAPI spec, for now it's done block-by-block.
@samypesse awesome - well done!
In the process of finding the right tool to publicly document an API, will definitely be looking into this a bit more.
🚀