Documentation is the product

Documentation is one of the first things developers will interact with when they're learning, and it's the thing they'll keep coming back to as they integrate deeper.
This means we need to treat it as a first-class citizen.

— Zeno '@zenorocha' Rocha, Co-founder and CEO of Resend in Resend's Philosophy

When I joined Bucket a few weeks ago, Rasmus '@makwarth' Makwarth started by introducing me to Bucket's first principle: Quality over quantity.

We prioritize craftsmanship. Because we're building a developer-first product, a feature management tool for B2B engineers, this applies to documentation, too. To quote @zenorocha, "documentation is not auxiliary to the product — documentation is the product." As developers, it's one of the first things we read when evaluating a new tool. Great docs are vital. We want our docs to be as polished as our product, as thoughtful and helpful as possible for a consistent, joyful experience. Our documentation must reflect Bucket's first principles.

GitBook powers our docs, as part of a design-driven decision, and we recently sat down with Addison Schultz, Developer Relations Lead at GitBook, to discuss how it helps us create and maintain high-quality developer docs.

Read the full interview on gitbook.com.

If you enjoyed, please add some ❤️🦄🤯🙌🔥 and repost this