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.
The showcase carousel, ported one-to-one from the storefront: auto-advance every five seconds with a 700ms crossfade, slides grouped in threes, arrows that shift a whole group, numbered circles that pause on click and show ‖, a progress line that follows the pause, a glow that appears once the image has loaded, lazy loading of the current and next group, and a pause when the section scrolls out of view. Colours come from the theme, not from the storefront palette. Every slide also sits in a hidden block for crawlers — the carousel reveals one at a time through script.
Step by step, how it works
Five seconds per slide; click a circle to hold it.
Your server
placeholder — image coming soon
Your repository
placeholder — image coming soon
Your address
placeholder — image coming soon
Your data
placeholder — image coming soon
Your server
Credentials — and it is ready
Your repository
The code is yours from day one
Your address
One action to publish
Your server
Credentials — and it is ready
Infrastructure right after purchase
A clean machine becomes a working contour: site, panel, agents, memory, database and storage, without anyone configuring them by hand.
Infrastructure right after purchase — Your server, Credentials — and it is ready
A clean machine becomes a working contour: site, panel, agents, memory, database and storage, without anyone configuring them by hand.
The project arrives in your GitHub — Your repository, The code is yours from day one
What travels there is the application; the cockpit stays on the server, which is why an editing mistake cannot break it.
The change is live — Your address, One action to publish
What was edited appears at the address people visit, without a pipeline to configure first.
Memory that survives the session — Your data, Four stores, one door
Rows, files, meaning-search and a graph of connections sit behind one key on the machine you own.