Decision tree

# ZajLibrary — authoring & site docs

You are a **ZajLibrary documentation assistant**. This is a meta page about the library itself — you help the user author or audit pages per the writing-style and component rules.

**Mission:** Help the user author or audit ZajLibrary pages per the writing-style and component rules referenced below.

## Metadata
- title: Decision tree
- url: https://library.zajapps.com/zajlibrary/authoring/content-system/resources/reference/content-architecture/decision-tree/
- shelf: Resources
- doc_type: site documentation
- status: current
- kind: reference
- category: zajlibrary
- subcategory: authoring
- topic: content-system
- description: The routing tree for deciding where a new ZajLibrary item belongs.
- tags: system-docs, decision-tree, taxonomy

## Authoring rules
- Help the user author or audit ZajLibrary pages per the writing-style and component rules referenced here.
- Prefer Starlight components and the visuals/warrant-test contract over raw HTML or undiagrammed walls of text.
- Cite the specific rule or section you are applying.

---

# Decision tree

Use this when a new file, folder, note, export, or generated artifact lands in the library. Ask the questions in order and stop at the first clear match.

First pick or create the topic home (`category` / `subcategory` / `topic`). Then pick the shelf and kind inside that topic. `collection` is optional legacy metadata for prompts and old grouping language; it is not a shelf or an active route family.

## The routing tree

```txt
New content item

├── Is it an entity to browse?
│   └── Directory
│       ├── Tool
│       ├── Skill
│       ├── Vendor
│       ├── Product
│       ├── Person
│       └── Link
│
├── Is it reusable, copyable, fillable, downloadable, or quick lookup?
│   └── Resources
│       ├── Template
│       ├── Kit
│       ├── Cheat sheet
│       ├── Reference
│       ├── Glossary
│       └── Prompt pack
│
├── Is it for building, operating, or verifying something?
│   └── Build & Create
│       ├── Playbook
│       ├── Blueprint
│       ├── SOP
│       ├── Runbook
│       └── Checklist
│
└── Is it for learning, understanding, or preserving evidence?
    └── Learn & Understand
        ├── Handbook
        ├── Guide
        ├── Concept / Explainer
        ├── Research
        └── Case study
```

## Fast questions

| Question | If yes |
| --- | --- |
| "Do I browse this as an entity?" | Directory |
| "Do I copy, fill, download, or glance at this?" | Resources |
| "Do I use this to build, run, or verify work?" | Build & Create |
| "Do I read this to understand or learn?" | Learn & Understand |

## Common routing examples

| Item | Shelf | Kind |
| --- | --- | --- |
| "Setup New Laravel/CodeCanyon" | Build & Create | Playbook |
| "Production deploy exact commands" | Build & Create | Runbook |
| "Vercel Git authorization steps" | Learn & Understand | Guide |
| "ZajLibrary content model" | Build & Create or System docs | Blueprint / concept |
| "Best Starlight plugins research" | Learn & Understand | Research |
| "AGENTS.md starter file" | Resources | Template |
| "CodeCanyon AI System bundle" | Resources | Kit |
| "Vercel project IDs" | Resources | Reference |
| "Starlight command crib sheet" | Resources | Cheat sheet |
| "Cloudflare vendor card" | Directory | Vendor |

## When two labels seem valid

Pick the label that matches the reader's next action.

```txt
Read to learn      → Guide / Handbook / Research
Follow to execute  → Playbook / SOP / Runbook
Copy to reuse      → Template / Kit
Glance to recall   → Cheat sheet / Reference
Browse as entity   → Directory
```

Then confirm metadata:

```txt
Broad family      → category
Narrow area       → subcategory
Exact topic       → topic
Legacy bundle     → collection (optional)
Cross-cut filters → tags
```

# Decision tree

> Source: https://library.zajapps.com/zajlibrary/authoring/content-system/resources/reference/content-architecture/decision-tree/

Use this when a new file, folder, note, export, or generated artifact lands in the library. Ask the questions in order and stop at the first clear match.

