Skip to main content
Projects are workspace containers within an organization that group related content and assets. Each project maintains its own set of components, content types, content, and assets.

The Project Object

string
Unique identifier (UUID)
string
Parent organization ID
string
Project name
string
URL-friendly project identifier
string
Project description
string
Status: active, archived, or deleted
string
Environment: production, staging, or development
object
Project settings including locales, platforms, and CDN configuration
object[]
Project dependencies with projectId and version
object
Project-level permissions and role configurations
object
Additional project metadata including createdBy and tags
string
Creation timestamp (ISO 8601 format)
string
Last update timestamp (ISO 8601 format)

Settings Object

Example Object

Project Structure

Projects contain the following resources:
  • Collections - Organizational groups for components
  • Components - View and layout components with versions
  • Content Types - Schemas defining content structure
  • Content - Actual content entries
  • Assets - Media files and images
  • Saved Searches - Reusable search configurations
  • Packages - Versioned snapshots of components

Project Dependencies

Projects can depend on other projects, allowing you to share components and content types across projects. Dependencies are specified with a project ID and semantic version.
When a package is created, it snapshots the current project dependencies, ensuring consistent behavior across deployments.