|
All checks were successful
Deploy content to live site / deploy (push) Successful in 2s
Match the May 2026 ZDDC simplification — channel mirrors (_stable, _beta, _alpha) and partial-version pins (_v<X.Y>, _v<X>) are gone. Each tool has one canonical URL (<tool>.html, symlink → current stable) and a set of immutable per-version files. index.html: - Remove .channel-row CSS - Replace the per-tool 3-channel row with one card linking to the canonical <tool>.html; cards are now clickable - Drop "Each tool is published in three channels" paragraph; replace with "tracks current stable; pin on the releases page for reproducibility" - Update apps: example to use 'stable' or 'v0.0.4' (drop beta/alpha and partial-pin options) - Update header dropdown links + "Local: just download" links to canonical URLs - Drop "channel build" wording in the "All releases" footer link reference.html: - Update hardcoded header dropdown links + Section 11 tool cards from archive_stable.html / browse_stable.html to archive.html / browse.html Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| css | ||
| img | ||
| js | ||
| CLAUDE.md | ||
| federal.html | ||
| index.html | ||
| LICENSE | ||
| pubkey.pem | ||
| README.md | ||
| reference.html | ||
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 deployed to the live site by
its build pipeline. They live on the deploy host under
/srv/zddc/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/deploy-content.yml rsyncs the working tree into
/srv/zddc/ on the deploy host on every push to main. The rsync
uses --delete-after and excludes /releases/, /.git*,
/.forgejo*, /README.md, and /LICENSE — anything else added at
the repo root will be published.
Editing notes
js/layout.jsqueries 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>(seeindex.html); only shared rules go incss/style.css. Design tokens (--color-accent, spacing scale, etc.) live at the top ofcss/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.