Why start with the frontend before Supabase?
Because the first commercial need is a convincing, fast, and deployable public surface. The backend will follow once the product language, routing, and content model are stable.
FAQ
Key implementation questions already have clear answers
This route establishes the future SEO and trust structure for launch documentation and structured content.
Will this still support supplier dashboards later?
Yes. The Nuxt route structure and shared UI system are being set up so the future dashboard, builder, and profile routes can attach without replacing the public experience.
Is the supplier builder part of the initial release?
Not in the first public slice. The initial release focuses on brand, content, and market-facing credibility, then the builder prototype follows as the next major implementation phase.
How does Hetzner and Coolify fit into this phase?
They are the deployment target from day one. Even before live backend services exist, the public Nuxt site can be staged and shipped through the same production environment.