CollectContent CollectContent is built around a simple but powerful content model. Understanding how the core concepts fit together will help you get the most out of the platform from day one.
The core concepts
Teams
Teams acts as a shared workspace, containing all of your projects. You can invite other team members to collaborate, with different roles to ensure your content remains secure.
Billing and usage are tied to your team. However, you can create a new team at any time.
Projects
Each team can have many projects. A project, such as a "Website migration", contains all of your content, templates and a specific workflow that the content within this project should follow.
You can create different projects for your different needs.
Structure (Templates & Components)
A template defines the structure of a piece of content, what fields it contains, what type of data each field holds and how the editor is laid out. Think of it as a blueprint for your content.
Template fields have a type (text, images, attachments, checkboxes, etc.) that controls what kind of content they can hold. Each field has a number of configurable settings, such as limiting the number of attachments that can be uploaded, defining specific image crop sizes or switching a text field to plain text only.
Template fields can also be:
- Marked as "repeatable", allowing your editors to add additional repeats of a field, which is ideal for dynamic content such as FAQs.
- Saved as "reusable components", allowing you to reuse a specific group of fields in other templates.
See Understanding Field Types for the full list.
Content Items
An item is a single piece of content created from a template. It inherits the template's field structure and is where your team actually writes and uploads content.
The content editor is a collaborative workspace where your team members can collaborate on a piece of content in real time with live cursors.
Workflow stages
Each project defines a workflow. A workflow helps you to keep track of the progress of your content. For example, whether your content is "In-Draft", "In-Progress" or "In-Review".
Workflow stages can be colour-coded and allow you to define due-dates, whether the content item should be "read-only" while in the workflow stage and assign specific team members who may need to action the content in some way during that stage.
How they connect
Project → Templates → Items
Every item belongs to one project and is based on one template. When you update a template's fields, all existing items retain their data, new fields appear empty, and removed fields are archived rather than deleted.
What's next?
Now that you understand the model, head to Creating a Template to put it into practice.