# Home
CherryBomb: two cherries with a lit fuse and sunglasses

A static site generator
for all the hackers

A modern take on static site generation: typed content, deterministic builds, themes that survive upgrades. One binary, fuse lit.

Quick-start Docs GitHub

macOS / Linuxcurl -fsSL https://cherrybomb.dev/install.sh | sh
Windowsirm https://cherrybomb.dev/install.ps1 | iex
## One CLI to rule them all No Node, no bundler, no config safari. Install the binary, then watch how far four commands go. Real output throughout, because this site is built by the same tool it describes. ### 1 · Plant ```sh cherry new junovale ``` ```text * creating cherry.exs * creating .gitignore * creating README.md * creating AGENTS.md * creating .claude/skills/publish/SKILL.md * creating content/pages/index.md * creating content/pages/about.md * creating content/posts/2026-08-19-hello-cherry.md * creating static/images/.gitkeep Your orchard is planted at junovale. Next: cd junovale cherry serve # live-reloading dev server cherry check # the verifier agents build against cherry gen.action # GitHub Pages deploy workflow ``` A working site, a first post, and an `AGENTS.md` that teaches the whole workflow to whatever coding agent you point at it. `cherry serve` gives you live reload from the first second. ### 2 · Write ```sh cherry gen.post "Growing season" --json ``` ```json { "ok": true, "command": "gen.post", "data": { "date": "2026-08-14", "path": "content/posts/2026-08-14-growing-season.md", "slug": "growing-season" } } ``` One file, valid frontmatter, `draft: true`. The envelope hands back the path, so pipe it straight into your editor, a script, or whatever else does your writing. Markdown is GitHub-flavoured, and the things markdown is bad at are one directive away: ```text ::figure{src="/images/harvest.jpg" alt="Crates at dusk" caption="Season one."} ::video{youtube="q6Yr9DkTn2k" title="The talk"} :::tip{title="Rule of thumb"} Size the queue for the promise, not the traffic. ::: ``` Figures with captions, video embeds that make zero third-party requests until clicked, and callouts. Framework-level, so they survive a theme swap. ### 3 · Verify `cherry check` builds the whole site in memory, writes nothing, and returns structured diagnostics. Here it catches a link to a page that doesn't exist: ```sh cherry check --strict --json ``` ```json { "ok": false, "command": "check", "error": { "code": "check_failed", "message": "Checked 12 page(s): 1 error(s), 0 warning(s).", "details": { "errors": 1, "diagnostics": [ { "file": "content/pages/reading.md", "rule": "broken-link", "severity": "error", "message": "links to /guides/pruning/, which this build does not emit" } ] } } } ``` The diagnostic names the file, the rule, and the problem. Fix it, run again, exit 0. That's the verifier loop: build, check, fix, repeat. A broken link cannot reach production, because the deploy workflow runs the same check before it builds. ### 4 · Ship ```sh cherry build ``` ```text Built 12 page(s), 2 asset(s) → _site ``` Same tree in, same bytes out: builds are deterministic, so your CI can prove nothing drifted. Push, and the GitHub Actions workflow from `cherry gen.action` deploys Pages. That's the entire pipeline.
## Make it yours without forking anything Styling is a ladder, and the first rung is one command: ```sh cherry config tokens.--color-accent "#7c3aed" ``` ```sh tokens.--color-accent: light-dark(#b3173e, #f4718c) → #7c3aed (written to cherry.exs) ``` The write is surgical: comments and layout in `cherry.exs` survive byte-for-byte, and the override lands as one entry in the keyword list: ```elixir tokens: ["--color-accent": "#7c3aed"] ``` Every theme publishes its tokens as an API (`cherry theme.tokens` lists them, documented). Light and dark are one value: tokens are `light-dark()` pairs, so the theme toggle flips a single `color-scheme` property and print always comes out clean. Need more than tokens? Drop an `assets/custom.css` that always wins, overlay a single template in EEx or HEEx, or `cherry theme.eject` with provenance recorded so upgrades merge instead of freezing. Each rung costs exactly as much ownership as you take.
## More than a blog roll The same content tree that builds your posts can carry your whole developer story. Portfolio collections (positions, projects, talks, open source, education) render a **timeline** at `/portfolio/`, **story pages** that cross-link everything sharing a tag, and a **`/cv`** shaped for employers: curated bullets, evidence-backed skills, a print stylesheet that produces a clean one-pager, and a machine-readable `cv.json` in JSON Resume format. All of it static, all of it typed, all of it checked by the same verifier as the blog. [Build yours in one guide.](/guides/portfolio-and-cv/)
## Start here The [quick-start](/guides/quick-start/) goes from install to a deployed site in fifteen minutes. The [guides](/guides/) are project-shaped: build a portfolio with a hosted CV, create a theme of your own, wire up an agent. The [docs](/docs/) cover every verb, every config key, and every schema, with real output for all of it. This very site is Cherry's own dogfood: every page here is also [plain markdown](/index.md).