diff --git a/CreateaProject.mdx b/CreateaProject.mdx
new file mode 100644
index 0000000..72155cc
--- /dev/null
+++ b/CreateaProject.mdx
@@ -0,0 +1,117 @@
+---
+title: "Create a Project"
+---
+
+#
+
+## Roles: Manager | Partner
+
+
+
+
+
+You can create a new project right after adding your cloud credentials! During project creation, you have the option to specify various settings and configurations to suit your needs.
+
+### Steps to Create a New Project
+
+
+
+
+ Open the Projects menu in the Taikun CloudWorks platform.
+
+
+
+ Locate and click the **Add Project** button in the top right corner.
+
+
+
+ Enter a name for your project and select a **Cloud** provider in the pop-up.
+
+
+
+
+ Profiles for **Access**, **Alerting**, **Kubernetes**, and **Policy** are initially set to default. Custom profiles need to be created in advance before using them in your projects.
+
+
+
+
+ Certain features in Taikun CloudWorks, such as **Alerting Profiles**, **Monitoring**, **Backup**, and **Expiration Dates**, can be configured or enabled after the project is created.
+
+
+***
+
+***
+
+
+ If you intend to use a specific **Access Profile** in your project, create it *before* starting the project creation process. This profile can then be selected from the drop-down menu during project creation.
+
+
+***
+
+***
+
+### Project Details
+
+* **Project Name**: Enter a unique name for your project. Only lowercase alphanumeric characters and dashes are allowed (3-30 characters; no underscores). Example: `my-project1`
+
+* **Cloud**: Select where to store your project. For instructions on connecting a new cloud, see [Cloud Credentials](#cloud-credentials).
+
+#### Optional Settings
+
+* **Kubernetes Version**: Choose a specific Kubernetes version, if needed.
+
+* **CIDR**: Specify a network or sub-network if required.
+
+* **Access Profile**: Choose a profile for project access. (For setup instructions, see [Access Profiles](#access-profiles)).
+
+* **Alerting Profile**: Select an alerting profile from the dropdown if already created.
+
+* **Kubernetes Profile**: Choose a profile after creating it in Kubernetes Profiles.
+
+ * **For OpenStack**: If you choose a profile with an enabled Taikun Load Balancer, you’ll need to configure the **Taikun Load Balancer Flavor**, **Router Id Start Range**, and **Router Id End Range**.
+
+* **Policy Profile**: Select a policy profile for this project.
+
+* **Monitoring**: Enables monitoring of Kubernetes clusters to help manage containerized infrastructure, track resource utilization (memory, CPU, storage).
+
+* **Backup**: Choose backup credentials, or create new ones in [Backup Credentials](#backup-credentials). You can change this later if needed.
+
+* **Expiration Date**: Set a project expiration date. By default, this is set to infinity. Note: Projects remain unaffected after the expiration date.
+
+* **Serverless**: Enable serverless options to manage events and triggers. DNS setup is required.
+
+* **Spot Features**: Enable spot features (AWS, Azure, Google supported).
+
+ * **Allow Spot VMs**: Enable spots for standalone VMs.
+
+ * **Allow Full Spot Kubernetes**: Enable full spot for Kubernetes.
+
+ * **Allow Spot Workers**: Enable spots for workers only.
+
+ * **No Spot for Kubernetes**: Disable spots for Kubernetes.
+
+* **Flavor**: Bind specific flavors to the project. Multiple flavors can be added and managed in **Flavor Info**.
+
+#### Autoscaler Configuration
+
+Enable autoscaling by specifying server parameters:
+
+* **Name**: Define a name for the server.
+
+* **Minimum Workers**: Set the minimum number of workers.
+
+* **Maximum Workers**: Set the maximum number of workers.
+
+* **Disk Size**: Define disk size.
+
+* **Flavor**: Select a flavor for the server.
+
+***
+
+## Additional Resources
+
+For a comprehensive understanding of the project creation process, watch our instructional video below:
+
+
+
+
\ No newline at end of file
diff --git a/development.mdx b/development.mdx
deleted file mode 100644
index 8783008..0000000
--- a/development.mdx
+++ /dev/null
@@ -1,98 +0,0 @@
----
-title: 'Development'
-description: 'Learn how to preview changes locally'
----
-
-
- **Prerequisite** You should have installed Node.js (version 18.10.0 or
- higher).
-
-
-Step 1. Install Mintlify on your OS:
-
-
-
-```bash npm
-npm i -g mintlify
-```
-
-```bash yarn
-yarn global add mintlify
-```
-
-
-
-Step 2. Go to the docs are located (where you can find `mint.json`) and run the following command:
-
-```bash
-mintlify dev
-```
-
-The documentation website is now available at `http://localhost:3000`.
-
-### Custom Ports
-
-Mintlify uses port 3000 by default. You can use the `--port` flag to customize the port Mintlify runs on. For example, use this command to run in port 3333:
-
-```bash
-mintlify dev --port 3333
-```
-
-You will see an error like this if you try to run Mintlify in a port that's already taken:
-
-```md
-Error: listen EADDRINUSE: address already in use :::3000
-```
-
-## Mintlify Versions
-
-Each CLI is linked to a specific version of Mintlify. Please update the CLI if your local website looks different than production.
-
-
-
-```bash npm
-npm i -g mintlify@latest
-```
-
-```bash yarn
-yarn global upgrade mintlify
-```
-
-
-
-## Deployment
-
-
- Unlimited editors available under the [Startup
- Plan](https://mintlify.com/pricing)
-
-
-You should see the following if the deploy successfully went through:
-
-
-
-
-
-## Troubleshooting
-
-Here's how to solve some common problems when working with the CLI.
-
-
-
- Update to Node v18. Run `mintlify install` and try again.
-
-
-Go to the `C:/Users/Username/.mintlify/` directory and remove the `mint`
-folder. Then Open the Git Bash in this location and run `git clone
-https://github.com/mintlify/mint.git`.
-
-Repeat step 3.
-
-
-
- Try navigating to the root of your device and delete the ~/.mintlify folder.
- Then run `mintlify dev` again.
-
-
-
-Curious about what changed in a CLI version? [Check out the CLI changelog.](/changelog/command-line)
diff --git a/test.mdx b/test.mdx
index d4696bd..df0e8ee 100644
--- a/test.mdx
+++ b/test.mdx
@@ -1,13 +1,11 @@
# Create a Project
-
## Roles: Manager | Partner
-
You can create a new project right after adding your cloud credentials! During project creation, you have the option to specify various settings and configurations to suit your needs.
### Steps to Create a New Project
@@ -17,9 +15,11 @@ You can create a new project right after adding your cloud credentials! During p
Open the Projects menu in the Taikun CloudWorks platform.
+
Locate and click the **Add Project** button in the top right corner.
+
Enter a name for your project and select a **Cloud** provider in the pop-up.
@@ -31,15 +31,18 @@ You can create a new project right after adding your cloud credentials! During p
-Certain features in Taikun CloudWorks, such as **Alerting Profiles**, **Monitoring**, **Backup**, and **Expiration Dates**, can be configured or enabled after the project is created.
+ Certain features in Taikun CloudWorks, such as **Alerting Profiles**, **Monitoring**, **Backup**, and **Expiration Dates**, can be configured or enabled after the project is created.
----
***
+
+***
+
-If you intend to use a specific **Access Profile** in your project, create it *before* starting the project creation process. This profile can then be selected from the drop-down menu during project creation.
+ If you intend to use a specific **Access Profile** in your project, create it *before* starting the project creation process. This profile can then be selected from the drop-down menu during project creation.
----
+
+***
***
@@ -100,18 +103,11 @@ Enable autoscaling by specifying server parameters:
* **Flavor**: Select a flavor for the server.
***
+
## Additional Resources
For a comprehensive understanding of the project creation process, watch our instructional video below:
+
+
+You can create a new project right after adding your cloud credentials! During project creation, you have the option to specify various settings and configurations to suit your needs.
+
+### Steps to Create a New Project
+
+
-
-
-## Troubleshooting
-
-Here's how to solve some common problems when working with the CLI.
-
-