4.1 KiB

Bootstrap, layout, and application state

Use this topic for providers, navigation layouts, page caching, the settings drawer, Pinia, or persistence issues.

Question Read first Follow through
Initial rendering, Wujie mounting, and global services Application bootstrap, App provider composition Application providers, shared UI service interfaces, development diagnostics
Sidebar, top navigation, tabs, and search Application layout adapter, application navigation hook Shared AdminShell, host layout components, slot contract
Content area, loading, navigation, and KeepAlive Host content slot, host transition adapter Shared transitions and cached rendering, cache allowlist, page request cancellation
Layout preferences, JSON import/export, and transient state Settings store, preference-file validation, runtime store Host settings drawer, shared layout settings, reader guide

The layout package owns the shell and rendering; the application supplies navigation, settings, content, and runtime state. Access application stores through hooks. See the store conventions for persistence scope and historical formats. Preference files contain layout settings only; route sources and route JSON belong to routing.

Targeted verification: pnpm harness verify layout, including layout regressions, providers, and related hooks. Select affected layout modes using the browser dimensions. Check narrow widths for sizing changes, and reload restoration/readback when cache or preference behavior changes.