In the past article, we saw some numbers from the first quarter. That was nice because we could see exactly what was happening on each channel: Site, GitHub, and Twitter.

Today, we're not only analyzing what happened from April 1, 2015 to June 30, 2015, we'll also compare those numbers with Q1 to check what we did right and what we can improve.

Yesterday, we shared our thoughts on the promise of Web Components. In this post, we’ll answer a couple of recurring questions we get about the technology, including our implementation roadmap and how we currently think about its priority in regards to other related platform work. We’re excited about the potential of these technologies, and today we’re excited to announce that we’re beginning development on the HTML Template element, one of the core Web Components technologies and the #3 UserVoice request from developers.

Our interview series continues with Microsoft Software Engineer & Internet Maker Travis Leithead, who is currently focused on DOM architecture improvements and paving the path for Web Components in Microsoft's Edge Browser.

Four of our five most-requested platform features on UserVoice (Shadow DOM, Template, Custom Elements, HTML Imports) belong to the family of features called Web Components. In this post we’ll talk about Web Components and give our viewpoint, some background for those who may not be intimately familiar with them, and speculate a bit about where we might expect them to evolve in the future. To do it justice requires a bit of length, so sit back, grab a coffee (or non-caffeinated beverage) and read-on. In part two (coming tomorrow), we’ll address questions about our roadmap and plans for implementation.

WebComponents.org is a community project. We truly believe that in order for something to be fully embraced by the community, it needs to be transparent. Starting from now, we're going to share statistics that are often not publicized by other open source projects.

I attended Edge conference in Facebook’s London office. Edge is a formidable discussion forum between developers, browser vendors, and standards makers.

On the components panel, we discussed the challenges posed by Web Components such as performance and module loading. It was a fascinating conversation, but I felt that one party was missing from that discussion: what about our users? How will they benefit from Web Components?