richardk/iso27diy-corp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Organized folders, edited metadata note

Browse source
This commit is contained in:
Richard Kranendonk 2026-06-02 16:49:20 +02:00
parent df038765c0
commit e806e6764b
56 changed files with 113 additions and 55 deletions
Download patch file Download diff file Expand all files Collapse all files

36
metadata/front-matter-for-publications.md
View file

@ -4,43 +4,36 @@ 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"
title: "" # post title
series: "" # series title
series-slug: "" # series title as a slug, 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
channels: # 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
publish-dates: # 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
published-urls: # 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: []
notetype: publication
isotags:
iso-id
audience
---
```
### 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.
---
@ -57,8 +50,3 @@ 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.