TrustedSec - Obsidian - Taming a Collective Consciousness

#MMW-Dev/Workflow

About

#Omnivore

Read on Omnivore
Read Original

A thorough examination on using Obsidian collaboratively with Git

This page is powered by Omnivore ‐ you can read more about how I use Omnivore here: Omnivore - Saving Articles for Citations in Obsidian.

Highlights

Our Obsidian Git configuration consists of the following settings:

  1. Vault Backup Interval: 60
  2. Auto Pull Interval: 10
  3. Commit Message: FLast {{date}}
  4. Date Placeholder: MM-DD-YYYY HH:mm:ss
  5. Pull Changes Before Push: Enabled (default) ⤴️

Example Obsidian Git configuration for a collaborative Obsidian project.

Additionally, since we’re using Git, we were also able to leverage a .gitignore file to omit files and directories which either caused frequent conflicts or we deliberately did not want synced. We ultimately landed on a .gitignore file configuration of:

.obsidian/*

.obsidian/workspace/*

.obsidian/plugins/*

$VAULTNAME/Personal/
05*-*Personal/

DayPlanners/

.obsidian-git-data

Untitled*

null*

.trash/
.DS_Store ⤴️

Example .gitignore configuration for an Obsidian Git workflow.

Templates for Automation

Using SilentVoid13's Templater plugin, I’ve required the association of a Search Tag and a Title on the creation of a note. To require a template to run on the creation of a new note, you need to modify the following settings in the configuration options for the Templater Plugin Settings > Community Plugins.

  1. Template Folder Location

  1. Set Empty file template to 04 - Templates/0400 - Gen_Note. Differentiated by markdown "struct" we assign, this note will serve for the basis of ALL notes (content or categories).

Here we'll assign the Search Tag associated with TTP, and the title should be automatically populated from the link we clicked to create the note.

We created our note successfully! Since we selected the Search Tag of TTP, templater combined markdown elements to "build" a "TTP" note containing the boilerplate metadata and headings that may help a user get started documenting a particular TTP. Using templates in this way facilitates the abstraction of users from the overhead of committing information. In turn, this allows them to focus less on the categorization and organization of data and empowers us to control it administratively. ⤴️

Integrating Templater into the workflow to prepopulate required metadata fields and document structure.