Concepts overview
Kolony is Space-centric. Everything else either stores data in a Space, connects people to Spaces, or queries Space data through modules.
Core relationships
Section titled “Core relationships”| Concept | Role |
|---|---|
| Space | Heart of the platform: a data repository for published media assets and/or attached forms, plus settings and modules |
| Channel | Connected to Spaces its owner can access; members collaborate and query Space data via connected Space Modules |
| Module | Platform capability attached to a Space (GET /v0/modules). Tags is available today; more modules will follow |
| Comment | Discussion attached to a Space and/or a Channel — not the same thing as Tags |
| Tag | Provided by the Tags module on a Space; used to categorise and query Space data (details refined in a later docs pass) |
| Media | Binary upload/download via /v0/media (opaque ids; no storage paths) |
| Form | Structured data capture (configuration + instances + file fields), typically living with a Space |
| Workflow | Stateful review/approval-style processes (configuration, items, transitions) |
| Message | Direct messaging between users (threads), separate from Space/Channel comments |
| User | Profile (/v0/users/me) and handle search |
| Marketplace | Optional discovery listings for Spaces (trending / fetch / registration) — not required for core capture & collaboration |
Typical integrator path
Section titled “Typical integrator path”Account → Space → connect Modules (e.g. Tags) → publish media / attach forms → Channel (connect Spaces, members) → comments → workflows as needed → optional messaging
Deep-dives live under this Concepts section; end-to-end recipes live under Guides. Media details: Media uploads.