Build-time React and static HTML generation
We use React and Vite exclusively during the build step. The build process compiles templates and outputs clean static HTML files. Once rendering finishes, the React runtime and component abstractions are discarded completely.
In production, there is no Node.js runtime and no client-side framework. Files reside on disk and are delivered by nginx as pure markup and stylesheets, avoiding runtime server execution or client-side hydration.
A single small client script with event delegation
Interactive functionality on anaxita.com is limited to what visitors actually need and is contained within a single small client-side script.
The script handles toggling light and dark themes, opening the mobile navigation menu, submitting contact requests and the small availability-panel animation. Interactions are wired via event delegation on the document, avoiding individual listeners and third-party UI libraries.
Self-hosted typography and multilingual structure
Instead of loading fonts from Google Fonts, typography files are hosted locally on our own server. This eliminates external network requests during initial rendering and removes external domain resolution from the critical path.
The website serves two languages, placing Russian content under the /ru/ path prefix. Each document specifies canonical and hreflang tags, and an independent sitemap is maintained for each language to support clean search engine indexing.
Standard library Go service for contact submissions
Inquiries submitted through the contact form are processed by a lightweight Go backend implemented using only the Go standard library. The service does not depend on third-party frameworks or an application database.
When a form submission arrives, the Go handler validates the input and forwards the message directly to a Telegram channel.
Validating output through markup testing
Because static HTML is the final deliverable, quality assurance focuses directly on the compiled markup. Automated tests inspect the generated files after each build before deployment.
These tests verify DOM structure, confirm the presence of required metadata and hreflang links, check language attributes, and ensure pages render without missing elements.
Evaluating the trade-offs: fit and limitations
Prerendering without a client framework requires matching technical choices with the nature of the application. It offers distinct advantages for specific use cases but is not a universal replacement for web applications.
- Well suited for marketing platforms, landing pages, corporate websites, and documentation where content changes primarily at release time and interactivity is constrained.
- Not suitable for applications requiring complex authenticated state, live data streams, collaborative editing, or intricate client-side dashboards.
- Editorial workflows require triggering a build and deployment cycle to publish updates, which may not suit teams expecting immediate in-browser content publishing.