core-scss
Installation
SKILL.md
Styles in core/scss
core/scss is the product: a class that ships here is public API for every Tabler user. Components in shared/ui only assemble the class names defined here.
1. Where a style goes
| Path | Holds |
|---|---|
ui/_*.scss |
components — .badge, .card, .steps, one file per component |
layout/_*.scss |
page chrome — root, core, navbar, page, footer, dark, animations, accessibility |
utils/_*.scss |
utility classes — colors, background, text, sizing, shadow, opacity, scroll, hover |
mixins/, helpers/ |
mixins, functions, the utilities API |
bootstrap/ |
Tabler's managed copies of Bootstrap's own partials |
vendor/ |
overrides for third-party plugin CSS |
tests/ |
sass-true unit tests (see section 7) |
Entry points: tabler.scss (which forwards _core.scss, then _extends.scss last), plus the standalone bundles tabler-flags, tabler-marketing, tabler-payments, tabler-props, tabler-socials, tabler-themes, tabler-vendors. A new partial is not compiled until it is @forwarded from _core.scss (or the bundle it belongs to).
The module graph uses @use / @forward: a partial starts with @use '../config' as *, which is the hub forwarding settings, variables, variables-dark, maps, mixins and utilities. Cross-module @extend rules must stay in _extends.scss, which loads last.