forgejo-home

Minimal custom homepage content for forge.dikka.dev.

This repo generates and owns the Forgejo custom-template override:

content/home.json              # editable homepage content
scripts/build-home.py          # generator
custom/templates/home.tmpl     # generated Forgejo template to deploy

The override keeps Forgejo's normal base/head and base/footer templates, but replaces the whole homepage body between the top navigation and footer.

Current design is intentionally plain: a white page with black default-font text, one sentence, and a short list of links. It is meant to be boring and easy to replace later.

Local preview

Run a local Forgejo-like preview with live reload:

python3 scripts/dev-preview.py

Then open:

http://127.0.0.1:8787/

The preview renders the homepage inside a small static shell that mimics Forgejo's top nav and footer. The fake top bar also has an Inspiration link for the earlier reference board.

It reloads the browser when custom/templates/home.tmpl, content/home.json, or scripts/build-home.py changes. If the JSON or generator changes, the preview regenerates custom/templates/home.tmpl automatically.

Editing content

Most homepage copy/cards live in:

content/home.json

After changing it, regenerate the Forgejo template with:

python3 scripts/build-home.py

Check whether the generated template is current:

python3 scripts/build-home.py --check

Remote

Hosted on the user's Forgejo instance:

https://forge.dikka.dev/clank/forgejo-home

Deployment target

The file should be placed under Forgejo's custom path in the running container so the effective path is:

$FORGEJO_CUSTOM/templates/home.tmpl

Coolify currently runs the Forgejo app as resource forge (r1ia3d31bej2aemjhrp6uenw) with a persistent /data volume and existing file storages mounted under /data/gitea/..., so the practical path for this override is:

/data/gitea/templates/home.tmpl

Recommended deployment path: add/update a Coolify file storage mounted at that path with the contents of custom/templates/home.tmpl, then restart/redeploy the Forgejo application so the template override is loaded.