Backend of the sub-market template (spec agreed section by section with

the customer workflow in mind: the customer fills one XLSX per sub-market,
an importer builds the page).

- Frontend layout 21 'Sub-Market Page' in the existing
  BackendLayoutDataProvider: six zones, one per Figma section, emitted as
  colPos110..colPos160 - the JSON groups plus appearance.layout are the
  front-end contract (spec clause 7.17). A first attempt via page-TSconfig
  BackendLayouts was the wrong mechanism next to the provider and was
  removed again
- New Content Blocks vitec_markethero, vitec_marketintro,
  vitec_marketinsights (field bags, serialized unprefixed under data);
  the workflow section reuses intro-paragraph + vitec_card flip cards
- Stories gained quote/quote_person/quote_role (Testimonial tab),
  maintained once per story, emitted on every story card; usecaselist
  gained the layout value 'testimonials'
- New plugin vitec_productfeature: one referenced product as a full
  product card, serialisation shared with the product list (cObj made
  protected for the subclass)
- vitec_productlist gained hand-picked product selection: exactly the
  chosen products in the editor's order, category filter ignored,
  visibility filters kept - closes the long-standing single-select gap
- New CLI vitec:generate-submarket-workbooks: one protected customer
  XLSX per sub-market (9 main markets, 25 sub-markets from the Market
  category tree) - dropdowns filled live from the database, named ranges
  as the importer contract, hidden Meta sheet pinning submarket/group/
  record uid, soft character-limit warnings, asset URL fields

Verified end to end on Broadcast & Media: layout-21 payload with colPos110
carrying the hero element and its subline. Spec raised to v1.20.
This commit is contained in:
orasche committed 2026-10-02 10:18:36 +02:00
1 parent f0b0694842
commit 90ae6803a4
31 files changed
+493 -7

No files matched your search

@@ -27,6 +27,15 @@ final class BackendLayoutDataProvider implements DataProviderInterface
'hero' => 1,
'sidebar' => 2,
'preFooter' => 3,
// Sub-market template sections (spec 2026-10-01): one slot per Figma
// section. The headless JSON groups these as colPos110..colPos160 -
// that grouping IS the front-end contract for layout 21.
'smHero' => 110,
'smIntro' => 120,
'smWorkflow' => 130,
'smTestimonials' => 140,
'smProducts' => 150,
'smInsights' => 160,
];
/** Per-frontend-layout: title + ordered list of zones. */
@@ -52,6 +61,7 @@ final class BackendLayoutDataProvider implements DataProviderInterface
18 => ['title' => 'Content Page V3', 'zones' => ['hero', 'main', 'sidebar', 'preFooter']],
19 => ['title' => 'Events Overview', 'zones' => ['hero', 'main']],
20 => ['title' => 'Contact Page', 'zones' => ['hero', 'main', 'sidebar']],
21 => ['title' => 'Sub-Market Page', 'zones' => ['smHero', 'smIntro', 'smWorkflow', 'smTestimonials', 'smProducts', 'smInsights']],
];
/** Display name for each zone. Shown as column header in the BE page module. */
@@ -60,6 +70,12 @@ final class BackendLayoutDataProvider implements DataProviderInterface
'hero' => 'Hero',
'sidebar' => 'Sidebar',
'preFooter' => 'Pre-Footer',
'smHero' => '1 · Hero',
'smIntro' => '2 · Intro',
'smWorkflow' => '3 · Workflow (header + flip cards)',
'smTestimonials' => '4 · Testimonials',
'smProducts' => '5 · Products (featured + list)',
'smInsights' => '6 · Industry Insights',
];
public function getIdentifier(): string