CTXR Spaces
A space is where you make things — an independent website living on its own subdomain, {slug}.ctxr.app. Where an account is the consumer, a space is the producer: it publishes a site. From the moment it’s created it is fully autonomous, with no runtime leash back to the platform and none to any other space. The platform helps a space come into being and can serve it updates if you ask, but it never reaches in while the space is running.
This chapter is about that producer layer: what a space is made of, how one comes into being, and the envelope a plan defines around it.
What a space is and does
A space is made of three layers, each with a different owner. Content is the typed nodes editors create and approve. Settings are its identity, actors, plan and configuration, reached through the management layer. Build is the templates, styles and scripts that turn content into HTML — the developer’s domain, and the one layer the platform’s defaults give way to entirely.
A space doesn’t begin as a blank canvas. It starts as a clone of a curated example — real structure and example content together — which you then make your own; the reasoning is in The adoption model. What a space is allowed to do is set by its plan: a set of features and limits that defines the envelope it lives in, adopted rather than pushed, and tuned to keep the site fast.
A space is also worked — filled with content through an editor, and reachable through its own API. Both have a conceptual home here; their technical detail lives one layer deeper.
The third layer — actually building a space, its templates and the helpers they use — is large enough to be its own journey. The hands-on technical detail lives in Development, and the concrete catalogues of helpers, attributes and API actions in Reference. Both belong to the space world; this chapter holds the concepts they build on.
In this chapter
- What is a space — public co-creation under your own domain
- Limits and features — what a plan grants, with adoption as the upgrade path
- Every space has an API — each space’s own programmatic surface
- Editing content — how content is created and published, built on that API
- Extending with connectors — bridges to outside services, one per category
- The Space Wizard — automate bulk work through assessed plans of operations
The other half of the platform — your identity and the content you collect — is CTXR Accounts.