Update templates to use different sources of information
argenos opened this issue · 2 comments
argenos commented
Make templates recognize the source of the information, e.g. by using {{manifest.author}} in author info instead of plain placeholders:
This requires making changes to the script, so we pass different dictionaries for each source: obsidian_releases (plugins.json and themes.json), manifest.json, theme.css, eventually hub.yaml, etc.
Advantages:
- Templates become more self-documenting
- Easier to debug why some changes have happened (where did the information change)
argenos commented
Seems I had started working on this at some point: 4e3c52a
It doesn't make sense to continue on that branch, but just to have as a reference maybe.
claremacrae commented
Argenos and I discussed this, and decided that we would put the logic in to the Python code, such as in Plugin and Theme classes - and so the templates don't need to change.