updated onboarding steps for EW (#64)

Author: JamesLawton

sdk/headless-wallet/verification.mdx

@@ -20,9 +20,17 @@ A common use case is that you authenticate the user on the client, but you want
 
 Once a user has authenticated with an embedded wallet on the client, simply call the corresponding function in order get a JWT from Sequence.
 ```typescript
+// Using Sequence.js
 const { idToken } = await sequence.getIdToken();
 ``` 
 
+```typescript
+// Using Web-SDK in React
+const { connector } = useAccount()
+
+const { idToken, expiry } = await connector.sequenceWaas.getIdToken()
+``` 
+
 </Step>
 <Step title="Pass JWT to Backend">
 
@@ -56,8 +64,8 @@ const client = jwksClient({
   cacheMaxAge: 86400000, // 1 day
 });
 
-// Should be equal to the audience claim in the JWT that you want to verify which will be of the form https://api.sequence.build/project/*projectID*
-const EXPECTED_AUDIENCE = "https://api.sequence.build/project/*PROJECT_ID*"
+// Should be equal to the audience claim in the JWT that you want to verify which will be of the form https://sequence.build/project/*projectID*
+const EXPECTED_AUDIENCE = "https://sequence.build/project/*PROJECT_ID*"
 ```
 
 </Step>

solutions/builder/embedded-wallet/configuration.mdx

@@ -1,12 +1,12 @@
----
-
-title: "Embedded Wallet Configuration"
+---
+
+title: "Embedded Wallet Configuration"
 description: Configure a Sequence Embedded Wallet in Builder to easily onboard users to your games by integrating OAuth accounts. Learn how to set up login providers like Google Auth and Apple Auth, specify allowed origins for security, set up a recovery wallet, create an initial configuration.
 sidebarTitle: Configuration
----
-
+---
+
 
-You can configure a [Sequence Embedded Wallet](/solutions/wallets/embedded-wallet/overview) in Builder and integrate your own OAuth accounts to enable easy onboarding to your games. Configuration page in Builder [is available here](https://sequence.build/project/default/embedded-wallet).
+You can configure a [Sequence Embedded Wallet](https://sequence.build/project/default/embedded-wallet?tab=config) in Builder and integrate your own OAuth accounts to enable easy onboarding to your games. Configuration page in Builder [is available here](https://sequence.build/project/default/embedded-wallet).
 
 The following sections will explain the various ways to configure using an Embedded Wallet in Builder:
 - [Login Providers](/solutions/builder/embedded-wallet#login-providers): Web2 based authentication providers
@@ -16,11 +16,17 @@ The following sections will explain the various ways to configure using an Embed
 - [Configuration Changes](/solutions/builder/embedded-wallet#configuration-changes): Update configuration details at anypoint with password protection
 - [SDK Integrations](/solutions/builder/embedded-wallet#sdk-integrations): Sequence SDK products that allow developers to implement an Embedded Wallet across platforms
 
+
+
+
+
+
+
 ## Login Providers
-Sequence Embedded Wallet supports a multitude of login providers such as email, various social logins, and guest wallets. For social logins, you must go through the configuration process for the provider to retrieve a client specific ID to pass into Sequence Builder. We recommend visiting the specific login provider's configuration page for more information on the setup process.
+Sequence Embedded Wallet supports a multitude of login providers such as email, various social logins, and guest wallets. For social logins, you must go through the configuration process for the provider to retrieve a client specific ID to pass into Sequence Builder. We recommend visiting the specific login provider's configuration page for more information on the setup process for each specific provider.
 
 ## Allowed Origins
-This additional security measure will prevent unauthorized usage of your WaaS configuration outside of domains you whitelisted. Add any development and production URLs under Allowed Origins. By default all subpaths under theses hosts will be allowed.
+This additional security measure will prevent unauthorized usage of your embedded wallet configuration outside of domains you whitelisted. Add any development and production URLs under Allowed Origins. By default all subpaths under theses hosts will be allowed.
 
 You must define allowed origins with a valid scheme (i.e. `https`).
 

solutions/wallets/embedded-wallet/quickstart.mdx

@@ -5,8 +5,6 @@ description: Connect your users to your App with the Sequence Embedded Wallet.
 sidebarTitle: Quickstart
 ---
 
-For Unreal or Unity integration, go to [Unreal](/sdk/unreal/installation) or [Unity](/sdk/unity/installation).
-
 ## Integrate by Framework
 
 <div className="not-prose grid gap-x-4 gap-y-4 sm:grid-cols-2 lg:grid-cols-3 mt-8 mb-8">
@@ -86,47 +84,49 @@ npx sequence-cli boilerplates create-embedded-wallet-react-starter
 npx sequence-cli boilerplates create-kit-embedded-wallet-nextjs-starter
 ```
 </CodeGroup>
+
 </Step>
-<Step title="Copy example .env file">
 
-```bash
-cd embedded-wallet-react-boilerplate && cp .env.example .env
-```
+<Step title="Connect and Authenticate">
+Open your browser and navigate to `http://localhost:4444`. Click on <b>Connect</b> to initiate the authentication process.
+
+You can now test the Embedded wallet with the boilerplate! Now, let's configure your own project.
 </Step>
-<Step title="Install Packages and start app">
 
-<CodeGroup>
-```bash pnpm
-pnpm install && pnpm dev
-```
+<Step title="Configure your Project">
+<a href="https://sequence.build/project/default/embedded-wallet?tab=config">Navigate to embedded wallet configuration</a> for your project on Builder. Enter your recovery wallet address and set a password, then <b>Create Configuration</b>. Be aware that this configuration cannot be changed at a later date.
+</Step>
 
-```bash npm
-npm install && npm run dev
+<Step title="Update Environment Variables">
+Navigate to the cloned directory and copy & paste this configuration in the file `.env` replacing the existing configuration.
+
+Ensure you update the `PROJECT_ACCESS_KEY` and `WAAS_CONFIG_KEY` with the new keys located on the <a href="https://sequence.build/project/default/embedded-wallet?tab=integration">integration page</a>.
+```tsx
+# Update with your project access key
+VITE_PROJECT_ACCESS_KEY="AQAAAAAAAKJcPk5v95BJE-Q7GwdlY9hPuAM"
+# Update with your WAAS_CONFIG_KEY
+VITE_WAAS_CONFIG_KEY="eyJwcm9qZWN0SWQiOjQxNTY0LCJycGNTZXJ2ZXIiOiJodHRwczovL3dhYXMuc2VxdWVuY2UuYXBwIn0="
+VITE_GOOGLE= NULL
+VITE_APPLE= NULL
+VITE_WALLET_CONNECT_ID= NULL
+VITE_CHAINS= 80002
+VITE_DEFAULT_CHAIN= 80002
 ```
+</Step>
 
-```bash yarn
-yarn install && yarn dev
-```
-</CodeGroup>
+<Step title="Test your new configuration">
+Save your `.env` file, run `pnpm dev` from the root directory, and navigate back to `http://localhost:4444`. Sign into your wallet using email to test the wallet actions again.
 
-</Step>
-<Step title="Connect and Authenticate">
-Navigate to `localhost:4444` and click connect to try out the authentication.
-</Step>
-<Step title="Use Sequence Embedded Wallets!">
+You are done! You can now see your wallet connection on the Overview page and the keys are scoped to your project.
 
-Now that you have a working authentication, you can take look at our examples for the most common functions:
-- [Sign messages](/sdk/headless-wallet/use-wallets#sign-messages)
-- [Send transactions](/sdk/headless-wallet/use-wallets#send-transactions)
-- [Call contracts](/sdk/headless-wallet/use-wallets#call-any-contract)
-- [Verify a user on your backend](/sdk/headless-wallet/verification#prerequisite-deployment-of-a-parent-wallet)
 </Step>
 </Steps>
 
+As next steps:
+- You can now setup various [social authentication providers](/solutions/builder/embedded-wallet#login-providers).
+- [Use more features of our web-sdk](/sdk/web/guides/send-sponsored-tx).
+- [Request a ID token from Sequence to validate users on your backend](/sdk/headless-wallet/verification). 
 
-<Tip>
-We are using example variables in the .env file, so we recommend creating a project on [Sequence Builder](https://sequence.build/project/default/wallet/embedded-wallet) and [setting up your own wallet configuration](/solutions/builder/embedded-wallet) and update the environment variables to use more social providers for authentication, customize email templates, and more.
-</Tip>