Overview
Browse the app-shaped Dyrected examples that are planned next, see what each one is meant to teach, and jump to the docs pages that already cover the underlying patterns.
Examples are where Dyrected will show complete application shapes, not just isolated API features. The goal is to make it easier to answer a practical question: which example is closest to what I am building?
The examples are still careful about runtime boundaries. Cloud examples should show Dyrected as the managed content backend around an app. Self-hosted examples can show Dyrected inside the app backend when the CMS needs to own runtime behavior.
This section is intentionally light for now. The full example repositories are still coming together, so these pages focus on two things:
- what each example app is meant to demonstrate
- which Dyrected patterns you should read today while the full example is still on the way
Current example roadmap
Ecommerce
An online catalog and merchandising example with products, media, editorial content, and structured relationships between records.
Booking
A service-booking example focused on availability, editor-managed content, and the permissions and validation that keep booking flows predictable.
Knowledge base
A documentation-style content example with slugs, structured content, publishing flow, and the content modeling needed for search-friendly article collections.
How to use these pages today
Each example page tells you three things:
- the shape of the app it is meant to represent
- the Dyrected patterns the example is planned to use
- the canonical docs pages that already explain those patterns in detail
That means you can start learning the underlying building blocks now, even before the full example repositories are ready.
What comes later
As the examples land, these pages can grow into fuller implementation guides with repository links, architecture notes, and code walkthroughs. For now, treat them as the public map for the examples Dyrected is actively preparing.