Design system
The one set of colours, sizes, corners and building blocks that every LeorWiki page, menu and tool uses, so the whole wiki looks and works the same.
- Everyone who adds or changes a CSS snippet, a menu, a page type or an HTML tool in LeorWiki, Claude included
- All CSS snippets in .obsidian/snippets, the website head (🗂️ All files/Site/translate-head.html), Ask LeorWiki and the Service Explorer
1. Where the design system lives
| What | Holds | Rule |
|---|---|---|
| leor-tokens.css | Every colour, size, corner, line and shadow, for light, dark and print | The single source. Change a value here, never in another snippet. |
| Other snippets | The look of one component (home-menu, leor-submenu, sops-menu, task-list ...) | Use only var(--lw-...) values. No hex colours, except black and white inside print rules and inside drawn icons. |
| This note | The rules and the list of tokens and components | Update it in the same step as leor-tokens.css. |
| Update tokens.bat | Copies the tokens into Ask LeorWiki and the Service Explorer | Run it after every change to leor-tokens.css. |
| Backups | _backups/2026-10-25 design system (outside the vault) | The state before the design system. Never inside the vault, so it is not exported. |
When a rule changes: update leor-tokens.css, then this note, then run Update tokens.bat, then check Home, one SOP and one menu in light and dark.
2. Rule zero: markdown first
The strength of LeorWiki is that every page is a markdown note that anyone can read and edit in Obsidian, by hand or with Claude. The design system never takes that away. The look comes from CSS; the content stays plain markdown.
The more often a piece of content changes, the plainer its markdown must be:
| Tier | Content | Changes | Allowed in the note |
|---|---|---|---|
| 1. Documents | SOP procedures, task lists, agendas, standards, PCIs, skill notes, checklists | Weekly | Headings, tables, lists, bold, italics, links and the standard callouts. The look comes from one cssclass (sop, tasks, skill, checklist, rguide). |
| 2. Menus | Submenus, SOPs menu, Items, Meetings, Documents | When pages are added | One callout with one list line per item. Add a page = add a line. Draft state follows the note's Status. |
| 3. Screen pages | Home, Org Chart, Client Visit Journey, Skills Map, Training Passports | Rarely | Nested callouts. Options as words after the callout name, for example [!home-tile|sparkles c-treatments]. Generated pages stay generated by their script. |
| 4. Tools | Ask LeorWiki, Service Explorer | When the tool changes | HTML. The token block is copied in by Update tokens.bat, never typed. |
Never in a note:
- HTML tags. The only exception is
<br>for a line break inside a table cell. - Colours, sizes or styles typed into the note.
- A new callout name without a snippet that styles it and a line in this note.
Links in lists (tablet use: every link must be easy to tap):
- One link per bullet. When several links belong together, write a label bullet and put each link on its own bullet under it, never as a comma list ("Radiance Facial, Hydrafacial, Leor Lite Facial").
- Two links inside one short sentence are fine ("Sponges or disposable face napkins").
- Menus (SOPs menu, submenus, Meetings, Items) are exempt: their snippet turns each link into its own button or row.
3. Tokens
All tokens start with --lw- and live in leor-tokens.css. Values are light | dark.
No red
Never use red or pink-red anywhere in LeorWiki: menus, tiles, buttons, icons, alerts, tools, the website, exported Excel files. Red looks alarming in a clinic and clashes with the Leor look (decision 29 Oct 2026).
- Warnings use amber (--lw-warn), the strongest alerts (stop rule, High priority, errors) use charcoal (--lw-risk) with an icon such as the octagon.
- Before adding a colour: its hue must not be between 330 and 20 degrees (red, rose, pink-red).
- Status emoji in notes stay as they are (🟢 Live, 🟠 Review, 🟡 Draft); never add 🔴 to a menu; roles are role tags, not emoji squares.
Neutrals
These follow Obsidian's own greys, so the wiki keeps matching Obsidian.
| Token | Light | dark | Use |
|---|---|---|
| --lw-bg | #ffffff | #1c1c1c | Page |
| --lw-card | #f6f6f6 | #282828 | Tiles, grouped lists, cards |
| --lw-line | #e4e4e4 | #333333 | Borders and dividers |
| --lw-hover | 6.7% black | 6.7% white | Hover, empty icon squares |
| --lw-ink | #222222 | #dadada | Text |
| --lw-muted | #5c5c5c | #b3b3b3 | Descriptions, section labels |
| --lw-faint | #767676 | #8a8a8a | Soon, chevrons, counts (readable: 4.5 to 1) |
| --lw-connector | #9a9a9a | #6f6f6f | Lines in diagrams (Org Chart, Skills Map, journey, trees) |
| --lw-connector-strong | #7a7a7a | #9a9a9a | Darker neutral marks (circle rings, the direct route) |
Accent and status
| Token | Light | dark | Use |
|---|---|---|
| --lw-accent | #2f7fb5 | #5a9fd0 | Leor blue: icons, fills, links, switches. Obsidian's own accent is set to the same blue. |
| --lw-accent-text | #2c76a9 | #7db4dc | Small blue text on grey (tags, small buttons) |
| --lw-accent-fixed | #2f7fb5 in both | Blue that must not change with the theme (blue bars with white text, numbers drawn on pictures) |
| --lw-ok | #2e8a55 | #6cc191 | Live, Standards box, good, Low priority |
| --lw-warn | #b86e00 | #f0a83a | Critical box, watch, Medium priority |
| --lw-risk | #3d4045 | #d6d9de | Stop rule, never, High priority, errors. Charcoal, not red (see No red) |
| --lw-review | #be7a08 | #f59e0b | Orange Review dot on SOP / PCI buttons |
Note Status stays as emoji in the notes (🟡 Draft, 🟠 Review, 🟢 Live). These tokens only colour what the CSS draws.
The standard callouts use the shared colours: Definition (info) is Leor blue, Critical (warning) is --lw-warn, Standards (success) is --lw-ok. Applicable to (abstract) keeps Obsidian's colour.
Section colours
Used on Home, the Skills Map, the Org Chart and task lists. Each section has the colour of the role that owns it.
| Section | Token | Light | dark | Role |
|---|---|---|---|
| Treatments | --lw-sec-treatments | #4f80bf | #8fb2e0 blue | Skin Practitioner |
| Medical | --lw-sec-medical | #a68329 | #dcbc62 yellow | Doctor |
| Operations | --lw-sec-operations | #679558 | #9cc48e green | Receptionist |
| Sales | --lw-sec-sales | #8761a8 | #b99ad6 purple | Relationship Manager |
| Management | --lw-sec-management | #5b6b8c | #93a3c6 dark slate | Center Manager |
| Customer | --lw-sec-customer | #778ca1 | #9fb3c6 grey-blue | |
| Software | --lw-sec-software | #4f8a8b | #8cc3c4 teal | |
| HR | --lw-sec-hr | #6f7f3a | #b9c47c olive | |
| Training | --lw-sec-training | #c0703f | #e3a37c orange | |
| Other | --lw-sec-other | #828994 | #9aa1ab grey | |
| Brand | --lw-sec-brand | #6b4d44 | #c9ad9f LEOR brown |
On Home and in task lists, a tile or section gets its colour from a word: c-treatments, c-operations, c-sales, c-medical, c-management, c-customer, c-software, c-hr, c-training, c-other, c-brand.
Treatment group colours
Only inside Treatments screens (SOPs menu, Service Explorer, PCIs), never on a screen together with section colours.
| Group | Token | Light | dark | Icon |
|---|---|---|---|
| Consultation | --lw-grp-cons | #a68329 | #dcbc62 | stethoscope |
| Medi-facial | --lw-grp-medi | #5b67b8 | #9aa3e0 indigo | face with glow |
| Skin | --lw-grp-skin | #4f8a8b | #8cc3c4 | layers |
| Hair | --lw-grp-hair | #8761a8 | #b99ad6 | crown |
| Body | --lw-grp-body | #c0703f | #e3a37c | figure |
| Slimming | --lw-grp-slim | #679558 | #9cc48e | diagonal ruler |
| LHR | --lw-grp-lhr | #2f7fb5 | #8fb2e0 | zap |
In the SOPs menu, peels, lasers, energy devices, regenerative, injectables and procedures belong to Skin. A category without an SOP yet stays grey until its SOP exists.
Role colours
Roles are shown as role tags, never as emoji squares (decision 29 Oct 2026). A tag is a small inline span, the one agreed HTML exception: <span class="r-fm">Floor Manager</span>. One label per role, the same everywhere (SOP and checklist "By" columns, meetings, lists, the Visit Journey): the full name in the table below, singular, never a typed short label (Pract., RM, CM ...; the screen shortens it by itself) and never untagged where a role is named as the one who does, leads or attends something. In running sentences a role stays plain text. The lead of a meeting has its own Lead line in the [!glance] card, above Attendees, and is not repeated in the attendee list (decision 1 Nov 2026). Tags have one size everywhere (0.85 of the body text) and wrap only between words (decision 29 Oct 2026).
Short labels everywhere (decision 18 Nov 2026; before: SOP step tables only, 29 Oct 2026). On screen every role tag shows a short label: SOPs, the Visit Journey, meeting agendas, checklists, skill notes, JDs, also inside sentences. Hovering (mouse) or tapping (tablet) shows the full name in a small dark pop-up above the tag. The note still holds the full name, so nothing is typed differently, and search, copy and screen readers get the full name. Paper always shows the full name. Styled by role-tags.css; the website pop-up is drawn by "ROLE TAG TIP" in translate-head.html.