Managing sub (#787)

* separating pages

* redirects

nginx.conf

@@ -90,11 +90,8 @@ http {
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$                        $scheme://$http_host/docs/$1/quick-start/                                   permanent;
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/assemblyscript-api/$                $scheme://$http_host/docs/$1/developing/graph-ts/api/                       permanent;
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/assemblyscript-api/$               $scheme://$http_host/docs/$1/developing/graph-ts/api/                       permanent;
-        rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/deprecating-a-subgraph/$             $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/    permanent;
-        rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transferring-subgraph-ownership/$    $scheme://$http_host/docs/$1/managing/transfer-and-deprecate-a-subgraph/    permanent;
         rewrite ^/docs/en/substreams/(?!index\.).+$                                     https://substreams.streamingfast.io                                         permanent;
         rewrite ^/docs/en/firehose/(?!index\.).+$                                       https://firehose.streamingfast.io                                           permanent;
-
         # Temporary redirects (302)
         rewrite ^/docs/en/querying/graph-client/$                                       $scheme://$http_host/docs/en/querying/graph-client/README/                  redirect;
         rewrite ^/docs/en/developing/graph-ts/$                                         $scheme://$http_host/docs/en/developing/graph-ts/README/                    redirect;

website/pages/ar/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/yo/managing/transfer-and-deprecate-a-subgraph.mdx → website/pages/ar/managing/transfer-a-subgraph.mdx

@@ -1,5 +1,5 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
 ## Transferring ownership of a subgraph

website/pages/cs/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/de/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/en/developing/developer-faqs.mdx

@@ -80,7 +80,7 @@ If only one entity is created during the event and if there's nothing better ava
 
 ### 15. Can I delete my subgraph?
 
-It is not possible to delete subgraphs once they are created. However, you can [transfer and deprecate your subgraph](/managing/transfer-and-deprecate-a-subgraph/).
+It is not possible to delete subgraphs once they are created. However, you can [transfer](/managing/transfer-a-subgraph/) and [deprecate](/managing/deprecate-a-subgraph/) your subgraph.
 
 ## Network Related
 

website/pages/en/managing/_meta.js

@@ -1,3 +1,4 @@
 export default {
-  'transfer-and-deprecate-a-subgraph': '',
+  'transfer-a-subgraph': '',
+  'deprecate-a-subgraph': '',
 }

website/pages/en/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,22 @@
+---
+title: Deprecate a Subgraph
+---
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+## Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+## Reminders
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/zh/managing/transfer-and-deprecate-a-subgraph.mdx → website/pages/en/managing/transfer-a-subgraph.mdx

@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,7 +25,7 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
@@ -42,24 +40,3 @@ To transfer ownership of a subgraph, do the following:
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/en/network/developing.mdx

@@ -59,7 +59,7 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi
 When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
 
 - This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
-- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-and-deprecate-a-subgraph/) by sending the NFT.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
 - Published subgraphs have associated metadata, which provides other network participants with useful context and information.
 
 ### Add Curation Signal for Indexing
@@ -86,4 +86,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa
 
 ### Deprecating & Transferring Subgraphs
 
-If you no longer need a published subgraph, you can [deprecate or transfer a subgraph](/managing/transfer-and-deprecate-a-subgraph/). Deprecating a subgraph returns any signaled GRT to [Curators](/network/curating/).
+If you no longer need a published subgraph, you can [deprecate](/managing/deprecate-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deprecating a subgraph returns any signaled GRT to [Curators](/network/curating/).

website/pages/es/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/fr/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/ha/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/hi/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/it/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/ja/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

website/pages/ko/managing/deprecate-a-subgraph.mdx

@@ -0,0 +1,24 @@
+---
+title: Deprecate a Subgraph
+---
+
+## Deprecating a Subgraph
+
+Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+
+### Step-by-Step
+
+To deprecate your subgraph, do the following:
+
+1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
+2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
+3.  Your subgraph will no longer appear in searches on Graph Explorer.
+
+**Please note the following:**
+
+- The owner's wallet should call the `deprecateSubgraph` function.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deprecated subgraphs will show an error message.
+
+> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.