# Admin interface conventions [Project overview](../README.md) · [Development](development.md) The admin UI uses one Alpine application and shared layout primitives for every section. Add features to this model rather than introducing a separate mobile page or section-specific navigation. ## Ownership - `templates/admin/navigation.html`: the single navigation tree, grouped into Operations (reviews/tasks), Music (library/tools/statistics), and Instance (users/settings). Existing hash routes remain the source of navigation state. - `templates/admin/styles.html`: colors, typography and component appearance. - `templates/admin/responsive.html`: shared layout, breakpoints, touch targets, scroll regions, table cards and dialog sizing. Put responsive rules here. - `templates/admin/ui.html`: viewport state, task tabs, settings navigation and the shared overlay lifecycle. Business data and API actions remain in `adminV2()` in `v2.html`. ## Layout | Width | Navigation | Workspaces | Lists and dialogs | | --- | --- | --- | --- | | 1280 px and above | Persistent sidebar | Task list/detail/log side by side | Tables, centered bounded dialogs | | 1024–1279 px | Persistent sidebar | Task tabs; settings in one column | Tables, bounded dialogs | | 768–1023 px | Drawer | Task tabs; settings section picker | Tables in contained scroll areas | | Below 768 px | Drawer | Single column | Table cards, full viewport dialogs | Keep CSS and `matchMedia` breakpoints in `ui.html` synchronized. The main panel owns page scrolling. Use `minmax(0, 1fr)` and `min-width:0` for grid/flex children; never restore a global minimum page width. The top bar stays available while content scrolls. Navigation closes after route changes and when switching to the desktop layout. It retains the active section and the existing URL routes. Use `.panel`, `.panel-head`, `.panel-title`, `.toolbar`, `.action-strip`, `.field` and `.editor-grid` for new content. Toolbars wrap, inputs fill available space, and mobile controls use 44 px touch targets and 16 px input text. Long identifiers, paths and names must wrap. Avoid fixed column widths and inline grid definitions. For tabular lists, add `.responsive-table`, a `data-label` to every cell, and `data-primary` to its identifying cell. Mobile CSS presents the same DOM as cards; do not duplicate rows or hide actions. Give clickable row titles real buttons using `.row-link`, so the operation also works with a keyboard. Dense comparisons, charts and logs may scroll inside a named, keyboard-focusable region; horizontal scrolling must never propagate to the page. Keep these exceptions intentional. Task tabs change presentation only: configuration and selected run stay in memory when switching tabs or rotating the device. In settings, add a section ID and a matching entry to the section picker. Put related controls in `.settings-grid`. ## Dialogs Every dialog uses the same hierarchy and lifecycle: ```html