Skip navigation

Set up your project

Every organization is different and we at Kentico know that. That’s why projects in Kontent can be whatever you need them to be.

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.

Table of contents

    It all begins with a project

    This section will help you with the decisions regarding your subscription, projects, and environments. Decisions on these topics will set the path for many decisions later, which will be described in other articles.

    Technically speaking, a project is an organizational unit. The content inside a project shares its configuration. All content in one project uses the same workflow, the project has a group of users and roles. Similarly, a project has its content types and content can be easily interlinked. However, each subscription planOpens in a new window comes with a different level of functionality so we recommend you get familiar with your current subscription so that you can switch your plan when desired.

    When deciding how to approach the setup of projects in your organization, think in terms of content reuse, organizational boundaries, and access rights. Moreover, break your organizational silos and remove content friction like copying and pasting.

    1. Create more projects if needed

    Kontent allows you to create any number of projects in your subscription. Depending on your project needs, decide whether you are going to set up one or multiple projects.

    In most cases, a single project is sufficient to cover typical content needs. But there might be some exceptions when you'll benefit from using more projects. The question typically is whether all content can share most of the settings or if you need to separate your content in some way.

    Decide for one or more projects

    2. Choose your approach for assets

    Assets might seem less important than projects, yet it's the opposite. The way of storing your assets is a part of the decisions that determine how your project will work and affect how your content creators will work later.

    The default approach is to use Kontent's out-of-the-box asset library, which you can use for the content in your project. However, larger companies may already have implemented a digital asset management (DAM)Opens in a new window system. Using a third-party DAM is also an option for Kontent.

    Looking into how assets work will help you when modeling content, which is going to be the next step.

    Decide about your asset storage

    What's next?

    Setting up your subscription and project will set the boundaries that you'll follow when configuring Kontent further. It's the first step not only on the path of migrating to Kontent but also on the path of having your whole content process improved.

    When you're finished with the decisions about your projects and assets, continue by setting up your content model.