vault backup: 2026-04-17 16:29:28
This commit is contained in:
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 2026-04-17T14:57:07-0400
|
||||
aliases: []
|
||||
title: 2026-04-17 14:57:07
|
||||
tags:
|
||||
- authorship/original
|
||||
- destiny/permanent
|
||||
- status/draft
|
||||
- type/periodic/timestamped
|
||||
dg-publish: true
|
||||
date-created: 2026-04-17T14:57:07-04:00
|
||||
daily: "[[2026-04-17]]"
|
||||
weekly: "[[2026-W16]]"
|
||||
monthly: "[[2026-04]]"
|
||||
quarterly: "[[2026-Q2]]"
|
||||
yearly: "[[2026]]"
|
||||
---
|
||||
# 2026-04-17 14:57:07
|
||||
|
||||
## Templater Community Plugin
|
||||
|
||||
[Templater](https://silentvoid13.github.io/Templater/introduction.html)
|
||||
is an [[obsidian]] community plugin
|
||||
which appears at first glance to be for note templates,
|
||||
like the Templates core plugin,
|
||||
but it's really more of a low-level plugin
|
||||
for executing arbitrary [[javascript]] on your vault
|
||||
which happens to be useful for templates.
|
||||
|
||||
I believe I tried it once before,
|
||||
but I bounced off the use patterns.
|
||||
|
||||
A "template" to Templater
|
||||
is better called a _script_,
|
||||
but unlike in most interpreters,
|
||||
text is passed through by default.
|
||||
Body text is not necessary either,
|
||||
you could have a "template" that's just straight JS
|
||||
(via the <%* %> syntax).
|
||||
|
||||
Many community plugins could be replaced with templates,
|
||||
namely those with simple behavior and no GUI.
|
||||
|
||||
I think Templater may be ideal for [[vault-maintenance]] scripts,
|
||||
one because it doesn't require a separate runtime,
|
||||
but mostly because scripts can be written in Obsidian.
|
||||
|
||||
***
|
||||
|
||||
Ensure all linked periodic notes exist:
|
||||
1. Get all linked periodic notes that don't exist
|
||||
2. Create each with all appropriate frontmatter properties
|
||||
3. Repeat until all exist.
|
||||
Reference in New Issue
Block a user