Table of Contents
Generated from docs/reference/page-types.md at v10.1.0 – edit the repository, not this wiki.
Page types
Every page type the stack ships for kb/: what it is for, where its pages are written, its
subtypes and its required frontmatter fields, generated from the type-specs under types/ and
their schemas.
This page describes the stack's shipped defaults. An instance adopts these type-specs from their
.template and may change them, or add types of its own; tools/wikitool types list and
tools/wikitool types describe <type> show what this instance has.
Contents
comparison
Structured type for comparison pages that set several entities or approaches against one another
- Written to:
kb/comparisons/
Required fields
type- stringcreated- stringentities- arraysummary- string
concept
Base type for concept pages - architectures, patterns, protocols, workflows, decisions or problems
- Written to:
kb/concepts/<subtype directory>/
Subtypes (field concept_type)
| Value | Written to | Index section |
|---|---|---|
architecture |
kb/concepts/architectures/ |
Architekturen |
pattern |
kb/concepts/patterns/ |
Muster |
protocol |
kb/concepts/protocols/ |
Protokolle |
workflow |
kb/concepts/workflows/ |
Abläufe |
decision |
kb/concepts/decisions/ |
Entscheidungen |
problem |
kb/concepts/problems/ |
Problemstellungen |
Required fields
type- stringconcept_type- string, one ofarchitecture,pattern,protocol,workflow,decision,problemcreated- stringmodified- stringprovenance- string, one ofsourced,general,mixedsummary- string
entity
Base type for entity pages - codebases, systems, tools, technologies, people or organizations
- Written to:
kb/entities/<subtype directory>/
Subtypes (field entity_type)
| Value | Written to | Index section |
|---|---|---|
codebase |
kb/entities/codebases/ |
Codebasen |
system |
kb/entities/systems/ |
Systeme |
tool |
kb/entities/tools/ |
Werkzeuge |
technology |
kb/entities/technologies/ |
Technologien |
person |
kb/entities/people/ |
Personen |
organization |
kb/entities/organizations/ |
Organisationen |
Required fields
type- stringentity_type- string, one ofcodebase,system,tool,technology,person,organizationcreated- stringmodified- stringprovenance- string, one ofsourced,general,mixedsummary- string
project
Structured type for a committed initiative (a GTD project) - goal, participants, durable status, open loops
- Written to:
kb/gtd/<subtype directory>/
Subtypes (field responsibility)
| Value | Written to | Index section |
|---|---|---|
haus |
kb/gtd/haus/ |
Haus |
finanzen |
kb/gtd/finanzen/ |
Finanzen |
technik |
kb/gtd/technik/ |
Technik |
Required fields
type- stringstate- string, one ofactive,dormant,completed,abandonedresponsibility- string, one ofhaus,finanzen,technikcreated- stringmodified- stringprovenance- string, one ofsourced,general,mixedsummary- string
source
Structured type for source pages that record and summarize ingested raw material
- Written to:
kb/sources/<subtype directory>/ - Title prefix:
Source -
Subtypes (field source_type)
| Value | Written to | Index section |
|---|---|---|
transcript |
kb/sources/transcripts/ |
Transkripte |
analysis |
kb/sources/analyses/ |
Analysen |
article |
kb/sources/articles/ |
Artikel |
document |
kb/sources/documents/ |
Dokumente |
notes |
kb/sources/notes/ |
Notizen |
tracker |
kb/sources/trackers/ |
Tracker-Exporte |
unclassified |
kb/sources/unclassified/ |
Unklassifiziert |
Required fields
type- stringsource_type- string, one oftranscript,analysis,article,document,notes,tracker,unclassifiedauthor- stringraw_files- arraydate- stringsummary- string
- Chemenu - Personal IT Knowledge Base
- Install a Chemenu instance
- Tutorials
- How-to guides
- Back up to a synced folder
- Browse the wiki in Obsidian
- Capture documentation from a git repository
- Collect documents from a synced folder
- Export guidelines to captured repositories
- Export to a synced folder
- Fetch pages behind a login
- Ingest a source
- Maintain the wiki
- Query the wiki
- Run the weekly review
- Set up the MCP read server
- Trace and score agent sessions
- Troubleshoot an instance
- Update an instance
- Use 1Password for settings
- Write a site handler
- Reference
- Explanation
- Architecture
- Configuration tiers
- Why knowledge and commitments are two layers
- Language Boundaries
- Choosing a Claude Code model and effort level
- Ownership and Templates
- Why the pipeline has four stages
- Telemetry and evaluation
- Why the stack version splits compatibility from migration
- Why gates are code
- Dev