The headers, buttons, cards and forms should form a common system. Comparing them together in one place helps to evaluate project coherence and develop subsequent subpages efficiently.
Collect items that occur multiple times
The design of the page repeats the buttons, section titles, service cards and messages. If each screen is created independently, small differences occur quickly: a different radius of rounding, a larger arrow or a different interval. In time, the service loses its uniform character.
It is worth preparing a simple library of these elements. It does not need to be an extended documentation. It should show the approved appearance and roles of the most important parts of the interface.
Describe the application of options
The main button can distinguish the most important action and the calmer option leads to auxiliary information. The article card and service card may be similar, but they do not have to contain the same data. Differences should result from the function rather than from the case.
- Specify the style of the main and auxiliary button.
- Set the hierarchy of headers and descriptive text.
- Show the rules for using icons and arrows.
- Consider focus, activity indication and waiting state.
Test Elements on Harder Examples
In the library, add a long title, button with more words and a card without an image. Check the behavior on a small width and with enlarged text. Thus, the following subpages do not require separate bypasses for any unusual content.
Update pattern with project
If you change a common item, check the places that use it. One patch can affect many views. Save the reason for the change and keep the compatibility between the project and the implemented version. You will read about the full behavior of the interface in the material o cohesion of the modern sideA good library does not limit creativity: it allows you to consciously develop the project while maintaining its recognizable principles.
