Desktop Application and Preferences Wireframe
A three-page desktop workspace with a project explorer, document editor, and preferences.
Introduction
STUDIO brings together a dark project rail, a spacious file list, and a focused document editor. Open a project, follow the Preferences link, and return to the editor. Every screen is a separate named page in the same YAML document.
Separate navigation, content and settings
STUDIO is a starting point for an editor, document manager or internal desktop utility. The explorer establishes project context; the document screen focuses on the current file; preferences isolates configuration from the main task. Review whether navigation stays predictable when someone moves between them.
These are browser-rendered prototype pages, not an installed desktop package or a file-system integration. Project names and document contents are illustrative.
Inspect nested row and column frames
The preferences hierarchy demonstrates horizontal label/control relationships inside vertical sections. Inspect the frame padding, gaps and child IDs before adding a setting. A meaningful layout relationship is easier to review than a collection of unrelated coordinates.
Try adding one optional preference while preserving existing IDs and navigation. Validate the draft and check the section still fits its page. Read the layout element reference for the distinction between frames, groups and visual surfaces.
Plan document and settings states
Extend the prototype with an empty project, missing file, unsaved changes prompt, save failure and reset-preferences confirmation. State which actions need a real file service or persistence layer. Keyboard shortcuts, focus behavior, platform menus and accessibility must be implemented and tested in the final application.
For a multi-step settings journey, compare onboarding. Keep an .rvv revision and share PNG/SVG when reviewing layout alternatives.