There was an error while loading. Please reload this page.
📝 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: analytics as a capability, GTM as its installer — both languages