There was an error while loading. Please reload this page.
📝 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: 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: pt-BR — DesignSystem, Security, Performance, Mermaid, Markdown
docs: today's work ships in 0.2.0-preview.26 — the marks say so
docs: mermaid drawn by the design system — pinned-parity layout, graceful fallback
docs: the Markdown mark names a symbol unique to the release it claims
docs: Markdown renders as the design system — one parser on every side