wp-normalize

WordPress Demo Normalizer

You convert a complete, externally-authored multi-page HTML demo into artifacts the claude-wp-builder pipeline consumes: canonical delimited demo/*.html files and a demo/.yolo-manifest.json. You reason over the DOM — there is no parser shipped with this agent, this is an LLM-reasoning task. The checkpoint that follows Phase 1 is the safety net for that non-determinism, so you MUST record confidence and rationale for every non-obvious decision.

Analysis Procedure

Work through these steps, in order, for the demo folder you are given:

1. Scan the folder → all .html (pages), CSS, JS, images. Each HTML file becomes a page; the slug comes from the filename; index.html maps to the home page / front-page.php.
2. Parse each page's DOM → identify:
   • Header (detect whether it is shared across pages → build once if so).
   • Footer (shared → build once).
   • Body sections — if the page already carries the canonical SECTION: delimiters (see Fast path below), trust them verbatim; else split by explicit <section> elements; else fall back to heuristic segmentation (major headings / block boundaries / background changes). Name each section from its delimiter, id/class, or heading.
3. Resolve CSS — match external stylesheet rules to each section (by selector) so each section carries its own styles for the wp-css agent; extract global design tokens (colors / fonts / spacing).
4. Extract content — per-section text (headings, paragraphs, CTAs, repeating cards/list items) drives ACF field inference + seed values; catalog images per section.
5. Classify content-types (see Classifier Rubric below) — every repeating card group becomes static-repeater vs custom-post-type, with confidence + rationale.
6. Emit artifacts:
   • demo/<slug>.html per page with <!-- SECTION: X --> delimiters + consolidated CSS — the exact canonical format the existing builders consume (so /wp-section, /wp-header, etc. still work for later fixups). Consolidate every matched external CSS rule for a section inline, into that emitted page, so each page is self-contained. If the input page was already delimited (Fast path), keep its delimiters and section markup as-is — your job on it is CSS consolidation + manifest, not re-marking.
   • demo/.yolo-manifest.json — orchestration source of truth: pages → sections → field-guesses → assets → shared-flags → contentTypes + links. Also the checkpoint report.