Daisy Days
Cheerful pastel deck with hand-drawn daisies, stars, and rainbows. Friendly, soft, and warm.
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: light
- Formality: low
- Density: medium
- Slides in demo: 10
Best for
Anything that should feel friendly, soft, and joyful: educational content, kids and family, wellness programs, community workshops, creator portfolios for craft / illustration. Also lovely for an unexpected playful internal kickoff, a wedding planning deck, or any moment where warmth is the message — including across tech or business contexts.
Avoid for
Contexts where the audience explicitly expects authority and precision — the hand-drawn pastel SVG decorations are the opposite of buttoned-up.
Workflow
- Clone
example.html into the user's workspace as the working file.
- 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-daisy-days" 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-daisy-days3description: A customer-success workshop onboarding users to a project-management app — the first-value path and the habits that retain. Built as a decision-grade professional training deck for new customers, CS team.4---5
6# Daisy Days
7
8> Cheerful pastel deck with hand-drawn daisies, stars, and rainbows. Friendly, soft, and warm.
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:** light
17- **Formality:** low
18- **Density:** medium
19- **Slides in demo:** 10
20
21## Best for
22
23Anything that should feel friendly, soft, and joyful: educational content, kids and family, wellness programs, community workshops, creator portfolios for craft / illustration. Also lovely for an unexpected playful internal kickoff, a wedding planning deck, or any moment where warmth is the message — including across tech or business contexts.
24
25## Avoid for
26
27Contexts where the audience explicitly expects authority and precision — the hand-drawn pastel SVG decorations are the opposite of buttoned-up.
28
29## Workflow
30
311. **Clone `example.html`** into the user's workspace as the working file.
322. **Replace placeholder content** with the user's real headlines, body copy,
33 numbers, names, dates, and section labels. Match existing dimensions when
34 swapping image placeholders.
353. **Preserve the design system.** Never substitute fonts, recolor the palette,
36 restructure the layout grid, or strip decorative elements (corner brackets,
37 paper grain, geometric shapes, illustrated SVGs). They are part of the
38 identity.
394. **Adjust deck length by duplicating layouts.** If the user has more content
40 than the demo holds, duplicate an existing slide of the most appropriate
41 layout. If less, drop slides from the bottom. Update page-number labels.
425. **Designing missing layouts:** if a slide needs a layout the template
43 doesn't have, design it from scratch using the same fonts, palette,
44 decorative vocabulary, spacing rhythm, and component grammar — never bail
45 to a different template.
466. **Keep the navigation runtime as shipped.** If the deck ships an
47 `assets/deck-stage.js` or inline keyboard handler, leave it intact.
48
49## Output contract
50
51Emit between `<artifact>` tags:
52
53```
54<artifact identifier="zhangzara-daisy-days" type="text/html" title="Deck Title">
55<!doctype html>
56<html>...</html>
57</artifact>
58```
59
60## Source & license
61
62Vendored from upstream MIT-licensed
63[`zarazhangrui/beautiful-html-templates`](https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/daisy-days).
64
65The full upstream MIT license text — including the original copyright notice — ships in this skill at
66[`LICENSE`](./LICENSE) and must be redistributed alongside any copy of `example.html`,
67`template.json`, or any vendored `assets/` runtime. See `template.json` for the upstream metadata snapshot.
gabrielmoreira