ZDDC
38c8b0cfa1
All checks were successful
Deploy content to live site / deploy (push) Successful in 2s
Catches the website up to the v0.0.21 server contract:
- Project structure (reference.html §9): archive/ is the only
physical project-root directory; the in-flight lifecycle
(working/staging/reviewing) now lives PER-PARTY under
archive/<party>/. Six top-level URLs (ssr/mdl/rsk/working/
staging/reviewing) are virtual aggregators synthesised from
each party's content.
- Retired the staging↔working mirror language — drafting a
response transmittal now walks the in-flight ratchet through
Plan Review's scaffold at archive/<party>/reviewing/<tracking>/.
- Role descriptions (§10): document_controller is no longer
subtree-admin anywhere. Authority cascades from the auto-own
.zddc written at each archive/<party>/ folder, which grants
both the creator email AND the document_controller role
`rwcda` (via auto_own_roles in the defaults). Multi-DC
deployments work without admin status because the role itself
is named in every party's auto-own grant.
- Added the `observer` role (third standard role) with a
pure-read-only intent for external auditors.
- Documented the in-flight ratchet (working → staging → issued)
as a one-way handoff that downgrades the prior role's modify
rights at each step.
- Clarified that the `a` verb is the .zddc-edit verb, distinct
from the elevation-bypass sudo channel (root admins: list).
- Dropped `on_plan_review:` from the cascade-keys reference (the
key was retired when Plan Review hardcoded the scaffold
convention); added `auto_own_roles:` and `auto_own_fenced:`.
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.