Ecommerce (Coming Soon)
What to expect from the Dyrected ecommerce section while the public ecommerce docs are still being prepared.
This section is intentionally a placeholder for now.
Dyrected's ecommerce story needs a clearer public teaching path before these pages should ship in the main navigation. Instead of sending readers into empty or incomplete docs, this landing page explains the gap and keeps the unfinished child pages out of the production sidebar.
For Cloud, ecommerce docs should focus on catalog content, media, merchandising, landing pages, and editorial workflow. Checkout, payments, carts, orders, and customer accounts stay in the commerce app or commerce platform.
For self-hosted Dyrected, future ecommerce docs may cover deeper backend behavior once the public package surface and recommended architecture are verified.
What this section is expected to cover
When this section is ready, it should teach:
- what the ecommerce plugin or package surface actually includes
- how storefront and admin responsibilities are divided
- how payment adapters fit into the architecture
- what the recommended setup path is for a real commerce project
- which parts are core concepts versus advanced extensions
Based on the current section structure, the intended topics are:
- the ecommerce plugin itself
- frontend integration
- payment adapters
- advanced ecommerce-specific patterns
Current status
This section is visible as a roadmap marker, not as finished guidance.
That keeps the top-level navigation honest: readers can see ecommerce is a planned area, but they are not pushed into thin pages that make the product surface look more complete than it is.
What happens next
Each ecommerce page should be published only after the public package behavior, setup flow, and recommended architecture are verified and written as real task-oriented docs.