Joakim
00255cb105
- Add class-based template comparison to differentiate styling variants - Implement template deduplication based on structure + class signatures - Add GetCollectionTemplate method to repository interface and implementations - Fix collection item creation by replacing unimplemented CreateCollectionItemAtomic - Add template selection modal with auto-default selection in frontend - Generate meaningful template names from distinctive CSS classes - Fix unique constraint violations with timestamp-based collection item IDs - Add collection templates API endpoint for frontend template fetching - Update simple demo with featured/compact/dark testimonial variants for testing
21 lines
1.2 KiB
HTML
21 lines
1.2 KiB
HTML
<!-- insertr collections is defined with .insertr-add -->
|
|
<div class="insertr-add">
|
|
<!-- the collection containers children are collection items. -->
|
|
<!-- this is meant mostly for structural elements such as cards, testimonials etc. -->
|
|
<!-- it is not meant for text editing (such as multiple paragraphs) and you should instead use .insertr-content -->
|
|
<div class="variant-1">
|
|
<!-- The cards content can be edited as normal insertr elements -->
|
|
<h2 class="insertr">Card 1</h2>
|
|
<p class="insertr lead">This is a lead paragraph</p>
|
|
<p class="insertr">This is the main paragraph that could be longer and give additional info</p>
|
|
</div>
|
|
<!-- Since the developer has defined two templates in the markup two templates must be generated. -->
|
|
<!-- they might have different structure, or been styled differently. (imagine an alternating color on testimonial cards). the variant-x classnames are only for ilustration and is not a keyword -->
|
|
<div class="variant-2">
|
|
<h2 class="insertr">Card 2</h2>
|
|
<p class="insertr">This is the main paragraph that could be longer and give additional info</p>
|
|
<button type="button insertr">Call to action</button>
|
|
</div>
|
|
</div>
|
|
|