React Commons Collection

Thank you for your question @ThomasJay200.

The reason I built this and other similar libraries for UI components is due to the fact that I and other developers, most of the time run into situations where we would like to drastically customise already built UI pieces into something very different with respect to styles. The way these components have been built is with minimum styles which can be customised by the dev, also on top of that they could add more custom styles.

Also, the other key area of these libraries is to keep the library footprint to minimum as possible. A few popular libraries happen to have a large footprint even for a small component and that is cuz they have embedded a ton of excessive features underneath to support most cases, which devs don't even use them quite often. This all adds more bytes to your bundle and hence we end up with more chunkier apps.

Lastly, for larger UI components, I have also baked in the responsive mechanism right into the component, devs could customise every responsive breakpoint of these components as per their needs and style preferences, we don't want them to lock them in to something that we think is right, let them have their preferences.

The most compelling reason as I see it is, extreme use-ability across various projects. The idea was to built most common ui pieces in such a way that it could then be re-used into any project I or other devs built without to go into the basis of building them from ground zero. To further elaborate what I meant by this, please have a look at another library React UI Collection (https://taimoormk.github.io/react-ui-collection/) - Please note that this library has two apps built which is merely an extension of React Commons Collection. Not only that, I have made several client's projects extending React Commons Collection which saves me time and keep up with the quality across projects. All UI components are built with TypeScript and tested ensuring robust and performant codebase. Plus, an underlying theming system has been setup and wired across all these libraries, and I have extended a mechanism for other devs to customise the provided theme with the one of their choice, however they want it to be for their project.

Hope it answers your question, should you have more please keep them coming.

Say something nice to taimoormk…

2

This comment was deleted 6 years ago

DeletedUser

·
6 years ago
1. 1
  
  Thank you for your question @ThomasJay200.
  
  The reason I built this and other similar libraries for UI components is due to the fact that I and other developers, most of the time run into situations where we would like to drastically customise already built UI pieces into something very different with respect to styles. The way these components have been built is with minimum styles which can be customised by the dev, also on top of that they could add more custom styles.
  
  Also, the other key area of these libraries is to keep the library footprint to minimum as possible. A few popular libraries happen to have a large footprint even for a small component and that is cuz they have embedded a ton of excessive features underneath to support most cases, which devs don't even use them quite often. This all adds more bytes to your bundle and hence we end up with more chunkier apps.
  
  Lastly, for larger UI components, I have also baked in the responsive mechanism right into the component, devs could customise every responsive breakpoint of these components as per their needs and style preferences, we don't want them to lock them in to something that we think is right, let them have their preferences.
  
  The most compelling reason as I see it is, extreme use-ability across various projects. The idea was to built most common ui pieces in such a way that it could then be re-used into any project I or other devs built without to go into the basis of building them from ground zero. To further elaborate what I meant by this, please have a look at another library React UI Collection (https://taimoormk.github.io/react-ui-collection/) - Please note that this library has two apps built which is merely an extension of React Commons Collection. Not only that, I have made several client's projects extending React Commons Collection which saves me time and keep up with the quality across projects. All UI components are built with TypeScript and tested ensuring robust and performant codebase. Plus, an underlying theming system has been setup and wired across all these libraries, and I have extended a mechanism for other devs to customise the provided theme with the one of their choice, however they want it to be for their project.
  
  Hope it answers your question, should you have more please keep them coming.
  
  Taimoor
  
  ·
  6 years ago
  ·