graphprotocol · benface · Aug 22, 2024 · Aug 22, 2024 · Aug 22, 2024 · benface
@@ -44,10 +44,10 @@ http {
         rewrite ^/(.*)//+(.*)   $scheme://$http_host/$1/$2  permanent; # remove adjacent slashes in the middle of the URI
         rewrite ^/([^.]*[^/])$  $scheme://$http_host/$1/    permanent; # force a trailing slash except for files with an extension
 
-        # Permanent redirects (301)
-        rewrite ^/docs/hostedservice/(.*)$                              $scheme://$http_host/docs/en/hosted-service/$1      permanent;
-        rewrite ^/docs/(?!(?:[a-zA-Z][a-zA-Z]|_next|img)(?:/|$))(.*)$   $scheme://$http_host/docs/en/$1                     permanent; # Redirect to `/en` if no language in URL and not an asset URL
+        # Redirect to `/en` if no language in URL and not an asset URL
+        rewrite ^/docs/(?!(?:[a-zA-Z][a-zA-Z]|_next|img)(?:/|$))(.*)$ $scheme://$http_host/docs/en/$1 permanent;
 
+        # Permanent redirects (301)
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/about/introduction/$                          $scheme://$http_host/docs/$1/about/                                         permanent;
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/about/network/$                               $scheme://$http_host/docs/$1/network/overview/                              permanent;
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/curating/$                                    $scheme://$http_host/docs/$1/network/curating/                              permanent;
@@ -88,14 +88,16 @@ http {
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/arbitrum-faq/$                                $scheme://$http_host/docs/$1/arbitrum/arbitrum-faq/                         permanent;
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/migrating-a-subgraph/$               $scheme://$http_host/docs/$1/cookbook/upgrading-a-subgraph/                 permanent;
         rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$                        $scheme://$http_host/docs/$1/quick-start/                                   permanent;
-        rewrite ^/docs/en/substreams/(?!index\.).+$                                     https://substreams.streamingfast.io                                         permanent;
-        rewrite ^/docs/en/firehose/(?!index\.).+$                                       https://firehose.streamingfast.io                                           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;
+        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;
 
         location / {
             try_files $uri $uri.html $uri/index.html =404;

@@ -56,31 +56,7 @@ export default withNextra({
       destination: '/en/',
       permanent: true,
     },
-    {
-      source: '/en/arbitrum-faq/',
-      destination: '/en/arbitrum/arbitrum-faq/',
-      permanent: true,
-    },
-    {
-      source: '/en/querying/graph-client/',
-      destination: '/en/querying/graph-client/README/',
-      permanent: false,
-    },
-    {
-      source: '/en/developing/graph-ts/',
-      destination: '/en/developing/graph-ts/README/',
-      permanent: false,
-    },
-    {
-      source: '/en/developer/assemblyscript-api/',
-      destination: '/en/developing/graph-ts/api/',
-      permanent: true,
-    },
-    {
-      source: '/en/developing/assemblyscript-api/',
-      destination: '/en/developing/graph-ts/api/',
-      permanent: true,
-    },
+    // If we ever change `output` to not be `export`, we should move all the redirects from `nginx.conf` here
   ],
   images: {
     unoptimized: true,

@@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 تمت كتابة المعالجات الخاصة بمعالجة الأحداث بـ[ أسيمبلي سكريبت ](https://www.assemblyscript.org/).
 
-Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/assemblyscript-api/).
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {

@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 تمت كتابة المعالجات(handlers) الخاصة بمعالجة الأحداث بـ[ AssemblyScript ](https://www.assemblyscript.org/).
 
-Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/assemblyscript-api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {

@@ -37,7 +37,7 @@ title: بناء Subgraphs على NEAR
 
 **schema.graphql:** a schema file that defines what data is stored for your subgraph, and how to query it via GraphQL. The requirements for NEAR subgraphs are covered by [the existing documentation](/developing/creating-a-subgraph#the-graphql-schema).
 
-**AssemblyScript Mappings:** [AssemblyScript code](/developing/assemblyscript-api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 During subgraph development there are two key commands:
 
@@ -98,7 +98,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 تمت كتابة المعالجات(handlers) الخاصة بمعالجة الأحداث بـ[ AssemblyScript ](https://www.assemblyscript.org/).
 
-NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/assemblyscript-api).
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ These types are passed to block & receipt handlers:
 - معالجات الكتلة ستتلقى`Block`
 - معالجات الاستلام ستتلقى`ReceiptWithOutcome`
 
-Otherwise, the rest of the [AssemblyScript API](/developing/assemblyscript-api) is available to NEAR subgraph developers during mapping execution.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/assemblyscript-api#json-api) to allow developers to easily process these logs.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## نشر NEAR Subgraph
 

@@ -136,7 +136,7 @@ Make sure **Update Subgraph Details in Explorer** is checked and click on **Save
 
 ## Deprecating a Subgraph on The Graph Network
 
-Follow the steps [here](/managing/deprecating-a-subgraph) to deprecate your subgraph and remove it from The Graph Network.
+Follow the steps [here](/managing/transfer-and-deprecate-a-subgraph) to deprecate your subgraph and remove it from The Graph Network.
 
 ## Querying a Subgraph + Billing on The Graph Network
 

@@ -1477,7 +1477,7 @@ The file data source must specifically mention all the entity types which it wil
 
 #### Create a new handler to process files
 
-This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/assemblyscript-api/#json-api)).
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
 
 The CID of the file as a readable string can be accessed via the `dataSource` as follows:
 

@@ -1368,7 +1368,7 @@ The log output includes the test run duration. Here's an example:
 
 > Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined
 
-This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/assemblyscript-api/#logging-api)
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
 >

@@ -105,7 +105,7 @@ Definice schématu popisuje strukturu výsledné databáze podgrafu a vztahy mez
 
 Obslužné programy pro zpracování událostí jsou napsány v jazyce [AssemblyScript](https://www.assemblyscript.org/).
 
-Indexování Arweave zavádí do [AssemblyScript API](/developing/assemblyscript-api/) datové typy specifické pro Arweave.
+Indexování Arweave zavádí do [AssemblyScript API](/developing/graph-ts/api/) datové typy specifické pro Arweave.
 
 ```tsx
 class Block {

@@ -85,7 +85,7 @@ Definice schématu popisuje strukturu výsledné databáze podgrafů a vztahy me
 
 Obslužné programy pro zpracování událostí jsou napsány v jazyce [AssemblyScript](https://www.assemblyscript.org/).
 
-Indexování Cosmos zavádí datové typy specifické pro Cosmos do [AssemblyScript API](/developing/assemblyscript-api/).
+Indexování Cosmos zavádí datové typy specifické pro Cosmos do [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {

@@ -37,7 +37,7 @@ Definice podgrafů má tři aspekty:
 
 **schema.graphql:** soubor se schématem, který definuje, jaká data jsou uložena pro váš podgraf, a jak je možné je dotazovat pomocí GraphQL. Požadavky na podgrafy NEAR jsou pokryty [existující dokumentací](/developing/creating-a-subgraph#the-graphql-schema).
 
-**Mapování v jazyce AssemblyScript:** [Kód jazyka AssemblyScript](/developing/assemblyscript-api), který převádí data událostí na entity definované ve vašem schématu. Podpora NEAR zavádí datové typy specifické pro NEAR a nové funkce pro parsování JSON.
+**Mapování v jazyce AssemblyScript:** [Kód jazyka AssemblyScript](/developing/graph-ts/api), který převádí data událostí na entity definované ve vašem schématu. Podpora NEAR zavádí datové typy specifické pro NEAR a nové funkce pro parsování JSON.
 
 Při vývoji podgrafů existují dva klíčové příkazy:
 
@@ -98,7 +98,7 @@ Definice schématu popisuje strukturu výsledné databáze podgrafů a vztahy me
 
 Obslužné programy pro zpracování událostí jsou napsány v jazyce [AssemblyScript](https://www.assemblyscript.org/).
 
-Indexování NEAR zavádí do rozhraní [AssemblyScript API](/developing/assemblyscript-api) datové typy specifické pro NEAR.
+Indexování NEAR zavádí do rozhraní [AssemblyScript API](/developing/graph-ts/api) datové typy specifické pro NEAR.
 
 ```typescript
 
@@ -165,9 +165,9 @@ Tyto typy jsou předány do block & obsluha účtenek:
 - Obsluhy bloků obdrží `Block`
 - Obsluhy příjmu obdrží `ReceiptWithOutcome`
 
-Jinak je zbytek [AssemblyScript API](/developing/assemblyscript-api) dostupný vývojářům podgrafů NEAR během provádění mapování.
+Jinak je zbytek [AssemblyScript API](/developing/graph-ts/api) dostupný vývojářům podgrafů NEAR během provádění mapování.
 
-To zahrnuje novou funkci parsování JSON - záznamy na NEAR jsou často vysílány ve formě zřetězených JSON. Nová funkce `json.fromString(...)` je k dispozici jako součást [JSON API](/developing/assemblyscript-api#json-api), které umožňuje vývojářům snadno zpracovávat tyto záznamy.
+To zahrnuje novou funkci parsování JSON - záznamy na NEAR jsou často vysílány ve formě zřetězených JSON. Nová funkce `json.fromString(...)` je k dispozici jako součást [JSON API](/developing/graph-ts/api#json-api), které umožňuje vývojářům snadno zpracovávat tyto záznamy.
 
 ## Nasazení podgrafu NEAR
 

@@ -136,7 +136,7 @@ Ujistěte se, že je zaškrtnuto políčko **Aktualizovat podrobnosti subgrafu v
 
 ## Odepsání subgrafu v síti Graph
 
-Postupujte podle pokynů [zde](/managing/deprecating-a-subgraph), abyste svůj podgraf vyřadili a odstranili jej ze sítě The Graph Network.
+Postupujte podle pokynů [zde](/managing/transfer-and-deprecate-a-subgraph), abyste svůj podgraf vyřadili a odstranili jej ze sítě The Graph Network.
 
 ## Dotazování podgrafu + fakturace v síti graph
 

@@ -1477,7 +1477,7 @@ The file data source must specifically mention all the entity types which it wil
 
 #### Vytvoření nové obslužné pro zpracování souborů
 
-This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/assemblyscript-api/#json-api)).
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
 
 CID souboru jako čitelný řetězec lze získat prostřednictvím `dataSource` následujícím způsobem:
 

@@ -1368,7 +1368,7 @@ Výstup protokolu obsahuje dobu trvání test. Zde je příklad:
 
 > Kritické: Nelze vytvořit WasmInstance z platného modulu s kontextem: neznámý import: wasi_snapshot_preview1::fd_write nebyl definován
 
-To znamená, že jste ve svém kódu použili `console.log`, což není podporováno jazykem AssemblyScript. Zvažte prosím použití [Logging API](/developing/assemblyscript-api/#logging-api)
+To znamená, že jste ve svém kódu použili `console.log`, což není podporováno jazykem AssemblyScript. Zvažte prosím použití [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
 >

@@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Die Handler für die Ereignisverarbeitung sind in [AssemblyScript](https://www.assemblyscript.org/) geschrieben.
 
-Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/assemblyscript-api/).
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {

@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Die Handler für die Ereignisverarbeitung sind in [AssemblyScript](https://www.assemblyscript.org/) geschrieben.
 
-Die Cosmos-Indizierung führt Cosmos-spezifische Datentypen in die [AssemblyScript-API](/developing/assemblyscript-api/) ein.
+Die Cosmos-Indizierung führt Cosmos-spezifische Datentypen in die [AssemblyScript-API](/developing/graph-ts/api/) ein.
 
 ```tsx
 class Block {

@@ -37,7 +37,7 @@ There are three aspects of subgraph definition:
 
 **schema.graphql:** a schema file that defines what data is stored for your subgraph, and how to query it via GraphQL. The requirements for NEAR subgraphs are covered by [the existing documentation](/developing/creating-a-subgraph#the-graphql-schema).
 
-**AssemblyScript Mappings:** [AssemblyScript code](/developing/assemblyscript-api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 During subgraph development there are two key commands:
 
@@ -98,7 +98,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Die Handler für die Ereignisverarbeitung sind in [AssemblyScript](https://www.assemblyscript.org/) geschrieben.
 
-NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/assemblyscript-api).
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ These types are passed to block & receipt handlers:
 - Block handlers will receive a `Block`
 - Receipt handlers will receive a `ReceiptWithOutcome`
 
-Otherwise, the rest of the [AssemblyScript API](/developing/assemblyscript-api) is available to NEAR subgraph developers during mapping execution.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/assemblyscript-api#json-api) to allow developers to easily process these logs.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## Deploying a NEAR Subgraph
 

@@ -136,7 +136,7 @@ Make sure **Update Subgraph Details in Explorer** is checked and click on **Save
 
 ## Deprecating a Subgraph on The Graph Network
 
-Follow the steps [here](/managing/deprecating-a-subgraph) to deprecate your subgraph and remove it from The Graph Network.
+Follow the steps [here](/managing/transfer-and-deprecate-a-subgraph) to deprecate your subgraph and remove it from The Graph Network.
 
 ## Querying a Subgraph + Billing on The Graph Network
 

@@ -1477,7 +1477,7 @@ The file data source must specifically mention all the entity types which it wil
 
 #### Create a new handler to process files
 
-This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/assemblyscript-api/#json-api)).
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
 
 The CID of the file as a readable string can be accessed via the `dataSource` as follows: