draft

content/manuals/projects/_index.md

@@ -10,6 +10,10 @@
 description: Learn how to use Docker Projects which provides a unified, project-based workflow to run your containerized projects. 
 keywords: Docker, projects, docker deskotp, containerization
 grid:
+- title: How Docker Projects works
+  description: Learn How Docker Projects works
+  icon: category
+  link: /projects/about/
 - title: Open a new project
   description: Learn how to open a new local or remote projects.
   icon: checklist
@@ -22,6 +26,14 @@
   description: Run or remove your projects.
   icon: tune
   link: /projects/manage/
+- title: View your projects
+  description: View detailed information about your projects and services within your projects
+  icon: visibility
+  link: /projects/view/
+- title: FAQs
+  description: View common FAQs about Docker Projects
+  icon: help
+  link: /projects/faq/
 ---
 
 Docker Projects provides a simplified, project-based workflow for running and managing containerized applications. It organizes your code, configurations, and logs across local and cloud environments into a single view, making it easy to collaborate and share across teams.
@@ -30,42 +42,9 @@
 
 ### Key features and benefits
 
  - One-click project setup: Open a local folder or clone a Git repository and run your project instantly.
  - Minimal Docker expertise required: Ideal for both beginners and experienced engineers.
  - Custom `run` commands for your projects: Define and store preconfigured `run` commands that are equivalent to running `docker compose up`.
  - Local & remote projects:  Work on projects locally or sync artifacts to the cloud for cross-device access and easy collaboration.
 
-## How it works 
-
-Docker Projects requires a Compose file (docker-compose.yml) to define your application's services, networks, and configurations. When you open a project, Docker Projects automatically detects the Compose file, allowing you to configure and run services with pre-set commands. 
-
-By integrating with Docker Compose, Docker Projects ensures a consistent, easy-to-manage workflow for both individual developers and teams. Whether you're starting a new project, configuring it, or collaborating with a team, Docker Projects keeps the process simple.
-
-1. Create or open a project. You can:
-
- - Open a local project: Select a folder on your machine that contains your project code.
- - Clone a Git repository:Provide a repository URL and clone the project into a local directory.
-
-Once a project is opened, Docker Desktop detects the Compose file and prepares the project for execution.
-
-2. Configure and run your project with pre-configured commands. These commands:
-
- - Work like `docker compose up`, launching services based on the Compose file.
- - Can be customized with additional flags, multiple Compose files, and environment variables.
- - Allow pre-run tasks, such as executing scripts before starting the services.
-
-All of which means you can fine-tune your configurations without manually running complex CLI commands.
-
-3. Collaborate and share with teams. For projects linked to a Git repository, Docker Projects stores artifacts in the cloud, enabling easy collaboration:
-
- - Work across devices: Open a project from any machine and instantly access stored configurations.
- - Share configurations: Team members can access predefined run commands, reducing setup time.
-
-Collaboration is seamless—new developers can join a team, open a project, and start working without complex setup steps.
-
-4. Manage and iterate. Once a project is up and running, Docker Projects makes it easy to monitor, update, and troubleshoot:
-
- - View logs to debug issues and track service activity.
- - Edit configurations and run commands as requirements change.
-
 {{< grid >}}

content/manuals/projects/about.md

@@ -0,0 +1,36 @@
+---
+title: How it works
+description: Understand how Docker Projects works 
+keywords: docker projects
+---
+
+Docker Projects requires a Compose file (docker-compose.yml) to define your application's services, networks, and configurations. When you open a project, Docker Projects automatically detects the Compose file, allowing you to configure and run services with pre-set commands. 
+
+By integrating with Docker Compose, Docker Projects ensures a consistent, easy-to-manage workflow for both individual developers and teams. Whether you're starting a new project, configuring it, or collaborating with a team, Docker Projects keeps the process simple.
+
+1. Create or open a project. You can:
+
+ - Open a local project: Select a folder on your machine that contains your project code.
+ - Clone a Git repository:Provide a repository URL and clone the project into a local directory.
+
+Once a project is opened, Docker Desktop detects the Compose file and prepares the project for execution.
+
+2. Configure and run your project with pre-configured commands. These commands:
+
+ - Work like `docker compose up`, launching services based on the Compose file.
+ - Can be customized with additional flags, multiple Compose files, and environment variables.
+ - Allow pre-run tasks, such as executing scripts before starting the services.
+
+All of which means you can fine-tune your configurations without manually running complex CLI commands.
+
+3. Collaborate and share with teams. For projects linked to a Git repository, Docker Projects stores artifacts in the cloud, enabling easy collaboration:
+
+ - Work across devices: Open a project from any machine and instantly access stored configurations.
+ - Share configurations: Team members can access predefined run commands, reducing setup time.
+
+Collaboration is seamless—new developers can join a team, open a project, and start working without complex setup steps.
+
+4. Manage and iterate. Once a project is up and running, Docker Projects makes it easy to monitor, update, and troubleshoot:
+
+ - View logs to debug issues and track service activity.
+ - Edit configurations and run commands as requirements change.

