Every organization is different, and we at Kontent.ai know that. That’s why projects in Kontent.ai can be whatever you need them to be.This lesson gives you a general overview of what projects are and what options you have to neatly organize your content within them.
Project as a top-level unit of content organization
For one organization, a project represents the whole organizational structure and its content. For another, it would be one website or campaign. You can imagine a project as a pool of all content or content with a common purpose.Technically speaking, a project is an organizational unit. All content inside a project shares the same configuration:
Your content model is project-wide: content types, taxonomies, workflows, or collections, for example.
When you need to reuse parts of your content in multiple places (other content items), you can do so without hassle within one project.
You can organize your content within one project in multiple ways:
Using taxonomies to organize your content by purpose, audience, or any other aspects important to your business.
Using collections to divide your content according to your business structure, the regions you operate in, the purpose of the content, and so on.
By defining multiple workflows to reflect the differences between how you work with various types of content and they flow through their life cycle.
Users within a project are assigned roles defined on the project level. These roles define the access level for a specific group of users, including access to content.
When deciding how to approach the setup of projects in your organization, think about content reuse, organizational boundaries, and access rights. Moreover, break your organizational silos and remove content friction like copying and pasting.
How many projects?
One of the initial decisions of your Kontent.ai implementation is how to divide content in your project and whether you need to use more than one project.