new-gpui-view

To add a new GPUI page, you need to create the view file, register it in the module exports, add a Page enum variant, and update the render dispatch and sidebar navigation. This ensures the new page integrates with the established routing and UI patterns.

Scaffolding a GPUI view involves creating a Rust file under the views directory, updating mod.rs for module exports, extending state.rs with a new Page variant, and wiring the rendering logic. This matches the structure used for existing dashboard and settings pages.

To integrate a sidebar entry for a GPUI page, you add the navigation item within the render_sidebar function using the page title and enum variant. This connects the new view to the sidebar navigation so it appears in the UI.

Yes, scaffolding a GPUI view requires updating the application state enum. You must extend state.rs with a new Page variant and add a corresponding match arm in the render_content function to dispatch the view correctly.

The best way to match existing UI patterns is to follow the established page structure by creating the view component, wiring it through module exports and state enums, and adding the sidebar entry. This guarantees consistency with other pages like logs and profiles.