Using atlas
A survey sheet: the blog index is a map you pan and zoom, posts placed as cards in tag regions with a minimap; Geologica throughout.
Like every official theme in the gallery, atlas implements theme contract 1.1: every colour flows through the tokens below, the stylesheet lives in the theme cascade layer so your unlayered overrides always win, and any template it does not ship falls back to the default theme's copy.
Install
One config line, or one command:
# cherry.exs
theme: "atlas"
$ cherry config theme atlas
Then cherry build (or cherry serve while you look around). Nothing else moves: your content, your overlays for other themes, and your token overrides for other themes stay where they are.
The styling ladder, applied to atlas
Restyling costs exactly as much ownership as you choose to take. In order:
Rung 1 - override a token. The manifest below is atlas's public styling API. Overrides land in every page head, survive theme upgrades, and are validated against the manifest (a typo is an error, not a dead line):
$ cherry config tokens.--color-accent "light-dark(#0b6e6e, #5ad1c4)"
$ cherry theme.tokens # shows the merged view
Rung 2 - custom.css. Drop assets/custom.css into your site and it links after the theme stylesheet and the tokens block on every page. atlas's own CSS lives in the theme cascade layer, so a plain selector in your unlayered file beats the theme without specificity games or !important.
Rung 3 - overlay a template. Write themes/atlas/templates/<template>.html.eex (or .html.heex) in your site and it shadows just that template.
Rung 4 - eject. cherry theme.eject <template> copies the original into that overlay directory with a provenance header, so cherry theme.diff can tell you forever after whether upstream moved under your copy.
Rung 5 - a theme of your own. cherry gen.theme mytheme --from atlas scaffolds the whole thing - manifest, templates, stylesheet, islands - into themes/mytheme/, yours deliberately.
The theming reference covers every rung in depth; the theme guide walks rung 5.
Token API
Colour tokens are light-dark() pairs: one override sets both renditions, and the theme toggle flips a single color-scheme property.
Surface and text
| Token | Light | Dark | Role |
|---|---|---|---|
--color-bg |
#f4f6f2 |
#0b1417 |
Page background. |
--color-surface |
#e9ede6 |
#122024 |
Raised ground: code blocks, inline code. |
--color-fg |
#172221 |
#e3ebe9 |
Body text. |
--color-muted |
#56676a |
#8fa3a3 |
Secondary text: metadata, nav, footer. |
--color-border |
#cfd7d1 |
#22353a |
Hairline rules and control borders. |
--color-accent |
#0b6e6e |
#5ad1c4 |
Links and interactive accents. |
--color-accent-strong |
#075353 |
#8fe6dc |
Hover/active accent. |
--color-selection |
#cfe9e6 |
#153e3d |
Text selection ground. |
Syntax highlighting
| Token | Light | Dark | Role |
|---|---|---|---|
--syn-keyword |
#0b6e6e |
#5ad1c4 |
Syntax: keywords. |
--syn-string |
#7a5a00 |
#e4c46a |
Syntax: strings and characters. |
--syn-comment |
#7d8a8a |
#6f8484 |
Syntax: comments (italic). |
--syn-function |
#8a2f7a |
#e49ad8 |
Syntax: functions and methods. |
--syn-constant |
#b4461a |
#ffa270 |
Syntax: constants, numbers, booleans. |
--syn-type |
#1d5ea8 |
#7fb7ff |
Syntax: types, modules, tags, attributes. |
--syn-variable |
#172221 |
#e3ebe9 |
Syntax: variables and default code text. |
--syn-punct |
#56676a |
#8fa3a3 |
Syntax: punctuation and operators. |
Type and measure
| Token | Default | Role |
|---|---|---|
--font-prose |
'Geologica', system-ui, 'Segoe UI', Roboto, sans-serif |
Reading and display face (Geologica, self-hosted 22 KB latin subset, OFL). |
--font-mono |
ui-monospace, 'Cascadia Code', 'SF Mono', Consolas, 'DejaVu Sans Mono', monospace |
Structure and code face. |
--measure |
42rem |
Reading column width. |
Templates
atlas ships 3 of the 9 templates in the contract; the rest resolve to the default theme's copy, so they stay current without you owning them. Overlay or eject any name in either list.
Shipped by atlas
| Template | Assigns | Purpose |
|---|---|---|
layout |
@site, @inner, @page_title, @head_extra, @nav, @search, @page_class |
Outer HTML shell wrapped around every rendered page. |
page |
@site, @doc |
A freeform page from the pages collection. |
post_list |
@site, @posts |
Reverse-chronological index of published posts. |
Inherited from default
| Template | Assigns | Purpose |
|---|---|---|
post |
@site, @doc |
A single blog post with title, date, and tags. |
tag |
@site, @tag, @posts, @story_href |
Published posts carrying one tag; links to the tag's story when one exists. |
portfolio_timeline |
@site, @portfolio, @cv_href |
The timeline mode of the profile: dated entries, open source; cv_href links the switcher back to the CV view when public. |
story |
@site, @tag, @portfolio, @posts |
One tag across the whole story: portfolio entries plus blog posts. |
cv |
@site, @cv |
The employer-shaped CV: cv-curated entries in the careers layout, print-first. |
not_found |
@site |
The 404 page. |
Working with an agent
Cherry ships a skill that teaches a coding agent the operating loop above - the ladder, the CLI verbs, and the recovery playbook - so you can say "make the accent electric blue, the Cherry way" and it will reach for cherry config tokens.--color-accent instead of forking the stylesheet. Install it into your site's .claude/skills/ (sites scaffolded with cherry new already carry AGENTS.md describing the same loop), then ask in terms of outcomes:
- "Warm up atlas's palette for both renditions" - the agent lists the manifest with
cherry theme.tokens, overrides rung-1 tokens, and verifies withcherry check. - "Tighten the reading column" - one token:
--measure. - "Restyle the post list" - rung 2 in
assets/custom.cssif CSS reaches it,cherry theme.eject post_listif structure has to change.
The one rule to hold an agent to: never edit the theme's own files under themes/atlas/ unless they were ejected there on purpose - cherry theme.diff will name anything that drifts.