SOP overview

These SOPs cover the two automation pillars of a template build and quantify the time they save:

• Auto-input — how content and layout get into a template automatically, per platform (WordPress, Duda, Astro).
• Automation testing — how the QA suite runs (SEO, design, visual, agentic, uptime), per platform.
• QA architecture — how the system is built: hosts, data stores (git / R2 / KV), the edge worker, cost budgets, secrets.
• Time savings & ROI — estimated hours saved per template, split by “design ready” vs “from scratch”.

QA console

Live status for every site — SEO, design, visual, agentic, and uptime — is at sn-automation-testing.pages.dev: uptime refreshed every 15 min from the edge monitor (with a 30-day SLO % and latency sparkline per site), an Incidents page, per-site detail with findings + fixes, and the visual Baseline/New comparison with one-click baseline promotion (instant — no re-run). See Automation testing §8.

The build, in five phases

A template build is modelled as five phases. The two pillars touch phases 2–5:

#	Phase	Touched by
1	Design the template	— (from-scratch only)
2	Build structure on the platform	auto-input
3	Auto-input content (text / images / SEO meta)	auto-input
4	QA / testing	automation-testing
5	Fix + re-verify	both

Per-platform at a glance

Platform	Auto-input	Testing
WordPress	Claude MCP tools (drafts, code-first pages, Elementor)	Output audit on the live URL
Duda	Dev Mode (no API)	Output audit on the preview link and the live site
Astro	Done in code — no separate input step	Runs on the source + CI gate

Start with Auto-input, then Automation testing, then read the ROI.