Launch a new site with Forge

End-to-end: intake → Brand DNA → build → Inspector gate → ship.

Overview

Launching a site on Creytix is one continuous path, not five disconnected tools: you answer an intake, lock a Brand DNA, build against it, clear a QA gate, and ship — all inside the same workspace. This guide walks that path start to finish, naming which department owns each step so you know where to go next.

How it works

A launch moves through four stages, each owned by a different Creytix department:

Forge turns your intake answers into a pattern brief and a locked Brand DNA — the tokens, copy voice, and route classes everything downstream inherits.
Studio and Design Labs build against that DNA — content blocks, pages, and the design system your brand actually uses.
Inspector runs its pre-ship checks against what you built, and blocks the ship if something fails.
Ship takes a cleared build and publishes it, wiring release events and search indexing on the way out.

Nothing here is a black box — you can stop at any stage, review what's been generated, and send it back before it moves forward.

Steps

•
Start the Forge intake
Open Forge from the Creytix Control Panel and answer the intake: what the site is for, who it's for, and the route classes it needs (storefront, blog, booking, and so on).
•
Lock your Brand DNA
Forge turns your answers into a pattern brief and a Brand DNA — palette, type, voice, and component defaults. Review it and lock it. Everything built after this point inherits from here.
•
Scaffold the site
With Brand DNA locked, Forge scaffolds the site structure — pages, route classes, and content slots — ready for editing.
•
Build in Studio and Design Labs
Fill in content through Studio's CMS and asset workspace, and confirm the shared component matrix in Design Labs matches what your brand needs.
•
Wire the Connect tools you need
Turn on any Connect tools the site depends on — Mail for campaigns, Scheduling for bookings, Checkout for commerce — before you ship, so nothing's missing on day one.
•
Clear the Inspector gate
Run Inspector's Protect checks and the CI gate. Fix what's flagged, or make an explicit call to accept a finding — the gate is honest about what it caught, not a silent pass.
•
Ship
Once the gate is clear, publish through Ship. Release events fire, and IndexNow pings search engines that new pages exist.

Capabilities

One intake, one Brand DNA — every later stage reads from the same lock, so a page can't quietly drift off-brand.
Department handoffs, not manual re-entry — Forge's output is what Studio builds against; Inspector's gate is what Ship reads before publishing.
Stop-and-review points — Brand DNA lock and the Inspector gate are both deliberate checkpoints, not automatic pass-throughs.
Connect tools opt in per site — you wire only the fleet services a given launch actually needs.

Limits & honest scope

This is a guided build path with human checkpoints, not a fully autonomous site generator.