Plugin system
Your expertise on top of CDT.
A plugin adds a tool, a live-data layer or a data page to a running CDT instance without changing CDT core.
Plugin docsGallery
Plugins in action
How it works
Add your own features without changing CDT core.
CDT core stays general and dependable for every organization. Domain-specific work lives in plugins that each organization builds, owns and maintains.
No change to core
A plugin is a folder with a manifest and React components. CDT loads it and renders its contributions next to the core.
Mounted or compiled in
A self-hosted deployment mounts a built plugin folder and restarts. A plugin useful to every installation goes into core through a pull request.
Two-level opt-in
An administrator adds a plugin to the organization, then each person chooses whether it runs for them. Nothing appears because an update shipped it.
Open standards
Plugins read and write IFC, IDS, bSDD, GeoJSON, WMS, SensorThings and BCF, so the data they produce is never tied to CDT.
What a plugin brings, and where it shows up in CDT
Build your own
Start from something that already runs.
create-cdt-plugin generates a working plugin from a few answers, including the manifest, the build configuration and the translations. The docs also cover building a plugin with an AI coding assistant.
npx create-cdt-plugin