diff --git a/docs/enterprise/adfs-sso.md b/docs/enterprise/adfs-sso.md
index 14e9ca2b..80a93ceb 100644
--- a/docs/enterprise/adfs-sso.md
+++ b/docs/enterprise/adfs-sso.md
@@ -19,7 +19,10 @@ StackBlitz is excited to offer SAML-based Single Sign-on (SSO) to organizations
## StackBlitz Admin Panel Auth Settings Page
:::warning IMPORTANT:
-Admin accounts should not be made with an individual work email that will be used to create a separate user account later. Should this happen, we recommend the following steps:
+Each user account (including the Admin User) must have a unique email address. Use a service account email address (like IT@yourcompany.com) to ensure that the admin account doesn't cause email collisions for SSO users. If your admin email address matches an SSO user's email address, said SSO user will receive an "invalid login or password" error when signing in.
+\
+
+Should this happen, we recommend the following steps:
- Log in as admin
- Navigate to `https://editor.stackblitz.[COMPANY.COM]/users/edit` to change your email address to a different one. It will show the same screen as the changing email/password when first logging in as an admin, but you only need to change your email.
:::
diff --git a/docs/enterprise/assets/okta-sso/okta-integration-5.png b/docs/enterprise/assets/okta-sso/okta-integration-5.png
index 8455176b..9853d530 100644
Binary files a/docs/enterprise/assets/okta-sso/okta-integration-5.png and b/docs/enterprise/assets/okta-sso/okta-integration-5.png differ
diff --git a/docs/enterprise/assets/saml-config.png b/docs/enterprise/assets/saml-config.png
index 2617fae2..7892f82e 100644
Binary files a/docs/enterprise/assets/saml-config.png and b/docs/enterprise/assets/saml-config.png differ
diff --git a/docs/enterprise/installation/quickstart-gcp.md b/docs/enterprise/installation/quickstart-gcp.md
index f90fb77d..6c717b0f 100644
--- a/docs/enterprise/installation/quickstart-gcp.md
+++ b/docs/enterprise/installation/quickstart-gcp.md
@@ -28,6 +28,8 @@ Getting started on GCP (no GKE, no existing cluster):
- 8080
- 6443
- Run the kots intaller command: `curl -sSL https://k8s.kurl.sh/stackblitz | sudo bash`.
+ - **Note:** The KURL installer may prompt some packages for manual installation.
+ See: [Host Package Requirements](https://kurl.sh/docs/add-ons/kubernetes#host-package-requirements).
:::tip Using load balancers?
Ports 80 and 443 should be forwarded from the load balancer. The remaining ports are for inbound rules on the security group.
diff --git a/docs/enterprise/installation/quickstart.md b/docs/enterprise/installation/quickstart.md
index 0b560fcd..d8b2eb15 100644
--- a/docs/enterprise/installation/quickstart.md
+++ b/docs/enterprise/installation/quickstart.md
@@ -27,6 +27,8 @@ Getting started on bare metal (no existing Kubernetes cluster):
- 8080
- 6443
- Run the kots intaller command: `curl -sSL https://k8s.kurl.sh/stackblitz | sudo bash`.
+ - **Note:** The KURL installer may prompt some packages for manual installation.
+ See: [Host Package Requirements](https://kurl.sh/docs/add-ons/kubernetes#host-package-requirements).
:::tip Using load balancers?
Ports 80 and 443 should be forwarded from the load balancer. The remaining ports are for inbound rules on the security group.
diff --git a/docs/enterprise/okta-sso.md b/docs/enterprise/okta-sso.md
index 530c4539..5b805a43 100644
--- a/docs/enterprise/okta-sso.md
+++ b/docs/enterprise/okta-sso.md
@@ -19,7 +19,10 @@ StackBlitz SAML integration relies on a user-level token. To ensure consistent d
### Navigate to Auth Settings Page Within the Admin Panel
:::warning IMPORTANT:
-Admin accounts should not be made with an individual work email that will be used to create a separate user account later. Should this happen, we recommend the following steps:
+Each user account (including the Admin User) must have a unique email address. Use a service account email address (like IT@yourcompany.com) to ensure that the admin account doesn't cause email collisions for SSO users. If your admin email address matches an SSO user's email address, said SSO user will receive an "invalid login or password" error when signing in.
+\
+
+Should this happen, we recommend the following steps:
- Log in as admin
- Navigate to `https://editor.stackblitz.[COMPANY.COM]/users/edit` to change your email address to a different one. It will show the same screen as the changing email/password when first logging in as an admin, but you only need to change your email.
:::
@@ -43,7 +46,7 @@ Next, fill out the `App name` for the SAML integration. This is what the App wil
On the next page, you'll need to fill out a few options using values from the Auth Settings page in the StackBlitz admin dashboard.
- For the `Single sign on URL`, use the `Assertion Customer Service URL` from the StackBlitz Auth Settings page.
-- For `Audience URI (SP Entity ID)`, choose an identifier for the SAML application. We recommend using `stackblitz`. Use the same value in your StackBlitz SAML settings for `Issuer (Service Provider Entity ID)`.
+- For `Audience URI (SP Entity ID)`, choose an identifier for the SAML application. We recommend using `stackblitz`. Use the same value in your StackBlitz SAML settings for `Client ID (Service Provider Entity ID / Issuer)`.
- In the `Attribute Statements (optional)` section, you must configure the `email` and `name` attributes for your users. We recommend using `user.email` for the `email` attribute, and `user.firstName + " " + user.lastName` for the `name` attribute.
diff --git a/docs/enterprise/sso.md b/docs/enterprise/sso.md
index a070a217..89a781c0 100644
--- a/docs/enterprise/sso.md
+++ b/docs/enterprise/sso.md
@@ -17,10 +17,15 @@ StackBlitz SAML integration relies on a user-level token. To ensure consistent d
- StackBlitz offers just-in-time provisioning. This means that if a user logs into StackBlitz for the first time using SSO, an account will automatically be created.
:::
+
+
### Configure your IdP
:::warning IMPORTANT:
-Admin accounts should not be made with an individual work email that will be used to create a separate user account later. Should this happen, we recommend the following steps:
+Each user account (including the Admin User) must have a unique email address. Use a service account email address (like IT@yourcompany.com) to ensure that the admin account doesn't cause email collisions for SSO users. If your admin email address matches an SSO user's email address, said SSO user will receive an "invalid login or password" error when signing in.
+\
+
+Should this happen, we recommend the following steps:
- Log in as admin
- Navigate to `https://editor.stackblitz.[COMPANY.COM]/users/edit` to change your email address to a different one. It will show the same screen as the changing email/password when first logging in as an admin, but you only need to change your email.
:::
@@ -57,4 +62,4 @@ Please ensure that the email addresses in the IdP are what your users will be us
### Troubleshooting
-If you're unable to login after verifying these things, please reach out to [enterprise@stackblitz.com](mailto:enterprise@stackblitz.com) for support.
\ No newline at end of file
+If you're unable to login after verifying these things, please reach out to [enterprise@stackblitz.com](mailto:enterprise@stackblitz.com) for support.
diff --git a/docs/platform/api/javascript-sdk.md b/docs/platform/api/javascript-sdk.md
index 30ed982f..9714f581 100644
--- a/docs/platform/api/javascript-sdk.md
+++ b/docs/platform/api/javascript-sdk.md
@@ -8,6 +8,11 @@ og_image: javascript-sdk.png
The StackBlitz JavaScript SDK lets you programmatically create StackBlitz projects to be opened in a new window or embedded in your docs, example pages, or blog posts. Once embedded, the projects can be controlled by using [the SDK’s VM interface][sdk_vm_docs].
+:::tip Interactive Tutorial
+In addition to this guide, you can also play with our _interactive_ StackBlitz SDK tutorial (build with [TutorialKit](https://tutorialkit.dev/)): [StackBlitz SDK Tutorial](https://stackblitz-sdk-tutorial.pages.dev/)
+:::
+
+
## Install the SDK
The SDK is _3kB gzipped_ and can be installed from npm:
diff --git a/docs/platform/webcontainers/assets/chrome-memory-saver.png b/docs/platform/webcontainers/assets/chrome-memory-saver.png
index abceddf6..65648356 100644
Binary files a/docs/platform/webcontainers/assets/chrome-memory-saver.png and b/docs/platform/webcontainers/assets/chrome-memory-saver.png differ
diff --git a/docs/platform/webcontainers/assets/chrome-settings-cookies-1.png b/docs/platform/webcontainers/assets/chrome-settings-cookies-1.png
index 109322f4..357ef610 100644
Binary files a/docs/platform/webcontainers/assets/chrome-settings-cookies-1.png and b/docs/platform/webcontainers/assets/chrome-settings-cookies-1.png differ
diff --git a/docs/platform/webcontainers/assets/chrome-settings-cookies-2.png b/docs/platform/webcontainers/assets/chrome-settings-cookies-2.png
index a4105a48..1702fb5a 100644
Binary files a/docs/platform/webcontainers/assets/chrome-settings-cookies-2.png and b/docs/platform/webcontainers/assets/chrome-settings-cookies-2.png differ
diff --git a/docs/platform/webcontainers/assets/chrome-settings-cookies-3.png b/docs/platform/webcontainers/assets/chrome-settings-cookies-3.png
index 4288835b..a720c08f 100644
Binary files a/docs/platform/webcontainers/assets/chrome-settings-cookies-3.png and b/docs/platform/webcontainers/assets/chrome-settings-cookies-3.png differ
diff --git a/docs/platform/webcontainers/assets/chrome-settings-popups.png b/docs/platform/webcontainers/assets/chrome-settings-popups.png
index b8de4ec3..01aaf569 100644
Binary files a/docs/platform/webcontainers/assets/chrome-settings-popups.png and b/docs/platform/webcontainers/assets/chrome-settings-popups.png differ
diff --git a/docs/platform/webcontainers/assets/firefox-settings-cookies-2.png b/docs/platform/webcontainers/assets/firefox-settings-cookies-2.png
index fe100a56..3c026404 100644
Binary files a/docs/platform/webcontainers/assets/firefox-settings-cookies-2.png and b/docs/platform/webcontainers/assets/firefox-settings-cookies-2.png differ
diff --git a/docs/platform/webcontainers/assets/firefox-settings-popups.png b/docs/platform/webcontainers/assets/firefox-settings-popups.png
index 55d1d23c..60d39ec9 100644
Binary files a/docs/platform/webcontainers/assets/firefox-settings-popups.png and b/docs/platform/webcontainers/assets/firefox-settings-popups.png differ
diff --git a/docs/platform/webcontainers/browser-config.md b/docs/platform/webcontainers/browser-config.md
index 5e4e5b4b..a66d5305 100644
--- a/docs/platform/webcontainers/browser-config.md
+++ b/docs/platform/webcontainers/browser-config.md
@@ -30,6 +30,7 @@ This can happen automatically if your popups settings, [chrome://settings/conten
```
https://[*.]webcontainer.io
+https://[*.]webcontainer-api.io
```
@@ -40,6 +41,7 @@ Lastly, if Chrome's [memory saver][CHROME_MEMORY_SAVER] is turned on, this step
```
https://webcontainer.io
+https://webcontainer-api.io
https://stackblitz.com
```
@@ -70,6 +72,7 @@ To allow all StackBlitz projects to use Service Workers, go to your browser’s
```
https://[*.]stackblitz.io
https://[*.]webcontainer.io
+https://[*.]webcontainer-api.io
```
For instance, in Chrome, go to `chrome://settings/cookies` and add those exceptions in the “Sites that can always use cookies” section.
@@ -123,6 +126,7 @@ To add exceptions for StackBlitz, scroll down to the “Cookies and Site Data”
```
https://stackblitz.io
https://webcontainer.io
+https://webcontainer-api.io
```
diff --git a/docs/public/img/logo/readme.md b/docs/public/img/logo/readme.md
new file mode 100644
index 00000000..cd31f559
--- /dev/null
+++ b/docs/public/img/logo/readme.md
@@ -0,0 +1,16 @@
+# StackBlitz Logo
+
+The files in this folder serve as a resource for third parties to access StackBlitz logos.
+
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-bolt-blue.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-bolt-white.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-black_blue.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-black.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-white_blue.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-white.svg
diff --git a/docs/public/img/logo/stackblitz-bolt-blue.svg b/docs/public/img/logo/stackblitz-bolt-blue.svg
new file mode 100644
index 00000000..2ffb7ab2
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-bolt-blue.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/public/img/logo/stackblitz-bolt-white.svg b/docs/public/img/logo/stackblitz-bolt-white.svg
new file mode 100644
index 00000000..ce0fb292
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-bolt-white.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-black.svg b/docs/public/img/logo/stackblitz-logo-black.svg
new file mode 100644
index 00000000..d14a5329
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-black.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-black_blue.svg b/docs/public/img/logo/stackblitz-logo-black_blue.svg
new file mode 100644
index 00000000..e61c10aa
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-black_blue.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-white.svg b/docs/public/img/logo/stackblitz-logo-white.svg
new file mode 100644
index 00000000..ae8e361f
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-white.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-white_blue.svg b/docs/public/img/logo/stackblitz-logo-white_blue.svg
new file mode 100644
index 00000000..67961d53
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-white_blue.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/teams/assets/project-access-settings.png b/docs/teams/assets/project-access-settings.png
new file mode 100644
index 00000000..538ccd87
Binary files /dev/null and b/docs/teams/assets/project-access-settings.png differ
diff --git a/docs/teams/collaboration-and-access-control.md b/docs/teams/collaboration-and-access-control.md
index 151df978..b31eff4b 100644
--- a/docs/teams/collaboration-and-access-control.md
+++ b/docs/teams/collaboration-and-access-control.md
@@ -12,6 +12,14 @@ By default, all StackBlitz projects created within a Team are publicly viewable
+### Team settings
+When collaborating inside a StackBlitz Team, you have these additional controls:
+- Allow or disallow team members from inviting external users to collaborate on projects created inside the team.
+- Select the highest level of external visibility (to those outside the team) allowed for projects created inside the team (private, secret, or public).
+- Default member role allows you to set the default level of access that members of the team have to newly created projects (co-owner, editor, or viewer). This can be changed on an individual project-by-project basis as well.
+
+
+
:::tip
-Currently it is not possible to hide projects (or remove edit access) from other members within the StackBlitz Team. Selecting Visibility: Private will only hide the project from users NOT in the Team. [Let us know](mailto:hello@stackblitz.com) if additional configurability here is important to you.
+Currently it is not possible to hide projects from other members within the StackBlitz Team. Selecting Visibility: Private will only hide the project from users NOT in the Team. [Let us know](mailto:hello@stackblitz.com) if additional configurability here is important to you.
:::
\ No newline at end of file
diff --git a/docs/teams/private-npm-registry-integration.md b/docs/teams/private-npm-registry-integration.md
index c4190e99..33a8d5c4 100644
--- a/docs/teams/private-npm-registry-integration.md
+++ b/docs/teams/private-npm-registry-integration.md
@@ -16,7 +16,7 @@ If you can ping/access your registry without a proxy or firewall then you can fo
These items can be found in your private npm registry server settings.
- [Jfrog Artifactory Documentation](https://jfrog.com/help/r/jfrog-artifactory-documentation/jfrog-artifactory)
- [Sonatype Nexus Documentation](https://help.sonatype.com/repomanager3)
-2. Navigate to `https://stackblitz.com/orgs/github/[YOUR_ORG_NAME]/settings` and scroll to the bottom of the page
+2. Navigate to `https://stackblitz.com/orgs/github/[YOUR_ORG_NAME]/npm_registries` and scroll to the bottom of the page
3. Click “Add new registry”
4. Enter the URL and Access Token, and click “Add registry”
diff --git a/netlify.toml b/netlify.toml
index 1469e706..e13e1b91 100644
--- a/netlify.toml
+++ b/netlify.toml
@@ -2,3 +2,4 @@
for = "/img/*"
[headers.values]
Cross-Origin-Resource-Policy = "cross-origin"
+ Access-Control-Allow-Origin = "*"
@@ -40,6 +41,7 @@ Lastly, if Chrome's [memory saver][CHROME_MEMORY_SAVER] is turned on, this step
```
https://webcontainer.io
+https://webcontainer-api.io
https://stackblitz.com
```
@@ -70,6 +72,7 @@ To allow all StackBlitz projects to use Service Workers, go to your browser’s
```
https://[*.]stackblitz.io
https://[*.]webcontainer.io
+https://[*.]webcontainer-api.io
```
For instance, in Chrome, go to `chrome://settings/cookies` and add those exceptions in the “Sites that can always use cookies” section.
@@ -123,6 +126,7 @@ To add exceptions for StackBlitz, scroll down to the “Cookies and Site Data”
```
https://stackblitz.io
https://webcontainer.io
+https://webcontainer-api.io
```
diff --git a/docs/public/img/logo/readme.md b/docs/public/img/logo/readme.md
new file mode 100644
index 00000000..cd31f559
--- /dev/null
+++ b/docs/public/img/logo/readme.md
@@ -0,0 +1,16 @@
+# StackBlitz Logo
+
+The files in this folder serve as a resource for third parties to access StackBlitz logos.
+
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-bolt-blue.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-bolt-white.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-black_blue.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-black.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-white_blue.svg
+- 
+ https://developer.stackblitz.com/img/logo/stackblitz-logo-white.svg
diff --git a/docs/public/img/logo/stackblitz-bolt-blue.svg b/docs/public/img/logo/stackblitz-bolt-blue.svg
new file mode 100644
index 00000000..2ffb7ab2
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-bolt-blue.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/public/img/logo/stackblitz-bolt-white.svg b/docs/public/img/logo/stackblitz-bolt-white.svg
new file mode 100644
index 00000000..ce0fb292
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-bolt-white.svg
@@ -0,0 +1,3 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-black.svg b/docs/public/img/logo/stackblitz-logo-black.svg
new file mode 100644
index 00000000..d14a5329
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-black.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-black_blue.svg b/docs/public/img/logo/stackblitz-logo-black_blue.svg
new file mode 100644
index 00000000..e61c10aa
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-black_blue.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-white.svg b/docs/public/img/logo/stackblitz-logo-white.svg
new file mode 100644
index 00000000..ae8e361f
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-white.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/public/img/logo/stackblitz-logo-white_blue.svg b/docs/public/img/logo/stackblitz-logo-white_blue.svg
new file mode 100644
index 00000000..67961d53
--- /dev/null
+++ b/docs/public/img/logo/stackblitz-logo-white_blue.svg
@@ -0,0 +1,13 @@
+
diff --git a/docs/teams/assets/project-access-settings.png b/docs/teams/assets/project-access-settings.png
new file mode 100644
index 00000000..538ccd87
Binary files /dev/null and b/docs/teams/assets/project-access-settings.png differ
diff --git a/docs/teams/collaboration-and-access-control.md b/docs/teams/collaboration-and-access-control.md
index 151df978..b31eff4b 100644
--- a/docs/teams/collaboration-and-access-control.md
+++ b/docs/teams/collaboration-and-access-control.md
@@ -12,6 +12,14 @@ By default, all StackBlitz projects created within a Team are publicly viewable
+### Team settings
+When collaborating inside a StackBlitz Team, you have these additional controls:
+- Allow or disallow team members from inviting external users to collaborate on projects created inside the team.
+- Select the highest level of external visibility (to those outside the team) allowed for projects created inside the team (private, secret, or public).
+- Default member role allows you to set the default level of access that members of the team have to newly created projects (co-owner, editor, or viewer). This can be changed on an individual project-by-project basis as well.
+
+
+
:::tip
-Currently it is not possible to hide projects (or remove edit access) from other members within the StackBlitz Team. Selecting Visibility: Private will only hide the project from users NOT in the Team. [Let us know](mailto:hello@stackblitz.com) if additional configurability here is important to you.
+Currently it is not possible to hide projects from other members within the StackBlitz Team. Selecting Visibility: Private will only hide the project from users NOT in the Team. [Let us know](mailto:hello@stackblitz.com) if additional configurability here is important to you.
:::
\ No newline at end of file
diff --git a/docs/teams/private-npm-registry-integration.md b/docs/teams/private-npm-registry-integration.md
index c4190e99..33a8d5c4 100644
--- a/docs/teams/private-npm-registry-integration.md
+++ b/docs/teams/private-npm-registry-integration.md
@@ -16,7 +16,7 @@ If you can ping/access your registry without a proxy or firewall then you can fo
These items can be found in your private npm registry server settings.
- [Jfrog Artifactory Documentation](https://jfrog.com/help/r/jfrog-artifactory-documentation/jfrog-artifactory)
- [Sonatype Nexus Documentation](https://help.sonatype.com/repomanager3)
-2. Navigate to `https://stackblitz.com/orgs/github/[YOUR_ORG_NAME]/settings` and scroll to the bottom of the page
+2. Navigate to `https://stackblitz.com/orgs/github/[YOUR_ORG_NAME]/npm_registries` and scroll to the bottom of the page
3. Click “Add new registry”
4. Enter the URL and Access Token, and click “Add registry”
diff --git a/netlify.toml b/netlify.toml
index 1469e706..e13e1b91 100644
--- a/netlify.toml
+++ b/netlify.toml
@@ -2,3 +2,4 @@
for = "/img/*"
[headers.values]
Cross-Origin-Resource-Policy = "cross-origin"
+ Access-Control-Allow-Origin = "*"