4.0 Project Concept: Developer

Introduction

A Project is single repository of content. Everything you do in Forrit One happens within the context of a Project. You can use multiple Projects to manage different sets of content – such as for separate applications.

In this section, you will learn:

1. What a Project is

2. What is included in a Project

3. Why you might use multiple Projects

Project overview

A Project is a single repository of content

Whenever you create content, it is stored within the context of a Project. In the Forrit One UI, Projects are content repositories you can switch between; in the Forrit One backend, Projects are their own database and storage instance.

This means Projects each have their own Components, Content Types, and Releases. Projects also store some non-content data for the purpose of administration – such as users, roles, and Workflows. Essentially, any data that is created in or managed by the Forrit One UI is segregated by Project.

Projects are thus highly isolated from one another, and are typically used to safely provide bespoke content to different enterprise applications. For example, applications running on different domains and managed by separate teams might each require distinct content, release timelines, and administration – all features that Projects offer.

Using multiple Projects to manage separate content

The following diagram shows how two Projects can be used to manage different sets of content.

The ‘Education’ Project contains the Pages, Components, and Media Items that are education-related and which might be used as the content of an online learning service, while the ‘Health’ Project includes health-related content – such as for hospital websites or applications.

User journeys

1. Opening a Project

2. Using the Project Dropdown

Glossary

See the Glossary for more information.