Theme Customization
Revela lets you customize a theme without touching the original theme files. You override only what you want, and everything else falls back to the installed theme.
Overview
βοΈ Footer Text
Set your studio name (or clear it) via site.json, no extraction needed.
π¨ Colors & Type
Edit native CSS Custom Properties in Assets/main.css for colors, spacing, and fonts.
π§© Override Files
Extract only the templates or assets you want to change, and the rest stays managed.
Quick Win: Footer Text
The footer shows whatever you put in site.copyright in your site.json, with no theme editing required:
{
"copyright": "Β© 2026 Jane Doe Photography"
}
Leave it blank to hide it, or set it to your own attribution.
Change Colors, Spacing & Type
Lumina exposes its design tokens as native CSS Custom Properties in Assets/main.css. To tweak them, extract that one file and edit it.
Using the interactive menu (the usual way):
- Run
revelawith no arguments to open the menu. - Go to Addons β theme β extract.
- Pick Lumina, choose Select specific files, and select
Assets/main.css.
Prefer the command line?
revela theme extract Lumina --file Assets/main.css
Either way you now have themes/Lumina/Assets/main.css. Edit the tokens in :root:
:root {
--color: light-dark(hsl(0 0% 20%), hsl(0 0% 80%));
--color-bg: light-dark(hsl(40 30% 98%), hsl(220 15% 8%));
--content-max-width: 900px;
}
This is the browser-native standard: light-dark() gives automatic dark mode and clamp() gives fluid spacing. No JSON, no template edits.
Preview as you go: run
revela serveand refresh your browser.
How Theme Resolution Works
When generating, Revela resolves a theme in this order:
- Local theme:
themes/<name>/in your project (highest priority) - Installed theme: from a NuGet package or the bundled theme
- Default: Lumina
So a themes/Lumina/ folder in your project overrides the bundled Lumina, and you only need to place the files you actually changed.
Extracting a Theme
Via the menu
Run revela β Addons β theme β extract β choose a theme β then:
- Extract entire theme: copies everything (great for a full restyle)
- Select specific files: pick just the files you want to override
Via the command line
# Full extraction β themes/Lumina/
revela theme extract Lumina
# Extract under a different name β themes/MyTheme/
revela theme extract Lumina MyTheme
# Only specific files or folders
revela theme extract Lumina --file Body/Gallery.revela
revela theme extract Lumina --file Assets/
# Overwrite existing files
revela theme extract Lumina --force
--file (-F) selects a file or folder; --force (-f) overwrites without asking. For a full extraction, --force replaces the whole themes/<name>/ folder. The target name must be a single folder inside themes/, so names such as .. or absolute paths are rejected.
See what's available first:
revela theme list # installed themes (add --online for NuGet)
revela theme files # files in the active theme (--theme to pick one)
Theme Structure
A full extraction of Lumina looks like this:
your-project/
βββ themes/
β βββ Lumina/
β βββ theme.json # Theme description (name, version, templates)
β βββ Layout.revela # Main page layout
β βββ Assets/ # Static assets (copied as-is)
β β βββ main.css
β β βββ main.js
β βββ Body/ # Page body templates
β β βββ Gallery.revela
β β βββ NotFound.revela # 404.html (rendered once at the output root)
β β βββ Page.revela
β β βββ Photo.revela
β βββ Configuration/
β β βββ images.json # Responsive image sizes
β β βββ site.json # Template for your site.json
β βββ Locales/
β β βββ en.json # UI text (buttons, labels, screen-reader text)
β β βββ de.json
β βββ Partials/
β βββ ContentImage.revela # Required: renders 
β βββ GalleryGrid.revela # Renders [[gallery]] blocks
β βββ PhotoFigure.revela # Renders [[photo: β¦]] blocks
β βββ Image.revela
β βββ Navigation.revela
β βββ HeaderNavigation.revela
β βββ Favicon.revela
β βββ OpenGraphImage.revela # og:image for social previews
β βββ ...
βββ source/
βββ project.json
βββ site.json
Templates, partials, assets and Configuration/images.json override the installed theme file by file: extract a file and it becomes yours, while everything you don't extract keeps loading from the installed theme. To change only the image sizes, extract just that file and edit it:
revela theme extract Lumina --file Configuration/images.json
Theme Language
Lumina's own text (the menu button, photo navigation, "Close photo", the
screen-reader labels for aperture, shutter and focal length, the statistics page
headings, calendar legend defaults) follows language in site.json:
{
"language": "de"
}
Lumina and its extensions ship English (en) and German (de). Revela tries
the exact language first (de-CH), then the language without region (de),
then English. Your own content (titles, descriptions, Markdown) and EXIF values
are never translated. Month and day names from format_date follow the same
language.
A site has one language. Revela does not build multilingual sites (the same
pages in several languages with a language switcher). The revela command line
itself is English, and page titles written by revela create page (such as
"Photo Statistics") are plain front matter you can change to your language.
Change a Wording
Each theme keeps its text in Locales/<language>.json, a flat list of
"key": "text" pairs:
{
"photo.close": "Foto schlieΓen",
"photo.return_to": "ZurΓΌck zu {0}"
}
{0}, {1}, β¦ are filled in by the theme (for example with the gallery name).
To change a wording, extract the file and edit it:
revela theme extract Lumina --file Locales/de.json
Your themes/Lumina/Locales/de.json is merged key by key on top of the
installed text, so you may also delete every line except the ones you changed;
keys the theme adds in a later version keep working. Extension text lives in a
subfolder named after the extension, e.g.
revela theme extract Lumina --file Locales/Statistics/de.json β
themes/Lumina/Locales/Statistics/de.json. revela theme files lists all
locale files.
Add a Language
Create themes/Lumina/Locales/<language>.json (e.g. fr.json) with the keys
from en.json translated, and set "language": "fr" in site.json. Keys you
leave out fall back to English.
Building or Deeply Changing a Theme
Required partials, the shared image helpers, editing templates, UI text, image sizes and theme extensions are covered in Theme Authoring, in the developer section.
Tips
- Start small. Extract only the files you actually change.
- Version control. Commit your
themes/folder. - Prefer CSS Custom Properties. For visual tweaks, edit the tokens in
Assets/main.cssrather than templates. - Update-friendly. When the bundled theme updates, your extracted overrides stay put.
- Preview locally. Keep
revela serverunning in a second terminal; after each edit, runrevela generate alland refresh the browser (there is no live reload).
See Also
- Theme Authoring: build a theme or change templates
- Configuration: project and site settings
- Source Structure: how galleries and pages map to templates