# This site.

> Nuxsol’s own site. A site for a new company that had two kinds of readers from day one.

- Sector: Nuxsol’s own site
- Year: 2026
- Project: Nuxsol
- Client: Nuxsol
- Design and development: Nuxsol
- Live: https://nuxsol.eu
- Services: Digital design, Development, Marketing & growth

This site was built to prove the studio’s own claim: that one page can serve a person and a machine with the same words.

## In the project

- Every page rendered on the server
- A Markdown copy of every page
- llms.txt, robots.txt and a sitemap
- Structured data on every page
- Search palette and machine view

## The challenge

A new company has two kinds of readers from day one: people deciding whether to call, and the AI systems those people ask first. Most agency sites are built only for the first. They reach a crawler as a script and an empty page.

A studio that sells readable websites cannot have one of those. Every claim on the service pages had to be something a visitor could check on the site itself.

## What we built

Every page is rendered on the server, so a crawler receives the same words a person reads. The crawler policy names each search and answer engine. The company, its services and its articles are described in structured data. Every page has a Markdown copy at a predictable address, and llms.txt points to them.

The machine layer is part of the design. The reader switch in the header shows the same content both ways.

## What it runs on

Astro renders the pages on the server. GSAP and Lenis handle motion, on transform and opacity only. The site was built with Claude.

## Who it is for

- The person deciding whether to call: Needs to see what the studio does, and how well, in one visit.
- The crawler: Receives HTML and nothing else. Needs the words to be in it.
- The assistant answering a buyer: Needs a short description it can quote, and a clean copy of each page.

## What we did

### Digital design

Used: Web design.

1. Set the two readers: Every page is designed for a person and for a machine.
2. Design the scenes: Hero, case studies, services, approach, offers and notes.
3. Draw the visuals in code: Interface drawings and case artwork, with no stock imagery.

### Development

Used: Front-end, Astro, Marketing sites, Performance.

1. Render on the server: Astro builds every page as HTML.
2. Generate the machine copies: Markdown, llms.txt, the sitemap and structured data come from the same data as the pages.
3. Add motion last: GSAP and Lenis, on transform and opacity only, with a reduced-motion state.
4. Measure: Speed, accessibility and layout are checked on the production build.

### Marketing & growth

Used: SEO, GEO and AIO, Agent-ready websites, Machine-readable websites.

1. Name the crawlers: Each search and answer engine has its own rule.
2. Describe the company: Structured data on every page.
3. Publish the copies: A Markdown address for every page, listed in llms.txt.

## Design decisions

1. Every page is rendered on the server. A crawler that does not run scripts still receives the full text. The page a person sees and the response a machine gets hold the same words. Instead of: An app rendered in the browser, with a prerender service in front.
2. A Markdown copy of every page. Each page has an address ending in .md, generated from the same data as the designed page, so the two cannot drift apart. Instead of: A separate text version written by hand.
3. The machine layer is shown, not hidden. The reader switch in the header and the terminal in the hero put the Markdown, the schema and the crawler rules in front of visitors. Instead of: Keeping structured data and llms.txt as invisible plumbing.
4. Counted, not claimed. The figures on the home page are counted each time the site is built: pages, Markdown copies, schema types and named crawlers. Instead of: Rounded marketing numbers.

## How it works

1. Rendered on the server: A crawler receives the same words a person reads.
2. Named crawlers: The crawler policy names each search and answer engine.
3. Structured data: The company, its services and its articles are described in a form machines read.
4. Markdown copies: Every page has one at a predictable address, and llms.txt points to them.

## The principle

The same words for a person and for a machine.

## What it is built to change

- Build counts: Pages rendered on the server, Markdown copies, schema types and named crawlers, counted at every build and shown on the home page.
- The same words both ways: Open any page, switch to the machine view, and compare.
