Why we created WebComponents.org?
• 4,702 views
It all started 7 months ago in October, 2013 with a new organization on GitHub called
WebComponentsOrg. Googlers from the Polymer/Chrome team, along with some great folks from Mozilla's X-Tag/Brick, as well as other Web Components community members (like me) had been cooking up a vision for a simple, neutral site/community devoted to encouraging good best practices for Web Components.
However, we believed that for Web Components to truly succeed, it was important that web developers strive to make their components interoperable among frameworks and easily discoverable. Polymer was doing well in the role of pioneering and evangelizing those best practices, but it was becoming clear that formalizing them in a more neutral place will be strategically important.
Getting our hands dirty
We were a bunch of developers with limited resources, so we started to develop ourselfs. First, Addy Osmani put together something simple based on the setup over on yeoman.io using Jekyll and Redcarpet. The idea was a compiled wiki that anyone could come in and edit but members of the site team needed to approve the changes in order for them to go live.
That helped us to shape what we wanted to cover under that new initiative. But we clearly needed to put more effort into it, specially in the user interface part. In November 2013, I created a mockup and proposed a new UI based in cards. Then I went to the Mountain View and presented it to some Chrome team members.
Everybody liked it but we still needed someone to design it in Photoshop or something like that. Again, resources were limited, we just couldn't alocate a design team from Google or hire a design agency to do this. But hey, this is the open source world that we're living it. So I talked to Briza Bueno, an incredible person with high skills in design who happens to be my sister. She agreed to help us and we started to play for real now.
New logo, new home, new everything
Briza did some really cool stuff, from redesigning the main logo to creating several W3C's Spec icons. Which can be all found in the Web Components icons repository by the way.
At some point, tired of writing
WebComponentsOrg all the time on GitHub, I decided to track the owner of the WebComponents organization. After some tweets I finally found Daniel Buchner from Mozilla who was kind enough to add us as admins.
The CustomElements.io source code and the boilerplate repo were moved under this new organization too. Later on, new boilerplates were date:
Finally, some social media and discussion channels were created too:
- @webcomponents on GitHub
- @Web_Components on Twitter
- +Web Components on Google+
- webcomponents on Google Groups
#webcomponentson Freenode IRC
...And it finally landed!
After months thinking and discussing this project, I'm really glad that it's finally live to the public at WebComponents.org.
I just got back from San Francisco after officialy launching it at SFHTML5 and now I'm in a plane from Salvador (Brazil) to Warsaw (Poland) where three presentations wait for me in Europe. We still have lots of things to do but it's a honor to show this project to people all over the world.
Each day I believe more that to achieve great things you need great people next you. This project wouldn't exist with the help of many people that you may not see in the commit history but had a really big influence like Addy Osmani, Alex Komoroske, Bernard De Luna, Briza Bueno, Ciro Nunes, Daniel Buchner, Eduardo Lundgren, Eric Bidelman, Luan Muniz, Pascal Precht, Rob Dodson, and Sindre Sorhus.
Thank you so much guys for all support you've been providing.
Stay up to date
My email list is the best way to follow all the work I'm doing. Sign up below.