How to get an account and sign in — Discord/Authentik, the EVC relay, and the PSN apps. Start here.
- Dockerfile 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
Some checks failed
image / build (push) Has been cancelled
The README was 19 words - a title - and there was nothing anywhere explaining how to
change this repo. Everything learned building it lived in one session's head.
README.md what the site is, where it is served, the two commands to preview
it, and a pointer to the rest.
CONTRIBUTING.md the layout, how to add a page (including the two things the build
will not fail on but will be wrong: the nav entry and the frontmatter
icon), how to add an image (crop, shrink, and never ship somebody
else's data - cropped out of frame rather than blurred), when to use
tabs, the conventions, the release loop, and the pre-merge checks.
Also fixed a real bug found while writing it: the workflow's paths filter watched
mkdocs.yml, a file this site has never had. It builds Zensical from zensical.toml, so a
change to the nav order or the extension list - the two edits most likely to matter -
would not have triggered CI at all. Silent, and exactly the shape of failure the
documentation is meant to prevent.
Conventions are recorded with their reasons rather than as rules: why there are no
third-party requests (Mermaid is 953 KB gzipped from unpkg), why --strict matters when
renaming a page, and why a page must not claim more than its source supports.
|
||
| .forgejo/workflows | ||
| docs | ||
| .gitignore | ||
| Containerfile | ||
| Containerfile.nginx.conf | ||
| CONTRIBUTING.md | ||
| README.md | ||
| zensical.toml | ||
Getting started
The PSN onboarding site — https://start.psn.virtualcalz.one.
It answers one question for somebody new: I have an account, so now what? Create the account, get the team vault syncing in Obsidian, and reach the PSN apps.
The Markdown in docs/ is the source of truth. The image contains only the build output, so
the published site cannot drift from this repository.
Preview it
podman build -t getting-started:local .
podman run --rm -p 8080:8080 getting-started:local
Then open http://localhost:8080.
Working on it
CONTRIBUTING.md has the edit → preview → release loop, the conventions this site holds to, and the checks worth running before you merge.