You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's a first try at the Tailwind/design-system slice. It starts from main and makes no functional changes.
The approach. The design branch moved one area at a time onto new Tailwind-only layouts, so every area also brought new navigation and moved buttons. This stack does the opposite. It loads the design system next to Bootstrap on today's pages (no Tailwind reset, and a spec guards against class-name collisions). Then it brings the design system in one concept at a time, across the whole app.
The plan:docs/design-system-slicing-plan.md, on the design branch. It covers the next concept slices (icons, buttons, tables, forms, … then retiring Bootstrap). It also lists bugs main should get fixed regardless, the product/IA decisions hidden in the branch that each need a yes or no, the features riding along, and what probably shouldn't land.
Activity
seanmarcia commentedon Nov 16, 2026
Is a phased approach best? We can just rip off the bandaid :)
awwaiid commentedon Nov 16, 2026
Yes we took a vote and voted the branch off the island. It is too big for us to trust, there is no reason to make it too big to fail.
Add a plan for peeling the design branch apart by concept (#5764)
awwaiid commentedon Nov 19, 2026
From claude code:
Here's a first try at the Tailwind/design-system slice. It starts from
mainand makes no functional changes.The approach. The
designbranch moved one area at a time onto new Tailwind-only layouts, so every area also brought new navigation and moved buttons. This stack does the opposite. It loads the design system next to Bootstrap on today's pages (no Tailwind reset, and a spec guards against class-name collisions). Then it brings the design system in one concept at a time, across the whole app.The stack (draft PRs; review them in order):
assets:precompilefailure thedesignbranch would have hit.mainby itself.The plan:
docs/design-system-slicing-plan.md, on thedesignbranch. It covers the next concept slices (icons, buttons, tables, forms, … then retiring Bootstrap). It also lists bugsmainshould get fixed regardless, the product/IA decisions hidden in the branch that each need a yes or no, the features riding along, and what probably shouldn't land.