Dev tool websites consist of so many pages. A blog, feature pages, use case pages for jobs to be done or persona, roadmaps, resource libraries, courses, community. You name it. And when you look at those great successful dev tool companies they have it all.

But you don’t need it all right away. You need a solid MVP. And build from it later.

The way I see it, the minimal viable dev tool website, has a homepage, docs, and pricing. You also need a solid navbar showing login, signup, contact us, and maybe a GitHub icon if you are open source.

Docs will typically be somewhere else and owned/done by someone else, typically the product or technical writing team. But they need to be visible on the website.

At the beginning having an About Us or Company page may also be important. It builds trust when you haven’t built your brand yet. That would be it. It supports the core needs of the developer and lets them self-serve. Everything else is extra. But these are non-negotiable. The most important website traffic will go through these pages. You should nail them cold. As if you don’t whatever developer traffic you manage to drive will not convert.

Over time, depending on your product and go-to-market motion you add case studies, comparison pages, blog articles, integrations, code examples or templates, video tutorials, and live sandboxes. You add whitepapers and an enterprise page. You create feature pages, use case pages, and persona pages. You create resource libraries and courses that organize all this other content. You add community and events pages or developer portals.

All of that is heavily dependent on your strategy. If you think going for written content is the way to go, as it often is, you need a blog. If you are in a very competitive niche or have a big incumbent you’ll need comparison pages. If you are going after enterprises you’ll likely need case studies and an enterprise page. If your product is horizontal but you see devs use it often for a few clear use cases, you should create those pages.

But all of that is step two. The core needs to work. Spend your time and prioritize accordingly.