Web information architecture: one target, one job
The website should explain the minimum value before showing compatibility breadth or future coordination.
Primary story
Hero: Arrive ready. Get to work. The first layer of understanding is an existing project, upstream preparation, separate source/environment delivery, and direct work in the chosen target. The default story keeps one example target from start to finish.
Navigation
How it works, Environment, Compatibility and Docs are primary. Get started is the main call to action. Next remains available as a lower-priority future chapter.
Main stage
Use one readable work surface rather than three miniature simultaneous panels. The five scenes are project, preparation, ready assets, delivery boundary and native task. The target scene must not show pip/npm/runtime installation on the strict path.
Small screens
Use complete vertical scenes instead of shrinking a desktop composition into unreadable micro-panels. Keep natural scrolling and allow internal scrolling only where long code or tables require it.