Skip to content

UI/UX design system segmental transition #5764

Open

Description

@ruestitch

Sean and friends created a new design system that we want to incorporate in lean slices from the Design branch

Our first slice is the style and accessibility system Tailwind, switching from Bootstrap

This is part of an overall Ruby for Good unified design system transformation

Activity

  1. added this to the RFG Design System milestone on Nov 15, 2026
  2. seanmarcia commented on Nov 16, 2026

    @seanmarcia
    Member

    Is a phased approach best? We can just rip off the bandaid :)

  3. awwaiid commented on Nov 16, 2026

    @awwaiid
    Collaborator

    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.

  4. awwaiid commented on Nov 19, 2026

    @awwaiid
    Collaborator

    From claude code:

    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 stack (draft PRs; review them in order):

    1. Design system 1/4: Add the Tailwind toolchain and tokens (not yet loaded) #5765 Tailwind toolchain and tokens. No visible change.
    2. Design system 2/4: Load the design system stylesheet alongside Bootstrap #5766 Load it alongside Bootstrap. No visible change, and pages are pixel-identical. It also fixes a production assets:precompile failure the design branch would have hit.
    3. Design system 3/4: Paint the existing UI with the design system's colour tokens #5767 Brand colours on the existing UI. Colours only; every page keeps its exact dimensions.
    4. Design system 4/4: Switch the typeface to Figtree #5768 Figtree typeface, plus a date-picker spec race fix that can also land on main by itself.

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions