Skip to content
← All articles
6 min read

Prerendered static site without client framework: how anaxita.com is built

For anaxita.com, we chose a prerendered static site without client framework in production. Pages are generated as static HTML during the build, eliminating React and Node.js from the production environment while keeping infrastructure straightforward.

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.
Questions

FAQ

Didn't find an answer — ask on the call or in Telegram.

Why use React if it is completely stripped from production?

React provides structured templating, reusable components, and developer ergonomics during development. Prerendering extracts static HTML while sparing visitors the download and execution cost of a JavaScript runtime.

Why avoid Google Fonts?

Fetching fonts from external servers introduces extra DNS lookups, TLS connections, and network dependencies that can delay text display. Self-hosting assets on the same origin ensures predictable loading.

How does the Go backend stay secure and maintainable?

Relying strictly on the Go standard library avoids third-party dependency vulnerabilities and framework upgrades. The service only parses form input, validates fields, and sends the notification to Telegram.

Related service

Go backend development for business applications

We build the server side of web products and develop existing systems. Data, traffic and reliability requirements come first, so the architecture fits the work it needs to do.

Learn about the service
Other articles
Contact

Shall we discuss your task?

Thirty minutes on a call — and you understand the architecture, timeline and engagement format. No obligations.

Or message us on Telegram →Follow our Telegram channel →

Enter your Telegram or email so we can reply.

We reply within 15 minutes.