(chore) alphabetize sidenav; .env.local --> env; clean up /account-portal/overview#sign-in-or-up (#2060)

Author: alexisintech

CONTRIBUTING.md

@@ -420,7 +420,7 @@ You can use the following shortcodes within a code block to inject information f
 - `{{fapi_url}}` – Frontend API URL
 
 ````mdx
-```sh {{ filename: '.env.local' }}
+```sh {{ filename: '.env' }}
 NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY={{pub_key}}
 CLERK_SECRET_KEY={{secret}}
 ```

docs/advanced-usage/satellite-domains.mdx

@@ -69,7 +69,7 @@ To access authentication state from a satellite domain, users will be transparen
       - In the `.env` file associated with your primary domain:
 
         <CodeBlockTabs options={["Next.js", "Remix"]}>
-          ```env {{ filename: '.env.local' }}
+          ```env {{ filename: '.env' }}
           NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY={{pub_key}}
           CLERK_SECRET_KEY={{secret}}
           NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in
@@ -85,7 +85,7 @@ To access authentication state from a satellite domain, users will be transparen
       - In the `.env` file associated with your other (satellite) domain:
 
         <CodeBlockTabs options={["Next.js", "Remix"]}>
-          ```env {{ filename: '.env.local' }}
+          ```env {{ filename: '.env' }}
           NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY={{pub_key}}
           CLERK_SECRET_KEY={{secret}}
           NEXT_PUBLIC_CLERK_IS_SATELLITE=true

docs/advanced-usage/using-proxies.mdx

@@ -184,11 +184,11 @@ When using a proxy, all requests to the Frontend API will be made through your d
 
   #### Environment variables
 
-  To configure your proxy setup using environment variables, your `.env.local` file should look like this:
+  To configure your proxy setup using environment variables, your `.env` file should look like this:
 
   <Tabs items={["Next.js", "Remix", "JavaScript"]}>
     <Tab>
-      ```env {{ filename: '.env.local' }}
+      ```env {{ filename: '.env' }}
       NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY={{pub_key}}
       CLERK_SECRET_KEY={{secret}}
 
@@ -197,7 +197,7 @@ When using a proxy, all requests to the Frontend API will be made through your d
     </Tab>
 
     <Tab>
-      ```env {{ filename: '.env.local' }}
+      ```env {{ filename: '.env' }}
       CLERK_PUBLISHABLE_KEY={{pub_key}}
       CLERK_SECRET_KEY={{secret}}
 
@@ -208,7 +208,7 @@ When using a proxy, all requests to the Frontend API will be made through your d
     <Tab>
       You will only need to set environment variables in your JavaScript application if you are using a bundler (the `NPM module` method for ClerkJS installation). If you are using the `<script>` method, configure your proxy setup using [properties in your application](#properties-in-your-application) instead.
 
-      ```env {{ filename: '.env.local' }}
+      ```env {{ filename: '.env' }}
       CLERK_PUBLISHABLE_KEY={{pub_key}}
       CLERK_SECRET_KEY={{secret}}
 

docs/authentication/configuration/legal-compliance.mdx

@@ -3,7 +3,7 @@ title: Legal compliance
 description: Learn how to configure your legal compliance settings in the Clerk Dashboard.
 ---
 
-Clerk provides a legal compliance setting that allows you to require users to agree to your terms of service or privacy policy before they can sign up to your application. After enabling the setting, there will be a checkbox to accept the terms in your [`<SignUp />` component](/docs/components/authentication/sign-up) or [Account Portal sign-up page](/docs/account-portal/overview#sign-in-or-up).
+Clerk provides a legal compliance setting that allows you to require users to agree to your terms of service or privacy policy before they can sign up to your application. After enabling the setting, there will be a checkbox to accept the terms in your [`<SignUp />` component](/docs/components/authentication/sign-up) or [Account Portal sign-up page](/docs/account-portal/overview#sign-up).
 
 To configure the setting:
 

docs/authentication/configuration/sign-up-sign-in-options.mdx

@@ -170,7 +170,7 @@ To enable social connections:
 
 ## Web3 authentication
 
-Clerk provides [Web3 authentication](/docs/users/web3) with either MetaMask, Coinbase Wallet or OKX Wallet. As part of validating the accuracy of the returned Web3 account address, Clerk handles the signing of a message and verifying the signature. Because sign-in with Web3 uses the same abstraction as our other authentication factors, like passwords or email links, other Clerk features like multi-factor authentication and profile enrichment work for Web3 users out-of-the-box.
+Clerk provides Web3 authentication with either [MetaMask](/docs/authentication/web3/metamask), [Coinbase Wallet](/docs/authentication/web3/coinbase-wallet), or [OKX Wallet](/docs/authentication/web3/okx-wallet). As part of validating the accuracy of the returned Web3 account address, Clerk handles the signing of a message and verifying the signature. Because sign-in with Web3 uses the same abstraction as our other authentication factors, like passwords or email links, other Clerk features like multi-factor authentication and profile enrichment work for Web3 users out-of-the-box.
 
 To enable Web3 authentication:
 

docs/authentication/overview.mdx

@@ -7,6 +7,24 @@ Clerk supports multiple authentication strategies so that you can implement the
 
 ## Configuration
 
-Clerk's configuration settings affect how the users of your application can [sign up and sign in](/docs/authentication/configuration/sign-up-sign-in-options) and which properties are editable via their user profile. You can also manage [user sessions](/docs/authentication/configuration/session-options), [control who gets access](/docs/authentication/configuration/restrictions) to your application, and [customize the email & SMS messages](/docs/authentication/configuration/email-sms-templates) that are sent by Clerk during authentication flows. All of these settings can be found under the **User & Authentication** section in the [Clerk Dashboard](https://dashboard.clerk.com/).
+Configuring your application is done through the [Clerk Dashboard](https://dashboard.clerk.com). The Clerk Dashboard is where you, as the application owner, can manage your application's settings, users, and organizations. For example, if you want to enable phone number authentication, multi-factor authentication, social providers like Google, delete users, or create organizations, you can do all of this and more in the Clerk Dashboard. You can even invite other users to join your [organization workspace](/docs/organizations/organization-workspaces) and help configure and manage your application with you.
 
-For more information on how to set up your application, see the [setup guide](/docs/quickstarts/setup-clerk).
+## SSO authentication
+
+SSO authentication allows users to sign in to your application using an existing account from an external identity provider (IdP), such as Google.
+
+Clerk supports the following SSO types:
+
+- [OAuth SSO, also known as social connections or social providers](/docs/authentication/social-connections/overview)
+- [Enterprise SSO](/docs/authentication/enterprise-connections/overview)
+  - SAML
+  - OIDC
+    - EASIE
+
+## Web3 authentication
+
+Clerk supports the following Web3 providers:
+
+- [Coinbase Wallet](/docs/authentication/web3/coinbase-wallet)
+- [Metamask](/docs/authentication/web3/metamask)
+- [OKX Wallet](/docs/authentication/web3/okx-wallet)

docs/authentication/social-connections/oauth.mdx

@@ -17,6 +17,8 @@ The easiest way to add social connections to your Clerk app is by using [prebuil
 
 ## Enable a social connection
 
+### Development instances
+
 For **development** instances, Clerk uses pre-configured shared OAuth credentials and redirect URIs to make the development flow as smooth as possible. This means that you can enable most social providers without additional configuration.
 
 To enable a social connection:
@@ -26,6 +28,8 @@ To enable a social connection:
 1. In the **Choose provider** dropdown, select the provider you want to use.
 1. Select **Add connection**.
 
+### Production instances
+
 For **production** instances, you will need to configure the provider with custom OAuth credentials. See the social provider's [dedicated guide](/docs/authentication/social-connections/overview) for more information.
 
 ## Configure additional OAuth scopes

docs/backend-requests/resources/cookies.mdx

@@ -3,7 +3,7 @@ title: Cookies
 description: Learn how cookies enable secure authentication and manage browser-server interactions.
 ---
 
-Cookies play a vital role in authentication, state management, and browser-server communication. By understanding their attributes, developers can ensure secure and efficient use in their applications. Clerk leverages cookies in a secure, privacy-compliant manner to facilitate seamless user authentication across domains and subdomains.
+Cookies play a vital role in authentication, state management, and browser-server communication. By understanding their attributes, developers can ensure secure and efficient use in their applications.
 
 ## What are cookies?
 
@@ -101,3 +101,7 @@ Cookies **explicitly** set with a domain appear in devtools with a leading perio
 ## Controlling JavaScript access with `HttpOnly`
 
 By default, cookies can be accessed via `document.cookie` in JavaScript. While this can be useful, it exposes cookies to risks like [Cross-Site Scripting (XSS) attacks](https://owasp.org/www-community/attacks/xss/). Setting the [`HttpOnly`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#httponly) flag prevents JavaScript from accessing the cookie, enhancing security. These cookies are still sent with HTTP requests but are inaccessible to client-side scripts.
+
+## How Clerk uses cookies
+
+Clerk leverages cookies in a secure, privacy-compliant manner to facilitate seamless user authentication across domains and subdomains. See the [guide on Clerk cookies](/docs/how-clerk-works/cookies) for more details.

docs/components/clerk-provider.mdx

@@ -55,7 +55,7 @@ The recommended approach is to wrap your entire app with `<ClerkProvider>` at th
     const PUBLISHABLE_KEY = import.meta.env.VITE_CLERK_PUBLISHABLE_KEY
 
     if (!PUBLISHABLE_KEY) {
-      throw new Error('Add your Clerk Publishable Key to the .env.local file')
+      throw new Error('Add your Clerk Publishable Key to the .env file')
     }
 
     ReactDOM.createRoot(document.getElementById('root')!).render(

docs/components/control/redirect-to-signin.mdx

@@ -67,7 +67,7 @@ The `<RedirectToSignIn />` component will navigate to the sign in URL which has
     const PUBLISHABLE_KEY = import.meta.env.VITE_CLERK_PUBLISHABLE_KEY
 
     if (!PUBLISHABLE_KEY) {
-      throw new Error('Add your Clerk Publishable Key to the .env.local file')
+      throw new Error('Add your Clerk Publishable Key to the .env file')
     }
 
     function PrivatePage() {