This week the hub is opening, and the first thing anyone touches is the website. So today is only about web design. By the end you will know how to build a site that updates itself instead of rotting the day after you launch it. No mystery, just the moves we used on our own front door.

First move. Stop thinking in pages, start thinking in sections. A header, a service block, a footer. Each one is written a single time as a component. You feed it words and it draws itself. When the same service block appears on ten pages, you are not editing it ten times. You edit the one block, and all ten follow.

Second move. Keep your content in a plain file, not buried inside the design. A list of services, prices, hours, sits in one source file. The page reads from it. So a client changes their hours once, in one place, and every page that shows hours is correct. The old way scatters the same fact across a dozen files and lets one go stale.

Third move. The repetitive markup is a job for a coding agent in the terminal. You describe the section in plain words, it writes the clean code, you check it in the browser. You stay the editor with taste. The agent is the fast pair of hands. That is how one person ships a full site in a day without cutting corners on the parts that show.

Here is the proof, and it is honest. The site you would visit for the hub is built exactly this way. One source file, sections that render themselves, an agent doing the typing. When we change the week, the whole site changes with it. We are not selling you a method we do not run on ourselves.

So that is web design the way the hub does it. Sections written once, content in one file, an agent for the heavy lifting. Your step today is small. Go see it live at office.temerarii.xyz, then take your own worst page, the one with the wrong hours, and rebuild it as one section reading from one file.