Model local data → WordPress-driven data

Some hand-authored sites render their main content from JavaScript data: an empty container like <div id="newestGrid"></div> is filled at runtime by a mount call (mountGrid('#newestGrid', newestObjets(4))) that maps over an in-file array (const OBJETS = [ … ]). Others render repeated content cards directly in static HTML, such as a blog/archive index of post-preview cards. On a straight carry these grids are empty or non-native in the block editor — the data lives in JS or fixed HTML, not WordPress records.

This skill reads the source and produces a data-model.json describing how to make the data WordPress-driven: records + taxonomy + per-item meta, native core/query loops in place of the mounts/cards, and a faithful card render — while the source's styling, animation, filtering, and detail-modal JS keep running (reading WordPress data from per-card DOM islands).

The deterministic converter (liberate_convert_local_site) consumes the file; this skill only authors the model by reading the source.

When it applies

Run this BEFORE liberate_convert_local_site when the source has any of:

• empty mount containers (<div id="…"> / <ul id="…"> with no children) filled by JS,
• an in-file data array of records (each with a stable id),
• a list/grid/catalog/gallery rendered by mapping that array to card markup,
• optionally a detail modal that looks an item up by id (ARR.find(x => x.id === id)).