First pick or create the topic home (`category` / `subcategory` / `topic`). Then pick the shelf and kind inside that topic. `collection` is optional legacy metadata for prompts and old grouping language; it is not a shelf or an active route family.

## The routing tree

```txt
New content item

├── Is it an entity to browse?
│   └── Directory
│       ├── Tool
│       ├── Skill
│       ├── Vendor
│       ├── Product
│       ├── Person
│       └── Link
│
├── Is it reusable, copyable, fillable, downloadable, or quick lookup?
│   └── Resources
│       ├── Template
│       ├── Kit
│       ├── Cheat sheet
│       ├── Reference
│       ├── Glossary
│       └── Prompt pack
│
├── Is it for building, operating, or verifying something?
│   └── Build & Create
│       ├── Playbook
│       ├── Blueprint
│       ├── SOP
│       ├── Runbook
│       └── Checklist
│
└── Is it for learning, understanding, or preserving evidence?
    └── Learn & Understand
        ├── Handbook
        ├── Guide
        ├── Concept / Explainer
        ├── Research
        └── Case study
```

## Fast questions

| Question | If yes |
| --- | --- |
| "Do I browse this as an entity?" | Directory |
| "Do I copy, fill, download, or glance at this?" | Resources |
| "Do I use this to build, run, or verify work?" | Build & Create |
| "Do I read this to understand or learn?" | Learn & Understand |

## Common routing examples

| Item | Shelf | Kind |
| --- | --- | --- |
| "Setup New Laravel/CodeCanyon" | Build & Create | Playbook |
| "Production deploy exact commands" | Build & Create | Runbook |
| "Vercel Git authorization steps" | Learn & Understand | Guide |
| "ZajLibrary content model" | Build & Create or System docs | Blueprint / concept |
| "Best Starlight plugins research" | Learn & Understand | Research |
| "AGENTS.md starter file" | Resources | Template |
| "CodeCanyon AI System bundle" | Resources | Kit |
| "Vercel project IDs" | Resources | Reference |
| "Starlight command crib sheet" | Resources | Cheat sheet |
| "Cloudflare vendor card" | Directory | Vendor |

## When two labels seem valid

Pick the label that matches the reader's next action.

```txt
Read to learn      → Guide / Handbook / Research
Follow to execute  → Playbook / SOP / Runbook
Copy to reuse      → Template / Kit
Glance to recall   → Cheat sheet / Reference
Browse as entity   → Directory
```

Then confirm metadata:

```txt
Broad family      → category
Narrow area       → subcategory
Exact topic       → topic
Legacy bundle     → collection (optional)
Cross-cut filters → tags
```

Use this when a new file, folder, note, export, or generated artifact lands in the library. Ask the questions in order and stop at the first clear match.

First pick or create the topic home (category / subcategory / topic). Then pick the shelf and kind inside that topic. collection is optional legacy metadata for prompts and old grouping language; it is not a shelf or an active route family.

The routing tree

New content item

├── Is it an entity to browse?
│   └── Directory
│       ├── Tool
│       ├── Skill
│       ├── Vendor
│       ├── Product
│       ├── Person
│       └── Link
│
├── Is it reusable, copyable, fillable, downloadable, or quick lookup?
│   └── Resources
│       ├── Template
│       ├── Kit
│       ├── Cheat sheet
│       ├── Reference
│       ├── Glossary
│       └── Prompt pack
│
├── Is it for building, operating, or verifying something?
│   └── Build & Create
│       ├── Playbook
│       ├── Blueprint
│       ├── SOP
│       ├── Runbook
│       └── Checklist
│
└── Is it for learning, understanding, or preserving evidence?
    └── Learn & Understand
        ├── Handbook
        ├── Guide
        ├── Concept / Explainer
        ├── Research
        └── Case study

Fast questions

