Yesterday we built the engine. Today, under the same banner, run it and see it, we open web design. By the end you will know how to build a site where one source file feeds every page, so the machine does the typing and you do the thinking. This is the part most agencies hand-make and overcharge for.

The first move is to put your real content in one structured file. A simple data file, the kind a person and a machine can both read. Your services, your prices, your pages, all of it lives in that one place. Stop scattering the truth across a dozen hand-typed pages where it rots.

The second move is to point your coding agent at that file and tell it to generate the pages from it. The agent reads the data, then writes the actual web pages around it. Change one line in the source file and every page that uses it updates. You edit the truth once, not in twenty spots.

The third move is to name your design choices. Your red, your black, your spacing, your font, written as plain settings the agent reuses everywhere. These are called design tokens. Now the site looks like one studio, not ten different moods, because every page pulls from the same short list.

The fourth move is to actually look. Have the agent open the page in a headless browser, a browser with no window, and take a screenshot. Then you both stare at the picture. A model can write a page that is technically fine and still ugly. Looking at it catches what the code cannot.

The proof is the office site itself. Every page you see at our public office is built from that one source file, by the agent, checked in the browser. Nobody hand-types the pages. When we add a service, we add a line, and the site grows itself.

That is web design done by the machine: one source of truth, generated pages, shared tokens, eyes on the result. Tomorrow we make the boring work run on its own. Until then, open office.temerarii.xyz and notice how the pages all rhyme. That is the source file talking.