#292's last part: there was no design page among the wiki's 23, and
CONTRIBUTING described the mechanics -- components live here, Basecoat draws
them, icons come from Lucide -- without a word about what the result should
look like. So every judgement about the interface was somebody's taste on the
day, and the six ways of writing a page title are what that produced.
The page says what the tokens are and when to reach for each: the two scales
and the semantic names, the one radius everything is derived from, the three
planes, the type sizes, the two densities, and the empty state. It says what
is not negotiable, in the places where a design decision would otherwise cost
a criterion -- colour is never the only thing saying something, a
high-contrast theme throws backgrounds and shadows away, nothing moves unless
somebody's system allows it, compact may not shrink a target.
It also says where the skeleton went, since #292 asked for one: Postulo
renders on the server, so there is no moment with nothing in it to fill, and
what htmx replaces is the previous answer and still true while it does.
It points at the gallery rather than describing it. *Server settings ->
Design* shows every component in whichever theme you are reading it in, which
is a thing to look at rather than a thing to read about.
Refs postulo/postulo#292
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Document the whole API surface: every call, the machine endpoints, the plugin API
The API named every call, but the scope each needs lived in prose, and
the discard reasons and what /me answers were not written anywhere. It
gains both, and one list of all 39 calls with method, path and scope,
generated from the API's own routers.
/healthz, /metrics and /logs answer machines about the instance and
were only rows in Configuration. Health, metrics and logs says what
each returns, how it is switched on and guarded, the rate limit, the
parameters /logs takes, and every metric with its labels.
The plugin guide was postulo's docs/PLUGINS.md and never reached the
wiki. It is Writing a plugin now, opening with every kind of plugin,
its entry-point group and the interface it satisfies, and carrying a
reference of all 37 names postulo.plugins.api promises -- eight of
which the guide had never named. It also says plainly that a
notifier's Notification, and the client's DestinationRefused, are used
from outside the surface today.
The sidebar gains a Building on it group for the API and the plugin
guide, and the three pages that linked to docs/PLUGINS.md link here.
postulo's tests/test_wiki_surface.py now reads these three pages
against the code.
Refs postulo/postulo#170
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Take the pages over from postulo/wiki, which this repository now replaces
Until now this was a copy of postulo/wiki, refreshed by postulo's
scripts/publish-wiki.sh whenever somebody remembered to run it. The last
time was 5 September (postulo@9645ee1). This brings it to postulo@b6cfb8f7:
- the four pages that never arrived: Accessibility, Hardening, Listings
and Reports;
- the seventeen that had changed since;
- the images, which the script never copied because it copied *.md and
nothing else, so Home has shown its logo and its Buy me a coffee button
broken since the day they were added.
Nothing here was lost: every earlier commit is a publish, and the pages
they left matched postulo/wiki at 9645ee1 exactly.
From here pages are written in this repository and nowhere else.
Refs postulo/postulo#169
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
