Creation Rules should support file templates.

[taylorhadden]

A note creation rule should be able to reference a file template when creating the note.

There are a couple of open questions here:

• Where are file templates stored?
• Are file templates just other notes? Are they a special file format?
• What kind of wildcards / replacement tokes should be supported?

[WhiskeyJack96]

Some of my thoughts:

• templates are often the least portable between apps (they rarely render the same in different pkms)
• templates are rarely desired to be linked to/queried from
  • templates linking to their children is the typical mode of linking I've found useful, but only when I'm changing a template
  • being able to "apply changes to children" of the template (as an option) might be nice (adding a new yaml field, or removing one)

Given the above points I think storing templates out of band of the application might be ok? Perhaps a .templates or even in the .tangent folder?

As for wildcards/replacements perhaps deciding on the syntax but providing only a few simple things would be good to start (to limit scope) perhaps current date and/or the note title?

[taylorhadden]

Interesting! I was leaning towards templates being normal markdown files with some light markup assistance for the wildcards. I suppose they still would be regardless of whether they lived inside the .tangent folder or not.

The question of linking notes to the templates that they were generated from is definitely an interesting idea. I'd ideally like that to be as simple and plain-text-ey as possible, but I also don't want to add a bunch of metadata cruft to generated documents.

The concept of re-templating content is really interesting, but also potentially seriously complicated.