IMHO the current boilerplate is overly complex and adds a lot of barriers to entry; limiting the number of components that will be created by the open source community.

Here are my concerns:

• Why is browserify and webpack used?
• What is the purpose of the browser.js build and how does it differ from dist, or index?
• The ghpages stuff seems superfluous to me, some components won't have a demo, and others might use their own scripts to manage publishing.
• The dev step seems limited; I still need to run my own server to actually test and develop the examples/?
• The test hooks and init configs are a little overwhelming (I am only familiar with tape, which tends to be much simpler).
• Are all components expected to follow this set of guidelines, or is it going to be more lenient?

With so much boilerplate/tools/config/etc in this repo, there will inevitably be a lot of fixes and changes in this repo over time (like #3), and community-driven components will lag behind.

Use budo to do the magic

Since aframe-core is now deprecated/moved

In package.json:

  "version": "0.1.0",

Boilerplate version should probably start at 1.0.0 to avoid common problems with the magic zero. Most users are unaware of the subtle differences and will leave it at whatever version is set in the boilerplate.

    "aframe-core": "*",

It might be good to avoid wildcards and just try to keep the boilerplate up to date with whatever is the latest version of aframe-core. Otherwise community driven components will quickly start running into version woes with wildcard dependencies.