From 5906aa163f07e4f0fc1433b173bd8775581ebf12 Mon Sep 17 00:00:00 2001 From: Richard Kranendonk Date: Mon, 1 Jun 2026 22:35:10 +0200 Subject: [PATCH] moved a folder --- .../Content Factory Implementation.md | 2 +- {Corpus => metadata}/Corpus overview notes.md | 0 ...adata - ISO 27002 Themes and Attributes.md | 0 .../Obsidian Front Matter Syntax.md | 0 .../_Corpus-metadata.md | 4 +- metadata/front-matter-for-marketing-posts.md | 64 +++++++++++++++++++ 6 files changed, 67 insertions(+), 3 deletions(-) rename {Corpus => metadata}/Corpus overview notes.md (100%) rename {Corpus => metadata}/Metadata - ISO 27002 Themes and Attributes.md (100%) rename {Corpus => metadata}/Obsidian Front Matter Syntax.md (100%) rename {Corpus/Standards => metadata}/_Corpus-metadata.md (94%) create mode 100644 metadata/front-matter-for-marketing-posts.md diff --git a/Content Factory/Content Factory Implementation.md b/Content Factory/Content Factory Implementation.md index 1651fa4..b1c4ce8 100644 --- a/Content Factory/Content Factory Implementation.md +++ b/Content Factory/Content Factory Implementation.md @@ -17,7 +17,7 @@ See [PROJECT - Five Agents](PROJECT%20-%20Five%20Agents.md) for role description - Create a single short Corpus Index Note with a list of all overview notes, with a one-line description of what they cover. - Upload the Corpus Index Note and all Overview Notes to each agent Project. Claude will read the ones it needs and ignore the rest. -See [Corpus overview notes](../Corpus/Corpus%20overview%20notes.md). +See [Corpus overview notes](../metadata/Corpus%20overview%20notes.md). **3. Prepare and maintain a log** diff --git a/Corpus/Corpus overview notes.md b/metadata/Corpus overview notes.md similarity index 100% rename from Corpus/Corpus overview notes.md rename to metadata/Corpus overview notes.md diff --git a/Corpus/Metadata - ISO 27002 Themes and Attributes.md b/metadata/Metadata - ISO 27002 Themes and Attributes.md similarity index 100% rename from Corpus/Metadata - ISO 27002 Themes and Attributes.md rename to metadata/Metadata - ISO 27002 Themes and Attributes.md diff --git a/Corpus/Obsidian Front Matter Syntax.md b/metadata/Obsidian Front Matter Syntax.md similarity index 100% rename from Corpus/Obsidian Front Matter Syntax.md rename to metadata/Obsidian Front Matter Syntax.md diff --git a/Corpus/Standards/_Corpus-metadata.md b/metadata/_Corpus-metadata.md similarity index 94% rename from Corpus/Standards/_Corpus-metadata.md rename to metadata/_Corpus-metadata.md index d4350b9..beed4b1 100644 --- a/Corpus/Standards/_Corpus-metadata.md +++ b/metadata/_Corpus-metadata.md @@ -1,7 +1,7 @@ # Corpus Metadata - All notes in this Obsidian vault need metadata. -- These metadata need to follow the [Obsidian Front Matter Syntax](../Obsidian%20Front%20Matter%20Syntax.md). +- These metadata need to follow the [Obsidian Front Matter Syntax](Obsidian%20Front%20Matter%20Syntax.md). - Obsidian calls metadata variables 'Properties' - In this Corpus we use General properties (every note should have them) and Specific properties (depending on the kind of note, can be inferred from other properties) @@ -33,5 +33,5 @@ For example, a note that needs to be linked to ISO 27001 clause 5.2 Policy, will - These notes are tagged with “sourcetext”. - The body of these notes must never be changed! - Specific properties for ISO 27002 OST notes are deduced from chapter 4 of the standard ("Themes and Attributes"). They are: `theme`, `control_type`, `information_security_properties`, `cybersecurity_concepts`, `operational_capabilities`, and `security_domains`. -- For the possible values of these properties, see [Metadata - ISO 27002 Themes and Attributes](../Metadata%20-%20ISO%2027002%20Themes%20and%20Attributes.md). +- For the possible values of these properties, see [Metadata - ISO 27002 Themes and Attributes](Metadata%20-%20ISO%2027002%20Themes%20and%20Attributes.md). diff --git a/metadata/front-matter-for-marketing-posts.md b/metadata/front-matter-for-marketing-posts.md new file mode 100644 index 0000000..7d4b2c6 --- /dev/null +++ b/metadata/front-matter-for-marketing-posts.md @@ -0,0 +1,64 @@ +# Front matter for marketing posts + +From [claude chat](https://claude.ai/share/614ce436-307d-4740-a79f-40225461e743) + +``` +--- +title: "" +series: "" # slug for the series this belongs to, e.g. "access-control-basics" +series-part: 1 # position within the series; omit if standalone +theme: "" # broader topic cluster, e.g. "ISO27001 myths" +channel: # list — a post can go to multiple channels + - linkedin + - newsletter + - blog +status: draft # draft | ready | scheduled | published +publish-date: # ISO 8601, e.g. 2026-06-10; can be a list if channels differ + linkedin: 2026-06-10 + newsletter: 2026-06-17 + blog: 2026-06-17 +published-url: # fill in after publishing; one per channel + linkedin: "" + blog: "" +content-type: "" # post | article | newsletter-section | thread +source-notes: # vault notes this was drawn from + - "[[path/to/note]]" +tags: [] +--- +``` + +### Folder structure to go with it + +``` +Content Factory/ + Publishing/ + Series/ + access-control-basics/ + part-1.md + part-2.md + Standalone/ + some-one-off-post.md +``` + +Or if you prefer tag-based grouping over folders, skip the subfolders and rely on `series` + Dataview to surface series views. + +--- + +### Dataview query to check what's scheduled + +dataview + +```dataview +TABLE series, channel, publish-date, status +FROM "Content Factory/Publishing" +WHERE status != "published" +SORT publish-date ASC +``` + +--- + +### Issues to flag + +- If you're already using front matter on content notes, check for conflicts with any existing `status` or `tags` fields before rolling this out. +- `published-url` will stay empty a lot. That's fine — it's a record, not a requirement. +- If posts get repurposed significantly between channels (not just reformatted), they probably deserve separate notes rather than one note with multiple channels listed. \ No newline at end of file