RSS feeds in the directory: 2797
Added today: 0
Added yesterday: 0
Translation of the article Components and concerns from adactio.com published on css-live.ru with permission of the author by Jeremy Keith
Sometimes we are too addicted to the false opposition in the world of web design and web development. Recently, I noticed one pop up regularly in the design of systems and components.
But in the present era of a component indicate that it makes sense to divide things according to their function. Here is what Diane Mounter in his great article about the design system in Github:
This is very consonant with the thesis stated earlier in the presentation, Cristiano Rastelli.
the Division of responsibility in accordance with the objective of each component is more than logical... but that doesn't mean that we should cease to separate structure, presentation and behavior! Why not do both?
In his article "the First library patterns: an approach to the control of CSS" Rachel advises to start each component with a good markup:
You should always start with well-structured markup.
This ensures that your content is available on the most basic level, but it also means that you can take advantage of the normal flow (i.e. the most basic CSS layouts, blocks and lines of text — approx. transl.).
basically this approach, the rule language with the least capacity (the more powerful the language data is processed, the harder it is to use these data in the future, so if the problem can be solved in simple, purely descriptive language, it is not necessary to select a complex procedural; sometimes considered a special case of the principle of least privilege with regard to the choice of language — approx. transl.). In Chapter 6 of the book "Sustainable web design" I have outlined a three-step process that I follow when designing for the web:
to Determine the basic functionality to Make this functionality available using the most simple technology, which only you can Add to improve!
the Chapter is full of examples of how to apply these steps to the whole site or product, but it is not necessary to stop on it:
This three-step process can be applied at the scale of individual components on the page. "What is the main functionality of this component? How can I make this functionality available using the simplest technology? But now how can I improve it?"
the division of responsibility when creating pages when creating components, there is another common benefit. In the case of pages, the question "what's the main functionality?" will help you to find a good URL. With respect to the components this will help to come up with a good name... and this is what constitutes the core of good design system. In his brilliant book "Design system" Ala recommends that you ask the question "what is the purpose?", to achieve a good common language for everyone who works with the components.
My thesis is:
to Separate structure, presentation and behaviour is good. To divide the interface components is good.
These ideas not contradict each other. To present them as a mutually exclusive choice — it's like saying "I used to eat Italian food, but now I drink Italian wine." They work best in combination with each other.
Efficient work standards, part 2: the hard way to compromise 03.07.2018 at 15:10
Stable, declarative, contextual (a new look at the strengths of CSS) 01.07.2018 at 12:57
11 best English-language resource for web designers 30.06.2018 at 08:56
The state of Affairs on the web: main strategies image optimization 24.06.2018 at 19:49
Weekly compilation of beautiful effects in CSS/SVG/JS #79 09.06.2018 at 21:14
Where are all the hard line breaks. That's all CSS and HTML tricks to do this 28.05.2018 at 08:24
Eqio — simple, compact alternative to expression from the element/container 22.05.2018 at 08:40
More accessible markup with display:contents 17.05.2018 at 09:18
The path to the CSS in addition to the "big three" properties 14.05.2018 at 11:03