feat: create Knowledge Management category (#346)

New category: knowledge-management
- P.A.R.A. Method (moved from documentation)
- todo.txt-flavoured Markdown (moved from development-workflow)

GTD will be added here after #377 merges.

Translations: "Knowledge Management" (EN), "Wissensmanagement" (DE)

Closes #346

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: raifdmueller

docs/anchors/para-method.adoc

@@ -1,5 +1,5 @@
 = P.A.R.A. Method
-:categories: documentation
+:categories: knowledge-management
 :roles: software-developer, team-lead, technical-writer, educator
 :related: diataxis-framework, todotxt-flavoured-markdown
 :proponents: Tiago Forte

docs/anchors/para-method.de.adoc

@@ -1,5 +1,5 @@
 = P.A.R.A. Method
-:categories: documentation
+:categories: knowledge-management
 :roles: software-developer, team-lead, technical-writer, educator
 :related: diataxis-framework, todotxt-flavoured-markdown
 :proponents: Tiago Forte

docs/anchors/todotxt-flavoured-markdown.adoc

@@ -1,5 +1,5 @@
 = todo.txt-flavoured Markdown
-:categories: development-workflow
+:categories: knowledge-management
 :roles: software-developer, team-lead, technical-writer
 :proponents: Combines GitHub-flavoured Markdown task lists with Gina Trapani's todo.txt format
 :tier: 3

docs/anchors/todotxt-flavoured-markdown.de.adoc

@@ -1,5 +1,5 @@
 = todo.txt-flavoured Markdown
-:categories: development-workflow
+:categories: knowledge-management
 :roles: software-developer, team-lead, technical-writer
 :proponents: Combines GitHub-flavoured Markdown task lists with Gina Trapani's todo.txt format
 

website/public/data/anchors.json

@@ -1965,6 +1965,35 @@
     "filePath": "docs/anchors/owasp-top-10.adoc",
     "tier": 3
   },
+  {
+    "id": "para-method",
+    "title": "P.A.R.A. Method",
+    "categories": [
+      "knowledge-management"
+    ],
+    "roles": [
+      "software-developer",
+      "team-lead",
+      "technical-writer",
+      "educator"
+    ],
+    "related": [
+      "diataxis-framework",
+      "todotxt-flavoured-markdown"
+    ],
+    "proponents": [
+      "Tiago Forte"
+    ],
+    "tags": [
+      "knowledge-management",
+      "personal-productivity",
+      "note-taking",
+      "organization",
+      "second-brain"
+    ],
+    "filePath": "docs/anchors/para-method.adoc",
+    "tier": 3
+  },
   {
     "id": "pert",
     "title": "PERT",
@@ -2129,35 +2158,6 @@
     "filePath": "docs/anchors/pugh-matrix.adoc",
     "tier": 2
   },
-  {
-    "id": "para-method",
-    "title": "P.A.R.A. Method",
-    "categories": [
-      "documentation"
-    ],
-    "roles": [
-      "software-developer",
-      "team-lead",
-      "technical-writer",
-      "educator"
-    ],
-    "related": [
-      "diataxis-framework",
-      "todotxt-flavoured-markdown"
-    ],
-    "proponents": [
-      "Tiago Forte"
-    ],
-    "tags": [
-      "knowledge-management",
-      "personal-productivity",
-      "note-taking",
-      "organization",
-      "second-brain"
-    ],
-    "filePath": "docs/anchors/para-method.adoc",
-    "tier": 3
-  },
   {
     "id": "pyramid-principle",
     "title": "Pyramid Principle according to Barbara Minto",
@@ -2796,7 +2796,7 @@
     "id": "todotxt-flavoured-markdown",
     "title": "todo.txt-flavoured Markdown",
     "categories": [
-      "development-workflow"
+      "knowledge-management"
     ],
     "roles": [
       "software-developer",
@@ -2922,4 +2922,4 @@
     "filePath": "docs/anchors/yagni.adoc",
     "tier": 1
   }
-]
+]

website/public/data/categories.json

@@ -41,6 +41,7 @@
       "gof-strategy-pattern",
       "gof-template-method-pattern",
       "gof-visitor-pattern",
+      "grasp",
       "kiss-principle",
       "solid-dip",
       "solid-isp",
@@ -65,8 +66,7 @@
       "regulated-environment",
       "semantic-versioning",
       "sota",
-      "timtowtdi",
-      "todotxt-flavoured-markdown"
+      "timtowtdi"
     ]
   },
   {
@@ -84,6 +84,14 @@
       "docs-as-code"
     ]
   },
+  {
+    "id": "knowledge-management",
+    "name": "Knowledge Management",
+    "anchors": [
+      "para-method",
+      "todotxt-flavoured-markdown"
+    ]
+  },
   {
     "id": "meta",
     "name": "Meta",

website/public/data/metadata.json

@@ -1,15 +1,15 @@
 {
-  "generatedAt": "2026-03-26T09:31:40.107Z",
+  "generatedAt": "2026-03-27T08:59:25.567Z",
   "version": "1.0.0",
   "counts": {
-    "anchors": 107,
-    "categories": 12,
+    "anchors": 111,
+    "categories": 13,
     "roles": 12
   },
   "statistics": {
-    "averageRolesPerAnchor": "3.11",
+    "averageRolesPerAnchor": "3.14",
     "averageCategoriesPerAnchor": "1.01",
-    "anchorsWithTags": 67,
-    "anchorsWithRelated": 38
+    "anchorsWithTags": 71,
+    "anchorsWithRelated": 42
   }
 }

website/src/translations/de.json

@@ -40,6 +40,7 @@
   "categories.development-workflow": "Entwicklungs-Workflow",
   "categories.dialogue-interaction": "Dialog & Interaktionsmuster",
   "categories.documentation": "Dokumentationspraktiken",
+  "categories.knowledge-management": "Wissensmanagement",
   "categories.meta": "Meta (Repository & Katalog)",
   "categories.problem-solving": "Problemlösungs-Methoden",
   "categories.requirements-engineering": "Requirements Engineering",

website/src/translations/en.json

@@ -40,6 +40,7 @@
   "categories.development-workflow": "Development Workflow",
   "categories.dialogue-interaction": "Dialogue & Interaction Patterns",
   "categories.documentation": "Documentation Practices",
+  "categories.knowledge-management": "Knowledge Management",
   "categories.meta": "Meta (Repository & Catalog)",
   "categories.problem-solving": "Problem-Solving Methodologies",
   "categories.requirements-engineering": "Requirements Engineering",