Yes — keep the product data separate from the catalog page layout. That is the easiest way to update specs or pictures later without rebuilding the page.

*Local demo / Diagram · Spreadsheet → data file → filterable page*
Recommended shape
- Source spreadsheet — SKU, category, specs, image links. Treat this as the source of truth.
- Data file in Drive (JSON/CSV/table the page reads) — Buda converts the spreadsheet into this once, then you refresh it when products change.
- Catalog page — filters by category, cards open to specs/images. The page only *reads* the data file; it should not hard-code product rows.
Skip ordering and payments for v1, as you said.
How to brief the first build
Ask Buda roughly like this:
Build a filterable product catalog. Put product rows in a Drive data file generated from my spreadsheet. The page should filter by category and open a card for specs and images. Do not bake product data into the page layout. Later I will only refresh the data file and images.
Optional naming convention for images: sku-angle-use.ext so the data file can point at stable paths.
Steps
- Upload the spreadsheet (and images) to Drive.
- Ask Buda to generate the data file + a simple catalog page that reads it.
- Check filters and one or two detail cards.
- For updates: change the spreadsheet → regenerate/refresh only the data file (and new images) → reload the page.
How to verify
- Change one price or add one image in the data file → the catalog shows it without a layout rebuild.
- Filter by category still works after the refresh.
- Cards still open the right specs.
Boundaries
- If product fields keep changing every week, freeze a small “card schema” (name, category, 3–5 spec fields, images) so the page stays stable.
- A full rebuild is only needed when you change the *page design*, not when you edit product rows.