Establish a Design System (Storybook or similar)

[davort]

More and more fragmentation is being introduced as we keep building new parts of MyMeta and MetaOS. There are cases where within a single view, same components—e.g. primary and secondary buttons—look slightly different. This makes us look bad, whereas it deteriorates the experience for users, and makes it more difficult for them to use MetaOS.

In order to keep growing the MetaOS in a sustainable manner—such where every new part that's built doesn't introduce more variety and decreases consistency of UX—it is time that we start actively working on our design system.

We used to have Storybook, but now it's gone. We need it—or another viable alternative—again.

This time around, let's start small, and grow from there. Inspired by this article—Starting a Design System—I propose that we start with:

1. Header
2. Buttons
3. Footer

Every new UI that we build should use exactly these coded components. All new components that we design and code for the next UI, once optimised, would be "extracted" and introduced into the Design System—both in Figma and Storybook.

I would be happy to prepare the components in Figma. Looking for a builder who would like to contribute from the code/Storybook side of things.