POC: Merging Pajamas and GitLab UI
Overview
We'd like to put together a proof of concept that combines Pajamas and GitLab UI into one repository. The proof of concept will be a new, third repo to test out how the two repos will work together and ensure CI still functions as expected.
By the end of the POC we should know whether or not it is feasible to migrate the repos into one monorepo. We should also determine whether or not this solves for the problems outlined below.
Background
Problems we want to solve
- Having two external sites (pajamas & gitlabui) to visit, depending on the use case
- Building/updating components separately from updating usage documentation
Considerations:
- We want to maintain the ability to brand our design system in alignment with principles and design standards.
- We want to remain flexible. Marketing is building their own separate design system (currently a component library) using storybook. We should think about how those two component libraries may work together to build one cohesive design system in the future.
Related issues:
#359 (closed) gitlab-org/gitlab-ui#888 (closed) gitlab-org/gitlab-ui#1162 (closed) #490 (closed) #359 (closed)
Meeting notes
Paul: storybook is a great tool for writing components, it's isolated and has lots of addons like accessibility that are valuable. On the other hand, we have a Nuxt website that is easy to brand. Maybe we can build more bridges between both. Maybe embed storybook pages into nice website to make it clear SSOT.
Eipi: Based on your point above, what if we pull them into one repository?
Paul: Monorepo, so you can build components and specs/guidelines in the same project.
Eipi: One thing we could do is have design.gitlab.com folder and gitlab ui file in monorepo so keep structure in place.
Eipi: We could create a third project as a test project and a POC.
Mike: There is a react focus on storybook, so when running yarn you see a lot of errors. Were already seeing some friction in how we use storybook vs. how its suppose to be used.