Quickstart
From zero to first publish: create a workspace, run a Forge intake, and ship your first page.

Overview
This is the fastest path from an empty workspace to a page your visitors can actually see. It follows the same route every new Creytix site takes: a Forge intake sets the plan, Design Labs locks the brand system that plan inherits, Studio is where you fill in the page, Inspector checks it, and Ship carries it to production.
You don't need to understand every department to get through this — just enough of each to move to the next stage.
How it works
Creytix enforces structure before generation. A Forge intake produces a pattern brief and a Brand DNA lock; nothing renders until that lock is set, so your first page is never a blank template guessing at your brand. From there, content and QA follow the same stage model as every other build: Intake → Plan → Build → Review → Guard → Release.
Steps
- •
Connect your workspace
Open the Creytix Control Panel, sign in, and open (or create) the workspace for your site. See Connect your workspace if this is your first time in.
- •
Run a Forge intake
Start a Site Forge intake: answer the pattern brief, and let the Brand DNA lock gate finish before you continue. This is the step every later department reads from.
- •
Fill your first page in Studio
Open Creytix Studio and build your first page from the content blocks Forge scaffolded. Use the SEO sidecar as you write instead of bolting on optimization afterward.
- •
Run the Inspector gate
Before you ship, run Inspector's Protect checks — deterministic SEO, schema, and accessibility checks that catch the obvious mistakes before a human has to.
- •
Ship it
Hand the page to Creytix Ship. A release moves from approval to production, and IndexNow pings on cutover so it gets found.
Capabilities
- One flow, five departments — Forge, Design Labs, Studio, Inspector, and Ship each own one stage of the same path, with no separate logins or exports between them.
- Structure-first generation — the Brand DNA lock gate means your first page is built against your actual brand, not a generic starter template.
- A QA gate before you ship, not after — Inspector's rule checks run pre-release, not as a cleanup pass once something's already live.
- A real release, not a manual upload — Ship handles the approval-to-production hop and pings IndexNow for you.
Limits & honest scope
This quickstart covers the standard Forge intake path — the one every new site takes on day one.
- It is not a guide for migrating an existing site into Creytix or for highly custom builds that skip the standard intake pattern; those need a Forge conversation first, not a self-serve quickstart.
- Some of the deeper Studio and Design Labs surfaces referenced later in the docs (asset manager, component gallery) are still Building — you won't need them for a first publish, but don't expect them at full depth yet.
- This page assumes you already have workspace access. If you don't, see Connect your workspace first.