major rework - don't merge yet!

[jonschlinkert]

I just wanted to get this pushed up. we can leave the pr open until everyone things it's good to merge.

There is a lot here, but the main thing I focused on was subgenerators. I started documentation for them, but not all of them have been created. Since @doowb already put the helper/plugin generators together, it might be good to use those somehow when a user runs yo assemble:helper etc. But I'm not sure how that works yet.

Also, I probably broke the gruntfile! sorry @hariadi, I haven't had a chance to test or fix issues - I'm still working on this.

If anyone else wants to add to this pr, with templates, tests, fixes, whatever, please do!!! Let's make this a first class generator! (I might even add themes!)

[hariadi]

💯

themes? 1000X 👍

[jonschlinkert]

what do you think so far @hariadi? I think the structure and flow is feeling pretty good, so I can start working on actual templates/content next.

[hariadi]

👍

I'm working on configstore in my local. It's ok with current structure?

[hariadi]

Ahhh.. I see you already use configstore. 👍

[jonschlinkert]

yeah, it seems to work great. basically it just saves a few values from the previous run. any time you change one of those values, you will be presented with the new value(s) on the next run.

[pburtchaell]

Hey @jonschlinkert and @hariadi if there is anything I can do to help out here, I would be happy to. I could work on LESS and Sass support as requested in #48 as well as Foundation 5 support as requested in #46.

[jonschlinkert]

@pburtchaell awesome, that would be great! on a related note, might be good to do a skype call or something to update you on what we're planning in general

[pburtchaell]

Certainly @jonschlinkert. I will be on vacation from tomorrow to August 10 so I'll be fairly free; send me an email at [email protected] or a DM on Twitter and we can plan out a call.

[jonschlinkert]

@pburtchaell sounds like a plan!

[pburtchaell]

So my thoughts are to split the generator several parts:

1. Have a main generator for your gruntfile, package.json, and some example markdown, handlebar files, etc —all that you need to generate HTML pages.
2. Have a sub-generator for CSS (and maybe JS?) —choose from bootstrap, foundation, or no framework (no framework being just a CSS compiler task where you can choose either Sass or LESS).
3. Have a blog sub-generator.

What do you think everyone?

[jonschlinkert]

Well, we might want to hold off until we release the next version. Actually related to the call I mentioned.

Have you seen the pr?

Sent from my iPhone

On Jul 23, 2014, at 10:26 PM, Patrick Burtchaell [email protected] wrote:

So my thoughts are to split the generator several parts:

Have a main generator for your gruntfile, package.json, and some example markdown, handlebar files, etc —all that you need to generate HTML pages.

Have a sub-generator for CSS (and maybe JS?). Choose from bootstrap, foundation, or no framework (just a CSS compiler task where you can choose either Sass or LESS).

Have a blog sub-generator.

What do you think everyone?

—
Reply to this email directly or view it on GitHub.

[pburtchaell]

I did not actually... for some reason I assumed it wasn't a major change because of the small # of commits, but I just checked out the PR. Looks good. And yeah, we can discuss on a call.

[salbaldovinos]

I'd love to see #46 👍