Concepts

Learn · concept

▶Start here

You are here: Learn → Concepts This type is for you if: you need vocabulary, mental models, or the why before architecture or code. Not this? Blueprints = pre-build design · Guides = one how-to path.

The map

graph TD
  C["Concept"] --> V["Vocabulary"]
  C --> M["Mental model"]
  C --> W["Why it works"]
  C --> B["Blueprint<br/>when design is next"]

---

Start here

Concept pages live under category folders when published. Until standalone concept files land here, the durable mental models live in handbooks and guides:

Laravel · CodeCanyon handbook ZajModules, three-tier admin, schema, and version management.

Laravel · CodeCanyon guides Read-once theory — deployment, security, database, architecture.

AI agents · Agent framework concepts Framework primitives for the Mastra-style agent stack.

Content architecture How this library organizes knowledge.

Understand everything — concept vs guide vs handbook

• Concept = explain relationships and definitions (often diagram-worthy).
• Guide = walk one path to one outcome.
• Handbook = durable multi-page reference for a whole domain.

Concepts stay Learn; pre-build system design belongs in Blueprints.