Manage multiple websites with ease

Cameron Tape, Jan Cerman

3 minutes

Projects / Collections / Spaces / Taxonomy

Download PDF

One of the core use cases for a headless CMS is creating content for multiple channels, including multiple websites. Kontent.ai provides many tools for managing content across multiple sites, so you can always find the right approach for your needs.

Why is this important?

To effectively manage multiple websites, you need to assign the right people to the right content and ensure it’s published on the right website. Finding the ideal solution for your organization can improve the following:

Scalability: Effective site configuration allows content and websites to grow without significant restructuring.
Content delivery: Thoughtful planning ensures content reaches the right channels and is shared seamlessly between sites.
Consistency: Shared content types and guidelines ensure a unified style and structure across all sites.
Collaboration: A well-considered setup helps different teams find and work on relevant content, reduce duplication, and restrict access appropriately.

Available solutions with Kontent.ai

Start with one project for simplicity, using spaces and collections to segment content.
Opt for multiple projects only if content or workflows must remain entirely separate.
Combine roles and permissions with spaces or collections for fine-grained access control.

Choose the solution that aligns best with your organization’s structure, content strategy, and scalability goals.

Approach A: Spaces

Spaces provide a unique context for each channel or website, allowing management of multiple websites in a single project. Use spaces to preview and edit multiple websites in Web Spotlight and to see channel-specific content. For dynamic content such as news feeds or live updates, consider also using taxonomies as an alternative. Taxonomies are flexible and easy to update as your needs change; but don’t offer the same tools for previewing or permission restrictions as spaces.

Pros	Cons
Flexible categorization and permissions via collections Shared content models, roles, and workflows simplify operations Flexibility in permissions and categorization thanks to each space linking multiple collections and vice versa	Requires complex role configurations to restrict user access Spaces must be linked to collections to filter content effectively

Approach B: Collections

Collections are a great tool for grouping and dividing content, making them highly suitable for organizing content for different websites.

Pros	Cons
Efficient organization for content reuse and consistent messaging Enhanced security through role-based permissions for each collection	Careful planning needed to avoid content duplication across collections Requires a robust content model to work across multiple sites

Approach C: Roles and permissions

When websites are highly similar, such as a franchise that provides a website for each store, you can use roles and permissions to separate and manage content for multiple websites without using different collections or projects. In most cases, we recommend using roles and permissions to support your spaces (approach A) and collections (approach B), not as a standalone solution. Different roles can be assigned to specific collections or languages, which is great for fine-grained access control.

Pros	Cons
Enhanced security through different roles set for each collection Simplifies adding new content for specific teams or regions Straightforward for editors of varying skill levels	Highly dependent on appropriate role creation and assignment May be unsuitable for complex projects and content models Requires careful consideration and assignment of any shared and/or global content

Approach D: Multiple projects

Multiple projects provide complete separation for unrelated sites or brands. This approach is useful for unique workflows, content models, or permissions.

Pros	Cons
Complete separation of content, users, and access Highly customizable for complex needs	Requires more effort to configure and manage separately Sharing content between projects is technically demanding