One of the limitation of using static files as the basis for templates (as opposed to dotnet templates for instance) is that there is no template processing, of content or filenames, when generating a new project. I have now added rudimentary template processing to the au template command I added earlier. It is used like this:
au template -n App -o Src -ns Designs.Digital.App
Here:
-n App would set the name of the project file to App.csproj
-o Src would set the output folder to be named Src
-ns Designs.Digital.App would set the base namespace of all the classes in the project to Designs.Digital.App. This is throughout the project.
Values entered at the command line when invoking the au template command can be mapped to a template using an aurelia.template file at the root of the template. So any values entered can be used in the processing of the template during project generation. The template processing consists of file content string replacement and file renaming.
So now it should be possible to create templates of any project type and have some basic customisation based on user input.
As @ajoslin103 mentioned, versioning the templates with metadata in the aurelia.template file would be required, and maybe template specific install process and instructions via individual WorkflowEngine definitions?