A small, focused product deserves a clear, focused website.

The MVP website is intentionally static. That keeps the cost of change low and makes every page easy to reason about during the period when messaging and product scope are still moving.

Instead of introducing a CMS or a content abstraction layer, the repo keeps page-specific content close to the page that owns it.

If Kevly grows into pricing pages, changelogs, case studies, or a broader product surface, the current structure still holds up. New routes can be added directly under src/app with shared design primitives reused across them.

More complex systems should be introduced only when repeated editing or workflow pain makes them justified.