Architect layer

Design

The name, addresses, meta and appearance of this project. Saved settings are read at runtime — a change shows on the next page load, with no rebuild.

Blocks

Every block this project can build a page from, drawn by the real renderer. Grouped by what the block is for.

A block is the unit a page is made of. A page here is not a laid-out file — it is a LIST OF BLOCKS. The renderers are already compiled; the page says which kinds stand on it, in what order and with what text. That is why every page in the project looks like one product rather than like the work of five different people.

flow01

How something works, as steps that light up in turn with a spark running along the link between them. Order is the CONTENT here, not decoration — that is what separates it from an olist in a box. Movement is pure CSS (styles/globals.css): it works with JavaScript off and stands still for prefers-reduced-motion. The wording never dims — only the frame, the glow and the numbered node do, because text faded with opacity drops below the contrast threshold.

How it works

Three steps, and the third feeds the first: the loop is the product.

  1. Stand the server up

    An installer robot leaves you an operating system, a starter template, a control panel, storage and authorization — already wired together.

  2. Work where you work

    Sync with GitHub, clone onto your own machine, open your usual editor. The data keeps coming from your server; only the code runs locally.

  3. Push, and it is live

    A push starts a deployment on your own server, and the visitor sees the new version.

carousel01

Slides the reader turns. NO auto-advance, deliberately different from the showcase it was taken from: motion that cannot be stopped takes away the right to finish reading. Turning is a radio input plus a CSS rule, so it works with JavaScript switched off, and every slide sits in the markup where a crawler sees it. Limit: ten slides.

Step by step

Each slide is one move; nothing advances on its own.

first step

The server is born

A clean machine becomes a working contour without anyone configuring it by hand.

second step

The project arrives

The repository is yours; the code travels to it and back with one action.

third step

The change is live

What was edited appears at the address people visit.

Powered by Fractera