Documentation
Done Differently

You’re in one of two states, your docs are out of sync, or your docs are non-existent.

This has been the plight of my software engineering career. It doesn’t matter if it’s a personal project I’m trying to ship or working with my team to release a new design-system site that actually communicates our brand ethos.

The problem? You’re forced into tools outside your own code, tools that don’t run at 60 fps or reflect the level of polish you build into your product.

Current offerings are too domain-specific and often bolt on a separate build step or have incentives outside of building great docs, which we all know is a problem.

I never understood why I had to write the source code and then write the same thing again for documentation. It goes against the first thing you learn as an engineer, don’t repeat yourself.

I built renoun to fix this, to let you focus on the quality and craft you pour into your product every day, and showcase that same quality through your documentation.

Documentation is the soul of your company, it shouldn’t feel like every other product because you’re not every other product, you’re renoun.