Trunk is a dev tools company that builds engineering velocity software. And with such a strong focus on developers, they understand their audience well enough to know that what they really care about is the details.
โOur marketing site is for product-focused people,โ explains Eli. โBut most engineers will look right past all that and head to the docs for the nuts and bolts. So we invest heavily into making sure our docs are detailed, inviting and modern.โ
For Trunk, that of course meant packing the documentation with useful information โ but the team also wanted to give readers a great experience. They needed powerful customization options, as well great version control and a safety net when they need to make bigger changes across all their pages.
โWe were using ReadMe for all of our documentation,โ says Eli. โThe design left a lot to be desired โ I think visually it feels quite stale.โ Beyond the visual design, the team also found that they couldnโt do basic things that they expected, like adding tabs to explain different processes and workflows.
But the Trunk team also struggled when it came to keeping track of changes. โReadMe has a custom versioning concept that made it really hard for the team to update documentation,โ Eli tells us. โPeople would be in the wrong version, or people would create a new version with new edits, but they wouldn't back-fill into an old version. We were constantly like, โwhere are we at?!โ.โ
To overcome these challenges, Eli and the team moved their documentation over to GitBook. Not only did our recent customization improvements help them create beautiful, branded docs โ our two-way Git Sync also helped them work on bigger changes right from their repo.
โI love the ability to go in and edit locally through the WYSIWYG editor,โ says Eli. โBut then when there are large changes, I can go in and bulk edit with my IDE, and do a global search and replace.โ Of course, with Git Sync, those changes automatically appear in the teamโs GitBook docs, too, so everything stays up-to-date. โThat's super powerful,โ asserts Eli.
But the team made Git Sync even more powerful by combining it with the tools they built using Trunk itself โ a series of custom linters to check their documentation before it goes live. Those linters check for live links, dead links, formatting errors, SVG compression and more. โWe run all that using Trunk on our own GitBook. Itโs really an awesome way to keep the documentation efficient but in a way thatโs still nicely presented.โ
Presentation, of course, is a big deal for Trunk โ which is why Eli and the team appreciate how much they can customize their GitBook docs. โI think so much of the stuff I care about is the presentation layer,โ he tell us. โHow do I set the Favicon for my site, for example? I think GitBook has the right ethos โ โletโs make sure that this stuff looks beautifulโ.โ
Trunk uses cards, code blocks and more to create beautiful-looking docs in GitBook.
The best part? Getting the rest of the team on board was a breeze. โI basically just said, โOkay everyone, weโre using GitBook, here you go.โโ laughs Eli. โAnd everyone was able to jump in and start making edits instantly. I think thatโs quite telling โ if engineers can just pick up a thing and start using it, then thatโs a big deal.โ
The team had their docs up and running in no time, and now their linters check big changes they make for consistency and accuracy. The docs feel more branded, thanks to nicely-designed cards, and any technical changes the team need to make can go through either a change request in GitBook or a pull request in GitHub. So whatโs next for the Trunk team?
โI want to consolidate all of our documentation โ both internal and external,โ says Eli. โSo I plan to move the entire company from Slite onto GitBook. Iโd rather have one solution for everything.โ
โ Get started with GitBook for free
โ Discover GitBookโs customization options
โ Make your documentation process more collaborative with change requests
