As developers, we constantly interact with documentation. It’s what welcomes us to a project for the first time, it’s a trusted companion that guides us toward celebrating our first “Hello World,” and it’s the first place we turn when we’re frustrated with a bug or curious about a new feature.
Good documentation is at the heart of crafting an excellent developer experience, which is why we’re making a big investment in improving our docs at Apollo. Today, we’re excited to share the first big milestone on our journey: Apollo’s new docs site built with Gatsby! 🚀
From Hexo to Gatsby
Previously, our docs site was built with Hexo, a static site generator, and shared its theme with Meteor. Although we love our Meteor roots, the shared theme was becoming difficult for our team to maintain and evolve over time.
We wanted to migrate to React so we could share UI across all Apollo sites and add interactive elements to our docs. While I wouldn’t normally advocate for a rewrite, our team decided it was necessary in order to modernize our stack. Both our homepage and the GraphQL Summit site are built with Gatsby, so it was an easy choice for our new docs infrastructure.
With nearly 200 repositories in the Apollo organization on GitHub, it’s important that each project’s documentation lives alongside the code. When we first heard about Gatsby’s new themes feature, Apollo engineer Trevor Blades quickly built a proof-of-concept that confirmed it would be perfect for our needs.
Gatsby themes allow you to easily compose UI, configuration, and functionality across multiple sites. Themes are distributed as npm packages, and we use them for sharing versioning logic, constructing the left-hand navigation, common layout components, and more. Not only are Gatsby themes awesome for building docs sites, they’re also great for quickly spinning up derivative sites like Principled GraphQL, which was built by extending
We’ve been really happy with themes so far, and can’t wait to explore them further. Thank you to Christopher Biscardi and the rest of the Gatsby team for all their support along the way! 🤗
Focusing on discoverability
When designing our new UI, we wanted to focus on making our content more discoverable. Previously, our layout displayed too much information on the left sidebar, which made it difficult to find what you were looking for without scrolling. Apollo designer Jess Marina rose to the challenge and created a cleaner layout and navigation structure to solve this pain point.
Cleaner navigation 🗺
For our new docs site, we removed article details from the left sidebar and added a navigation panel to the right of the screen to show users all the topics that would be covered on a page. We also made each section on the left sidebar expand and contract so users could zero in on the pages that are relevant to them.
Prominent search 🕵️♀️
Since our docs site spans a large breadth of content, we wanted to improve the search experience. We moved the search bar to a more prominent location, redesigned the search menu, and added a keyboard command to trigger search.
Looking to the future
We’re happy with the progress we’ve made toward improving the Apollo docs experience, but our work isn’t done yet! Over the next few months, we will be working on a refactor of our information architecture in order to help developers find what they’re looking for faster. Before embarking on this project, we will conduct user testing and publicize a plan to the Apollo community for feedback. If you’re interested in contributing, check out our Docs channel on Spectrum to learn more.
We can’t wait to see what the future holds for Apollo docs, and we hope you enjoy exploring the new site! If you have any feature requests or feedback on the site, please let us know by filing an issue in the Gatsby theme repo.
Stay in our orbit!
Become an Apollo insider and get first access to new features, best practices, and community events. Oh, and no junk mail. Ever.