potential changes

Author: idalithb

website/pages/en/deploying/deploying-a-subgraph-to-studio.mdx

@@ -2,16 +2,34 @@
 title: Deploying a Subgraph to Subgraph Studio
 ---
 
-These are the steps to deploy your subgraph to Subgraph Studio:
+> Before deploying, you must install The Graph CLI; please review [Creating a Subgraph]()
 
-- Install The Graph CLI (with either yarn or npm)
+When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to stage it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you are publishing it on-chain.
+
+## What can you do in Subgraph Studio?
+
+[Subgraph Studio]() allows you to do the following:
+
+- Create and manage your API keys for specific subgraphs
 - Create your Subgraph in Subgraph Studio
 - Authenticate your account from the CLI
-- Deploying a Subgraph to Subgraph Studio
+- Deploy a Subgraph to Subgraph Studio
+- Stage it in the playground environment
+- Integrate it in staging using the query URL
+
+In Subgraph Studio, you can view the following:
 
-## Installing Graph CLI
+- Your user account controls
+- A list of subgraphs you've created
+- A section to manage your API keys
+- A section to manage, view details, and visualize the status of a specific subgraph
+- A section to manage your billing
 
-There is a CLI to deploy subgraphs to [Subgraph Studio](https://thegraph.com/studio/). Here are the commands to install `graph-cli`. This can be done using npm or yarn.
+Step-by-Step
+
+## Install the Graph CLI
+
+You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use the Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
 **Install with yarn:**
 
@@ -27,7 +45,35 @@ npm install -g @graphprotocol/graph-cli
 
 ## Create your Subgraph in Subgraph Studio
 
-Before deploying your actual subgraph you need to create a subgraph in [Subgraph Studio](https://thegraph.com/studio/). We recommend you read our [Studio documentation](/deploying/subgraph-studio) to learn more about this.
+### Create an account
+
+Before deploying your subgraph you need to create a subgraph in [Subgraph Studio](https://thegraph.com/studio/).
+
+1. Open [Subgraph Studio](https://thegraph.com/studio/).
+2. Connect your wallet.
+   - You can do this via MetaMask, WalletConnect, Coinbase Wallet, or Safe.
+3. After you connect your wallet, your unique deploy key will be displayed on your "My Subgraphs" page or your “subgraph details” page in the Studio.
+   - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
+4. You can create one or multiple API keys by clicking the API keys tab at the top of your homepage. See image below:
+   - You can limit API keys to a specific domain in the security section.
+
+> Important: You need API keys to query subgraphs
+
+#### How to create a subgraph in Subgraph Studio
+
+<VideoEmbed youtube="nGIFuC69bSA" />
+
+> For additional written detail, review the [quick-start]()
+
+#### Subgraph Compatibility with The Graph Network
+
+In order to be supported by Indexers on The Graph Network, subgraphs must:
+
+- Index a [supported network](/developing/supported-networks)
+- Must not use any of the following features:
+  - ipfs.cat & ipfs.map
+  - Non-fatal errors
+  - Grafting
 
 ## Initialize your Subgraph
 
@@ -37,32 +83,54 @@ Once your subgraph has been created in Subgraph Studio you can initialize the su
 graph init --studio <SUBGRAPH_SLUG>
 ```
 
-The `<SUBGRAPH_SLUG>` value can be found on your subgraph details page in Subgraph Studio:
+You can view the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 
-After running `graph init`, you will be asked to input the contract address, network, and ABI that you want to query. Doing this will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
+After running `graph init`, you will be asked to input the contract address, network, and ABI that you want to query.
+
+- This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
 ## Graph Auth
 
-Before being able to deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key that you can find on your "My Subgraphs" page or your subgraph details page.
+Before can deploy your subgraph to Subgraph Studio, you must login into your account using the CLI. To do this, you will need your deploy key (you can find it on your "My Subgraphs" page or under your subgraph details page).
 
-Here is the command that you need to use to authenticate from the CLI:
+Then, use the following command to authenticate from the CLI:
 
 ```bash
 graph auth --studio <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph to Subgraph Studio
 
-Once you are ready, you can deploy your subgraph to Subgraph Studio. Doing this won't publish your subgraph to the decentralized network, it will only deploy it to your Studio account where you will be able to test it and update the metadata.
+Once you are ready, you can deploy your subgraph to Subgraph Studio.
 
-Here is the CLI command that you need to use to deploy your subgraph.
+> Deploying a subgraph with the CLI pushes it to the Studio, where you can test it and and update the metadata. This action won't publish your subgraph to the decentralized network.
+
+Use the following CLI command to deploy your subgraph:
 
 ```bash
 graph deploy --studio <SUBGRAPH_SLUG>
 ```
 
-After running this command, the CLI will ask for a version label, you can name it however you want, you can use labels such as `0.1` and `0.2` or use letters as well such as `uniswap-v2-0.1`. Those labels will be visible in Graph Explorer and can be used by curators to decide if they want to signal on this version or not, so choose them wisely.
+After running this command, the CLI will ask for a version label.
+
+- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
+- The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
+
+## Testing your Subgraph
+
+After deploying, you can test/stage your subgraph in Subgraph Studio, deploy another version, update the metadata, and publish to Graph Explorer when you are ready.
+
+Use Subgraph Studio’s playground to:
+
+- Check your subgraph logs
+- The subgraph logs will indicate if and where a subgraph fails.
+
+## Publish your Subgraph in Subgraph Studio
+
+You are now ready to publish your subgraph!
+
+In order to publish your subgraph successfully, review [publishing a subgraph] (/publishing/publishing-a-subgraph/).
 
-Once deployed, you can test your subgraph in Subgraph Studio using the playground, deploy another version if needed, update the metadata, and when you are ready, publish your subgraph to Graph Explorer.
+<VideoEmbed youtube="satdwdbvzAQ" />