boorb-2024-01-25-02:10UTC

Getting Started with Obsidian.md

@@ -1,5 +1,6 @@
 ---
-creation-date: 2022-11-06
+date: 2022-11-06
+last-update: 2024-12-22
 ---
 # Getting Started with Obsidian
 ```table-of-contents
@@ -228,7 +229,7 @@ See [[journal]] for an example journal template file.
 
 I use weekly notes as a recurring commitment to reflect on my values, projects, and other commitments, as the important through-lines of my life. My weekly note template links to other notes that I intend to regularly revisit:
 ```
-# w-<% tp.date.now("YYYY") %>-W<% tp.date.now("ww") %>]]
+# w-2024-W02]]
 ## reminders:
 - look at [[thor-short term goals]]
 ## reach out to people, make social plans for next week -  [people sheet](https://docs.google.com/spreadsheets/d/redacted)
@@ -330,7 +331,7 @@ What follows is my current system for Very Little Overhead, which is really just
 When I evaluate a new project, I start with the following template:
 ```
 ---
-creation-date: <% tp.file.creation_date("YYYY-MM-DD") %>
+creation-date: 2024-01-12
 tags: org/project,
 ---
 # project-projectname
@@ -633,5 +634,5 @@ matches:
 [^3]:  How to choose between creating a QA Capture, QA Template, QA Macro, and `Templater: Create new note from template` :
 - Templater create new note from template: Least setup, just write the template. Create a new note from a template, filed at the top level directory. You will have to manually move the file to it's correct location (I bind this to `Alt R`.)
 - QA Template: Some setup and testing. Create a new note from a given template, either in a given directory (less useful) or with a dynamic directory selection (more useful). Allows the user to set a file naming convention.
-- QA Macro: potentially very fiddly. Combine other commands together. Works best with other QA commands, as you can reuse entry values, eg. {{VALUE:filename}}, across commands. See the QA setup for an examlpe macro in this vault.
+- QA Capture: As much setup as QA Template. Besides adding new content to other notes, QA capture can also be used to create notes from templates. QA Capture does not have dynamic directory selection, but is as useful as QA template if you already know where the file needs to be created.
 - QA Macro: potentially very fiddly. Combine other commands together. Works best with other QA commands, as you can reuse entry values, eg. {{VALUE:filename}}, across commands. See the QA setup for an examlpe macro in this vault.