chore: redirect to docs (#454)

Author: jrvidal

README.md

@@ -6,7 +6,7 @@ This repository serves as a coordination point for the WebContainer™ working g
 
 |![](https://raw.githubusercontent.com/alrra/browser-logos/master/src/chrome/chrome_48x48.png)<br>Chrome|![](https://raw.githubusercontent.com/alrra/browser-logos/master/src/edge/edge_48x48.png)<br>Edge|![](https://raw.githubusercontent.com/alrra/browser-logos/master/src/brave/brave_48x48.png)<br>Brave|![](https://raw.githubusercontent.com/alrra/browser-logos/master/src/safari/safari_48x48.png)<br>Safari|![](https://raw.githubusercontent.com/alrra/browser-logos/master/src/firefox/firefox_48x48.png)<br>Firefox|
 |:---:|:---:|:---:|:---:|:---:|
-|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:<br>[Config needed](browsers/brave/brave.md)|:soon:|:soon:|
+|:heavy_check_mark:|:heavy_check_mark:|:heavy_check_mark:<br>[Config needed](https://developer.stackblitz.com/docs/platform/brave-support)|:soon:|:soon:|
 
 ## Explainer
 

browsers/brave/1-stuck-project.png

@@ -1,27 +1 @@
-# Running WebContainer in Brave Browser
-
-WebContainer — the technology behind Node.js projects on StackBlitz — does work in Brave. However, it requires a small configuration change.
-
-## What’s the problem?
-
-By default, Brave’s “Shields” feature blocks [Service Workers](https://developer.mozilla.org/en-US/docs/Web/API/Service_Worker_API) and cookies from third-party domains.
-
-When you visit a WebContainer-enabled project on [stackblitz.com](https://www.stackblitz.com/), StackBlitz tries to register a Service Worker for the domain `<project_name>.stackblitz.io`. Since it’s considered a third-party domain, Brave will reject it.
-
-## How to allow third-party service workers for stackblitz.com
-
-1. Visit a WebContainer-based project, for instance https://www.stackblitz.com/edit/nextjs. The project’s boot sequence might stay stuck on the “Running start command” step:
-
-<img src="1-stuck-project.png" width="784" alt="Screenshot of Brave on a WebContainer project with the Brave Shields feature on. Loading the project’s web server is stuck on the last step.">
-
-2. Click on the “Shields” icon at the right of the address bar, then click on “Advanced View”.
-
-<img src="2-shields-popup.png" width="380" alt="Screenshot showing the Shields configuration popup for stackblitz.com.">
-
-3. In the advanced view, change the “Cross-site cookies blocked” option to “All cookies allowed”.
-
-<img src="3-shields-details.png" width="760" alt="Screenshot showing the advanced view of the Shields configuration popup, with a drop-down selector for cross-site cookie permissions.">
-
-Brave will reload the page, and you should get a working project:
-
-<img src="4-working-project.png" width="784" alt="Screenshot of Brave on a WebContainer project with the Brave Shields feature tweaked to allow third-party cookies and Service Workers. Loading the web server works, and shows the default page for Next.js’s starter project.">
+Moved to https://developer.stackblitz.com/docs/platform/brave-support