rebrand, change URLs

Author: Lagoja

docs/app/cloud/sandboxes/_category_.json renamed to docs/app/cloud/devspace/_category_.json

@@ -0,0 +1,42 @@
+---
+title: FAQ
+sidebar_position: 6
+hide_title: false
+---
+
+## What is Jetify Devspace?
+
+Jetify Devspace is a cloud-based development environment that can be customized and preconfigured using Devbox. Your Devspace is fully managed by Jetify, so you don't need to worry about setting up servers or infrastructure to get started.
+
+## What size instances are available for Jetify Sandboxes?
+
+Currently, all Jetify Sandboxes are configured with the following default specs:
+
+* 4 vCPUs
+* 16 GB RAM
+* 10 GB Home Dir SSD
+
+## Can I request a custom instance size?
+
+We are working on adding support for more instance sizes, including the ability to configure custom sizes. Stay tuned for updates!
+
+## Can I create an instance with a GPU?
+
+GPU support is coming soon!
+
+## What are the limitations for the Jetify Devspace Free Tier?
+
+Our Free Tier comes with the following limitations per user:
+
+* 2 Devspaces
+* 25 active hours per month
+* 15-minute inactivity timeout
+* 4-hours maximum runtime per Devspace
+
+## Do you have offers for Education and Open Source projects?
+
+If you're interested in using Jetify Devspace for Education or Open Source projects, please reach out to us at [[email protected]](mailto:[email protected]) to discuss your use case and needs!
+
+## Do you offer self-hosted or Enterprise solutions?
+
+We're looking for early design partners for our self-hosted and Enterprise solutions. If you're interested in exploring Jetify Devspace for your enterprise, please reach out to us at [[email protected]](mailto:[email protected])

docs/app/cloud/devspace/faq.md

@@ -1,5 +1,5 @@
 h--
-title: Linking Cloudboxes from your Repo
+title: Linking a Devspace from your Repo
 sidebar_position: 5
 hide_title: false
 ---

docs/app/cloud/sandboxes/index.md renamed to docs/app/cloud/devspace/index.md

