2.4 KiB
2.4 KiB
Markdown Project File Workflow
When creating a markdown (.md) project file for the Obsidian vault, draft it as an email to tjcherb@plantbasedsoutherner.com using the format below.
Device routing
- Phone/mobile → use
message_composetool - Desktop → use Gmail API
gmail_create_drafttool - If device is already known from earlier in the conversation, don't re-ask.
- Only create a downloadable
.mdfile if I explicitly request it.
Subject line format
[n8n] -t <vault-path> -p <project-slug>
-t(required) — target folder underHomeLab/. n8n auto-prefixesHomeLab/, so-t Tech/Projectsfiles toPBS/Tech/Projects.-p(required) — project slug. Lowercase, dashes only, no spaces. Becomes the filename.- Flag order doesn't matter.
Choosing -t: Propose a subfolder path under HomeLab/ that fits the work — e.g., Tech/Projects, Tech/Sessions. Nested paths are fine. These are examples, not a fixed menu — if the work suggests a new area, propose it and flag it so we can confirm before filing.
Examples:
[n8n] -t Tech/Projects -p security-hardening
[n8n] -t Tech/Sessions -p traefik-debugging
Markdown body requirements
- Obsidian-compatible format
- YAML frontmatter at the top (template below)
- Obsidian checkbox syntax
- [ ]for tasks - Fenced code blocks for commands and configs
Frontmatter template
---
project: <unique-project-slug>
type: <type-value>
status: active
path: <path-value>
tags:
- <tag>
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
---
Field reference:
project(read by n8n) — must match the-pslug. Becomes the filename.type(Obsidian only, not read by n8n) — document kind. Standard values:project-plan,session-notes,reference,content-plan,recipe-dev,brand-assets,tech-setup,campaign.status—active,paused,completed,archived.tags— topic tags. Common:pbs,website,wordpress,content,recipe,branding,sunnie,mailerlite,youtube,instagram,sunnies.created/updated— ISO dates (YYYY-MM-DD).path— target folder path in your Obsidian vault, so n8n knows exactly where to drop the file. Use the same value you chose for-tabove (see "Choosing-t").
If a type, tag, or status value doesn't fit the standard options, flag it and ask rather than guessing.