Auto-input
This is the build-side counterpart to Automation testing; together they drive the Time savings & ROI. It’s the decision + sequence layer over the per-platform workflow guides.
The key fact: auto-input is a distinct lever only on WordPress and Duda. On Astro there is no separate “auto-input” step — content goes in as code, in Claude Code, as part of building the page.
| Platform | Mechanism | Separate auto-input lever? |
|---|---|---|
| WordPress | SEO Navigator MCP tools | Yes |
| Duda | Dev Mode (no API) | Yes |
| Astro | Direct code in Claude Code | No — inherent to coding |
1. WordPress — via MCP
Section titled “1. WordPress — via MCP”Content and pages are created through the SEO Navigator MCP, no manual wp-admin clicking.
| Step | Tool(s) | Notes |
|---|---|---|
| Blog drafts | create_draft / update_draft | markdown or HTML body; deploy_md_to_site for the GitHub-markdown flow |
| Code-first pages | create_page_from_code | HTML/CSS/JS → Gutenberg <!-- wp:html --> with auto-scoped CSS |
| Elementor layouts | the Elementor MCP tools (build-page, add-*, apply-template, duplicate-element) | reuse/duplicate existing Elementor templates |
| Taxonomy / media | auto tag/category resolve in deploy_md_to_site; upload_media | names → IDs resolved per target site |
Guides:
- WordPress · Blog posts
- WordPress · Pages (Gutenberg / Elementor)
- WordPress · Code-first pages
- WordPress · Elementor template duplicate
2. Duda — via Dev Mode (no API)
Section titled “2. Duda — via Dev Mode (no API)”Duda has no API for building templates. All layout and content population is done through Dev Mode — there is no Pages v2 / Page Elements API path for the template build, and this SOP deliberately does not reference one.
Guide:
The output is a published Duda site; QA then runs output-only against both the preview link and the live URL (see Automation testing §4).
3. Astro — direct code in Claude Code (no separate auto-input)
Section titled “3. Astro — direct code in Claude Code (no separate auto-input)”On Astro, everything is done directly in code inside Claude Code: writing
.astro files, routes, and components, and putting content straight into the
source. Populating content is an inherent part of coding, not a separate
mechanism like WP’s MCP or Duda’s Dev Mode.
Where automation actually helps on Astro is the build pipeline skills:
figma-to-astro— Figma design → Astro template plus a section spec JSON (docs/<project>-pages.json). That spec JSON is the oracle the content-fidelity test consumes (see Automation testing §1).clone-to-astro— Duda clone → Astro migration (assets, mojibake fix, page generation, zero-CDN verify, deploy).
Route mechanics (when needed) use the MCP Astro tools — guides:
4. Why the two parts belong together
Section titled “4. Why the two parts belong together”- On WordPress / Duda, auto-input and testing are two separate mechanisms you invoke in sequence (populate → audit the rendered URL).
- On Astro, they converge in the code: the same spec JSON produced while building is exactly what the content-fidelity test asserts against. Build and verify are one loop.
This is why the ROI model treats the Astro code + content phases as merged, but keeps them separate for WP/Duda.
What’s next
Section titled “What’s next”- Automation testing — the QA-side counterpart.
- Content + Design team workflow — the two-role flow auto-input plugs into.