How It Works

A reviewed production path

Move fast without skipping the decisions that matter.

Kitten begins with the real WordPress environment, keeps content editable, and separates draft creation from site-wide assignment and publishing.

Five guarded stages

Inspect → Plan → Build Drafts → Review & QA → Publish Separately

01

Inspect

Run doctor and preflight; read theme, templates, permissions, plugins, content, media, languages, forms, SEO, commerce, backup, and rollback context.

02

Plan

Map pages, CMS models, provider ownership, assets, SEO, localization, and every site-wide change before presentation work.

03

Build Drafts

Create CMS-backed pages, entities, products, components, and pending Media Library assets without publishing.

04

Review & QA

Validate manifests, compare the real draft with the source, audit content and providers, and review fingerprinted assignments.

05

Publish Separately

A human explicitly approves assignments and each publish action only after target-specific evidence is reviewed.

Why draft-first

WordPress stays authoritative and every risky change remains visible.

Drafts preserve editorial review and revisions. Provider-owned data stays with its plugin. Homepage, navigation, template, theme, permalink, visibility, cache, media approval, restore, and publishing decisions remain explicit.

Start safely

Connect, inspect, and create the first reviewed draft.