Philosophy
Server-first by default
The default path favors HTML, routes, and predictable request handling instead of pushing every project into a client-heavy architecture.
About
Wevoa exists to make the web stack feel more coherent.
The project brings together a language, runtime, framework, CLI, and distribution story so the full experience from install to deployment feels intentional instead of stitched together.
Identity
One product surface
Wevoa is a language, runtime, framework, CLI, and distribution story designed to feel coherent from install to deployment.
Direction
Small surface, real capability
The goal is not to imitate every existing stack. The goal is to provide a simpler stack that still handles real product needs.
What makes Wevoa different
The language and framework are designed together.
- Language semantics, templates, routing, and CLI are part of one system.
- The default path is HTML-first and server-rendered, not client-heavy by assumption.
- Installer, runtime, docs, and starter packs are treated as first-class parts of the product.
Current direction
Public-ready, still focused.
Wevoa is already usable for websites, dashboards, internal tools, and language/runtime experimentation. The next stage is expanding ecosystem quality, deployment paths, and documentation while keeping the core system small and understandable.