Project Creation

Introduction

This page serves as the entry point to creating a project within the DXP platform. The steps outlined below assume you have the necessary permissions (e.g., Architect role) to access and manage projects within your organization.

---

Prerequisites

Before starting, ensure you meet the following prerequisites:

• Permission: You must have the appropriate permissions (e.g., Architect role) to create projects.
• DevOps Tab Access: You should be familiar with the DevOps tab where projects are managed.

---

Step 1: Navigating to project creation

Where to find the project creation option

Once logged in and assigned the appropriate permissions, navigate to the DevOps tab. Here, you'll see a list of existing projects. Look for the '+' symbol above the project list, which indicates the option to create a new project.

---

Step 2: Initiating the project creation process

After clicking the '+', you will be taken to a two-step project creation page. This page includes fields that need to be filled out for your project setup.

---

Step 2.1: General project information

In this first step, you’ll input basic project details:

1. Project Name: Enter a unique name for your project.
2. Description: Provide a description to help identify the project's purpose.
3. Organization Selection: Select the organization to which the project belongs. This choice dictates who will
4. have access to the project and what permissions are applied.

Once you choose the organization, a dropdown will appear to select the project type. The project type list will vary depending on the organization.

Step 2.2: Defining project parameters

Next, choose the following settings to define the nature of your project:

1. Project Type: The types available will depend on your organization, and this will influence which install profiles are available.
   
   
2. Install Profile: This determines the codebase from which your project will be built. For example:
   • Standard Drupal Profiles contain only Drupal core.
   • Rocketship Profiles include additional modules and scripts to speed up project development.
3. Choose a deployment method.
4. Server and Environment Configuration: Select the server that will host your project. The server selection also influences the versions of PHP and Node.js.
   
   

---

Step 3: Configuring environments

Step 3.1: Default environments setup

In the second step, you will define the default environments that accompany your project. By default, you’ll configure at least two environments: dev and staging.

For each environment, you need to:

• Assign a name.
• Optionally, add a description.

Additional environments

Additional environments can be created later as needed. For more information, refer to the Create a new environment page.

---

Step 4: Completing the project creation

Once all necessary details are confirmed, click to finalize the project creation. You will be redirected to the project page. At this stage, the environments are still being created, so limited actions will be available.

---

Step 5: Monitoring environment creation

After confirming the project setup, your environments will begin to populate. This process may take some time, during which you can monitor progress:

• Notifications: Updates on environment creation will appear in the notifications section (accessible via the bell icon in the header).

• Environment Tab: Once the environments are created, they will appear in the Environments tab. Initially, their status will show as 'creating.'

Once completed, environments will transition to an active state and can be accessed individually.

---

Next steps

For more advanced configurations, refer to additional documentation on deploying environments or managing your project and its environments.