diff --git a/packages/projects-docs/pages/faq.mdx b/packages/projects-docs/pages/faq.mdx
index 31838d26..74574771 100644
--- a/packages/projects-docs/pages/faq.mdx
+++ b/packages/projects-docs/pages/faq.mdx
@@ -116,7 +116,7 @@ We currently provide [Browser Sandboxes](/learn/sandboxes/overview#what-is-a-bro
the sandbox or preview in a web browser.
- When using a container, the sandbox has a 1GB persistent storage limit, a 1GB vCPU soft
limit, and a hard memory limit of 2 GB.
-
+
Cloud Sandboxes are part of our evolved CodeSandbox experience, so we highly advise you to use them to avoid encountering these limitations.
## I'm getting a 'Request Entity too Large' error, what should I do?
@@ -156,7 +156,7 @@ If you're having issues with your database, you can check the logs of the contai
## How do I change the editor's theme?
-To change the [theme of a Cloud Sandbox](https://codesandbox.io/docs/learn/repositories/themes), click on the CodeSandbox logo at the top left, then go to Settings > Preferences, and select a theme from the Themes dropdown. You can also do it from the [command palette](https://codesandbox.io/docs/learn/repositories/commandpalette).
+To change the [theme of a Cloud Sandbox](https://codesandbox.io/docs/learn/repositories/themes), click on the CodeSandbox logo at the top left, then go to Settings > Preferences, and select a theme from the Themes dropdown. You can also do it from the [command palette](https://codesandbox.io/docs/learn/repositories/commandpalette).
On a Browser Sandbox, you can change the theme from File > Preferences > Color Theme in the editor. You can also set a custom VS Code theme on a Browser Sandbox. Open VS Code, Press (CMD or CTRL) +
SHIFT + P, Enter: '> Developer: Generate Color Scheme From Current Settings',
@@ -175,17 +175,18 @@ resolve it. For example:
[https://codesandbox.io/s/new?runonclick=1](https://codesandbox.io/s/new?runonclick=1)
## Can I push/pull from a GitLab, Azure DevOps, or BitBucket repository?
+
Yes. While our Repositories only have built-in push and sync capabilities for GitHub, you can connect to a remote repository from any other git provider.
To do that, use our terminal to `git remote add` the remote repository and then add your credentials for it. You can also add the authentication details to the CodeSandbox microVM using [environment variables](https://codesandbox.io/docs/learn/environment/secrets).
-## How do I cancel my Personal Pro, Team Pro or Patron plan?
+## How do I cancel my Pro or Patron plan?
-For Team Pro & Personal Pro users, once you've logged in, you can downgrade your plan on the
-[Settings page](https://codesandbox.io/dashboard/settings).
+For Pro users, once you've logged in, you can downgrade your plan on the
+[Settings page](https://codesandbox.io/dashboard/settings).
If you're on one of our legacy Patron plans you can cancel
-your subscription on the [Patron page](https://codesandbox.io/patron).
+your subscription on the [Patron page](https://codesandbox.io/patron).
@@ -216,17 +217,19 @@ Yes. Follow the steps below:
## More Questions?
If you have additional questions or need support, please use the community [Discord server](https://discord.gg/R32XxEGp4s).
+
- ## Sandboxes
+ ## Sandboxes
### Why am I getting a git error resolving a dependency?
+
CodeSandbox for iOS is only compatible with dependencies hosted and accessible via HTTP or HTTPS.
This happens because the app doesn't provide local shell environments where you can run arbitrary commands, like git. Use the [CodeSandbox web editor](/learn/sandboxes/editors) instead.
You may find some of the following answers helpful if you have gone through the sections in this documentation but still haven’t solved your questions:
-
+
### I'm getting an error trying to run my sandbox in CodeSandbox for iOS. What could be the cause?
The root cause of the problem could be either a coding mistake on your side or a dependency trying to do something forbidden by iOS.
@@ -244,14 +247,18 @@ Only the scripts that start with `node` or the name of a dependency located insi
The runtime provides a `WEB_PORT` environment variable matching the port used by default by the in-app web browser. If your sandbox doesn't use the port in that environment variable, then you will need to fix the URL in the web browser to load the page on the right port.
### Why does my sandbox stop running when I move the app to the background?
+
This happens because iOS suspends the process while the application is in the background, which also suspends all its activity.
### My sandbox requires Node.js 14 but the app uses Node.js 12. How can I change the Node.js version?
+
The application uses a Node.js port that hasn’t been upgraded to Node.js 14 as we have been focused on integrating the new CodeSandbox experience instead. Stay tuned, as we will be making some updates.
## Repositories
### Why can't I make any changes to my project?
+
You likely have a protected branch selected (i.e. `main`). Forking a branch will create a new one where you can make changes.
-
-
\ No newline at end of file
+
+
+
diff --git a/packages/projects-docs/pages/learn/boxy/faqs.mdx b/packages/projects-docs/pages/learn/boxy/faqs.mdx
index 172ea7fe..ff531da9 100644
--- a/packages/projects-docs/pages/learn/boxy/faqs.mdx
+++ b/packages/projects-docs/pages/learn/boxy/faqs.mdx
@@ -6,15 +6,19 @@ description: Frequently asked questions
# Boxy FAQs
### How does Boxy differ from ChatGPT?
+
Although Boxy is built using GPT at its core, one key distinguishing factor is that Boxy is aware of the code in your sandbox or repository. As a result, Boxy's suggestions will consider existing patterns in your project's code.
### How do I get access to Boxy?
-Boxy and all CodeSandbox AI-powered tools are available to Personal Pro and Team Pro users. You can [upgrade](https://codesandbox.io/pro) or [start a free trial](https://codesandbox.io/pro?team) to experience development with Boxy.
+
+Boxy and all CodeSandbox AI-powered tools are available to Pro workspaces. You can [upgrade](https://codesandbox.io/pro) or start a free trial to experience development with Boxy.
### Is Boxy available in all CodeSandbox plans?
+
No. Boxy is only available to [Pro subscribers](https://codesandbox.io/pro).
### Is Boxy available for browser sandboxes?
+
No. Boxy is exclusively available in cloud sandboxes and repositories. However, you can easily [fork a browser sandbox into a cloud sandbox](/tutorial/convert-browser-sandbox-cloud) to get access to Boxy. This is available through the "sparkles" icon at the bottom of the left sidebar, as seen below.
-
\ No newline at end of file
+
diff --git a/packages/projects-docs/pages/learn/images/teams-new.jpg b/packages/projects-docs/pages/learn/images/teams-new.jpg
deleted file mode 100644
index 2fa4347f..00000000
Binary files a/packages/projects-docs/pages/learn/images/teams-new.jpg and /dev/null differ
diff --git a/packages/projects-docs/pages/learn/images/teams-new.png b/packages/projects-docs/pages/learn/images/teams-new.png
new file mode 100644
index 00000000..0e19197d
Binary files /dev/null and b/packages/projects-docs/pages/learn/images/teams-new.png differ
diff --git a/packages/projects-docs/pages/learn/images/workspace-selector-newteam.png b/packages/projects-docs/pages/learn/images/workspace-selector-newteam.png
index 491399ca..e6e27c65 100644
Binary files a/packages/projects-docs/pages/learn/images/workspace-selector-newteam.png and b/packages/projects-docs/pages/learn/images/workspace-selector-newteam.png differ
diff --git a/packages/projects-docs/pages/learn/plans/_meta.json b/packages/projects-docs/pages/learn/plans/_meta.json
index 199a6a33..572f4318 100644
--- a/packages/projects-docs/pages/learn/plans/_meta.json
+++ b/packages/projects-docs/pages/learn/plans/_meta.json
@@ -2,7 +2,7 @@
"plan-overview": "Choosing a plan",
"workspace": "Workspaces",
"pricing-faq": "Pricing FAQ",
- "permissions": "User Permissions",
+ "permissions": "User permissions",
"preferences": "Preferences",
"trials": "Trials"
}
diff --git a/packages/projects-docs/pages/learn/plans/plan-overview.mdx b/packages/projects-docs/pages/learn/plans/plan-overview.mdx
index ef067ea3..1037ae37 100644
--- a/packages/projects-docs/pages/learn/plans/plan-overview.mdx
+++ b/packages/projects-docs/pages/learn/plans/plan-overview.mdx
@@ -7,28 +7,29 @@ import { Callout } from 'nextra-theme-docs'
# Plans
-## Personal
-Everyone that signs up to CodeSandbox gets a free personal workspace. Here you can work on unlimited public sandboxes and repositories. If you want to work on anything private or work in collaboration with others, you will need a Pro subscription.
+## Free
-## Pro
-Pro offers unlimited collaboration, umlimited sandboxes and repositories (both private and public), higher VM specs and [much more](https://codesandbox.io/pricing).
+Free workspaces are a great way to get started with CodeSandbox. By simply creating an account and opening a workspace, you can create any public sandbox or import any public repository.
+Additionally, you may invite others to join the workspace so that you can collaborate on sandboxes or repositories.
+If at any time you need access to private sandboxes or repos, or are in need of higher VMs, a trial provides access to 2 weeks of free access to Pro.
+## Pro
+Pro offers unlimited collaboration, unlimited sandboxes and repositories (both private and public), higher VM specs and [much more](https://codesandbox.io/pricing).
-### Creating a new Pro worksapce
+### Creating a new Pro workspace
1. Go to the [Dashboard](https://codesandbox.io/dashboard).
2. Open the workspace selector and click on the `Create a Pro workspace` button at the bottom.
-3. Select `Start Trial` or `Create a Pro workspace` depending on your elibility for a trial.
-3. Choose a **workspace name**.
-4. Add **members** by inviting them via email or searching for their CodeSandbox username.
-
-
+3. Select `Start Trial` or `Create a Pro workspace` depending on your eligibility for a trial.
+4. Choose a **workspace name**.
+5. Add **members** by inviting them via email or searching for their CodeSandbox username.
+
### Add or remove people from a workspace
1. Go to the [Dashboard](https://codesandbox.io/dashboard).
-1. In the top left corner, select the **team** you'd like to edit in the dropdown.
+1. In the top left corner, select the **team** you'd like to edit in the dropdown.
1. Click on the **settings** icon next to the team.
1. Add or remove people through the **Members** section by inviting them via email or searching for their CodeSandbox username.
diff --git a/packages/projects-docs/pages/learn/plans/trials.mdx b/packages/projects-docs/pages/learn/plans/trials.mdx
index 3a4ab8c9..b1ca3aa4 100644
--- a/packages/projects-docs/pages/learn/plans/trials.mdx
+++ b/packages/projects-docs/pages/learn/plans/trials.mdx
@@ -29,7 +29,7 @@ By adding your team members to CodeSandbox, you can experience the possibilities
This means that you can simply share the link of a PR or branch with anyone from your workspace to get timely feedback and shorten the review cycle.
-### More VM Specs
+### More VM specs
Our Pro trial allows teams to work with higher VM specs, thereby reducing potential frustration with speed or memory limits. This is especially important when you are working with more complex codebases.
### Access to private repositories
diff --git a/packages/projects-docs/pages/learn/plans/workspace.mdx b/packages/projects-docs/pages/learn/plans/workspace.mdx
index 08dbf718..14962a8d 100644
--- a/packages/projects-docs/pages/learn/plans/workspace.mdx
+++ b/packages/projects-docs/pages/learn/plans/workspace.mdx
@@ -1,69 +1,68 @@
---
-title: Teams
+title: Workspaces
authors: ['CompuIves']
description:
- A team makes it easier to collaborate on code with others. In a team you share
+ A workspace makes it easier to collaborate on code with others. In a workspace, you share
ownership of repositories, sandboxes and templates.
---
import { Callout } from 'nextra-theme-docs'
# Workspaces
-
-
-CodeSandbox uses **Workspaces** to provide boundaries for collaboration on CodeSandbox. [Personal workspace](#personal-workspace) are available to all users for public, individual development work. [Pro workspaces](#pro-workspace), on the other hand are reserved for any type of work requiring privacy or collaboration with others.
-
-Every sandbox belongs to a workspace, and every branch of a repository has a separate development environment in each workspace. If you are working on something in your personal workspace and decide to collaborate with others, it may be necessary to transfer (in the case of a sandbox) or re-import (in the case of a repository) your work to a Pro workspace.
-## Personal Workspace
-
-By default, when you set up an account, you have a free personal workspace. This is a free space to create, prototype and build anything you like. You can think of this as your starting point for any personal, public projects. The personal workspace contains any public sandboxes and repositories you added while active in your workspace.
+
-**Sandboxes**: Your personal workspace contains any public sandboxes created while your personal workspace. If you want to make any of these sandboxes unlisted or private, you will need to create a [Pro workspace](##pro-workspace) and transfer the sandboxes to that workspace.
+CodeSandbox uses **Workspaces** to provide boundaries for collaboration on CodeSandbox. [Free workspaces](#free-workspace) are available to all users for public development work. [Pro workspaces](#pro-workspace), on the other hand, are reserved for any type of work requiring privacy or collaboration with others.
-**Repositories**: Personal workspaces also contain any public repositories that are imported while that workspace was active. To collaborate with others, you will have to re-import the repository to a team workspace that includes your collaboration partners.
+Every sandbox belongs to a workspace, and every branch of a repository has a separate development environment in each workspace. If you are working on something in one workspace and decide to collaborate with users who are in a different workspace, it may be necessary to transfer (in the case of a sandbox) or re-import (in the case of a repository) into a workspace that your workspace members have access to.
-
+## Getting started with workspaces
-Your personal workspace also contains a section for your [open source contributions](/learn/getting-started/open-source#introducing-contribution-branches).
+When you create an account, you will be taken through a flow to create your first workspace. From here you can choose to upgrade this workspace to Pro or continue using the free workspace.
-
+Free workspaces are a great way to get started with CodeSandbox.
+You may add members to your workspace anytime by navigating to the workspace settings and sending an invite to their email.
+You can also upgrade to Pro at any time to experience CodeSandbox without limits.
-### Personal Pro
-Personal Pro has been depricated in favor of [Pro workspaces](##pro-workspace). Existing personal Pro subscriptions will continue to be supported in their current form.
+Currently, every account must be associated with at least one workspace. In the future, we will introduce more flexibility that will allow you to change and delete your primary workspace.
+## Collaboration on workspaces
-## Pro Workspace
+You can add as many members to a workspace as you like. You can invite them when you are creating the workspace for the first time, or later through the subscription management view.
-Pro workspaces are for private development and collaboration.
-If you want to work together with a friend or colleague on a sandbox or repository, start by creating a Pro workspace and inviting them to join you.
+
-**Sandboxes**: Anyone with edit permi to the Pro workspace can edit its sandboxes. If you want to collaborate live with workspace members, you can start a [live session](/learn/getting-started/collaborate-share) (with a Pro subscription).
+Users with an active CodeSandbox account will get a notification (the bell icon in the header) in CodeSandbox as well as an email.
+From there, they can accept or decline the invitation.
-**Repositories**: Similarly, anyone with edit access to the team workspace can edit its repositories — as long as they also have write access to the repository on the git provider (such as GitHub). Branches have their own development environments for each workspace, so files saved on `my-branch` of a repository in your personal workspace will not appear on `my-branch` in the team workspace until they are committed and pushed to the git provider.
+You can also invite workspace members who do not have a CodeSandbox account. They will be sent an email inviting them to create an account where they will have access to the workspace.
-### Creating a Pro workspace
+#### Collaborating on sandboxes
-You can create a Pro workspace from the workspace selector:
+Anyone with edit permissions to the workspace can edit its sandboxes.
-
+Sandboxes are tied to the workspace. Anyone in the workspace can move sandboxes between folders—however, only the creator of a sandbox can permanently delete a sandbox.
+Admins may move sandboxes to different workspaces. This is done by right-clicking on a sandbox in the dashboard, selecting `Move to folder` and selecting a different workspace from the menu.
+If you want to collaborate live with workspace members, you can start a [live session](/learn/getting-started/collaborate-share) (with a Pro subscription).
-### Inviting People to a workspace
+#### Collaborating on repositories
-You can add as many members to a Pro workspace as you like. You can invite them when you are creating the workspace for the first time, or later through the subscription management view.
+Similarly, anyone with edit access to the team workspace can edit its repositories—as long as they also have write access to the repository on the git provider (such as GitHub). Branches have their own development environments for each workspace, so files saved on `my-branch` of a repository in your personal workspace will not appear on `my-branch` in the team workspace until they are committed and pushed to the git provider.
-
+Live collaboration on branches is restricted to members of the same workspace. If you don't see your collaboration partners working, you may be looking at the same branch in a different workspace. Otherwise, your work will be visible in every workspace as soon as it is committed and pushed to the git provider.
-Users with an active CodeSandbox account will get a notification (the bell icon in the header) in CodeSandbox as well as an email.
-From there, they can accept or decline the invitation.
+You can learn more about how to work with collaborators in the sections on [repository](/learn/repositories/collaborate-share) collaboration.
+
+## Creating a new workspace
-You can also invite workspace members that do not have a CodeSandbox account. They will be sent an email inviting them to create an account where they will have access to the workspace.
+You can create a workspace directly from the workspace selector:
+
-### Managing workspaces and subscriptions
+## Managing workspaces and subscriptions
You can create and manage workspaces from the dashboard settings page.
To find this, select your workspace and open the subscription page.
@@ -71,32 +70,35 @@ To find this, select your workspace and open the subscription page.
Here you can see the team overview with subscription details, team members and roles.
-Admins can edit team member access and roles here as well as edit the subscription.
+Admins can edit team member access and roles here as well as edit the subscription.
+## Transitioned personal workspaces
-**Free Team**
+As of Nov 12, 2023, all personal workspaces act as standard workspaces.
+Previously, everyone who signed up for a CodeSandbox account would automatically have a personal workspace created for them.
+This workspace would hold:
-
-Free teams have been depricated. Existing free team subscriptions will continue to be supported in their current form.
-
+- your account details
+- your contribution branches
+- all the sandboxes created in the workspace
-### Collaboration in workspaces
+However, there was no option to add people to the workspace or upgrade the space.
+With the recent changes, every workspace will be treated the same. This means that workspaces that were previously a Free Personal can do the following:
-You can learn how to work with collaborators in the sections on [repository](/learn/repositories/collaborate-share) and [sandbox]() collaboration
+#### Add collaborators
-#### Sandboxes access
+Just like in a Pro workspace, you may add members to the workspace by navigating to the workspace settings, and either sending an invite URL or entering the email address of the member you wish to add (they will be notified by email).
-Sandboxes are tied to the workspace. Anyone in the workspace can move sandboxes between folders, however only the creator a sandbox can permenatly delete a sandbox.
-Admins may move sandboxes to different workspaces. This is done by opening the right-clicking on a sandbox in the dashboard, selecting `Move to folder` and selecting a different workspace from the menu.
+#### Upgrade to Pro
-#### Collaborating on sandboxes
+Every workspace can now be upgraded. By selecting any action to upgrade from within a workspace, you will be able to remove free limitations from any workspace and access all Pro features on the sandboxes and repos that already exist in that space.
-You and other members of a workspace can open a sandbox at the same time and see each other's cursor to work together. You can still invite other people who aren't members of the team to the sandbox or host a [live session](/learn/getting-started/collaborate-share).
+#### Access account details from any workspace
-#### Collaborating on repositories
-
-While sandboxes belong to only one workspace, repositories can exist in multiple workspaces at once. This means that users with write access to a repository may import it to their personal workspace while another team may import the same repository to work on it together.
+Account information is now held in a separate account view. You can access it from the main menu within `Preferences`.
-Live collaboration on branches is restricted to members of the same workspace. If you don't see your collaboration partners working, you may be looking at the same branch in a different workspace. Otherwise, your work will be visible in every workspace as soon as it is committed and pushed to the git provider.
+
+If you have a legacy Personal Pro account, some of these options may vary.
+
diff --git a/packages/projects-docs/pages/learn/repositories/getting-started/configure-vscode.mdx b/packages/projects-docs/pages/learn/repositories/getting-started/configure-vscode.mdx
index d9772efd..5c29381d 100644
--- a/packages/projects-docs/pages/learn/repositories/getting-started/configure-vscode.mdx
+++ b/packages/projects-docs/pages/learn/repositories/getting-started/configure-vscode.mdx
@@ -33,4 +33,4 @@ If you want to have some personal extensions available in any CodeSandbox branch
"GitHub.copilot",
"eamodio.gitlens"
]
-```
\ No newline at end of file
+```