Plugins (Coming Soon)
What to expect from the Dyrected plugins section while the public plugin docs are still being written.
This section is intentionally a placeholder for now.
The plugin ecosystem is part of Dyrected's planned public docs, but the current pages under this section are not ready to ship as user-facing guides yet. Rather than sending readers into thin or incomplete pages, this landing page sets the expectation clearly and keeps the unfinished plugin docs out of the production sidebar.
What this section is expected to cover
When this section is published properly, it should explain:
- which Dyrected plugins are official today
- what problem each plugin solves
- how to install and configure each one
- when to choose a plugin over core Dyrected configuration
- how to build your own plugin when the existing ones are not enough
Based on the current repo structure, the planned coverage includes topics such as:
- building your own plugin
- advanced plugin APIs
- form builder
- import/export
- MCP
- multi-tenant
- nested docs
- redirects
- search
- sentry
- SEO
- Stripe
Current status
Treat this section as a documentation roadmap, not as finished guidance.
The section is being left visible in the menu so readers know the ecosystem area is planned, but the unfinished child pages are being kept out of the production navigation until they are review-ready.
What happens next
The right next step is not to fill this area with placeholders. Each plugin page should be rewritten only once the public package surface, setup steps, and recommended use cases can be verified against the actual Dyrected packages and docs sources.
Token Data
What a Dyrected session token actually carries — the identity claims sub, email, and collection — and how the full user object in your access rules and hooks is rebuilt from the database on each request.
Deployment
Ship Dyrected to production with the right boundary, durable infrastructure, stable secrets, and a deployment flow that matches how the product actually boots.