Forgejo Themes — Custom themes & landing page for Forgejo
  • CSS 91.5%
  • Go Template 6.7%
  • JavaScript 1.8%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
WillFatty dd789960b4 Style issue and PR filter search controls
Set the filter search input to a consistent height and style its syntax-help button as a green square with a hover state.
2026-10-19 13:35:26 -04:00
themes Style issue and PR filter search controls 2026-10-19 13:35:26 -04:00
.gitignore Nebula: orange-on-warm-slate theme for Forgejo 2026-10-19 15:24:18 +00:00
MARKDOWN_TEST.md Add MARKDOWN_TEST.md: kitchen-sink Markdown rendering test 2026-10-19 15:29:29 +00:00
README.md Add GitHub Dark theme and organize overlays 2026-10-19 13:24:53 -04:00

Custom Forgejo themes

Self-contained theme overlays for Forgejo. Each theme lives in its own folder under themes/ and uses only the officially documented interface customization extension points — no Forgejo source file is patched and no rebuild is required.

Theme Look JS Landing page
Nebula Orange-on-warm-slate, gradient accents, pills, glow focus, custom homepage nebula.js Custom hero
GitHub Dark GitHub Primer dark palette, flat surfaces, green primary buttons, coral tab underline none Custom dark hero

Layout

themes/
├── nebula/
│   ├── README.md
│   └── custom/                 # drop-in contents for $FORGEJO_CUSTOM
│       ├── conf/app.ini.example
│       ├── public/assets/{css,img,js}/
│       └── templates/
└── github-dark/
    ├── README.md
    └── custom/
        ├── conf/app.ini.example
        ├── public/assets/css/github-dark.css
        └── templates/
            ├── custom/header.tmpl
            └── home.tmpl

Each themes/<name>/custom/ directory mirrors Forgejo's custom path, so it can be copied over $FORGEJO_CUSTOM directly.

Install a theme

Your custom path is usually <forgejo-workpath>/custom (check forgejo help or Site Administration → Configuration). It can also be set with FORGEJO_CUSTOM or --custom-path.

# from the repo root — pick one theme
cp -rv themes/github-dark/custom/. /var/lib/forgejo/custom/

# fully restart Forgejo (config/template changes need a restart)
systemctl restart forgejo      # or: docker restart forgejo

Then merge the theme's conf/app.ini.example keys into $FORGEJO_CUSTOM/conf/app.ini and hard-refresh the browser (Ctrl+Shift+R).

Switch themes

A theme is a complete overlay, so install one at a time. Remove the previous theme's hooks and assets before copying the next one:

CUSTOM=/var/lib/forgejo/custom

rm -f  "$CUSTOM/templates/custom/header.tmpl" "$CUSTOM/templates/custom/footer.tmpl"
rm -f  "$CUSTOM/templates/home.tmpl"
rm -f  "$CUSTOM/public/assets/css/nebula.css" "$CUSTOM/public/assets/css/github-dark.css"
rm -f  "$CUSTOM/public/assets/js/nebula.js"
rm -f  "$CUSTOM/public/assets/img/logo.svg" "$CUSTOM/public/assets/img/favicon.svg" "$CUSTOM/public/assets/img/favicon.png"

cp -rv themes/nebula/custom/. "$CUSTOM"       # or themes/github-dark/custom/.
systemctl restart forgejo

Keep your own custom/conf/app.ini; only the theme's UI keys change.

Upgrading Forgejo

Template overrides are unsupported by Forgejo and can break without warning. Both themes keep almost all styling in CSS, which is resilient. If a templates/custom/*.tmpl hook fails after an upgrade, remove it and the instance falls back to stock Forgejo. Always test upgrades in staging and see the theme README for theme-specific notes.