VARASYS/ZDDC-website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
12 commits 1 branch 0 tags 439 KiB
HTML 67.8%
CSS 27.5%
JavaScript 4.7%
Find a file
ZDDC f81fb4e769 docs: canonical folder layout, role-based ACL, WORM, lazy creation 
Update reference.html § 9 (transmittal workflow): replace the legacy
per-party tree (project/{party-name}/{incoming,received,issued}) with
the current canonical layout — project root has working/, staging/,
reviewing/, archive/, and per-party folders sit under
archive/<party>/{mdl,incoming,received,issued}/. Note lazy creation,
case-fold matching, the per-user virtual <viewer-email>/ entry, mdl
opening the table editor, and the staging↔working drafting mirror.
Add a "Drafting a response transmittal" subsection describing how
inbound submittals (-SUB- @ IFR/IFA) flow through staging→working
into archive/<party>/issued/ as RS* responses.

Update index.html "Access control via .zddc files" bullet to describe
what the server actually does today: cascade direction, the five
verbs (r/w/c/d/a), explicit deny via empty grant, and the
X-Auth-Request-Email convention. Add new bullets for roles (with a
short YAML example), WORM archive folders + drop-in producer pattern,
lazy folder creation + case-fold matching, the cascade tracer
admin endpoint, and an expanded OPA paragraph (input shape, cache
TTL, fail-open flag, --print-rego=federal). Update the install card's
tool-folder list to use lowercase canonical names, mention browse,
and add mdl.table.html as the per-party MDL view.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 09:30:31 -05:00
.forgejo/workflows ci: drop /avatar.png exclude (file removed) 2026-05-02 21:44:26 -05:00
css fix: dark-mode contrast on blue pills, brand logo, stable channel chip 2026-05-02 21:27:20 -05:00
img Initial commit: hand-edited content from the prior orphan branch. 2026-05-02 08:53:11 -05:00
js Initial commit: hand-edited content from the prior orphan branch. 2026-05-02 08:53:11 -05:00
CLAUDE.md docs: add Publishing and Editing notes to README; stub CLAUDE.md 2026-05-02 21:27:10 -05:00
federal.html docs: federal compliance page (federal.html) + home-page cross-links 2026-05-04 21:33:16 -05:00
index.html docs: canonical folder layout, role-based ACL, WORM, lazy creation 2026-05-07 09:30:31 -05:00
LICENSE Initial commit: hand-edited content from the prior orphan branch. 2026-05-02 08:53:11 -05:00
pubkey.pem docs: publish Ed25519 pubkey for apps signing 2026-05-04 21:59:20 -05:00
README.md docs: add Publishing and Editing notes to README; stub CLAUDE.md 2026-05-02 21:27:10 -05:00
reference.html docs: canonical folder layout, role-based ACL, WORM, lazy creation 2026-05-07 09:30:31 -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, transmittal, classifier, mdedit, 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.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.