General Documentation Database
Purpose: Store all types of documentation in a searchable, organized database.
Schema
| Property |
Type |
Options |
Purpose |
| Title |
title |
- |
Document name |
| Type |
select |
How-To, Concept, Reference, FAQ, Decision, Post-Mortem |
Categorize content type |
| Category |
select |
Engineering, Product, Design, Operations, General |
Organize by department/topic |
| Tags |
multi_select |
- |
Additional categorization (languages, tools, topics) |
| Status |
select |
Draft, In Review, Final, Deprecated |
Track document lifecycle |
| Owner |
people |
- |
Document maintainer |
| Created |
created_time |
- |
Auto-populated creation date |
| Last Updated |
last_edited_time |
- |
Auto-populated last edit |
| Last Reviewed |
date |
- |
Manual review tracking |
Usage
Create pages with properties:
{
"Title": "How to Deploy to Production",
"Type": "How-To",
"Category": "Engineering",
"Tags": "deployment, production, DevOps",
"Status": "Final",
"Owner": [current_user],
"Last Reviewed": "2025-10-01"
}
Views
By Type: Group by Type property
By Category: Group by Category property
Recent Updates: Sort by Last Updated descending
Needs Review: Filter where Last Reviewed > 90 days ago
Draft Docs: Filter where Status = "Draft"
Creating This Database
Use Notion:notion-create-database:
{
"parent": {"page_id": "wiki-page-id"},
"title": [{"text": {"content": "Team Documentation"}}],
"properties": {
"Type": {
"select": {
"options": [
{"name": "How-To", "color": "blue"},
{"name": "Concept", "color": "green"},
{"name": "Reference", "color": "gray"},
{"name": "FAQ", "color": "yellow"}
]
}
},
"Category": {
"select": {
"options": [
{"name": "Engineering", "color": "red"},
{"name": "Product", "color": "purple"},
{"name": "Design", "color": "pink"}
]
}
},
"Tags": {"multi_select": {"options": []}},
"Owner": {"people": {}},
"Status": {
"select": {
"options": [
{"name": "Draft", "color": "gray"},
{"name": "Final", "color": "green"},
{"name": "Deprecated", "color": "red"}
]
}
}
}
}
Best Practices
- Start with this schema - most flexible for general documentation
- Use relations to connect related docs
- Create views for common use cases
- Review properties quarterly - remove unused ones
- Document the schema in database description
- Train team on property usage and conventions
1---2name: documentation-database3description: Imported skill documentation_database from openai4---5
6# General Documentation Database
7
8**Purpose**: Store all types of documentation in a searchable, organized database.
9
10## Schema
11
12| Property | Type | Options | Purpose |
13|----------|------|---------|---------|
14| **Title** | title | - | Document name |
15| **Type** | select | How-To, Concept, Reference, FAQ, Decision, Post-Mortem | Categorize content type |
16| **Category** | select | Engineering, Product, Design, Operations, General | Organize by department/topic |
17| **Tags** | multi_select | - | Additional categorization (languages, tools, topics) |
18| **Status** | select | Draft, In Review, Final, Deprecated | Track document lifecycle |
19| **Owner** | people | - | Document maintainer |
20| **Created** | created_time | - | Auto-populated creation date |
21| **Last Updated** | last_edited_time | - | Auto-populated last edit |
22| **Last Reviewed** | date | - | Manual review tracking |
23
24## Usage
25
26```
27Create pages with properties:
28{
29 "Title": "How to Deploy to Production",
30 "Type": "How-To",
31 "Category": "Engineering",
32 "Tags": "deployment, production, DevOps",
33 "Status": "Final",
34 "Owner": [current_user],
35 "Last Reviewed": "2025-10-01"
36}
37```
38
39## Views
40
41**By Type**: Group by Type property
42**By Category**: Group by Category property
43**Recent Updates**: Sort by Last Updated descending
44**Needs Review**: Filter where Last Reviewed > 90 days ago
45**Draft Docs**: Filter where Status = "Draft"
46
47## Creating This Database
48
49Use `Notion:notion-create-database`:
50
51```javascript
52{
53 "parent": {"page_id": "wiki-page-id"},
54 "title": [{"text": {"content": "Team Documentation"}}],
55 "properties": {
56 "Type": {
57 "select": {
58 "options": [
59 {"name": "How-To", "color": "blue"},
60 {"name": "Concept", "color": "green"},
61 {"name": "Reference", "color": "gray"},
62 {"name": "FAQ", "color": "yellow"}
63 ]
64 }
65 },
66 "Category": {
67 "select": {
68 "options": [
69 {"name": "Engineering", "color": "red"},
70 {"name": "Product", "color": "purple"},
71 {"name": "Design", "color": "pink"}
72 ]
73 }
74 },
75 "Tags": {"multi_select": {"options": []}},
76 "Owner": {"people": {}},
77 "Status": {
78 "select": {
79 "options": [
80 {"name": "Draft", "color": "gray"},
81 {"name": "Final", "color": "green"},
82 {"name": "Deprecated", "color": "red"}
83 ]
84 }
85 }
86 }
87}
88```
89
90## Best Practices
91
921. **Start with this schema** - most flexible for general documentation
932. **Use relations** to connect related docs
943. **Create views** for common use cases
954. **Review properties** quarterly - remove unused ones
965. **Document the schema** in database description
976. **Train team** on property usage and conventions
98
bitwikiorg