Update file data sources for Arweave

website/pages/en/developing/creating-a-subgraph.mdx

@@ -963,7 +963,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o
 
 ## File Data Sources
 
-File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way, starting with IPFS.
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
 
 > This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
 
@@ -1030,7 +1030,7 @@ If the relationship is 1:1 between the parent entity and the resulting file data
 
 > You can use [nested filters](https://thegraph.com/docs/en/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
 
-#### Add a new templated data source with `kind: file/ipfs`
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
 
 This is the data source which will be spawned when a file of interest is identified.
 
@@ -1096,9 +1096,11 @@ export function handleMetadata(content: Bytes): void {
 You can now create file data sources during execution of chain-based handlers:
 
 - Import the template from the auto-generated `templates`
-- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid IPFS content identifier
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
 
-> Currently Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`)
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, Graph Node is able to fetch files based on their [transaction id](https://docs.arweave.org/developers/server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Bundlr, but [does not currently support Bundlr manifests](https://docs.bundlr.network/learn/gateways#indexing).
 
 Example:
 
@@ -1129,7 +1131,7 @@ export function handleTransfer(event: TransferEvent): void {
 }
 ```
 
-This will create a new file data source, which will poll Graph Node's configured IPFS endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
 
 This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.