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 don't mean that (the title) as a slight or in any negative way at all. My suggestion is this, "create the examples as close to actual projects as possible" to illustrate to people how they could/should structure a project for their own ideas.
I'd be happy to help submit PRs to illustrate if you are interested.
The text was updated successfully, but these errors were encountered:
I'm deep in a contract right now. Once I come up for air I'm considering building a landing page. If you have some fun examples (ideally ones that "dazzle" with pretty graphics and stuff) that would look good on a landing page, please do send them.
One "rule of thumb" I've learned from this current contract is to use child combinators for pretty much everything.
So your top-level classes should be "unique" enough (i.e. .user-comment-component). Then, for all the child elements, I use child combinators for selecting them (i.e. .user-comment-component > .form > .title > label). This protects against "surprises" when you nest components and styles cascade down into the children.
ShadowDOM would also solve this, but comes with it's own trade-offs.
I don't mean that (the title) as a slight or in any negative way at all. My suggestion is this, "create the examples as close to actual projects as possible" to illustrate to people how they could/should structure a project for their own ideas.
I'd be happy to help submit PRs to illustrate if you are interested.
The text was updated successfully, but these errors were encountered: