Four parts, one product
1. The builder
A single-page application. On the left: your pages, your files, and the component palette. On the right: the live preview, which is not a picture of the page — it is the page, updating the moment a property changes. You can build from the palette or click directly in the preview; both sides edit the same document. Projects save to a single file and re-open byte-for-byte identical (proven — see the testing page).
The palette holds sixteen components, each with its own name: CrestHeader (site header), CascadeMenu (dropdown navigation), HeroStage (the big opening section), Headline, TextBlock, PictureFrame (one picture), SlideRiver (a slideshow whose speed the visitor chooses, with Back and Next buttons), VeilPlay (video behind a protection toggle), ActionButton, FlowColumns, ReachForm (contact form), MapFrame, SocialRow, SiteGate (accounts for the exported site), FootBar (footer) and BreatherSpace.
2. The export engine
One action — Export — writes a complete, standalone website folder: the pages, their stylesheet and script, the media, a configuration file, a plain-language README (Read Me), and the server bundle below. The export is a file the owner keeps. There is no lock-in and no rent: the exported site runs anywhere the small server runs, and the static pages open from the folder even with no server at all.
3. The server bundle (exported with every site)
A small, dependency-free server that gives the exported site its living parts:
- Real accounts. Registration and sign-in with roles — the first account registered becomes the site's administrator; later accounts are members. Passwords are stored only as salted scrypt hashes; sessions are stored hashed, in cookies marked HttpOnly (HyperText Transfer Protocol Only) and SameSite=Lax.
- A mail endpoint. The contact form delivers into the site's own outbox as real mail files, which the administrator reads in the admin view. A submission is never silently dropped.
- Password recovery by a single-use, expiring token delivered to the outbox; a reset kills the old password and the old sessions.
- Privacy rights built in. Every account holder can download all of their data and delete their account, and deletion is real — the row is gone and the sign-in then fails. Consent is recorded at registration.
- An append-only audit log of security events, in order, with no passwords in it — ever.
- Protections baked in. Cross-site request forgery tokens, output encoding against cross-site scripting, parameterised database queries against injection, path-traversal refusal, login rate limiting, and a full set of security headers on every response.
- Protected video. With the VeilPlay toggle on, a video file cannot be fetched by its direct path — only through a signed, expiring address. Forged and expired addresses are refused.
4. The installers
One file per platform, per the house rule: download, click, the setup runs, the software opens itself, and an icon is left behind.
- Linux: a single self-extracting setup (32,682 bytes) carrying the whole builder; its payload integrity is verified against a built-in checksum manifest before anything is installed.
- Windows: a single native setup program (813,033 bytes) with the payload embedded. It carries a built-in self-test that verifies every file it carries before installing, then extracts the files and creates Desktop and Start Menu shortcuts.