Editorial Tri-Tone
Three-color editorial system: dusty pink, mustard cream, and deep burgundy, set in Bricolage + Instrument Serif.
A single self-contained HTML deck — typography, palette, decorative system,
and slide vocabulary are all tuned together. Mixing layouts across templates
breaks the system; stay inside this one.
At a glance
- Scheme: mixed
- Formality: medium-high
- Density: medium
- Slides in demo: 8
Best for
Anything that should feel like a fashion-magazine spread: editorial pitches, fashion brand decks, lifestyle media, art direction reviews. Equally good for any deck — including tech, research, or business — that wants tri-tone discipline and serif/sans contrast instead of the usual neutrals.
Avoid for
Decks that need to read as soft or comforting — the burgundy/pink/cream tri-tone is intentionally high-contrast and styled.
Workflow
- 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.
- Replace placeholder content with the user's real headlines, body copy,
numbers, names, dates, and section labels. Match existing dimensions when
swapping image placeholders.
- 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.
- 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.
- 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.
- Keep the navigation runtime as shipped. If the deck ships an
assets/deck-stage.js or inline keyboard handler, leave it intact.
Output contract
Emit between <artifact> tags:
<artifact identifier="zhangzara-editorial-tri-tone" type="text/html" title="Deck Title">
<!doctype html>
<html>...</html>
</artifact>
Source & license
Vendored from upstream MIT-licensed
zarazhangrui/beautiful-html-templates.
The full upstream MIT license text — including the original copyright notice — ships in this skill at
LICENSE and must be redistributed alongside any copy of example.html,
template.json, or any vendored assets/ runtime. See template.json for the upstream metadata snapshot.
1---2name: html-ppt-zhangzara-editorial-tri-tone3description: A type-and-color system for a culture magazine relaunch — the grid, the tri-tone palette, and the layout kit. Built as a decision-grade design craft deck for editorial & design team.4---5
6# Editorial Tri-Tone
7
8> Three-color editorial system: dusty pink, mustard cream, and deep burgundy, set in Bricolage + Instrument Serif.
9
10A single self-contained HTML deck — typography, palette, decorative system,
11and slide vocabulary are all tuned together. Mixing layouts across templates
12breaks the system; stay inside this one.
13
14## At a glance
15
16- **Scheme:** mixed
17- **Formality:** medium-high
18- **Density:** medium
19- **Slides in demo:** 8
20
21## Best for
22
23Anything that should feel like a fashion-magazine spread: editorial pitches, fashion brand decks, lifestyle media, art direction reviews. Equally good for any deck — including tech, research, or business — that wants tri-tone discipline and serif/sans contrast instead of the usual neutrals.
24
25## Avoid for
26
27Decks that need to read as soft or comforting — the burgundy/pink/cream tri-tone is intentionally high-contrast and styled.
28
29## Workflow
30
311. **Clone `example.html` AND the `assets/` folder** into the user's workspace.
32 This template ships an `assets/deck-stage.js` runtime (keyboard navigation,
33 stage rendering); the HTML references it as `assets/deck-stage.js`, so the
34 file must sit next to the cloned HTML or that path will 404 in the generated
35 artifact and navigation will silently break. Inlining the JS into a single
36 `<script>` block in the HTML is an acceptable alternative when a single
37 self-contained file is preferred.
382. **Replace placeholder content** with the user's real headlines, body copy,
39 numbers, names, dates, and section labels. Match existing dimensions when
40 swapping image placeholders.
413. **Preserve the design system.** Never substitute fonts, recolor the palette,
42 restructure the layout grid, or strip decorative elements (corner brackets,
43 paper grain, geometric shapes, illustrated SVGs). They are part of the
44 identity.
454. **Adjust deck length by duplicating layouts.** If the user has more content
46 than the demo holds, duplicate an existing slide of the most appropriate
47 layout. If less, drop slides from the bottom. Update page-number labels.
485. **Designing missing layouts:** if a slide needs a layout the template
49 doesn't have, design it from scratch using the same fonts, palette,
50 decorative vocabulary, spacing rhythm, and component grammar — never bail
51 to a different template.
526. **Keep the navigation runtime as shipped.** If the deck ships an
53 `assets/deck-stage.js` or inline keyboard handler, leave it intact.
54
55## Output contract
56
57Emit between `<artifact>` tags:
58
59```
60<artifact identifier="zhangzara-editorial-tri-tone" type="text/html" title="Deck Title">
61<!doctype html>
62<html>...</html>
63</artifact>
64```
65
66## Source & license
67
68Vendored from upstream MIT-licensed
69[`zarazhangrui/beautiful-html-templates`](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/editorial-tri-tone).
70
71The full upstream MIT license text — including the original copyright notice — ships in this skill at
72[`LICENSE`](./LICENSE) and must be redistributed alongside any copy of `example.html`,
73`template.json`, or any vendored `assets/` runtime. See `template.json` for the upstream metadata snapshot.