Application Patterns
Browse Dyrected application patterns by problem, get a short summary of what each one solves, and jump straight to the canonical docs when you need the full explanation.
Application patterns are the problem-first layer of the docs. They are here to help when you know what you are trying to solve, but you do not yet know which Dyrected feature or page to reach for.
Some patterns are Cloud-safe as written. Others need self-hosted Dyrected because they run arbitrary server code, own application-user auth, or depend on local infrastructure. When that matters, the pattern page calls it out before the example.
These pages stay intentionally short. Each pattern gives you:
- the problem it helps solve
- a short summary of the approach
- links to the canonical docs where the full explanation lives
When a pattern also has a validated recipe in @dyrected/knowledge, the goal is discovery first, not duplicate teaching. Use these pages to orient quickly, then move to the deeper docs for the full implementation detail.
Browse by problem
Content modeling
Patterns for reusable page sections, relationships between records, and other content-structure decisions that affect how editors work day to day.
Access control
Patterns for row-level access, role-based permissions, and deciding who can read, update, or delete which records.
Admin experience
Patterns for making the Admin UI react to editor input, reveal fields only when needed, and keep forms easier to use.
Custom app surfaces
Patterns for building media tools, document editors, and theme-aware Dyrected UI directly inside your own product pages and dashboards.
Data lifecycle
Patterns for slugs, cross-field validation, and schema changes that need to stay safe as content evolves over time.
Workflows
Patterns for draft, review, and publishing flows when content needs approval before it goes live.
Integrations
Patterns that connect content structure to supporting capabilities such as uploads and media handling.