feat: adopt Tailwind CSS utility classes for styling - #6
Open
nicomiguelino wants to merge 2 commits into
Open
Conversation
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.
nicomiguelino
marked this pull request as ready for review
August 4, 2026 20:44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Migrates
menu-board-appto Tailwind CSS utility classes, part of the company-wide rollout across edge-app repos. Reference pilot implementations: Screenly/clock-app#12 and Screenly/weather-app#6.index.html: replaced custom CSS classes with Tailwind utility classes using arbitrary-value bracket syntax for exact px/rem/gradient/shadow/color values (e.g.text-[3.5rem],bg-[linear-gradient(...)],shadow-[...],max-[1200px]:for the app's custom max-width breakpoints).src/main.ts: the dynamically rendered menu item cards (renderPage()) now carry Tailwind utility classes appended to their existing class names. Named CSS grid areas (grid-template-areas) are expressed via Tailwind's arbitrary-property bracket syntax directly on the elements.src/css/style.css: slimmed to the standard layered import (@layer theme, base, utilities+tailwindcss/theme.css+@screenly/edge-apps/styles+tailwindcss/utilities.css), plus the two custom@font-facerules (Playfair Display, Source Sans 3) and a handful of things that genuinely can't be static utilities:.fade-out { opacity: 0 }— toggled at runtime viaclassList.add/remove('fade-out')..label.vegetarian/.spicy/.gluten-freecolor overrides — keyed off arbitrary, user-configured label text lower-cased at render time, so they can't be resolved into the template ahead of time.@supports not (backdrop-filter: blur(10px))fallback.:rootcustom properties--accent-color(overridden at runtime viadocumentElement.style.setProperty) and--spacing-md(read bymain.tsfor the header's fallback margin), still referenced from Tailwind arbitrary values (text-[var(--accent-color)], etc.).package.json: bumped@screenly/edge-appsto^1.3.0(unpublished; ships Tailwind support). Lockfile untouched.screenshots/*.webp.This repo did not previously import
@screenly/edge-apps/styles(it had its own bespoke reset/tokens) — it's now brought in line with the rest of the fleet via the standard layered CSS entry point, same as the two pilot repos.Test plan
bun run type-check— passesbun test src/— 14/14 passbun run build— builds cleanly (only pre-existing, unrelatedimport.meta/chunk-size warnings)bun run screenshots— all 10 resolutions generated successfully