Edit your templates
Change the Markdown that future creation commands use without overwriting existing notes.
On this page
Obsibrain reads creation templates from templates/obsibrain/ in your vault. Edit those files to change future notes. Existing notes keep their current content.
Find the right template
The folder contains Daily.md, Weekly.md, Monthly.md, Quarterly.md, Yearly.md, Project.md, Goal.md, Area.md, Resource.md, Meeting.md, and Person.md for enabled workflows.
- Open the template for the command you want to change.
- Edit its headings, prompts, Markdown, or native widgets.
- Save the template.
- Create a new note with the matching command.
- Check the new note’s content and views.
Keep the native properties that identify the note. For example, a meeting needs type: meeting, and its schedule comes from the creation prompt.
Use native template tokens
Obsibrain resolves a defined set of tokens during creation:
| Token | Result |
|---|---|
{{obsibrain:file.title}} |
The new note title |
{{obsibrain:file.created|YYYY-MM-DD}} |
The creation date in the requested format |
{{obsibrain:meeting.scheduled}} |
The schedule collected for a new meeting |
Review defaults also contain tokens for period navigation and reflection content. Keep a review token in the matching review template. Unknown or malformed tokens produce an error.
V2 does not evaluate arbitrary JavaScript in templates. V1 Templater scripts do not become native V2 tokens.
Understand restoration
Normal provisioning creates missing defaults and never replaces an existing template. A disabled review cycle does not receive a default template until you enable it again.
To preserve a customized template before a reset, copy it outside the vault or include it in a verified backup. Reset vault is destructive and removes vault content before restoring defaults.
The root dashboard is a separate user-owned note. Edit Dashboard.md directly and use the widget library to change its views.