Took the v3.0 recipe for Oscar, ran it through the converter, produced a FVS app spec in two modes.
Reads a v3.0 recipe, produces a FVS-compatible app:
| Mode | Output | Use case | Status |
|---|---|---|---|
| A — Static mirror | Rendered HTML + downloaded assets + fvs-app.json | Archival, backup, snapshot | done |
| B — Live edit | fvs-app.json with editable content blocks | Operator wants the content editable | done (spec) |
| C — Hybrid | Static shell + editable zones | Marketing sites, speed + selective edit | same code path |
Source: wp-oscar.freshvibeapps.com (WordPress + Elementor)
Recipe: 7 pages, 28 assets, 10 interactions, 134 DOM root nodes
Converter output (Mode A):
Converter output (Mode B):
[
{"type": "site-header", "source_role": "header", "fvs_confidence": 0.6},
{"type": "nav", "source_role": "navigation", "fvs_confidence": 0.6},
{"type": "modal", "source_role": "modal", "fvs_confidence": 0.6},
{"type": "rich-text", "source_role": "content", "fvs_confidence": 0.6,
"text": "Learn with Nature"},
{"type": "rich-text", "source_role": "content", "fvs_confidence": 0.6,
"text": "Explore the World of Trees"},
...
]
The classifier looks at the DOM role hint from v3.0 and maps to FVS block types:
| DOM role | FVS block |
|---|---|
| hero | hero |
| header | site-header |
| footer | site-footer |
| navigation | nav |
| sidebar | sidebar |
| modal | modal |
| form-section | form |
| testimonial | testimonial-carousel |
| team | team-grid |
| pricing | pricing-table |
| features | feature-grid |
| gallery | image-gallery |
| card-section | card-grid |
| cta | cta-banner |
| content | rich-text |
rich-text but should be hero. The v3.0 role inferrer needs visual signals (large text + image + button) to detect heroes.# Scan a site python3 fvre_v3_scan.py https://example.com --out recipe.json # Convert to FVS app (static mirror) python3 fvre_v3_convert.py recipe.json --mode A --out ./my-fvs-app # Or convert to editable FVS spec python3 fvre_v3_convert.py recipe.json --mode B --out ./my-fvs-app-edit
Now we have a spec format that describes the FVS app. v3.2 wires up the FreshCards editor so the operator can edit any of the content blocks inline. The spec stays the same — v3.2 just adds the editing surface.