The world of frontend development is getting more complicated by the hour. There are new frameworks, tools, techniques, and user requirements every time I decide to read some news and tweets to catch up.
Finding a direction in that kind of quick and always changing environment is difficult. One way of finding a stable ground is organizing the code by some standard or a design system.
It is a system that recognizes hierarchy, importance, type, and role of each and every component. The components are combined in a way that resembles the structure of our universe.
The need for some kind of a design system appears when we start to get overwhelmed by the count of components on a project. In projects where there are a hundred or two hundred components, it is not easy to remember everything.
The mind behind this system is Brad Frost, and for those of you who want to learn more about it feel free to stop right here and first read his in-depth post on the subject. There is even a book.
In my quest for the perfect UI to recreate, I could not find anything that satisfied me completely. This is the closest I could find.
I will not try to pixel perfect it nor achieve the exact same layout. The goal here is to showcase the separation of components.
I do not consider this a deterministic process. I am certain there are better ways to decouple this UI into components but the essence is the same, make them more manageable. I will use the top-down approach.
- one page - dashboard
- two templates - header and workspace
- many organisms - tools, time, map,…
- even more molecules - tool buttons, temperature info, feed items,…
- probably even more atoms - labels, icons, links, headings,…
Making every component decoupled and available in an online catalog will make it easier for future developers to find and use them.
A component-as-a-service platform that enables components to be cloud-hosted, discoverable, versioned, isolated, and easily incorporated in other projects.
It solves common problems of managing component systems and saves developers from reinventing the wheel while increasing their productivity. Below is an example of a rendered component pushed to the Bit scope. For more information watch this video.
In the end, I created 15 components that can be combined to build the view from the example UI. The charts are not included because they are out of the scope of this article. Components are cataloged and available on this link. The repo that contains whole code can be found here.
After the development, it is really easy to make your own catalog of components. You just need to sign up on the bitsrc.io, then type in a few short commands and you are done.
# Navigate to the project directory and initialize Bit
$ cd projectdir
$ bit init
$ bit login
# Add the components to the local scope
$ bit add src/components/atoms/*
$ bit add src/components/pages/*
# Check if all components are added
$ bit status
# Tag the version and upload the components to Bit
$ bit tag --all 1.0.0
$ bit export <yourusername>.<yourscope>
The result can be seen on this link. That is a scope, think of it like a namespace for exported components. You can have as many scopes as you want, and you can make them private or public.
Let us see the
<Panel /> component here. There is support for component documentation, testing, building, and compiling. You can even explore file structure and code.
$ bit init
$ bit import <yourusername/<your_scope/avatar-image \
You are now able to use these components in any future project by just importing the component. You do need to make sure the project that you are importing the components in supports bundling of resources used. For example, components from the link above import .css files.
You should definitely explore features that Bit offers like component rendering, testing, and documenting. The best place to start is the official documentation.
Bit is a refreshing new tool that makes it easier to manage modular and reusable components in a standardized way. Developers should focus on the project requirements and quality code delivery, they should not worry about the usage of their components in other projects or by other people.
Let me know if you like this story below in the responses and make sure other people see it by clicking on the 👏.