Implement getTemplate() api for theming and plugins

[Oza94]

Now it is not possible for a theme (or a plugin although this is not implemented yet) to override a jade template. We should offer this feature by exposing a getTemplate('path/to/template') method and using this method rather than standard include path/to/template.

On application startup, we will lookup for templates in 4 locations (higher number means higher priority)

1. default template
2. theme folder
3. plugins folder
4. site templates (user defined templates)

If two plugins override the same template, then the last one who overrides the template has won.

Therefore, templates should be as modular as possible. The recommendation if there is a conflict between themes/plugins (e.g. and theme and a plugin booth try to change the editor template) is to create a proper template in site templates.

[izeau]

I think a more modular approach would be to use hooks, e.g. a hook when the navbar is being rendered, a hook when an article is being rendered, etc. This way, multiple plugins can override the rendered HTML, and the theme can define what’s available or not for plugins.

My 2 cents.=

[Oza94]

You are right I think there is two use cases

• When you need to replace the whole template (because you need to use some special markup, e.g. angular-material)
• Hooks when you want to append content to an existing template (social share icons, footer content, ect.)

The getTemplate() method is a suggestion, I'm thinking about an elegant way to implement such a system.