I may have found a cool & easy to implement solution to both problems.
Will blog about it soon and put it up for a vote.

Allowing sharing of templates online is really cool as well, but I definitely see your point about trying to limit the scope.

These are some really interesting ideas.

Some of them might be a little big for the scope of the graduate project.

Originally I had thought of developing this as a WPF standalone application which would run after installation,
but your idea sets up the ground for a much bigger project with collaboration built-in.

I will raise this for a vote.

Thanks for your feedback and hope you keep following and helping us with this project’s development.

Success with your graduation project. I used to use Regionerate before. There are some pains in it that made me not reinstall/use it, especially in a corporate environment. One of the pain points is (you already mention it yourself) the way templates are created. I am (apparently one of the few) one of those who created completely new templates. If I go brainstorming a bit the following features come to mind:

– you could create the drag and drop editor online (you can actually base some kind of business model on it through advertising). I created something similar. I can give you the following advise: “use an existing javascript framework like jQuery or MooTools”, it’ll make your life easy.

– you can host and provide templates committed by users to your users as a service.

– allow company wide distribution of the templates, through a company-local repository or something similar. This is a pain point, when you work in a corporate environment it’s a pain to make everybody use the same templates and the same version of the template.

– it would be nice to be able to validate code files against a template in some way. So that we can check code layout during CI builds or source control commits.