Why ?
I work for Famiris which is a government organization which has multiple application with their own front ends. So I was wondering if it's not better to have one generic UI Component library instead of 1 per project. And I think that other big organisations also can benefit from this setup.
How ?
I learned of a "new" platform https://bit.dev/ which you can easily create new component share them and even has versioning. Some kind of Git for your components. The components are automatically tested ( if you have tests (spec test no e2e tests).
What is Bit.dev ? => https://www.youtube.com/watch?v=E5lgoz6-nfs
For presenting those components you can use https://storybook.js.org/ . Something i want to look into for presenting it to the business.
What is StoryBook ? => https://www.youtube.com/watch?v=JF7d18MqOXs
Which Components?
I was thinking to create some basic components, that we can invest more time in setting up the system instead of creating fancy components.
Some Complexer Components?
Now we know it works ?! we throw the real world stuff to it.
1) So we will take a random library and adjust some things from it and create a component around it. Is this easy to share ?
2) How do we handle some Project specific components ? Can we still injects services in it ? Can we use pipes ? And can other project makes use of it, and what do they need to import.
Time over?
Let's look into writing test and how the system handles this. Are testBed possible ? Or is there another library / platform we can use for testing our generic components.
What to do if we fuck up some thing ? How do we handle the versioning ?
Log in or sign up for Devpost to join the conversation.