webcomponents / polymer-boilerplate Goto Github PK

I'm trying to upgrade my elements to polymer 0.8, I can put up a PR for this boilerplate after upgrading. Just checking if this is in need, or I shouldn't do it.

I think that a Yeoman generator for this project should be as light-weight as possible. Maybe the flow of questions could be:

• What is the name of your element?
• How would you describe the element?
• What is your GitHub username?
• What is your name?

In other generators we try to ascertain the last two from your Git config, so maybe we could do that here too to keep things simple.

Anything else we should keep in mind?

I'm keeping forgot to build before running deploy, and it's worse when I made a release w/o knowing the dist files are not updated.

The link in the readme for the demo goes to a 404 page.

When we stopped to use the CDN and started to use Bower we had this default bower_components folder commited (which is now called lib).

We made this decision because we want people to be able to demonstrate their elements right from the gh-pages and debug them easily.

However this causes reusability problems. They cannot be shared with Bower and used by other apps.

• Encouraging use of a bower.json
• Optionally adding Polymer/Platform from Bower
• Quick description of how to publish your component to Bower

Since there're 2 branches now for this boilerplate, how do you keep src/my-element.html synced between two branches?

Does it make sense to remove src/my-element.html in gh-pages, and in index.html to make a hotlink to blob/master/src/my-element.html?

I made a component to youtube, have a look. https://github.com/brunoqueiros/youtube-element

• http://www.html5rocks.com/en/tutorials/webcomponents/customelements/

So component authors don't need to update their code after every polymer release. Eg:

"dependencies": {
    "polymer": "Polymer/polymer"
}

Or maybe a "minimum version" requirement ?

But https://github.com/PolymerLabs/seed-element does. Why are they so different?