The DreamWeave Mod Template turns a repository into three things at once: a mod page people can read, archives people can install, and a set of static files that tools can read without scraping either. You write two files per mod. Everything else is generated, checked, and published by the workflow.
One repository, three audiences
What you write, what the tooling checks and generates, and who reads the result.
-
source
You write
content/<mod>/index.md for people, content/<mod>/mod.toml for facts, and the mod's files beside them.
-
tool
CI checks and packages
Validates every push, packages byte-reproducible archives with offline docs, records each tagged release in mod.lock, writes the manifests.
-
result
Zola renders
The mod page, its docs, its changelog and the network page, from the same mod.toml and mod.lock. zola serve shows it locally.
Players
Read the page, download the archive, follow the install section.
Clients and indexes
CHIMERA, St4sh and anything else read dreamweave.json and the manifests. No HTML scraping.
Mirrors
Serve the same bytes under the same SHA-256. They never become the authority.
How the pieces relate
- You write CI checks and packages
- CI checks and packages Zola renders
- Zola renders Players
- Zola renders Clients and indexes
- Clients and indexes verify by hash Mirrors
If this is your first mod on the template, read Start here and stop when your page is up. Come back for Releases when you have something to release. The protocol pages are for people writing tools that read what the template publishes; you do not need them to publish a mod.