Ecommerce
A coming-soon ecommerce example focused on product content, media, relationships, and the editorial patterns teams usually need before launch.
This example is planned as the closest Dyrected reference for teams building a storefront, catalog, or merchandised content experience. It is meant to cover the content structures that usually sit behind product pages, category pages, promotional content, and media-heavy landing pages.
For Cloud, read this as a content-backed storefront example. Dyrected Cloud should own catalog content, media, editorial pages, and publishing workflow. Your commerce app or commerce platform still owns carts, checkout, payments, orders, customer accounts, and product-specific business logic.
The full example is still coming soon, so use this page as a guide to the patterns that matter most while the repository work catches up.
Example status
Coming soon. The public example implementation is not ready yet.
What this example is meant to show
- a product and category content model
- media collections for product imagery and supporting assets
- relationships between products, categories, and editorial content
- flexible page composition for merchandising and campaign pages
- access and workflow patterns for teams managing storefront content
Patterns used
Because the full example is still in progress, treat this as the planned coverage for the first version.
- Build flexible pages from reusable blocks
- Model a relationship and its reverse lookup
- Restrict content operations by user role
- Create a media upload collection
- Add draft, review, and publishing states
- Validate related fields before saving
Related docs
Booking
A coming-soon booking example focused on scheduling-friendly content models, validation, permissions, and editor-managed service flows.
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.