sofzcc commited on
Commit
b837285
·
verified ·
1 Parent(s): d1514bf

Create Knowledge_Base_Structure

Browse files
Files changed (1) hide show
  1. kb/Knowledge_Base_Structure +87 -0
kb/Knowledge_Base_Structure ADDED
@@ -0,0 +1,87 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # 📘 2. Knowledge Base Structure & Information Architecture Best Practices
2
+ ---
3
+
4
+
5
+ ## 1. Create a Logical Hierarchy
6
+
7
+
8
+ Use broad categories, then subcategories:
9
+ - Product / Features
10
+ - Account & Billing
11
+ - Getting Started
12
+ - Troubleshooting
13
+ - Policies
14
+
15
+
16
+ Each article should naturally fit in one place.
17
+
18
+
19
+ ---
20
+
21
+
22
+ ## 2. Use Strong Naming Conventions
23
+
24
+
25
+ Titles should be:
26
+ - **Actionable** (“Set Up Two-Factor Authentication”)
27
+ - **Predictable**
28
+ - **Search-friendly**
29
+
30
+
31
+ Avoid internal jargon.
32
+
33
+
34
+ ---
35
+
36
+
37
+ ## 3. Choose a Taxonomy Style
38
+
39
+
40
+ Successful KBs use:
41
+ - Hierarchical categories
42
+ - Tags
43
+ - Metadata (audience, version, difficulty)
44
+
45
+
46
+ Tags must be purposeful.
47
+
48
+
49
+ ---
50
+
51
+
52
+ ## 4. Avoid Overcategorization
53
+
54
+
55
+ **Rule:** If a category has fewer than **5 articles**, merge it.
56
+
57
+
58
+ Less is more.
59
+
60
+
61
+ ---
62
+
63
+
64
+ ## 5. Build With Search in Mind
65
+
66
+
67
+ Improve findability by:
68
+ - Using natural language
69
+ - Adding synonyms
70
+ - Enhancing metadata
71
+ - Avoiding duplicates
72
+
73
+
74
+ ---
75
+
76
+
77
+ ## 6. Establish Ownership
78
+
79
+
80
+ Assign owners:
81
+ - Support
82
+ - Product
83
+ - Engineering
84
+ - Knowledge Manager
85
+
86
+
87
+ Without ownership, structure deteriorates.