Files
4grayandClaude Opus 5.5 e8b181fcea fix(ui): Cyrillic/Greek weights, html lang, weight normalisation (#1780)
Load Roboto 600/700 and DM Sans 700 so Cyrillic and Greek headings render
real semibold and bold faces instead of a synthetic bold, keep
<html lang> in step with the UI language, and move every font weight onto
the 400/500/600/700 scale (JetBrains Mono at 500 or lighter; the dashboard
LIVE badge now uses the interface font at 700).

Add the `styles:font-weights:validate` ratchet guard and its CI step. It
reads stylesheets much as Sass and the browser do (cascade, layers,
mixins, content blocks, `@extend`, `@at-root`, `:is()`/`:where()`,
keyframes) and lists what it deliberately does not trace in its header.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-04 08:55:23 +02:00

64 lines
3.1 KiB
Markdown

---
name: iptvnator-theme-style
description: Use when changing IPTVnator SCSS tokens, shared layout mixins, portal headers, sidebars, detail views, Electron drag regions, or cross-portal visual consistency.
---
# IPTVnator Theme Style
## Canonical Sources
- Theme contexts and app tokens: `apps/web/src/m3-theme.scss`
- Shared forwarding inventory: `libs/ui/styles/_index.scss`
- Shared partials: `libs/ui/styles/_portal-layout.scss`,
`libs/ui/styles/_content-grid.scss`, `libs/ui/styles/_portal-sidebar.scss`,
`libs/ui/styles/_panel-header.scss`, `libs/ui/styles/_detail-view.scss`, and
`libs/ui/styles/_detail-view-actions.scss`
- UI policy and migration debt: `docs/architecture/iptvnator-ui-guidelines.md`
The index is a barrel, not a configured Sass include path. Production
consumers currently use relative `@use` paths to the needed partial.
## Token Boundary
- App-owned surfaces, text, separators, hover states, selections, and provider
accents use `--app-*` tokens from `m3-theme.scss`.
- Use `--app-selection-on-color` for foregrounds placed on the selection
accent; do not assume white has enough contrast in both themes.
- Angular Material mixins and Material-component overrides may use Material
tokens. `m3-theme.scss` declares `--mat-sys-*` for both theme contexts; use
them outside Material components only for roles without an app token.
- Set component tokens through `mat.*-overrides()`; retired `--mdc-*` names
do nothing and `pnpm run styles:material-tokens:validate` rejects them.
- Destructive buttons use `.app-destructive-button` (the `warn` color input is
a no-op with M3); provider icons come from `SOURCE_TYPE_ICONS`.
- Local semantic status colors are acceptable. Existing hard-coded layout,
selection, and EPG surface colors are migration debt, not precedent.
## Shared Layout Rules
- Extend the matching partial instead of copying a large provider stylesheet.
Provider-neutral services and UI use the existing shared data-access/UI
libraries; repeated visual structure belongs in a shared Sass partial.
Portal-shared consumers use their existing forwarding style modules instead
of copied SCSS.
- In an Electron drag region, every interactive descendant—buttons, links,
inputs, overlays, and resize handles—must explicitly use
`app-region: no-drag`. The shared directive-generated `.resize-handle` sets
this centrally. Shared live sidebars reserve 8 px between their scroll
content and the edge so scrollbar and resize hit areas stay independent.
- A shared change must be checked across M3U, Xtream, Stalker, workspace,
portal catalog/shared UI, and unified collections where relevant.
## Typography
- Font weights are 400, 500, 600 or 700 only, and JetBrains Mono stays at 500
or lighter (also where a mono modifier inherits a heavier weight);
`pnpm run styles:font-weights:validate` enforces the scale, and the Mono
cap in rules that set that family. Read the
guidelines' Typography section before changing bundled fonts.
## Validation
Run the affected consumer's Nx lint/test/build target. Inspect light and dark
themes, selected/hover states, and Electron title-bar drag/no-drag behavior.