Template module structure

[jackrobertscott]

Reconsider how templates may be built.

Consider current structure of template modules:

.
+-- init
    +-- questions.json
    +-- templates
        +-- .gitignore
        +-- bower.tpl.json
        +-- etc...

This structure allows templates to decide which files should be rendered through templating engine (by appeding the ext '.tpl' to a file) and provides questions for inquirer.js to ask to which the answers are used in templating the files.

This format is lacking following abilities:

• Change file names
• Bower/NPM install
• Include/exclude files based on inquirer answers
• Depend/extend from other templates

That said, this is not a complete list of desired features and not all mentioned features may be desired for compilation, but there is definitely room for improvement in current system.

[jackrobertscott]

Custom file names may be set by renaming files like the following:

example.file.txt --> {{fname}}.file.txt

Then using the corresponding inquirer data value, replace {{fname}} with data value.

[jackrobertscott]

Give templates the ability to run shell scripts before or after generator runs.