Some further feedback :)

[addyosmani]

Hey Zeno!

I thought I'd continue our thread here just to capture some more feedback in case it's of help:

• Rather than calling the generator yeoman-jquery, generator-jquery-boilerplate might be a more readable entry for the npm registry and it follows the convention being used by other authors.
• It might be useful to add a few sentences about how the output of this differs from grunt-init (which Yeoman will be replacing soon) so that developers know that the output is of course specific to jQuery Boilerplate.

[zenorocha]

Hey Addy!

Awesome, thanks :)

• NPM registries generator-jquery and yeoman-jquery are now removed to give place to generator-jquery-boilerplate.
• That's true, I'll try to write something about that.

[addyosmani]

I wonder if there's anything more we can do to improve the user-experience of this generator. Perhaps we could prompt them for common actions/boilerplate they may need that we could add on top of jQuery boilerplate or help in other ways?

Perhaps we could even recommend it somewhere on http://jqueryboilerplate.com/?

[zenorocha]

First step completed.

With the new redesign of jqueryboilerplate.com, people can now discover this Yeoman Generator project.

[zenorocha]

I agree that we could improve the UX with some prompts, I'm going to add it to the roadmap.

[johnraz]

Any news about the prompt system ? I was first thinking of doing some nasty search replace magic before copying the files over but it's definitely too ugly to be considered acceptable.

Do you think that it would be possible to change the main jquery boilerplate's file to make use of yeoman template variable where relevant?

[addyosmani]

Do you think that it would be possible to change the main jquery boilerplate's file to make use of yeoman template variable where relevant?

Should be possible.