@@ -0,0 +1,30 @@
+---
+title: Managing Devspace
+sidebar_position: 3
+hide_title: false
+---
+Devspaces that you've previously created can be managed from the Jetify Cloud dashboard. You can use the dashboard start, stop, and delete your previous Devspace instances.
+
+## Accessing the Dashboard
+
+To access Devspace in your dashboard, navigate to [cloud.jetify.com](https://cloud.jetify.com) and log in with your Jetify account. Once you select an Org, you will can view all the Devspaces that you have created within that org on the org page.
+
+If you've created any projects in the org, you can also navigate to the project and select the Devspace tab to view all your instances in that project.
+
+## Stopping and Starting Devspace
+
+Your Devspaces are automatically stopped after 15 minutes of user inactivity. This is to help you save resources, and avoid being billed for unused CPU time.
+
+If you want to manually stop your instance, click on the `Options` button on the Devspace that you want to stop, and then click on the `Stop` button. Your package store and project data will be saved, so you can quickly resume your work when you restart the Devspace.
+
+:::info
+Stopped instances are not billed for CPU usage, but you may be billed for storage usage in excess of the free tier.
+:::
+
+To restart your Devspace, click the option button on the cloud box you want to start, and then click the "Start" button. This will relaunch with the Home directory and packages from your previous session.
+
+## Deleting Devspaces
+
+By default, Devspaces are deleted if they are not used for more than 14 consecutive days. This is to help you save storage costs, and avoid being billed for unused disks.
+
+If you are done with a Devspace, you can delete it by clicking on the `Options` button on the instance that you want to delete, and then clicking on the `Delete` button. This will permanently delete all data associated with the Devspace.

docs/app/cloud/sandboxes/link_sandboxes.md renamed to docs/app/cloud/devspace/link_sandboxes.md

@@ -1,12 +1,12 @@
 ---
-title: Cloudboxes Quickstart
+title: Jetify Devspace Quickstart
 sidebar_position: 1
 hide_title: false
 ---
 
-Jetify Cloudboxes let you spin up reproducible cloud development environments in your browser in seconds. Jetify Cloudboxes are powered by [Devbox](/devbox/docs), so you can run your environment on any machine. You can launch any
+Jetify Devspace let you spin up reproducible cloud development environments in your browser in seconds. Jetify Devspace is powered by [Devbox](/devbox/docs), so you can run your environment on any machine. You can launch any
 
-Let's launch our first Dev Environment with Jetify Cloudboxes.
+Let's launch our first Dev Environment in Jetify Devspace.
 
 ## Step 1: Launch a Sandbox from Github
 
@@ -16,18 +16,19 @@ You can launch any Github Repo in a Jetify Sandbox by prepend the repo URL with:
 https://cloud.jetify.com/new/
 ```
 
-For example, to launch the [Devbox repo](https://github.com/jetify-com/devbox) in Jetify Cloudboxes, open the following URL in your browser
+For example, to launch the [Devbox repo](https://github.com/jetify-com/devbox), open the following URL in your browser
 
   [https://cloud.jetify.com/new/github.com/jetify-com/devbox](https://cloud.jetify.com/new/github.com/jetify-com/devbox)
 
 :::tip
   If you need some inspiration, you can also launch one of our [templates](/devbox/docs/devbox_examples) projects to get started
 :::
-You can also launch a new Sandbox by navigating to your [Dashboard](https://cloud.jetify.com/dashboard) and clicking on the `New Sandbox` button.
 
-## Step 2: Customize your Sandbox with Devbox
+You can also launch a new Devspace by navigating to your [Dashboard](https://cloud.jetify.com/dashboard) and clicking on the `New Devspace` button.
 
-You can customize your Jetify Sandbox with over 100,000 Nix packages in seconds using Devbox.
+## Step 2: Customize your Environment with Devbox
+
+You can customize your Jetify Devspace with over 100,000 Nix packages in seconds using Devbox.
 
 If your project doesn't already have a devbox.json, you can initialize one with:
 
@@ -58,9 +59,9 @@ For further reading on how to install packages with Devbox, see:
 
 ## Step 3: Save your Dev Environment with `devbox.json`
 
-Once you've customized your environment, you can save your Dev Environment config to source control by checking in your `devbox.json` and `devbox.lock` files. These files can be used to recreate your environment on Jetify Cloudboxes, or on any other machine that has devbox installed.
+Once you've customized your environment, you can save your Dev Environment config to source control by checking in your `devbox.json` and `devbox.lock` files. These files can be used to recreate your environment on Jetify Devspace, or on any other machine that has devbox installed.
 
-You can also use this file to configure initilization hooks, scripts, services, and environment variables for your project. For further reading, see:
+You can also use this file to configure initialization hooks, scripts, services, and environment variables for your project. For further reading, see:
 
 * [Devbox Configuration Reference](/devbox/docs/configuration)
 * [Devbox Script](/devbox/docs/guides/scripts)

docs/app/cloud/devspace/managing_sandboxes.md

@@ -4,7 +4,7 @@ sidebar_position: 4
 hide_title: false
 ---
 
-**Jetify Projects** are a great way to share configuration and secrets with your team. A project can store repository settings and secrets that are shared across all Cloudboxes and users in the project. For example, you can configure a project for a Backend API with the database parameters, API keys, and other secrets. When a user launches a Sandbox in the project, they will automatically have access to the project's configuration and secrets.
+**Jetify Projects** are a great way to share configuration and secrets with your team. A project can store repository settings and secrets that are shared across all Devspace users in the project. For example, you can configure a project for a Backend API with the database parameters, API keys, and other secrets. When a user launches a Sandbox in the project, they will automatically have access to the project's configuration and secrets.
 
 ## Creating a Project
 
@@ -20,14 +20,14 @@ Once the project is linked to a repository, developers can automatically create
 
 ## Sharing Secrets across Sandboxes
 
-Jetify Projects can store secrets with Jetify Secrets that are shared across all Cloudboxes in the project. Cloudboxes will automatically use the `dev` namespace when accessing secrets.
+Jetify Projects can store secrets with Jetify Secrets that are shared across all Devspaces in the project. New Jetify Devspace instance will automatically use the `dev` namespace when accessing secrets.
 
 To add a secret to a project:
 
 1. Navigate to the project in the Jetify Dashboard
 2. Click on the `Secrets` tab
 3. In the New Secrets form, provide a key and value for the secret, and then click "Add Secret"
 
-Jetify will automatically add the secrets to any Cloudbox that is launched in the project. Note that if a Cloudbox is currently running when you add a secret, you will need to restart it to access the new secret.
+Jetify will automatically add the secrets to any session that is launched in the project. Note that if a Devspace instance is currently running when you add a secret, you will need to restart it to access the new secret.
 
 For more information on managing secrets, see the [Jetify Secrets](../../secrets) guide.

docs/app/cloud/sandboxes/quickstart.md renamed to docs/app/cloud/devspace/quickstart.md

@@ -31,9 +31,9 @@ Jetify Deploys cost $0.10/vCPU per hour while your deployment is scheduled. If y
 
 -->
 
-## What are the specs of the Jetify Cloudboxes?
+## What are the specs of Jetify Devspace?
 
-Jetify Cloudboxes by default have:
+Devspaces by default have:
 
 * 4 Dedicated vCPUs
 * 16 GB of RAM