Accessibility is one of the areas which is very important yet ignored by the developers, designers, and copywriters.
Everyone assumes that Accessibility is 'only' developer thing and there are many such myths around Accessibility. Today I am going to burst such myths.
For the last 2 years, I am working on the Design System. For the last 1 year, I am working on building a Design system for my company.
I have given a few talks on the same locally and international too. I keep sharing my learning around DS on my social media profiles such as Twitter or Linkedin. Yeah!! folks reach to me with their doubts and questions around design system and here are that :< /p>
Your design system is available from a year now and now you have to take the call on removing some components or features. Should you? and if yes...then how?
How to build the design system? What to keep in the design system? What features we should have? How the components should look like? and so on. I am sure whenever you hear about building or designing a design system, these questions popping in your head. Well, whom to go for the answers of these?
You will hear or read a lot around the Design system and why one should consider building or adapting one. Before committing yourself to the Design system, it is important to understand the other (non-happy) side of the design system too.
Building design system is a task in itself but how your users are going to consume your design system in their code is an important task to plan for. This is important also because this will bring few more topics too such as release plans, maintenance, scalability, etc.
Developer experience is an important aspect while building the Design System. When I say 'developer', it means developers behind the design system. Why their experience is important? My question would be why not? They are the one who is building the Design system as well as while maintaining and scaling your design system dev experience matters a lot.
As a design author, you will get stuck to decide how much components should be flexible? What flexibility means the end consumer (developer) can extend the component, change the style, functionality and edit it as per their requirement. So, how much flexible your Design system should be? or it should not be? Let's see
If you are building a design system for open source then the things we discussed in earlier posts about design and tech audit won't be applicable in this case. Then the biggest problem cames is which component to keep and which to not? In this post, I will share the components must be in your design system
Developers have many options in today's world to create reusable components for the Design system. From Reactjs to the vanilla js. Picking the right tech could be overwhelming because of the obvious reasons - too many choices. Let's see today what key factors one should consider while picking the UI tech for the development of the components.
We are again and again talking about the components. Make the list of the components, make the reusable components. I am sure you must be scratching your head that what these components are? How I pick the components? Will, there be any architecture of the components?
