wp-classic-themelisted
Install: claude install-skill roama-studio/skills
# Classic WordPress theme from a static site
A migration, not a redesign: the static site the client approved is the
source of truth. Markup, classes, ids, `data-*`, CSS and JS move as they
are; only the source of content (SCF, WordPress) and form sending (CF7)
change. A reference build is the free ROAMA base theme (https://github.com/roama-studio/roama-wp-theme): the
same structure, SCF Local JSON, CF7, leads, importer and client docs.
## 1. Before any PHP: audit and plan (write it down)
Write `WP-MIGRATION-PLAN.md` in the project:
- **Pages**: slug, template, where the content comes from.
- **What repeats** across pages (header, footer, modal, hero, CTA, contact
tiles) -> one template part each, with `$args`.
- **One data source per thing**: the same services on Home and Services =
ONE repeater; dishes on Home and Menu = ONE custom post type; event types
in a slider, a filter and a form select = ONE taxonomy.
- **What must NOT be editable**: section order, heading ids used by CSS/GSAP,
decor, logos, UI icons, aria-labels, service labels, the developer credit.
- **JS that depends on markup**: list every id/`data-*` the scripts read.
Content hard-coded in JS (a slides array) moves to JSON printed by PHP.
## 2. Content model: decide every element
For each element: **fixed / editable / repeatable**, and **short / long**.
| Kind | Field | Rule |
|---|---|---|
| title, button, tag, nav label, price, counter | SCF text | **Character Limit always** (`maxlength`) +