consider moving boilerplates to different org

[jonschlinkert]

I think boilerplates are essential to success for assemble, because they show users how it works. But to keep the assemble org focused on utils and the core codebase, we might want to move boilerplates here: https://github.com/boilerplates

Then, at https://github.com/assemble/boilerplates we would maintain an up-to-date list of available boilerplates.

cc/ @doowb / @hariadi any thoughts?

[doowb]

:+1: I think example projects can go in there too, just call them boilerplates... I'm thinking of what I just set up for assemble-swig-example since it would really be a boilerplate for using swig templates in assemble.

[jonschlinkert]

yeah, I almost made an issue to call it a boilerplate lol, but figured it was my ocd. Btw, I'm about to push updates to this mostly for the readme.

[hariadi]

:+1:

Agreed with @doowb. We need to move the examples into a repo as well.

Boilerplate

• https://github.com/assemble/boilerplate-h5bp
• https://github.com/assemble/boilerplate-gist-blog
• https://github.com/assemble/boilerplate-bootstrap
• https://github.com/assemble/boilerplate-markdown
• https://github.com/assemble/boilerplate-site
• https://github.com/assemble/boilerplate-book
• https://github.com/assemble/boilerplate-sitemap

Example (rename to boilerplate?)

• https://github.com/assemble/assemble-swig-example
• https://github.com/assemble/handlebars-helpers-examples

And update #8