📝 docs: the server events page reads in Spanish, French and German
✨ feat: the wiki reads in five languages
Spanish, French and German join English and Portuguese: 25 of the 39 pages
translated, each language with its own `_Sidebar.md` under `locale/<culture>/`,
which is the file GitHub resolves beside a page and the site reads as that
language's navigation.
The language switch on every page lists only the languages whose file EXISTS,
so a page with no Spanish yet offers the four that are there and never a dead
link. It is generated rather than written, so each tranche of translations
lights its own entries and nothing has to be remembered.
Version marks carry over verbatim: the `eq:since` comment is byte-identical
across languages and only the italic word changes (Since / Desde / Depuis /
Seit). Production reads the comment and never the word, so the runtime is
language-agnostic; the one place that knew the words was the site's own guard.
Still to translate, the fourteen longest: BuildFlow, Capabilities, CodeEditor,
Compiler, Debug, DesignSystem, Diagnostics, Icons, Photon, ServerEvents,
ServerIntegration, SupportedFeatures, Upgrading, VisualEditor.
Also drops 150 em-dashes from the English pages and 134 from the Portuguese
ones, on the pages this commit touches.
📝 docs: two rules for one topic both rule, so the app tightens a library's topic (EN + pt-BR)
📝 docs: server events evaluate a topic's policies with their schemes, take a template's defaults, and release a bind left unanswered (EN + pt-BR)
📝 docs: server events hear a connection's transitions in order, and ask a release again (EN + pt-BR)
📝 docs: server events take JSON binds, ask a bind again, check their limits at startup, and EQ2013 (EN + pt-BR)
📝 docs: server events, a component hearing the server on a typed topic
A ServerEvents page in both languages (#291): the typed topic, the
IServerEvents capability and its connection, publishing, who may hear a
topic (route templates, policies with the topic as resource, a delegate,
closed by default), the lifecycle handlers, the backplane and the session
affinity several instances need, the limits bound from
EQuantic:ServerEvents, and what goes over the wire. Capabilities lists
IServerEvents, ServerIntegration documents UseServerEvents and no longer
promises SignalR services, Architecture points there from Server Actions,
and the Roadmap keeps the slices still ahead.