Skip to content

Commit 696703f

Browse files
committed
update overview content
1 parent c5f018d commit 696703f

File tree

3 files changed

+19
-85
lines changed

3 files changed

+19
-85
lines changed

packages/projects-docs/pages/learn/devboxes/overview.mdx

+5-25
Original file line numberDiff line numberDiff line change
@@ -14,18 +14,12 @@ We generally recommend using Devboxes, which provide all the tooling needed for
1414

1515
Previously known as Cloud Sandboxes, Devboxes are a great way to work on any type of project, regardless of its language or size. Devboxes run [VMs](/learn/environment/vm) and leverage our memory snapshotting to spin up an environment in 1.5 seconds. They have built-in [Docker support](/learn/environment/docker) and include several valuable features, such as [AI](/learn/ai/overview), collaborative [Terminals](/learn/repositories/terminal), [Tasks](/learn/repositories/task), and [VS Code integration](/learn/getting-started/setting-up-vscode).
1616

17-
<Callout>
18-
Devboxes are built for scale. Our Free plan includes generous VM specs but you can easily [start a Pro trial](https://codesandbox.io/pro) to improve them.
17+
<Callout type="info" emoji="ℹ️">
18+
Devboxes run on VM credits. Check out the [plans page](/learn/plans/subscriptions) to learn how these credits work.
1919
</Callout>
2020

21-
## Creating a Devbox
22-
To create a new Devbox, you can clone a template from our ["Create Devbox"](https://codesandbox.io/d) modal. When clicking on a template, we create a fork (a copy) of the template and open the newly created sandbox in our web editor.
23-
24-
## Difference between Devboxes & Sandboxes
25-
26-
<Tabs tabs={["Devbox", "Sandbox"]}>
27-
<WrapContent>
2821
## What is a Devbox?
22+
2923
Unlike Sandboxes that run on your browser, Devboxes run on our [VMs](/learn/environment/vm).
3024

3125
Devboxes are great for prototyping any type of project in any programming language. They can run both backend and front-end services.
@@ -44,21 +38,7 @@ Unlike Sandboxes that run on your browser, Devboxes run on our [VMs](/learn/envi
4438
- Full integration with GitHub
4539

4640
To configure a Devbox, you can read more about [tasks](https://codesandbox.io/docs/learn/repositories/task) and [Docker](https://codesandbox.io/docs/learn/environment/docker).
47-
</WrapContent>
48-
<WrapContent>
49-
## What is a Sandbox?
50-
When using Sandboxes, your code is evaluated and run in our built-in
51-
execution environment. These client environments run entirely inside of your browser and will continue to
52-
bundle your code even when you lose your connection to our servers.
5341

54-
Sandboxes each have their own bundler attached to them which is
55-
configured to support a specific framework and emulate their official CLI tools.
56-
They are not one-to-one implementations and thus do not support advanced
57-
configuration like custom webpack configurations or ejecting. However, they are
58-
designed to mirror the default behavior of the framework.
59-
60-
If your project requires the use of a terminal or any additional advanced configuration like Docker, you can use a [Devbox](/learn/sandboxes/overview?tab=cloud) instead.
61-
62-
</WrapContent>
42+
## Creating a Devbox
6343

64-
</Tabs>
44+
To create a new Devbox, you can clone a template from our ["Create Devbox"](https://codesandbox.io/d) modal. When clicking on a template, we create a fork (a copy) of the template and open the newly created sandbox in our web editor.

packages/projects-docs/pages/learn/guides/_meta.json

+2-2
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
"href": "/learn/devboxes/your-first-sandbox"
99
},
1010
"setting-up-vscode": {
11-
"title": "Getting started with VS Code",
12-
"href": "/learn/editors/vscode/setting-up-vscode"
11+
"title": "Getting started with VS Code Desktop",
12+
"href": "/learn/editors/desktop-setup"
1313
}
1414
}

packages/projects-docs/pages/learn/index.mdx

+12-58
Original file line numberDiff line numberDiff line change
@@ -13,71 +13,25 @@ import { Tabs, WrapContent } from '../../../../shared-components/Tabs'
1313

1414
![](./images/cover-projects.jpg)
1515

16-
CodeSandbox provides instant cloud development environments that keep you in flow.
16+
CodeSandbox provides instant development environments that get you up and running quickly and keep you in flow.
1717

18-
Our microVM infrastructure makes it easy for you to spin up a development environment in the cloud and start working on it, whether it's a small prototype or a big monolith with multiple services.
18+
We provide dozens of templates to start from or the option to import your own repository or Sandbox.
1919

20-
To use CodeSandbox for cloud development with a strong GitHub integration, we recommend using [Repositories](/learn/repositories/overview). If you want to prototype an idea or create a demo, we recommend using [Devboxes](/learn/devboxes/overview).
20+
The code can run on either the browser or in a virutal machine. Projects that run in the browser are called Sandboxes and projects that run on virtual machines (VMs) are called Devboxes.
2121

22-
## Editors
23-
24-
We provide many alternatives for you to code. Each option is built to help you focus on what matters: getting the work done without friction.
25-
26-
<Tabs tabs={["Web Editor", "VS Code", "iOS"]}>
27-
28-
<WrapContent>
29-
30-
## Unified Platform Editor
31-
32-
In November 2023 we launched the latest version of our web editor. Leveraging the power of VSCode, our new editor offers a seamless experience whether you're coding a basic front end demonstration in a [Sandbox](/learn/devboxes/editors?tab=sandbox) or building a full stack prototype in a [Devbox](/learn/devboxes/editors?tab=devbox).
33-
While there are some feature differences between the two environments. The Editor experience and layout is consistent on CodeSandbox, regardless of your start point. You can also easily convert Sandboxes to Devboxes when you're ready to take any of your projects to the next level.
34-
35-
## V1 Sandbox Editor
36-
37-
Known and loved for years, our original editor was built for rapid web development using only the power of the browser. All the features from this editor are gradually being added to the Unified Platfrom Editor. However, the browser editor remains available to everyone who still calls it home.
38-
39-
[Learn more](/learn/legacy-sandboxes/overview)
40-
41-
<Callout>
42-
The V1 Editor only works with Browser Sandboxes. You can opt out of the Unified Platform (Beta) editor in your [Experiments Settings](https://codesandbox.io/dashboard/recent?preferences=experiments)
43-
</Callout>
44-
45-
</WrapContent>
22+
## Devboxes
4623

47-
<WrapContent>
48-
## Easily move between web and VS Code
24+
Devboxes are powerful and versatile. Offering support for a wide range of language and frameworks. Devboxes are built to scale as your project grows. Learn more about Devboxes and VM runtimes [here](/learn/devboxes/overview)
4925

50-
Any project running in a cloud web editor may also be run in VS Code. Work from your local environment with your own configurations and shortcuts whilst remaining connected to the CodeSandbox development environment.
26+
To use CodeSandbox for cloud development with a strong GitHub integration, we recommend using [Repositories](/learn/repositories/overview).
5127

52-
**Install the CodeSandbox VS Code extension and open any branch or Devbox directly in your VS Code editor.**
28+
## Sandboxes
5329

54-
[Install VS Code Extension](https://marketplace.visualstudio.com/items?itemName=CodeSandbox-io.codesandbox-projects)
30+
Sandboxes, on the other hand are ideal for prototyping and sharing code snippets.
31+
When using Sandboxes, your code is evaluated and run in our built-in execution environment. These client environments run entirely inside of your browser and will continue to bundle your code even when you lose your connection to our servers.
5532

56-
## Opening a branch in VS Code
33+
Sandboxes each have their own bundler attached to them which is configured to support a specific framework and emulate their official CLI tools. They are not one-to-one implementations and thus do not support advanced configuration like custom webpack configurations or ejecting. However, they are designed to mirror the default behavior of the framework.
5734

58-
![Open in vscode button](./images/getting-openvscode.jpg)
59-
60-
To start working on a branch on VS Code, open the branch in the Editor and click on the `Open in VS Code` button positioned in the bottom left corner. This will prompt you to install the CodeSandbox extension responsible for making the connection to our cloud development environment.
61-
62-
### Learn more
63-
64-
To get the most from your local setup, check our [VS Code Extension documentation](/learn/editors/vscode/overview).
65-
66-
</WrapContent>
67-
68-
<WrapContent>
69-
## Keep working on the iPad or iPhone
70-
71-
![iOS-App](./images/iOS-iPad.jpg)
72-
73-
<Callout emoji="ℹ️">
74-
The CodeSandbox for iOS app is currently not supported.
75-
</Callout>
76-
77-
**CodeSandbox for iOS** is a fully native development environment that brings the power of modern software development to your iOS device. Use your iPhone or iPad to develop any kind of application or collaborate in real time with others.
78-
79-
[Go to the App Store](https://apps.apple.com/us/app/codesandbox/id1423330822)
35+
## Editors
8036

81-
</WrapContent>
82-
83-
</Tabs>
37+
Both Sandboxes and Devboxes run on a version of VS Code for the web. You can learn more about the editor [here](/learn/editors/overview)

0 commit comments

Comments
 (0)