Westbrook Johnson

As the WCCG, we leverage the logo in https://twitter.com/webcomponentscg and https://github.com/webcomponents-cg/ and I think other places as well. Decided. It's the "what's the 'official' web components logo?" question that I...

The "current" usage as favicon can look like the favicon for: https://web-components-cg.netlify.app/ which is the content we're working on in: https://github.com/webcomponents-cg/docs-and-guides to eventually replace webcomponents.org and that we're discussing in...

Also, as for "making a proclamation/decision/official logo"... now that we've got a decent amount of comments here, I'd like to give this a quick go no go vote at the...

Definitely, lower investment is better. In that I don't know of a way to get data out of the wiki for a repo, does it make sense to starts a...

@erikkroes you may be interested in being poked about this. I'd love to partner on some content in this area! There were some really great presentations of progress in this...

There's been some interesting talk about the _level_ of styling you can adopt in a pattern (regardless of implementation) lately and one path could be that you litter vend multiple...

I've been toying with an approach to making this possible: https://github.com/adobe/spectrum-web-components/pull/420 For me, there are two issues in particular that I'm working on: 1) ES Module based support so that...

So, in a way, the above is also a bit of a revival of #161 as well... 😬

Definitely the steps for full web component support could be more complex, but ensuring that DOM targetted code can actually be tested in a real DOM environment would be a...

Thanks for your thoughts here. I wouldn't be opposed to that, to support that path requiring as few modifications as possible could you share a little more on the following...