1. You can mix and match components
For example, let's say a site only contains five atoms: a small image, large image, paragraph, list item, and a link. You could create a very usable web page by duplicating and combining these atoms to make molecules.
2. Creating a style guide is simple
Even for sites that haven't been built atomically, it isn't difficult to extrapolate the basic components and put them together to construct more pages.
Bear in mind, though, it is always best to create a site atomically from the beginning, rather than trying to introduce Atomic Design principles to a site later on. If a site is created according to Atomic Design principles from the get-go, all the atoms and molecules that are created before the site is built can serve as a basic style guide.
3. Easy to understand the layout
The code of an anatomically designed website is typically much easier to read than one created a more traditional way. Another bonus of this is that it makes it easier to explain the codebase to a new developer.This is true not only during the time of creation but in the future when a site is being looked back on for reference or small tweaks. Because of the documentation around what atoms molecules and organisms are being used and where it's easy to see what each part of the code represents.
Useful topics for you: android code signing, software tester skills, programming languages for programmers
If there were no red buttons, they'd need to create a new one. However, it is easy to go back through the list of atoms and find that exact red button. For example, if someone creates a site without using Atomic Design and they require, say, a red button, they would have to look through the whole site to try and find an existing one.
This becomes a much easier process when the Pattern Lab library is involved. Pattern Lab is a collection of tools that make Atomic Design easier.
Let's say a creator has a list of titles used for the site, all in black: the main header, sub-header and paragraph title. A great example of this would be for titles on a site. Instead, they can simply look through the list of existing atoms, and tweak them to create new atoms if required.
4. Code is more consistent
With Atomic Design, you use predefined atoms to create the site layout, it is easy to see which components are being used for different parts of the site. This reduces the likelihood of writing duplicate code. If this did exist, they would need to copy and paste that code to the new instance.If there were no red buttons, they'd need to create a new one. However, it is easy to go back through the list of atoms and find that exact red button. For example, if someone creates a site without using Atomic Design and they require, say, a red button, they would have to look through the whole site to try and find an existing one.
This becomes a much easier process when the Pattern Lab library is involved. Pattern Lab is a collection of tools that make Atomic Design easier.
5. No focus on pixel-perfect designs
They haven't worked on the site in a while and need to come back to the site to add a new blue title. They could take a look at the titles that already exist and customize one of them to get the result they desire. As the idea behind Atomic Design is to use atoms as the building blocks for site creation, it is less likely that a web developer will create many atoms for a similar thing.Let's say a creator has a list of titles used for the site, all in black: the main header, sub-header and paragraph title. A great example of this would be for titles on a site. Instead, they can simply look through the list of existing atoms, and tweak them to create new atoms if required.
6. Quicker prototyping
The mockup can then be customized and refined for the final site. Having a list of atoms before site creation begins means you can mock-up pages quickly and easily – all that is required is to pick and combine the required elements for the page.7. Easier to update and remove parts of the site
Similarly, unwanted components can easily be removed. As only one atom, molecule or organism is being changed at any one time, it is easy to ensure that any updates to a component are carried across to all other instances across the site.8. More modular file structure
I myself use atomic CSS for websites I create and have found great benefits to this approach. However, I believe with the arrival of things like HTML components it would make sense to separate CSS and JavaScript specific to an atom into its own folder along with the HTML.
Although Atomic Design is very prevalent when it comes to markup, I believe these techniques can also be used for CSS, JavaScript, or any other languages used to create a site to make overall code more modular and reusable. So if anything needs updating or deleting, you know exactly where to go and what to change.
9. Fewer components overall
This will result in fewer atoms being used overall, making for a cleaner and leaner website. If a title with a font size of 4.5em is required for design but there is already a 4em size title in existence from the list of atoms, it is more likely a creator will pick the 4em one than create a completely new title.
If a creator has a list of atoms, molecules, and organisms presented to them before site creation begins, they are more likely to use what already exists than create new components for small variations.
0 Comments
Post a Comment