feat: adopt Tailwind CSS utility classes for styling - #9
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
1 participant
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
@screenly/edge-appsto^1.3.0(Tailwind CSS support, not yet published — matches the version in thetailwind-supportbranch)index.htmlto use Tailwind utility classes instead of custom CSS classes, keeping visual appearance and behavior unchangedsrc/css/style.cssdown to just the design-system import (skip Preflight, which resets border/margin/padding on custom-element hosts like<app-header>)src/render.tsso the dynamically rendered employee rows, avatars, initials, empty states, and the overlapping avatar-group in the portrait summary view carry the equivalent Tailwind utility classes (no rendering logic changed) — JS-referenced/tested class names (employee-row,employee-name,avatar,avatar-initials,empty-state,summary-count,avatar-group) are preserved verbatim alongside the new utilitiesscreenshots/*.webpto reflect current mock dataReference implementations for this company-wide Tailwind rollout:
Test plan
bun run type-checkpassesbun run buildsucceedsbun testpasses (15/15)bun run screenshotsregenerated all 10 screenshots (10/10 pass)