Booking
A coming-soon booking example focused on scheduling-friendly content models, validation, permissions, and editor-managed service flows.
This example is planned for teams building a service-booking, appointment, or reservation flow where content and operational rules need to stay predictable. It is meant to show how Dyrected can support the editable side of the experience without turning business logic into fragile CMS configuration.
For self-hosted Dyrected, the example can include application-user auth, local validation hooks, transaction-aware scheduling behavior, and integrations that need to run in your backend.
The implementation is still coming soon, so this page points you to the core patterns worth learning now.
Example status
Coming soon. The public example implementation is not ready yet.
What this example is meant to show
- service and location content models
- editor-managed content around scheduling and availability
- validation rules for date, time, and related fields
- access rules for staff-owned or team-owned records
- admin behavior that adapts as editors fill in the booking form
Patterns used
Because the full example is still in progress, treat this as the planned coverage for the first version.
- Validate related fields before saving
- Limit documents to their owner
- Restrict content operations by user role
- Update a dropdown from another field
- Show an Admin field only when it is relevant
- Model a relationship and its reverse lookup
Related docs
Knowledge Base
A coming-soon knowledge-base example focused on article modeling, slugs, structured publishing, and content relationships for documentation-style sites.
Ecommerce
A coming-soon ecommerce example focused on product content, media, relationships, and the editorial patterns teams usually need before launch.