Organized folders, edited metadata note

Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business drivers.md

@@ -1,3 +1,3 @@
-- [Perverse prikkels in de normindustrie](../../../../../Marketing/content/Scratch%20file/Perverse%20prikkels%20in%20de%20normindustrie.md)
+- [Perverse prikkels in de normindustrie](../../../../../Marketing/publications/Scratch%20file/Perverse%20prikkels%20in%20de%20normindustrie.md)
-- [GRC software is geschreven voor domeindeskundigen](../../../../../Marketing/content/Scratch%20file/GRC%20software%20is%20geschreven%20voor%20domeindeskundigen.md)
+- [GRC software is geschreven voor domeindeskundigen](../../../../../Marketing/publications/Scratch%20file/GRC%20software%20is%20geschreven%20voor%20domeindeskundigen.md)
 - [Problems solved 1](../../../../Sparks/Problems%20solved%201.md)

Corpus/Standards/ISO27x/legacy/iso27DIY mk I/ISO27DIY Business model.md

@@ -1,6 +1,6 @@
 Child notes:
 - [Blurbs](../../../../Sparks/Blurbs.md)
-- [Toegevoegde waarde van ISO27DIY](../../../../../Marketing/content/Scratch%20file/Toegevoegde%20waarde%20van%20ISO27DIY.md)
+- [Toegevoegde waarde van ISO27DIY](../../../../../Marketing/publications/Scratch%20file/Toegevoegde%20waarde%20van%20ISO27DIY.md)
 - [Friendly targets](../../../../../../💡Permanent%20ideas/Friendly%20targets.md)
 - [Possible Colabs](../../../../../AuditGlue/Possible%20Colabs.md)
 - [List of possible partners](../../../../../AuditGlue/List%20of%20possible%20partners.md)

Corpus/Standards/other/Privacy frameworks list.md

@@ -5,6 +5,6 @@
 [Privacy in ISO 27k](../ISO27x/Privacy%20in%20ISO%2027k.md)
 
 Related:
-- [Privacy protection in Databases](../../../Marketing/content/Scratch%20file/Privacy%20protection%20in%20Databases.md)
+- [Privacy protection in Databases](../../../Marketing/publications/Scratch%20file/Privacy%20protection%20in%20Databases.md)
 - [ISO 27001 A.18.1.4 Privacy and protection of personally identifiable information](../ISO27x/legacy/ISO%2027001%202013/ISO%2027001%20A.18.1.4%20Privacy%20and%20protection%20of%20personally%20identifiable%20information.md)
 

marketing/content/eBook-Audit/.claude/settings.local.json

@@ -1,7 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "Bash(bash build.sh)"
-    ]
-  }
-}

marketing/publications/Scratch file/startproblemen of vastloper.md

@@ -0,0 +1,15 @@
+
+Vastgelopen met je ISO 27001 implementatie? Komt je SIO 27001 implementatie niet van de grond? Ik kan je helpen
+
+Wie moet je erbij betrekken?
+Wie moet je verantwoordelijk maken?
+Hoeveel tijd moet je vrijmaken?
+Welke tooling is nodig
+Moet jhe een consultant inhuren ?
+Wie maak je projectmanager?
+Waar moet je beginnen?
+Moet je alle controls implementeren?
+Loopt de boel niet vast in eindeloze procedures?
+Wordt het niet veel te bureacratisch
+Mensen szien de noodzaak niet
+IT werkt tegen

marketing/publications/posts/ZZP/For Leadership/s02p05nl - De Cbw is geen project.md

@@ -1,3 +1,5 @@
+`posted on 1 June 2026 15:31 CEST to LinkedIn personal stream`
+
 # De Cbw is geen project!
 
 Cbw compliance is geen project, maar vraagt van jou als bestuurder voortdurende aandacht.

metadata/corpus-metadata.md

@@ -1,37 +1,97 @@
 # Corpus Metadata
 
-- All notes in this Obsidian vault need metadata. 
+- All notes in `/Users/rico/Library/Mobile Documents/iCloud~md~obsidian/Documents/MyVault/iso27diy-corp/Corpus` need metadata. 
 - These metadata need to follow the [obsidian-front-matter-syntax](obsidian-front-matter-syntax.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)
+- In this Corpus we use General properties (every note should have them) and specific properties (depending on the kind of note, which can be inferred from the `notetype` property, see below).
 
-## General metadata
+## General properties
 
-### Notetype
+**Notetype**
 
 The `notetype` field will have one of the following values:
