You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to avoid including css classes as much as possible in core, leaving those kind of things to components. There are sometimes though when it makes sense to include classes to avoid duplicating code and to help encourage better markup.
.callout for example is included to style a box as if it were a blockquote. I made this decision because often we reach for <blockquote> when we're really writing an admonishment or to call attention to some bit of information, which is not the correct use of the element.
There is also an argument that an admonishment should not be styled like a blockquote because it could be considered deceitful to present one ui element as another when they are semantically different.
That's just one example, but I also want to review the inclusion of utility classes like those for typography sizes, such as .txt-h2 which styles an element as though it were an h2 (which again, could fall into the same argument above). This is not meant to be a utility heavy css boilerplate. Its not the direction I want to go, so I may eventually remove these.
Other classes, such as the video and table wrappers are necessary for those to be responsive, so those will likely be left in unless there is a more semantic way of doing this.
The text was updated successfully, but these errors were encountered:
I want to avoid including css classes as much as possible in core, leaving those kind of things to components. There are sometimes though when it makes sense to include classes to avoid duplicating code and to help encourage better markup.
.callout
for example is included to style a box as if it were a blockquote. I made this decision because often we reach for<blockquote>
when we're really writing an admonishment or to call attention to some bit of information, which is not the correct use of the element.There is also an argument that an admonishment should not be styled like a blockquote because it could be considered deceitful to present one ui element as another when they are semantically different.
That's just one example, but I also want to review the inclusion of utility classes like those for typography sizes, such as
.txt-h2
which styles an element as though it were an h2 (which again, could fall into the same argument above). This is not meant to be a utility heavy css boilerplate. Its not the direction I want to go, so I may eventually remove these.Other classes, such as the video and table wrappers are necessary for those to be responsive, so those will likely be left in unless there is a more semantic way of doing this.
The text was updated successfully, but these errors were encountered: