There was an error while loading. Please reload this page.
📝 docs: which languages the SDK ships, and how an app ships fewer The question that prompted it: should the SDK's resx move to a package per language, the way Humanizer does it? No — and the page now says why where a reader will look for it. One package carrying its languages is what Roslyn and the test platform do, and .NET already owns the "I only want English" decision through SatelliteResourceLanguages, so a package matrix would buy nothing that a one-line property does not. Measured rather than asserted, and the caveat is measured too: on a consumer of the published package the property drops es/ and pt-BR/ entirely, and on a PROJECT reference — this repository's own samples — it drops nothing, because it filters what arrives through a package. The English page also still promised the resx seam as future work. It landed: every SdkStrings property reads SdkResources, and eqc rewrites the accessor into the culture catalog on the web. The pt-BR twin had already been corrected, which is the direction that rot usually runs in reverse.
📝 docs: UseCultureRoutes shipped in preview.36, not .35 The mark named the version that was current while the page was being written, but v0.2.0-preview.35 had already been cut — the feature commit (c39ea5d1) landed after the tag, so it went out in .36. Invisible until .36 existed: with no later tag the guard reads "not shipped yet" and stays quiet, which is the right answer for a promise. Cutting the release made the truth resolvable and the guard failed the build on it, which is exactly its job.
📝 docs: the language rides the URL — UseCultureRoutes, in English and pt-BR
📝 docs: hreflang, and a mark that named the wrong release ServerIntegration gains the hreflang section (the policy, the two ready-made URL shapes, the three rules enforced for the app, and the DI caveat that cost an afternoon), Localization points at it from where someone would look, and the SeoBuilder table lists Alternate/AlternateDefault. Icons said gradients shipped in preview.30. The tag points at b57575f and the gradient commit came after it, so both languages now say preview.31.
📝 docs: the audit's findings — a false fence, two missing sections, one spelling A pass over the whole wiki, mechanical rather than read: every version mark checked against the tag that actually contains the commit introducing its symbol, every canonical page checked for a twin, every backticked identifier checked against the source. - Icons said gradients were DROPPED from the `.svg` subset. They are understood since preview.30, in both units, with `href` for a shared palette, and each target paints the run the way it natively can. The paragraph said the opposite in both languages, which is the exact shape of rot this wiki is prone to: the code moved and the page stayed confident. - The pt-BR Home lost its Development Guide section and the pt-BR Localization page never got "Photon windows adopt the machine's locale at launch" — the only mark missing from a twin. - Eight marks in five pt-BR pages said *Since* where the page teaching the convention says *Desde*. The site accepts both; a reader on GitHub sees the prose. Clean in the audit: 147 marks, none naming the wrong release; 36 canonical pages, none without a twin and no orphan twins; no backticked identifier naming an API the source does not have.
📝 docs: the visual editor page catches up with the editor The page was written when there was a preview and an identity mechanism and nothing else, and it has been saying "no editing from the canvas" through four slices that added exactly that. Nothing compiles a wiki, so a stale page stays green forever and the site publishes it. Now documented, EN and pt-BR: the three tiers a selected node is classified into and why they exist (a row built five hundred times in a foreach has one source site and no separate existence, so "delete this row" is wrong for it); the inspector, its three honesty rules — compiled before offered, WorkspaceEdit rather than a file write, never rewriting the form the file is written in — and the one level it descends so that padding and background are reachable at all; and the three structural gestures with the fence they live inside. The distinction the whole design turns on is now stated rather than implied: UNDERSTANDING is not fenced, only WRITING is. The editor opens code that already exists, and real code splits itself across helper methods and files. Both Roadmap pages carried a premise the work disproved on day one — that click-to-select would ride the V3 source maps eqc already emits. It cannot: the whole Build body is emitted through one call, so the finest position a map can name is the start of the method. The repo's ROADMAP said so; the wiki went on telling readers the opposite.
docs: the interaction contract catches up with the a11y pass — both languages
📝 docs: the Localization page gains its window half — both languages M3 closed: two cultures in one Photon window, from the same component classes. The page now carries the three joints a window has and a request does not, the D13 pair visible in one frame, and the null-controller bug the sample exposed.
📝 docs: 0.2.0-preview.28 lands on the pages that promised it — in both languages Mermaid's edges curve (the orthogonal fence closes and names its release), Markdown's italic fence closes the way it said it would, Photon documents run-by-run text and the decided-height rule, the Roadmap drops the inline-link item it no longer owes, Icons and DesignSystem carry the Vector aspect and the slant axis, and Localization gains the born-localized template. Every canonical edit ships with its pt-BR twin in this same commit — the staleness guard is the law, and this is the discipline it enforces.
docs: a tradução pt-BR ganha o parágrafo de satélites sob AOT
docs: pt-BR pilot — locale/ tree with its own sidebar (the ArchiSteamFarm layout)