# Templater Setup > [!abstract] What this note is > How the [Templater](https://github.com/SilentVoid13/Templater) plugin is configured in this vault, where that configuration physically lives, and how to fix it when new notes show raw `<% %>` code. ## What Templater does (in one breath) Obsidian's built-in templates paste static text. Templater pastes text **with the blanks filled in** — today's date, the time, links to yesterday and tomorrow — by running the little `<% ... %>` instructions inside a template file. Our [[Daily Notes Template]] depends on it. ## Where the config lives Plugin settings are *not* stored with your notes. Each plugin gets its own folder inside the hidden `.obsidian` directory: ``` vault/.obsidian/plugins/templater-obsidian/ ├── main.js ← the plugin's code (installed by Obsidian) ├── manifest.json ← version info └── data.json ← YOUR SETTINGS — the part worth knowing about ``` Everything you toggle in Settings → Templater is saved to that `data.json`. Ours says, in plain English: | Setting | Value | Meaning | |---|---|---| | `templates_folder` | `templates` | Look for templates in the `templates/` folder | | `trigger_on_file_creation` | `true` | **The important one.** Run Templater automatically on every newly created note | | `enable_folder_templates` | `true` | Allow per-folder template rules | | `folder_templates` | `journal` → `Daily Notes Template.md` | Any note born inside `journal/` gets the daily template | ## Why "trigger on file creation" matters The Daily Notes core plugin *pastes* the template but doesn't *run* it — it isn't Templater-aware. Without the trigger setting, you get a note full of raw code like: ``` # <% tp.date.now("dddd, MMMM D") %> ``` With the trigger on, Templater notices the new file, executes the instructions, and you get: ``` # Friday, July 10 ``` > [!tip] Golden rule > If a new note ever shows raw `<% %>` tags: Settings → Templater → turn on **"Trigger Templater on new file creation"**, reload Obsidian, delete the broken note, and create it again. To rescue a broken note instead, open it and run the command **"Templater: Replace templates in the active file."** ## Gotchas learned the hard way - **Reload after hand-editing.** Obsidian reads `data.json` at startup only. Change it outside the app (by hand, by script, by AI) and nothing happens until you reload. - **Link formats must match filenames.** The template's `previous:`/`next:` links must use the *exact* daily-note filename format (`YYYY-MM-DD dddd`), or every note links to nowhere. - **Multi-line code breaks inside callouts.** A `<%* ... %>` block spanning several lines inside a `> ` callout gets the `>` characters mixed into its code. Keep template code on one line, or outside callouts. ## Related - [[Vault Schema]] — the whole vault's blueprint, including all config files - [[How To Get Started]] — what plugins are, for newcomers