vault-context

Vault structure uses separate directories for each content type: blog/ for posts, daily/ for notes, projects/ for work, reference/ for materials, archive/ for old content, templates/ for reusable formats, and scripts/ for automation. This separation enables consistent file naming, metadata conventions, and workflow automation across your vault.

Use YAML frontmatter at the top of each file for metadata, follow one-idea-per-file conventions, and link between files using Markdown syntax to create a connected reference system. The vault enforces consistent linking guidelines and frontmatter structure to maintain a source of truth across blog, daily notes, projects, and reference material.

The weekly writing pipeline structures tasks Monday through Sunday, coordinating daily notes, blog drafts, project updates, and archiving cycles. Make commands automate these recurring tasks, and templates standardize formatting so your entire workflow stays consistent week to week.

Yes. Make commands handle routine vault tasks like archiving old content, organizing files by date or category, and triggering pipeline steps. The vault provides a reference guide to common Make commands that integrate with your directory structure and file-naming rules.

The vault enforces file-naming rules, directory layout standards, and archiving protocols to keep content organized and discoverable. Following these conventions ensures compatibility with Make automation, internal linking, templates, and weekly workflows across all vault directories.