A website is usually described as a marketing surface. That is true, but incomplete.
For a small software company, the website is also a product surface. It holds positioning, navigation, documentation, legal pages, pricing, notes, and proof that the team knows how to ship.
The site has workflows
A visitor does not experience the website as a folder of pages. They experience it as a sequence:
- understand the company
- inspect the product
- check credibility
- read the thinking
- decide whether to trust the team
Each page should help that sequence continue.
The site has architecture
The repository should make repeated work easy:
- shared layouts in the theme
- app-local content for site-specific writing
- predictable route files
- a small number of reusable section frames
- checks that catch broken pages before deploy
That is product work, not decoration.
The site has maintenance cost
Every clever page becomes a future maintenance bill. A good website system makes new pages cheaper without making them look generic.
That balance is why components matter. They keep the interface coherent while leaving enough room for each page to say something specific.
The site should keep changing
A static website becomes stale because the company keeps learning. Treating the site as a product gives those learnings a place to go.
Related Notes
Continue through the same thinking system.