+
 - `guide`: guided, hands-on lessons, learning by doing, interactive lessons
 - `explanation`: background and context to the standards, paraphrases of the original standard texts, opinion, discussion, underlying principles, interpretation
 - `application`: steps to solve a specific, real-world problem. Implementing the standard in real world environments, implementation aids, implementation examples, templates, etc.
-- `reference`: for original standard texts, dictionaries, terms and definitions.
+- `reference`: secondary sources of information, like original standard texts, dictionaries, terms and definitions.
+- `publication`: for content created by TSW for publication, e.g. articles, eBooks, social media posts.
 - `other`: for all notes that, by there content, cannot be placed in one for the previous categories.
+- `iso27diyGIS`: notes that belong to the ISO27DIY Guided Implementation System (GIS).
 
-Note:
+**Language**
-- Notes in the iso27DIY-gis/guide folder and subfolders are typically of the `guide` type.
-- Notes in iso27DIY-gis/reference and subfolders are typically of the `explanation` or `application` type.
 
-### Language
+- For the `language` property we use the language code as defined in ISO 639-1.
-For the `language` property we use the language code as defined in ISO 639-1.
+
+**Isotags**
 
-### Status
-As of yet, the only value defined for the `status` property is `active`.
-## Isotags
 The property `isotags`, of type list, allows any note to be linked to clauses and controls of the ISO 27001 / ISO 27002 standard, by the `id` property of the Original Standard Texts, found in `Corpus/Standards/ISO27x/OST/27001/EN` and `/Corpus/Standards/ISO27x/OST/27002/EN`, respectively.
-For example, a note that needs to be linked to ISO 27001 clause 5.2 Policy, will get a value of C.5.2 added to its `isotags` list. Likewise, a note that needs to be linked to ISO 27002 control 5.15 Access control, will get a value of A.5.15 added to its `isotags` list.
+
-## Metadata for ISO 27001 and 27002 Original Standard Texts
+For example, a note that needs to be linked to ISO 27001 clause 5.2 Policy, will get a value of `C.5.2` added to its `isotags` list. Likewise, a note that needs to be linked to ISO 27002 control 5.15 Access control, will get a value of `A.5.15` added to its `isotags` list.
-- The original texts of the ISO 27001 and ISO 27002 standards can be found in the OST folder and subfolders. 
+
-- These notes are tagged with “sourcetext”. 
+## Properties for ISO 27001 and 27002 Original Standard Texts
-- 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`. 
+Original Standard Texts are found in `Corpus/Standards/ISO27x/OST/` .
-- For the possible values of these properties, see [themes-and-attributes-in-iso-27002](themes-and-attributes-in-iso-27002.md).
+
+*Important: the body of these notes must never be changed!*
+
+OST notes inherit the general properties, and also have the following properties:
+
+-  `status`: as of yet, the only value defined for the property is `active`. I foresee a `superseded` or `replaced` status for later.
+- `sourcetext`: the standard name and version, e.g. `iso27001:en:2022`
+
+The OST/27002 have specific properties deduced from chapter 4 of the standard ("Themes and Attributes"). They are:
+- `theme`
+- `control_type`
+- `information_security_properties`
+- `cybersecurity_concepts`
+- `operational_capabilities`
+- `security_domains`. 
+
+For the possible values of these properties, see [themes-and-attributes-in-iso-27002](themes-and-attributes-in-iso-27002.md).
+
+## Properties for the ISO27DIY Guided Implementation System
+
+- Notes in the `iso27DIY-gis` folder and subfolders are of `notetype`  `iso27diyGIS`.
+- Notes in the `iso27DIY-gis/guide` subfolder ...
+- Notes in the `iso27DIY-gis/reference` subfolder ...
+
+## Properties for Publications
+
+- publications can be found in `iso27diy-corp/Marketing/publications` and are of `notetype` `publication`
+
+
+```
+---
+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"
+channels:            # list — a post can go to multiple channels
+  - linkedin
+  - newsletter
+  - blog
+status: draft        # draft | ready | scheduled | published
+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-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
+
+---
+```
+
+
 

metadata/front-matter-for-publications.md

@@ -4,43 +4,36 @@ From [claude chat](https://claude.ai/share/614ce436-307d-4740-a79f-40225461e743)
 
 ```
 ---
-title: ""
+title: ""            # post title
-series: ""           # slug for the series this belongs to, e.g. "access-control-basics"
+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.