- HTML 100%
e14bab7e74
Generated output (PNG/HTML + thumbnails, PDF/PPTX) stored directly in git (no LFS) so a plain git clone yields real files with no git lfs pull step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| hero_slides_intro | ||
| test | ||
| test2 | ||
| .gitattributes | ||
| .gitignore | ||
| README.md | ||
hero_slides_decks
Pre-generated hero_slides decks, published as a
git-linked collection so a deployed hero_slides instance can pull the slides
(including their already-rendered output) without regenerating them.
Decks
| Deck | Slides | Output |
|---|---|---|
hero_slides_intro |
6 | PNG |
test |
1 | PNG + PDF + PPTX |
test2 |
5 | HTML + PPTX |
Each deck folder holds its source (*.md, theme.md, instructions.md,
metadata.toml) and its generated output/ (rendered images/HTML + thumbnails).
The metadata.toml content hashes match the shipped output, so a linked instance
treats every slide as up-to-date and will not attempt regeneration.
Large files
Rendered assets (*.png, *.html, *.pdf, *.pptx) are stored via Git LFS.
After cloning, run git lfs pull to fetch them (the hero_slides collection link
does this automatically).
Use as a collection
In the hero_slides admin UI: Link from Git with this repo's clone URL, then Pull. The three decks appear as a collection; the deployed instance serves the pre-rendered slides directly.