Remove Legacy Sandboxes docs?

Open
#246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Domain
documentation

Research direction

Start with the Legacy Sandboxes docs section at the linked overview page and review the surrounding Legacy Sandboxes content. Check whether the section is still needed after the stated end-of-2023 support period, then remove or retain the related documentation consistently. Done means the obsolete section and its references are resolved without leaving broken navigation.

Written by the indexing model from the issue text.

Description

Hi, first of all, thanks for CodeSandbox and the ecosystem, it's pushed the industry to make the whole "online editor" experience very common - especially great for reproductions.

To my request:

There's a Legacy Sandboxes docs section that says:

As of Nov 20, 2023, the Sandbox editor was replaced with a new unified editor experience that blends seamlessly into the Devbox experience. Legacy sandboxes will be supported during the beta era of the new editor (until the end of 2023).

Screenshot 2024-04-04 at 16 00 14

Now that it's past the end of 2023, should all Legacy Sandboxes docs and the section be removed?

Dominant language
MDX
Stars
21
Forks
16
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codesandbox/docs

All issues in codesandbox/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.