Examples
Complete, importable themes and a library of ideas to remix.
Each example page links to a .unixnotis preset bundle. Importing a preset is
the preferred path because the bundle carries the matching config, CSS, assets,
and scripts together.
Each downloadable bundle is refreshed with the CLI used to produce that archive. Inspect and re-export a changed setup
before publishing it so the config, CSS paths, defaults, scripts, and assets stay together.
theme.toml, when present locally, is compatibility metadata only; normal preset export does not
need or include it.
For a guided path that starts with a blank design brief instead of an existing theme, see Build Your Setup.
| Example | Defining technique | Motion model | Data and assets |
|---|---|---|---|
| Hotpink Fade | foundation-only palette and font restyle over stock components | none | stock commands; no bundled assets or scripts |
| Retro Industrial | physical controls made from hard shadows, inset states, paper, and scanlines | none; state changes are immediate | built-in cards; no bundled assets or scripts |
| Kernel Desk | dense monospace telemetry with small, beveled surfaces | none; state is communicated through color and depth | six local system-reader scripts, including two disabled card ideas |
| Anime Styled | position-bound art cards with readability overlays | short toggle state transitions; no repeating animation | three active card images and eight plugin-backed widgets |
| Glitchy Glow | animated cyber console with an intentionally glitching empty state | three active keyframe loops plus interaction transitions | cached market/weather readers and one active card image |
The bundles in this repository are re-exported with the target CLI. Their contents are intentionally dependency-based: unused files are not copied into a new archive. Inspect the archive itself rather than relying on a file count that can change when a preset is re-exported.
Start with the example whose design problem matches the intended setup, not necessarily the one whose colors are closest. Palette, geometry, content, and behavior can be borrowed independently.
Downloaded presets can contain commands and executable files. Review the complete bundle before approving those parts:
noticenterctl preset inspect example-name.unixnotis
noticenterctl preset import example-name.unixnotis --dry-runUse --allow-exec only after every displayed command and executable file is understood. The
individual example pages call out which bundles include scripts or command-backed widgets.
A useful reading order is:
-
config.tomlfor panel composition, widget inventory, media layout, and theme file wiring -
base.cssfor the palette and shared visual language -
panel.cssandpopup.cssfor notification presentation -
widgets.cssandmedia.cssfor controls, cards, and player treatment -
assets/for portable artwork andscripts/for local behavior
When remixing, import into a disposable configuration, edit the resulting config/theme files, run
validation, and export a new bundle. Keep one clear owner for each idea. A borrowed palette belongs
in base.css; a borrowed media shell needs matching [media] config and media.css; a custom card
may also need its script and asset.
Protect local pieces during import with repeatable --except options:
noticenterctl preset import example-name.unixnotis --allow-exec --except config.toml
noticenterctl preset import example-name.unixnotis --allow-exec --except scripts --except assetsRun the dry run first. See Presets for path rules, backup behavior, portability checks, and more selective import patterns.
To make a preset from a local setup:
noticenterctl preset export example-name.unixnotisBefore importing someone else's setup, inspect it first:
noticenterctl preset inspect example-name.unixnotisGive a remix its own name and preview. Mention any external commands, fonts, icon themes, or local services it expects, even when those dependencies are not embedded in the bundle.
