You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strongly related to #654 (comment) (as a nice followup) - once a generalized "get input from prompts to hydrate a template" is available, how about using template "fragments" to insert structured text into the current note/buffer rather than only using templates to create new notes?
Again, this is a workflow I've come to really appreciate in Obsidian, powered by QuickAdd.
The most powerful unlock of this feature is that you can pop open a command and enter some text, knowing the correct update will end up in the correct note without having to change bufffers, open a split, etc. otherwise lose context on your current work.
Alternatives
No response
Additional context
Examples of how I use the above feature in Obsidian today:
New Note. Prompt for:
title of note
I (optionally) use this prompt to create notes because: a template fragment inserts a:
- New note created (<timestamp>): <note title>
In my daily note for that day. This way new notes automatically end up with a backlink to the day they were authored.
Capture "thing I did". Prompt for:
what did you do?
This action inserts a similar bullet as above with <timestamp> thing I did: <template text> into that day's daily note. This is nice for quickly logging little journal-like items without opening up your daily note and writing out a timestamp.
There are some others but I think the point is made.
If you look back to the linked issue at the top, each of those multi-step templates are actually triggered by the style of command I'm describing here and each is logged to my current daily note as mentioned above.
This is a daily-note-centric approach to how I happen to use these features. But with prompting templates + the ability to insert structured text fragments into other notes, arbitrary powerful custom workflows can be created fairly easily.
The text was updated successfully, but these errors were encountered:
🚀 The feature, motivation and pitch
Strongly related to #654 (comment) (as a nice followup) - once a generalized "get input from prompts to hydrate a template" is available, how about using template "fragments" to insert structured text into the current note/buffer rather than only using templates to create new notes?
Again, this is a workflow I've come to really appreciate in Obsidian, powered by QuickAdd.
The most powerful unlock of this feature is that you can pop open a command and enter some text, knowing the correct update will end up in the correct note without having to change bufffers, open a split, etc. otherwise lose context on your current work.
Alternatives
No response
Additional context
Examples of how I use the above feature in Obsidian today:
I (optionally) use this prompt to create notes because: a template fragment inserts a:
In my daily note for that day. This way new notes automatically end up with a backlink to the day they were authored.
This action inserts a similar bullet as above with
<timestamp> thing I did: <template text>
into that day's daily note. This is nice for quickly logging little journal-like items without opening up your daily note and writing out a timestamp.There are some others but I think the point is made.
If you look back to the linked issue at the top, each of those multi-step templates are actually triggered by the style of command I'm describing here and each is logged to my current daily note as mentioned above.
This is a daily-note-centric approach to how I happen to use these features. But with prompting templates + the ability to insert structured text fragments into other notes, arbitrary powerful custom workflows can be created fairly easily.
The text was updated successfully, but these errors were encountered: