customizations

[jonschlinkert]

We are planning on implementing some features to give implementors and end-users more control over the experience. This issue will be used for tracking.

• ~/generate: by default, user customizations, overrides, config, templates, etc will be in a generate folder in user home.
• make the folder path customizable
• generators will be in sub-directories in the ~/generate folder
• users can define a ~/generate/config.js file with any custom code to be used when running generate. This file will work like any other generator.js file, so when running generate, the CLI will do something like app.use(require('~/generate/config.js')); before loading any generators
• users can define a ~/generate/config.json file, with any global options/preferences. the path to this file will be customizable
• users can define a ~/generate/generate-foo/config.js file for every generator, which would be lazily loaded directly prior to running generate-foo
• users can define a ~/generate/generate-foo/config.json file, with options/preferences to be used every time generate-foo is run
• users can define custom templates for generate-foo in the ~/generate/generate-foo/templates directory

also discussed here: generate/generate-dest#1 (comment)

[tunnckoCore]

configurate generate with generate, that sounds like a freakin cool thing lol

[jonschlinkert]

lol yeah it's getting more fun now that we're finally actually "using" the stuff we've been creating.