Luminaux — Help Center
The end-user guide to Luminaux.
Looking for the code-level reference (props, file paths, architecture)? See the developer documentation. Evaluating the template before buying? See the marketing overview.
Info
📸 Screenshots are intentionally omitted in this revision and will be added once the product UI is finalized. Each article is written so images can be slotted in later without restructuring.
How this Help Center is organized
Articles mirror the app's own sidebar sections, so if you can find a screen in the menu you can find its help here. Every screen is documented with the same four-part block:
- What it is — the purpose of the screen in one or two sentences.
- Where to find it — the sidebar path and the URL route.
- How to use it — the real interactions, step by step.
- Tips — shortcuts, gotchas, and things that are easy to miss.
The five things worth learning first
- Global search — press
⌘K(orCtrl+K) anywhere to jump to any page, or use the Recent list. - Switch theme & colour from the header — the sun/moon icon toggles Light/Dark/System, and the palette icon opens the skin switcher (13 looks). See Appearance & layouts.
- Reshape the whole app from the header gear (the Customizer) — sidebar style, fixed header, footer, widgets, and more, all previewed live.
- Everything you change is remembered in your browser, per person. Reset to defaults (in the Customizer or Layout Settings) restores the factory look without signing you out.
- Press
?anywhere (outside a text field) to open the keyboard-shortcuts cheat sheet.
Who should read what
- Everyday users of a deployed Luminaux dashboard → start with Getting around, then read the article for the area you work in.
- Administrators configuring the workspace → Settings and Appearance & layouts.
- Developers & designers → the developer docs instead — they cover the code, tokens, and how to change copy.
Info
Note on data: Luminaux ships as a demonstration template. App data (chat messages, calendar events, board tasks, applicants, invoices) is saved in your browser, not on a server, unless your team has wired the app to a live API. Clearing your browser storage or using Reset to defaults restores the seeded sample data.
Was this page helpful?
