How Web Components Are Used at GitHub and Salesforce – The New Stack
I’m very taken with Github’s tab-container element—this is exactly how I think web components should be designed!
If you want to use Brad’s Atomic Design naming convention—atoms, molecules, etc.—and you like using Fractal for making your components, this starter kit is just for you:
Keep what you need, delete what you don’t and add whatever you like on top of whats already there.
I’m very taken with Github’s tab-container element—this is exactly how I think web components should be designed!
Remember when I wrote about Web Audio weirdness on iOS? Well, this is a nice little library that wraps up the same hacky solution that I ended up using.
It’s always gratifying when something you do—especially something that feels so hacky—turns out to be independently invented elsewhere.
This is a great proposal that would make the Cache API even more powerful by adding metadata to cached items, like when it was cached, how big it is, and how many times it’s been retrieved.
Now this is how you design a web component! A great example of progressive enhancement by Mu-An Chiou that’s used all over Github: a details element that gets turbo-charged into a details-menu.
There’s also a slidedeck explaining the whole thing.
Tim recently gave an excellent talk at FFConf. He mentioned this variation of Markdown, specifically for writing coding tutorials that update as you scroll. You can see it in action on his Generative Artistry site.
Kind of reminds of some of Bret Viktor’s work.
My Clearleft colleagues are an inspiration.
Naming custom elements, naming attributes, the single responsibility principle, and communicating across components.
I’m trying to understand why developers would trust third-party code more than a native browser feature.
Gotta keep ‘em separated.
You should hire Clearleft for these front-end development skills.