How we built softfix.dev: fast, prerendered and readable by AI

The goal

We wanted a site that feels alive — motion that follows the scroll, a terminal that echoes your project brief as you type, a cursor that reacts to everything — without the usual price of a JavaScript-heavy site: blank pages while code downloads, and content search engines struggle to read.

We also build websites for clients, so this one had to be proof of the approach, not just a brochure.

React, prerendered to HTML

The site is written in React and TypeScript and bundled with Vite. After the normal build, a small script renders every route on the server and writes it out as an HTML file, with the page’s title, description, social cards and structured data already in the head. The browser then “hydrates” the same markup, so the interactive parts come to life without re-drawing the page.

Each page also gets the stylesheet inlined and its fonts and code chunks preloaded, so the first paint doesn’t wait on extra round trips.

Written for AI assistants too

• Every page has a plain-Markdown twin at the same address with “.md” added — clean text with no layout to parse.
• llms.txt and llms-full.txt describe the studio, its services, case studies and posts in one place, following the llms.txt proposal.
• robots.txt explicitly welcomes search engines and AI crawlers.
• Each post starts with a short, direct answer — the paragraph an assistant is most likely to quote.

One source of truth

Services, projects, posts and FAQs live in typed data files. The pages, the sitemap, the RSS feed, the Markdown twins, llms.txt and the schema.org structured data are all generated from that same data at build time. Change a service description once and it changes everywhere, so the different views of the site never drift apart.

Security and privacy by default

• Served as static files: no server-side code on the website to break into.
• A strict Content Security Policy — scripts, fonts and images only from our own domain.
• HTTPS everywhere with HSTS, plus protections against clickjacking and content sniffing.
• Cookie-free analytics, so no consent banner and no tracking across sites.
• Fonts self-hosted and subset to the characters we use, instead of loaded from a third party.

One codebase, two sites

The SoftFix shop at shop.softfix.dev is built from the same code with a single build flag. It shares the design system, navigation and components, but has its own pages, sitemap and structured data — so the two sites look like one company without duplicating work.

What it means for your project

The same approach works for any marketing site, documentation or content-heavy product page: fast for visitors, easy for search engines and AI to read, and cheap and safe to host. If you want your site to be found — by people and by the assistants they now ask — this is how we would build it.