Skip to content

feat: adopt Tailwind CSS utility classes for styling - #6

Draft
nicomiguelino wants to merge 1 commit into
developmentfrom
chore/adopt-tailwind-css
Draft

feat: adopt Tailwind CSS utility classes for styling#6
nicomiguelino wants to merge 1 commit into
developmentfrom
chore/adopt-tailwind-css

Conversation

@nicomiguelino

Copy link
Copy Markdown
Contributor

Summary

  • Rework index.html to use Tailwind CSS utility classes (with arbitrary-value bracket syntax for exact px/rem/gradient/shadow values) instead of the custom .container/.qr-section/.text-content/.qr-container/#qr-code/#cta CSS classes.
  • Landscape max-width breakpoints and portrait overrides are expressed with landscape:max-[Npx]: / portrait: / max-[Npx]:portrait: variants, in the same cascade order as the original media queries so narrower breakpoints still win.
  • The dynamically-inserted QR SVG (appended to #qr-code via JS) is styled with the [&>svg]:w-full [&>svg]:h-full [&>svg]:block arbitrary variant instead of a #qr-code svg selector.
  • The --theme-color-* custom properties (set at runtime by setupTheme()) are now referenced inline via var(--theme-color-primary,#972eff)-style fallbacks directly on the elements that use them, instead of a :root block.
  • Slim src/css/style.css down to the standard layer/import block used across the migrated repos.
  • Bump @screenly/edge-apps to ^1.3.0 (unpublished; ships Tailwind support).
  • Regenerate screenshots.

This is a pure refactor - no visual or behavioral changes intended. Same pattern as the pilot migrations:

Test plan

  • bun run type-check passes
  • bun run build:dev builds cleanly, Tailwind utilities compile into dist/css/style.css
  • bun run screenshots (Playwright) regenerates all 10 screenshots successfully
  • Visually reviewed landscape (1920x1080), portrait (1080x1920), and small portrait (480x800) screenshots - headline, QR code sizing/position, and CTA text all render correctly
  • @screenly/edge-apps was temporarily installed from the local unpublished tailwind-support tarball for testing, then package.json/bun.lock were reset to committed state before committing (only the ^1.3.0 version bump reapplied; lockfile untouched)

Rework index.html to use Tailwind utility classes instead of custom CSS
classes, keeping visual appearance and behavior unchanged. Slim the CSS
entry point down to just the design-system import. Bump
@screenly/edge-apps to ^1.3.0 for upcoming Tailwind CSS support.
Regenerate screenshots to reflect the change.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant