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.
24 lines
1.7 KiB
XML
24 lines
1.7 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<xliff version="1.2">
|
|
<file source-language="en" datatype="plaintext" original="messages">
|
|
<body>
|
|
<trans-unit id="title"><source>VITEC · Market Insights</source></trans-unit>
|
|
<trans-unit id="description"><source>Sub-market template, section 6: two paragraphs, optional CTA, optional video card with person.</source></trans-unit>
|
|
<trans-unit id="text1.label"><source>Paragraph 1</source></trans-unit>
|
|
<trans-unit id="text1.description"><source>Plain text, max ~250 characters.</source></trans-unit>
|
|
<trans-unit id="text2.label"><source>Paragraph 2</source></trans-unit>
|
|
<trans-unit id="text2.description"><source>Plain text, max ~250 characters.</source></trans-unit>
|
|
<trans-unit id="cta_label.label"><source>CTA label</source></trans-unit>
|
|
<trans-unit id="cta_label.description"><source>Empty = no button.</source></trans-unit>
|
|
<trans-unit id="cta_target.label"><source>CTA target</source></trans-unit>
|
|
<trans-unit id="cta_target.description"><source>Section anchor OR URL. Empty with a label set = /success-stories.</source></trans-unit>
|
|
<trans-unit id="video_person.label"><source>Person</source></trans-unit>
|
|
<trans-unit id="video_role.label"><source>Role / title</source></trans-unit>
|
|
<trans-unit id="video_title.label"><source>Video title</source></trans-unit>
|
|
<trans-unit id="video_url.label"><source>Video URL</source></trans-unit>
|
|
<trans-unit id="video_url.description"><source>Empty = no video card, text runs wider.</source></trans-unit>
|
|
<trans-unit id="video_cover.label"><source>Cover image</source></trans-unit>
|
|
</body>
|
|
</file>
|
|
</xliff>
|