Create shared lvl0/theme package for cross-project styling #26

New issue

Open

opened 2026-03-30 01:02:30 +02:00 by myrmidex · 0 comments

myrmidex commented

2026-03-30 01:02:30 +02:00

Owner

Create a shared lvl0/theme repo containing the common visual identity used across all lvl0 projects.

Scope (CSS/Tailwind only — no framework components):

Tailwind preset: color palette (red-500 primary, dark backgrounds), spacing, typography scale
CSS custom properties for non-Tailwind consumers
Font files (7-segment digital font, monospace stack)
Utility classes (.glow-red, glow effects, 80s digital theme utilities)
Shared app.css base styles

Not in scope:

React/Livewire/framework-specific components (framework-agnostic by design)
Component behavior or JS logic

Consumption: npm package or git submodule. Each project imports the preset in tailwind.config and the base CSS.

Why: The 80s digital theme currently lives only in buckets' app.css. As more lvl0 projects launch, duplicating and drifting styles is inevitable. A single source of truth keeps the visual identity consistent.

Depends on: #21 (extract reusable UI components) — that ticket will identify exactly which styles are shared vs project-specific, informing what goes into the theme package.

Create a shared `lvl0/theme` repo containing the common visual identity used across all lvl0 projects. **Scope (CSS/Tailwind only — no framework components):** - Tailwind preset: color palette (red-500 primary, dark backgrounds), spacing, typography scale - CSS custom properties for non-Tailwind consumers - Font files (7-segment digital font, monospace stack) - Utility classes (`.glow-red`, glow effects, 80s digital theme utilities) - Shared `app.css` base styles **Not in scope:** - React/Livewire/framework-specific components (framework-agnostic by design) - Component behavior or JS logic **Consumption:** npm package or git submodule. Each project imports the preset in `tailwind.config` and the base CSS. **Why:** The 80s digital theme currently lives only in buckets' `app.css`. As more lvl0 projects launch, duplicating and drifting styles is inevitable. A single source of truth keeps the visual identity consistent. **Depends on:** #21 (extract reusable UI components) — that ticket will identify exactly which styles are shared vs project-specific, informing what goes into the theme package.