Question	If yes
”Do I browse this as an entity?”	Directory
”Do I copy, fill, download, or glance at this?”	Resources
”Do I use this to build, run, or verify work?”	Build & Create
”Do I read this to understand or learn?”	Learn & Understand

Common routing examples

Item	Shelf	Kind
”Setup New Laravel/CodeCanyon”	Build & Create	Playbook
”Production deploy exact commands”	Build & Create	Runbook
”Vercel Git authorization steps”	Learn & Understand	Guide
”ZajLibrary content model”	Build & Create or System docs	Blueprint / concept
”Best Starlight plugins research”	Learn & Understand	Research
”AGENTS.md starter file”	Resources	Template
”CodeCanyon AI System bundle”	Resources	Kit
”Vercel project IDs”	Resources	Reference
”Starlight command crib sheet”	Resources	Cheat sheet
”Cloudflare vendor card”	Directory	Vendor

When two labels seem valid

Pick the label that matches the reader’s next action.

Read to learn      → Guide / Handbook / Research
Follow to execute  → Playbook / SOP / Runbook
Copy to reuse      → Template / Kit
Glance to recall   → Cheat sheet / Reference
Browse as entity   → Directory

Then confirm metadata:

Broad family      → category
Narrow area       → subcategory
Exact topic       → topic
Legacy bundle     → collection (optional)
Cross-cut filters → tags

# ZajLibrary — authoring & site docs

You are a **ZajLibrary documentation assistant**. This is a meta page about the library itself — you help the user author or audit pages per the writing-style and component rules.

**Mission:** Help the user author or audit ZajLibrary pages per the writing-style and component rules referenced below.

## Metadata
- title: Decision tree
- url: https://library.zajapps.com/zajlibrary/authoring/content-system/resources/reference/content-architecture/decision-tree/
- shelf: Resources
- doc_type: site documentation
- status: current
- kind: reference
- category: zajlibrary
- subcategory: authoring
- topic: content-system
- description: The routing tree for deciding where a new ZajLibrary item belongs.
- tags: system-docs, decision-tree, taxonomy

## Authoring rules
- Help the user author or audit ZajLibrary pages per the writing-style and component rules referenced here.
- Prefer Starlight components and the visuals/warrant-test contract over raw HTML or undiagrammed walls of text.
- Cite the specific rule or section you are applying.

---

# Decision tree

Use this when a new file, folder, note, export, or generated artifact lands in the library. Ask the questions in order and stop at the first clear match.

First pick or create the topic home (`category` / `subcategory` / `topic`). Then pick the shelf and kind inside that topic. `collection` is optional legacy metadata for prompts and old grouping language; it is not a shelf or an active route family.

## The routing tree

```txt
New content item

├── Is it an entity to browse?
│   └── Directory
│       ├── Tool
│       ├── Skill
│       ├── Vendor
│       ├── Product
│       ├── Person
│       └── Link
│
├── Is it reusable, copyable, fillable, downloadable, or quick lookup?
│   └── Resources
│       ├── Template
│       ├── Kit
│       ├── Cheat sheet
│       ├── Reference
│       ├── Glossary
│       └── Prompt pack
│
├── Is it for building, operating, or verifying something?
│   └── Build & Create
│       ├── Playbook
│       ├── Blueprint
│       ├── SOP
│       ├── Runbook
│       └── Checklist
│
└── Is it for learning, understanding, or preserving evidence?
    └── Learn & Understand
        ├── Handbook
        ├── Guide
        ├── Concept / Explainer
        ├── Research
        └── Case study
```

## Fast questions

| Question | If yes |
| --- | --- |
| "Do I browse this as an entity?" | Directory |
| "Do I copy, fill, download, or glance at this?" | Resources |
| "Do I use this to build, run, or verify work?" | Build & Create |
| "Do I read this to understand or learn?" | Learn & Understand |

## Common routing examples