content/manuals/projects/edit.md

@@ -2,20 +2,20 @@
 title: Add or edit your run commands
 description: Learn how to add or edit your run commands in Docker Projects
 keywords: Docker, projects, docker deskotp, containerization, open, remote, local, run commands
-weight: 20
+weight: 30
 ---
 
 ## Add a run command to a project
 
 1. Open an existing project and ensure that it is stopped.
 
 2. From the command dopdown menu, select **New run command**.
 
 3. Specify the following information for the run command:
 
    > [!TIP]
    >
    > While configuring your run command, you can view the equivalent docker compose up command in the Run command section on the configuration page. You can also use this command to run your project from the command line. You can refer to the docker compose up reference documentation to learn more about the options you configure. 
 
    - **Name**: Specify a name to identify the run command.
    - **Compose files**: Select one or more Compose files from your project. 
@@ -25,16 +25,16 @@
    > 
    > While the --env-file flag isn't currently supported, you can specify environment variables in your Compose file, or use the Tasks option to run a script that sets your environment variables. 
 
    - **Services that will run**: After selecting one or more Compose files, the services defined in the files will appear here. If there is more than one service, you can optionally choose to not run a service by unchecking it.
    - **Tasks (Advanced options)**: Optionally specify a command to run before running the project. For example, if you want to run a bash script from the project directory named set-vars.sh, you can specify bash set-vars.sh. Or, on Windows to run a script with cmd.exe named set-vars.bat, specify set-vars.bat. Note that a task can access environment variables from your terminal profile, but it can't access local shell functions nor aliases.
 
 4. Select **Save changes**. 
 
 You can now select the new run command from the dropdown menu after opening the project.
 
 ## Edit a run command
 
 1. Open an existing project and ensure that it is stopped.
 2. Select the run command you want to change from the command dropdown menu.
 3. Select the **Edit** icon next to the **Run** button.
 4. Specify your changes and then select **Save changes**.

content/manuals/projects/faq.md

@@ -3,6 +3,7 @@
 linkTitle: FAQs
 description: Find common FAQs for Docker Projects
 keywords: faqs, docker projects, local, remote
+weight: 60
 ---
 
 ## Why is a Compose file required?
@@ -16,5 +17,5 @@
 
 Without a Compose file, Docker Projects doesn't have a way to understand how your application should be structured or executed.
 
 ## What if my project doesn’t have a Compose file?
 

content/manuals/projects/manage.md

@@ -2,14 +2,14 @@
 title: Manage your projects
 description: Learn how to delete or completely remove a project.
 keywords: Docker, projects, docker deskotp, containerization, open, remote, local
-weight: 30
+weight: 40
 ---
 
 ## Run a project or service
 
 1. Open a new or existing project.
 
 2. Select a run command from the dropdown menu.
 
 3. Select the **Run** button for the project or the **Play** button next to the service you'd like to run.
 
@@ -21,7 +21,7 @@
 
 ## Remove a project from Docker Desktop
 
 If a project is associated with a Git repository, you can remove it from Docker Desktop.  When a project is deleted, you can no longer run the project from the **Projects** view, but its run configuration still exists remotely in the cloud. 
 
 This means that you can later [open the project](/manuals/projects/open.md#open-an-existing-remote-project) and associate it with the remote run configuration without having to specify the run command again.
 None of your local code is deleted when removing a project from Docker Desktop.

content/manuals/projects/open.md

@@ -91,7 +91,7 @@ To clone and open a remote project:
 
 2. Open your project by selecting your project under **Recents**, or by selecting the specific owner that your project is associated with and then select your project. 
 
-## Open an existing remote project
+### Open an existing remote project
 
 In the Projects page in Docker Desktop, existing remote projects display No local copy under the project. 
 

content/manuals/projects/share.md

@@ -3,6 +3,7 @@ title: Share and collaborate on a project
 linkTitle: Collaborate
 description: TBD
 keywords: TBD
+weight: 50
 ---
 
 Incoming..

content/manuals/projects/view.md

@@ -2,11 +2,12 @@
 title: View your project
 description: View information about your project or the services within your project.
 keywords: containers, docker projects, local, remote, docker desktop
+weight: 20
 ---
 
 
 View a project’s readme
 If a project has a readme file, you can view it via Docker Projects. Note that the README tab is only visible if the project has a readme file.
 To view a project’s readme:
 Open a new or existing project.
 Select the README tab..