Guides

Learn · guide

▶Start here

You are here: Learn → Guides This type is for you if: you want one focused how-to — start at the top, finish at the bottom. Not this? Handbooks = whole domains · Playbooks = phased execution with gates.

The map

graph LR
  G["Guide<br/>one topic"] --> Out["One outcome"]
  H["Handbook"] --> Spine["Multi-page spine"]
  G -.->|"grows past ~1 screen"| H

---

Start here

Guides are grouped by category → subcategory folders (see Path layout).

AI System · MCP Build an MCP server for your docs site.

AI System · Claude Code Package MCP + skill + command as a plugin.

Servers · Shared Hosting Understand account-level setup before app deploys consume cron, alerts, and monitoring.

Laravel · CodeCanyon Read-once theory for CodeCanyon Laravel.

Handbooks Whole-domain reference (e.g. Mastra).

Understand everything — what belongs in Guides

A guide is a single-purpose narrative: one problem, one path, one result. If it sprouts distinct sections that each deserve their own URL, promote it to a handbook folder. If it becomes an executable workflow with phases and gates, move the procedure to Build → Playbooks.

Path rule: drop files at learn/guides/<category>/<subcategory>/<slug>.mdx — never loose under learn/guides/. Set matching category + subcategory frontmatter; use collection + tags for cross-shelf browse pages.