Cormorant Garamond serif on warm paper with sage, blush, and lemon accents.

• Scheme: light
• Formality: high
• Density: low
• Slides in demo: 12

1. Clone

   example.html

   AND the

   assets/

   folder into the user's workspace. This template ships an

   assets/deck-stage.js

   runtime (keyboard navigation, stage rendering); the HTML references it as

   assets/deck-stage.js

   , so the file must sit next to the cloned HTML or that path will 404 in the generated artifact and navigation will silently break. Inlining the JS into a single

   <script>

   block in the HTML is an acceptable alternative when a single self-contained file is preferred.
2. Replace placeholder content with the user's real headlines, body copy, numbers, names, dates, and section labels. Match existing dimensions when swapping image placeholders.
3. Preserve the design system. Never substitute fonts, recolor the palette, restructure the layout grid, or strip decorative elements (corner brackets, paper grain, geometric shapes, illustrated SVGs). They are part of the identity.
4. Adjust deck length by duplicating layouts. If the user has more content than the demo holds, duplicate an existing slide of the most appropriate layout. If less, drop slides from the bottom. Update page-number labels.
5. Designing missing layouts: if a slide needs a layout the template doesn't have, design it from scratch using the same fonts, palette, decorative vocabulary, spacing rhythm, and component grammar — never bail to a different template.
6. Keep the navigation runtime as shipped. If the deck ships an

   assets/deck-stage.js

   or inline keyboard handler, leave it intact.