Currently the Templates/ folder in the SFS stores the files that are used to instantiate complete files. However there
is an emergent use case for creating templates for snippets of code. For example see the Add Property module's use of
the template:

http://www.netbeans.org/source/browse/contrib/AddProperty/src/org/netbeans/modules/java/addproperty/AddProperty.freemarker

which uses the now available powerful mechanism of scripting based template instantiation to create the snippets of java
code while generating the property. I want to allow the user to edit this template using the Template manager
mechanism...for that I set the attribute template to true...so that it appears in the template manager. However that
makes the template appear in the New file wizard. Therefore an additional mechanism needs to be supported to store the
templates with say an attribute partial=true or something like that which are excluded from the New File wizard.

Using the new mime-path based lexer functionality could be used to do syntax colouring of template files e.g. java with
embedded freemarker and so on.

Lastly every time NetBeans does any code generation e.g. Alt+Insert in Java editor (Generate Getter, Setter, Getter and
Setter and so on...) it should be based on templates. That way the user will be able to customize the generated code.
The abbreviations could also be stored in a similar fashion and use the same mechanism. Of course the templates could
clearly indicate the required parameters in a scripting language comment block (possibly in a read only editor fold).
The read only editor folds/sections could be used in templates to disallow modification of required parts of the template.