Docs Developer Site
Enonic XP
arrow-down
  1. Manifesto
    1. Projects
    2. Build System
    1. Globals
    2. HTTP
    3. Controllers
    4. Filters
    5. Events
    6. Websocket
    7. Error handler
    8. ID provider
    9. Tasks
    10. Localization
    11. Java bridge
      1. Webapp Engine
        1. Image service
        2. Component service
      3. Admin Engine
      4. Asset service
      5. HTTP service
      6. IDprovider service
    2. Task engine
    3. Management Endpoint
    4. Statistics Endpoint
    1. NoQL syntax
    2. System properties
    3. Index configuration
    4. Aggregations
    5. Highlighting
    6. Branches
  6. IAM
    1. Widgets
    1. Content Projects
    2. Schema System
    3. Mixins
    4. Input Types
    5. Content Types
    6. X-data
    7. Macros
    8. Sites
    9. Page Components
    10. Contributions
    11. Mappings
    12. Response Processors
    1. Strategies
    2. Distribution
    3. Docker image
    4. Vhosts
    5. Configuration
    6. Data management
    7. Clustering
    1. Admin API
    2. Authentication API
    3. Cluster API
    4. Common API
    5. Content API
    6. Context API
    7. Event API
    8. I18N API
    9. IO API
    10. Mail API
    11. Node API
    12. Portal API
    13. Project API
    14. Repo API
    15. Tasks API
    16. Value API
    17. Websocket API
    1. Upgrade Notes
    2. Upgrading Apps
Enonic XPCMSContent Projects

Content projects

Contents

Content projects

Introduction

Content projects represet the starting point of XP’s CMS. In order to create sites and content, you first need to create a project. Project defines default permissions and other useful settings for your content and editors.

Project settings

Basics

  • Display name - a human readable name

  • Identifier - a unique id within the installation. Cannot be changed when first created

  • Default language - Specifies the default language for content created in the project

Access mode

Project access mode defines default read permissions for it’s content. The available values are:

  • Public (Everyone can read the content)

  • Private (only users with project roles can read the content)

  • Custom (a specific list of principals can be granted access to read the content, i.e. Employees)

To handle private and custom mode, a special "viewer" role is created and given read access to the content items.

Roles

To provide access to a project or manage it, users can be granted special roles. The following roles are available per project:

  • Contributor - Access to project and issues (must be given specific permissions to create or manage any content)

  • Author - Same as contributor, but can additionally create and update content anywhere in the structure

  • Editor - Same as Author, but with full permissions and access to rich-text editor source mode

  • Owner - Same as Editor, but can also manage the project settings

For each project, dedicated principal roles are created. The roles are named as follows: com.enonic.cms.project.<id>.<roletype>

An example might be com.enonic.cms.myproject.author.

Storage

Another important purpose of projecs is to strictly isolate the content from other projects. As such, each project gets a dedicated repository.

This means, that editors of a particular project will not be able to see, use or link to content within other projects.

Site engine

When accessing your content through the site engine, the project identifier is used to access the specific project. I.e. the internal path /site/myproject/draft can be used to access draft items of the project with identifier ´myproject´.

API

To programmatically manage projects, use the project API

Contents