Polymer boilerplates

[Addy Osmani]

We currently have two Polymer boilerplate projects being used by the community to create new elements.

• element-boilerplate by Zeno Rocha
• polymer-boilerplate by me

Zeno and I are currently discussing how best to consolidate and improve these efforts and were wondering if there were any thoughts about an 'official' Polymer boilerplate being offered up to users. We're happy to continue working away on boilerplate efforts regardless but just wanted to check :)

Some of the areas we would love to improve our story on are:

• Documentation - at present neither boilerplate prescribes a way to approach this. We're interested in whether the current approach the Polymer team are using around <polymer-doc-viewer> is something worth suggesting at this point.
• Unit testing - we get asked about this a lot but are unsure if Polymer has a 'preferred' testing stack just yet. I've seen some elements using Mocha/Chai for this and we could put together something the team could perhaps review.
• Tooling - Zeno's boilerplate offers barebones tooling (Grunt + connect) whilst mine prescribes Vulcanizer, JS/CSS/Image optimization and a kitchen-sink of tooling. We'd be interested in what the Polymer team is a sweet-spot worth suggesting.

We realize that it's still early days for the Polymer eco-system and things are still being worked out. We feel that the earlier we can prescribe some common-sense best practices (which can evolve over time), the better.

Any thoughts here would be much appreciated :)