There was an error while loading. Please reload this page.
📝 docs: Track W — Photon on the desktop The desktop gaps verified in code (paths, frame clock, hit-testing, shell surface, signing, multi-window), what the sweep found that shrinks the work, the six workstreams and their sequencing. Born from a real Electron-app migration plan; every piece generic. EN and pt-BR together.
📝 docs: Track M — email rendering Author an email in C# with the same components a page is written with, and get HTML an email client will actually render. Email is a THIRD REALIZER beside web and Photon — a target whose engine is merely very restrictive, which is architecturally the same shape as a target with no DOM. Nothing in the authoring layer changes. Two pieces already exist and the page says so, because a plan that ignores them would overstate the work: WebRealizer.Lower with no style sink keeps styles INLINE rather than atomising them into classes, and HtmlRenderer.RenderNode turns the lowered tree into a string. What is missing is the medium — nested tables for Outlook's Word engine, literal colors, absolute image URLs, the 600px shell, and a fence over everything email cannot do. M0 MEASURES before M1 builds: render an existing component through those two calls and open it in real clients. Half a day, no new code, and it decides the size of the rest. Written that way on purpose after a day in which every confident conclusion drawn from a harness rather than a real run turned out wrong. Page, both sidebars and both roadmaps, EN and pt-BR together.
📝 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 rail, and a track for the form factors Components gains NavigationRail beside BottomNavigation, stated as what it is: the same destinations for two window widths, one NavItem list inside an AdaptiveNode, with the 3-5 / 3-7 counts and the Drawer past them. Both roadmaps gain Track F: tablet is shipped, ahead are the template shells, Wear OS and Android TV, and Car/AAOS is out of scope with the reason written down. Both languages, and without em-dashes, following the sweep already in the working tree.
docs: the phones read the screen too, in both languages The Photon accessibility section gains the iOS and Android bridges beside the macOS one: the container of UIAccessibility elements and the virtual AccessibilityNodeInfo hierarchy, what each platform calls a role, where a check's state lives on each, the two fences (no third check state on either phone, no link class on Android), and the proof each shell gives by asking the PLATFORM rather than the tree. The roadmap item that named the two bridges is gone from both roadmaps. The pages these touch also carry the working tree's em-dash sweep for those files.
docs: the interaction contract catches up with the a11y pass — both languages
📝 docs: forms leave the roadmap's ahead list — both languages
📝 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: DeclarativeSurface, Styling, Lottie, Charts and Roadmap speak pt-BR