| Item | Shelf | Kind |
| --- | --- | --- |
| "Setup New Laravel/CodeCanyon" | Build & Create | Playbook |
| "Production deploy exact commands" | Build & Create | Runbook |
| "Vercel Git authorization steps" | Learn & Understand | Guide |
| "ZajLibrary content model" | Build & Create or System docs | Blueprint / concept |
| "Best Starlight plugins research" | Learn & Understand | Research |
| "AGENTS.md starter file" | Resources | Template |
| "CodeCanyon AI System bundle" | Resources | Kit |
| "Vercel project IDs" | Resources | Reference |
| "Starlight command crib sheet" | Resources | Cheat sheet |
| "Cloudflare vendor card" | Directory | Vendor |

## When two labels seem valid

Pick the label that matches the reader's next action.

```txt
Read to learn      → Guide / Handbook / Research
Follow to execute  → Playbook / SOP / Runbook
Copy to reuse      → Template / Kit
Glance to recall   → Cheat sheet / Reference
Browse as entity   → Directory
```

Then confirm metadata:

```txt
Broad family      → category
Narrow area       → subcategory
Exact topic       → topic
Legacy bundle     → collection (optional)
Cross-cut filters → tags
```

# Decision tree

> Source: https://library.zajapps.com/zajlibrary/authoring/content-system/resources/reference/content-architecture/decision-tree/

Use this when a new file, folder, note, export, or generated artifact lands in the library. Ask the questions in order and stop at the first clear match.

First pick or create the topic home (`category` / `subcategory` / `topic`). Then pick the shelf and kind inside that topic. `collection` is optional legacy metadata for prompts and old grouping language; it is not a shelf or an active route family.

## The routing tree

```txt
New content item

├── Is it an entity to browse?
│   └── Directory
│       ├── Tool
│       ├── Skill
│       ├── Vendor
│       ├── Product
│       ├── Person
│       └── Link
│
├── Is it reusable, copyable, fillable, downloadable, or quick lookup?
│   └── Resources
│       ├── Template
│       ├── Kit
│       ├── Cheat sheet
│       ├── Reference
│       ├── Glossary
│       └── Prompt pack
│
├── Is it for building, operating, or verifying something?
│   └── Build & Create
│       ├── Playbook
│       ├── Blueprint
│       ├── SOP
│       ├── Runbook
│       └── Checklist
│
└── Is it for learning, understanding, or preserving evidence?
    └── Learn & Understand
        ├── Handbook
        ├── Guide
        ├── Concept / Explainer
        ├── Research
        └── Case study
```

## Fast questions

| Question | If yes |
| --- | --- |
| "Do I browse this as an entity?" | Directory |
| "Do I copy, fill, download, or glance at this?" | Resources |
| "Do I use this to build, run, or verify work?" | Build & Create |
| "Do I read this to understand or learn?" | Learn & Understand |

## Common routing examples

| Item | Shelf | Kind |
| --- | --- | --- |
| "Setup New Laravel/CodeCanyon" | Build & Create | Playbook |
| "Production deploy exact commands" | Build & Create | Runbook |
| "Vercel Git authorization steps" | Learn & Understand | Guide |
| "ZajLibrary content model" | Build & Create or System docs | Blueprint / concept |
| "Best Starlight plugins research" | Learn & Understand | Research |
| "AGENTS.md starter file" | Resources | Template |
| "CodeCanyon AI System bundle" | Resources | Kit |
| "Vercel project IDs" | Resources | Reference |
| "Starlight command crib sheet" | Resources | Cheat sheet |
| "Cloudflare vendor card" | Directory | Vendor |

## When two labels seem valid

Pick the label that matches the reader's next action.

```txt
Read to learn      → Guide / Handbook / Research
Follow to execute  → Playbook / SOP / Runbook
Copy to reuse      → Template / Kit
Glance to recall   → Cheat sheet / Reference
Browse as entity   → Directory
```

Then confirm metadata:

```txt
Broad family      → category
Narrow area       → subcategory
Exact topic       → topic
Legacy bundle     → collection (optional)
Cross-cut filters → tags
```