varasys/zddc-website
Watch
4
0
Fork
You've already forked zddc-website
 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
35 commits 1 branch 0 tags 3.1 MiB
  • HTML 80.7%
  • JavaScript 14.8%
  • CSS 4.5%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
casey 820f972ea6
All checks were successful
image / build (push) Successful in 36s
Details
Merge pull request 'chore: drop the umami beacon (the lab retires umami; visits are counted server-side)' (#2) from ctrl-agent/zddc-website:chore/drop-umami-beacon into main 
Reviewed-on: #2
2026-10-22 15:07:32 +00:00
.forgejo/workflows ci: publish the site as the sites/zddc OCI content image, retire the sftp deploy 2026-10-15 17:13:59 -05:00
css landing: current-versions table; beta strip on the custody spec pages 2026-09-22 21:11:30 -05:00
img ZDDC website: archive, browse, and classify tools + reference 2026-06-11 12:53:40 -05:00
js ZDDC website: archive, browse, and classify tools + reference 2026-06-11 12:53:40 -05:00
next spec: Core is §2-§8; workflow and implementer material get their own pages 2026-09-22 10:12:27 -05:00
spec chore: drop the umami beacon (the lab retires umami; visits are counted server-side) 2026-10-22 04:25:44 -05:00
.gitignore ZDDC website: archive, browse, and classify tools + reference 2026-06-11 12:53:40 -05:00
CLAUDE.md ci: publish the site as the sites/zddc OCI content image, retire the sftp deploy 2026-10-15 17:13:59 -05:00
index.html chore: drop the umami beacon (the lab retires umami; visits are counted server-side) 2026-10-22 04:25:44 -05:00
LICENSE ZDDC website: archive, browse, and classify tools + reference 2026-06-11 12:53:40 -05:00
pubkey.pem pubkey: rotate the release signing key (old key COMPROMISED 2026-09-29) 2026-09-29 10:01:54 -05:00
README.md ci: publish the site as the sites/zddc OCI content image, retire the sftp deploy 2026-10-15 17:13:59 -05:00
reference.html chore: drop the umami beacon (the lab retires umami; visits are counted server-side) 2026-10-22 04:25:44 -05:00
workflow.html chore: drop the umami beacon (the lab retires umami; visits are counted server-side) 2026-10-22 04:25:44 -05:00

README.md

ZDDC website

Hand-edited content for zddc.varasys.io. Two files:

  • index.html — landing page + install snippets.
  • reference.html — the ZDDC file-naming convention specification.

Plus css/, js/, img/ for shared styles and assets.

This repo intentionally does not contain release artifacts. The ZDDC tools (archive, browse, landing) and the zddc-server binary are built from the source repo at https://codeberg.org/VARASYS/ZDDC and published by its release pipeline as a separate image (sites/zddc-releases) that the origin serves as /releases/ — never in this repo's git history.

Preview locally

git clone https://codeberg.org/VARASYS/ZDDC-website
cd ZDDC-website
python3 -m http.server 8000
# open http://localhost:8000/

The preview won't have a /releases/ directory unless you also have the source repo and run its build pipeline. That's expected — the two repos are intentionally decoupled.

Publishing

.forgejo/workflows/image.yml runs on every push to main (and on manual dispatch). It stages a copy of the repo, drops /.git*, /.forgejo*, /ci, /README.md, /LICENSE, and /releases/, refuses to continue if index.html is missing, and builds the rest into a FROM-scratch OCI content image — so anything else added at the repo root will be published. The image is pushed to the registry as sites/zddc:<date>-<short-sha> and :latest, then the origin host is told to pull it (refresh-site zddc, over a key the origin pins to that one command) and serves it at /var/www/zddc/. While the DEPLOY_ORIGIN/DEPLOY_COMMAND variables are unset the refresh is skipped with a log line and the origin keeps serving its previous copy. /releases/ is a separate image owned by the ZDDC source repo's pipeline, mounted beside this one.

Configuration lives in repository/org variables and secrets, not in the workflow: variables REGISTRY, IMAGE_REPO, SITE_NAME, REGISTRY_USER, DEPLOY_ORIGIN, DEPLOY_COMMAND; secrets REGISTRY_TOKEN, STATIC_DEPLOY_KEY.

Editing notes

  • js/layout.js queries the header for .header-nav, .dropdown, .dropdown-toggle, .dropdown-menu, and .theme-toggle. Both HTML pages need to keep those classes or the theme toggle and Tools dropdown silently break.
  • Page-specific CSS goes in an inline <style> in <head> (see index.html); only shared rules go in css/style.css. Design tokens (--color-accent, spacing scale, etc.) live at the top of css/style.css — prefer those over hardcoded values.

Contributing

Issues + PRs welcome. For changes to the tool source code (not the website), file them at https://codeberg.org/VARASYS/ZDDC.

License

AGPL-3.0.