Presentation across devices and themes
Toolora uses project-specific design tokens and shared components for office and portal presentation. Device width, user task and theme affect layout; they do not change business authorization. A responsive action must preserve the same reviewed state and mutation contract as its desktop counterpart.
The frontend styling reference owns valid tokens. The Storybook contract owns synthetic visual states and their interaction checks. This reference describes those rules without claiming universal accessibility or complete device coverage.
Presentation contract
Section titled “Presentation contract”| Concern | Inspected rule or mechanism | Boundary |
|---|---|---|
| Surfaces and text | Project tokens such as bg-bg, bg-surface, text-fg and muted variants |
Default shadcn token names are not interchangeable with this project’s tokens |
| Semantic outcomes | Project danger, positive and warning tokens | Meaning must also be communicated by status text and controls |
| Theme preferences | Scoped by office/portal and user identity | Portal defaults to light; office defaults to dark unless that scope has a stored choice |
| Office navigation | Shared configuration for sidebar/mobile drawer | A different layout does not grant another route or capability |
| Save status | Polite atomic live region with explicit state text | The status reflects the supplied persistence controller only |
| Narrow review flows | Dedicated mobile composition where the page selects it | A compact card must retain original, decision and conflict context |
| Preview content | Domain preview/PDF and explicit viewing controls | A rendered preview is not send, publication or acceptance |
ThemeScope selects office or portal presentation from route context, including public quote, customer, worker, UE and field routes. The saved preference uses an area/user key. The root theme provider’s runtime setting is not the complete per-surface preference policy.
Save and interaction states
Section titled “Save and interaction states”The real SaveStatus component has idle, queued, saving, saved, error and conflict presentations. Idle reserves space without text. Queued displays Osparade ändringar. Error and conflict expose the appropriate retry or merge action when the caller supplies it. These labels must stay aligned with editing behaviour.
The gallery imports production components and CSS with synthetic inputs. A retry callback in a story demonstrates the control and event; it does not persist a quote or contact the backend. Quote-public stories similarly use an explicit fixture transport to exercise states without contacting a live recipient or provider.
What the visual matrix establishes
Section titled “What the visual matrix establishes”The Storybook configuration runs Chromium instances for both themes at desktop 1280 × 800 and mobile 390 × 844. Story play functions check their declared text, live-region attributes, callbacks, keyboard interactions and selected quote/UE states. Theme and viewport assertions establish that the chosen variation actually ran.
This matrix is not a screenshot-diff suite, an aesthetic judgement or a comprehensive responsive-layout audit. A passing keyboard callback for one control is not an accessibility certification. Visual review must still inspect reading order, focus, labels, contrast, overflow and task continuity where the change affects them.
The handbook has its own local-only layout, print and browser checks. Those validate this documentation artifact and cannot be reported as Toolora application device acceptance. Test levels and evidence separates component, database and shared functional outcomes.
Example and review scope
Section titled “Example and review scope”A synthetic user edits a quote at narrow width in the light portal-related presentation. Showing the correct save label and reachable merge action is necessary; squeezing a conflicting draft into a card without its explanation is not a complete task result. The same revision must still be checked by the API.
The named sources establish token, theme and fixture contracts. Existing shared receipts remain evidence only for their recorded pages, widths, themes and commits. This source review makes no blanket claim about every page, browser, screen reader or print format.