| name | html-ppt-zhangzara-soft-editorial |
| en_name | Deliver a Digital-Transformation Roadmap like a Big-Four Partner |
| zh_name | 像四大合伙人一样交付数字化转型路线图 |
| description | A digital-transformation roadmap for a legacy insurer — the diagnosis, the sequenced bets, and the operating rhythm to land them. Built as a decision-grade consulting deck for client executives.
|
| en_description | A digital-transformation roadmap for a legacy insurer — the diagnosis, the sequenced bets, and the operating rhythm to land them. Built as a decision-grade consulting deck for client executives.
|
| zh_description | 像四大合伙人一样交付数字化转型路线图——一份可商业交付的咨询交付 Deck，围绕真实主题、证据链与决策目标组织。
|
| tags | ["consulting","consulting-final-deck","strategy","consulting-deliverable","client","decision-deck","commercial-slide-agent","html-ppt-zhangzara-soft-editorial"] |
| triggers | ["consulting-final-deck","consulting","Deliver a Digital-Transformation Roadmap like a Big-Four Partner","像四大合伙人一样交付数字化转型路线图","consulting-deliverable","strategy","client","html deck","html slides"] |
| od | {"mode":"deck","upstream":"https://github.com/zarazhangrui/beautiful-html-templates/tree/main/templates/soft-editorial","upstream_license":"MIT","preview":{"type":"html","entry":"example.html"},"design_system":{"requires":false},"speaker_notes":false,"animations":false,"category":"consulting","scenario":"strategy","example_prompt":"Create \"Deliver a Digital-Transformation Roadmap like a Big-Four Partner\" as a decision-grade Consulting deck in this template's own visual system. Subject: A digital-transformation roadmap for a legacy insurer — the diagnosis, the sequenced bets, and the operating rhythm to land them. Audience: client executives. First ask only for missing essentials: audience, decision target, source-of-truth materials, deadline, and must-keep numbers. Then produce the slide plan, written slides, visual direction, speaker-ready structure, and a critic pass against this rubric: would a client know what to do Monday morning."} |
Soft Editorial
Cormorant Garamond serif on warm paper with sage, blush, and lemon accents.
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: high
- Density: low
- Slides in demo: 12
Best for
Anything that should feel literary, elegant, and unhurried: editorial features, longform brand stories, gallery / museum decks, advisory deliverables, wedding / lifestyle media, founder essays. Equally good for tech, research, or business decks that want a Sunday-supplement warmth instead of corporate polish.
Avoid for
Decks that need visual heat or punch — the warm-paper palette and Cormorant serif are intentionally quiet.
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.
