Where Web Components Went Wrong (And How We Can Turn It Around)
I believe the solution is staring us directly in the eyes. CSS is a declarative language that enhances HTML. CSS is agnostic of how the HTML is produced. Despite this CSS is extremely ergonomic and powerful.
The path is there for web components to be used in a responsible and progressive manner. We just need people with the drive and desire to find a better way than the hole we've dug ourselves in.
I'm building my version of this vision with Corset. I look forward to seeing what other solutions arise.
Corset
And then a few months later, the people actually running those instances are going to start flexing their muscle, and the users' response will be, "Wait, who even are you? This sucks. I just wanted my memes".
Definitive, Semantic, and Contextual naming conventions
Naming ConventionsDefinitive naming (Avoid!!!)Semantic naming (Describe color intent)Contextual naming (Describe color use)Combining Semantic+ContextualSemantic for DesignersContextual for EngineersColor weightsSemantic+weighted (tints/shades with numbers)Meaningful/useful weights (Use of L* values)Incidental vs. Essential weights (WCAG compliance)
Designing for people with dyscalculia and low numeracy
We often forget that some people struggle with numbers, which can make our services really hard to use. But, there are things you can do to make your services more accessible.
Designing for people who struggle with numbers
We need to deliver services which convey numbers plainly and in a way that is easy for everyone to understand.
Apple Silicon is changing how consumer tech is designed thanks to software-defined hardware blocks for homogenous compute. The end of the general-purpose CPU is near.