Closed Bug 1876603 Opened 2 years ago Closed 1 year ago

Research and doc ShadCN components and Tailwind CSS

Categories

(Firefox :: Messaging System, task, P2)

Product:
Firefox
Component:
Messaging System
Type:
task
Points:
5

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: dmosedale, Assigned: dmosedale)

References

(Blocks 1 open bug)

Details

(Whiteboard: [omc])

Bootstrapping Skylight was aided by using some prebuilt components from ShadCN, which depends on Tailwind CSS. They have some real advantages, but they're different enough from what the OMC team is used to.

I want to spike on getting rid of both in favor of just depending on one or two of the sub-components they depend on and see what that looks like. The biggest advantage to doing this would be to keep the stack closer to what the OMC team is used to, but it would also eliminate a bunch of dependencies.

There are more pros and cons than just the above, of course.

The time to make this call is now while things are still small and it's easy to change course.

Summary: Decide (and perhaps implement) whether to keep ShadCN components Tailwind CSS → Spike and decide whether to keep ShadCN components and Tailwind CSS
Summary: Spike and decide whether to keep ShadCN components and Tailwind CSS → Research and doc ShadCN components and Tailwind CSS

This ship has sailed.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.