Yes, this is a feature that is on my TODOList for future development. You may have noticed that we actually have two templates coded into zim already, one for new pages in general and one for calendar pages in specific. So far this is a hack and not really configurable. (You can change the wiki/_New.txt template to change the global template - but a bit of a hack.)
* A default template should be configurable per namespace
* All configured templates should be copied into the notebook for portability (but this can be hidden in the ui)
* Keep a library of global templates to choose from (include some examples e.g. books / recipes / ...)
* The "new page" dialog should allow you to choose a non-standard template from a dropdown
This work will be delayed untill the python port is available. The plan is to use the exact same template interface as for exporting with full access to all page and notebook properties from the template.
Also think about an interface for plugins to extend what can be done in a template.
Yes, this is a feature that is on my TODOList for future development. You may have noticed that we actually have two templates coded into zim already, one for new pages in general and one for calendar pages in specific. So far this is a hack and not really configurable. (You can change the wiki/_New.txt template to change the global template - but a bit of a hack.)
* A default template should be configurable per namespace
* All configured templates should be copied into the notebook for portability (but this can be hidden in the ui)
* Keep a library of global templates to choose from (include some examples e.g. books / recipes / ...)
* The "new page" dialog should allow you to choose a non-standard template from a dropdown
This work will be delayed untill the python port is available. The plan is to use the exact same template interface as for exporting with full access to all page and notebook properties from the template.
Also think about an interface for plugins to extend what can be done in a template.