From be1cda52751aa76ea5e3eb20210da8dc522686d3 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Fri, 15 Nov 2024 15:08:03 -0800 Subject: [PATCH 01/22] Draft 1 --- website/pages/en/_meta.js | 43 ++++++++++--------- website/pages/en/{network => }/contracts.mdx | 0 website/pages/en/developing/_meta.js | 10 ++--- website/pages/en/developing/creating/_meta.js | 7 +++ .../{ => creating}/creating-a-subgraph.mdx | 0 .../{ => creating}/developer-faqs.mdx | 0 .../{ => creating}/graph-ts/[[...slug]].mdx | 0 .../{ => creating}/graph-ts/_meta.js | 0 .../{ => creating}/graph-ts/api.mdx | 0 .../{ => creating}/graph-ts/common-issues.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 .../{ => creating}/unit-testing-framework.mdx | 0 .../en/{ => developing}/deploying/_meta.js | 0 .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../en/{ => developing}/managing/_meta.js | 0 .../managing/deprecate-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../en/{ => developing}/publishing/_meta.js | 0 .../publishing/publishing-a-subgraph.mdx | 0 .../pages/en/{ => developing}/subgraphs.mdx | 0 website/pages/en/{network => }/explorer.mdx | 0 website/pages/en/index.json | 2 +- website/pages/en/indexer-tooling/_meta.js | 5 +++ .../en/{ => indexer-tooling}/firehose.mdx | 0 .../en/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/en/network/_meta.js | 1 - 29 files changed, 40 insertions(+), 28 deletions(-) rename website/pages/en/{network => }/contracts.mdx (100%) create mode 100644 website/pages/en/developing/creating/_meta.js rename website/pages/en/developing/{ => creating}/creating-a-subgraph.mdx (100%) rename website/pages/en/developing/{ => creating}/developer-faqs.mdx (100%) rename website/pages/en/developing/{ => creating}/graph-ts/[[...slug]].mdx (100%) rename website/pages/en/developing/{ => creating}/graph-ts/_meta.js (100%) rename website/pages/en/developing/{ => creating}/graph-ts/api.mdx (100%) rename website/pages/en/developing/{ => creating}/graph-ts/common-issues.mdx (100%) rename website/pages/en/developing/{ => creating}/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/en/developing/{ => creating}/unit-testing-framework.mdx (100%) rename website/pages/en/{ => developing}/deploying/_meta.js (100%) rename website/pages/en/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/en/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/en/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/en/{ => developing}/managing/_meta.js (100%) rename website/pages/en/{ => developing}/managing/deprecate-a-subgraph.mdx (100%) rename website/pages/en/{ => developing}/managing/transfer-a-subgraph.mdx (100%) rename website/pages/en/{ => developing}/publishing/_meta.js (100%) rename website/pages/en/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/en/{ => developing}/subgraphs.mdx (100%) rename website/pages/en/{network => }/explorer.mdx (100%) create mode 100644 website/pages/en/indexer-tooling/_meta.js rename website/pages/en/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/en/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/en/{ => indexer-tooling}/operating-graph-node.mdx (100%) diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index 504a9e0a9263..896a00a4d42e 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -1,16 +1,7 @@ export default { index: '', - '---1': { - type: 'separator', - }, about: '', - network: 'The Graph Network', - sunrise: 'Post-Sunrise Upgrade FAQ', - billing: '', - glossary: '', - tokenomics: 'Tokenomics', - arbitrum: 'Scaling with Arbitrum', - '---2': { + '---1': { type: 'separator', }, '###1': { @@ -18,15 +9,12 @@ export default { title: 'Subgraphs', }, 'quick-start': '', - subgraphs: '', - developing: 'Developing', - deploying: 'Deploying', - publishing: 'Publishing', - managing: 'Managing', + explorer: '', querying: 'Querying', + developing: 'Developing', + billing: '', cookbook: 'Cookbook', - 'release-notes': 'Release Notes & Upgrade Guides', - '---3': { + '---2': { type: 'separator', }, '###2': { @@ -35,18 +23,31 @@ export default { }, substreams: '', sps: 'Substreams-powered Subgraphs', - '---4': { + cookbook: 'Cookbooks', + '---3': { type: 'separator', }, '###3': { type: 'heading', title: 'Indexing', }, - 'operating-graph-node': '', + 'indexer-tooling': 'Indexer Tooling', tap: '', 'supported-network-requirements': '', 'chain-integration-overview': '', 'new-chain-integration': '', - firehose: '', - graphcast: '', + '---4': { + type: 'separator', + }, + '###4': { + type: 'heading', + title: 'Resources', + }, + tokenomics: 'Tokenomics', + glossary: '', + contracts: '', + network: 'The Graph Network', + sunrise: 'Post-Sunrise Upgrade FAQ', + arbitrum: 'Scaling with Arbitrum', + 'release-notes': 'Release Notes & Upgrade Guides', } diff --git a/website/pages/en/network/contracts.mdx b/website/pages/en/contracts.mdx similarity index 100% rename from website/pages/en/network/contracts.mdx rename to website/pages/en/contracts.mdx diff --git a/website/pages/en/developing/_meta.js b/website/pages/en/developing/_meta.js index 8233bdd02d64..27088d40abca 100644 --- a/website/pages/en/developing/_meta.js +++ b/website/pages/en/developing/_meta.js @@ -1,8 +1,8 @@ export default { 'supported-networks': '', - 'creating-a-subgraph': '', - 'graph-ts': 'AssemblyScript API', - 'unit-testing-framework': '', - 'developer-faqs': '', - 'substreams-powered-subgraphs-faq': '', + subgraphs: '', + creating: 'Creating', + deploying: 'Deploying', + publishing: 'Publishing', + managing: 'Managing', } diff --git a/website/pages/en/developing/creating/_meta.js b/website/pages/en/developing/creating/_meta.js new file mode 100644 index 000000000000..66d7e48dc5ea --- /dev/null +++ b/website/pages/en/developing/creating/_meta.js @@ -0,0 +1,7 @@ +export default { + 'creating-a-subgraph': '', + 'graph-ts': 'AssemblyScript API', + 'unit-testing-framework': '', + 'developer-faqs': '', + 'substreams-powered-subgraphs-faq': '', +} diff --git a/website/pages/en/developing/creating-a-subgraph.mdx b/website/pages/en/developing/creating/creating-a-subgraph.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph.mdx rename to website/pages/en/developing/creating/creating-a-subgraph.mdx diff --git a/website/pages/en/developing/developer-faqs.mdx b/website/pages/en/developing/creating/developer-faqs.mdx similarity index 100% rename from website/pages/en/developing/developer-faqs.mdx rename to website/pages/en/developing/creating/developer-faqs.mdx diff --git a/website/pages/en/developing/graph-ts/[[...slug]].mdx b/website/pages/en/developing/creating/graph-ts/[[...slug]].mdx similarity index 100% rename from website/pages/en/developing/graph-ts/[[...slug]].mdx rename to website/pages/en/developing/creating/graph-ts/[[...slug]].mdx diff --git a/website/pages/en/developing/graph-ts/_meta.js b/website/pages/en/developing/creating/graph-ts/_meta.js similarity index 100% rename from website/pages/en/developing/graph-ts/_meta.js rename to website/pages/en/developing/creating/graph-ts/_meta.js diff --git a/website/pages/en/developing/graph-ts/api.mdx b/website/pages/en/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/en/developing/graph-ts/api.mdx rename to website/pages/en/developing/creating/graph-ts/api.mdx diff --git a/website/pages/en/developing/graph-ts/common-issues.mdx b/website/pages/en/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/en/developing/graph-ts/common-issues.mdx rename to website/pages/en/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/en/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/en/developing/creating/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/en/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/en/developing/creating/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/en/developing/unit-testing-framework.mdx b/website/pages/en/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/en/developing/unit-testing-framework.mdx rename to website/pages/en/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/en/deploying/_meta.js b/website/pages/en/developing/deploying/_meta.js similarity index 100% rename from website/pages/en/deploying/_meta.js rename to website/pages/en/developing/deploying/_meta.js diff --git a/website/pages/en/deploying/deploy-using-subgraph-studio.mdx b/website/pages/en/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/en/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/en/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/en/deploying/multiple-networks.mdx b/website/pages/en/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/en/deploying/multiple-networks.mdx rename to website/pages/en/developing/deploying/multiple-networks.mdx diff --git a/website/pages/en/deploying/subgraph-studio-faqs.mdx b/website/pages/en/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/en/deploying/subgraph-studio-faqs.mdx rename to website/pages/en/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/en/managing/_meta.js b/website/pages/en/developing/managing/_meta.js similarity index 100% rename from website/pages/en/managing/_meta.js rename to website/pages/en/developing/managing/_meta.js diff --git a/website/pages/en/managing/deprecate-a-subgraph.mdx b/website/pages/en/developing/managing/deprecate-a-subgraph.mdx similarity index 100% rename from website/pages/en/managing/deprecate-a-subgraph.mdx rename to website/pages/en/developing/managing/deprecate-a-subgraph.mdx diff --git a/website/pages/en/managing/transfer-a-subgraph.mdx b/website/pages/en/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/en/managing/transfer-a-subgraph.mdx rename to website/pages/en/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/en/publishing/_meta.js b/website/pages/en/developing/publishing/_meta.js similarity index 100% rename from website/pages/en/publishing/_meta.js rename to website/pages/en/developing/publishing/_meta.js diff --git a/website/pages/en/publishing/publishing-a-subgraph.mdx b/website/pages/en/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/en/publishing/publishing-a-subgraph.mdx rename to website/pages/en/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/en/subgraphs.mdx b/website/pages/en/developing/subgraphs.mdx similarity index 100% rename from website/pages/en/subgraphs.mdx rename to website/pages/en/developing/subgraphs.mdx diff --git a/website/pages/en/network/explorer.mdx b/website/pages/en/explorer.mdx similarity index 100% rename from website/pages/en/network/explorer.mdx rename to website/pages/en/explorer.mdx diff --git a/website/pages/en/index.json b/website/pages/en/index.json index 7b5de0b796fd..b622b0198a5b 100644 --- a/website/pages/en/index.json +++ b/website/pages/en/index.json @@ -1,5 +1,5 @@ { - "title": "Get Started", + "title": "Home", "intro": "Learn about The Graph, a decentralized protocol for indexing and querying data from blockchains.", "shortcuts": { "aboutTheGraph": { diff --git a/website/pages/en/indexer-tooling/_meta.js b/website/pages/en/indexer-tooling/_meta.js new file mode 100644 index 000000000000..b3d8363c749c --- /dev/null +++ b/website/pages/en/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +export default { + 'operating-graph-node': '', + firehose: '', + graphcast: '', +} diff --git a/website/pages/en/firehose.mdx b/website/pages/en/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/en/firehose.mdx rename to website/pages/en/indexer-tooling/firehose.mdx diff --git a/website/pages/en/graphcast.mdx b/website/pages/en/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/en/graphcast.mdx rename to website/pages/en/indexer-tooling/graphcast.mdx diff --git a/website/pages/en/operating-graph-node.mdx b/website/pages/en/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/en/operating-graph-node.mdx rename to website/pages/en/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/en/network/_meta.js b/website/pages/en/network/_meta.js index 555f264df379..7ccd4111162d 100644 --- a/website/pages/en/network/_meta.js +++ b/website/pages/en/network/_meta.js @@ -5,5 +5,4 @@ export default { delegating: '', curating: '', developing: '', - explorer: '', } From 95fd67ef4324c005a3a56a884451468696ee3920 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Tue, 10 Dec 2024 16:53:54 -0800 Subject: [PATCH 02/22] adjusting nav --- website/pages/en/_meta.js | 11 +++++++---- website/pages/en/archived/_meta.js | 4 ++++ website/pages/en/{ => archived}/arbitrum/_meta.js | 0 .../pages/en/{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../{ => archived}/arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/en/{ => archived}/sunrise.mdx | 0 website/pages/en/{network => }/benefits.mdx | 0 website/pages/en/billing.mdx | 2 +- website/pages/en/{network => }/curating.mdx | 0 website/pages/en/{network => }/delegating.mdx | 0 website/pages/en/developing/_meta.js | 1 + .../pages/en/{network => developing}/developing.mdx | 0 .../pages/en/indexer-tooling/operating-graph-node.mdx | 2 +- website/pages/en/{network => }/indexing.mdx | 0 website/pages/en/network/_meta.js | 8 -------- website/pages/en/{network => }/overview.mdx | 0 17 files changed, 14 insertions(+), 14 deletions(-) create mode 100644 website/pages/en/archived/_meta.js rename website/pages/en/{ => archived}/arbitrum/_meta.js (100%) rename website/pages/en/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/en/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/en/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/en/{ => archived}/sunrise.mdx (100%) rename website/pages/en/{network => }/benefits.mdx (100%) rename website/pages/en/{network => }/curating.mdx (100%) rename website/pages/en/{network => }/delegating.mdx (100%) rename website/pages/en/{network => developing}/developing.mdx (100%) rename website/pages/en/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/en/network/_meta.js rename website/pages/en/{network => }/overview.mdx (100%) diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index 896a00a4d42e..329cd17b7952 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -1,6 +1,7 @@ export default { index: '', about: '', + contracts: '', '---1': { type: 'separator', }, @@ -31,6 +32,7 @@ export default { type: 'heading', title: 'Indexing', }, + indexing: '', 'indexer-tooling': 'Indexer Tooling', tap: '', 'supported-network-requirements': '', @@ -43,11 +45,12 @@ export default { type: 'heading', title: 'Resources', }, + overview: 'Overview', + benefits: 'Benefits', tokenomics: 'Tokenomics', glossary: '', - contracts: '', - network: 'The Graph Network', - sunrise: 'Post-Sunrise Upgrade FAQ', - arbitrum: 'Scaling with Arbitrum', + delegating: '', + curating: '', 'release-notes': 'Release Notes & Upgrade Guides', + archived: 'Archived', } diff --git a/website/pages/en/archived/_meta.js b/website/pages/en/archived/_meta.js new file mode 100644 index 000000000000..25ac2b8ee56f --- /dev/null +++ b/website/pages/en/archived/_meta.js @@ -0,0 +1,4 @@ +export default { + sunrise: 'Post-Sunrise Upgrade FAQ', + arbitrum: 'Scaling with Arbitrum', +} diff --git a/website/pages/en/arbitrum/_meta.js b/website/pages/en/archived/arbitrum/_meta.js similarity index 100% rename from website/pages/en/arbitrum/_meta.js rename to website/pages/en/archived/arbitrum/_meta.js diff --git a/website/pages/en/arbitrum/arbitrum-faq.mdx b/website/pages/en/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/en/arbitrum/arbitrum-faq.mdx rename to website/pages/en/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/en/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/en/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/en/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/en/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/en/sunrise.mdx b/website/pages/en/archived/sunrise.mdx similarity index 100% rename from website/pages/en/sunrise.mdx rename to website/pages/en/archived/sunrise.mdx diff --git a/website/pages/en/network/benefits.mdx b/website/pages/en/benefits.mdx similarity index 100% rename from website/pages/en/network/benefits.mdx rename to website/pages/en/benefits.mdx diff --git a/website/pages/en/billing.mdx b/website/pages/en/billing.mdx index dec5cfdadc12..f3af2fd64994 100644 --- a/website/pages/en/billing.mdx +++ b/website/pages/en/billing.mdx @@ -2,7 +2,7 @@ title: Billing --- -## Subgraph Billing Plans +## Querying Plans There are two plans to use when querying subgraphs on The Graph Network. diff --git a/website/pages/en/network/curating.mdx b/website/pages/en/curating.mdx similarity index 100% rename from website/pages/en/network/curating.mdx rename to website/pages/en/curating.mdx diff --git a/website/pages/en/network/delegating.mdx b/website/pages/en/delegating.mdx similarity index 100% rename from website/pages/en/network/delegating.mdx rename to website/pages/en/delegating.mdx diff --git a/website/pages/en/developing/_meta.js b/website/pages/en/developing/_meta.js index 27088d40abca..898457bf3929 100644 --- a/website/pages/en/developing/_meta.js +++ b/website/pages/en/developing/_meta.js @@ -1,5 +1,6 @@ export default { 'supported-networks': '', + developing: '', subgraphs: '', creating: 'Creating', deploying: 'Deploying', diff --git a/website/pages/en/network/developing.mdx b/website/pages/en/developing/developing.mdx similarity index 100% rename from website/pages/en/network/developing.mdx rename to website/pages/en/developing/developing.mdx diff --git a/website/pages/en/indexer-tooling/operating-graph-node.mdx b/website/pages/en/indexer-tooling/operating-graph-node.mdx index 2f535c400734..003a17e22ec4 100644 --- a/website/pages/en/indexer-tooling/operating-graph-node.mdx +++ b/website/pages/en/indexer-tooling/operating-graph-node.mdx @@ -1,5 +1,5 @@ --- -title: Operating Graph Node +title: Graph Node --- Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer. diff --git a/website/pages/en/network/indexing.mdx b/website/pages/en/indexing.mdx similarity index 100% rename from website/pages/en/network/indexing.mdx rename to website/pages/en/indexing.mdx diff --git a/website/pages/en/network/_meta.js b/website/pages/en/network/_meta.js deleted file mode 100644 index 7ccd4111162d..000000000000 --- a/website/pages/en/network/_meta.js +++ /dev/null @@ -1,8 +0,0 @@ -export default { - overview: 'Overview', - benefits: 'Benefits', - indexing: '', - delegating: '', - curating: '', - developing: '', -} diff --git a/website/pages/en/network/overview.mdx b/website/pages/en/overview.mdx similarity index 100% rename from website/pages/en/network/overview.mdx rename to website/pages/en/overview.mdx From 13d6ea32fa32869ef14b6654d5bc15b4f44e5fa0 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Thu, 12 Dec 2024 15:59:50 -0800 Subject: [PATCH 03/22] updating branch --- website/pages/en/_meta.js | 2 +- website/pages/en/developing/_meta.js | 5 +++-- website/pages/en/developing/creating-a-subgraph/_meta.js | 2 ++ .../graph-ts/[[...slug]].mdx | 0 .../{creating => creating-a-subgraph}/graph-ts/_meta.js | 0 .../{creating => creating-a-subgraph}/graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../creating-a-subgraph/starting-your-subgraph.mdx | 2 ++ .../unit-testing-framework.mdx | 0 website/pages/en/developing/creating/_meta.js | 7 ------- .../pages/en/developing/{creating => }/developer-faqs.mdx | 0 website/pages/en/developing/developing.mdx | 2 +- website/pages/en/sps/_meta.js | 1 + .../creating => sps}/substreams-powered-subgraphs-faq.mdx | 0 14 files changed, 10 insertions(+), 11 deletions(-) rename website/pages/en/developing/{creating => creating-a-subgraph}/graph-ts/[[...slug]].mdx (100%) rename website/pages/en/developing/{creating => creating-a-subgraph}/graph-ts/_meta.js (100%) rename website/pages/en/developing/{creating => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/en/developing/{creating => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/en/developing/{creating => creating-a-subgraph}/unit-testing-framework.mdx (100%) delete mode 100644 website/pages/en/developing/creating/_meta.js rename website/pages/en/developing/{creating => }/developer-faqs.mdx (100%) rename website/pages/en/{developing/creating => sps}/substreams-powered-subgraphs-faq.mdx (100%) diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index 329cd17b7952..3c228ca8248d 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -23,7 +23,7 @@ export default { title: 'Substreams', }, substreams: '', - sps: 'Substreams-powered Subgraphs', + sps: 'Substreams Powered Subgraphs', cookbook: 'Cookbooks', '---3': { type: 'separator', diff --git a/website/pages/en/developing/_meta.js b/website/pages/en/developing/_meta.js index 898457bf3929..b961003946cc 100644 --- a/website/pages/en/developing/_meta.js +++ b/website/pages/en/developing/_meta.js @@ -1,9 +1,10 @@ export default { 'supported-networks': '', - developing: '', + developing: 'Introduction to Development', subgraphs: '', - creating: 'Creating', + 'creating-a-subgraph': 'Create a Subgraph', deploying: 'Deploying', publishing: 'Publishing', managing: 'Managing', + 'developer-faqs': '', } diff --git a/website/pages/en/developing/creating-a-subgraph/_meta.js b/website/pages/en/developing/creating-a-subgraph/_meta.js index ce17f461a35d..e789cda9cc73 100644 --- a/website/pages/en/developing/creating-a-subgraph/_meta.js +++ b/website/pages/en/developing/creating-a-subgraph/_meta.js @@ -5,4 +5,6 @@ export default { 'ql-schema': '', 'assemblyscript-mappings': '', advanced: '', + 'graph-ts': 'AssemblyScript API', + 'unit-testing-framework': '', } diff --git a/website/pages/en/developing/creating/graph-ts/[[...slug]].mdx b/website/pages/en/developing/creating-a-subgraph/graph-ts/[[...slug]].mdx similarity index 100% rename from website/pages/en/developing/creating/graph-ts/[[...slug]].mdx rename to website/pages/en/developing/creating-a-subgraph/graph-ts/[[...slug]].mdx diff --git a/website/pages/en/developing/creating/graph-ts/_meta.js b/website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js similarity index 100% rename from website/pages/en/developing/creating/graph-ts/_meta.js rename to website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js diff --git a/website/pages/en/developing/creating/graph-ts/api.mdx b/website/pages/en/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/en/developing/creating/graph-ts/api.mdx rename to website/pages/en/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/en/developing/creating/graph-ts/common-issues.mdx b/website/pages/en/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/en/developing/creating/graph-ts/common-issues.mdx rename to website/pages/en/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/en/developing/creating-a-subgraph/starting-your-subgraph.mdx index 5127f01632aa..4388c412b518 100644 --- a/website/pages/en/developing/creating-a-subgraph/starting-your-subgraph.mdx +++ b/website/pages/en/developing/creating-a-subgraph/starting-your-subgraph.mdx @@ -19,3 +19,5 @@ Start the process and build a subgraph that matches your needs: 3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema 4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings 5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features + +Explore additional [resources for APIs](/developing/creating-a-subgraph/graph-ts/README/) and conduct local testing with [Matchstick](/developing/creating-a-subgraph/unit-testing-framework/). diff --git a/website/pages/en/developing/creating/unit-testing-framework.mdx b/website/pages/en/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/en/developing/creating/unit-testing-framework.mdx rename to website/pages/en/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/en/developing/creating/_meta.js b/website/pages/en/developing/creating/_meta.js deleted file mode 100644 index 66d7e48dc5ea..000000000000 --- a/website/pages/en/developing/creating/_meta.js +++ /dev/null @@ -1,7 +0,0 @@ -export default { - 'creating-a-subgraph': '', - 'graph-ts': 'AssemblyScript API', - 'unit-testing-framework': '', - 'developer-faqs': '', - 'substreams-powered-subgraphs-faq': '', -} diff --git a/website/pages/en/developing/creating/developer-faqs.mdx b/website/pages/en/developing/developer-faqs.mdx similarity index 100% rename from website/pages/en/developing/creating/developer-faqs.mdx rename to website/pages/en/developing/developer-faqs.mdx diff --git a/website/pages/en/developing/developing.mdx b/website/pages/en/developing/developing.mdx index 6ba33f6d916c..7b630ce3a607 100644 --- a/website/pages/en/developing/developing.mdx +++ b/website/pages/en/developing/developing.mdx @@ -1,5 +1,5 @@ --- -title: Developing +title: Introduction to Development --- To start coding right away, go to [Developer Quick Start](/quick-start/). diff --git a/website/pages/en/sps/_meta.js b/website/pages/en/sps/_meta.js index a8b84287610e..6f0dc9c346ea 100644 --- a/website/pages/en/sps/_meta.js +++ b/website/pages/en/sps/_meta.js @@ -2,4 +2,5 @@ export default { introduction: 'Introduction', triggers: '', 'triggers-example': 'Tutorial', + 'substreams-powered-subgraphs-faq': 'SPS FAQ', } diff --git a/website/pages/en/developing/creating/substreams-powered-subgraphs-faq.mdx b/website/pages/en/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/en/developing/creating/substreams-powered-subgraphs-faq.mdx rename to website/pages/en/sps/substreams-powered-subgraphs-faq.mdx From be8d718a4128a2cc2df5c4e55b229faeb441fab1 Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Thu, 12 Dec 2024 16:33:07 -0800 Subject: [PATCH 04/22] adding folder --- website/pages/en/_meta.js | 5 +---- website/pages/en/roles-and-benefits/_meta.js | 6 ++++++ website/pages/en/{ => roles-and-benefits}/benefits.mdx | 0 website/pages/en/{ => roles-and-benefits}/curating.mdx | 0 website/pages/en/{ => roles-and-benefits}/delegating.mdx | 0 website/pages/en/{ => roles-and-benefits}/overview.mdx | 0 6 files changed, 7 insertions(+), 4 deletions(-) create mode 100644 website/pages/en/roles-and-benefits/_meta.js rename website/pages/en/{ => roles-and-benefits}/benefits.mdx (100%) rename website/pages/en/{ => roles-and-benefits}/curating.mdx (100%) rename website/pages/en/{ => roles-and-benefits}/delegating.mdx (100%) rename website/pages/en/{ => roles-and-benefits}/overview.mdx (100%) diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index 3c228ca8248d..7cff2ea6621d 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -45,12 +45,9 @@ export default { type: 'heading', title: 'Resources', }, - overview: 'Overview', - benefits: 'Benefits', + 'roles-and-benefits': 'Roles and Benefits', tokenomics: 'Tokenomics', glossary: '', - delegating: '', - curating: '', 'release-notes': 'Release Notes & Upgrade Guides', archived: 'Archived', } diff --git a/website/pages/en/roles-and-benefits/_meta.js b/website/pages/en/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..3a25fcb924c4 --- /dev/null +++ b/website/pages/en/roles-and-benefits/_meta.js @@ -0,0 +1,6 @@ +export default { + overview: 'Overview', + benefits: 'Benefits', + delegating: '', + curating: '', +} diff --git a/website/pages/en/benefits.mdx b/website/pages/en/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/en/benefits.mdx rename to website/pages/en/roles-and-benefits/benefits.mdx diff --git a/website/pages/en/curating.mdx b/website/pages/en/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/en/curating.mdx rename to website/pages/en/roles-and-benefits/curating.mdx diff --git a/website/pages/en/delegating.mdx b/website/pages/en/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/en/delegating.mdx rename to website/pages/en/roles-and-benefits/delegating.mdx diff --git a/website/pages/en/overview.mdx b/website/pages/en/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/en/overview.mdx rename to website/pages/en/roles-and-benefits/overview.mdx From 56af1cbfa9f6ebf8a08dfa50408d92d162560b44 Mon Sep 17 00:00:00 2001 From: benface Date: Mon, 16 Dec 2024 14:05:42 -0500 Subject: [PATCH 05/22] Fix import --- .../pages/en/developing/creating-a-subgraph/graph-ts/_meta.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js index 56029533d9ea..05a81c9d14c3 100644 --- a/website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js +++ b/website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js @@ -1,6 +1,6 @@ import { createCatchAllMeta } from 'nextra/catch-all' -import json from '../../../../remote-files/graph-ts.json' assert { type: 'json' } +import json from '../../../../../remote-files/graph-ts.json' assert { type: 'json' } export default () => createCatchAllMeta(json.filePaths, { From 5978a2f33a3c3c0be1284dc68fbaa85a2b39193a Mon Sep 17 00:00:00 2001 From: benface Date: Mon, 16 Dec 2024 14:06:06 -0500 Subject: [PATCH 06/22] Apply changes to all languages, fixing the build --- website/pages/ar/arbitrum/_meta.js | 5 - website/pages/ar/archived/_meta.js | 5 + website/pages/ar/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/ar/{ => archived}/sunrise.mdx | 0 website/pages/ar/{network => }/contracts.mdx | 0 website/pages/ar/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/ar/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../ar/{network => developing}/developing.mdx | 0 website/pages/ar/developing/graph-ts/_meta.js | 5 - website/pages/ar/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/ar/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/ar/{ => developing}/subgraphs.mdx | 0 website/pages/ar/{network => }/explorer.mdx | 0 website/pages/ar/indexer-tooling/_meta.js | 5 + .../ar/{ => indexer-tooling}/firehose.mdx | 0 .../ar/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/ar/{network => }/indexing.mdx | 0 website/pages/ar/managing/_meta.js | 5 - website/pages/ar/network/_meta.js | 5 - website/pages/ar/publishing/_meta.js | 5 - website/pages/ar/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/cs/arbitrum/_meta.js | 5 - website/pages/cs/archived/_meta.js | 5 + website/pages/cs/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/cs/{ => archived}/sunrise.mdx | 0 website/pages/cs/{network => }/contracts.mdx | 0 website/pages/cs/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/cs/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../cs/{network => developing}/developing.mdx | 0 website/pages/cs/developing/graph-ts/_meta.js | 5 - website/pages/cs/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/cs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/cs/{ => developing}/subgraphs.mdx | 0 website/pages/cs/{network => }/explorer.mdx | 0 website/pages/cs/indexer-tooling/_meta.js | 5 + .../cs/{ => indexer-tooling}/firehose.mdx | 0 .../cs/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/cs/{network => }/indexing.mdx | 0 website/pages/cs/managing/_meta.js | 5 - website/pages/cs/network/_meta.js | 5 - website/pages/cs/publishing/_meta.js | 5 - website/pages/cs/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/de/arbitrum/_meta.js | 5 - website/pages/de/archived/_meta.js | 5 + website/pages/de/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/de/{ => archived}/sunrise.mdx | 0 website/pages/de/{network => }/contracts.mdx | 0 website/pages/de/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/de/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../de/{network => developing}/developing.mdx | 0 website/pages/de/developing/graph-ts/_meta.js | 5 - website/pages/de/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/de/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/de/{ => developing}/subgraphs.mdx | 0 website/pages/de/{network => }/explorer.mdx | 0 website/pages/de/indexer-tooling/_meta.js | 5 + .../de/{ => indexer-tooling}/firehose.mdx | 0 .../de/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/de/{network => }/indexing.mdx | 0 website/pages/de/managing/_meta.js | 5 - website/pages/de/network/_meta.js | 5 - website/pages/de/publishing/_meta.js | 5 - website/pages/de/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/es/arbitrum/_meta.js | 5 - website/pages/es/archived/_meta.js | 5 + website/pages/es/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/es/{ => archived}/sunrise.mdx | 0 website/pages/es/{network => }/contracts.mdx | 0 website/pages/es/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/es/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../es/{network => developing}/developing.mdx | 0 website/pages/es/developing/graph-ts/_meta.js | 5 - website/pages/es/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/es/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/es/{ => developing}/subgraphs.mdx | 0 website/pages/es/{network => }/explorer.mdx | 0 website/pages/es/indexer-tooling/_meta.js | 5 + .../es/{ => indexer-tooling}/firehose.mdx | 0 .../es/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/es/{network => }/indexing.mdx | 0 website/pages/es/managing/_meta.js | 5 - website/pages/es/network/_meta.js | 5 - website/pages/es/publishing/_meta.js | 5 - website/pages/es/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/fr/arbitrum/_meta.js | 5 - website/pages/fr/archived/_meta.js | 5 + website/pages/fr/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/fr/{ => archived}/sunrise.mdx | 0 website/pages/fr/{network => }/contracts.mdx | 0 website/pages/fr/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/fr/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../fr/{network => developing}/developing.mdx | 0 website/pages/fr/developing/graph-ts/_meta.js | 5 - website/pages/fr/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/fr/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/fr/{ => developing}/subgraphs.mdx | 0 website/pages/fr/{network => }/explorer.mdx | 0 website/pages/fr/indexer-tooling/_meta.js | 5 + .../fr/{ => indexer-tooling}/firehose.mdx | 0 .../fr/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/fr/{network => }/indexing.mdx | 0 website/pages/fr/managing/_meta.js | 5 - website/pages/fr/network/_meta.js | 5 - website/pages/fr/publishing/_meta.js | 5 - website/pages/fr/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/hi/arbitrum/_meta.js | 5 - website/pages/hi/archived/_meta.js | 5 + website/pages/hi/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/hi/{ => archived}/sunrise.mdx | 0 website/pages/hi/{network => }/contracts.mdx | 0 website/pages/hi/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/hi/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../hi/{network => developing}/developing.mdx | 0 website/pages/hi/developing/graph-ts/_meta.js | 5 - website/pages/hi/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/hi/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/hi/{ => developing}/subgraphs.mdx | 0 website/pages/hi/{network => }/explorer.mdx | 0 website/pages/hi/indexer-tooling/_meta.js | 5 + .../hi/{ => indexer-tooling}/firehose.mdx | 0 .../hi/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/hi/{network => }/indexing.mdx | 0 website/pages/hi/managing/_meta.js | 5 - website/pages/hi/network/_meta.js | 5 - website/pages/hi/publishing/_meta.js | 5 - website/pages/hi/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/it/arbitrum/_meta.js | 5 - website/pages/it/archived/_meta.js | 5 + website/pages/it/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/it/{ => archived}/sunrise.mdx | 0 website/pages/it/{network => }/contracts.mdx | 0 website/pages/it/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/it/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../it/{network => developing}/developing.mdx | 0 website/pages/it/developing/graph-ts/_meta.js | 5 - website/pages/it/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/it/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/it/{ => developing}/subgraphs.mdx | 0 website/pages/it/{network => }/explorer.mdx | 0 website/pages/it/indexer-tooling/_meta.js | 5 + .../it/{ => indexer-tooling}/firehose.mdx | 0 .../it/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/it/{network => }/indexing.mdx | 0 website/pages/it/managing/_meta.js | 5 - website/pages/it/network/_meta.js | 5 - website/pages/it/publishing/_meta.js | 5 - website/pages/it/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/ja/arbitrum/_meta.js | 5 - website/pages/ja/archived/_meta.js | 5 + website/pages/ja/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/ja/{ => archived}/sunrise.mdx | 0 website/pages/ja/{network => }/contracts.mdx | 0 website/pages/ja/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/ja/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../ja/{network => developing}/developing.mdx | 0 website/pages/ja/developing/graph-ts/_meta.js | 5 - website/pages/ja/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/ja/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/ja/{ => developing}/subgraphs.mdx | 0 website/pages/ja/{network => }/explorer.mdx | 0 website/pages/ja/indexer-tooling/_meta.js | 5 + .../ja/{ => indexer-tooling}/firehose.mdx | 0 .../ja/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/ja/{network => }/indexing.mdx | 0 website/pages/ja/managing/_meta.js | 5 - website/pages/ja/network/_meta.js | 5 - website/pages/ja/publishing/_meta.js | 5 - website/pages/ja/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/ko/arbitrum/_meta.js | 5 - website/pages/ko/archived/_meta.js | 5 + website/pages/ko/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/ko/{ => archived}/sunrise.mdx | 0 website/pages/ko/{network => }/contracts.mdx | 0 website/pages/ko/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/ko/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../ko/{network => developing}/developing.mdx | 0 website/pages/ko/developing/graph-ts/_meta.js | 5 - website/pages/ko/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/ko/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/ko/{ => developing}/subgraphs.mdx | 0 website/pages/ko/{network => }/explorer.mdx | 0 website/pages/ko/indexer-tooling/_meta.js | 5 + .../ko/{ => indexer-tooling}/firehose.mdx | 0 .../ko/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/ko/{network => }/indexing.mdx | 0 website/pages/ko/managing/_meta.js | 5 - website/pages/ko/network/_meta.js | 5 - website/pages/ko/publishing/_meta.js | 5 - website/pages/ko/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/mr/arbitrum/_meta.js | 5 - website/pages/mr/archived/_meta.js | 5 + website/pages/mr/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/mr/{ => archived}/sunrise.mdx | 0 website/pages/mr/{network => }/contracts.mdx | 0 website/pages/mr/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/mr/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../mr/{network => developing}/developing.mdx | 0 website/pages/mr/developing/graph-ts/_meta.js | 5 - website/pages/mr/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/mr/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/mr/{ => developing}/subgraphs.mdx | 0 website/pages/mr/{network => }/explorer.mdx | 0 website/pages/mr/indexer-tooling/_meta.js | 5 + .../mr/{ => indexer-tooling}/firehose.mdx | 0 .../mr/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/mr/{network => }/indexing.mdx | 0 website/pages/mr/managing/_meta.js | 5 - website/pages/mr/network/_meta.js | 5 - website/pages/mr/publishing/_meta.js | 5 - website/pages/mr/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/nl/arbitrum/_meta.js | 5 - website/pages/nl/archived/_meta.js | 5 + website/pages/nl/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/nl/{ => archived}/sunrise.mdx | 0 website/pages/nl/{network => }/contracts.mdx | 0 website/pages/nl/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/nl/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../nl/{network => developing}/developing.mdx | 0 website/pages/nl/developing/graph-ts/_meta.js | 5 - website/pages/nl/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/nl/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/nl/{ => developing}/subgraphs.mdx | 0 website/pages/nl/{network => }/explorer.mdx | 0 website/pages/nl/indexer-tooling/_meta.js | 5 + .../nl/{ => indexer-tooling}/firehose.mdx | 0 .../nl/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/nl/{network => }/indexing.mdx | 0 website/pages/nl/managing/_meta.js | 5 - website/pages/nl/network/_meta.js | 5 - website/pages/nl/publishing/_meta.js | 5 - website/pages/nl/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/pl/arbitrum/_meta.js | 5 - website/pages/pl/archived/_meta.js | 5 + website/pages/pl/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/pl/{ => archived}/sunrise.mdx | 0 website/pages/pl/{network => }/contracts.mdx | 0 website/pages/pl/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/pl/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../pl/{network => developing}/developing.mdx | 0 website/pages/pl/developing/graph-ts/_meta.js | 5 - website/pages/pl/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/pl/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/pl/{ => developing}/subgraphs.mdx | 0 website/pages/pl/{network => }/explorer.mdx | 0 website/pages/pl/indexer-tooling/_meta.js | 5 + .../pl/{ => indexer-tooling}/firehose.mdx | 0 .../pl/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/pl/{network => }/indexing.mdx | 0 website/pages/pl/managing/_meta.js | 5 - website/pages/pl/network/_meta.js | 5 - website/pages/pl/publishing/_meta.js | 5 - website/pages/pl/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/pt/arbitrum/_meta.js | 5 - website/pages/pt/archived/_meta.js | 5 + website/pages/pt/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/pt/{ => archived}/sunrise.mdx | 0 website/pages/pt/{network => }/contracts.mdx | 0 website/pages/pt/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/pt/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../pt/{network => developing}/developing.mdx | 0 website/pages/pt/developing/graph-ts/_meta.js | 5 - website/pages/pt/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/pt/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/pt/{ => developing}/subgraphs.mdx | 0 website/pages/pt/{network => }/explorer.mdx | 0 website/pages/pt/indexer-tooling/_meta.js | 5 + .../pt/{ => indexer-tooling}/firehose.mdx | 0 .../pt/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/pt/{network => }/indexing.mdx | 0 website/pages/pt/managing/_meta.js | 5 - website/pages/pt/network/_meta.js | 5 - website/pages/pt/publishing/_meta.js | 5 - website/pages/pt/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/ro/arbitrum/_meta.js | 5 - website/pages/ro/archived/_meta.js | 5 + website/pages/ro/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/ro/{ => archived}/sunrise.mdx | 0 website/pages/ro/{network => }/contracts.mdx | 0 website/pages/ro/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/ro/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../ro/{network => developing}/developing.mdx | 0 website/pages/ro/developing/graph-ts/_meta.js | 5 - website/pages/ro/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/ro/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/ro/{ => developing}/subgraphs.mdx | 0 website/pages/ro/{network => }/explorer.mdx | 0 website/pages/ro/indexer-tooling/_meta.js | 5 + .../ro/{ => indexer-tooling}/firehose.mdx | 0 .../ro/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/ro/{network => }/indexing.mdx | 0 website/pages/ro/managing/_meta.js | 5 - website/pages/ro/network/_meta.js | 5 - website/pages/ro/publishing/_meta.js | 5 - website/pages/ro/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/ru/arbitrum/_meta.js | 5 - website/pages/ru/archived/_meta.js | 5 + website/pages/ru/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/ru/{ => archived}/sunrise.mdx | 0 website/pages/ru/{network => }/contracts.mdx | 0 website/pages/ru/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/ru/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../ru/{network => developing}/developing.mdx | 0 website/pages/ru/developing/graph-ts/_meta.js | 5 - website/pages/ru/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/ru/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/ru/{ => developing}/subgraphs.mdx | 0 website/pages/ru/{network => }/explorer.mdx | 0 website/pages/ru/indexer-tooling/_meta.js | 5 + .../ru/{ => indexer-tooling}/firehose.mdx | 0 .../ru/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/ru/{network => }/indexing.mdx | 0 website/pages/ru/managing/_meta.js | 5 - website/pages/ru/network/_meta.js | 5 - website/pages/ru/publishing/_meta.js | 5 - website/pages/ru/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/sv/arbitrum/_meta.js | 5 - website/pages/sv/archived/_meta.js | 5 + website/pages/sv/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/sv/{ => archived}/sunrise.mdx | 0 website/pages/sv/{network => }/contracts.mdx | 0 website/pages/sv/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/sv/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../sv/{network => developing}/developing.mdx | 0 website/pages/sv/developing/graph-ts/_meta.js | 5 - website/pages/sv/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/sv/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/sv/{ => developing}/subgraphs.mdx | 0 website/pages/sv/{network => }/explorer.mdx | 0 website/pages/sv/indexer-tooling/_meta.js | 5 + .../sv/{ => indexer-tooling}/firehose.mdx | 0 .../sv/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/sv/{network => }/indexing.mdx | 0 website/pages/sv/managing/_meta.js | 5 - website/pages/sv/network/_meta.js | 5 - website/pages/sv/publishing/_meta.js | 5 - website/pages/sv/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/sw/arbitrum/_meta.js | 5 - website/pages/sw/archived/_meta.js | 5 + website/pages/sw/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/sw/{ => archived}/sunrise.mdx | 0 website/pages/sw/{network => }/contracts.mdx | 0 website/pages/sw/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/sw/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../sw/{network => developing}/developing.mdx | 0 website/pages/sw/developing/graph-ts/_meta.js | 5 - website/pages/sw/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/sw/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/sw/{ => developing}/subgraphs.mdx | 0 website/pages/sw/{network => }/explorer.mdx | 0 website/pages/sw/indexer-tooling/_meta.js | 5 + .../sw/{ => indexer-tooling}/firehose.mdx | 0 .../sw/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/sw/{network => }/indexing.mdx | 0 website/pages/sw/managing/_meta.js | 5 - website/pages/sw/network/_meta.js | 5 - website/pages/sw/publishing/_meta.js | 5 - website/pages/sw/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/tr/arbitrum/_meta.js | 5 - website/pages/tr/archived/_meta.js | 5 + website/pages/tr/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/tr/{ => archived}/sunrise.mdx | 0 website/pages/tr/{network => }/contracts.mdx | 0 website/pages/tr/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/tr/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../tr/{network => developing}/developing.mdx | 0 website/pages/tr/developing/graph-ts/_meta.js | 5 - website/pages/tr/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/tr/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/tr/{ => developing}/subgraphs.mdx | 0 website/pages/tr/{network => }/explorer.mdx | 0 website/pages/tr/indexer-tooling/_meta.js | 5 + .../tr/{ => indexer-tooling}/firehose.mdx | 0 .../tr/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/tr/{network => }/indexing.mdx | 0 website/pages/tr/managing/_meta.js | 5 - website/pages/tr/network/_meta.js | 5 - website/pages/tr/publishing/_meta.js | 5 - website/pages/tr/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/uk/arbitrum/_meta.js | 5 - website/pages/uk/archived/_meta.js | 5 + website/pages/uk/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/uk/{ => archived}/sunrise.mdx | 0 website/pages/uk/{network => }/contracts.mdx | 0 website/pages/uk/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/uk/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../uk/{network => developing}/developing.mdx | 0 website/pages/uk/developing/graph-ts/_meta.js | 5 - website/pages/uk/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/uk/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/uk/{ => developing}/subgraphs.mdx | 0 website/pages/uk/{network => }/explorer.mdx | 0 website/pages/uk/indexer-tooling/_meta.js | 5 + .../uk/{ => indexer-tooling}/firehose.mdx | 0 .../uk/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/uk/{network => }/indexing.mdx | 0 website/pages/uk/managing/_meta.js | 5 - website/pages/uk/network/_meta.js | 5 - website/pages/uk/publishing/_meta.js | 5 - website/pages/uk/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/ur/arbitrum/_meta.js | 5 - website/pages/ur/archived/_meta.js | 5 + website/pages/ur/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/ur/{ => archived}/sunrise.mdx | 0 website/pages/ur/{network => }/contracts.mdx | 0 website/pages/ur/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/ur/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../ur/{network => developing}/developing.mdx | 0 website/pages/ur/developing/graph-ts/_meta.js | 5 - website/pages/ur/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/ur/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/ur/{ => developing}/subgraphs.mdx | 0 website/pages/ur/{network => }/explorer.mdx | 0 website/pages/ur/indexer-tooling/_meta.js | 5 + .../ur/{ => indexer-tooling}/firehose.mdx | 0 .../ur/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/ur/{network => }/indexing.mdx | 0 website/pages/ur/managing/_meta.js | 5 - website/pages/ur/network/_meta.js | 5 - website/pages/ur/publishing/_meta.js | 5 - website/pages/ur/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/vi/arbitrum/_meta.js | 5 - website/pages/vi/archived/_meta.js | 5 + website/pages/vi/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/vi/{ => archived}/sunrise.mdx | 0 website/pages/vi/{network => }/contracts.mdx | 0 website/pages/vi/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/vi/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../vi/{network => developing}/developing.mdx | 0 website/pages/vi/developing/graph-ts/_meta.js | 5 - website/pages/vi/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/vi/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/vi/{ => developing}/subgraphs.mdx | 0 website/pages/vi/{network => }/explorer.mdx | 0 website/pages/vi/indexer-tooling/_meta.js | 5 + .../vi/{ => indexer-tooling}/firehose.mdx | 0 .../vi/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/vi/{network => }/indexing.mdx | 0 website/pages/vi/managing/_meta.js | 5 - website/pages/vi/network/_meta.js | 5 - website/pages/vi/publishing/_meta.js | 5 - website/pages/vi/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/pages/zh/arbitrum/_meta.js | 5 - website/pages/zh/archived/_meta.js | 5 + website/pages/zh/archived/arbitrum/_meta.js | 5 + .../{ => archived}/arbitrum/arbitrum-faq.mdx | 0 .../arbitrum/l2-transfer-tools-faq.mdx | 0 .../arbitrum/l2-transfer-tools-guide.mdx | 0 website/pages/zh/{ => archived}/sunrise.mdx | 0 website/pages/zh/{network => }/contracts.mdx | 0 website/pages/zh/deploying/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 + .../graph-ts/api.mdx | 0 .../graph-ts/common-issues.mdx | 0 .../unit-testing-framework.mdx | 0 .../pages/zh/developing/deploying/_meta.js | 5 + .../deploy-using-subgraph-studio.mdx | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../zh/{network => developing}/developing.mdx | 0 website/pages/zh/developing/graph-ts/_meta.js | 5 - website/pages/zh/developing/managing/_meta.js | 5 + .../managing/delete-a-subgraph.mdx | 0 .../managing/transfer-a-subgraph.mdx | 0 .../pages/zh/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../pages/zh/{ => developing}/subgraphs.mdx | 0 website/pages/zh/{network => }/explorer.mdx | 0 website/pages/zh/indexer-tooling/_meta.js | 5 + .../zh/{ => indexer-tooling}/firehose.mdx | 0 .../zh/{ => indexer-tooling}/graphcast.mdx | 0 .../operating-graph-node.mdx | 0 website/pages/zh/{network => }/indexing.mdx | 0 website/pages/zh/managing/_meta.js | 5 - website/pages/zh/network/_meta.js | 5 - website/pages/zh/publishing/_meta.js | 5 - website/pages/zh/roles-and-benefits/_meta.js | 5 + .../benefits.mdx | 0 .../curating.mdx | 0 .../delegating.mdx | 0 .../overview.mdx | 0 .../substreams-powered-subgraphs-faq.mdx | 0 website/route-lockfile.txt | 1200 ++++++++--------- 881 files changed, 1480 insertions(+), 1260 deletions(-) delete mode 100644 website/pages/ar/arbitrum/_meta.js create mode 100644 website/pages/ar/archived/_meta.js create mode 100644 website/pages/ar/archived/arbitrum/_meta.js rename website/pages/ar/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/ar/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/ar/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/ar/{ => archived}/sunrise.mdx (100%) rename website/pages/ar/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/ar/deploying/_meta.js create mode 100644 website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/ar/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/ar/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/ar/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ar/developing/deploying/_meta.js rename website/pages/ar/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/ar/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/ar/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ar/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/ar/developing/graph-ts/_meta.js create mode 100644 website/pages/ar/developing/managing/_meta.js rename website/pages/ar/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/ar/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/ar/developing/publishing/_meta.js rename website/pages/ar/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ar/{ => developing}/subgraphs.mdx (100%) rename website/pages/ar/{network => }/explorer.mdx (100%) create mode 100644 website/pages/ar/indexer-tooling/_meta.js rename website/pages/ar/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/ar/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/ar/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/ar/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/ar/managing/_meta.js delete mode 100644 website/pages/ar/network/_meta.js delete mode 100644 website/pages/ar/publishing/_meta.js create mode 100644 website/pages/ar/roles-and-benefits/_meta.js rename website/pages/ar/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/ar/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/ar/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/ar/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/ar/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/cs/arbitrum/_meta.js create mode 100644 website/pages/cs/archived/_meta.js create mode 100644 website/pages/cs/archived/arbitrum/_meta.js rename website/pages/cs/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/cs/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/cs/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/cs/{ => archived}/sunrise.mdx (100%) rename website/pages/cs/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/cs/deploying/_meta.js create mode 100644 website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/cs/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/cs/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/cs/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/cs/developing/deploying/_meta.js rename website/pages/cs/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/cs/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/cs/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/cs/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/cs/developing/graph-ts/_meta.js create mode 100644 website/pages/cs/developing/managing/_meta.js rename website/pages/cs/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/cs/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/cs/developing/publishing/_meta.js rename website/pages/cs/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/cs/{ => developing}/subgraphs.mdx (100%) rename website/pages/cs/{network => }/explorer.mdx (100%) create mode 100644 website/pages/cs/indexer-tooling/_meta.js rename website/pages/cs/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/cs/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/cs/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/cs/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/cs/managing/_meta.js delete mode 100644 website/pages/cs/network/_meta.js delete mode 100644 website/pages/cs/publishing/_meta.js create mode 100644 website/pages/cs/roles-and-benefits/_meta.js rename website/pages/cs/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/cs/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/cs/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/cs/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/cs/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/de/arbitrum/_meta.js create mode 100644 website/pages/de/archived/_meta.js create mode 100644 website/pages/de/archived/arbitrum/_meta.js rename website/pages/de/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/de/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/de/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/de/{ => archived}/sunrise.mdx (100%) rename website/pages/de/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/de/deploying/_meta.js create mode 100644 website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/de/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/de/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/de/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/de/developing/deploying/_meta.js rename website/pages/de/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/de/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/de/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/de/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/de/developing/graph-ts/_meta.js create mode 100644 website/pages/de/developing/managing/_meta.js rename website/pages/de/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/de/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/de/developing/publishing/_meta.js rename website/pages/de/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/de/{ => developing}/subgraphs.mdx (100%) rename website/pages/de/{network => }/explorer.mdx (100%) create mode 100644 website/pages/de/indexer-tooling/_meta.js rename website/pages/de/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/de/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/de/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/de/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/de/managing/_meta.js delete mode 100644 website/pages/de/network/_meta.js delete mode 100644 website/pages/de/publishing/_meta.js create mode 100644 website/pages/de/roles-and-benefits/_meta.js rename website/pages/de/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/de/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/de/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/de/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/de/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/es/arbitrum/_meta.js create mode 100644 website/pages/es/archived/_meta.js create mode 100644 website/pages/es/archived/arbitrum/_meta.js rename website/pages/es/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/es/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/es/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/es/{ => archived}/sunrise.mdx (100%) rename website/pages/es/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/es/deploying/_meta.js create mode 100644 website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/es/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/es/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/es/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/es/developing/deploying/_meta.js rename website/pages/es/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/es/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/es/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/es/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/es/developing/graph-ts/_meta.js create mode 100644 website/pages/es/developing/managing/_meta.js rename website/pages/es/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/es/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/es/developing/publishing/_meta.js rename website/pages/es/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/es/{ => developing}/subgraphs.mdx (100%) rename website/pages/es/{network => }/explorer.mdx (100%) create mode 100644 website/pages/es/indexer-tooling/_meta.js rename website/pages/es/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/es/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/es/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/es/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/es/managing/_meta.js delete mode 100644 website/pages/es/network/_meta.js delete mode 100644 website/pages/es/publishing/_meta.js create mode 100644 website/pages/es/roles-and-benefits/_meta.js rename website/pages/es/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/es/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/es/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/es/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/es/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/fr/arbitrum/_meta.js create mode 100644 website/pages/fr/archived/_meta.js create mode 100644 website/pages/fr/archived/arbitrum/_meta.js rename website/pages/fr/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/fr/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/fr/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/fr/{ => archived}/sunrise.mdx (100%) rename website/pages/fr/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/fr/deploying/_meta.js create mode 100644 website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/fr/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/fr/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/fr/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/fr/developing/deploying/_meta.js rename website/pages/fr/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/fr/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/fr/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/fr/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/fr/developing/graph-ts/_meta.js create mode 100644 website/pages/fr/developing/managing/_meta.js rename website/pages/fr/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/fr/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/fr/developing/publishing/_meta.js rename website/pages/fr/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/fr/{ => developing}/subgraphs.mdx (100%) rename website/pages/fr/{network => }/explorer.mdx (100%) create mode 100644 website/pages/fr/indexer-tooling/_meta.js rename website/pages/fr/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/fr/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/fr/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/fr/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/fr/managing/_meta.js delete mode 100644 website/pages/fr/network/_meta.js delete mode 100644 website/pages/fr/publishing/_meta.js create mode 100644 website/pages/fr/roles-and-benefits/_meta.js rename website/pages/fr/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/fr/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/fr/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/fr/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/fr/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/hi/arbitrum/_meta.js create mode 100644 website/pages/hi/archived/_meta.js create mode 100644 website/pages/hi/archived/arbitrum/_meta.js rename website/pages/hi/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/hi/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/hi/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/hi/{ => archived}/sunrise.mdx (100%) rename website/pages/hi/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/hi/deploying/_meta.js create mode 100644 website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/hi/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/hi/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/hi/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/hi/developing/deploying/_meta.js rename website/pages/hi/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/hi/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/hi/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/hi/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/hi/developing/graph-ts/_meta.js create mode 100644 website/pages/hi/developing/managing/_meta.js rename website/pages/hi/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/hi/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/hi/developing/publishing/_meta.js rename website/pages/hi/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/hi/{ => developing}/subgraphs.mdx (100%) rename website/pages/hi/{network => }/explorer.mdx (100%) create mode 100644 website/pages/hi/indexer-tooling/_meta.js rename website/pages/hi/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/hi/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/hi/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/hi/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/hi/managing/_meta.js delete mode 100644 website/pages/hi/network/_meta.js delete mode 100644 website/pages/hi/publishing/_meta.js create mode 100644 website/pages/hi/roles-and-benefits/_meta.js rename website/pages/hi/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/hi/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/hi/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/hi/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/hi/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/it/arbitrum/_meta.js create mode 100644 website/pages/it/archived/_meta.js create mode 100644 website/pages/it/archived/arbitrum/_meta.js rename website/pages/it/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/it/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/it/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/it/{ => archived}/sunrise.mdx (100%) rename website/pages/it/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/it/deploying/_meta.js create mode 100644 website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/it/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/it/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/it/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/it/developing/deploying/_meta.js rename website/pages/it/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/it/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/it/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/it/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/it/developing/graph-ts/_meta.js create mode 100644 website/pages/it/developing/managing/_meta.js rename website/pages/it/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/it/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/it/developing/publishing/_meta.js rename website/pages/it/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/it/{ => developing}/subgraphs.mdx (100%) rename website/pages/it/{network => }/explorer.mdx (100%) create mode 100644 website/pages/it/indexer-tooling/_meta.js rename website/pages/it/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/it/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/it/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/it/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/it/managing/_meta.js delete mode 100644 website/pages/it/network/_meta.js delete mode 100644 website/pages/it/publishing/_meta.js create mode 100644 website/pages/it/roles-and-benefits/_meta.js rename website/pages/it/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/it/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/it/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/it/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/it/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/ja/arbitrum/_meta.js create mode 100644 website/pages/ja/archived/_meta.js create mode 100644 website/pages/ja/archived/arbitrum/_meta.js rename website/pages/ja/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/ja/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/ja/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/ja/{ => archived}/sunrise.mdx (100%) rename website/pages/ja/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/ja/deploying/_meta.js create mode 100644 website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/ja/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/ja/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/ja/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ja/developing/deploying/_meta.js rename website/pages/ja/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/ja/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/ja/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ja/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/ja/developing/graph-ts/_meta.js create mode 100644 website/pages/ja/developing/managing/_meta.js rename website/pages/ja/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/ja/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/ja/developing/publishing/_meta.js rename website/pages/ja/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ja/{ => developing}/subgraphs.mdx (100%) rename website/pages/ja/{network => }/explorer.mdx (100%) create mode 100644 website/pages/ja/indexer-tooling/_meta.js rename website/pages/ja/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/ja/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/ja/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/ja/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/ja/managing/_meta.js delete mode 100644 website/pages/ja/network/_meta.js delete mode 100644 website/pages/ja/publishing/_meta.js create mode 100644 website/pages/ja/roles-and-benefits/_meta.js rename website/pages/ja/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/ja/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/ja/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/ja/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/ja/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/ko/arbitrum/_meta.js create mode 100644 website/pages/ko/archived/_meta.js create mode 100644 website/pages/ko/archived/arbitrum/_meta.js rename website/pages/ko/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/ko/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/ko/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/ko/{ => archived}/sunrise.mdx (100%) rename website/pages/ko/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/ko/deploying/_meta.js create mode 100644 website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/ko/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/ko/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/ko/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ko/developing/deploying/_meta.js rename website/pages/ko/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/ko/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/ko/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ko/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/ko/developing/graph-ts/_meta.js create mode 100644 website/pages/ko/developing/managing/_meta.js rename website/pages/ko/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/ko/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/ko/developing/publishing/_meta.js rename website/pages/ko/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ko/{ => developing}/subgraphs.mdx (100%) rename website/pages/ko/{network => }/explorer.mdx (100%) create mode 100644 website/pages/ko/indexer-tooling/_meta.js rename website/pages/ko/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/ko/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/ko/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/ko/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/ko/managing/_meta.js delete mode 100644 website/pages/ko/network/_meta.js delete mode 100644 website/pages/ko/publishing/_meta.js create mode 100644 website/pages/ko/roles-and-benefits/_meta.js rename website/pages/ko/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/ko/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/ko/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/ko/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/ko/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/mr/arbitrum/_meta.js create mode 100644 website/pages/mr/archived/_meta.js create mode 100644 website/pages/mr/archived/arbitrum/_meta.js rename website/pages/mr/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/mr/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/mr/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/mr/{ => archived}/sunrise.mdx (100%) rename website/pages/mr/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/mr/deploying/_meta.js create mode 100644 website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/mr/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/mr/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/mr/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/mr/developing/deploying/_meta.js rename website/pages/mr/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/mr/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/mr/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/mr/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/mr/developing/graph-ts/_meta.js create mode 100644 website/pages/mr/developing/managing/_meta.js rename website/pages/mr/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/mr/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/mr/developing/publishing/_meta.js rename website/pages/mr/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/mr/{ => developing}/subgraphs.mdx (100%) rename website/pages/mr/{network => }/explorer.mdx (100%) create mode 100644 website/pages/mr/indexer-tooling/_meta.js rename website/pages/mr/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/mr/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/mr/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/mr/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/mr/managing/_meta.js delete mode 100644 website/pages/mr/network/_meta.js delete mode 100644 website/pages/mr/publishing/_meta.js create mode 100644 website/pages/mr/roles-and-benefits/_meta.js rename website/pages/mr/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/mr/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/mr/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/mr/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/mr/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/nl/arbitrum/_meta.js create mode 100644 website/pages/nl/archived/_meta.js create mode 100644 website/pages/nl/archived/arbitrum/_meta.js rename website/pages/nl/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/nl/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/nl/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/nl/{ => archived}/sunrise.mdx (100%) rename website/pages/nl/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/nl/deploying/_meta.js create mode 100644 website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/nl/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/nl/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/nl/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/nl/developing/deploying/_meta.js rename website/pages/nl/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/nl/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/nl/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/nl/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/nl/developing/graph-ts/_meta.js create mode 100644 website/pages/nl/developing/managing/_meta.js rename website/pages/nl/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/nl/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/nl/developing/publishing/_meta.js rename website/pages/nl/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/nl/{ => developing}/subgraphs.mdx (100%) rename website/pages/nl/{network => }/explorer.mdx (100%) create mode 100644 website/pages/nl/indexer-tooling/_meta.js rename website/pages/nl/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/nl/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/nl/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/nl/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/nl/managing/_meta.js delete mode 100644 website/pages/nl/network/_meta.js delete mode 100644 website/pages/nl/publishing/_meta.js create mode 100644 website/pages/nl/roles-and-benefits/_meta.js rename website/pages/nl/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/nl/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/nl/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/nl/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/nl/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/pl/arbitrum/_meta.js create mode 100644 website/pages/pl/archived/_meta.js create mode 100644 website/pages/pl/archived/arbitrum/_meta.js rename website/pages/pl/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/pl/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/pl/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/pl/{ => archived}/sunrise.mdx (100%) rename website/pages/pl/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/pl/deploying/_meta.js create mode 100644 website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/pl/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/pl/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/pl/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/pl/developing/deploying/_meta.js rename website/pages/pl/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/pl/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/pl/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/pl/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/pl/developing/graph-ts/_meta.js create mode 100644 website/pages/pl/developing/managing/_meta.js rename website/pages/pl/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/pl/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/pl/developing/publishing/_meta.js rename website/pages/pl/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/pl/{ => developing}/subgraphs.mdx (100%) rename website/pages/pl/{network => }/explorer.mdx (100%) create mode 100644 website/pages/pl/indexer-tooling/_meta.js rename website/pages/pl/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/pl/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/pl/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/pl/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/pl/managing/_meta.js delete mode 100644 website/pages/pl/network/_meta.js delete mode 100644 website/pages/pl/publishing/_meta.js create mode 100644 website/pages/pl/roles-and-benefits/_meta.js rename website/pages/pl/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/pl/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/pl/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/pl/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/pl/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/pt/arbitrum/_meta.js create mode 100644 website/pages/pt/archived/_meta.js create mode 100644 website/pages/pt/archived/arbitrum/_meta.js rename website/pages/pt/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/pt/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/pt/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/pt/{ => archived}/sunrise.mdx (100%) rename website/pages/pt/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/pt/deploying/_meta.js create mode 100644 website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/pt/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/pt/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/pt/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/pt/developing/deploying/_meta.js rename website/pages/pt/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/pt/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/pt/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/pt/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/pt/developing/graph-ts/_meta.js create mode 100644 website/pages/pt/developing/managing/_meta.js rename website/pages/pt/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/pt/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/pt/developing/publishing/_meta.js rename website/pages/pt/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/pt/{ => developing}/subgraphs.mdx (100%) rename website/pages/pt/{network => }/explorer.mdx (100%) create mode 100644 website/pages/pt/indexer-tooling/_meta.js rename website/pages/pt/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/pt/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/pt/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/pt/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/pt/managing/_meta.js delete mode 100644 website/pages/pt/network/_meta.js delete mode 100644 website/pages/pt/publishing/_meta.js create mode 100644 website/pages/pt/roles-and-benefits/_meta.js rename website/pages/pt/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/pt/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/pt/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/pt/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/pt/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/ro/arbitrum/_meta.js create mode 100644 website/pages/ro/archived/_meta.js create mode 100644 website/pages/ro/archived/arbitrum/_meta.js rename website/pages/ro/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/ro/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/ro/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/ro/{ => archived}/sunrise.mdx (100%) rename website/pages/ro/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/ro/deploying/_meta.js create mode 100644 website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/ro/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/ro/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/ro/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ro/developing/deploying/_meta.js rename website/pages/ro/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/ro/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/ro/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ro/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/ro/developing/graph-ts/_meta.js create mode 100644 website/pages/ro/developing/managing/_meta.js rename website/pages/ro/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/ro/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/ro/developing/publishing/_meta.js rename website/pages/ro/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ro/{ => developing}/subgraphs.mdx (100%) rename website/pages/ro/{network => }/explorer.mdx (100%) create mode 100644 website/pages/ro/indexer-tooling/_meta.js rename website/pages/ro/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/ro/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/ro/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/ro/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/ro/managing/_meta.js delete mode 100644 website/pages/ro/network/_meta.js delete mode 100644 website/pages/ro/publishing/_meta.js create mode 100644 website/pages/ro/roles-and-benefits/_meta.js rename website/pages/ro/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/ro/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/ro/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/ro/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/ro/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/ru/arbitrum/_meta.js create mode 100644 website/pages/ru/archived/_meta.js create mode 100644 website/pages/ru/archived/arbitrum/_meta.js rename website/pages/ru/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/ru/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/ru/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/ru/{ => archived}/sunrise.mdx (100%) rename website/pages/ru/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/ru/deploying/_meta.js create mode 100644 website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/ru/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/ru/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/ru/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ru/developing/deploying/_meta.js rename website/pages/ru/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/ru/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/ru/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ru/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/ru/developing/graph-ts/_meta.js create mode 100644 website/pages/ru/developing/managing/_meta.js rename website/pages/ru/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/ru/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/ru/developing/publishing/_meta.js rename website/pages/ru/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ru/{ => developing}/subgraphs.mdx (100%) rename website/pages/ru/{network => }/explorer.mdx (100%) create mode 100644 website/pages/ru/indexer-tooling/_meta.js rename website/pages/ru/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/ru/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/ru/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/ru/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/ru/managing/_meta.js delete mode 100644 website/pages/ru/network/_meta.js delete mode 100644 website/pages/ru/publishing/_meta.js create mode 100644 website/pages/ru/roles-and-benefits/_meta.js rename website/pages/ru/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/ru/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/ru/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/ru/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/ru/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/sv/arbitrum/_meta.js create mode 100644 website/pages/sv/archived/_meta.js create mode 100644 website/pages/sv/archived/arbitrum/_meta.js rename website/pages/sv/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/sv/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/sv/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/sv/{ => archived}/sunrise.mdx (100%) rename website/pages/sv/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/sv/deploying/_meta.js create mode 100644 website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/sv/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/sv/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/sv/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/sv/developing/deploying/_meta.js rename website/pages/sv/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/sv/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/sv/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/sv/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/sv/developing/graph-ts/_meta.js create mode 100644 website/pages/sv/developing/managing/_meta.js rename website/pages/sv/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/sv/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/sv/developing/publishing/_meta.js rename website/pages/sv/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/sv/{ => developing}/subgraphs.mdx (100%) rename website/pages/sv/{network => }/explorer.mdx (100%) create mode 100644 website/pages/sv/indexer-tooling/_meta.js rename website/pages/sv/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/sv/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/sv/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/sv/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/sv/managing/_meta.js delete mode 100644 website/pages/sv/network/_meta.js delete mode 100644 website/pages/sv/publishing/_meta.js create mode 100644 website/pages/sv/roles-and-benefits/_meta.js rename website/pages/sv/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/sv/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/sv/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/sv/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/sv/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/sw/arbitrum/_meta.js create mode 100644 website/pages/sw/archived/_meta.js create mode 100644 website/pages/sw/archived/arbitrum/_meta.js rename website/pages/sw/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/sw/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/sw/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/sw/{ => archived}/sunrise.mdx (100%) rename website/pages/sw/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/sw/deploying/_meta.js create mode 100644 website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/sw/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/sw/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/sw/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/sw/developing/deploying/_meta.js rename website/pages/sw/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/sw/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/sw/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/sw/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/sw/developing/graph-ts/_meta.js create mode 100644 website/pages/sw/developing/managing/_meta.js rename website/pages/sw/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/sw/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/sw/developing/publishing/_meta.js rename website/pages/sw/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/sw/{ => developing}/subgraphs.mdx (100%) rename website/pages/sw/{network => }/explorer.mdx (100%) create mode 100644 website/pages/sw/indexer-tooling/_meta.js rename website/pages/sw/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/sw/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/sw/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/sw/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/sw/managing/_meta.js delete mode 100644 website/pages/sw/network/_meta.js delete mode 100644 website/pages/sw/publishing/_meta.js create mode 100644 website/pages/sw/roles-and-benefits/_meta.js rename website/pages/sw/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/sw/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/sw/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/sw/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/sw/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/tr/arbitrum/_meta.js create mode 100644 website/pages/tr/archived/_meta.js create mode 100644 website/pages/tr/archived/arbitrum/_meta.js rename website/pages/tr/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/tr/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/tr/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/tr/{ => archived}/sunrise.mdx (100%) rename website/pages/tr/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/tr/deploying/_meta.js create mode 100644 website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/tr/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/tr/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/tr/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/tr/developing/deploying/_meta.js rename website/pages/tr/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/tr/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/tr/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/tr/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/tr/developing/graph-ts/_meta.js create mode 100644 website/pages/tr/developing/managing/_meta.js rename website/pages/tr/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/tr/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/tr/developing/publishing/_meta.js rename website/pages/tr/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/tr/{ => developing}/subgraphs.mdx (100%) rename website/pages/tr/{network => }/explorer.mdx (100%) create mode 100644 website/pages/tr/indexer-tooling/_meta.js rename website/pages/tr/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/tr/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/tr/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/tr/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/tr/managing/_meta.js delete mode 100644 website/pages/tr/network/_meta.js delete mode 100644 website/pages/tr/publishing/_meta.js create mode 100644 website/pages/tr/roles-and-benefits/_meta.js rename website/pages/tr/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/tr/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/tr/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/tr/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/tr/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/uk/arbitrum/_meta.js create mode 100644 website/pages/uk/archived/_meta.js create mode 100644 website/pages/uk/archived/arbitrum/_meta.js rename website/pages/uk/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/uk/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/uk/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/uk/{ => archived}/sunrise.mdx (100%) rename website/pages/uk/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/uk/deploying/_meta.js create mode 100644 website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/uk/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/uk/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/uk/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/uk/developing/deploying/_meta.js rename website/pages/uk/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/uk/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/uk/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/uk/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/uk/developing/graph-ts/_meta.js create mode 100644 website/pages/uk/developing/managing/_meta.js rename website/pages/uk/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/uk/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/uk/developing/publishing/_meta.js rename website/pages/uk/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/uk/{ => developing}/subgraphs.mdx (100%) rename website/pages/uk/{network => }/explorer.mdx (100%) create mode 100644 website/pages/uk/indexer-tooling/_meta.js rename website/pages/uk/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/uk/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/uk/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/uk/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/uk/managing/_meta.js delete mode 100644 website/pages/uk/network/_meta.js delete mode 100644 website/pages/uk/publishing/_meta.js create mode 100644 website/pages/uk/roles-and-benefits/_meta.js rename website/pages/uk/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/uk/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/uk/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/uk/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/uk/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/ur/arbitrum/_meta.js create mode 100644 website/pages/ur/archived/_meta.js create mode 100644 website/pages/ur/archived/arbitrum/_meta.js rename website/pages/ur/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/ur/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/ur/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/ur/{ => archived}/sunrise.mdx (100%) rename website/pages/ur/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/ur/deploying/_meta.js create mode 100644 website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/ur/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/ur/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/ur/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ur/developing/deploying/_meta.js rename website/pages/ur/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/ur/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/ur/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ur/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/ur/developing/graph-ts/_meta.js create mode 100644 website/pages/ur/developing/managing/_meta.js rename website/pages/ur/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/ur/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/ur/developing/publishing/_meta.js rename website/pages/ur/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ur/{ => developing}/subgraphs.mdx (100%) rename website/pages/ur/{network => }/explorer.mdx (100%) create mode 100644 website/pages/ur/indexer-tooling/_meta.js rename website/pages/ur/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/ur/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/ur/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/ur/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/ur/managing/_meta.js delete mode 100644 website/pages/ur/network/_meta.js delete mode 100644 website/pages/ur/publishing/_meta.js create mode 100644 website/pages/ur/roles-and-benefits/_meta.js rename website/pages/ur/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/ur/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/ur/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/ur/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/ur/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/vi/arbitrum/_meta.js create mode 100644 website/pages/vi/archived/_meta.js create mode 100644 website/pages/vi/archived/arbitrum/_meta.js rename website/pages/vi/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/vi/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/vi/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/vi/{ => archived}/sunrise.mdx (100%) rename website/pages/vi/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/vi/deploying/_meta.js create mode 100644 website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/vi/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/vi/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/vi/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/vi/developing/deploying/_meta.js rename website/pages/vi/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/vi/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/vi/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/vi/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/vi/developing/graph-ts/_meta.js create mode 100644 website/pages/vi/developing/managing/_meta.js rename website/pages/vi/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/vi/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/vi/developing/publishing/_meta.js rename website/pages/vi/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/vi/{ => developing}/subgraphs.mdx (100%) rename website/pages/vi/{network => }/explorer.mdx (100%) create mode 100644 website/pages/vi/indexer-tooling/_meta.js rename website/pages/vi/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/vi/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/vi/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/vi/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/vi/managing/_meta.js delete mode 100644 website/pages/vi/network/_meta.js delete mode 100644 website/pages/vi/publishing/_meta.js create mode 100644 website/pages/vi/roles-and-benefits/_meta.js rename website/pages/vi/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/vi/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/vi/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/vi/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/vi/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) delete mode 100644 website/pages/zh/arbitrum/_meta.js create mode 100644 website/pages/zh/archived/_meta.js create mode 100644 website/pages/zh/archived/arbitrum/_meta.js rename website/pages/zh/{ => archived}/arbitrum/arbitrum-faq.mdx (100%) rename website/pages/zh/{ => archived}/arbitrum/l2-transfer-tools-faq.mdx (100%) rename website/pages/zh/{ => archived}/arbitrum/l2-transfer-tools-guide.mdx (100%) rename website/pages/zh/{ => archived}/sunrise.mdx (100%) rename website/pages/zh/{network => }/contracts.mdx (100%) delete mode 100644 website/pages/zh/deploying/_meta.js create mode 100644 website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js rename website/pages/zh/developing/{ => creating-a-subgraph}/graph-ts/api.mdx (100%) rename website/pages/zh/developing/{ => creating-a-subgraph}/graph-ts/common-issues.mdx (100%) rename website/pages/zh/developing/{ => creating-a-subgraph}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/zh/developing/deploying/_meta.js rename website/pages/zh/{ => developing}/deploying/deploy-using-subgraph-studio.mdx (100%) rename website/pages/zh/{ => developing}/deploying/multiple-networks.mdx (100%) rename website/pages/zh/{ => developing}/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/zh/{network => developing}/developing.mdx (100%) delete mode 100644 website/pages/zh/developing/graph-ts/_meta.js create mode 100644 website/pages/zh/developing/managing/_meta.js rename website/pages/zh/{ => developing}/managing/delete-a-subgraph.mdx (100%) rename website/pages/zh/{ => developing}/managing/transfer-a-subgraph.mdx (100%) create mode 100644 website/pages/zh/developing/publishing/_meta.js rename website/pages/zh/{ => developing}/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/zh/{ => developing}/subgraphs.mdx (100%) rename website/pages/zh/{network => }/explorer.mdx (100%) create mode 100644 website/pages/zh/indexer-tooling/_meta.js rename website/pages/zh/{ => indexer-tooling}/firehose.mdx (100%) rename website/pages/zh/{ => indexer-tooling}/graphcast.mdx (100%) rename website/pages/zh/{ => indexer-tooling}/operating-graph-node.mdx (100%) rename website/pages/zh/{network => }/indexing.mdx (100%) delete mode 100644 website/pages/zh/managing/_meta.js delete mode 100644 website/pages/zh/network/_meta.js delete mode 100644 website/pages/zh/publishing/_meta.js create mode 100644 website/pages/zh/roles-and-benefits/_meta.js rename website/pages/zh/{network => roles-and-benefits}/benefits.mdx (100%) rename website/pages/zh/{network => roles-and-benefits}/curating.mdx (100%) rename website/pages/zh/{network => roles-and-benefits}/delegating.mdx (100%) rename website/pages/zh/{network => roles-and-benefits}/overview.mdx (100%) rename website/pages/zh/{developing => sps}/substreams-powered-subgraphs-faq.mdx (100%) diff --git a/website/pages/ar/arbitrum/_meta.js b/website/pages/ar/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/ar/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/archived/_meta.js b/website/pages/ar/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/ar/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/archived/arbitrum/_meta.js b/website/pages/ar/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/ar/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/arbitrum/arbitrum-faq.mdx b/website/pages/ar/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/ar/arbitrum/arbitrum-faq.mdx rename to website/pages/ar/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/ar/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/ar/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/ar/sunrise.mdx b/website/pages/ar/archived/sunrise.mdx similarity index 100% rename from website/pages/ar/sunrise.mdx rename to website/pages/ar/archived/sunrise.mdx diff --git a/website/pages/ar/network/contracts.mdx b/website/pages/ar/contracts.mdx similarity index 100% rename from website/pages/ar/network/contracts.mdx rename to website/pages/ar/contracts.mdx diff --git a/website/pages/ar/deploying/_meta.js b/website/pages/ar/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/ar/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/developing/graph-ts/api.mdx b/website/pages/ar/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/ar/developing/graph-ts/api.mdx rename to website/pages/ar/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/ar/developing/graph-ts/common-issues.mdx b/website/pages/ar/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ar/developing/graph-ts/common-issues.mdx rename to website/pages/ar/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/ar/developing/unit-testing-framework.mdx b/website/pages/ar/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/ar/developing/unit-testing-framework.mdx rename to website/pages/ar/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/ar/developing/deploying/_meta.js b/website/pages/ar/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/ar/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ar/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/ar/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ar/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/ar/deploying/multiple-networks.mdx b/website/pages/ar/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ar/deploying/multiple-networks.mdx rename to website/pages/ar/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ar/deploying/subgraph-studio-faqs.mdx b/website/pages/ar/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ar/deploying/subgraph-studio-faqs.mdx rename to website/pages/ar/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ar/network/developing.mdx b/website/pages/ar/developing/developing.mdx similarity index 100% rename from website/pages/ar/network/developing.mdx rename to website/pages/ar/developing/developing.mdx diff --git a/website/pages/ar/developing/graph-ts/_meta.js b/website/pages/ar/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/ar/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/managing/_meta.js b/website/pages/ar/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/ar/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/managing/delete-a-subgraph.mdx b/website/pages/ar/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/ar/managing/delete-a-subgraph.mdx rename to website/pages/ar/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/ar/managing/transfer-a-subgraph.mdx b/website/pages/ar/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ar/managing/transfer-a-subgraph.mdx rename to website/pages/ar/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ar/developing/publishing/_meta.js b/website/pages/ar/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/ar/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/publishing/publishing-a-subgraph.mdx b/website/pages/ar/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ar/publishing/publishing-a-subgraph.mdx rename to website/pages/ar/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ar/subgraphs.mdx b/website/pages/ar/developing/subgraphs.mdx similarity index 100% rename from website/pages/ar/subgraphs.mdx rename to website/pages/ar/developing/subgraphs.mdx diff --git a/website/pages/ar/network/explorer.mdx b/website/pages/ar/explorer.mdx similarity index 100% rename from website/pages/ar/network/explorer.mdx rename to website/pages/ar/explorer.mdx diff --git a/website/pages/ar/indexer-tooling/_meta.js b/website/pages/ar/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/ar/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/firehose.mdx b/website/pages/ar/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/ar/firehose.mdx rename to website/pages/ar/indexer-tooling/firehose.mdx diff --git a/website/pages/ar/graphcast.mdx b/website/pages/ar/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/ar/graphcast.mdx rename to website/pages/ar/indexer-tooling/graphcast.mdx diff --git a/website/pages/ar/operating-graph-node.mdx b/website/pages/ar/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ar/operating-graph-node.mdx rename to website/pages/ar/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/ar/network/indexing.mdx b/website/pages/ar/indexing.mdx similarity index 100% rename from website/pages/ar/network/indexing.mdx rename to website/pages/ar/indexing.mdx diff --git a/website/pages/ar/managing/_meta.js b/website/pages/ar/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/ar/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/network/_meta.js b/website/pages/ar/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ar/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/publishing/_meta.js b/website/pages/ar/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/ar/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/roles-and-benefits/_meta.js b/website/pages/ar/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/ar/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/network/benefits.mdx b/website/pages/ar/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/ar/network/benefits.mdx rename to website/pages/ar/roles-and-benefits/benefits.mdx diff --git a/website/pages/ar/network/curating.mdx b/website/pages/ar/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/ar/network/curating.mdx rename to website/pages/ar/roles-and-benefits/curating.mdx diff --git a/website/pages/ar/network/delegating.mdx b/website/pages/ar/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/ar/network/delegating.mdx rename to website/pages/ar/roles-and-benefits/delegating.mdx diff --git a/website/pages/ar/network/overview.mdx b/website/pages/ar/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/ar/network/overview.mdx rename to website/pages/ar/roles-and-benefits/overview.mdx diff --git a/website/pages/ar/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ar/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ar/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/ar/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/cs/arbitrum/_meta.js b/website/pages/cs/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/cs/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/archived/_meta.js b/website/pages/cs/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/cs/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/archived/arbitrum/_meta.js b/website/pages/cs/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/cs/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/arbitrum/arbitrum-faq.mdx b/website/pages/cs/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/cs/arbitrum/arbitrum-faq.mdx rename to website/pages/cs/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/cs/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/cs/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/cs/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/cs/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/cs/sunrise.mdx b/website/pages/cs/archived/sunrise.mdx similarity index 100% rename from website/pages/cs/sunrise.mdx rename to website/pages/cs/archived/sunrise.mdx diff --git a/website/pages/cs/network/contracts.mdx b/website/pages/cs/contracts.mdx similarity index 100% rename from website/pages/cs/network/contracts.mdx rename to website/pages/cs/contracts.mdx diff --git a/website/pages/cs/deploying/_meta.js b/website/pages/cs/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/cs/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/developing/graph-ts/api.mdx b/website/pages/cs/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/cs/developing/graph-ts/api.mdx rename to website/pages/cs/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/cs/developing/graph-ts/common-issues.mdx b/website/pages/cs/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/cs/developing/graph-ts/common-issues.mdx rename to website/pages/cs/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/cs/developing/unit-testing-framework.mdx b/website/pages/cs/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/cs/developing/unit-testing-framework.mdx rename to website/pages/cs/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/cs/developing/deploying/_meta.js b/website/pages/cs/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/cs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/deploying/deploy-using-subgraph-studio.mdx b/website/pages/cs/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/cs/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/cs/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/cs/deploying/multiple-networks.mdx b/website/pages/cs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/cs/deploying/multiple-networks.mdx rename to website/pages/cs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/cs/deploying/subgraph-studio-faqs.mdx b/website/pages/cs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/cs/deploying/subgraph-studio-faqs.mdx rename to website/pages/cs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/cs/network/developing.mdx b/website/pages/cs/developing/developing.mdx similarity index 100% rename from website/pages/cs/network/developing.mdx rename to website/pages/cs/developing/developing.mdx diff --git a/website/pages/cs/developing/graph-ts/_meta.js b/website/pages/cs/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/cs/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/managing/_meta.js b/website/pages/cs/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/cs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/managing/delete-a-subgraph.mdx b/website/pages/cs/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/cs/managing/delete-a-subgraph.mdx rename to website/pages/cs/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/cs/managing/transfer-a-subgraph.mdx b/website/pages/cs/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/cs/managing/transfer-a-subgraph.mdx rename to website/pages/cs/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/cs/developing/publishing/_meta.js b/website/pages/cs/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/cs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/publishing/publishing-a-subgraph.mdx b/website/pages/cs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/cs/publishing/publishing-a-subgraph.mdx rename to website/pages/cs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/cs/subgraphs.mdx b/website/pages/cs/developing/subgraphs.mdx similarity index 100% rename from website/pages/cs/subgraphs.mdx rename to website/pages/cs/developing/subgraphs.mdx diff --git a/website/pages/cs/network/explorer.mdx b/website/pages/cs/explorer.mdx similarity index 100% rename from website/pages/cs/network/explorer.mdx rename to website/pages/cs/explorer.mdx diff --git a/website/pages/cs/indexer-tooling/_meta.js b/website/pages/cs/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/cs/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/firehose.mdx b/website/pages/cs/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/cs/firehose.mdx rename to website/pages/cs/indexer-tooling/firehose.mdx diff --git a/website/pages/cs/graphcast.mdx b/website/pages/cs/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/cs/graphcast.mdx rename to website/pages/cs/indexer-tooling/graphcast.mdx diff --git a/website/pages/cs/operating-graph-node.mdx b/website/pages/cs/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/cs/operating-graph-node.mdx rename to website/pages/cs/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/cs/network/indexing.mdx b/website/pages/cs/indexing.mdx similarity index 100% rename from website/pages/cs/network/indexing.mdx rename to website/pages/cs/indexing.mdx diff --git a/website/pages/cs/managing/_meta.js b/website/pages/cs/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/cs/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/network/_meta.js b/website/pages/cs/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/cs/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/publishing/_meta.js b/website/pages/cs/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/cs/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/roles-and-benefits/_meta.js b/website/pages/cs/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/cs/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/network/benefits.mdx b/website/pages/cs/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/cs/network/benefits.mdx rename to website/pages/cs/roles-and-benefits/benefits.mdx diff --git a/website/pages/cs/network/curating.mdx b/website/pages/cs/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/cs/network/curating.mdx rename to website/pages/cs/roles-and-benefits/curating.mdx diff --git a/website/pages/cs/network/delegating.mdx b/website/pages/cs/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/cs/network/delegating.mdx rename to website/pages/cs/roles-and-benefits/delegating.mdx diff --git a/website/pages/cs/network/overview.mdx b/website/pages/cs/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/cs/network/overview.mdx rename to website/pages/cs/roles-and-benefits/overview.mdx diff --git a/website/pages/cs/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/cs/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/cs/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/cs/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/de/arbitrum/_meta.js b/website/pages/de/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/de/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/archived/_meta.js b/website/pages/de/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/de/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/archived/arbitrum/_meta.js b/website/pages/de/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/de/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/arbitrum/arbitrum-faq.mdx b/website/pages/de/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/de/arbitrum/arbitrum-faq.mdx rename to website/pages/de/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/de/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/de/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/de/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/de/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/de/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/de/sunrise.mdx b/website/pages/de/archived/sunrise.mdx similarity index 100% rename from website/pages/de/sunrise.mdx rename to website/pages/de/archived/sunrise.mdx diff --git a/website/pages/de/network/contracts.mdx b/website/pages/de/contracts.mdx similarity index 100% rename from website/pages/de/network/contracts.mdx rename to website/pages/de/contracts.mdx diff --git a/website/pages/de/deploying/_meta.js b/website/pages/de/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/de/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/developing/graph-ts/api.mdx b/website/pages/de/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/de/developing/graph-ts/api.mdx rename to website/pages/de/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/de/developing/graph-ts/common-issues.mdx b/website/pages/de/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/de/developing/graph-ts/common-issues.mdx rename to website/pages/de/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/de/developing/unit-testing-framework.mdx b/website/pages/de/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/de/developing/unit-testing-framework.mdx rename to website/pages/de/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/de/developing/deploying/_meta.js b/website/pages/de/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/de/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/deploying/deploy-using-subgraph-studio.mdx b/website/pages/de/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/de/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/de/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/de/deploying/multiple-networks.mdx b/website/pages/de/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/de/deploying/multiple-networks.mdx rename to website/pages/de/developing/deploying/multiple-networks.mdx diff --git a/website/pages/de/deploying/subgraph-studio-faqs.mdx b/website/pages/de/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/de/deploying/subgraph-studio-faqs.mdx rename to website/pages/de/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/de/network/developing.mdx b/website/pages/de/developing/developing.mdx similarity index 100% rename from website/pages/de/network/developing.mdx rename to website/pages/de/developing/developing.mdx diff --git a/website/pages/de/developing/graph-ts/_meta.js b/website/pages/de/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/de/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/managing/_meta.js b/website/pages/de/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/de/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/managing/delete-a-subgraph.mdx b/website/pages/de/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/de/managing/delete-a-subgraph.mdx rename to website/pages/de/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/de/managing/transfer-a-subgraph.mdx b/website/pages/de/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/de/managing/transfer-a-subgraph.mdx rename to website/pages/de/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/de/developing/publishing/_meta.js b/website/pages/de/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/de/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/publishing/publishing-a-subgraph.mdx b/website/pages/de/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/de/publishing/publishing-a-subgraph.mdx rename to website/pages/de/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/de/subgraphs.mdx b/website/pages/de/developing/subgraphs.mdx similarity index 100% rename from website/pages/de/subgraphs.mdx rename to website/pages/de/developing/subgraphs.mdx diff --git a/website/pages/de/network/explorer.mdx b/website/pages/de/explorer.mdx similarity index 100% rename from website/pages/de/network/explorer.mdx rename to website/pages/de/explorer.mdx diff --git a/website/pages/de/indexer-tooling/_meta.js b/website/pages/de/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/de/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/firehose.mdx b/website/pages/de/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/de/firehose.mdx rename to website/pages/de/indexer-tooling/firehose.mdx diff --git a/website/pages/de/graphcast.mdx b/website/pages/de/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/de/graphcast.mdx rename to website/pages/de/indexer-tooling/graphcast.mdx diff --git a/website/pages/de/operating-graph-node.mdx b/website/pages/de/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/de/operating-graph-node.mdx rename to website/pages/de/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/de/network/indexing.mdx b/website/pages/de/indexing.mdx similarity index 100% rename from website/pages/de/network/indexing.mdx rename to website/pages/de/indexing.mdx diff --git a/website/pages/de/managing/_meta.js b/website/pages/de/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/de/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/network/_meta.js b/website/pages/de/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/de/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/publishing/_meta.js b/website/pages/de/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/de/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/roles-and-benefits/_meta.js b/website/pages/de/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/de/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/network/benefits.mdx b/website/pages/de/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/de/network/benefits.mdx rename to website/pages/de/roles-and-benefits/benefits.mdx diff --git a/website/pages/de/network/curating.mdx b/website/pages/de/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/de/network/curating.mdx rename to website/pages/de/roles-and-benefits/curating.mdx diff --git a/website/pages/de/network/delegating.mdx b/website/pages/de/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/de/network/delegating.mdx rename to website/pages/de/roles-and-benefits/delegating.mdx diff --git a/website/pages/de/network/overview.mdx b/website/pages/de/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/de/network/overview.mdx rename to website/pages/de/roles-and-benefits/overview.mdx diff --git a/website/pages/de/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/de/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/de/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/de/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/es/arbitrum/_meta.js b/website/pages/es/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/es/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/archived/_meta.js b/website/pages/es/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/es/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/archived/arbitrum/_meta.js b/website/pages/es/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/es/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/arbitrum/arbitrum-faq.mdx b/website/pages/es/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/es/arbitrum/arbitrum-faq.mdx rename to website/pages/es/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/es/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/es/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/es/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/es/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/es/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/es/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/es/sunrise.mdx b/website/pages/es/archived/sunrise.mdx similarity index 100% rename from website/pages/es/sunrise.mdx rename to website/pages/es/archived/sunrise.mdx diff --git a/website/pages/es/network/contracts.mdx b/website/pages/es/contracts.mdx similarity index 100% rename from website/pages/es/network/contracts.mdx rename to website/pages/es/contracts.mdx diff --git a/website/pages/es/deploying/_meta.js b/website/pages/es/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/es/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/developing/graph-ts/api.mdx b/website/pages/es/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/es/developing/graph-ts/api.mdx rename to website/pages/es/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/es/developing/graph-ts/common-issues.mdx b/website/pages/es/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/es/developing/graph-ts/common-issues.mdx rename to website/pages/es/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/es/developing/unit-testing-framework.mdx b/website/pages/es/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/es/developing/unit-testing-framework.mdx rename to website/pages/es/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/es/developing/deploying/_meta.js b/website/pages/es/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/es/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/deploying/deploy-using-subgraph-studio.mdx b/website/pages/es/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/es/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/es/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/es/deploying/multiple-networks.mdx b/website/pages/es/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/es/deploying/multiple-networks.mdx rename to website/pages/es/developing/deploying/multiple-networks.mdx diff --git a/website/pages/es/deploying/subgraph-studio-faqs.mdx b/website/pages/es/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/es/deploying/subgraph-studio-faqs.mdx rename to website/pages/es/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/es/network/developing.mdx b/website/pages/es/developing/developing.mdx similarity index 100% rename from website/pages/es/network/developing.mdx rename to website/pages/es/developing/developing.mdx diff --git a/website/pages/es/developing/graph-ts/_meta.js b/website/pages/es/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/es/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/managing/_meta.js b/website/pages/es/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/es/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/managing/delete-a-subgraph.mdx b/website/pages/es/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/es/managing/delete-a-subgraph.mdx rename to website/pages/es/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/es/managing/transfer-a-subgraph.mdx b/website/pages/es/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/es/managing/transfer-a-subgraph.mdx rename to website/pages/es/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/es/developing/publishing/_meta.js b/website/pages/es/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/es/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/publishing/publishing-a-subgraph.mdx b/website/pages/es/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/es/publishing/publishing-a-subgraph.mdx rename to website/pages/es/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/es/subgraphs.mdx b/website/pages/es/developing/subgraphs.mdx similarity index 100% rename from website/pages/es/subgraphs.mdx rename to website/pages/es/developing/subgraphs.mdx diff --git a/website/pages/es/network/explorer.mdx b/website/pages/es/explorer.mdx similarity index 100% rename from website/pages/es/network/explorer.mdx rename to website/pages/es/explorer.mdx diff --git a/website/pages/es/indexer-tooling/_meta.js b/website/pages/es/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/es/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/firehose.mdx b/website/pages/es/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/es/firehose.mdx rename to website/pages/es/indexer-tooling/firehose.mdx diff --git a/website/pages/es/graphcast.mdx b/website/pages/es/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/es/graphcast.mdx rename to website/pages/es/indexer-tooling/graphcast.mdx diff --git a/website/pages/es/operating-graph-node.mdx b/website/pages/es/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/es/operating-graph-node.mdx rename to website/pages/es/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/es/network/indexing.mdx b/website/pages/es/indexing.mdx similarity index 100% rename from website/pages/es/network/indexing.mdx rename to website/pages/es/indexing.mdx diff --git a/website/pages/es/managing/_meta.js b/website/pages/es/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/es/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/network/_meta.js b/website/pages/es/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/es/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/publishing/_meta.js b/website/pages/es/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/es/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/roles-and-benefits/_meta.js b/website/pages/es/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/es/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/network/benefits.mdx b/website/pages/es/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/es/network/benefits.mdx rename to website/pages/es/roles-and-benefits/benefits.mdx diff --git a/website/pages/es/network/curating.mdx b/website/pages/es/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/es/network/curating.mdx rename to website/pages/es/roles-and-benefits/curating.mdx diff --git a/website/pages/es/network/delegating.mdx b/website/pages/es/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/es/network/delegating.mdx rename to website/pages/es/roles-and-benefits/delegating.mdx diff --git a/website/pages/es/network/overview.mdx b/website/pages/es/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/es/network/overview.mdx rename to website/pages/es/roles-and-benefits/overview.mdx diff --git a/website/pages/es/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/es/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/es/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/es/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/fr/arbitrum/_meta.js b/website/pages/fr/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/fr/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/archived/_meta.js b/website/pages/fr/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/fr/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/archived/arbitrum/_meta.js b/website/pages/fr/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/fr/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/arbitrum/arbitrum-faq.mdx b/website/pages/fr/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/fr/arbitrum/arbitrum-faq.mdx rename to website/pages/fr/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/fr/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/fr/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/fr/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/fr/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/fr/sunrise.mdx b/website/pages/fr/archived/sunrise.mdx similarity index 100% rename from website/pages/fr/sunrise.mdx rename to website/pages/fr/archived/sunrise.mdx diff --git a/website/pages/fr/network/contracts.mdx b/website/pages/fr/contracts.mdx similarity index 100% rename from website/pages/fr/network/contracts.mdx rename to website/pages/fr/contracts.mdx diff --git a/website/pages/fr/deploying/_meta.js b/website/pages/fr/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/fr/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/developing/graph-ts/api.mdx b/website/pages/fr/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/fr/developing/graph-ts/api.mdx rename to website/pages/fr/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/fr/developing/graph-ts/common-issues.mdx b/website/pages/fr/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/fr/developing/graph-ts/common-issues.mdx rename to website/pages/fr/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/fr/developing/unit-testing-framework.mdx b/website/pages/fr/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/fr/developing/unit-testing-framework.mdx rename to website/pages/fr/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/fr/developing/deploying/_meta.js b/website/pages/fr/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/fr/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/deploying/deploy-using-subgraph-studio.mdx b/website/pages/fr/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/fr/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/fr/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/fr/deploying/multiple-networks.mdx b/website/pages/fr/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/fr/deploying/multiple-networks.mdx rename to website/pages/fr/developing/deploying/multiple-networks.mdx diff --git a/website/pages/fr/deploying/subgraph-studio-faqs.mdx b/website/pages/fr/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/fr/deploying/subgraph-studio-faqs.mdx rename to website/pages/fr/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/fr/network/developing.mdx b/website/pages/fr/developing/developing.mdx similarity index 100% rename from website/pages/fr/network/developing.mdx rename to website/pages/fr/developing/developing.mdx diff --git a/website/pages/fr/developing/graph-ts/_meta.js b/website/pages/fr/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/fr/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/managing/_meta.js b/website/pages/fr/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/fr/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/managing/delete-a-subgraph.mdx b/website/pages/fr/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/fr/managing/delete-a-subgraph.mdx rename to website/pages/fr/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/fr/managing/transfer-a-subgraph.mdx b/website/pages/fr/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/fr/managing/transfer-a-subgraph.mdx rename to website/pages/fr/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/fr/developing/publishing/_meta.js b/website/pages/fr/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/fr/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/publishing/publishing-a-subgraph.mdx b/website/pages/fr/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/fr/publishing/publishing-a-subgraph.mdx rename to website/pages/fr/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/fr/subgraphs.mdx b/website/pages/fr/developing/subgraphs.mdx similarity index 100% rename from website/pages/fr/subgraphs.mdx rename to website/pages/fr/developing/subgraphs.mdx diff --git a/website/pages/fr/network/explorer.mdx b/website/pages/fr/explorer.mdx similarity index 100% rename from website/pages/fr/network/explorer.mdx rename to website/pages/fr/explorer.mdx diff --git a/website/pages/fr/indexer-tooling/_meta.js b/website/pages/fr/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/fr/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/firehose.mdx b/website/pages/fr/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/fr/firehose.mdx rename to website/pages/fr/indexer-tooling/firehose.mdx diff --git a/website/pages/fr/graphcast.mdx b/website/pages/fr/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/fr/graphcast.mdx rename to website/pages/fr/indexer-tooling/graphcast.mdx diff --git a/website/pages/fr/operating-graph-node.mdx b/website/pages/fr/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/fr/operating-graph-node.mdx rename to website/pages/fr/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/fr/network/indexing.mdx b/website/pages/fr/indexing.mdx similarity index 100% rename from website/pages/fr/network/indexing.mdx rename to website/pages/fr/indexing.mdx diff --git a/website/pages/fr/managing/_meta.js b/website/pages/fr/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/fr/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/network/_meta.js b/website/pages/fr/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/fr/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/publishing/_meta.js b/website/pages/fr/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/fr/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/roles-and-benefits/_meta.js b/website/pages/fr/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/fr/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/network/benefits.mdx b/website/pages/fr/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/fr/network/benefits.mdx rename to website/pages/fr/roles-and-benefits/benefits.mdx diff --git a/website/pages/fr/network/curating.mdx b/website/pages/fr/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/fr/network/curating.mdx rename to website/pages/fr/roles-and-benefits/curating.mdx diff --git a/website/pages/fr/network/delegating.mdx b/website/pages/fr/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/fr/network/delegating.mdx rename to website/pages/fr/roles-and-benefits/delegating.mdx diff --git a/website/pages/fr/network/overview.mdx b/website/pages/fr/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/fr/network/overview.mdx rename to website/pages/fr/roles-and-benefits/overview.mdx diff --git a/website/pages/fr/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/fr/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/fr/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/fr/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/hi/arbitrum/_meta.js b/website/pages/hi/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/hi/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/archived/_meta.js b/website/pages/hi/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/hi/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/archived/arbitrum/_meta.js b/website/pages/hi/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/hi/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/arbitrum/arbitrum-faq.mdx b/website/pages/hi/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/hi/arbitrum/arbitrum-faq.mdx rename to website/pages/hi/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/hi/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/hi/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/hi/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/hi/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/hi/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/hi/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/hi/sunrise.mdx b/website/pages/hi/archived/sunrise.mdx similarity index 100% rename from website/pages/hi/sunrise.mdx rename to website/pages/hi/archived/sunrise.mdx diff --git a/website/pages/hi/network/contracts.mdx b/website/pages/hi/contracts.mdx similarity index 100% rename from website/pages/hi/network/contracts.mdx rename to website/pages/hi/contracts.mdx diff --git a/website/pages/hi/deploying/_meta.js b/website/pages/hi/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/hi/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/developing/graph-ts/api.mdx b/website/pages/hi/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/hi/developing/graph-ts/api.mdx rename to website/pages/hi/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/hi/developing/graph-ts/common-issues.mdx b/website/pages/hi/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/hi/developing/graph-ts/common-issues.mdx rename to website/pages/hi/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/hi/developing/unit-testing-framework.mdx b/website/pages/hi/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/hi/developing/unit-testing-framework.mdx rename to website/pages/hi/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/hi/developing/deploying/_meta.js b/website/pages/hi/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/hi/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx b/website/pages/hi/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/hi/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/hi/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/hi/deploying/multiple-networks.mdx b/website/pages/hi/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/hi/deploying/multiple-networks.mdx rename to website/pages/hi/developing/deploying/multiple-networks.mdx diff --git a/website/pages/hi/deploying/subgraph-studio-faqs.mdx b/website/pages/hi/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/hi/deploying/subgraph-studio-faqs.mdx rename to website/pages/hi/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/hi/network/developing.mdx b/website/pages/hi/developing/developing.mdx similarity index 100% rename from website/pages/hi/network/developing.mdx rename to website/pages/hi/developing/developing.mdx diff --git a/website/pages/hi/developing/graph-ts/_meta.js b/website/pages/hi/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/hi/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/managing/_meta.js b/website/pages/hi/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/hi/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/managing/delete-a-subgraph.mdx b/website/pages/hi/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/hi/managing/delete-a-subgraph.mdx rename to website/pages/hi/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/hi/managing/transfer-a-subgraph.mdx b/website/pages/hi/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/hi/managing/transfer-a-subgraph.mdx rename to website/pages/hi/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/hi/developing/publishing/_meta.js b/website/pages/hi/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/hi/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/publishing/publishing-a-subgraph.mdx b/website/pages/hi/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/hi/publishing/publishing-a-subgraph.mdx rename to website/pages/hi/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/hi/subgraphs.mdx b/website/pages/hi/developing/subgraphs.mdx similarity index 100% rename from website/pages/hi/subgraphs.mdx rename to website/pages/hi/developing/subgraphs.mdx diff --git a/website/pages/hi/network/explorer.mdx b/website/pages/hi/explorer.mdx similarity index 100% rename from website/pages/hi/network/explorer.mdx rename to website/pages/hi/explorer.mdx diff --git a/website/pages/hi/indexer-tooling/_meta.js b/website/pages/hi/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/hi/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/firehose.mdx b/website/pages/hi/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/hi/firehose.mdx rename to website/pages/hi/indexer-tooling/firehose.mdx diff --git a/website/pages/hi/graphcast.mdx b/website/pages/hi/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/hi/graphcast.mdx rename to website/pages/hi/indexer-tooling/graphcast.mdx diff --git a/website/pages/hi/operating-graph-node.mdx b/website/pages/hi/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/hi/operating-graph-node.mdx rename to website/pages/hi/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/hi/network/indexing.mdx b/website/pages/hi/indexing.mdx similarity index 100% rename from website/pages/hi/network/indexing.mdx rename to website/pages/hi/indexing.mdx diff --git a/website/pages/hi/managing/_meta.js b/website/pages/hi/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/hi/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/network/_meta.js b/website/pages/hi/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/hi/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/publishing/_meta.js b/website/pages/hi/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/hi/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/roles-and-benefits/_meta.js b/website/pages/hi/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/hi/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/network/benefits.mdx b/website/pages/hi/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/hi/network/benefits.mdx rename to website/pages/hi/roles-and-benefits/benefits.mdx diff --git a/website/pages/hi/network/curating.mdx b/website/pages/hi/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/hi/network/curating.mdx rename to website/pages/hi/roles-and-benefits/curating.mdx diff --git a/website/pages/hi/network/delegating.mdx b/website/pages/hi/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/hi/network/delegating.mdx rename to website/pages/hi/roles-and-benefits/delegating.mdx diff --git a/website/pages/hi/network/overview.mdx b/website/pages/hi/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/hi/network/overview.mdx rename to website/pages/hi/roles-and-benefits/overview.mdx diff --git a/website/pages/hi/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/hi/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/hi/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/hi/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/it/arbitrum/_meta.js b/website/pages/it/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/it/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/archived/_meta.js b/website/pages/it/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/it/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/archived/arbitrum/_meta.js b/website/pages/it/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/it/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/arbitrum/arbitrum-faq.mdx b/website/pages/it/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/it/arbitrum/arbitrum-faq.mdx rename to website/pages/it/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/it/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/it/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/it/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/it/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/it/sunrise.mdx b/website/pages/it/archived/sunrise.mdx similarity index 100% rename from website/pages/it/sunrise.mdx rename to website/pages/it/archived/sunrise.mdx diff --git a/website/pages/it/network/contracts.mdx b/website/pages/it/contracts.mdx similarity index 100% rename from website/pages/it/network/contracts.mdx rename to website/pages/it/contracts.mdx diff --git a/website/pages/it/deploying/_meta.js b/website/pages/it/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/it/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/developing/graph-ts/api.mdx b/website/pages/it/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/it/developing/graph-ts/api.mdx rename to website/pages/it/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/it/developing/graph-ts/common-issues.mdx b/website/pages/it/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/it/developing/graph-ts/common-issues.mdx rename to website/pages/it/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/it/developing/unit-testing-framework.mdx b/website/pages/it/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/it/developing/unit-testing-framework.mdx rename to website/pages/it/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/it/developing/deploying/_meta.js b/website/pages/it/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/it/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/deploying/deploy-using-subgraph-studio.mdx b/website/pages/it/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/it/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/it/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/it/deploying/multiple-networks.mdx b/website/pages/it/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/it/deploying/multiple-networks.mdx rename to website/pages/it/developing/deploying/multiple-networks.mdx diff --git a/website/pages/it/deploying/subgraph-studio-faqs.mdx b/website/pages/it/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/it/deploying/subgraph-studio-faqs.mdx rename to website/pages/it/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/it/network/developing.mdx b/website/pages/it/developing/developing.mdx similarity index 100% rename from website/pages/it/network/developing.mdx rename to website/pages/it/developing/developing.mdx diff --git a/website/pages/it/developing/graph-ts/_meta.js b/website/pages/it/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/it/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/managing/_meta.js b/website/pages/it/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/it/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/managing/delete-a-subgraph.mdx b/website/pages/it/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/it/managing/delete-a-subgraph.mdx rename to website/pages/it/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/it/managing/transfer-a-subgraph.mdx b/website/pages/it/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/it/managing/transfer-a-subgraph.mdx rename to website/pages/it/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/it/developing/publishing/_meta.js b/website/pages/it/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/it/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/publishing/publishing-a-subgraph.mdx b/website/pages/it/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/it/publishing/publishing-a-subgraph.mdx rename to website/pages/it/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/it/subgraphs.mdx b/website/pages/it/developing/subgraphs.mdx similarity index 100% rename from website/pages/it/subgraphs.mdx rename to website/pages/it/developing/subgraphs.mdx diff --git a/website/pages/it/network/explorer.mdx b/website/pages/it/explorer.mdx similarity index 100% rename from website/pages/it/network/explorer.mdx rename to website/pages/it/explorer.mdx diff --git a/website/pages/it/indexer-tooling/_meta.js b/website/pages/it/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/it/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/firehose.mdx b/website/pages/it/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/it/firehose.mdx rename to website/pages/it/indexer-tooling/firehose.mdx diff --git a/website/pages/it/graphcast.mdx b/website/pages/it/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/it/graphcast.mdx rename to website/pages/it/indexer-tooling/graphcast.mdx diff --git a/website/pages/it/operating-graph-node.mdx b/website/pages/it/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/it/operating-graph-node.mdx rename to website/pages/it/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/it/network/indexing.mdx b/website/pages/it/indexing.mdx similarity index 100% rename from website/pages/it/network/indexing.mdx rename to website/pages/it/indexing.mdx diff --git a/website/pages/it/managing/_meta.js b/website/pages/it/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/it/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/network/_meta.js b/website/pages/it/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/it/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/publishing/_meta.js b/website/pages/it/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/it/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/roles-and-benefits/_meta.js b/website/pages/it/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/it/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/network/benefits.mdx b/website/pages/it/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/it/network/benefits.mdx rename to website/pages/it/roles-and-benefits/benefits.mdx diff --git a/website/pages/it/network/curating.mdx b/website/pages/it/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/it/network/curating.mdx rename to website/pages/it/roles-and-benefits/curating.mdx diff --git a/website/pages/it/network/delegating.mdx b/website/pages/it/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/it/network/delegating.mdx rename to website/pages/it/roles-and-benefits/delegating.mdx diff --git a/website/pages/it/network/overview.mdx b/website/pages/it/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/it/network/overview.mdx rename to website/pages/it/roles-and-benefits/overview.mdx diff --git a/website/pages/it/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/it/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/it/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/it/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ja/arbitrum/_meta.js b/website/pages/ja/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/ja/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/archived/_meta.js b/website/pages/ja/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/ja/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/archived/arbitrum/_meta.js b/website/pages/ja/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/ja/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/arbitrum/arbitrum-faq.mdx b/website/pages/ja/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/ja/arbitrum/arbitrum-faq.mdx rename to website/pages/ja/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/ja/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ja/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/ja/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/ja/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/ja/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/ja/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/ja/sunrise.mdx b/website/pages/ja/archived/sunrise.mdx similarity index 100% rename from website/pages/ja/sunrise.mdx rename to website/pages/ja/archived/sunrise.mdx diff --git a/website/pages/ja/network/contracts.mdx b/website/pages/ja/contracts.mdx similarity index 100% rename from website/pages/ja/network/contracts.mdx rename to website/pages/ja/contracts.mdx diff --git a/website/pages/ja/deploying/_meta.js b/website/pages/ja/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/ja/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/developing/graph-ts/api.mdx b/website/pages/ja/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/ja/developing/graph-ts/api.mdx rename to website/pages/ja/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/ja/developing/graph-ts/common-issues.mdx b/website/pages/ja/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ja/developing/graph-ts/common-issues.mdx rename to website/pages/ja/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/ja/developing/unit-testing-framework.mdx b/website/pages/ja/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/ja/developing/unit-testing-framework.mdx rename to website/pages/ja/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/ja/developing/deploying/_meta.js b/website/pages/ja/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/ja/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ja/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/ja/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ja/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/ja/deploying/multiple-networks.mdx b/website/pages/ja/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ja/deploying/multiple-networks.mdx rename to website/pages/ja/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ja/deploying/subgraph-studio-faqs.mdx b/website/pages/ja/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ja/deploying/subgraph-studio-faqs.mdx rename to website/pages/ja/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ja/network/developing.mdx b/website/pages/ja/developing/developing.mdx similarity index 100% rename from website/pages/ja/network/developing.mdx rename to website/pages/ja/developing/developing.mdx diff --git a/website/pages/ja/developing/graph-ts/_meta.js b/website/pages/ja/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/ja/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/managing/_meta.js b/website/pages/ja/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/ja/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/managing/delete-a-subgraph.mdx b/website/pages/ja/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/ja/managing/delete-a-subgraph.mdx rename to website/pages/ja/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/ja/managing/transfer-a-subgraph.mdx b/website/pages/ja/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ja/managing/transfer-a-subgraph.mdx rename to website/pages/ja/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ja/developing/publishing/_meta.js b/website/pages/ja/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/ja/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/publishing/publishing-a-subgraph.mdx b/website/pages/ja/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ja/publishing/publishing-a-subgraph.mdx rename to website/pages/ja/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ja/subgraphs.mdx b/website/pages/ja/developing/subgraphs.mdx similarity index 100% rename from website/pages/ja/subgraphs.mdx rename to website/pages/ja/developing/subgraphs.mdx diff --git a/website/pages/ja/network/explorer.mdx b/website/pages/ja/explorer.mdx similarity index 100% rename from website/pages/ja/network/explorer.mdx rename to website/pages/ja/explorer.mdx diff --git a/website/pages/ja/indexer-tooling/_meta.js b/website/pages/ja/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/ja/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/firehose.mdx b/website/pages/ja/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/ja/firehose.mdx rename to website/pages/ja/indexer-tooling/firehose.mdx diff --git a/website/pages/ja/graphcast.mdx b/website/pages/ja/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/ja/graphcast.mdx rename to website/pages/ja/indexer-tooling/graphcast.mdx diff --git a/website/pages/ja/operating-graph-node.mdx b/website/pages/ja/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ja/operating-graph-node.mdx rename to website/pages/ja/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/ja/network/indexing.mdx b/website/pages/ja/indexing.mdx similarity index 100% rename from website/pages/ja/network/indexing.mdx rename to website/pages/ja/indexing.mdx diff --git a/website/pages/ja/managing/_meta.js b/website/pages/ja/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/ja/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/network/_meta.js b/website/pages/ja/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ja/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/publishing/_meta.js b/website/pages/ja/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/ja/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/roles-and-benefits/_meta.js b/website/pages/ja/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/ja/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/network/benefits.mdx b/website/pages/ja/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/ja/network/benefits.mdx rename to website/pages/ja/roles-and-benefits/benefits.mdx diff --git a/website/pages/ja/network/curating.mdx b/website/pages/ja/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/ja/network/curating.mdx rename to website/pages/ja/roles-and-benefits/curating.mdx diff --git a/website/pages/ja/network/delegating.mdx b/website/pages/ja/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/ja/network/delegating.mdx rename to website/pages/ja/roles-and-benefits/delegating.mdx diff --git a/website/pages/ja/network/overview.mdx b/website/pages/ja/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/ja/network/overview.mdx rename to website/pages/ja/roles-and-benefits/overview.mdx diff --git a/website/pages/ja/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ja/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ja/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/ja/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ko/arbitrum/_meta.js b/website/pages/ko/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/ko/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/archived/_meta.js b/website/pages/ko/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/ko/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/archived/arbitrum/_meta.js b/website/pages/ko/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/ko/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/arbitrum/arbitrum-faq.mdx b/website/pages/ko/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/ko/arbitrum/arbitrum-faq.mdx rename to website/pages/ko/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/ko/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/ko/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/ko/sunrise.mdx b/website/pages/ko/archived/sunrise.mdx similarity index 100% rename from website/pages/ko/sunrise.mdx rename to website/pages/ko/archived/sunrise.mdx diff --git a/website/pages/ko/network/contracts.mdx b/website/pages/ko/contracts.mdx similarity index 100% rename from website/pages/ko/network/contracts.mdx rename to website/pages/ko/contracts.mdx diff --git a/website/pages/ko/deploying/_meta.js b/website/pages/ko/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/ko/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/developing/graph-ts/api.mdx b/website/pages/ko/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/ko/developing/graph-ts/api.mdx rename to website/pages/ko/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/ko/developing/graph-ts/common-issues.mdx b/website/pages/ko/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ko/developing/graph-ts/common-issues.mdx rename to website/pages/ko/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/ko/developing/unit-testing-framework.mdx b/website/pages/ko/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/ko/developing/unit-testing-framework.mdx rename to website/pages/ko/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/ko/developing/deploying/_meta.js b/website/pages/ko/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/ko/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ko/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/ko/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ko/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/ko/deploying/multiple-networks.mdx b/website/pages/ko/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ko/deploying/multiple-networks.mdx rename to website/pages/ko/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ko/deploying/subgraph-studio-faqs.mdx b/website/pages/ko/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ko/deploying/subgraph-studio-faqs.mdx rename to website/pages/ko/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ko/network/developing.mdx b/website/pages/ko/developing/developing.mdx similarity index 100% rename from website/pages/ko/network/developing.mdx rename to website/pages/ko/developing/developing.mdx diff --git a/website/pages/ko/developing/graph-ts/_meta.js b/website/pages/ko/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/ko/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/managing/_meta.js b/website/pages/ko/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/ko/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/managing/delete-a-subgraph.mdx b/website/pages/ko/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/ko/managing/delete-a-subgraph.mdx rename to website/pages/ko/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/ko/managing/transfer-a-subgraph.mdx b/website/pages/ko/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ko/managing/transfer-a-subgraph.mdx rename to website/pages/ko/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ko/developing/publishing/_meta.js b/website/pages/ko/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/ko/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/publishing/publishing-a-subgraph.mdx b/website/pages/ko/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ko/publishing/publishing-a-subgraph.mdx rename to website/pages/ko/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ko/subgraphs.mdx b/website/pages/ko/developing/subgraphs.mdx similarity index 100% rename from website/pages/ko/subgraphs.mdx rename to website/pages/ko/developing/subgraphs.mdx diff --git a/website/pages/ko/network/explorer.mdx b/website/pages/ko/explorer.mdx similarity index 100% rename from website/pages/ko/network/explorer.mdx rename to website/pages/ko/explorer.mdx diff --git a/website/pages/ko/indexer-tooling/_meta.js b/website/pages/ko/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/ko/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/firehose.mdx b/website/pages/ko/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/ko/firehose.mdx rename to website/pages/ko/indexer-tooling/firehose.mdx diff --git a/website/pages/ko/graphcast.mdx b/website/pages/ko/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/ko/graphcast.mdx rename to website/pages/ko/indexer-tooling/graphcast.mdx diff --git a/website/pages/ko/operating-graph-node.mdx b/website/pages/ko/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ko/operating-graph-node.mdx rename to website/pages/ko/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/ko/network/indexing.mdx b/website/pages/ko/indexing.mdx similarity index 100% rename from website/pages/ko/network/indexing.mdx rename to website/pages/ko/indexing.mdx diff --git a/website/pages/ko/managing/_meta.js b/website/pages/ko/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/ko/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/network/_meta.js b/website/pages/ko/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ko/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/publishing/_meta.js b/website/pages/ko/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/ko/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/roles-and-benefits/_meta.js b/website/pages/ko/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/ko/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/network/benefits.mdx b/website/pages/ko/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/ko/network/benefits.mdx rename to website/pages/ko/roles-and-benefits/benefits.mdx diff --git a/website/pages/ko/network/curating.mdx b/website/pages/ko/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/ko/network/curating.mdx rename to website/pages/ko/roles-and-benefits/curating.mdx diff --git a/website/pages/ko/network/delegating.mdx b/website/pages/ko/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/ko/network/delegating.mdx rename to website/pages/ko/roles-and-benefits/delegating.mdx diff --git a/website/pages/ko/network/overview.mdx b/website/pages/ko/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/ko/network/overview.mdx rename to website/pages/ko/roles-and-benefits/overview.mdx diff --git a/website/pages/ko/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ko/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ko/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/ko/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/mr/arbitrum/_meta.js b/website/pages/mr/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/mr/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/archived/_meta.js b/website/pages/mr/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/mr/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/archived/arbitrum/_meta.js b/website/pages/mr/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/mr/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/arbitrum/arbitrum-faq.mdx b/website/pages/mr/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/mr/arbitrum/arbitrum-faq.mdx rename to website/pages/mr/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/mr/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/mr/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/mr/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/mr/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/mr/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/mr/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/mr/sunrise.mdx b/website/pages/mr/archived/sunrise.mdx similarity index 100% rename from website/pages/mr/sunrise.mdx rename to website/pages/mr/archived/sunrise.mdx diff --git a/website/pages/mr/network/contracts.mdx b/website/pages/mr/contracts.mdx similarity index 100% rename from website/pages/mr/network/contracts.mdx rename to website/pages/mr/contracts.mdx diff --git a/website/pages/mr/deploying/_meta.js b/website/pages/mr/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/mr/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/developing/graph-ts/api.mdx b/website/pages/mr/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/mr/developing/graph-ts/api.mdx rename to website/pages/mr/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/mr/developing/graph-ts/common-issues.mdx b/website/pages/mr/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/mr/developing/graph-ts/common-issues.mdx rename to website/pages/mr/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/mr/developing/unit-testing-framework.mdx b/website/pages/mr/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/mr/developing/unit-testing-framework.mdx rename to website/pages/mr/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/mr/developing/deploying/_meta.js b/website/pages/mr/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/mr/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/deploying/deploy-using-subgraph-studio.mdx b/website/pages/mr/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/mr/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/mr/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/mr/deploying/multiple-networks.mdx b/website/pages/mr/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/mr/deploying/multiple-networks.mdx rename to website/pages/mr/developing/deploying/multiple-networks.mdx diff --git a/website/pages/mr/deploying/subgraph-studio-faqs.mdx b/website/pages/mr/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/mr/deploying/subgraph-studio-faqs.mdx rename to website/pages/mr/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/mr/network/developing.mdx b/website/pages/mr/developing/developing.mdx similarity index 100% rename from website/pages/mr/network/developing.mdx rename to website/pages/mr/developing/developing.mdx diff --git a/website/pages/mr/developing/graph-ts/_meta.js b/website/pages/mr/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/mr/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/managing/_meta.js b/website/pages/mr/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/mr/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/managing/delete-a-subgraph.mdx b/website/pages/mr/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/mr/managing/delete-a-subgraph.mdx rename to website/pages/mr/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/mr/managing/transfer-a-subgraph.mdx b/website/pages/mr/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/mr/managing/transfer-a-subgraph.mdx rename to website/pages/mr/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/mr/developing/publishing/_meta.js b/website/pages/mr/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/mr/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/publishing/publishing-a-subgraph.mdx b/website/pages/mr/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/mr/publishing/publishing-a-subgraph.mdx rename to website/pages/mr/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/mr/subgraphs.mdx b/website/pages/mr/developing/subgraphs.mdx similarity index 100% rename from website/pages/mr/subgraphs.mdx rename to website/pages/mr/developing/subgraphs.mdx diff --git a/website/pages/mr/network/explorer.mdx b/website/pages/mr/explorer.mdx similarity index 100% rename from website/pages/mr/network/explorer.mdx rename to website/pages/mr/explorer.mdx diff --git a/website/pages/mr/indexer-tooling/_meta.js b/website/pages/mr/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/mr/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/firehose.mdx b/website/pages/mr/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/mr/firehose.mdx rename to website/pages/mr/indexer-tooling/firehose.mdx diff --git a/website/pages/mr/graphcast.mdx b/website/pages/mr/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/mr/graphcast.mdx rename to website/pages/mr/indexer-tooling/graphcast.mdx diff --git a/website/pages/mr/operating-graph-node.mdx b/website/pages/mr/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/mr/operating-graph-node.mdx rename to website/pages/mr/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/mr/network/indexing.mdx b/website/pages/mr/indexing.mdx similarity index 100% rename from website/pages/mr/network/indexing.mdx rename to website/pages/mr/indexing.mdx diff --git a/website/pages/mr/managing/_meta.js b/website/pages/mr/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/mr/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/network/_meta.js b/website/pages/mr/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/mr/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/publishing/_meta.js b/website/pages/mr/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/mr/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/roles-and-benefits/_meta.js b/website/pages/mr/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/mr/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/network/benefits.mdx b/website/pages/mr/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/mr/network/benefits.mdx rename to website/pages/mr/roles-and-benefits/benefits.mdx diff --git a/website/pages/mr/network/curating.mdx b/website/pages/mr/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/mr/network/curating.mdx rename to website/pages/mr/roles-and-benefits/curating.mdx diff --git a/website/pages/mr/network/delegating.mdx b/website/pages/mr/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/mr/network/delegating.mdx rename to website/pages/mr/roles-and-benefits/delegating.mdx diff --git a/website/pages/mr/network/overview.mdx b/website/pages/mr/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/mr/network/overview.mdx rename to website/pages/mr/roles-and-benefits/overview.mdx diff --git a/website/pages/mr/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/mr/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/mr/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/mr/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/nl/arbitrum/_meta.js b/website/pages/nl/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/nl/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/archived/_meta.js b/website/pages/nl/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/nl/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/archived/arbitrum/_meta.js b/website/pages/nl/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/nl/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/arbitrum/arbitrum-faq.mdx b/website/pages/nl/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/nl/arbitrum/arbitrum-faq.mdx rename to website/pages/nl/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/nl/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/nl/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/nl/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/nl/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/nl/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/nl/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/nl/sunrise.mdx b/website/pages/nl/archived/sunrise.mdx similarity index 100% rename from website/pages/nl/sunrise.mdx rename to website/pages/nl/archived/sunrise.mdx diff --git a/website/pages/nl/network/contracts.mdx b/website/pages/nl/contracts.mdx similarity index 100% rename from website/pages/nl/network/contracts.mdx rename to website/pages/nl/contracts.mdx diff --git a/website/pages/nl/deploying/_meta.js b/website/pages/nl/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/nl/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/developing/graph-ts/api.mdx b/website/pages/nl/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/nl/developing/graph-ts/api.mdx rename to website/pages/nl/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/nl/developing/graph-ts/common-issues.mdx b/website/pages/nl/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/nl/developing/graph-ts/common-issues.mdx rename to website/pages/nl/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/nl/developing/unit-testing-framework.mdx b/website/pages/nl/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/nl/developing/unit-testing-framework.mdx rename to website/pages/nl/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/nl/developing/deploying/_meta.js b/website/pages/nl/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/nl/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/deploying/deploy-using-subgraph-studio.mdx b/website/pages/nl/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/nl/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/nl/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/nl/deploying/multiple-networks.mdx b/website/pages/nl/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/nl/deploying/multiple-networks.mdx rename to website/pages/nl/developing/deploying/multiple-networks.mdx diff --git a/website/pages/nl/deploying/subgraph-studio-faqs.mdx b/website/pages/nl/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/nl/deploying/subgraph-studio-faqs.mdx rename to website/pages/nl/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/nl/network/developing.mdx b/website/pages/nl/developing/developing.mdx similarity index 100% rename from website/pages/nl/network/developing.mdx rename to website/pages/nl/developing/developing.mdx diff --git a/website/pages/nl/developing/graph-ts/_meta.js b/website/pages/nl/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/nl/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/managing/_meta.js b/website/pages/nl/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/nl/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/managing/delete-a-subgraph.mdx b/website/pages/nl/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/nl/managing/delete-a-subgraph.mdx rename to website/pages/nl/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/nl/managing/transfer-a-subgraph.mdx b/website/pages/nl/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/nl/managing/transfer-a-subgraph.mdx rename to website/pages/nl/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/nl/developing/publishing/_meta.js b/website/pages/nl/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/nl/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/publishing/publishing-a-subgraph.mdx b/website/pages/nl/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/nl/publishing/publishing-a-subgraph.mdx rename to website/pages/nl/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/nl/subgraphs.mdx b/website/pages/nl/developing/subgraphs.mdx similarity index 100% rename from website/pages/nl/subgraphs.mdx rename to website/pages/nl/developing/subgraphs.mdx diff --git a/website/pages/nl/network/explorer.mdx b/website/pages/nl/explorer.mdx similarity index 100% rename from website/pages/nl/network/explorer.mdx rename to website/pages/nl/explorer.mdx diff --git a/website/pages/nl/indexer-tooling/_meta.js b/website/pages/nl/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/nl/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/firehose.mdx b/website/pages/nl/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/nl/firehose.mdx rename to website/pages/nl/indexer-tooling/firehose.mdx diff --git a/website/pages/nl/graphcast.mdx b/website/pages/nl/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/nl/graphcast.mdx rename to website/pages/nl/indexer-tooling/graphcast.mdx diff --git a/website/pages/nl/operating-graph-node.mdx b/website/pages/nl/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/nl/operating-graph-node.mdx rename to website/pages/nl/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/nl/network/indexing.mdx b/website/pages/nl/indexing.mdx similarity index 100% rename from website/pages/nl/network/indexing.mdx rename to website/pages/nl/indexing.mdx diff --git a/website/pages/nl/managing/_meta.js b/website/pages/nl/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/nl/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/network/_meta.js b/website/pages/nl/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/nl/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/publishing/_meta.js b/website/pages/nl/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/nl/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/roles-and-benefits/_meta.js b/website/pages/nl/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/nl/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/network/benefits.mdx b/website/pages/nl/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/nl/network/benefits.mdx rename to website/pages/nl/roles-and-benefits/benefits.mdx diff --git a/website/pages/nl/network/curating.mdx b/website/pages/nl/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/nl/network/curating.mdx rename to website/pages/nl/roles-and-benefits/curating.mdx diff --git a/website/pages/nl/network/delegating.mdx b/website/pages/nl/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/nl/network/delegating.mdx rename to website/pages/nl/roles-and-benefits/delegating.mdx diff --git a/website/pages/nl/network/overview.mdx b/website/pages/nl/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/nl/network/overview.mdx rename to website/pages/nl/roles-and-benefits/overview.mdx diff --git a/website/pages/nl/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/nl/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/nl/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/nl/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/pl/arbitrum/_meta.js b/website/pages/pl/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/pl/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/archived/_meta.js b/website/pages/pl/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/pl/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/archived/arbitrum/_meta.js b/website/pages/pl/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/pl/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/arbitrum/arbitrum-faq.mdx b/website/pages/pl/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/pl/arbitrum/arbitrum-faq.mdx rename to website/pages/pl/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/pl/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/pl/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/pl/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/pl/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/pl/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/pl/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/pl/sunrise.mdx b/website/pages/pl/archived/sunrise.mdx similarity index 100% rename from website/pages/pl/sunrise.mdx rename to website/pages/pl/archived/sunrise.mdx diff --git a/website/pages/pl/network/contracts.mdx b/website/pages/pl/contracts.mdx similarity index 100% rename from website/pages/pl/network/contracts.mdx rename to website/pages/pl/contracts.mdx diff --git a/website/pages/pl/deploying/_meta.js b/website/pages/pl/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/pl/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/developing/graph-ts/api.mdx b/website/pages/pl/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/pl/developing/graph-ts/api.mdx rename to website/pages/pl/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/pl/developing/graph-ts/common-issues.mdx b/website/pages/pl/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/pl/developing/graph-ts/common-issues.mdx rename to website/pages/pl/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/pl/developing/unit-testing-framework.mdx b/website/pages/pl/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/pl/developing/unit-testing-framework.mdx rename to website/pages/pl/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/pl/developing/deploying/_meta.js b/website/pages/pl/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/pl/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/deploying/deploy-using-subgraph-studio.mdx b/website/pages/pl/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/pl/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/pl/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/pl/deploying/multiple-networks.mdx b/website/pages/pl/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/pl/deploying/multiple-networks.mdx rename to website/pages/pl/developing/deploying/multiple-networks.mdx diff --git a/website/pages/pl/deploying/subgraph-studio-faqs.mdx b/website/pages/pl/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/pl/deploying/subgraph-studio-faqs.mdx rename to website/pages/pl/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/pl/network/developing.mdx b/website/pages/pl/developing/developing.mdx similarity index 100% rename from website/pages/pl/network/developing.mdx rename to website/pages/pl/developing/developing.mdx diff --git a/website/pages/pl/developing/graph-ts/_meta.js b/website/pages/pl/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/pl/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/managing/_meta.js b/website/pages/pl/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/pl/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/managing/delete-a-subgraph.mdx b/website/pages/pl/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/pl/managing/delete-a-subgraph.mdx rename to website/pages/pl/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/pl/managing/transfer-a-subgraph.mdx b/website/pages/pl/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/pl/managing/transfer-a-subgraph.mdx rename to website/pages/pl/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/pl/developing/publishing/_meta.js b/website/pages/pl/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/pl/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/publishing/publishing-a-subgraph.mdx b/website/pages/pl/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/pl/publishing/publishing-a-subgraph.mdx rename to website/pages/pl/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/pl/subgraphs.mdx b/website/pages/pl/developing/subgraphs.mdx similarity index 100% rename from website/pages/pl/subgraphs.mdx rename to website/pages/pl/developing/subgraphs.mdx diff --git a/website/pages/pl/network/explorer.mdx b/website/pages/pl/explorer.mdx similarity index 100% rename from website/pages/pl/network/explorer.mdx rename to website/pages/pl/explorer.mdx diff --git a/website/pages/pl/indexer-tooling/_meta.js b/website/pages/pl/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/pl/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/firehose.mdx b/website/pages/pl/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/pl/firehose.mdx rename to website/pages/pl/indexer-tooling/firehose.mdx diff --git a/website/pages/pl/graphcast.mdx b/website/pages/pl/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/pl/graphcast.mdx rename to website/pages/pl/indexer-tooling/graphcast.mdx diff --git a/website/pages/pl/operating-graph-node.mdx b/website/pages/pl/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/pl/operating-graph-node.mdx rename to website/pages/pl/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/pl/network/indexing.mdx b/website/pages/pl/indexing.mdx similarity index 100% rename from website/pages/pl/network/indexing.mdx rename to website/pages/pl/indexing.mdx diff --git a/website/pages/pl/managing/_meta.js b/website/pages/pl/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/pl/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/network/_meta.js b/website/pages/pl/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/pl/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/publishing/_meta.js b/website/pages/pl/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/pl/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/roles-and-benefits/_meta.js b/website/pages/pl/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/pl/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/network/benefits.mdx b/website/pages/pl/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/pl/network/benefits.mdx rename to website/pages/pl/roles-and-benefits/benefits.mdx diff --git a/website/pages/pl/network/curating.mdx b/website/pages/pl/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/pl/network/curating.mdx rename to website/pages/pl/roles-and-benefits/curating.mdx diff --git a/website/pages/pl/network/delegating.mdx b/website/pages/pl/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/pl/network/delegating.mdx rename to website/pages/pl/roles-and-benefits/delegating.mdx diff --git a/website/pages/pl/network/overview.mdx b/website/pages/pl/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/pl/network/overview.mdx rename to website/pages/pl/roles-and-benefits/overview.mdx diff --git a/website/pages/pl/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/pl/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/pl/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/pl/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/pt/arbitrum/_meta.js b/website/pages/pt/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/pt/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/archived/_meta.js b/website/pages/pt/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/pt/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/archived/arbitrum/_meta.js b/website/pages/pt/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/pt/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/arbitrum/arbitrum-faq.mdx b/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/pt/arbitrum/arbitrum-faq.mdx rename to website/pages/pt/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/pt/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/pt/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/pt/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/pt/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/pt/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/pt/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/pt/sunrise.mdx b/website/pages/pt/archived/sunrise.mdx similarity index 100% rename from website/pages/pt/sunrise.mdx rename to website/pages/pt/archived/sunrise.mdx diff --git a/website/pages/pt/network/contracts.mdx b/website/pages/pt/contracts.mdx similarity index 100% rename from website/pages/pt/network/contracts.mdx rename to website/pages/pt/contracts.mdx diff --git a/website/pages/pt/deploying/_meta.js b/website/pages/pt/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/pt/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/developing/graph-ts/api.mdx b/website/pages/pt/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/pt/developing/graph-ts/api.mdx rename to website/pages/pt/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/pt/developing/graph-ts/common-issues.mdx b/website/pages/pt/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/pt/developing/graph-ts/common-issues.mdx rename to website/pages/pt/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/pt/developing/unit-testing-framework.mdx b/website/pages/pt/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/pt/developing/unit-testing-framework.mdx rename to website/pages/pt/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/pt/developing/deploying/_meta.js b/website/pages/pt/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/pt/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/deploying/deploy-using-subgraph-studio.mdx b/website/pages/pt/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/pt/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/pt/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/pt/deploying/multiple-networks.mdx b/website/pages/pt/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/pt/deploying/multiple-networks.mdx rename to website/pages/pt/developing/deploying/multiple-networks.mdx diff --git a/website/pages/pt/deploying/subgraph-studio-faqs.mdx b/website/pages/pt/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/pt/deploying/subgraph-studio-faqs.mdx rename to website/pages/pt/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/pt/network/developing.mdx b/website/pages/pt/developing/developing.mdx similarity index 100% rename from website/pages/pt/network/developing.mdx rename to website/pages/pt/developing/developing.mdx diff --git a/website/pages/pt/developing/graph-ts/_meta.js b/website/pages/pt/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/pt/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/managing/_meta.js b/website/pages/pt/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/pt/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/managing/delete-a-subgraph.mdx b/website/pages/pt/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/pt/managing/delete-a-subgraph.mdx rename to website/pages/pt/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/pt/managing/transfer-a-subgraph.mdx b/website/pages/pt/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/pt/managing/transfer-a-subgraph.mdx rename to website/pages/pt/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/pt/developing/publishing/_meta.js b/website/pages/pt/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/pt/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/publishing/publishing-a-subgraph.mdx b/website/pages/pt/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/pt/publishing/publishing-a-subgraph.mdx rename to website/pages/pt/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/pt/subgraphs.mdx b/website/pages/pt/developing/subgraphs.mdx similarity index 100% rename from website/pages/pt/subgraphs.mdx rename to website/pages/pt/developing/subgraphs.mdx diff --git a/website/pages/pt/network/explorer.mdx b/website/pages/pt/explorer.mdx similarity index 100% rename from website/pages/pt/network/explorer.mdx rename to website/pages/pt/explorer.mdx diff --git a/website/pages/pt/indexer-tooling/_meta.js b/website/pages/pt/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/pt/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/firehose.mdx b/website/pages/pt/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/pt/firehose.mdx rename to website/pages/pt/indexer-tooling/firehose.mdx diff --git a/website/pages/pt/graphcast.mdx b/website/pages/pt/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/pt/graphcast.mdx rename to website/pages/pt/indexer-tooling/graphcast.mdx diff --git a/website/pages/pt/operating-graph-node.mdx b/website/pages/pt/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/pt/operating-graph-node.mdx rename to website/pages/pt/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/pt/network/indexing.mdx b/website/pages/pt/indexing.mdx similarity index 100% rename from website/pages/pt/network/indexing.mdx rename to website/pages/pt/indexing.mdx diff --git a/website/pages/pt/managing/_meta.js b/website/pages/pt/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/pt/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/network/_meta.js b/website/pages/pt/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/pt/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/publishing/_meta.js b/website/pages/pt/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/pt/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/roles-and-benefits/_meta.js b/website/pages/pt/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/pt/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/network/benefits.mdx b/website/pages/pt/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/pt/network/benefits.mdx rename to website/pages/pt/roles-and-benefits/benefits.mdx diff --git a/website/pages/pt/network/curating.mdx b/website/pages/pt/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/pt/network/curating.mdx rename to website/pages/pt/roles-and-benefits/curating.mdx diff --git a/website/pages/pt/network/delegating.mdx b/website/pages/pt/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/pt/network/delegating.mdx rename to website/pages/pt/roles-and-benefits/delegating.mdx diff --git a/website/pages/pt/network/overview.mdx b/website/pages/pt/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/pt/network/overview.mdx rename to website/pages/pt/roles-and-benefits/overview.mdx diff --git a/website/pages/pt/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/pt/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/pt/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/pt/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ro/arbitrum/_meta.js b/website/pages/ro/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/ro/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/archived/_meta.js b/website/pages/ro/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/ro/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/archived/arbitrum/_meta.js b/website/pages/ro/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/ro/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/arbitrum/arbitrum-faq.mdx b/website/pages/ro/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/ro/arbitrum/arbitrum-faq.mdx rename to website/pages/ro/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/ro/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/ro/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/ro/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/ro/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/ro/sunrise.mdx b/website/pages/ro/archived/sunrise.mdx similarity index 100% rename from website/pages/ro/sunrise.mdx rename to website/pages/ro/archived/sunrise.mdx diff --git a/website/pages/ro/network/contracts.mdx b/website/pages/ro/contracts.mdx similarity index 100% rename from website/pages/ro/network/contracts.mdx rename to website/pages/ro/contracts.mdx diff --git a/website/pages/ro/deploying/_meta.js b/website/pages/ro/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/ro/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/developing/graph-ts/api.mdx b/website/pages/ro/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/ro/developing/graph-ts/api.mdx rename to website/pages/ro/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/ro/developing/graph-ts/common-issues.mdx b/website/pages/ro/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ro/developing/graph-ts/common-issues.mdx rename to website/pages/ro/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/ro/developing/unit-testing-framework.mdx b/website/pages/ro/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/ro/developing/unit-testing-framework.mdx rename to website/pages/ro/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/ro/developing/deploying/_meta.js b/website/pages/ro/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/ro/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ro/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/ro/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ro/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/ro/deploying/multiple-networks.mdx b/website/pages/ro/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ro/deploying/multiple-networks.mdx rename to website/pages/ro/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ro/deploying/subgraph-studio-faqs.mdx b/website/pages/ro/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ro/deploying/subgraph-studio-faqs.mdx rename to website/pages/ro/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ro/network/developing.mdx b/website/pages/ro/developing/developing.mdx similarity index 100% rename from website/pages/ro/network/developing.mdx rename to website/pages/ro/developing/developing.mdx diff --git a/website/pages/ro/developing/graph-ts/_meta.js b/website/pages/ro/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/ro/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/managing/_meta.js b/website/pages/ro/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/ro/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/managing/delete-a-subgraph.mdx b/website/pages/ro/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/ro/managing/delete-a-subgraph.mdx rename to website/pages/ro/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/ro/managing/transfer-a-subgraph.mdx b/website/pages/ro/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ro/managing/transfer-a-subgraph.mdx rename to website/pages/ro/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ro/developing/publishing/_meta.js b/website/pages/ro/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/ro/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/publishing/publishing-a-subgraph.mdx b/website/pages/ro/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ro/publishing/publishing-a-subgraph.mdx rename to website/pages/ro/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ro/subgraphs.mdx b/website/pages/ro/developing/subgraphs.mdx similarity index 100% rename from website/pages/ro/subgraphs.mdx rename to website/pages/ro/developing/subgraphs.mdx diff --git a/website/pages/ro/network/explorer.mdx b/website/pages/ro/explorer.mdx similarity index 100% rename from website/pages/ro/network/explorer.mdx rename to website/pages/ro/explorer.mdx diff --git a/website/pages/ro/indexer-tooling/_meta.js b/website/pages/ro/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/ro/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/firehose.mdx b/website/pages/ro/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/ro/firehose.mdx rename to website/pages/ro/indexer-tooling/firehose.mdx diff --git a/website/pages/ro/graphcast.mdx b/website/pages/ro/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/ro/graphcast.mdx rename to website/pages/ro/indexer-tooling/graphcast.mdx diff --git a/website/pages/ro/operating-graph-node.mdx b/website/pages/ro/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ro/operating-graph-node.mdx rename to website/pages/ro/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/ro/network/indexing.mdx b/website/pages/ro/indexing.mdx similarity index 100% rename from website/pages/ro/network/indexing.mdx rename to website/pages/ro/indexing.mdx diff --git a/website/pages/ro/managing/_meta.js b/website/pages/ro/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/ro/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/network/_meta.js b/website/pages/ro/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ro/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/publishing/_meta.js b/website/pages/ro/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/ro/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/roles-and-benefits/_meta.js b/website/pages/ro/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/ro/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/network/benefits.mdx b/website/pages/ro/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/ro/network/benefits.mdx rename to website/pages/ro/roles-and-benefits/benefits.mdx diff --git a/website/pages/ro/network/curating.mdx b/website/pages/ro/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/ro/network/curating.mdx rename to website/pages/ro/roles-and-benefits/curating.mdx diff --git a/website/pages/ro/network/delegating.mdx b/website/pages/ro/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/ro/network/delegating.mdx rename to website/pages/ro/roles-and-benefits/delegating.mdx diff --git a/website/pages/ro/network/overview.mdx b/website/pages/ro/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/ro/network/overview.mdx rename to website/pages/ro/roles-and-benefits/overview.mdx diff --git a/website/pages/ro/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ro/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ro/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/ro/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ru/arbitrum/_meta.js b/website/pages/ru/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/ru/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/archived/_meta.js b/website/pages/ru/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/ru/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/archived/arbitrum/_meta.js b/website/pages/ru/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/ru/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/arbitrum/arbitrum-faq.mdx b/website/pages/ru/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/ru/arbitrum/arbitrum-faq.mdx rename to website/pages/ru/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/ru/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ru/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/ru/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/ru/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/ru/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/ru/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/ru/sunrise.mdx b/website/pages/ru/archived/sunrise.mdx similarity index 100% rename from website/pages/ru/sunrise.mdx rename to website/pages/ru/archived/sunrise.mdx diff --git a/website/pages/ru/network/contracts.mdx b/website/pages/ru/contracts.mdx similarity index 100% rename from website/pages/ru/network/contracts.mdx rename to website/pages/ru/contracts.mdx diff --git a/website/pages/ru/deploying/_meta.js b/website/pages/ru/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/ru/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/developing/graph-ts/api.mdx b/website/pages/ru/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/ru/developing/graph-ts/api.mdx rename to website/pages/ru/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/ru/developing/graph-ts/common-issues.mdx b/website/pages/ru/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ru/developing/graph-ts/common-issues.mdx rename to website/pages/ru/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/ru/developing/unit-testing-framework.mdx b/website/pages/ru/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/ru/developing/unit-testing-framework.mdx rename to website/pages/ru/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/ru/developing/deploying/_meta.js b/website/pages/ru/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/ru/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ru/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/ru/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ru/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/ru/deploying/multiple-networks.mdx b/website/pages/ru/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ru/deploying/multiple-networks.mdx rename to website/pages/ru/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ru/deploying/subgraph-studio-faqs.mdx b/website/pages/ru/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ru/deploying/subgraph-studio-faqs.mdx rename to website/pages/ru/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ru/network/developing.mdx b/website/pages/ru/developing/developing.mdx similarity index 100% rename from website/pages/ru/network/developing.mdx rename to website/pages/ru/developing/developing.mdx diff --git a/website/pages/ru/developing/graph-ts/_meta.js b/website/pages/ru/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/ru/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/managing/_meta.js b/website/pages/ru/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/ru/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/managing/delete-a-subgraph.mdx b/website/pages/ru/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/ru/managing/delete-a-subgraph.mdx rename to website/pages/ru/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/ru/managing/transfer-a-subgraph.mdx b/website/pages/ru/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ru/managing/transfer-a-subgraph.mdx rename to website/pages/ru/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ru/developing/publishing/_meta.js b/website/pages/ru/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/ru/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/publishing/publishing-a-subgraph.mdx b/website/pages/ru/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ru/publishing/publishing-a-subgraph.mdx rename to website/pages/ru/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ru/subgraphs.mdx b/website/pages/ru/developing/subgraphs.mdx similarity index 100% rename from website/pages/ru/subgraphs.mdx rename to website/pages/ru/developing/subgraphs.mdx diff --git a/website/pages/ru/network/explorer.mdx b/website/pages/ru/explorer.mdx similarity index 100% rename from website/pages/ru/network/explorer.mdx rename to website/pages/ru/explorer.mdx diff --git a/website/pages/ru/indexer-tooling/_meta.js b/website/pages/ru/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/ru/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/firehose.mdx b/website/pages/ru/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/ru/firehose.mdx rename to website/pages/ru/indexer-tooling/firehose.mdx diff --git a/website/pages/ru/graphcast.mdx b/website/pages/ru/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/ru/graphcast.mdx rename to website/pages/ru/indexer-tooling/graphcast.mdx diff --git a/website/pages/ru/operating-graph-node.mdx b/website/pages/ru/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ru/operating-graph-node.mdx rename to website/pages/ru/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/ru/network/indexing.mdx b/website/pages/ru/indexing.mdx similarity index 100% rename from website/pages/ru/network/indexing.mdx rename to website/pages/ru/indexing.mdx diff --git a/website/pages/ru/managing/_meta.js b/website/pages/ru/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/ru/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/network/_meta.js b/website/pages/ru/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ru/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/publishing/_meta.js b/website/pages/ru/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/ru/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/roles-and-benefits/_meta.js b/website/pages/ru/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/ru/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/network/benefits.mdx b/website/pages/ru/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/ru/network/benefits.mdx rename to website/pages/ru/roles-and-benefits/benefits.mdx diff --git a/website/pages/ru/network/curating.mdx b/website/pages/ru/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/ru/network/curating.mdx rename to website/pages/ru/roles-and-benefits/curating.mdx diff --git a/website/pages/ru/network/delegating.mdx b/website/pages/ru/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/ru/network/delegating.mdx rename to website/pages/ru/roles-and-benefits/delegating.mdx diff --git a/website/pages/ru/network/overview.mdx b/website/pages/ru/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/ru/network/overview.mdx rename to website/pages/ru/roles-and-benefits/overview.mdx diff --git a/website/pages/ru/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ru/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ru/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/ru/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/sv/arbitrum/_meta.js b/website/pages/sv/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/sv/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/archived/_meta.js b/website/pages/sv/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/sv/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/archived/arbitrum/_meta.js b/website/pages/sv/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/sv/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/arbitrum/arbitrum-faq.mdx b/website/pages/sv/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/sv/arbitrum/arbitrum-faq.mdx rename to website/pages/sv/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/sv/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/sv/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/sv/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/sv/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/sv/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/sv/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/sv/sunrise.mdx b/website/pages/sv/archived/sunrise.mdx similarity index 100% rename from website/pages/sv/sunrise.mdx rename to website/pages/sv/archived/sunrise.mdx diff --git a/website/pages/sv/network/contracts.mdx b/website/pages/sv/contracts.mdx similarity index 100% rename from website/pages/sv/network/contracts.mdx rename to website/pages/sv/contracts.mdx diff --git a/website/pages/sv/deploying/_meta.js b/website/pages/sv/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/sv/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/developing/graph-ts/api.mdx b/website/pages/sv/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/sv/developing/graph-ts/api.mdx rename to website/pages/sv/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/sv/developing/graph-ts/common-issues.mdx b/website/pages/sv/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/sv/developing/graph-ts/common-issues.mdx rename to website/pages/sv/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/sv/developing/unit-testing-framework.mdx b/website/pages/sv/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/sv/developing/unit-testing-framework.mdx rename to website/pages/sv/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/sv/developing/deploying/_meta.js b/website/pages/sv/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/sv/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/deploying/deploy-using-subgraph-studio.mdx b/website/pages/sv/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/sv/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/sv/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/sv/deploying/multiple-networks.mdx b/website/pages/sv/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/sv/deploying/multiple-networks.mdx rename to website/pages/sv/developing/deploying/multiple-networks.mdx diff --git a/website/pages/sv/deploying/subgraph-studio-faqs.mdx b/website/pages/sv/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/sv/deploying/subgraph-studio-faqs.mdx rename to website/pages/sv/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/sv/network/developing.mdx b/website/pages/sv/developing/developing.mdx similarity index 100% rename from website/pages/sv/network/developing.mdx rename to website/pages/sv/developing/developing.mdx diff --git a/website/pages/sv/developing/graph-ts/_meta.js b/website/pages/sv/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/sv/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/managing/_meta.js b/website/pages/sv/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/sv/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/managing/delete-a-subgraph.mdx b/website/pages/sv/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/sv/managing/delete-a-subgraph.mdx rename to website/pages/sv/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/sv/managing/transfer-a-subgraph.mdx b/website/pages/sv/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/sv/managing/transfer-a-subgraph.mdx rename to website/pages/sv/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/sv/developing/publishing/_meta.js b/website/pages/sv/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/sv/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/publishing/publishing-a-subgraph.mdx b/website/pages/sv/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/sv/publishing/publishing-a-subgraph.mdx rename to website/pages/sv/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/sv/subgraphs.mdx b/website/pages/sv/developing/subgraphs.mdx similarity index 100% rename from website/pages/sv/subgraphs.mdx rename to website/pages/sv/developing/subgraphs.mdx diff --git a/website/pages/sv/network/explorer.mdx b/website/pages/sv/explorer.mdx similarity index 100% rename from website/pages/sv/network/explorer.mdx rename to website/pages/sv/explorer.mdx diff --git a/website/pages/sv/indexer-tooling/_meta.js b/website/pages/sv/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/sv/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/firehose.mdx b/website/pages/sv/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/sv/firehose.mdx rename to website/pages/sv/indexer-tooling/firehose.mdx diff --git a/website/pages/sv/graphcast.mdx b/website/pages/sv/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/sv/graphcast.mdx rename to website/pages/sv/indexer-tooling/graphcast.mdx diff --git a/website/pages/sv/operating-graph-node.mdx b/website/pages/sv/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/sv/operating-graph-node.mdx rename to website/pages/sv/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/sv/network/indexing.mdx b/website/pages/sv/indexing.mdx similarity index 100% rename from website/pages/sv/network/indexing.mdx rename to website/pages/sv/indexing.mdx diff --git a/website/pages/sv/managing/_meta.js b/website/pages/sv/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/sv/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/network/_meta.js b/website/pages/sv/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/sv/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/publishing/_meta.js b/website/pages/sv/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/sv/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/roles-and-benefits/_meta.js b/website/pages/sv/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/sv/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/network/benefits.mdx b/website/pages/sv/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/sv/network/benefits.mdx rename to website/pages/sv/roles-and-benefits/benefits.mdx diff --git a/website/pages/sv/network/curating.mdx b/website/pages/sv/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/sv/network/curating.mdx rename to website/pages/sv/roles-and-benefits/curating.mdx diff --git a/website/pages/sv/network/delegating.mdx b/website/pages/sv/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/sv/network/delegating.mdx rename to website/pages/sv/roles-and-benefits/delegating.mdx diff --git a/website/pages/sv/network/overview.mdx b/website/pages/sv/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/sv/network/overview.mdx rename to website/pages/sv/roles-and-benefits/overview.mdx diff --git a/website/pages/sv/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/sv/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/sv/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/sv/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/sw/arbitrum/_meta.js b/website/pages/sw/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/sw/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/archived/_meta.js b/website/pages/sw/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/sw/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/archived/arbitrum/_meta.js b/website/pages/sw/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/sw/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/arbitrum/arbitrum-faq.mdx b/website/pages/sw/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/sw/arbitrum/arbitrum-faq.mdx rename to website/pages/sw/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/sw/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/sw/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/sw/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/sw/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/sw/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/sw/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/sw/sunrise.mdx b/website/pages/sw/archived/sunrise.mdx similarity index 100% rename from website/pages/sw/sunrise.mdx rename to website/pages/sw/archived/sunrise.mdx diff --git a/website/pages/sw/network/contracts.mdx b/website/pages/sw/contracts.mdx similarity index 100% rename from website/pages/sw/network/contracts.mdx rename to website/pages/sw/contracts.mdx diff --git a/website/pages/sw/deploying/_meta.js b/website/pages/sw/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/sw/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/developing/graph-ts/api.mdx b/website/pages/sw/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/sw/developing/graph-ts/api.mdx rename to website/pages/sw/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/sw/developing/graph-ts/common-issues.mdx b/website/pages/sw/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/sw/developing/graph-ts/common-issues.mdx rename to website/pages/sw/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/sw/developing/unit-testing-framework.mdx b/website/pages/sw/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/sw/developing/unit-testing-framework.mdx rename to website/pages/sw/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/sw/developing/deploying/_meta.js b/website/pages/sw/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/sw/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/deploying/deploy-using-subgraph-studio.mdx b/website/pages/sw/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/sw/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/sw/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/sw/deploying/multiple-networks.mdx b/website/pages/sw/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/sw/deploying/multiple-networks.mdx rename to website/pages/sw/developing/deploying/multiple-networks.mdx diff --git a/website/pages/sw/deploying/subgraph-studio-faqs.mdx b/website/pages/sw/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/sw/deploying/subgraph-studio-faqs.mdx rename to website/pages/sw/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/sw/network/developing.mdx b/website/pages/sw/developing/developing.mdx similarity index 100% rename from website/pages/sw/network/developing.mdx rename to website/pages/sw/developing/developing.mdx diff --git a/website/pages/sw/developing/graph-ts/_meta.js b/website/pages/sw/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/sw/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/managing/_meta.js b/website/pages/sw/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/sw/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/managing/delete-a-subgraph.mdx b/website/pages/sw/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/sw/managing/delete-a-subgraph.mdx rename to website/pages/sw/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/sw/managing/transfer-a-subgraph.mdx b/website/pages/sw/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/sw/managing/transfer-a-subgraph.mdx rename to website/pages/sw/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/sw/developing/publishing/_meta.js b/website/pages/sw/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/sw/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/publishing/publishing-a-subgraph.mdx b/website/pages/sw/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/sw/publishing/publishing-a-subgraph.mdx rename to website/pages/sw/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/sw/subgraphs.mdx b/website/pages/sw/developing/subgraphs.mdx similarity index 100% rename from website/pages/sw/subgraphs.mdx rename to website/pages/sw/developing/subgraphs.mdx diff --git a/website/pages/sw/network/explorer.mdx b/website/pages/sw/explorer.mdx similarity index 100% rename from website/pages/sw/network/explorer.mdx rename to website/pages/sw/explorer.mdx diff --git a/website/pages/sw/indexer-tooling/_meta.js b/website/pages/sw/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/sw/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/firehose.mdx b/website/pages/sw/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/sw/firehose.mdx rename to website/pages/sw/indexer-tooling/firehose.mdx diff --git a/website/pages/sw/graphcast.mdx b/website/pages/sw/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/sw/graphcast.mdx rename to website/pages/sw/indexer-tooling/graphcast.mdx diff --git a/website/pages/sw/operating-graph-node.mdx b/website/pages/sw/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/sw/operating-graph-node.mdx rename to website/pages/sw/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/sw/network/indexing.mdx b/website/pages/sw/indexing.mdx similarity index 100% rename from website/pages/sw/network/indexing.mdx rename to website/pages/sw/indexing.mdx diff --git a/website/pages/sw/managing/_meta.js b/website/pages/sw/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/sw/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/network/_meta.js b/website/pages/sw/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/sw/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/publishing/_meta.js b/website/pages/sw/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/sw/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/roles-and-benefits/_meta.js b/website/pages/sw/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/sw/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/network/benefits.mdx b/website/pages/sw/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/sw/network/benefits.mdx rename to website/pages/sw/roles-and-benefits/benefits.mdx diff --git a/website/pages/sw/network/curating.mdx b/website/pages/sw/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/sw/network/curating.mdx rename to website/pages/sw/roles-and-benefits/curating.mdx diff --git a/website/pages/sw/network/delegating.mdx b/website/pages/sw/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/sw/network/delegating.mdx rename to website/pages/sw/roles-and-benefits/delegating.mdx diff --git a/website/pages/sw/network/overview.mdx b/website/pages/sw/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/sw/network/overview.mdx rename to website/pages/sw/roles-and-benefits/overview.mdx diff --git a/website/pages/sw/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/sw/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/sw/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/sw/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/tr/arbitrum/_meta.js b/website/pages/tr/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/tr/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/archived/_meta.js b/website/pages/tr/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/tr/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/archived/arbitrum/_meta.js b/website/pages/tr/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/tr/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/arbitrum/arbitrum-faq.mdx b/website/pages/tr/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/tr/arbitrum/arbitrum-faq.mdx rename to website/pages/tr/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/tr/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/tr/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/tr/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/tr/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/tr/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/tr/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/tr/sunrise.mdx b/website/pages/tr/archived/sunrise.mdx similarity index 100% rename from website/pages/tr/sunrise.mdx rename to website/pages/tr/archived/sunrise.mdx diff --git a/website/pages/tr/network/contracts.mdx b/website/pages/tr/contracts.mdx similarity index 100% rename from website/pages/tr/network/contracts.mdx rename to website/pages/tr/contracts.mdx diff --git a/website/pages/tr/deploying/_meta.js b/website/pages/tr/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/tr/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/developing/graph-ts/api.mdx b/website/pages/tr/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/tr/developing/graph-ts/api.mdx rename to website/pages/tr/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/tr/developing/graph-ts/common-issues.mdx b/website/pages/tr/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/tr/developing/graph-ts/common-issues.mdx rename to website/pages/tr/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/tr/developing/unit-testing-framework.mdx b/website/pages/tr/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/tr/developing/unit-testing-framework.mdx rename to website/pages/tr/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/tr/developing/deploying/_meta.js b/website/pages/tr/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/tr/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/deploying/deploy-using-subgraph-studio.mdx b/website/pages/tr/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/tr/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/tr/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/tr/deploying/multiple-networks.mdx b/website/pages/tr/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/tr/deploying/multiple-networks.mdx rename to website/pages/tr/developing/deploying/multiple-networks.mdx diff --git a/website/pages/tr/deploying/subgraph-studio-faqs.mdx b/website/pages/tr/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/tr/deploying/subgraph-studio-faqs.mdx rename to website/pages/tr/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/tr/network/developing.mdx b/website/pages/tr/developing/developing.mdx similarity index 100% rename from website/pages/tr/network/developing.mdx rename to website/pages/tr/developing/developing.mdx diff --git a/website/pages/tr/developing/graph-ts/_meta.js b/website/pages/tr/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/tr/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/managing/_meta.js b/website/pages/tr/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/tr/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/managing/delete-a-subgraph.mdx b/website/pages/tr/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/tr/managing/delete-a-subgraph.mdx rename to website/pages/tr/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/tr/managing/transfer-a-subgraph.mdx b/website/pages/tr/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/tr/managing/transfer-a-subgraph.mdx rename to website/pages/tr/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/tr/developing/publishing/_meta.js b/website/pages/tr/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/tr/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/publishing/publishing-a-subgraph.mdx b/website/pages/tr/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/tr/publishing/publishing-a-subgraph.mdx rename to website/pages/tr/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/tr/subgraphs.mdx b/website/pages/tr/developing/subgraphs.mdx similarity index 100% rename from website/pages/tr/subgraphs.mdx rename to website/pages/tr/developing/subgraphs.mdx diff --git a/website/pages/tr/network/explorer.mdx b/website/pages/tr/explorer.mdx similarity index 100% rename from website/pages/tr/network/explorer.mdx rename to website/pages/tr/explorer.mdx diff --git a/website/pages/tr/indexer-tooling/_meta.js b/website/pages/tr/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/tr/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/firehose.mdx b/website/pages/tr/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/tr/firehose.mdx rename to website/pages/tr/indexer-tooling/firehose.mdx diff --git a/website/pages/tr/graphcast.mdx b/website/pages/tr/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/tr/graphcast.mdx rename to website/pages/tr/indexer-tooling/graphcast.mdx diff --git a/website/pages/tr/operating-graph-node.mdx b/website/pages/tr/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/tr/operating-graph-node.mdx rename to website/pages/tr/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/tr/network/indexing.mdx b/website/pages/tr/indexing.mdx similarity index 100% rename from website/pages/tr/network/indexing.mdx rename to website/pages/tr/indexing.mdx diff --git a/website/pages/tr/managing/_meta.js b/website/pages/tr/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/tr/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/network/_meta.js b/website/pages/tr/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/tr/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/publishing/_meta.js b/website/pages/tr/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/tr/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/roles-and-benefits/_meta.js b/website/pages/tr/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/tr/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/network/benefits.mdx b/website/pages/tr/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/tr/network/benefits.mdx rename to website/pages/tr/roles-and-benefits/benefits.mdx diff --git a/website/pages/tr/network/curating.mdx b/website/pages/tr/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/tr/network/curating.mdx rename to website/pages/tr/roles-and-benefits/curating.mdx diff --git a/website/pages/tr/network/delegating.mdx b/website/pages/tr/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/tr/network/delegating.mdx rename to website/pages/tr/roles-and-benefits/delegating.mdx diff --git a/website/pages/tr/network/overview.mdx b/website/pages/tr/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/tr/network/overview.mdx rename to website/pages/tr/roles-and-benefits/overview.mdx diff --git a/website/pages/tr/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/tr/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/tr/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/tr/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/uk/arbitrum/_meta.js b/website/pages/uk/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/uk/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/archived/_meta.js b/website/pages/uk/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/uk/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/archived/arbitrum/_meta.js b/website/pages/uk/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/uk/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/arbitrum/arbitrum-faq.mdx b/website/pages/uk/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/uk/arbitrum/arbitrum-faq.mdx rename to website/pages/uk/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/uk/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/uk/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/uk/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/uk/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/uk/sunrise.mdx b/website/pages/uk/archived/sunrise.mdx similarity index 100% rename from website/pages/uk/sunrise.mdx rename to website/pages/uk/archived/sunrise.mdx diff --git a/website/pages/uk/network/contracts.mdx b/website/pages/uk/contracts.mdx similarity index 100% rename from website/pages/uk/network/contracts.mdx rename to website/pages/uk/contracts.mdx diff --git a/website/pages/uk/deploying/_meta.js b/website/pages/uk/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/uk/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/developing/graph-ts/api.mdx b/website/pages/uk/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/uk/developing/graph-ts/api.mdx rename to website/pages/uk/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/uk/developing/graph-ts/common-issues.mdx b/website/pages/uk/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/uk/developing/graph-ts/common-issues.mdx rename to website/pages/uk/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/uk/developing/unit-testing-framework.mdx b/website/pages/uk/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/uk/developing/unit-testing-framework.mdx rename to website/pages/uk/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/uk/developing/deploying/_meta.js b/website/pages/uk/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/uk/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/deploying/deploy-using-subgraph-studio.mdx b/website/pages/uk/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/uk/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/uk/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/uk/deploying/multiple-networks.mdx b/website/pages/uk/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/uk/deploying/multiple-networks.mdx rename to website/pages/uk/developing/deploying/multiple-networks.mdx diff --git a/website/pages/uk/deploying/subgraph-studio-faqs.mdx b/website/pages/uk/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/uk/deploying/subgraph-studio-faqs.mdx rename to website/pages/uk/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/uk/network/developing.mdx b/website/pages/uk/developing/developing.mdx similarity index 100% rename from website/pages/uk/network/developing.mdx rename to website/pages/uk/developing/developing.mdx diff --git a/website/pages/uk/developing/graph-ts/_meta.js b/website/pages/uk/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/uk/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/managing/_meta.js b/website/pages/uk/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/uk/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/managing/delete-a-subgraph.mdx b/website/pages/uk/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/uk/managing/delete-a-subgraph.mdx rename to website/pages/uk/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/uk/managing/transfer-a-subgraph.mdx b/website/pages/uk/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/uk/managing/transfer-a-subgraph.mdx rename to website/pages/uk/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/uk/developing/publishing/_meta.js b/website/pages/uk/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/uk/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/publishing/publishing-a-subgraph.mdx b/website/pages/uk/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/uk/publishing/publishing-a-subgraph.mdx rename to website/pages/uk/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/uk/subgraphs.mdx b/website/pages/uk/developing/subgraphs.mdx similarity index 100% rename from website/pages/uk/subgraphs.mdx rename to website/pages/uk/developing/subgraphs.mdx diff --git a/website/pages/uk/network/explorer.mdx b/website/pages/uk/explorer.mdx similarity index 100% rename from website/pages/uk/network/explorer.mdx rename to website/pages/uk/explorer.mdx diff --git a/website/pages/uk/indexer-tooling/_meta.js b/website/pages/uk/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/uk/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/firehose.mdx b/website/pages/uk/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/uk/firehose.mdx rename to website/pages/uk/indexer-tooling/firehose.mdx diff --git a/website/pages/uk/graphcast.mdx b/website/pages/uk/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/uk/graphcast.mdx rename to website/pages/uk/indexer-tooling/graphcast.mdx diff --git a/website/pages/uk/operating-graph-node.mdx b/website/pages/uk/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/uk/operating-graph-node.mdx rename to website/pages/uk/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/uk/network/indexing.mdx b/website/pages/uk/indexing.mdx similarity index 100% rename from website/pages/uk/network/indexing.mdx rename to website/pages/uk/indexing.mdx diff --git a/website/pages/uk/managing/_meta.js b/website/pages/uk/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/uk/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/network/_meta.js b/website/pages/uk/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/uk/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/publishing/_meta.js b/website/pages/uk/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/uk/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/roles-and-benefits/_meta.js b/website/pages/uk/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/uk/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/network/benefits.mdx b/website/pages/uk/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/uk/network/benefits.mdx rename to website/pages/uk/roles-and-benefits/benefits.mdx diff --git a/website/pages/uk/network/curating.mdx b/website/pages/uk/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/uk/network/curating.mdx rename to website/pages/uk/roles-and-benefits/curating.mdx diff --git a/website/pages/uk/network/delegating.mdx b/website/pages/uk/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/uk/network/delegating.mdx rename to website/pages/uk/roles-and-benefits/delegating.mdx diff --git a/website/pages/uk/network/overview.mdx b/website/pages/uk/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/uk/network/overview.mdx rename to website/pages/uk/roles-and-benefits/overview.mdx diff --git a/website/pages/uk/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/uk/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/uk/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/uk/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ur/arbitrum/_meta.js b/website/pages/ur/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/ur/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/archived/_meta.js b/website/pages/ur/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/ur/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/archived/arbitrum/_meta.js b/website/pages/ur/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/ur/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/arbitrum/arbitrum-faq.mdx b/website/pages/ur/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/ur/arbitrum/arbitrum-faq.mdx rename to website/pages/ur/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/ur/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ur/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/ur/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/ur/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/ur/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/ur/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/ur/sunrise.mdx b/website/pages/ur/archived/sunrise.mdx similarity index 100% rename from website/pages/ur/sunrise.mdx rename to website/pages/ur/archived/sunrise.mdx diff --git a/website/pages/ur/network/contracts.mdx b/website/pages/ur/contracts.mdx similarity index 100% rename from website/pages/ur/network/contracts.mdx rename to website/pages/ur/contracts.mdx diff --git a/website/pages/ur/deploying/_meta.js b/website/pages/ur/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/ur/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/developing/graph-ts/api.mdx b/website/pages/ur/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/ur/developing/graph-ts/api.mdx rename to website/pages/ur/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/ur/developing/graph-ts/common-issues.mdx b/website/pages/ur/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ur/developing/graph-ts/common-issues.mdx rename to website/pages/ur/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/ur/developing/unit-testing-framework.mdx b/website/pages/ur/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/ur/developing/unit-testing-framework.mdx rename to website/pages/ur/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/ur/developing/deploying/_meta.js b/website/pages/ur/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/ur/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ur/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/ur/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ur/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/ur/deploying/multiple-networks.mdx b/website/pages/ur/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ur/deploying/multiple-networks.mdx rename to website/pages/ur/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ur/deploying/subgraph-studio-faqs.mdx b/website/pages/ur/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ur/deploying/subgraph-studio-faqs.mdx rename to website/pages/ur/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ur/network/developing.mdx b/website/pages/ur/developing/developing.mdx similarity index 100% rename from website/pages/ur/network/developing.mdx rename to website/pages/ur/developing/developing.mdx diff --git a/website/pages/ur/developing/graph-ts/_meta.js b/website/pages/ur/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/ur/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/managing/_meta.js b/website/pages/ur/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/ur/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/managing/delete-a-subgraph.mdx b/website/pages/ur/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/ur/managing/delete-a-subgraph.mdx rename to website/pages/ur/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/ur/managing/transfer-a-subgraph.mdx b/website/pages/ur/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/ur/managing/transfer-a-subgraph.mdx rename to website/pages/ur/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/ur/developing/publishing/_meta.js b/website/pages/ur/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/ur/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/publishing/publishing-a-subgraph.mdx b/website/pages/ur/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ur/publishing/publishing-a-subgraph.mdx rename to website/pages/ur/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ur/subgraphs.mdx b/website/pages/ur/developing/subgraphs.mdx similarity index 100% rename from website/pages/ur/subgraphs.mdx rename to website/pages/ur/developing/subgraphs.mdx diff --git a/website/pages/ur/network/explorer.mdx b/website/pages/ur/explorer.mdx similarity index 100% rename from website/pages/ur/network/explorer.mdx rename to website/pages/ur/explorer.mdx diff --git a/website/pages/ur/indexer-tooling/_meta.js b/website/pages/ur/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/ur/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/firehose.mdx b/website/pages/ur/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/ur/firehose.mdx rename to website/pages/ur/indexer-tooling/firehose.mdx diff --git a/website/pages/ur/graphcast.mdx b/website/pages/ur/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/ur/graphcast.mdx rename to website/pages/ur/indexer-tooling/graphcast.mdx diff --git a/website/pages/ur/operating-graph-node.mdx b/website/pages/ur/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ur/operating-graph-node.mdx rename to website/pages/ur/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/ur/network/indexing.mdx b/website/pages/ur/indexing.mdx similarity index 100% rename from website/pages/ur/network/indexing.mdx rename to website/pages/ur/indexing.mdx diff --git a/website/pages/ur/managing/_meta.js b/website/pages/ur/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/ur/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/network/_meta.js b/website/pages/ur/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ur/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/publishing/_meta.js b/website/pages/ur/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/ur/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/roles-and-benefits/_meta.js b/website/pages/ur/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/ur/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/network/benefits.mdx b/website/pages/ur/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/ur/network/benefits.mdx rename to website/pages/ur/roles-and-benefits/benefits.mdx diff --git a/website/pages/ur/network/curating.mdx b/website/pages/ur/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/ur/network/curating.mdx rename to website/pages/ur/roles-and-benefits/curating.mdx diff --git a/website/pages/ur/network/delegating.mdx b/website/pages/ur/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/ur/network/delegating.mdx rename to website/pages/ur/roles-and-benefits/delegating.mdx diff --git a/website/pages/ur/network/overview.mdx b/website/pages/ur/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/ur/network/overview.mdx rename to website/pages/ur/roles-and-benefits/overview.mdx diff --git a/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ur/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/ur/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/vi/arbitrum/_meta.js b/website/pages/vi/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/vi/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/archived/_meta.js b/website/pages/vi/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/vi/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/archived/arbitrum/_meta.js b/website/pages/vi/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/vi/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/arbitrum/arbitrum-faq.mdx b/website/pages/vi/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/vi/arbitrum/arbitrum-faq.mdx rename to website/pages/vi/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/vi/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/vi/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/vi/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/vi/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/vi/sunrise.mdx b/website/pages/vi/archived/sunrise.mdx similarity index 100% rename from website/pages/vi/sunrise.mdx rename to website/pages/vi/archived/sunrise.mdx diff --git a/website/pages/vi/network/contracts.mdx b/website/pages/vi/contracts.mdx similarity index 100% rename from website/pages/vi/network/contracts.mdx rename to website/pages/vi/contracts.mdx diff --git a/website/pages/vi/deploying/_meta.js b/website/pages/vi/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/vi/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/developing/graph-ts/api.mdx b/website/pages/vi/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/vi/developing/graph-ts/api.mdx rename to website/pages/vi/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/vi/developing/graph-ts/common-issues.mdx b/website/pages/vi/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/vi/developing/graph-ts/common-issues.mdx rename to website/pages/vi/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/vi/developing/unit-testing-framework.mdx b/website/pages/vi/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/vi/developing/unit-testing-framework.mdx rename to website/pages/vi/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/vi/developing/deploying/_meta.js b/website/pages/vi/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/vi/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/deploying/deploy-using-subgraph-studio.mdx b/website/pages/vi/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/vi/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/vi/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/vi/deploying/multiple-networks.mdx b/website/pages/vi/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/vi/deploying/multiple-networks.mdx rename to website/pages/vi/developing/deploying/multiple-networks.mdx diff --git a/website/pages/vi/deploying/subgraph-studio-faqs.mdx b/website/pages/vi/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/vi/deploying/subgraph-studio-faqs.mdx rename to website/pages/vi/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/vi/network/developing.mdx b/website/pages/vi/developing/developing.mdx similarity index 100% rename from website/pages/vi/network/developing.mdx rename to website/pages/vi/developing/developing.mdx diff --git a/website/pages/vi/developing/graph-ts/_meta.js b/website/pages/vi/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/vi/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/managing/_meta.js b/website/pages/vi/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/vi/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/managing/delete-a-subgraph.mdx b/website/pages/vi/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/vi/managing/delete-a-subgraph.mdx rename to website/pages/vi/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/vi/managing/transfer-a-subgraph.mdx b/website/pages/vi/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/vi/managing/transfer-a-subgraph.mdx rename to website/pages/vi/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/vi/developing/publishing/_meta.js b/website/pages/vi/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/vi/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/publishing/publishing-a-subgraph.mdx b/website/pages/vi/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/vi/publishing/publishing-a-subgraph.mdx rename to website/pages/vi/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/vi/subgraphs.mdx b/website/pages/vi/developing/subgraphs.mdx similarity index 100% rename from website/pages/vi/subgraphs.mdx rename to website/pages/vi/developing/subgraphs.mdx diff --git a/website/pages/vi/network/explorer.mdx b/website/pages/vi/explorer.mdx similarity index 100% rename from website/pages/vi/network/explorer.mdx rename to website/pages/vi/explorer.mdx diff --git a/website/pages/vi/indexer-tooling/_meta.js b/website/pages/vi/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/vi/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/firehose.mdx b/website/pages/vi/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/vi/firehose.mdx rename to website/pages/vi/indexer-tooling/firehose.mdx diff --git a/website/pages/vi/graphcast.mdx b/website/pages/vi/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/vi/graphcast.mdx rename to website/pages/vi/indexer-tooling/graphcast.mdx diff --git a/website/pages/vi/operating-graph-node.mdx b/website/pages/vi/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/vi/operating-graph-node.mdx rename to website/pages/vi/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/vi/network/indexing.mdx b/website/pages/vi/indexing.mdx similarity index 100% rename from website/pages/vi/network/indexing.mdx rename to website/pages/vi/indexing.mdx diff --git a/website/pages/vi/managing/_meta.js b/website/pages/vi/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/vi/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/network/_meta.js b/website/pages/vi/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/vi/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/publishing/_meta.js b/website/pages/vi/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/vi/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/roles-and-benefits/_meta.js b/website/pages/vi/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/vi/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/network/benefits.mdx b/website/pages/vi/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/vi/network/benefits.mdx rename to website/pages/vi/roles-and-benefits/benefits.mdx diff --git a/website/pages/vi/network/curating.mdx b/website/pages/vi/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/vi/network/curating.mdx rename to website/pages/vi/roles-and-benefits/curating.mdx diff --git a/website/pages/vi/network/delegating.mdx b/website/pages/vi/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/vi/network/delegating.mdx rename to website/pages/vi/roles-and-benefits/delegating.mdx diff --git a/website/pages/vi/network/overview.mdx b/website/pages/vi/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/vi/network/overview.mdx rename to website/pages/vi/roles-and-benefits/overview.mdx diff --git a/website/pages/vi/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/vi/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/vi/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/vi/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/zh/arbitrum/_meta.js b/website/pages/zh/arbitrum/_meta.js deleted file mode 100644 index 321fe93849be..000000000000 --- a/website/pages/zh/arbitrum/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/arbitrum/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/archived/_meta.js b/website/pages/zh/archived/_meta.js new file mode 100644 index 000000000000..d1341196f7d2 --- /dev/null +++ b/website/pages/zh/archived/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/archived/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/archived/arbitrum/_meta.js b/website/pages/zh/archived/arbitrum/_meta.js new file mode 100644 index 000000000000..944ca24a1f62 --- /dev/null +++ b/website/pages/zh/archived/arbitrum/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/archived/arbitrum/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/arbitrum/arbitrum-faq.mdx b/website/pages/zh/archived/arbitrum/arbitrum-faq.mdx similarity index 100% rename from website/pages/zh/arbitrum/arbitrum-faq.mdx rename to website/pages/zh/archived/arbitrum/arbitrum-faq.mdx diff --git a/website/pages/zh/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/zh/archived/arbitrum/l2-transfer-tools-faq.mdx similarity index 100% rename from website/pages/zh/arbitrum/l2-transfer-tools-faq.mdx rename to website/pages/zh/archived/arbitrum/l2-transfer-tools-faq.mdx diff --git a/website/pages/zh/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/zh/archived/arbitrum/l2-transfer-tools-guide.mdx similarity index 100% rename from website/pages/zh/arbitrum/l2-transfer-tools-guide.mdx rename to website/pages/zh/archived/arbitrum/l2-transfer-tools-guide.mdx diff --git a/website/pages/zh/sunrise.mdx b/website/pages/zh/archived/sunrise.mdx similarity index 100% rename from website/pages/zh/sunrise.mdx rename to website/pages/zh/archived/sunrise.mdx diff --git a/website/pages/zh/network/contracts.mdx b/website/pages/zh/contracts.mdx similarity index 100% rename from website/pages/zh/network/contracts.mdx rename to website/pages/zh/contracts.mdx diff --git a/website/pages/zh/deploying/_meta.js b/website/pages/zh/deploying/_meta.js deleted file mode 100644 index 3d7abedc4d57..000000000000 --- a/website/pages/zh/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js new file mode 100644 index 000000000000..9c23f4f1b1a1 --- /dev/null +++ b/website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/developing/graph-ts/api.mdx b/website/pages/zh/developing/creating-a-subgraph/graph-ts/api.mdx similarity index 100% rename from website/pages/zh/developing/graph-ts/api.mdx rename to website/pages/zh/developing/creating-a-subgraph/graph-ts/api.mdx diff --git a/website/pages/zh/developing/graph-ts/common-issues.mdx b/website/pages/zh/developing/creating-a-subgraph/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/zh/developing/graph-ts/common-issues.mdx rename to website/pages/zh/developing/creating-a-subgraph/graph-ts/common-issues.mdx diff --git a/website/pages/zh/developing/unit-testing-framework.mdx b/website/pages/zh/developing/creating-a-subgraph/unit-testing-framework.mdx similarity index 100% rename from website/pages/zh/developing/unit-testing-framework.mdx rename to website/pages/zh/developing/creating-a-subgraph/unit-testing-framework.mdx diff --git a/website/pages/zh/developing/deploying/_meta.js b/website/pages/zh/developing/deploying/_meta.js new file mode 100644 index 000000000000..7d696b40205a --- /dev/null +++ b/website/pages/zh/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/deploying/deploy-using-subgraph-studio.mdx b/website/pages/zh/developing/deploying/deploy-using-subgraph-studio.mdx similarity index 100% rename from website/pages/zh/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/zh/developing/deploying/deploy-using-subgraph-studio.mdx diff --git a/website/pages/zh/deploying/multiple-networks.mdx b/website/pages/zh/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/zh/deploying/multiple-networks.mdx rename to website/pages/zh/developing/deploying/multiple-networks.mdx diff --git a/website/pages/zh/deploying/subgraph-studio-faqs.mdx b/website/pages/zh/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/zh/deploying/subgraph-studio-faqs.mdx rename to website/pages/zh/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/zh/network/developing.mdx b/website/pages/zh/developing/developing.mdx similarity index 100% rename from website/pages/zh/network/developing.mdx rename to website/pages/zh/developing/developing.mdx diff --git a/website/pages/zh/developing/graph-ts/_meta.js b/website/pages/zh/developing/graph-ts/_meta.js deleted file mode 100644 index 466762da9ce8..000000000000 --- a/website/pages/zh/developing/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/managing/_meta.js b/website/pages/zh/developing/managing/_meta.js new file mode 100644 index 000000000000..faa0447a3553 --- /dev/null +++ b/website/pages/zh/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/managing/delete-a-subgraph.mdx b/website/pages/zh/developing/managing/delete-a-subgraph.mdx similarity index 100% rename from website/pages/zh/managing/delete-a-subgraph.mdx rename to website/pages/zh/developing/managing/delete-a-subgraph.mdx diff --git a/website/pages/zh/managing/transfer-a-subgraph.mdx b/website/pages/zh/developing/managing/transfer-a-subgraph.mdx similarity index 100% rename from website/pages/zh/managing/transfer-a-subgraph.mdx rename to website/pages/zh/developing/managing/transfer-a-subgraph.mdx diff --git a/website/pages/zh/developing/publishing/_meta.js b/website/pages/zh/developing/publishing/_meta.js new file mode 100644 index 000000000000..5fa714a2763a --- /dev/null +++ b/website/pages/zh/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/publishing/publishing-a-subgraph.mdx b/website/pages/zh/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/zh/publishing/publishing-a-subgraph.mdx rename to website/pages/zh/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/zh/subgraphs.mdx b/website/pages/zh/developing/subgraphs.mdx similarity index 100% rename from website/pages/zh/subgraphs.mdx rename to website/pages/zh/developing/subgraphs.mdx diff --git a/website/pages/zh/network/explorer.mdx b/website/pages/zh/explorer.mdx similarity index 100% rename from website/pages/zh/network/explorer.mdx rename to website/pages/zh/explorer.mdx diff --git a/website/pages/zh/indexer-tooling/_meta.js b/website/pages/zh/indexer-tooling/_meta.js new file mode 100644 index 000000000000..3d6a0e72ad23 --- /dev/null +++ b/website/pages/zh/indexer-tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexer-tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/firehose.mdx b/website/pages/zh/indexer-tooling/firehose.mdx similarity index 100% rename from website/pages/zh/firehose.mdx rename to website/pages/zh/indexer-tooling/firehose.mdx diff --git a/website/pages/zh/graphcast.mdx b/website/pages/zh/indexer-tooling/graphcast.mdx similarity index 100% rename from website/pages/zh/graphcast.mdx rename to website/pages/zh/indexer-tooling/graphcast.mdx diff --git a/website/pages/zh/operating-graph-node.mdx b/website/pages/zh/indexer-tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/zh/operating-graph-node.mdx rename to website/pages/zh/indexer-tooling/operating-graph-node.mdx diff --git a/website/pages/zh/network/indexing.mdx b/website/pages/zh/indexing.mdx similarity index 100% rename from website/pages/zh/network/indexing.mdx rename to website/pages/zh/indexing.mdx diff --git a/website/pages/zh/managing/_meta.js b/website/pages/zh/managing/_meta.js deleted file mode 100644 index a7c7b3d79464..000000000000 --- a/website/pages/zh/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/network/_meta.js b/website/pages/zh/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/zh/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/publishing/_meta.js b/website/pages/zh/publishing/_meta.js deleted file mode 100644 index eb06f56f912a..000000000000 --- a/website/pages/zh/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/roles-and-benefits/_meta.js b/website/pages/zh/roles-and-benefits/_meta.js new file mode 100644 index 000000000000..cc666d15a6ca --- /dev/null +++ b/website/pages/zh/roles-and-benefits/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/roles-and-benefits/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/network/benefits.mdx b/website/pages/zh/roles-and-benefits/benefits.mdx similarity index 100% rename from website/pages/zh/network/benefits.mdx rename to website/pages/zh/roles-and-benefits/benefits.mdx diff --git a/website/pages/zh/network/curating.mdx b/website/pages/zh/roles-and-benefits/curating.mdx similarity index 100% rename from website/pages/zh/network/curating.mdx rename to website/pages/zh/roles-and-benefits/curating.mdx diff --git a/website/pages/zh/network/delegating.mdx b/website/pages/zh/roles-and-benefits/delegating.mdx similarity index 100% rename from website/pages/zh/network/delegating.mdx rename to website/pages/zh/roles-and-benefits/delegating.mdx diff --git a/website/pages/zh/network/overview.mdx b/website/pages/zh/roles-and-benefits/overview.mdx similarity index 100% rename from website/pages/zh/network/overview.mdx rename to website/pages/zh/roles-and-benefits/overview.mdx diff --git a/website/pages/zh/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/zh/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/zh/developing/substreams-powered-subgraphs-faq.mdx rename to website/pages/zh/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/route-lockfile.txt b/website/route-lockfile.txt index 56593e71f953..5483dda68765 100644 --- a/website/route-lockfile.txt +++ b/website/route-lockfile.txt @@ -2,11 +2,13 @@ /ar/ /ar/404/ /ar/about/ -/ar/arbitrum/arbitrum-faq/ -/ar/arbitrum/l2-transfer-tools-faq/ -/ar/arbitrum/l2-transfer-tools-guide/ +/ar/archived/arbitrum/arbitrum-faq/ +/ar/archived/arbitrum/l2-transfer-tools-faq/ +/ar/archived/arbitrum/l2-transfer-tools-guide/ +/ar/archived/sunrise/ /ar/billing/ /ar/chain-integration-overview/ +/ar/contracts/ /ar/cookbook/arweave/ /ar/cookbook/avoid-eth-calls/ /ar/cookbook/cosmos/ @@ -23,37 +25,32 @@ /ar/cookbook/substreams-powered-subgraphs/ /ar/cookbook/timeseries/ /ar/cookbook/transfer-to-the-graph/ -/ar/deploying/deploy-using-subgraph-studio/ -/ar/deploying/multiple-networks/ -/ar/deploying/subgraph-studio-faqs/ /ar/developing/creating-a-subgraph/advanced/ /ar/developing/creating-a-subgraph/assemblyscript-mappings/ +/ar/developing/creating-a-subgraph/graph-ts/api/ +/ar/developing/creating-a-subgraph/graph-ts/common-issues/ /ar/developing/creating-a-subgraph/install-the-cli/ /ar/developing/creating-a-subgraph/ql-schema/ /ar/developing/creating-a-subgraph/starting-your-subgraph/ /ar/developing/creating-a-subgraph/subgraph-manifest/ +/ar/developing/creating-a-subgraph/unit-testing-framework/ +/ar/developing/deploying/deploy-using-subgraph-studio/ +/ar/developing/deploying/multiple-networks/ +/ar/developing/deploying/subgraph-studio-faqs/ /ar/developing/developer-faqs/ -/ar/developing/graph-ts/api/ -/ar/developing/graph-ts/common-issues/ -/ar/developing/substreams-powered-subgraphs-faq/ +/ar/developing/developing/ +/ar/developing/managing/delete-a-subgraph/ +/ar/developing/managing/transfer-a-subgraph/ +/ar/developing/publishing/publishing-a-subgraph/ +/ar/developing/subgraphs/ /ar/developing/supported-networks/ -/ar/developing/unit-testing-framework/ -/ar/firehose/ +/ar/explorer/ /ar/glossary/ -/ar/graphcast/ -/ar/managing/delete-a-subgraph/ -/ar/managing/transfer-a-subgraph/ -/ar/network/benefits/ -/ar/network/contracts/ -/ar/network/curating/ -/ar/network/delegating/ -/ar/network/developing/ -/ar/network/explorer/ -/ar/network/indexing/ -/ar/network/overview/ +/ar/indexer-tooling/firehose/ +/ar/indexer-tooling/graphcast/ +/ar/indexer-tooling/operating-graph-node/ +/ar/indexing/ /ar/new-chain-integration/ -/ar/operating-graph-node/ -/ar/publishing/publishing-a-subgraph/ /ar/querying/distributed-systems/ /ar/querying/graphql-api/ /ar/querying/managing-api-keys/ @@ -65,23 +62,28 @@ /ar/quick-start/ /ar/release-notes/assemblyscript-migration-guide/ /ar/release-notes/graphql-validations-migration-guide/ +/ar/roles-and-benefits/benefits/ +/ar/roles-and-benefits/curating/ +/ar/roles-and-benefits/delegating/ +/ar/roles-and-benefits/overview/ /ar/sps/introduction/ +/ar/sps/substreams-powered-subgraphs-faq/ /ar/sps/triggers-example/ /ar/sps/triggers/ -/ar/subgraphs/ /ar/substreams/ -/ar/sunrise/ /ar/supported-network-requirements/ /ar/tap/ /ar/tokenomics/ /cs/ /cs/404/ /cs/about/ -/cs/arbitrum/arbitrum-faq/ -/cs/arbitrum/l2-transfer-tools-faq/ -/cs/arbitrum/l2-transfer-tools-guide/ +/cs/archived/arbitrum/arbitrum-faq/ +/cs/archived/arbitrum/l2-transfer-tools-faq/ +/cs/archived/arbitrum/l2-transfer-tools-guide/ +/cs/archived/sunrise/ /cs/billing/ /cs/chain-integration-overview/ +/cs/contracts/ /cs/cookbook/arweave/ /cs/cookbook/avoid-eth-calls/ /cs/cookbook/cosmos/ @@ -98,37 +100,32 @@ /cs/cookbook/substreams-powered-subgraphs/ /cs/cookbook/timeseries/ /cs/cookbook/transfer-to-the-graph/ -/cs/deploying/deploy-using-subgraph-studio/ -/cs/deploying/multiple-networks/ -/cs/deploying/subgraph-studio-faqs/ /cs/developing/creating-a-subgraph/advanced/ /cs/developing/creating-a-subgraph/assemblyscript-mappings/ +/cs/developing/creating-a-subgraph/graph-ts/api/ +/cs/developing/creating-a-subgraph/graph-ts/common-issues/ /cs/developing/creating-a-subgraph/install-the-cli/ /cs/developing/creating-a-subgraph/ql-schema/ /cs/developing/creating-a-subgraph/starting-your-subgraph/ /cs/developing/creating-a-subgraph/subgraph-manifest/ +/cs/developing/creating-a-subgraph/unit-testing-framework/ +/cs/developing/deploying/deploy-using-subgraph-studio/ +/cs/developing/deploying/multiple-networks/ +/cs/developing/deploying/subgraph-studio-faqs/ /cs/developing/developer-faqs/ -/cs/developing/graph-ts/api/ -/cs/developing/graph-ts/common-issues/ -/cs/developing/substreams-powered-subgraphs-faq/ +/cs/developing/developing/ +/cs/developing/managing/delete-a-subgraph/ +/cs/developing/managing/transfer-a-subgraph/ +/cs/developing/publishing/publishing-a-subgraph/ +/cs/developing/subgraphs/ /cs/developing/supported-networks/ -/cs/developing/unit-testing-framework/ -/cs/firehose/ +/cs/explorer/ /cs/glossary/ -/cs/graphcast/ -/cs/managing/delete-a-subgraph/ -/cs/managing/transfer-a-subgraph/ -/cs/network/benefits/ -/cs/network/contracts/ -/cs/network/curating/ -/cs/network/delegating/ -/cs/network/developing/ -/cs/network/explorer/ -/cs/network/indexing/ -/cs/network/overview/ +/cs/indexer-tooling/firehose/ +/cs/indexer-tooling/graphcast/ +/cs/indexer-tooling/operating-graph-node/ +/cs/indexing/ /cs/new-chain-integration/ -/cs/operating-graph-node/ -/cs/publishing/publishing-a-subgraph/ /cs/querying/distributed-systems/ /cs/querying/graphql-api/ /cs/querying/managing-api-keys/ @@ -140,21 +137,26 @@ /cs/quick-start/ /cs/release-notes/assemblyscript-migration-guide/ /cs/release-notes/graphql-validations-migration-guide/ +/cs/roles-and-benefits/benefits/ +/cs/roles-and-benefits/curating/ +/cs/roles-and-benefits/delegating/ +/cs/roles-and-benefits/overview/ /cs/sps/introduction/ +/cs/sps/substreams-powered-subgraphs-faq/ /cs/sps/triggers-example/ /cs/sps/triggers/ -/cs/subgraphs/ /cs/substreams/ -/cs/sunrise/ /cs/supported-network-requirements/ /cs/tap/ /cs/tokenomics/ /de/about/ -/de/arbitrum/arbitrum-faq/ -/de/arbitrum/l2-transfer-tools-faq/ -/de/arbitrum/l2-transfer-tools-guide/ +/de/archived/arbitrum/arbitrum-faq/ +/de/archived/arbitrum/l2-transfer-tools-faq/ +/de/archived/arbitrum/l2-transfer-tools-guide/ +/de/archived/sunrise/ /de/billing/ /de/chain-integration-overview/ +/de/contracts/ /de/cookbook/arweave/ /de/cookbook/avoid-eth-calls/ /de/cookbook/cosmos/ @@ -171,37 +173,32 @@ /de/cookbook/substreams-powered-subgraphs/ /de/cookbook/timeseries/ /de/cookbook/transfer-to-the-graph/ -/de/deploying/deploy-using-subgraph-studio/ -/de/deploying/multiple-networks/ -/de/deploying/subgraph-studio-faqs/ /de/developing/creating-a-subgraph/advanced/ /de/developing/creating-a-subgraph/assemblyscript-mappings/ +/de/developing/creating-a-subgraph/graph-ts/api/ +/de/developing/creating-a-subgraph/graph-ts/common-issues/ /de/developing/creating-a-subgraph/install-the-cli/ /de/developing/creating-a-subgraph/ql-schema/ /de/developing/creating-a-subgraph/starting-your-subgraph/ /de/developing/creating-a-subgraph/subgraph-manifest/ +/de/developing/creating-a-subgraph/unit-testing-framework/ +/de/developing/deploying/deploy-using-subgraph-studio/ +/de/developing/deploying/multiple-networks/ +/de/developing/deploying/subgraph-studio-faqs/ /de/developing/developer-faqs/ -/de/developing/graph-ts/api/ -/de/developing/graph-ts/common-issues/ -/de/developing/substreams-powered-subgraphs-faq/ +/de/developing/developing/ +/de/developing/managing/delete-a-subgraph/ +/de/developing/managing/transfer-a-subgraph/ +/de/developing/publishing/publishing-a-subgraph/ +/de/developing/subgraphs/ /de/developing/supported-networks/ -/de/developing/unit-testing-framework/ -/de/firehose/ +/de/explorer/ /de/glossary/ -/de/graphcast/ -/de/managing/delete-a-subgraph/ -/de/managing/transfer-a-subgraph/ -/de/network/benefits/ -/de/network/contracts/ -/de/network/curating/ -/de/network/delegating/ -/de/network/developing/ -/de/network/explorer/ -/de/network/indexing/ -/de/network/overview/ +/de/indexer-tooling/firehose/ +/de/indexer-tooling/graphcast/ +/de/indexer-tooling/operating-graph-node/ +/de/indexing/ /de/new-chain-integration/ -/de/operating-graph-node/ -/de/publishing/publishing-a-subgraph/ /de/querying/distributed-systems/ /de/querying/graphql-api/ /de/querying/managing-api-keys/ @@ -213,23 +210,28 @@ /de/quick-start/ /de/release-notes/assemblyscript-migration-guide/ /de/release-notes/graphql-validations-migration-guide/ +/de/roles-and-benefits/benefits/ +/de/roles-and-benefits/curating/ +/de/roles-and-benefits/delegating/ +/de/roles-and-benefits/overview/ /de/sps/introduction/ +/de/sps/substreams-powered-subgraphs-faq/ /de/sps/triggers-example/ /de/sps/triggers/ -/de/subgraphs/ /de/substreams/ -/de/sunrise/ /de/supported-network-requirements/ /de/tap/ /de/tokenomics/ /en/ /en/404/ /en/about/ -/en/arbitrum/arbitrum-faq/ -/en/arbitrum/l2-transfer-tools-faq/ -/en/arbitrum/l2-transfer-tools-guide/ +/en/archived/arbitrum/arbitrum-faq/ +/en/archived/arbitrum/l2-transfer-tools-faq/ +/en/archived/arbitrum/l2-transfer-tools-guide/ +/en/archived/sunrise/ /en/billing/ /en/chain-integration-overview/ +/en/contracts/ /en/cookbook/arweave/ /en/cookbook/avoid-eth-calls/ /en/cookbook/cosmos/ @@ -246,39 +248,34 @@ /en/cookbook/substreams-powered-subgraphs/ /en/cookbook/timeseries/ /en/cookbook/transfer-to-the-graph/ -/en/deploying/deploy-using-subgraph-studio/ -/en/deploying/multiple-networks/ -/en/deploying/subgraph-studio-faqs/ /en/developing/creating-a-subgraph/advanced/ /en/developing/creating-a-subgraph/assemblyscript-mappings/ +/en/developing/creating-a-subgraph/graph-ts/CHANGELOG/ +/en/developing/creating-a-subgraph/graph-ts/README/ +/en/developing/creating-a-subgraph/graph-ts/api/ +/en/developing/creating-a-subgraph/graph-ts/common-issues/ /en/developing/creating-a-subgraph/install-the-cli/ /en/developing/creating-a-subgraph/ql-schema/ /en/developing/creating-a-subgraph/starting-your-subgraph/ /en/developing/creating-a-subgraph/subgraph-manifest/ +/en/developing/creating-a-subgraph/unit-testing-framework/ +/en/developing/deploying/deploy-using-subgraph-studio/ +/en/developing/deploying/multiple-networks/ +/en/developing/deploying/subgraph-studio-faqs/ /en/developing/developer-faqs/ -/en/developing/graph-ts/CHANGELOG/ -/en/developing/graph-ts/README/ -/en/developing/graph-ts/api/ -/en/developing/graph-ts/common-issues/ -/en/developing/substreams-powered-subgraphs-faq/ +/en/developing/developing/ +/en/developing/managing/delete-a-subgraph/ +/en/developing/managing/transfer-a-subgraph/ +/en/developing/publishing/publishing-a-subgraph/ +/en/developing/subgraphs/ /en/developing/supported-networks/ -/en/developing/unit-testing-framework/ -/en/firehose/ +/en/explorer/ /en/glossary/ -/en/graphcast/ -/en/managing/delete-a-subgraph/ -/en/managing/transfer-a-subgraph/ -/en/network/benefits/ -/en/network/contracts/ -/en/network/curating/ -/en/network/delegating/ -/en/network/developing/ -/en/network/explorer/ -/en/network/indexing/ -/en/network/overview/ +/en/indexer-tooling/firehose/ +/en/indexer-tooling/graphcast/ +/en/indexer-tooling/operating-graph-node/ +/en/indexing/ /en/new-chain-integration/ -/en/operating-graph-node/ -/en/publishing/publishing-a-subgraph/ /en/querying/distributed-systems/ /en/querying/graph-client/README/ /en/querying/graph-client/architecture/ @@ -293,23 +290,28 @@ /en/quick-start/ /en/release-notes/assemblyscript-migration-guide/ /en/release-notes/graphql-validations-migration-guide/ +/en/roles-and-benefits/benefits/ +/en/roles-and-benefits/curating/ +/en/roles-and-benefits/delegating/ +/en/roles-and-benefits/overview/ /en/sps/introduction/ +/en/sps/substreams-powered-subgraphs-faq/ /en/sps/triggers-example/ /en/sps/triggers/ -/en/subgraphs/ /en/substreams/ -/en/sunrise/ /en/supported-network-requirements/ /en/tap/ /en/tokenomics/ /es/ /es/404/ /es/about/ -/es/arbitrum/arbitrum-faq/ -/es/arbitrum/l2-transfer-tools-faq/ -/es/arbitrum/l2-transfer-tools-guide/ +/es/archived/arbitrum/arbitrum-faq/ +/es/archived/arbitrum/l2-transfer-tools-faq/ +/es/archived/arbitrum/l2-transfer-tools-guide/ +/es/archived/sunrise/ /es/billing/ /es/chain-integration-overview/ +/es/contracts/ /es/cookbook/arweave/ /es/cookbook/avoid-eth-calls/ /es/cookbook/cosmos/ @@ -326,37 +328,32 @@ /es/cookbook/substreams-powered-subgraphs/ /es/cookbook/timeseries/ /es/cookbook/transfer-to-the-graph/ -/es/deploying/deploy-using-subgraph-studio/ -/es/deploying/multiple-networks/ -/es/deploying/subgraph-studio-faqs/ /es/developing/creating-a-subgraph/advanced/ /es/developing/creating-a-subgraph/assemblyscript-mappings/ +/es/developing/creating-a-subgraph/graph-ts/api/ +/es/developing/creating-a-subgraph/graph-ts/common-issues/ /es/developing/creating-a-subgraph/install-the-cli/ /es/developing/creating-a-subgraph/ql-schema/ /es/developing/creating-a-subgraph/starting-your-subgraph/ /es/developing/creating-a-subgraph/subgraph-manifest/ +/es/developing/creating-a-subgraph/unit-testing-framework/ +/es/developing/deploying/deploy-using-subgraph-studio/ +/es/developing/deploying/multiple-networks/ +/es/developing/deploying/subgraph-studio-faqs/ /es/developing/developer-faqs/ -/es/developing/graph-ts/api/ -/es/developing/graph-ts/common-issues/ -/es/developing/substreams-powered-subgraphs-faq/ +/es/developing/developing/ +/es/developing/managing/delete-a-subgraph/ +/es/developing/managing/transfer-a-subgraph/ +/es/developing/publishing/publishing-a-subgraph/ +/es/developing/subgraphs/ /es/developing/supported-networks/ -/es/developing/unit-testing-framework/ -/es/firehose/ +/es/explorer/ /es/glossary/ -/es/graphcast/ -/es/managing/delete-a-subgraph/ -/es/managing/transfer-a-subgraph/ -/es/network/benefits/ -/es/network/contracts/ -/es/network/curating/ -/es/network/delegating/ -/es/network/developing/ -/es/network/explorer/ -/es/network/indexing/ -/es/network/overview/ +/es/indexer-tooling/firehose/ +/es/indexer-tooling/graphcast/ +/es/indexer-tooling/operating-graph-node/ +/es/indexing/ /es/new-chain-integration/ -/es/operating-graph-node/ -/es/publishing/publishing-a-subgraph/ /es/querying/distributed-systems/ /es/querying/graphql-api/ /es/querying/managing-api-keys/ @@ -368,23 +365,28 @@ /es/quick-start/ /es/release-notes/assemblyscript-migration-guide/ /es/release-notes/graphql-validations-migration-guide/ +/es/roles-and-benefits/benefits/ +/es/roles-and-benefits/curating/ +/es/roles-and-benefits/delegating/ +/es/roles-and-benefits/overview/ /es/sps/introduction/ +/es/sps/substreams-powered-subgraphs-faq/ /es/sps/triggers-example/ /es/sps/triggers/ -/es/subgraphs/ /es/substreams/ -/es/sunrise/ /es/supported-network-requirements/ /es/tap/ /es/tokenomics/ /fr/ /fr/404/ /fr/about/ -/fr/arbitrum/arbitrum-faq/ -/fr/arbitrum/l2-transfer-tools-faq/ -/fr/arbitrum/l2-transfer-tools-guide/ +/fr/archived/arbitrum/arbitrum-faq/ +/fr/archived/arbitrum/l2-transfer-tools-faq/ +/fr/archived/arbitrum/l2-transfer-tools-guide/ +/fr/archived/sunrise/ /fr/billing/ /fr/chain-integration-overview/ +/fr/contracts/ /fr/cookbook/arweave/ /fr/cookbook/avoid-eth-calls/ /fr/cookbook/cosmos/ @@ -401,37 +403,32 @@ /fr/cookbook/substreams-powered-subgraphs/ /fr/cookbook/timeseries/ /fr/cookbook/transfer-to-the-graph/ -/fr/deploying/deploy-using-subgraph-studio/ -/fr/deploying/multiple-networks/ -/fr/deploying/subgraph-studio-faqs/ /fr/developing/creating-a-subgraph/advanced/ /fr/developing/creating-a-subgraph/assemblyscript-mappings/ +/fr/developing/creating-a-subgraph/graph-ts/api/ +/fr/developing/creating-a-subgraph/graph-ts/common-issues/ /fr/developing/creating-a-subgraph/install-the-cli/ /fr/developing/creating-a-subgraph/ql-schema/ /fr/developing/creating-a-subgraph/starting-your-subgraph/ /fr/developing/creating-a-subgraph/subgraph-manifest/ +/fr/developing/creating-a-subgraph/unit-testing-framework/ +/fr/developing/deploying/deploy-using-subgraph-studio/ +/fr/developing/deploying/multiple-networks/ +/fr/developing/deploying/subgraph-studio-faqs/ /fr/developing/developer-faqs/ -/fr/developing/graph-ts/api/ -/fr/developing/graph-ts/common-issues/ -/fr/developing/substreams-powered-subgraphs-faq/ +/fr/developing/developing/ +/fr/developing/managing/delete-a-subgraph/ +/fr/developing/managing/transfer-a-subgraph/ +/fr/developing/publishing/publishing-a-subgraph/ +/fr/developing/subgraphs/ /fr/developing/supported-networks/ -/fr/developing/unit-testing-framework/ -/fr/firehose/ +/fr/explorer/ /fr/glossary/ -/fr/graphcast/ -/fr/managing/delete-a-subgraph/ -/fr/managing/transfer-a-subgraph/ -/fr/network/benefits/ -/fr/network/contracts/ -/fr/network/curating/ -/fr/network/delegating/ -/fr/network/developing/ -/fr/network/explorer/ -/fr/network/indexing/ -/fr/network/overview/ +/fr/indexer-tooling/firehose/ +/fr/indexer-tooling/graphcast/ +/fr/indexer-tooling/operating-graph-node/ +/fr/indexing/ /fr/new-chain-integration/ -/fr/operating-graph-node/ -/fr/publishing/publishing-a-subgraph/ /fr/querying/distributed-systems/ /fr/querying/graphql-api/ /fr/querying/managing-api-keys/ @@ -443,23 +440,28 @@ /fr/quick-start/ /fr/release-notes/assemblyscript-migration-guide/ /fr/release-notes/graphql-validations-migration-guide/ +/fr/roles-and-benefits/benefits/ +/fr/roles-and-benefits/curating/ +/fr/roles-and-benefits/delegating/ +/fr/roles-and-benefits/overview/ /fr/sps/introduction/ +/fr/sps/substreams-powered-subgraphs-faq/ /fr/sps/triggers-example/ /fr/sps/triggers/ -/fr/subgraphs/ /fr/substreams/ -/fr/sunrise/ /fr/supported-network-requirements/ /fr/tap/ /fr/tokenomics/ /hi/ /hi/404/ /hi/about/ -/hi/arbitrum/arbitrum-faq/ -/hi/arbitrum/l2-transfer-tools-faq/ -/hi/arbitrum/l2-transfer-tools-guide/ +/hi/archived/arbitrum/arbitrum-faq/ +/hi/archived/arbitrum/l2-transfer-tools-faq/ +/hi/archived/arbitrum/l2-transfer-tools-guide/ +/hi/archived/sunrise/ /hi/billing/ /hi/chain-integration-overview/ +/hi/contracts/ /hi/cookbook/arweave/ /hi/cookbook/avoid-eth-calls/ /hi/cookbook/cosmos/ @@ -476,37 +478,32 @@ /hi/cookbook/substreams-powered-subgraphs/ /hi/cookbook/timeseries/ /hi/cookbook/transfer-to-the-graph/ -/hi/deploying/deploy-using-subgraph-studio/ -/hi/deploying/multiple-networks/ -/hi/deploying/subgraph-studio-faqs/ /hi/developing/creating-a-subgraph/advanced/ /hi/developing/creating-a-subgraph/assemblyscript-mappings/ +/hi/developing/creating-a-subgraph/graph-ts/api/ +/hi/developing/creating-a-subgraph/graph-ts/common-issues/ /hi/developing/creating-a-subgraph/install-the-cli/ /hi/developing/creating-a-subgraph/ql-schema/ /hi/developing/creating-a-subgraph/starting-your-subgraph/ /hi/developing/creating-a-subgraph/subgraph-manifest/ +/hi/developing/creating-a-subgraph/unit-testing-framework/ +/hi/developing/deploying/deploy-using-subgraph-studio/ +/hi/developing/deploying/multiple-networks/ +/hi/developing/deploying/subgraph-studio-faqs/ /hi/developing/developer-faqs/ -/hi/developing/graph-ts/api/ -/hi/developing/graph-ts/common-issues/ -/hi/developing/substreams-powered-subgraphs-faq/ +/hi/developing/developing/ +/hi/developing/managing/delete-a-subgraph/ +/hi/developing/managing/transfer-a-subgraph/ +/hi/developing/publishing/publishing-a-subgraph/ +/hi/developing/subgraphs/ /hi/developing/supported-networks/ -/hi/developing/unit-testing-framework/ -/hi/firehose/ +/hi/explorer/ /hi/glossary/ -/hi/graphcast/ -/hi/managing/delete-a-subgraph/ -/hi/managing/transfer-a-subgraph/ -/hi/network/benefits/ -/hi/network/contracts/ -/hi/network/curating/ -/hi/network/delegating/ -/hi/network/developing/ -/hi/network/explorer/ -/hi/network/indexing/ -/hi/network/overview/ +/hi/indexer-tooling/firehose/ +/hi/indexer-tooling/graphcast/ +/hi/indexer-tooling/operating-graph-node/ +/hi/indexing/ /hi/new-chain-integration/ -/hi/operating-graph-node/ -/hi/publishing/publishing-a-subgraph/ /hi/querying/distributed-systems/ /hi/querying/graphql-api/ /hi/querying/managing-api-keys/ @@ -518,23 +515,28 @@ /hi/quick-start/ /hi/release-notes/assemblyscript-migration-guide/ /hi/release-notes/graphql-validations-migration-guide/ +/hi/roles-and-benefits/benefits/ +/hi/roles-and-benefits/curating/ +/hi/roles-and-benefits/delegating/ +/hi/roles-and-benefits/overview/ /hi/sps/introduction/ +/hi/sps/substreams-powered-subgraphs-faq/ /hi/sps/triggers-example/ /hi/sps/triggers/ -/hi/subgraphs/ /hi/substreams/ -/hi/sunrise/ /hi/supported-network-requirements/ /hi/tap/ /hi/tokenomics/ /it/ /it/404/ /it/about/ -/it/arbitrum/arbitrum-faq/ -/it/arbitrum/l2-transfer-tools-faq/ -/it/arbitrum/l2-transfer-tools-guide/ +/it/archived/arbitrum/arbitrum-faq/ +/it/archived/arbitrum/l2-transfer-tools-faq/ +/it/archived/arbitrum/l2-transfer-tools-guide/ +/it/archived/sunrise/ /it/billing/ /it/chain-integration-overview/ +/it/contracts/ /it/cookbook/arweave/ /it/cookbook/avoid-eth-calls/ /it/cookbook/cosmos/ @@ -551,37 +553,32 @@ /it/cookbook/substreams-powered-subgraphs/ /it/cookbook/timeseries/ /it/cookbook/transfer-to-the-graph/ -/it/deploying/deploy-using-subgraph-studio/ -/it/deploying/multiple-networks/ -/it/deploying/subgraph-studio-faqs/ /it/developing/creating-a-subgraph/advanced/ /it/developing/creating-a-subgraph/assemblyscript-mappings/ +/it/developing/creating-a-subgraph/graph-ts/api/ +/it/developing/creating-a-subgraph/graph-ts/common-issues/ /it/developing/creating-a-subgraph/install-the-cli/ /it/developing/creating-a-subgraph/ql-schema/ /it/developing/creating-a-subgraph/starting-your-subgraph/ /it/developing/creating-a-subgraph/subgraph-manifest/ +/it/developing/creating-a-subgraph/unit-testing-framework/ +/it/developing/deploying/deploy-using-subgraph-studio/ +/it/developing/deploying/multiple-networks/ +/it/developing/deploying/subgraph-studio-faqs/ /it/developing/developer-faqs/ -/it/developing/graph-ts/api/ -/it/developing/graph-ts/common-issues/ -/it/developing/substreams-powered-subgraphs-faq/ +/it/developing/developing/ +/it/developing/managing/delete-a-subgraph/ +/it/developing/managing/transfer-a-subgraph/ +/it/developing/publishing/publishing-a-subgraph/ +/it/developing/subgraphs/ /it/developing/supported-networks/ -/it/developing/unit-testing-framework/ -/it/firehose/ +/it/explorer/ /it/glossary/ -/it/graphcast/ -/it/managing/delete-a-subgraph/ -/it/managing/transfer-a-subgraph/ -/it/network/benefits/ -/it/network/contracts/ -/it/network/curating/ -/it/network/delegating/ -/it/network/developing/ -/it/network/explorer/ -/it/network/indexing/ -/it/network/overview/ +/it/indexer-tooling/firehose/ +/it/indexer-tooling/graphcast/ +/it/indexer-tooling/operating-graph-node/ +/it/indexing/ /it/new-chain-integration/ -/it/operating-graph-node/ -/it/publishing/publishing-a-subgraph/ /it/querying/distributed-systems/ /it/querying/graphql-api/ /it/querying/managing-api-keys/ @@ -593,23 +590,28 @@ /it/quick-start/ /it/release-notes/assemblyscript-migration-guide/ /it/release-notes/graphql-validations-migration-guide/ +/it/roles-and-benefits/benefits/ +/it/roles-and-benefits/curating/ +/it/roles-and-benefits/delegating/ +/it/roles-and-benefits/overview/ /it/sps/introduction/ +/it/sps/substreams-powered-subgraphs-faq/ /it/sps/triggers-example/ /it/sps/triggers/ -/it/subgraphs/ /it/substreams/ -/it/sunrise/ /it/supported-network-requirements/ /it/tap/ /it/tokenomics/ /ja/ /ja/404/ /ja/about/ -/ja/arbitrum/arbitrum-faq/ -/ja/arbitrum/l2-transfer-tools-faq/ -/ja/arbitrum/l2-transfer-tools-guide/ +/ja/archived/arbitrum/arbitrum-faq/ +/ja/archived/arbitrum/l2-transfer-tools-faq/ +/ja/archived/arbitrum/l2-transfer-tools-guide/ +/ja/archived/sunrise/ /ja/billing/ /ja/chain-integration-overview/ +/ja/contracts/ /ja/cookbook/arweave/ /ja/cookbook/avoid-eth-calls/ /ja/cookbook/cosmos/ @@ -626,37 +628,32 @@ /ja/cookbook/substreams-powered-subgraphs/ /ja/cookbook/timeseries/ /ja/cookbook/transfer-to-the-graph/ -/ja/deploying/deploy-using-subgraph-studio/ -/ja/deploying/multiple-networks/ -/ja/deploying/subgraph-studio-faqs/ /ja/developing/creating-a-subgraph/advanced/ /ja/developing/creating-a-subgraph/assemblyscript-mappings/ +/ja/developing/creating-a-subgraph/graph-ts/api/ +/ja/developing/creating-a-subgraph/graph-ts/common-issues/ /ja/developing/creating-a-subgraph/install-the-cli/ /ja/developing/creating-a-subgraph/ql-schema/ /ja/developing/creating-a-subgraph/starting-your-subgraph/ /ja/developing/creating-a-subgraph/subgraph-manifest/ +/ja/developing/creating-a-subgraph/unit-testing-framework/ +/ja/developing/deploying/deploy-using-subgraph-studio/ +/ja/developing/deploying/multiple-networks/ +/ja/developing/deploying/subgraph-studio-faqs/ /ja/developing/developer-faqs/ -/ja/developing/graph-ts/api/ -/ja/developing/graph-ts/common-issues/ -/ja/developing/substreams-powered-subgraphs-faq/ +/ja/developing/developing/ +/ja/developing/managing/delete-a-subgraph/ +/ja/developing/managing/transfer-a-subgraph/ +/ja/developing/publishing/publishing-a-subgraph/ +/ja/developing/subgraphs/ /ja/developing/supported-networks/ -/ja/developing/unit-testing-framework/ -/ja/firehose/ +/ja/explorer/ /ja/glossary/ -/ja/graphcast/ -/ja/managing/delete-a-subgraph/ -/ja/managing/transfer-a-subgraph/ -/ja/network/benefits/ -/ja/network/contracts/ -/ja/network/curating/ -/ja/network/delegating/ -/ja/network/developing/ -/ja/network/explorer/ -/ja/network/indexing/ -/ja/network/overview/ +/ja/indexer-tooling/firehose/ +/ja/indexer-tooling/graphcast/ +/ja/indexer-tooling/operating-graph-node/ +/ja/indexing/ /ja/new-chain-integration/ -/ja/operating-graph-node/ -/ja/publishing/publishing-a-subgraph/ /ja/querying/distributed-systems/ /ja/querying/graphql-api/ /ja/querying/managing-api-keys/ @@ -668,21 +665,26 @@ /ja/quick-start/ /ja/release-notes/assemblyscript-migration-guide/ /ja/release-notes/graphql-validations-migration-guide/ +/ja/roles-and-benefits/benefits/ +/ja/roles-and-benefits/curating/ +/ja/roles-and-benefits/delegating/ +/ja/roles-and-benefits/overview/ /ja/sps/introduction/ +/ja/sps/substreams-powered-subgraphs-faq/ /ja/sps/triggers-example/ /ja/sps/triggers/ -/ja/subgraphs/ /ja/substreams/ -/ja/sunrise/ /ja/supported-network-requirements/ /ja/tap/ /ja/tokenomics/ /ko/about/ -/ko/arbitrum/arbitrum-faq/ -/ko/arbitrum/l2-transfer-tools-faq/ -/ko/arbitrum/l2-transfer-tools-guide/ +/ko/archived/arbitrum/arbitrum-faq/ +/ko/archived/arbitrum/l2-transfer-tools-faq/ +/ko/archived/arbitrum/l2-transfer-tools-guide/ +/ko/archived/sunrise/ /ko/billing/ /ko/chain-integration-overview/ +/ko/contracts/ /ko/cookbook/arweave/ /ko/cookbook/avoid-eth-calls/ /ko/cookbook/cosmos/ @@ -699,37 +701,32 @@ /ko/cookbook/substreams-powered-subgraphs/ /ko/cookbook/timeseries/ /ko/cookbook/transfer-to-the-graph/ -/ko/deploying/deploy-using-subgraph-studio/ -/ko/deploying/multiple-networks/ -/ko/deploying/subgraph-studio-faqs/ /ko/developing/creating-a-subgraph/advanced/ /ko/developing/creating-a-subgraph/assemblyscript-mappings/ +/ko/developing/creating-a-subgraph/graph-ts/api/ +/ko/developing/creating-a-subgraph/graph-ts/common-issues/ /ko/developing/creating-a-subgraph/install-the-cli/ /ko/developing/creating-a-subgraph/ql-schema/ /ko/developing/creating-a-subgraph/starting-your-subgraph/ /ko/developing/creating-a-subgraph/subgraph-manifest/ +/ko/developing/creating-a-subgraph/unit-testing-framework/ +/ko/developing/deploying/deploy-using-subgraph-studio/ +/ko/developing/deploying/multiple-networks/ +/ko/developing/deploying/subgraph-studio-faqs/ /ko/developing/developer-faqs/ -/ko/developing/graph-ts/api/ -/ko/developing/graph-ts/common-issues/ -/ko/developing/substreams-powered-subgraphs-faq/ +/ko/developing/developing/ +/ko/developing/managing/delete-a-subgraph/ +/ko/developing/managing/transfer-a-subgraph/ +/ko/developing/publishing/publishing-a-subgraph/ +/ko/developing/subgraphs/ /ko/developing/supported-networks/ -/ko/developing/unit-testing-framework/ -/ko/firehose/ +/ko/explorer/ /ko/glossary/ -/ko/graphcast/ -/ko/managing/delete-a-subgraph/ -/ko/managing/transfer-a-subgraph/ -/ko/network/benefits/ -/ko/network/contracts/ -/ko/network/curating/ -/ko/network/delegating/ -/ko/network/developing/ -/ko/network/explorer/ -/ko/network/indexing/ -/ko/network/overview/ +/ko/indexer-tooling/firehose/ +/ko/indexer-tooling/graphcast/ +/ko/indexer-tooling/operating-graph-node/ +/ko/indexing/ /ko/new-chain-integration/ -/ko/operating-graph-node/ -/ko/publishing/publishing-a-subgraph/ /ko/querying/distributed-systems/ /ko/querying/graphql-api/ /ko/querying/managing-api-keys/ @@ -741,23 +738,28 @@ /ko/quick-start/ /ko/release-notes/assemblyscript-migration-guide/ /ko/release-notes/graphql-validations-migration-guide/ +/ko/roles-and-benefits/benefits/ +/ko/roles-and-benefits/curating/ +/ko/roles-and-benefits/delegating/ +/ko/roles-and-benefits/overview/ /ko/sps/introduction/ +/ko/sps/substreams-powered-subgraphs-faq/ /ko/sps/triggers-example/ /ko/sps/triggers/ -/ko/subgraphs/ /ko/substreams/ -/ko/sunrise/ /ko/supported-network-requirements/ /ko/tap/ /ko/tokenomics/ /mr/ /mr/404/ /mr/about/ -/mr/arbitrum/arbitrum-faq/ -/mr/arbitrum/l2-transfer-tools-faq/ -/mr/arbitrum/l2-transfer-tools-guide/ +/mr/archived/arbitrum/arbitrum-faq/ +/mr/archived/arbitrum/l2-transfer-tools-faq/ +/mr/archived/arbitrum/l2-transfer-tools-guide/ +/mr/archived/sunrise/ /mr/billing/ /mr/chain-integration-overview/ +/mr/contracts/ /mr/cookbook/arweave/ /mr/cookbook/avoid-eth-calls/ /mr/cookbook/cosmos/ @@ -774,37 +776,32 @@ /mr/cookbook/substreams-powered-subgraphs/ /mr/cookbook/timeseries/ /mr/cookbook/transfer-to-the-graph/ -/mr/deploying/deploy-using-subgraph-studio/ -/mr/deploying/multiple-networks/ -/mr/deploying/subgraph-studio-faqs/ /mr/developing/creating-a-subgraph/advanced/ /mr/developing/creating-a-subgraph/assemblyscript-mappings/ +/mr/developing/creating-a-subgraph/graph-ts/api/ +/mr/developing/creating-a-subgraph/graph-ts/common-issues/ /mr/developing/creating-a-subgraph/install-the-cli/ /mr/developing/creating-a-subgraph/ql-schema/ /mr/developing/creating-a-subgraph/starting-your-subgraph/ /mr/developing/creating-a-subgraph/subgraph-manifest/ +/mr/developing/creating-a-subgraph/unit-testing-framework/ +/mr/developing/deploying/deploy-using-subgraph-studio/ +/mr/developing/deploying/multiple-networks/ +/mr/developing/deploying/subgraph-studio-faqs/ /mr/developing/developer-faqs/ -/mr/developing/graph-ts/api/ -/mr/developing/graph-ts/common-issues/ -/mr/developing/substreams-powered-subgraphs-faq/ +/mr/developing/developing/ +/mr/developing/managing/delete-a-subgraph/ +/mr/developing/managing/transfer-a-subgraph/ +/mr/developing/publishing/publishing-a-subgraph/ +/mr/developing/subgraphs/ /mr/developing/supported-networks/ -/mr/developing/unit-testing-framework/ -/mr/firehose/ +/mr/explorer/ /mr/glossary/ -/mr/graphcast/ -/mr/managing/delete-a-subgraph/ -/mr/managing/transfer-a-subgraph/ -/mr/network/benefits/ -/mr/network/contracts/ -/mr/network/curating/ -/mr/network/delegating/ -/mr/network/developing/ -/mr/network/explorer/ -/mr/network/indexing/ -/mr/network/overview/ +/mr/indexer-tooling/firehose/ +/mr/indexer-tooling/graphcast/ +/mr/indexer-tooling/operating-graph-node/ +/mr/indexing/ /mr/new-chain-integration/ -/mr/operating-graph-node/ -/mr/publishing/publishing-a-subgraph/ /mr/querying/distributed-systems/ /mr/querying/graphql-api/ /mr/querying/managing-api-keys/ @@ -816,21 +813,26 @@ /mr/quick-start/ /mr/release-notes/assemblyscript-migration-guide/ /mr/release-notes/graphql-validations-migration-guide/ +/mr/roles-and-benefits/benefits/ +/mr/roles-and-benefits/curating/ +/mr/roles-and-benefits/delegating/ +/mr/roles-and-benefits/overview/ /mr/sps/introduction/ +/mr/sps/substreams-powered-subgraphs-faq/ /mr/sps/triggers-example/ /mr/sps/triggers/ -/mr/subgraphs/ /mr/substreams/ -/mr/sunrise/ /mr/supported-network-requirements/ /mr/tap/ /mr/tokenomics/ /nl/about/ -/nl/arbitrum/arbitrum-faq/ -/nl/arbitrum/l2-transfer-tools-faq/ -/nl/arbitrum/l2-transfer-tools-guide/ +/nl/archived/arbitrum/arbitrum-faq/ +/nl/archived/arbitrum/l2-transfer-tools-faq/ +/nl/archived/arbitrum/l2-transfer-tools-guide/ +/nl/archived/sunrise/ /nl/billing/ /nl/chain-integration-overview/ +/nl/contracts/ /nl/cookbook/arweave/ /nl/cookbook/avoid-eth-calls/ /nl/cookbook/cosmos/ @@ -847,37 +849,32 @@ /nl/cookbook/substreams-powered-subgraphs/ /nl/cookbook/timeseries/ /nl/cookbook/transfer-to-the-graph/ -/nl/deploying/deploy-using-subgraph-studio/ -/nl/deploying/multiple-networks/ -/nl/deploying/subgraph-studio-faqs/ /nl/developing/creating-a-subgraph/advanced/ /nl/developing/creating-a-subgraph/assemblyscript-mappings/ +/nl/developing/creating-a-subgraph/graph-ts/api/ +/nl/developing/creating-a-subgraph/graph-ts/common-issues/ /nl/developing/creating-a-subgraph/install-the-cli/ /nl/developing/creating-a-subgraph/ql-schema/ /nl/developing/creating-a-subgraph/starting-your-subgraph/ /nl/developing/creating-a-subgraph/subgraph-manifest/ +/nl/developing/creating-a-subgraph/unit-testing-framework/ +/nl/developing/deploying/deploy-using-subgraph-studio/ +/nl/developing/deploying/multiple-networks/ +/nl/developing/deploying/subgraph-studio-faqs/ /nl/developing/developer-faqs/ -/nl/developing/graph-ts/api/ -/nl/developing/graph-ts/common-issues/ -/nl/developing/substreams-powered-subgraphs-faq/ +/nl/developing/developing/ +/nl/developing/managing/delete-a-subgraph/ +/nl/developing/managing/transfer-a-subgraph/ +/nl/developing/publishing/publishing-a-subgraph/ +/nl/developing/subgraphs/ /nl/developing/supported-networks/ -/nl/developing/unit-testing-framework/ -/nl/firehose/ +/nl/explorer/ /nl/glossary/ -/nl/graphcast/ -/nl/managing/delete-a-subgraph/ -/nl/managing/transfer-a-subgraph/ -/nl/network/benefits/ -/nl/network/contracts/ -/nl/network/curating/ -/nl/network/delegating/ -/nl/network/developing/ -/nl/network/explorer/ -/nl/network/indexing/ -/nl/network/overview/ +/nl/indexer-tooling/firehose/ +/nl/indexer-tooling/graphcast/ +/nl/indexer-tooling/operating-graph-node/ +/nl/indexing/ /nl/new-chain-integration/ -/nl/operating-graph-node/ -/nl/publishing/publishing-a-subgraph/ /nl/querying/distributed-systems/ /nl/querying/graphql-api/ /nl/querying/managing-api-keys/ @@ -889,21 +886,26 @@ /nl/quick-start/ /nl/release-notes/assemblyscript-migration-guide/ /nl/release-notes/graphql-validations-migration-guide/ +/nl/roles-and-benefits/benefits/ +/nl/roles-and-benefits/curating/ +/nl/roles-and-benefits/delegating/ +/nl/roles-and-benefits/overview/ /nl/sps/introduction/ +/nl/sps/substreams-powered-subgraphs-faq/ /nl/sps/triggers-example/ /nl/sps/triggers/ -/nl/subgraphs/ /nl/substreams/ -/nl/sunrise/ /nl/supported-network-requirements/ /nl/tap/ /nl/tokenomics/ /pl/about/ -/pl/arbitrum/arbitrum-faq/ -/pl/arbitrum/l2-transfer-tools-faq/ -/pl/arbitrum/l2-transfer-tools-guide/ +/pl/archived/arbitrum/arbitrum-faq/ +/pl/archived/arbitrum/l2-transfer-tools-faq/ +/pl/archived/arbitrum/l2-transfer-tools-guide/ +/pl/archived/sunrise/ /pl/billing/ /pl/chain-integration-overview/ +/pl/contracts/ /pl/cookbook/arweave/ /pl/cookbook/avoid-eth-calls/ /pl/cookbook/cosmos/ @@ -920,37 +922,32 @@ /pl/cookbook/substreams-powered-subgraphs/ /pl/cookbook/timeseries/ /pl/cookbook/transfer-to-the-graph/ -/pl/deploying/deploy-using-subgraph-studio/ -/pl/deploying/multiple-networks/ -/pl/deploying/subgraph-studio-faqs/ /pl/developing/creating-a-subgraph/advanced/ /pl/developing/creating-a-subgraph/assemblyscript-mappings/ +/pl/developing/creating-a-subgraph/graph-ts/api/ +/pl/developing/creating-a-subgraph/graph-ts/common-issues/ /pl/developing/creating-a-subgraph/install-the-cli/ /pl/developing/creating-a-subgraph/ql-schema/ /pl/developing/creating-a-subgraph/starting-your-subgraph/ /pl/developing/creating-a-subgraph/subgraph-manifest/ +/pl/developing/creating-a-subgraph/unit-testing-framework/ +/pl/developing/deploying/deploy-using-subgraph-studio/ +/pl/developing/deploying/multiple-networks/ +/pl/developing/deploying/subgraph-studio-faqs/ /pl/developing/developer-faqs/ -/pl/developing/graph-ts/api/ -/pl/developing/graph-ts/common-issues/ -/pl/developing/substreams-powered-subgraphs-faq/ +/pl/developing/developing/ +/pl/developing/managing/delete-a-subgraph/ +/pl/developing/managing/transfer-a-subgraph/ +/pl/developing/publishing/publishing-a-subgraph/ +/pl/developing/subgraphs/ /pl/developing/supported-networks/ -/pl/developing/unit-testing-framework/ -/pl/firehose/ +/pl/explorer/ /pl/glossary/ -/pl/graphcast/ -/pl/managing/delete-a-subgraph/ -/pl/managing/transfer-a-subgraph/ -/pl/network/benefits/ -/pl/network/contracts/ -/pl/network/curating/ -/pl/network/delegating/ -/pl/network/developing/ -/pl/network/explorer/ -/pl/network/indexing/ -/pl/network/overview/ +/pl/indexer-tooling/firehose/ +/pl/indexer-tooling/graphcast/ +/pl/indexer-tooling/operating-graph-node/ +/pl/indexing/ /pl/new-chain-integration/ -/pl/operating-graph-node/ -/pl/publishing/publishing-a-subgraph/ /pl/querying/distributed-systems/ /pl/querying/graphql-api/ /pl/querying/managing-api-keys/ @@ -962,23 +959,28 @@ /pl/quick-start/ /pl/release-notes/assemblyscript-migration-guide/ /pl/release-notes/graphql-validations-migration-guide/ +/pl/roles-and-benefits/benefits/ +/pl/roles-and-benefits/curating/ +/pl/roles-and-benefits/delegating/ +/pl/roles-and-benefits/overview/ /pl/sps/introduction/ +/pl/sps/substreams-powered-subgraphs-faq/ /pl/sps/triggers-example/ /pl/sps/triggers/ -/pl/subgraphs/ /pl/substreams/ -/pl/sunrise/ /pl/supported-network-requirements/ /pl/tap/ /pl/tokenomics/ /pt/ /pt/404/ /pt/about/ -/pt/arbitrum/arbitrum-faq/ -/pt/arbitrum/l2-transfer-tools-faq/ -/pt/arbitrum/l2-transfer-tools-guide/ +/pt/archived/arbitrum/arbitrum-faq/ +/pt/archived/arbitrum/l2-transfer-tools-faq/ +/pt/archived/arbitrum/l2-transfer-tools-guide/ +/pt/archived/sunrise/ /pt/billing/ /pt/chain-integration-overview/ +/pt/contracts/ /pt/cookbook/arweave/ /pt/cookbook/avoid-eth-calls/ /pt/cookbook/cosmos/ @@ -995,37 +997,32 @@ /pt/cookbook/substreams-powered-subgraphs/ /pt/cookbook/timeseries/ /pt/cookbook/transfer-to-the-graph/ -/pt/deploying/deploy-using-subgraph-studio/ -/pt/deploying/multiple-networks/ -/pt/deploying/subgraph-studio-faqs/ /pt/developing/creating-a-subgraph/advanced/ /pt/developing/creating-a-subgraph/assemblyscript-mappings/ +/pt/developing/creating-a-subgraph/graph-ts/api/ +/pt/developing/creating-a-subgraph/graph-ts/common-issues/ /pt/developing/creating-a-subgraph/install-the-cli/ /pt/developing/creating-a-subgraph/ql-schema/ /pt/developing/creating-a-subgraph/starting-your-subgraph/ /pt/developing/creating-a-subgraph/subgraph-manifest/ +/pt/developing/creating-a-subgraph/unit-testing-framework/ +/pt/developing/deploying/deploy-using-subgraph-studio/ +/pt/developing/deploying/multiple-networks/ +/pt/developing/deploying/subgraph-studio-faqs/ /pt/developing/developer-faqs/ -/pt/developing/graph-ts/api/ -/pt/developing/graph-ts/common-issues/ -/pt/developing/substreams-powered-subgraphs-faq/ +/pt/developing/developing/ +/pt/developing/managing/delete-a-subgraph/ +/pt/developing/managing/transfer-a-subgraph/ +/pt/developing/publishing/publishing-a-subgraph/ +/pt/developing/subgraphs/ /pt/developing/supported-networks/ -/pt/developing/unit-testing-framework/ -/pt/firehose/ +/pt/explorer/ /pt/glossary/ -/pt/graphcast/ -/pt/managing/delete-a-subgraph/ -/pt/managing/transfer-a-subgraph/ -/pt/network/benefits/ -/pt/network/contracts/ -/pt/network/curating/ -/pt/network/delegating/ -/pt/network/developing/ -/pt/network/explorer/ -/pt/network/indexing/ -/pt/network/overview/ +/pt/indexer-tooling/firehose/ +/pt/indexer-tooling/graphcast/ +/pt/indexer-tooling/operating-graph-node/ +/pt/indexing/ /pt/new-chain-integration/ -/pt/operating-graph-node/ -/pt/publishing/publishing-a-subgraph/ /pt/querying/distributed-systems/ /pt/querying/graphql-api/ /pt/querying/managing-api-keys/ @@ -1037,21 +1034,26 @@ /pt/quick-start/ /pt/release-notes/assemblyscript-migration-guide/ /pt/release-notes/graphql-validations-migration-guide/ +/pt/roles-and-benefits/benefits/ +/pt/roles-and-benefits/curating/ +/pt/roles-and-benefits/delegating/ +/pt/roles-and-benefits/overview/ /pt/sps/introduction/ +/pt/sps/substreams-powered-subgraphs-faq/ /pt/sps/triggers-example/ /pt/sps/triggers/ -/pt/subgraphs/ /pt/substreams/ -/pt/sunrise/ /pt/supported-network-requirements/ /pt/tap/ /pt/tokenomics/ /ro/about/ -/ro/arbitrum/arbitrum-faq/ -/ro/arbitrum/l2-transfer-tools-faq/ -/ro/arbitrum/l2-transfer-tools-guide/ +/ro/archived/arbitrum/arbitrum-faq/ +/ro/archived/arbitrum/l2-transfer-tools-faq/ +/ro/archived/arbitrum/l2-transfer-tools-guide/ +/ro/archived/sunrise/ /ro/billing/ /ro/chain-integration-overview/ +/ro/contracts/ /ro/cookbook/arweave/ /ro/cookbook/avoid-eth-calls/ /ro/cookbook/cosmos/ @@ -1068,37 +1070,32 @@ /ro/cookbook/substreams-powered-subgraphs/ /ro/cookbook/timeseries/ /ro/cookbook/transfer-to-the-graph/ -/ro/deploying/deploy-using-subgraph-studio/ -/ro/deploying/multiple-networks/ -/ro/deploying/subgraph-studio-faqs/ /ro/developing/creating-a-subgraph/advanced/ /ro/developing/creating-a-subgraph/assemblyscript-mappings/ +/ro/developing/creating-a-subgraph/graph-ts/api/ +/ro/developing/creating-a-subgraph/graph-ts/common-issues/ /ro/developing/creating-a-subgraph/install-the-cli/ /ro/developing/creating-a-subgraph/ql-schema/ /ro/developing/creating-a-subgraph/starting-your-subgraph/ /ro/developing/creating-a-subgraph/subgraph-manifest/ +/ro/developing/creating-a-subgraph/unit-testing-framework/ +/ro/developing/deploying/deploy-using-subgraph-studio/ +/ro/developing/deploying/multiple-networks/ +/ro/developing/deploying/subgraph-studio-faqs/ /ro/developing/developer-faqs/ -/ro/developing/graph-ts/api/ -/ro/developing/graph-ts/common-issues/ -/ro/developing/substreams-powered-subgraphs-faq/ +/ro/developing/developing/ +/ro/developing/managing/delete-a-subgraph/ +/ro/developing/managing/transfer-a-subgraph/ +/ro/developing/publishing/publishing-a-subgraph/ +/ro/developing/subgraphs/ /ro/developing/supported-networks/ -/ro/developing/unit-testing-framework/ -/ro/firehose/ +/ro/explorer/ /ro/glossary/ -/ro/graphcast/ -/ro/managing/delete-a-subgraph/ -/ro/managing/transfer-a-subgraph/ -/ro/network/benefits/ -/ro/network/contracts/ -/ro/network/curating/ -/ro/network/delegating/ -/ro/network/developing/ -/ro/network/explorer/ -/ro/network/indexing/ -/ro/network/overview/ +/ro/indexer-tooling/firehose/ +/ro/indexer-tooling/graphcast/ +/ro/indexer-tooling/operating-graph-node/ +/ro/indexing/ /ro/new-chain-integration/ -/ro/operating-graph-node/ -/ro/publishing/publishing-a-subgraph/ /ro/querying/distributed-systems/ /ro/querying/graphql-api/ /ro/querying/managing-api-keys/ @@ -1110,23 +1107,28 @@ /ro/quick-start/ /ro/release-notes/assemblyscript-migration-guide/ /ro/release-notes/graphql-validations-migration-guide/ +/ro/roles-and-benefits/benefits/ +/ro/roles-and-benefits/curating/ +/ro/roles-and-benefits/delegating/ +/ro/roles-and-benefits/overview/ /ro/sps/introduction/ +/ro/sps/substreams-powered-subgraphs-faq/ /ro/sps/triggers-example/ /ro/sps/triggers/ -/ro/subgraphs/ /ro/substreams/ -/ro/sunrise/ /ro/supported-network-requirements/ /ro/tap/ /ro/tokenomics/ /ru/ /ru/404/ /ru/about/ -/ru/arbitrum/arbitrum-faq/ -/ru/arbitrum/l2-transfer-tools-faq/ -/ru/arbitrum/l2-transfer-tools-guide/ +/ru/archived/arbitrum/arbitrum-faq/ +/ru/archived/arbitrum/l2-transfer-tools-faq/ +/ru/archived/arbitrum/l2-transfer-tools-guide/ +/ru/archived/sunrise/ /ru/billing/ /ru/chain-integration-overview/ +/ru/contracts/ /ru/cookbook/arweave/ /ru/cookbook/avoid-eth-calls/ /ru/cookbook/cosmos/ @@ -1143,37 +1145,32 @@ /ru/cookbook/substreams-powered-subgraphs/ /ru/cookbook/timeseries/ /ru/cookbook/transfer-to-the-graph/ -/ru/deploying/deploy-using-subgraph-studio/ -/ru/deploying/multiple-networks/ -/ru/deploying/subgraph-studio-faqs/ /ru/developing/creating-a-subgraph/advanced/ /ru/developing/creating-a-subgraph/assemblyscript-mappings/ +/ru/developing/creating-a-subgraph/graph-ts/api/ +/ru/developing/creating-a-subgraph/graph-ts/common-issues/ /ru/developing/creating-a-subgraph/install-the-cli/ /ru/developing/creating-a-subgraph/ql-schema/ /ru/developing/creating-a-subgraph/starting-your-subgraph/ /ru/developing/creating-a-subgraph/subgraph-manifest/ +/ru/developing/creating-a-subgraph/unit-testing-framework/ +/ru/developing/deploying/deploy-using-subgraph-studio/ +/ru/developing/deploying/multiple-networks/ +/ru/developing/deploying/subgraph-studio-faqs/ /ru/developing/developer-faqs/ -/ru/developing/graph-ts/api/ -/ru/developing/graph-ts/common-issues/ -/ru/developing/substreams-powered-subgraphs-faq/ +/ru/developing/developing/ +/ru/developing/managing/delete-a-subgraph/ +/ru/developing/managing/transfer-a-subgraph/ +/ru/developing/publishing/publishing-a-subgraph/ +/ru/developing/subgraphs/ /ru/developing/supported-networks/ -/ru/developing/unit-testing-framework/ -/ru/firehose/ +/ru/explorer/ /ru/glossary/ -/ru/graphcast/ -/ru/managing/delete-a-subgraph/ -/ru/managing/transfer-a-subgraph/ -/ru/network/benefits/ -/ru/network/contracts/ -/ru/network/curating/ -/ru/network/delegating/ -/ru/network/developing/ -/ru/network/explorer/ -/ru/network/indexing/ -/ru/network/overview/ +/ru/indexer-tooling/firehose/ +/ru/indexer-tooling/graphcast/ +/ru/indexer-tooling/operating-graph-node/ +/ru/indexing/ /ru/new-chain-integration/ -/ru/operating-graph-node/ -/ru/publishing/publishing-a-subgraph/ /ru/querying/distributed-systems/ /ru/querying/graphql-api/ /ru/querying/managing-api-keys/ @@ -1185,23 +1182,28 @@ /ru/quick-start/ /ru/release-notes/assemblyscript-migration-guide/ /ru/release-notes/graphql-validations-migration-guide/ +/ru/roles-and-benefits/benefits/ +/ru/roles-and-benefits/curating/ +/ru/roles-and-benefits/delegating/ +/ru/roles-and-benefits/overview/ /ru/sps/introduction/ +/ru/sps/substreams-powered-subgraphs-faq/ /ru/sps/triggers-example/ /ru/sps/triggers/ -/ru/subgraphs/ /ru/substreams/ -/ru/sunrise/ /ru/supported-network-requirements/ /ru/tap/ /ru/tokenomics/ /sv/ /sv/404/ /sv/about/ -/sv/arbitrum/arbitrum-faq/ -/sv/arbitrum/l2-transfer-tools-faq/ -/sv/arbitrum/l2-transfer-tools-guide/ +/sv/archived/arbitrum/arbitrum-faq/ +/sv/archived/arbitrum/l2-transfer-tools-faq/ +/sv/archived/arbitrum/l2-transfer-tools-guide/ +/sv/archived/sunrise/ /sv/billing/ /sv/chain-integration-overview/ +/sv/contracts/ /sv/cookbook/arweave/ /sv/cookbook/avoid-eth-calls/ /sv/cookbook/cosmos/ @@ -1218,37 +1220,32 @@ /sv/cookbook/substreams-powered-subgraphs/ /sv/cookbook/timeseries/ /sv/cookbook/transfer-to-the-graph/ -/sv/deploying/deploy-using-subgraph-studio/ -/sv/deploying/multiple-networks/ -/sv/deploying/subgraph-studio-faqs/ /sv/developing/creating-a-subgraph/advanced/ /sv/developing/creating-a-subgraph/assemblyscript-mappings/ +/sv/developing/creating-a-subgraph/graph-ts/api/ +/sv/developing/creating-a-subgraph/graph-ts/common-issues/ /sv/developing/creating-a-subgraph/install-the-cli/ /sv/developing/creating-a-subgraph/ql-schema/ /sv/developing/creating-a-subgraph/starting-your-subgraph/ /sv/developing/creating-a-subgraph/subgraph-manifest/ +/sv/developing/creating-a-subgraph/unit-testing-framework/ +/sv/developing/deploying/deploy-using-subgraph-studio/ +/sv/developing/deploying/multiple-networks/ +/sv/developing/deploying/subgraph-studio-faqs/ /sv/developing/developer-faqs/ -/sv/developing/graph-ts/api/ -/sv/developing/graph-ts/common-issues/ -/sv/developing/substreams-powered-subgraphs-faq/ +/sv/developing/developing/ +/sv/developing/managing/delete-a-subgraph/ +/sv/developing/managing/transfer-a-subgraph/ +/sv/developing/publishing/publishing-a-subgraph/ +/sv/developing/subgraphs/ /sv/developing/supported-networks/ -/sv/developing/unit-testing-framework/ -/sv/firehose/ +/sv/explorer/ /sv/glossary/ -/sv/graphcast/ -/sv/managing/delete-a-subgraph/ -/sv/managing/transfer-a-subgraph/ -/sv/network/benefits/ -/sv/network/contracts/ -/sv/network/curating/ -/sv/network/delegating/ -/sv/network/developing/ -/sv/network/explorer/ -/sv/network/indexing/ -/sv/network/overview/ +/sv/indexer-tooling/firehose/ +/sv/indexer-tooling/graphcast/ +/sv/indexer-tooling/operating-graph-node/ +/sv/indexing/ /sv/new-chain-integration/ -/sv/operating-graph-node/ -/sv/publishing/publishing-a-subgraph/ /sv/querying/distributed-systems/ /sv/querying/graphql-api/ /sv/querying/managing-api-keys/ @@ -1260,21 +1257,26 @@ /sv/quick-start/ /sv/release-notes/assemblyscript-migration-guide/ /sv/release-notes/graphql-validations-migration-guide/ +/sv/roles-and-benefits/benefits/ +/sv/roles-and-benefits/curating/ +/sv/roles-and-benefits/delegating/ +/sv/roles-and-benefits/overview/ /sv/sps/introduction/ +/sv/sps/substreams-powered-subgraphs-faq/ /sv/sps/triggers-example/ /sv/sps/triggers/ -/sv/subgraphs/ /sv/substreams/ -/sv/sunrise/ /sv/supported-network-requirements/ /sv/tap/ /sv/tokenomics/ /sw/about/ -/sw/arbitrum/arbitrum-faq/ -/sw/arbitrum/l2-transfer-tools-faq/ -/sw/arbitrum/l2-transfer-tools-guide/ +/sw/archived/arbitrum/arbitrum-faq/ +/sw/archived/arbitrum/l2-transfer-tools-faq/ +/sw/archived/arbitrum/l2-transfer-tools-guide/ +/sw/archived/sunrise/ /sw/billing/ /sw/chain-integration-overview/ +/sw/contracts/ /sw/cookbook/arweave/ /sw/cookbook/avoid-eth-calls/ /sw/cookbook/cosmos/ @@ -1291,37 +1293,32 @@ /sw/cookbook/substreams-powered-subgraphs/ /sw/cookbook/timeseries/ /sw/cookbook/transfer-to-the-graph/ -/sw/deploying/deploy-using-subgraph-studio/ -/sw/deploying/multiple-networks/ -/sw/deploying/subgraph-studio-faqs/ /sw/developing/creating-a-subgraph/advanced/ /sw/developing/creating-a-subgraph/assemblyscript-mappings/ +/sw/developing/creating-a-subgraph/graph-ts/api/ +/sw/developing/creating-a-subgraph/graph-ts/common-issues/ /sw/developing/creating-a-subgraph/install-the-cli/ /sw/developing/creating-a-subgraph/ql-schema/ /sw/developing/creating-a-subgraph/starting-your-subgraph/ /sw/developing/creating-a-subgraph/subgraph-manifest/ +/sw/developing/creating-a-subgraph/unit-testing-framework/ +/sw/developing/deploying/deploy-using-subgraph-studio/ +/sw/developing/deploying/multiple-networks/ +/sw/developing/deploying/subgraph-studio-faqs/ /sw/developing/developer-faqs/ -/sw/developing/graph-ts/api/ -/sw/developing/graph-ts/common-issues/ -/sw/developing/substreams-powered-subgraphs-faq/ +/sw/developing/developing/ +/sw/developing/managing/delete-a-subgraph/ +/sw/developing/managing/transfer-a-subgraph/ +/sw/developing/publishing/publishing-a-subgraph/ +/sw/developing/subgraphs/ /sw/developing/supported-networks/ -/sw/developing/unit-testing-framework/ -/sw/firehose/ +/sw/explorer/ /sw/glossary/ -/sw/graphcast/ -/sw/managing/delete-a-subgraph/ -/sw/managing/transfer-a-subgraph/ -/sw/network/benefits/ -/sw/network/contracts/ -/sw/network/curating/ -/sw/network/delegating/ -/sw/network/developing/ -/sw/network/explorer/ -/sw/network/indexing/ -/sw/network/overview/ +/sw/indexer-tooling/firehose/ +/sw/indexer-tooling/graphcast/ +/sw/indexer-tooling/operating-graph-node/ +/sw/indexing/ /sw/new-chain-integration/ -/sw/operating-graph-node/ -/sw/publishing/publishing-a-subgraph/ /sw/querying/distributed-systems/ /sw/querying/graphql-api/ /sw/querying/managing-api-keys/ @@ -1333,23 +1330,28 @@ /sw/quick-start/ /sw/release-notes/assemblyscript-migration-guide/ /sw/release-notes/graphql-validations-migration-guide/ +/sw/roles-and-benefits/benefits/ +/sw/roles-and-benefits/curating/ +/sw/roles-and-benefits/delegating/ +/sw/roles-and-benefits/overview/ /sw/sps/introduction/ +/sw/sps/substreams-powered-subgraphs-faq/ /sw/sps/triggers-example/ /sw/sps/triggers/ -/sw/subgraphs/ /sw/substreams/ -/sw/sunrise/ /sw/supported-network-requirements/ /sw/tap/ /sw/tokenomics/ /tr/ /tr/404/ /tr/about/ -/tr/arbitrum/arbitrum-faq/ -/tr/arbitrum/l2-transfer-tools-faq/ -/tr/arbitrum/l2-transfer-tools-guide/ +/tr/archived/arbitrum/arbitrum-faq/ +/tr/archived/arbitrum/l2-transfer-tools-faq/ +/tr/archived/arbitrum/l2-transfer-tools-guide/ +/tr/archived/sunrise/ /tr/billing/ /tr/chain-integration-overview/ +/tr/contracts/ /tr/cookbook/arweave/ /tr/cookbook/avoid-eth-calls/ /tr/cookbook/cosmos/ @@ -1366,37 +1368,32 @@ /tr/cookbook/substreams-powered-subgraphs/ /tr/cookbook/timeseries/ /tr/cookbook/transfer-to-the-graph/ -/tr/deploying/deploy-using-subgraph-studio/ -/tr/deploying/multiple-networks/ -/tr/deploying/subgraph-studio-faqs/ /tr/developing/creating-a-subgraph/advanced/ /tr/developing/creating-a-subgraph/assemblyscript-mappings/ +/tr/developing/creating-a-subgraph/graph-ts/api/ +/tr/developing/creating-a-subgraph/graph-ts/common-issues/ /tr/developing/creating-a-subgraph/install-the-cli/ /tr/developing/creating-a-subgraph/ql-schema/ /tr/developing/creating-a-subgraph/starting-your-subgraph/ /tr/developing/creating-a-subgraph/subgraph-manifest/ +/tr/developing/creating-a-subgraph/unit-testing-framework/ +/tr/developing/deploying/deploy-using-subgraph-studio/ +/tr/developing/deploying/multiple-networks/ +/tr/developing/deploying/subgraph-studio-faqs/ /tr/developing/developer-faqs/ -/tr/developing/graph-ts/api/ -/tr/developing/graph-ts/common-issues/ -/tr/developing/substreams-powered-subgraphs-faq/ +/tr/developing/developing/ +/tr/developing/managing/delete-a-subgraph/ +/tr/developing/managing/transfer-a-subgraph/ +/tr/developing/publishing/publishing-a-subgraph/ +/tr/developing/subgraphs/ /tr/developing/supported-networks/ -/tr/developing/unit-testing-framework/ -/tr/firehose/ +/tr/explorer/ /tr/glossary/ -/tr/graphcast/ -/tr/managing/delete-a-subgraph/ -/tr/managing/transfer-a-subgraph/ -/tr/network/benefits/ -/tr/network/contracts/ -/tr/network/curating/ -/tr/network/delegating/ -/tr/network/developing/ -/tr/network/explorer/ -/tr/network/indexing/ -/tr/network/overview/ +/tr/indexer-tooling/firehose/ +/tr/indexer-tooling/graphcast/ +/tr/indexer-tooling/operating-graph-node/ +/tr/indexing/ /tr/new-chain-integration/ -/tr/operating-graph-node/ -/tr/publishing/publishing-a-subgraph/ /tr/querying/distributed-systems/ /tr/querying/graphql-api/ /tr/querying/managing-api-keys/ @@ -1408,21 +1405,26 @@ /tr/quick-start/ /tr/release-notes/assemblyscript-migration-guide/ /tr/release-notes/graphql-validations-migration-guide/ +/tr/roles-and-benefits/benefits/ +/tr/roles-and-benefits/curating/ +/tr/roles-and-benefits/delegating/ +/tr/roles-and-benefits/overview/ /tr/sps/introduction/ +/tr/sps/substreams-powered-subgraphs-faq/ /tr/sps/triggers-example/ /tr/sps/triggers/ -/tr/subgraphs/ /tr/substreams/ -/tr/sunrise/ /tr/supported-network-requirements/ /tr/tap/ /tr/tokenomics/ /uk/about/ -/uk/arbitrum/arbitrum-faq/ -/uk/arbitrum/l2-transfer-tools-faq/ -/uk/arbitrum/l2-transfer-tools-guide/ +/uk/archived/arbitrum/arbitrum-faq/ +/uk/archived/arbitrum/l2-transfer-tools-faq/ +/uk/archived/arbitrum/l2-transfer-tools-guide/ +/uk/archived/sunrise/ /uk/billing/ /uk/chain-integration-overview/ +/uk/contracts/ /uk/cookbook/arweave/ /uk/cookbook/avoid-eth-calls/ /uk/cookbook/cosmos/ @@ -1439,37 +1441,32 @@ /uk/cookbook/substreams-powered-subgraphs/ /uk/cookbook/timeseries/ /uk/cookbook/transfer-to-the-graph/ -/uk/deploying/deploy-using-subgraph-studio/ -/uk/deploying/multiple-networks/ -/uk/deploying/subgraph-studio-faqs/ /uk/developing/creating-a-subgraph/advanced/ /uk/developing/creating-a-subgraph/assemblyscript-mappings/ +/uk/developing/creating-a-subgraph/graph-ts/api/ +/uk/developing/creating-a-subgraph/graph-ts/common-issues/ /uk/developing/creating-a-subgraph/install-the-cli/ /uk/developing/creating-a-subgraph/ql-schema/ /uk/developing/creating-a-subgraph/starting-your-subgraph/ /uk/developing/creating-a-subgraph/subgraph-manifest/ +/uk/developing/creating-a-subgraph/unit-testing-framework/ +/uk/developing/deploying/deploy-using-subgraph-studio/ +/uk/developing/deploying/multiple-networks/ +/uk/developing/deploying/subgraph-studio-faqs/ /uk/developing/developer-faqs/ -/uk/developing/graph-ts/api/ -/uk/developing/graph-ts/common-issues/ -/uk/developing/substreams-powered-subgraphs-faq/ +/uk/developing/developing/ +/uk/developing/managing/delete-a-subgraph/ +/uk/developing/managing/transfer-a-subgraph/ +/uk/developing/publishing/publishing-a-subgraph/ +/uk/developing/subgraphs/ /uk/developing/supported-networks/ -/uk/developing/unit-testing-framework/ -/uk/firehose/ +/uk/explorer/ /uk/glossary/ -/uk/graphcast/ -/uk/managing/delete-a-subgraph/ -/uk/managing/transfer-a-subgraph/ -/uk/network/benefits/ -/uk/network/contracts/ -/uk/network/curating/ -/uk/network/delegating/ -/uk/network/developing/ -/uk/network/explorer/ -/uk/network/indexing/ -/uk/network/overview/ +/uk/indexer-tooling/firehose/ +/uk/indexer-tooling/graphcast/ +/uk/indexer-tooling/operating-graph-node/ +/uk/indexing/ /uk/new-chain-integration/ -/uk/operating-graph-node/ -/uk/publishing/publishing-a-subgraph/ /uk/querying/distributed-systems/ /uk/querying/graphql-api/ /uk/querying/managing-api-keys/ @@ -1481,23 +1478,28 @@ /uk/quick-start/ /uk/release-notes/assemblyscript-migration-guide/ /uk/release-notes/graphql-validations-migration-guide/ +/uk/roles-and-benefits/benefits/ +/uk/roles-and-benefits/curating/ +/uk/roles-and-benefits/delegating/ +/uk/roles-and-benefits/overview/ /uk/sps/introduction/ +/uk/sps/substreams-powered-subgraphs-faq/ /uk/sps/triggers-example/ /uk/sps/triggers/ -/uk/subgraphs/ /uk/substreams/ -/uk/sunrise/ /uk/supported-network-requirements/ /uk/tap/ /uk/tokenomics/ /ur/ /ur/404/ /ur/about/ -/ur/arbitrum/arbitrum-faq/ -/ur/arbitrum/l2-transfer-tools-faq/ -/ur/arbitrum/l2-transfer-tools-guide/ +/ur/archived/arbitrum/arbitrum-faq/ +/ur/archived/arbitrum/l2-transfer-tools-faq/ +/ur/archived/arbitrum/l2-transfer-tools-guide/ +/ur/archived/sunrise/ /ur/billing/ /ur/chain-integration-overview/ +/ur/contracts/ /ur/cookbook/arweave/ /ur/cookbook/avoid-eth-calls/ /ur/cookbook/cosmos/ @@ -1514,37 +1516,32 @@ /ur/cookbook/substreams-powered-subgraphs/ /ur/cookbook/timeseries/ /ur/cookbook/transfer-to-the-graph/ -/ur/deploying/deploy-using-subgraph-studio/ -/ur/deploying/multiple-networks/ -/ur/deploying/subgraph-studio-faqs/ /ur/developing/creating-a-subgraph/advanced/ /ur/developing/creating-a-subgraph/assemblyscript-mappings/ +/ur/developing/creating-a-subgraph/graph-ts/api/ +/ur/developing/creating-a-subgraph/graph-ts/common-issues/ /ur/developing/creating-a-subgraph/install-the-cli/ /ur/developing/creating-a-subgraph/ql-schema/ /ur/developing/creating-a-subgraph/starting-your-subgraph/ /ur/developing/creating-a-subgraph/subgraph-manifest/ +/ur/developing/creating-a-subgraph/unit-testing-framework/ +/ur/developing/deploying/deploy-using-subgraph-studio/ +/ur/developing/deploying/multiple-networks/ +/ur/developing/deploying/subgraph-studio-faqs/ /ur/developing/developer-faqs/ -/ur/developing/graph-ts/api/ -/ur/developing/graph-ts/common-issues/ -/ur/developing/substreams-powered-subgraphs-faq/ +/ur/developing/developing/ +/ur/developing/managing/delete-a-subgraph/ +/ur/developing/managing/transfer-a-subgraph/ +/ur/developing/publishing/publishing-a-subgraph/ +/ur/developing/subgraphs/ /ur/developing/supported-networks/ -/ur/developing/unit-testing-framework/ -/ur/firehose/ +/ur/explorer/ /ur/glossary/ -/ur/graphcast/ -/ur/managing/delete-a-subgraph/ -/ur/managing/transfer-a-subgraph/ -/ur/network/benefits/ -/ur/network/contracts/ -/ur/network/curating/ -/ur/network/delegating/ -/ur/network/developing/ -/ur/network/explorer/ -/ur/network/indexing/ -/ur/network/overview/ +/ur/indexer-tooling/firehose/ +/ur/indexer-tooling/graphcast/ +/ur/indexer-tooling/operating-graph-node/ +/ur/indexing/ /ur/new-chain-integration/ -/ur/operating-graph-node/ -/ur/publishing/publishing-a-subgraph/ /ur/querying/distributed-systems/ /ur/querying/graphql-api/ /ur/querying/managing-api-keys/ @@ -1556,21 +1553,26 @@ /ur/quick-start/ /ur/release-notes/assemblyscript-migration-guide/ /ur/release-notes/graphql-validations-migration-guide/ +/ur/roles-and-benefits/benefits/ +/ur/roles-and-benefits/curating/ +/ur/roles-and-benefits/delegating/ +/ur/roles-and-benefits/overview/ /ur/sps/introduction/ +/ur/sps/substreams-powered-subgraphs-faq/ /ur/sps/triggers-example/ /ur/sps/triggers/ -/ur/subgraphs/ /ur/substreams/ -/ur/sunrise/ /ur/supported-network-requirements/ /ur/tap/ /ur/tokenomics/ /vi/about/ -/vi/arbitrum/arbitrum-faq/ -/vi/arbitrum/l2-transfer-tools-faq/ -/vi/arbitrum/l2-transfer-tools-guide/ +/vi/archived/arbitrum/arbitrum-faq/ +/vi/archived/arbitrum/l2-transfer-tools-faq/ +/vi/archived/arbitrum/l2-transfer-tools-guide/ +/vi/archived/sunrise/ /vi/billing/ /vi/chain-integration-overview/ +/vi/contracts/ /vi/cookbook/arweave/ /vi/cookbook/avoid-eth-calls/ /vi/cookbook/cosmos/ @@ -1587,37 +1589,32 @@ /vi/cookbook/substreams-powered-subgraphs/ /vi/cookbook/timeseries/ /vi/cookbook/transfer-to-the-graph/ -/vi/deploying/deploy-using-subgraph-studio/ -/vi/deploying/multiple-networks/ -/vi/deploying/subgraph-studio-faqs/ /vi/developing/creating-a-subgraph/advanced/ /vi/developing/creating-a-subgraph/assemblyscript-mappings/ +/vi/developing/creating-a-subgraph/graph-ts/api/ +/vi/developing/creating-a-subgraph/graph-ts/common-issues/ /vi/developing/creating-a-subgraph/install-the-cli/ /vi/developing/creating-a-subgraph/ql-schema/ /vi/developing/creating-a-subgraph/starting-your-subgraph/ /vi/developing/creating-a-subgraph/subgraph-manifest/ +/vi/developing/creating-a-subgraph/unit-testing-framework/ +/vi/developing/deploying/deploy-using-subgraph-studio/ +/vi/developing/deploying/multiple-networks/ +/vi/developing/deploying/subgraph-studio-faqs/ /vi/developing/developer-faqs/ -/vi/developing/graph-ts/api/ -/vi/developing/graph-ts/common-issues/ -/vi/developing/substreams-powered-subgraphs-faq/ +/vi/developing/developing/ +/vi/developing/managing/delete-a-subgraph/ +/vi/developing/managing/transfer-a-subgraph/ +/vi/developing/publishing/publishing-a-subgraph/ +/vi/developing/subgraphs/ /vi/developing/supported-networks/ -/vi/developing/unit-testing-framework/ -/vi/firehose/ +/vi/explorer/ /vi/glossary/ -/vi/graphcast/ -/vi/managing/delete-a-subgraph/ -/vi/managing/transfer-a-subgraph/ -/vi/network/benefits/ -/vi/network/contracts/ -/vi/network/curating/ -/vi/network/delegating/ -/vi/network/developing/ -/vi/network/explorer/ -/vi/network/indexing/ -/vi/network/overview/ +/vi/indexer-tooling/firehose/ +/vi/indexer-tooling/graphcast/ +/vi/indexer-tooling/operating-graph-node/ +/vi/indexing/ /vi/new-chain-integration/ -/vi/operating-graph-node/ -/vi/publishing/publishing-a-subgraph/ /vi/querying/distributed-systems/ /vi/querying/graphql-api/ /vi/querying/managing-api-keys/ @@ -1629,23 +1626,28 @@ /vi/quick-start/ /vi/release-notes/assemblyscript-migration-guide/ /vi/release-notes/graphql-validations-migration-guide/ +/vi/roles-and-benefits/benefits/ +/vi/roles-and-benefits/curating/ +/vi/roles-and-benefits/delegating/ +/vi/roles-and-benefits/overview/ /vi/sps/introduction/ +/vi/sps/substreams-powered-subgraphs-faq/ /vi/sps/triggers-example/ /vi/sps/triggers/ -/vi/subgraphs/ /vi/substreams/ -/vi/sunrise/ /vi/supported-network-requirements/ /vi/tap/ /vi/tokenomics/ /zh/ /zh/404/ /zh/about/ -/zh/arbitrum/arbitrum-faq/ -/zh/arbitrum/l2-transfer-tools-faq/ -/zh/arbitrum/l2-transfer-tools-guide/ +/zh/archived/arbitrum/arbitrum-faq/ +/zh/archived/arbitrum/l2-transfer-tools-faq/ +/zh/archived/arbitrum/l2-transfer-tools-guide/ +/zh/archived/sunrise/ /zh/billing/ /zh/chain-integration-overview/ +/zh/contracts/ /zh/cookbook/arweave/ /zh/cookbook/avoid-eth-calls/ /zh/cookbook/cosmos/ @@ -1662,37 +1664,32 @@ /zh/cookbook/substreams-powered-subgraphs/ /zh/cookbook/timeseries/ /zh/cookbook/transfer-to-the-graph/ -/zh/deploying/deploy-using-subgraph-studio/ -/zh/deploying/multiple-networks/ -/zh/deploying/subgraph-studio-faqs/ /zh/developing/creating-a-subgraph/advanced/ /zh/developing/creating-a-subgraph/assemblyscript-mappings/ +/zh/developing/creating-a-subgraph/graph-ts/api/ +/zh/developing/creating-a-subgraph/graph-ts/common-issues/ /zh/developing/creating-a-subgraph/install-the-cli/ /zh/developing/creating-a-subgraph/ql-schema/ /zh/developing/creating-a-subgraph/starting-your-subgraph/ /zh/developing/creating-a-subgraph/subgraph-manifest/ +/zh/developing/creating-a-subgraph/unit-testing-framework/ +/zh/developing/deploying/deploy-using-subgraph-studio/ +/zh/developing/deploying/multiple-networks/ +/zh/developing/deploying/subgraph-studio-faqs/ /zh/developing/developer-faqs/ -/zh/developing/graph-ts/api/ -/zh/developing/graph-ts/common-issues/ -/zh/developing/substreams-powered-subgraphs-faq/ +/zh/developing/developing/ +/zh/developing/managing/delete-a-subgraph/ +/zh/developing/managing/transfer-a-subgraph/ +/zh/developing/publishing/publishing-a-subgraph/ +/zh/developing/subgraphs/ /zh/developing/supported-networks/ -/zh/developing/unit-testing-framework/ -/zh/firehose/ +/zh/explorer/ /zh/glossary/ -/zh/graphcast/ -/zh/managing/delete-a-subgraph/ -/zh/managing/transfer-a-subgraph/ -/zh/network/benefits/ -/zh/network/contracts/ -/zh/network/curating/ -/zh/network/delegating/ -/zh/network/developing/ -/zh/network/explorer/ -/zh/network/indexing/ -/zh/network/overview/ +/zh/indexer-tooling/firehose/ +/zh/indexer-tooling/graphcast/ +/zh/indexer-tooling/operating-graph-node/ +/zh/indexing/ /zh/new-chain-integration/ -/zh/operating-graph-node/ -/zh/publishing/publishing-a-subgraph/ /zh/querying/distributed-systems/ /zh/querying/graphql-api/ /zh/querying/managing-api-keys/ @@ -1704,12 +1701,15 @@ /zh/quick-start/ /zh/release-notes/assemblyscript-migration-guide/ /zh/release-notes/graphql-validations-migration-guide/ +/zh/roles-and-benefits/benefits/ +/zh/roles-and-benefits/curating/ +/zh/roles-and-benefits/delegating/ +/zh/roles-and-benefits/overview/ /zh/sps/introduction/ +/zh/sps/substreams-powered-subgraphs-faq/ /zh/sps/triggers-example/ /zh/sps/triggers/ -/zh/subgraphs/ /zh/substreams/ -/zh/sunrise/ /zh/supported-network-requirements/ /zh/tap/ /zh/tokenomics/ From 3d453a4cf501851896d379ee012ce88cd09616d2 Mon Sep 17 00:00:00 2001 From: benface Date: Mon, 16 Dec 2024 19:50:06 -0500 Subject: [PATCH 07/22] =?UTF-8?q?=E2=80=9CRoles=20and=20Benefits=E2=80=9D?= =?UTF-8?q?=20=3D>=20=E2=80=9CNetwork=E2=80=9D=20+=20move=20Tokenomics=20t?= =?UTF-8?q?o=20it?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- website/pages/ar/network/_meta.js | 5 +++++ .../pages/ar/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/ar/{roles-and-benefits => network}/curating.mdx | 0 .../pages/ar/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/ar/{roles-and-benefits => network}/overview.mdx | 0 website/pages/ar/{ => network}/tokenomics.mdx | 0 website/pages/ar/roles-and-benefits/_meta.js | 5 ----- website/pages/cs/network/_meta.js | 5 +++++ .../pages/cs/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/cs/{roles-and-benefits => network}/curating.mdx | 0 .../pages/cs/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/cs/{roles-and-benefits => network}/overview.mdx | 0 website/pages/cs/{ => network}/tokenomics.mdx | 0 website/pages/cs/roles-and-benefits/_meta.js | 5 ----- website/pages/de/network/_meta.js | 5 +++++ .../pages/de/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/de/{roles-and-benefits => network}/curating.mdx | 0 .../pages/de/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/de/{roles-and-benefits => network}/overview.mdx | 0 website/pages/de/{ => network}/tokenomics.mdx | 0 website/pages/de/roles-and-benefits/_meta.js | 5 ----- website/pages/en/_meta.js | 3 +-- website/pages/en/{roles-and-benefits => network}/_meta.js | 1 + .../pages/en/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/en/{roles-and-benefits => network}/curating.mdx | 0 .../pages/en/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/en/{roles-and-benefits => network}/overview.mdx | 0 website/pages/en/{ => network}/tokenomics.mdx | 0 website/pages/es/network/_meta.js | 5 +++++ .../pages/es/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/es/{roles-and-benefits => network}/curating.mdx | 0 .../pages/es/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/es/{roles-and-benefits => network}/overview.mdx | 0 website/pages/es/{ => network}/tokenomics.mdx | 0 website/pages/es/roles-and-benefits/_meta.js | 5 ----- website/pages/fr/network/_meta.js | 5 +++++ .../pages/fr/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/fr/{roles-and-benefits => network}/curating.mdx | 0 .../pages/fr/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/fr/{roles-and-benefits => network}/overview.mdx | 0 website/pages/fr/{ => network}/tokenomics.mdx | 0 website/pages/fr/roles-and-benefits/_meta.js | 5 ----- website/pages/hi/network/_meta.js | 5 +++++ .../pages/hi/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/hi/{roles-and-benefits => network}/curating.mdx | 0 .../pages/hi/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/hi/{roles-and-benefits => network}/overview.mdx | 0 website/pages/hi/{ => network}/tokenomics.mdx | 0 website/pages/hi/roles-and-benefits/_meta.js | 5 ----- website/pages/it/network/_meta.js | 5 +++++ .../pages/it/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/it/{roles-and-benefits => network}/curating.mdx | 0 .../pages/it/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/it/{roles-and-benefits => network}/overview.mdx | 0 website/pages/it/{ => network}/tokenomics.mdx | 0 website/pages/it/roles-and-benefits/_meta.js | 5 ----- website/pages/ja/network/_meta.js | 5 +++++ .../pages/ja/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/ja/{roles-and-benefits => network}/curating.mdx | 0 .../pages/ja/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/ja/{roles-and-benefits => network}/overview.mdx | 0 website/pages/ja/{ => network}/tokenomics.mdx | 0 website/pages/ja/roles-and-benefits/_meta.js | 5 ----- website/pages/ko/network/_meta.js | 5 +++++ .../pages/ko/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/ko/{roles-and-benefits => network}/curating.mdx | 0 .../pages/ko/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/ko/{roles-and-benefits => network}/overview.mdx | 0 website/pages/ko/{ => network}/tokenomics.mdx | 0 website/pages/ko/roles-and-benefits/_meta.js | 5 ----- website/pages/mr/network/_meta.js | 5 +++++ .../pages/mr/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/mr/{roles-and-benefits => network}/curating.mdx | 0 .../pages/mr/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/mr/{roles-and-benefits => network}/overview.mdx | 0 website/pages/mr/{ => network}/tokenomics.mdx | 0 website/pages/mr/roles-and-benefits/_meta.js | 5 ----- website/pages/nl/network/_meta.js | 5 +++++ .../pages/nl/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/nl/{roles-and-benefits => network}/curating.mdx | 0 .../pages/nl/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/nl/{roles-and-benefits => network}/overview.mdx | 0 website/pages/nl/{ => network}/tokenomics.mdx | 0 website/pages/nl/roles-and-benefits/_meta.js | 5 ----- website/pages/pl/network/_meta.js | 5 +++++ .../pages/pl/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/pl/{roles-and-benefits => network}/curating.mdx | 0 .../pages/pl/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/pl/{roles-and-benefits => network}/overview.mdx | 0 website/pages/pl/{ => network}/tokenomics.mdx | 0 website/pages/pl/roles-and-benefits/_meta.js | 5 ----- website/pages/pt/network/_meta.js | 5 +++++ .../pages/pt/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/pt/{roles-and-benefits => network}/curating.mdx | 0 .../pages/pt/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/pt/{roles-and-benefits => network}/overview.mdx | 0 website/pages/pt/{ => network}/tokenomics.mdx | 0 website/pages/pt/roles-and-benefits/_meta.js | 5 ----- website/pages/ro/network/_meta.js | 5 +++++ .../pages/ro/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/ro/{roles-and-benefits => network}/curating.mdx | 0 .../pages/ro/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/ro/{roles-and-benefits => network}/overview.mdx | 0 website/pages/ro/{ => network}/tokenomics.mdx | 0 website/pages/ro/roles-and-benefits/_meta.js | 5 ----- website/pages/ru/network/_meta.js | 5 +++++ .../pages/ru/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/ru/{roles-and-benefits => network}/curating.mdx | 0 .../pages/ru/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/ru/{roles-and-benefits => network}/overview.mdx | 0 website/pages/ru/{ => network}/tokenomics.mdx | 0 website/pages/ru/roles-and-benefits/_meta.js | 5 ----- website/pages/sv/network/_meta.js | 5 +++++ .../pages/sv/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/sv/{roles-and-benefits => network}/curating.mdx | 0 .../pages/sv/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/sv/{roles-and-benefits => network}/overview.mdx | 0 website/pages/sv/{ => network}/tokenomics.mdx | 0 website/pages/sv/roles-and-benefits/_meta.js | 5 ----- website/pages/sw/network/_meta.js | 5 +++++ .../pages/sw/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/sw/{roles-and-benefits => network}/curating.mdx | 0 .../pages/sw/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/sw/{roles-and-benefits => network}/overview.mdx | 0 website/pages/sw/{ => network}/tokenomics.mdx | 0 website/pages/sw/roles-and-benefits/_meta.js | 5 ----- website/pages/tr/network/_meta.js | 5 +++++ .../pages/tr/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/tr/{roles-and-benefits => network}/curating.mdx | 0 .../pages/tr/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/tr/{roles-and-benefits => network}/overview.mdx | 0 website/pages/tr/{ => network}/tokenomics.mdx | 0 website/pages/tr/roles-and-benefits/_meta.js | 5 ----- website/pages/uk/network/_meta.js | 5 +++++ .../pages/uk/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/uk/{roles-and-benefits => network}/curating.mdx | 0 .../pages/uk/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/uk/{roles-and-benefits => network}/overview.mdx | 0 website/pages/uk/{ => network}/tokenomics.mdx | 0 website/pages/uk/roles-and-benefits/_meta.js | 5 ----- website/pages/ur/network/_meta.js | 5 +++++ .../pages/ur/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/ur/{roles-and-benefits => network}/curating.mdx | 0 .../pages/ur/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/ur/{roles-and-benefits => network}/overview.mdx | 0 website/pages/ur/{ => network}/tokenomics.mdx | 0 website/pages/ur/roles-and-benefits/_meta.js | 5 ----- website/pages/vi/network/_meta.js | 5 +++++ .../pages/vi/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/vi/{roles-and-benefits => network}/curating.mdx | 0 .../pages/vi/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/vi/{roles-and-benefits => network}/overview.mdx | 0 website/pages/vi/{ => network}/tokenomics.mdx | 0 website/pages/vi/roles-and-benefits/_meta.js | 5 ----- website/pages/zh/network/_meta.js | 5 +++++ .../pages/zh/{roles-and-benefits => network}/benefits.mdx | 0 .../pages/zh/{roles-and-benefits => network}/curating.mdx | 0 .../pages/zh/{roles-and-benefits => network}/delegating.mdx | 0 .../pages/zh/{roles-and-benefits => network}/overview.mdx | 0 website/pages/zh/{ => network}/tokenomics.mdx | 0 website/pages/zh/roles-and-benefits/_meta.js | 5 ----- 161 files changed, 112 insertions(+), 112 deletions(-) create mode 100644 website/pages/ar/network/_meta.js rename website/pages/ar/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/ar/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/ar/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/ar/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/ar/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/ar/roles-and-benefits/_meta.js create mode 100644 website/pages/cs/network/_meta.js rename website/pages/cs/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/cs/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/cs/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/cs/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/cs/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/cs/roles-and-benefits/_meta.js create mode 100644 website/pages/de/network/_meta.js rename website/pages/de/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/de/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/de/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/de/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/de/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/de/roles-and-benefits/_meta.js rename website/pages/en/{roles-and-benefits => network}/_meta.js (78%) rename website/pages/en/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/en/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/en/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/en/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/en/{ => network}/tokenomics.mdx (100%) create mode 100644 website/pages/es/network/_meta.js rename website/pages/es/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/es/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/es/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/es/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/es/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/es/roles-and-benefits/_meta.js create mode 100644 website/pages/fr/network/_meta.js rename website/pages/fr/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/fr/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/fr/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/fr/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/fr/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/fr/roles-and-benefits/_meta.js create mode 100644 website/pages/hi/network/_meta.js rename website/pages/hi/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/hi/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/hi/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/hi/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/hi/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/hi/roles-and-benefits/_meta.js create mode 100644 website/pages/it/network/_meta.js rename website/pages/it/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/it/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/it/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/it/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/it/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/it/roles-and-benefits/_meta.js create mode 100644 website/pages/ja/network/_meta.js rename website/pages/ja/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/ja/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/ja/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/ja/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/ja/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/ja/roles-and-benefits/_meta.js create mode 100644 website/pages/ko/network/_meta.js rename website/pages/ko/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/ko/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/ko/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/ko/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/ko/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/ko/roles-and-benefits/_meta.js create mode 100644 website/pages/mr/network/_meta.js rename website/pages/mr/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/mr/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/mr/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/mr/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/mr/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/mr/roles-and-benefits/_meta.js create mode 100644 website/pages/nl/network/_meta.js rename website/pages/nl/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/nl/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/nl/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/nl/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/nl/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/nl/roles-and-benefits/_meta.js create mode 100644 website/pages/pl/network/_meta.js rename website/pages/pl/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/pl/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/pl/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/pl/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/pl/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/pl/roles-and-benefits/_meta.js create mode 100644 website/pages/pt/network/_meta.js rename website/pages/pt/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/pt/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/pt/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/pt/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/pt/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/pt/roles-and-benefits/_meta.js create mode 100644 website/pages/ro/network/_meta.js rename website/pages/ro/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/ro/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/ro/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/ro/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/ro/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/ro/roles-and-benefits/_meta.js create mode 100644 website/pages/ru/network/_meta.js rename website/pages/ru/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/ru/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/ru/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/ru/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/ru/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/ru/roles-and-benefits/_meta.js create mode 100644 website/pages/sv/network/_meta.js rename website/pages/sv/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/sv/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/sv/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/sv/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/sv/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/sv/roles-and-benefits/_meta.js create mode 100644 website/pages/sw/network/_meta.js rename website/pages/sw/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/sw/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/sw/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/sw/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/sw/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/sw/roles-and-benefits/_meta.js create mode 100644 website/pages/tr/network/_meta.js rename website/pages/tr/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/tr/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/tr/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/tr/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/tr/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/tr/roles-and-benefits/_meta.js create mode 100644 website/pages/uk/network/_meta.js rename website/pages/uk/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/uk/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/uk/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/uk/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/uk/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/uk/roles-and-benefits/_meta.js create mode 100644 website/pages/ur/network/_meta.js rename website/pages/ur/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/ur/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/ur/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/ur/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/ur/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/ur/roles-and-benefits/_meta.js create mode 100644 website/pages/vi/network/_meta.js rename website/pages/vi/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/vi/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/vi/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/vi/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/vi/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/vi/roles-and-benefits/_meta.js create mode 100644 website/pages/zh/network/_meta.js rename website/pages/zh/{roles-and-benefits => network}/benefits.mdx (100%) rename website/pages/zh/{roles-and-benefits => network}/curating.mdx (100%) rename website/pages/zh/{roles-and-benefits => network}/delegating.mdx (100%) rename website/pages/zh/{roles-and-benefits => network}/overview.mdx (100%) rename website/pages/zh/{ => network}/tokenomics.mdx (100%) delete mode 100644 website/pages/zh/roles-and-benefits/_meta.js diff --git a/website/pages/ar/network/_meta.js b/website/pages/ar/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/ar/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/roles-and-benefits/benefits.mdx b/website/pages/ar/network/benefits.mdx similarity index 100% rename from website/pages/ar/roles-and-benefits/benefits.mdx rename to website/pages/ar/network/benefits.mdx diff --git a/website/pages/ar/roles-and-benefits/curating.mdx b/website/pages/ar/network/curating.mdx similarity index 100% rename from website/pages/ar/roles-and-benefits/curating.mdx rename to website/pages/ar/network/curating.mdx diff --git a/website/pages/ar/roles-and-benefits/delegating.mdx b/website/pages/ar/network/delegating.mdx similarity index 100% rename from website/pages/ar/roles-and-benefits/delegating.mdx rename to website/pages/ar/network/delegating.mdx diff --git a/website/pages/ar/roles-and-benefits/overview.mdx b/website/pages/ar/network/overview.mdx similarity index 100% rename from website/pages/ar/roles-and-benefits/overview.mdx rename to website/pages/ar/network/overview.mdx diff --git a/website/pages/ar/tokenomics.mdx b/website/pages/ar/network/tokenomics.mdx similarity index 100% rename from website/pages/ar/tokenomics.mdx rename to website/pages/ar/network/tokenomics.mdx diff --git a/website/pages/ar/roles-and-benefits/_meta.js b/website/pages/ar/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/ar/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/network/_meta.js b/website/pages/cs/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/cs/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/roles-and-benefits/benefits.mdx b/website/pages/cs/network/benefits.mdx similarity index 100% rename from website/pages/cs/roles-and-benefits/benefits.mdx rename to website/pages/cs/network/benefits.mdx diff --git a/website/pages/cs/roles-and-benefits/curating.mdx b/website/pages/cs/network/curating.mdx similarity index 100% rename from website/pages/cs/roles-and-benefits/curating.mdx rename to website/pages/cs/network/curating.mdx diff --git a/website/pages/cs/roles-and-benefits/delegating.mdx b/website/pages/cs/network/delegating.mdx similarity index 100% rename from website/pages/cs/roles-and-benefits/delegating.mdx rename to website/pages/cs/network/delegating.mdx diff --git a/website/pages/cs/roles-and-benefits/overview.mdx b/website/pages/cs/network/overview.mdx similarity index 100% rename from website/pages/cs/roles-and-benefits/overview.mdx rename to website/pages/cs/network/overview.mdx diff --git a/website/pages/cs/tokenomics.mdx b/website/pages/cs/network/tokenomics.mdx similarity index 100% rename from website/pages/cs/tokenomics.mdx rename to website/pages/cs/network/tokenomics.mdx diff --git a/website/pages/cs/roles-and-benefits/_meta.js b/website/pages/cs/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/cs/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/network/_meta.js b/website/pages/de/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/de/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/roles-and-benefits/benefits.mdx b/website/pages/de/network/benefits.mdx similarity index 100% rename from website/pages/de/roles-and-benefits/benefits.mdx rename to website/pages/de/network/benefits.mdx diff --git a/website/pages/de/roles-and-benefits/curating.mdx b/website/pages/de/network/curating.mdx similarity index 100% rename from website/pages/de/roles-and-benefits/curating.mdx rename to website/pages/de/network/curating.mdx diff --git a/website/pages/de/roles-and-benefits/delegating.mdx b/website/pages/de/network/delegating.mdx similarity index 100% rename from website/pages/de/roles-and-benefits/delegating.mdx rename to website/pages/de/network/delegating.mdx diff --git a/website/pages/de/roles-and-benefits/overview.mdx b/website/pages/de/network/overview.mdx similarity index 100% rename from website/pages/de/roles-and-benefits/overview.mdx rename to website/pages/de/network/overview.mdx diff --git a/website/pages/de/tokenomics.mdx b/website/pages/de/network/tokenomics.mdx similarity index 100% rename from website/pages/de/tokenomics.mdx rename to website/pages/de/network/tokenomics.mdx diff --git a/website/pages/de/roles-and-benefits/_meta.js b/website/pages/de/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/de/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index 7cff2ea6621d..926203946230 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -45,8 +45,7 @@ export default { type: 'heading', title: 'Resources', }, - 'roles-and-benefits': 'Roles and Benefits', - tokenomics: 'Tokenomics', + network: 'Network', glossary: '', 'release-notes': 'Release Notes & Upgrade Guides', archived: 'Archived', diff --git a/website/pages/en/roles-and-benefits/_meta.js b/website/pages/en/network/_meta.js similarity index 78% rename from website/pages/en/roles-and-benefits/_meta.js rename to website/pages/en/network/_meta.js index 3a25fcb924c4..4cda16e151d4 100644 --- a/website/pages/en/roles-and-benefits/_meta.js +++ b/website/pages/en/network/_meta.js @@ -1,6 +1,7 @@ export default { overview: 'Overview', benefits: 'Benefits', + tokenomics: 'Tokenomics', delegating: '', curating: '', } diff --git a/website/pages/en/roles-and-benefits/benefits.mdx b/website/pages/en/network/benefits.mdx similarity index 100% rename from website/pages/en/roles-and-benefits/benefits.mdx rename to website/pages/en/network/benefits.mdx diff --git a/website/pages/en/roles-and-benefits/curating.mdx b/website/pages/en/network/curating.mdx similarity index 100% rename from website/pages/en/roles-and-benefits/curating.mdx rename to website/pages/en/network/curating.mdx diff --git a/website/pages/en/roles-and-benefits/delegating.mdx b/website/pages/en/network/delegating.mdx similarity index 100% rename from website/pages/en/roles-and-benefits/delegating.mdx rename to website/pages/en/network/delegating.mdx diff --git a/website/pages/en/roles-and-benefits/overview.mdx b/website/pages/en/network/overview.mdx similarity index 100% rename from website/pages/en/roles-and-benefits/overview.mdx rename to website/pages/en/network/overview.mdx diff --git a/website/pages/en/tokenomics.mdx b/website/pages/en/network/tokenomics.mdx similarity index 100% rename from website/pages/en/tokenomics.mdx rename to website/pages/en/network/tokenomics.mdx diff --git a/website/pages/es/network/_meta.js b/website/pages/es/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/es/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/roles-and-benefits/benefits.mdx b/website/pages/es/network/benefits.mdx similarity index 100% rename from website/pages/es/roles-and-benefits/benefits.mdx rename to website/pages/es/network/benefits.mdx diff --git a/website/pages/es/roles-and-benefits/curating.mdx b/website/pages/es/network/curating.mdx similarity index 100% rename from website/pages/es/roles-and-benefits/curating.mdx rename to website/pages/es/network/curating.mdx diff --git a/website/pages/es/roles-and-benefits/delegating.mdx b/website/pages/es/network/delegating.mdx similarity index 100% rename from website/pages/es/roles-and-benefits/delegating.mdx rename to website/pages/es/network/delegating.mdx diff --git a/website/pages/es/roles-and-benefits/overview.mdx b/website/pages/es/network/overview.mdx similarity index 100% rename from website/pages/es/roles-and-benefits/overview.mdx rename to website/pages/es/network/overview.mdx diff --git a/website/pages/es/tokenomics.mdx b/website/pages/es/network/tokenomics.mdx similarity index 100% rename from website/pages/es/tokenomics.mdx rename to website/pages/es/network/tokenomics.mdx diff --git a/website/pages/es/roles-and-benefits/_meta.js b/website/pages/es/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/es/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/network/_meta.js b/website/pages/fr/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/fr/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/roles-and-benefits/benefits.mdx b/website/pages/fr/network/benefits.mdx similarity index 100% rename from website/pages/fr/roles-and-benefits/benefits.mdx rename to website/pages/fr/network/benefits.mdx diff --git a/website/pages/fr/roles-and-benefits/curating.mdx b/website/pages/fr/network/curating.mdx similarity index 100% rename from website/pages/fr/roles-and-benefits/curating.mdx rename to website/pages/fr/network/curating.mdx diff --git a/website/pages/fr/roles-and-benefits/delegating.mdx b/website/pages/fr/network/delegating.mdx similarity index 100% rename from website/pages/fr/roles-and-benefits/delegating.mdx rename to website/pages/fr/network/delegating.mdx diff --git a/website/pages/fr/roles-and-benefits/overview.mdx b/website/pages/fr/network/overview.mdx similarity index 100% rename from website/pages/fr/roles-and-benefits/overview.mdx rename to website/pages/fr/network/overview.mdx diff --git a/website/pages/fr/tokenomics.mdx b/website/pages/fr/network/tokenomics.mdx similarity index 100% rename from website/pages/fr/tokenomics.mdx rename to website/pages/fr/network/tokenomics.mdx diff --git a/website/pages/fr/roles-and-benefits/_meta.js b/website/pages/fr/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/fr/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/network/_meta.js b/website/pages/hi/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/hi/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/roles-and-benefits/benefits.mdx b/website/pages/hi/network/benefits.mdx similarity index 100% rename from website/pages/hi/roles-and-benefits/benefits.mdx rename to website/pages/hi/network/benefits.mdx diff --git a/website/pages/hi/roles-and-benefits/curating.mdx b/website/pages/hi/network/curating.mdx similarity index 100% rename from website/pages/hi/roles-and-benefits/curating.mdx rename to website/pages/hi/network/curating.mdx diff --git a/website/pages/hi/roles-and-benefits/delegating.mdx b/website/pages/hi/network/delegating.mdx similarity index 100% rename from website/pages/hi/roles-and-benefits/delegating.mdx rename to website/pages/hi/network/delegating.mdx diff --git a/website/pages/hi/roles-and-benefits/overview.mdx b/website/pages/hi/network/overview.mdx similarity index 100% rename from website/pages/hi/roles-and-benefits/overview.mdx rename to website/pages/hi/network/overview.mdx diff --git a/website/pages/hi/tokenomics.mdx b/website/pages/hi/network/tokenomics.mdx similarity index 100% rename from website/pages/hi/tokenomics.mdx rename to website/pages/hi/network/tokenomics.mdx diff --git a/website/pages/hi/roles-and-benefits/_meta.js b/website/pages/hi/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/hi/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/network/_meta.js b/website/pages/it/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/it/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/roles-and-benefits/benefits.mdx b/website/pages/it/network/benefits.mdx similarity index 100% rename from website/pages/it/roles-and-benefits/benefits.mdx rename to website/pages/it/network/benefits.mdx diff --git a/website/pages/it/roles-and-benefits/curating.mdx b/website/pages/it/network/curating.mdx similarity index 100% rename from website/pages/it/roles-and-benefits/curating.mdx rename to website/pages/it/network/curating.mdx diff --git a/website/pages/it/roles-and-benefits/delegating.mdx b/website/pages/it/network/delegating.mdx similarity index 100% rename from website/pages/it/roles-and-benefits/delegating.mdx rename to website/pages/it/network/delegating.mdx diff --git a/website/pages/it/roles-and-benefits/overview.mdx b/website/pages/it/network/overview.mdx similarity index 100% rename from website/pages/it/roles-and-benefits/overview.mdx rename to website/pages/it/network/overview.mdx diff --git a/website/pages/it/tokenomics.mdx b/website/pages/it/network/tokenomics.mdx similarity index 100% rename from website/pages/it/tokenomics.mdx rename to website/pages/it/network/tokenomics.mdx diff --git a/website/pages/it/roles-and-benefits/_meta.js b/website/pages/it/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/it/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/network/_meta.js b/website/pages/ja/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/ja/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/roles-and-benefits/benefits.mdx b/website/pages/ja/network/benefits.mdx similarity index 100% rename from website/pages/ja/roles-and-benefits/benefits.mdx rename to website/pages/ja/network/benefits.mdx diff --git a/website/pages/ja/roles-and-benefits/curating.mdx b/website/pages/ja/network/curating.mdx similarity index 100% rename from website/pages/ja/roles-and-benefits/curating.mdx rename to website/pages/ja/network/curating.mdx diff --git a/website/pages/ja/roles-and-benefits/delegating.mdx b/website/pages/ja/network/delegating.mdx similarity index 100% rename from website/pages/ja/roles-and-benefits/delegating.mdx rename to website/pages/ja/network/delegating.mdx diff --git a/website/pages/ja/roles-and-benefits/overview.mdx b/website/pages/ja/network/overview.mdx similarity index 100% rename from website/pages/ja/roles-and-benefits/overview.mdx rename to website/pages/ja/network/overview.mdx diff --git a/website/pages/ja/tokenomics.mdx b/website/pages/ja/network/tokenomics.mdx similarity index 100% rename from website/pages/ja/tokenomics.mdx rename to website/pages/ja/network/tokenomics.mdx diff --git a/website/pages/ja/roles-and-benefits/_meta.js b/website/pages/ja/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/ja/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/network/_meta.js b/website/pages/ko/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/ko/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/roles-and-benefits/benefits.mdx b/website/pages/ko/network/benefits.mdx similarity index 100% rename from website/pages/ko/roles-and-benefits/benefits.mdx rename to website/pages/ko/network/benefits.mdx diff --git a/website/pages/ko/roles-and-benefits/curating.mdx b/website/pages/ko/network/curating.mdx similarity index 100% rename from website/pages/ko/roles-and-benefits/curating.mdx rename to website/pages/ko/network/curating.mdx diff --git a/website/pages/ko/roles-and-benefits/delegating.mdx b/website/pages/ko/network/delegating.mdx similarity index 100% rename from website/pages/ko/roles-and-benefits/delegating.mdx rename to website/pages/ko/network/delegating.mdx diff --git a/website/pages/ko/roles-and-benefits/overview.mdx b/website/pages/ko/network/overview.mdx similarity index 100% rename from website/pages/ko/roles-and-benefits/overview.mdx rename to website/pages/ko/network/overview.mdx diff --git a/website/pages/ko/tokenomics.mdx b/website/pages/ko/network/tokenomics.mdx similarity index 100% rename from website/pages/ko/tokenomics.mdx rename to website/pages/ko/network/tokenomics.mdx diff --git a/website/pages/ko/roles-and-benefits/_meta.js b/website/pages/ko/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/ko/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/network/_meta.js b/website/pages/mr/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/mr/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/roles-and-benefits/benefits.mdx b/website/pages/mr/network/benefits.mdx similarity index 100% rename from website/pages/mr/roles-and-benefits/benefits.mdx rename to website/pages/mr/network/benefits.mdx diff --git a/website/pages/mr/roles-and-benefits/curating.mdx b/website/pages/mr/network/curating.mdx similarity index 100% rename from website/pages/mr/roles-and-benefits/curating.mdx rename to website/pages/mr/network/curating.mdx diff --git a/website/pages/mr/roles-and-benefits/delegating.mdx b/website/pages/mr/network/delegating.mdx similarity index 100% rename from website/pages/mr/roles-and-benefits/delegating.mdx rename to website/pages/mr/network/delegating.mdx diff --git a/website/pages/mr/roles-and-benefits/overview.mdx b/website/pages/mr/network/overview.mdx similarity index 100% rename from website/pages/mr/roles-and-benefits/overview.mdx rename to website/pages/mr/network/overview.mdx diff --git a/website/pages/mr/tokenomics.mdx b/website/pages/mr/network/tokenomics.mdx similarity index 100% rename from website/pages/mr/tokenomics.mdx rename to website/pages/mr/network/tokenomics.mdx diff --git a/website/pages/mr/roles-and-benefits/_meta.js b/website/pages/mr/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/mr/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/network/_meta.js b/website/pages/nl/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/nl/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/roles-and-benefits/benefits.mdx b/website/pages/nl/network/benefits.mdx similarity index 100% rename from website/pages/nl/roles-and-benefits/benefits.mdx rename to website/pages/nl/network/benefits.mdx diff --git a/website/pages/nl/roles-and-benefits/curating.mdx b/website/pages/nl/network/curating.mdx similarity index 100% rename from website/pages/nl/roles-and-benefits/curating.mdx rename to website/pages/nl/network/curating.mdx diff --git a/website/pages/nl/roles-and-benefits/delegating.mdx b/website/pages/nl/network/delegating.mdx similarity index 100% rename from website/pages/nl/roles-and-benefits/delegating.mdx rename to website/pages/nl/network/delegating.mdx diff --git a/website/pages/nl/roles-and-benefits/overview.mdx b/website/pages/nl/network/overview.mdx similarity index 100% rename from website/pages/nl/roles-and-benefits/overview.mdx rename to website/pages/nl/network/overview.mdx diff --git a/website/pages/nl/tokenomics.mdx b/website/pages/nl/network/tokenomics.mdx similarity index 100% rename from website/pages/nl/tokenomics.mdx rename to website/pages/nl/network/tokenomics.mdx diff --git a/website/pages/nl/roles-and-benefits/_meta.js b/website/pages/nl/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/nl/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/network/_meta.js b/website/pages/pl/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/pl/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/roles-and-benefits/benefits.mdx b/website/pages/pl/network/benefits.mdx similarity index 100% rename from website/pages/pl/roles-and-benefits/benefits.mdx rename to website/pages/pl/network/benefits.mdx diff --git a/website/pages/pl/roles-and-benefits/curating.mdx b/website/pages/pl/network/curating.mdx similarity index 100% rename from website/pages/pl/roles-and-benefits/curating.mdx rename to website/pages/pl/network/curating.mdx diff --git a/website/pages/pl/roles-and-benefits/delegating.mdx b/website/pages/pl/network/delegating.mdx similarity index 100% rename from website/pages/pl/roles-and-benefits/delegating.mdx rename to website/pages/pl/network/delegating.mdx diff --git a/website/pages/pl/roles-and-benefits/overview.mdx b/website/pages/pl/network/overview.mdx similarity index 100% rename from website/pages/pl/roles-and-benefits/overview.mdx rename to website/pages/pl/network/overview.mdx diff --git a/website/pages/pl/tokenomics.mdx b/website/pages/pl/network/tokenomics.mdx similarity index 100% rename from website/pages/pl/tokenomics.mdx rename to website/pages/pl/network/tokenomics.mdx diff --git a/website/pages/pl/roles-and-benefits/_meta.js b/website/pages/pl/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/pl/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/network/_meta.js b/website/pages/pt/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/pt/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/roles-and-benefits/benefits.mdx b/website/pages/pt/network/benefits.mdx similarity index 100% rename from website/pages/pt/roles-and-benefits/benefits.mdx rename to website/pages/pt/network/benefits.mdx diff --git a/website/pages/pt/roles-and-benefits/curating.mdx b/website/pages/pt/network/curating.mdx similarity index 100% rename from website/pages/pt/roles-and-benefits/curating.mdx rename to website/pages/pt/network/curating.mdx diff --git a/website/pages/pt/roles-and-benefits/delegating.mdx b/website/pages/pt/network/delegating.mdx similarity index 100% rename from website/pages/pt/roles-and-benefits/delegating.mdx rename to website/pages/pt/network/delegating.mdx diff --git a/website/pages/pt/roles-and-benefits/overview.mdx b/website/pages/pt/network/overview.mdx similarity index 100% rename from website/pages/pt/roles-and-benefits/overview.mdx rename to website/pages/pt/network/overview.mdx diff --git a/website/pages/pt/tokenomics.mdx b/website/pages/pt/network/tokenomics.mdx similarity index 100% rename from website/pages/pt/tokenomics.mdx rename to website/pages/pt/network/tokenomics.mdx diff --git a/website/pages/pt/roles-and-benefits/_meta.js b/website/pages/pt/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/pt/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/network/_meta.js b/website/pages/ro/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/ro/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/roles-and-benefits/benefits.mdx b/website/pages/ro/network/benefits.mdx similarity index 100% rename from website/pages/ro/roles-and-benefits/benefits.mdx rename to website/pages/ro/network/benefits.mdx diff --git a/website/pages/ro/roles-and-benefits/curating.mdx b/website/pages/ro/network/curating.mdx similarity index 100% rename from website/pages/ro/roles-and-benefits/curating.mdx rename to website/pages/ro/network/curating.mdx diff --git a/website/pages/ro/roles-and-benefits/delegating.mdx b/website/pages/ro/network/delegating.mdx similarity index 100% rename from website/pages/ro/roles-and-benefits/delegating.mdx rename to website/pages/ro/network/delegating.mdx diff --git a/website/pages/ro/roles-and-benefits/overview.mdx b/website/pages/ro/network/overview.mdx similarity index 100% rename from website/pages/ro/roles-and-benefits/overview.mdx rename to website/pages/ro/network/overview.mdx diff --git a/website/pages/ro/tokenomics.mdx b/website/pages/ro/network/tokenomics.mdx similarity index 100% rename from website/pages/ro/tokenomics.mdx rename to website/pages/ro/network/tokenomics.mdx diff --git a/website/pages/ro/roles-and-benefits/_meta.js b/website/pages/ro/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/ro/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/network/_meta.js b/website/pages/ru/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/ru/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/roles-and-benefits/benefits.mdx b/website/pages/ru/network/benefits.mdx similarity index 100% rename from website/pages/ru/roles-and-benefits/benefits.mdx rename to website/pages/ru/network/benefits.mdx diff --git a/website/pages/ru/roles-and-benefits/curating.mdx b/website/pages/ru/network/curating.mdx similarity index 100% rename from website/pages/ru/roles-and-benefits/curating.mdx rename to website/pages/ru/network/curating.mdx diff --git a/website/pages/ru/roles-and-benefits/delegating.mdx b/website/pages/ru/network/delegating.mdx similarity index 100% rename from website/pages/ru/roles-and-benefits/delegating.mdx rename to website/pages/ru/network/delegating.mdx diff --git a/website/pages/ru/roles-and-benefits/overview.mdx b/website/pages/ru/network/overview.mdx similarity index 100% rename from website/pages/ru/roles-and-benefits/overview.mdx rename to website/pages/ru/network/overview.mdx diff --git a/website/pages/ru/tokenomics.mdx b/website/pages/ru/network/tokenomics.mdx similarity index 100% rename from website/pages/ru/tokenomics.mdx rename to website/pages/ru/network/tokenomics.mdx diff --git a/website/pages/ru/roles-and-benefits/_meta.js b/website/pages/ru/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/ru/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/network/_meta.js b/website/pages/sv/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/sv/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/roles-and-benefits/benefits.mdx b/website/pages/sv/network/benefits.mdx similarity index 100% rename from website/pages/sv/roles-and-benefits/benefits.mdx rename to website/pages/sv/network/benefits.mdx diff --git a/website/pages/sv/roles-and-benefits/curating.mdx b/website/pages/sv/network/curating.mdx similarity index 100% rename from website/pages/sv/roles-and-benefits/curating.mdx rename to website/pages/sv/network/curating.mdx diff --git a/website/pages/sv/roles-and-benefits/delegating.mdx b/website/pages/sv/network/delegating.mdx similarity index 100% rename from website/pages/sv/roles-and-benefits/delegating.mdx rename to website/pages/sv/network/delegating.mdx diff --git a/website/pages/sv/roles-and-benefits/overview.mdx b/website/pages/sv/network/overview.mdx similarity index 100% rename from website/pages/sv/roles-and-benefits/overview.mdx rename to website/pages/sv/network/overview.mdx diff --git a/website/pages/sv/tokenomics.mdx b/website/pages/sv/network/tokenomics.mdx similarity index 100% rename from website/pages/sv/tokenomics.mdx rename to website/pages/sv/network/tokenomics.mdx diff --git a/website/pages/sv/roles-and-benefits/_meta.js b/website/pages/sv/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/sv/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/network/_meta.js b/website/pages/sw/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/sw/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/roles-and-benefits/benefits.mdx b/website/pages/sw/network/benefits.mdx similarity index 100% rename from website/pages/sw/roles-and-benefits/benefits.mdx rename to website/pages/sw/network/benefits.mdx diff --git a/website/pages/sw/roles-and-benefits/curating.mdx b/website/pages/sw/network/curating.mdx similarity index 100% rename from website/pages/sw/roles-and-benefits/curating.mdx rename to website/pages/sw/network/curating.mdx diff --git a/website/pages/sw/roles-and-benefits/delegating.mdx b/website/pages/sw/network/delegating.mdx similarity index 100% rename from website/pages/sw/roles-and-benefits/delegating.mdx rename to website/pages/sw/network/delegating.mdx diff --git a/website/pages/sw/roles-and-benefits/overview.mdx b/website/pages/sw/network/overview.mdx similarity index 100% rename from website/pages/sw/roles-and-benefits/overview.mdx rename to website/pages/sw/network/overview.mdx diff --git a/website/pages/sw/tokenomics.mdx b/website/pages/sw/network/tokenomics.mdx similarity index 100% rename from website/pages/sw/tokenomics.mdx rename to website/pages/sw/network/tokenomics.mdx diff --git a/website/pages/sw/roles-and-benefits/_meta.js b/website/pages/sw/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/sw/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/network/_meta.js b/website/pages/tr/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/tr/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/roles-and-benefits/benefits.mdx b/website/pages/tr/network/benefits.mdx similarity index 100% rename from website/pages/tr/roles-and-benefits/benefits.mdx rename to website/pages/tr/network/benefits.mdx diff --git a/website/pages/tr/roles-and-benefits/curating.mdx b/website/pages/tr/network/curating.mdx similarity index 100% rename from website/pages/tr/roles-and-benefits/curating.mdx rename to website/pages/tr/network/curating.mdx diff --git a/website/pages/tr/roles-and-benefits/delegating.mdx b/website/pages/tr/network/delegating.mdx similarity index 100% rename from website/pages/tr/roles-and-benefits/delegating.mdx rename to website/pages/tr/network/delegating.mdx diff --git a/website/pages/tr/roles-and-benefits/overview.mdx b/website/pages/tr/network/overview.mdx similarity index 100% rename from website/pages/tr/roles-and-benefits/overview.mdx rename to website/pages/tr/network/overview.mdx diff --git a/website/pages/tr/tokenomics.mdx b/website/pages/tr/network/tokenomics.mdx similarity index 100% rename from website/pages/tr/tokenomics.mdx rename to website/pages/tr/network/tokenomics.mdx diff --git a/website/pages/tr/roles-and-benefits/_meta.js b/website/pages/tr/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/tr/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/network/_meta.js b/website/pages/uk/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/uk/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/roles-and-benefits/benefits.mdx b/website/pages/uk/network/benefits.mdx similarity index 100% rename from website/pages/uk/roles-and-benefits/benefits.mdx rename to website/pages/uk/network/benefits.mdx diff --git a/website/pages/uk/roles-and-benefits/curating.mdx b/website/pages/uk/network/curating.mdx similarity index 100% rename from website/pages/uk/roles-and-benefits/curating.mdx rename to website/pages/uk/network/curating.mdx diff --git a/website/pages/uk/roles-and-benefits/delegating.mdx b/website/pages/uk/network/delegating.mdx similarity index 100% rename from website/pages/uk/roles-and-benefits/delegating.mdx rename to website/pages/uk/network/delegating.mdx diff --git a/website/pages/uk/roles-and-benefits/overview.mdx b/website/pages/uk/network/overview.mdx similarity index 100% rename from website/pages/uk/roles-and-benefits/overview.mdx rename to website/pages/uk/network/overview.mdx diff --git a/website/pages/uk/tokenomics.mdx b/website/pages/uk/network/tokenomics.mdx similarity index 100% rename from website/pages/uk/tokenomics.mdx rename to website/pages/uk/network/tokenomics.mdx diff --git a/website/pages/uk/roles-and-benefits/_meta.js b/website/pages/uk/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/uk/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/network/_meta.js b/website/pages/ur/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/ur/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/roles-and-benefits/benefits.mdx b/website/pages/ur/network/benefits.mdx similarity index 100% rename from website/pages/ur/roles-and-benefits/benefits.mdx rename to website/pages/ur/network/benefits.mdx diff --git a/website/pages/ur/roles-and-benefits/curating.mdx b/website/pages/ur/network/curating.mdx similarity index 100% rename from website/pages/ur/roles-and-benefits/curating.mdx rename to website/pages/ur/network/curating.mdx diff --git a/website/pages/ur/roles-and-benefits/delegating.mdx b/website/pages/ur/network/delegating.mdx similarity index 100% rename from website/pages/ur/roles-and-benefits/delegating.mdx rename to website/pages/ur/network/delegating.mdx diff --git a/website/pages/ur/roles-and-benefits/overview.mdx b/website/pages/ur/network/overview.mdx similarity index 100% rename from website/pages/ur/roles-and-benefits/overview.mdx rename to website/pages/ur/network/overview.mdx diff --git a/website/pages/ur/tokenomics.mdx b/website/pages/ur/network/tokenomics.mdx similarity index 100% rename from website/pages/ur/tokenomics.mdx rename to website/pages/ur/network/tokenomics.mdx diff --git a/website/pages/ur/roles-and-benefits/_meta.js b/website/pages/ur/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/ur/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/network/_meta.js b/website/pages/vi/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/vi/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/roles-and-benefits/benefits.mdx b/website/pages/vi/network/benefits.mdx similarity index 100% rename from website/pages/vi/roles-and-benefits/benefits.mdx rename to website/pages/vi/network/benefits.mdx diff --git a/website/pages/vi/roles-and-benefits/curating.mdx b/website/pages/vi/network/curating.mdx similarity index 100% rename from website/pages/vi/roles-and-benefits/curating.mdx rename to website/pages/vi/network/curating.mdx diff --git a/website/pages/vi/roles-and-benefits/delegating.mdx b/website/pages/vi/network/delegating.mdx similarity index 100% rename from website/pages/vi/roles-and-benefits/delegating.mdx rename to website/pages/vi/network/delegating.mdx diff --git a/website/pages/vi/roles-and-benefits/overview.mdx b/website/pages/vi/network/overview.mdx similarity index 100% rename from website/pages/vi/roles-and-benefits/overview.mdx rename to website/pages/vi/network/overview.mdx diff --git a/website/pages/vi/tokenomics.mdx b/website/pages/vi/network/tokenomics.mdx similarity index 100% rename from website/pages/vi/tokenomics.mdx rename to website/pages/vi/network/tokenomics.mdx diff --git a/website/pages/vi/roles-and-benefits/_meta.js b/website/pages/vi/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/vi/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/network/_meta.js b/website/pages/zh/network/_meta.js new file mode 100644 index 000000000000..49858537c885 --- /dev/null +++ b/website/pages/zh/network/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/network/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/roles-and-benefits/benefits.mdx b/website/pages/zh/network/benefits.mdx similarity index 100% rename from website/pages/zh/roles-and-benefits/benefits.mdx rename to website/pages/zh/network/benefits.mdx diff --git a/website/pages/zh/roles-and-benefits/curating.mdx b/website/pages/zh/network/curating.mdx similarity index 100% rename from website/pages/zh/roles-and-benefits/curating.mdx rename to website/pages/zh/network/curating.mdx diff --git a/website/pages/zh/roles-and-benefits/delegating.mdx b/website/pages/zh/network/delegating.mdx similarity index 100% rename from website/pages/zh/roles-and-benefits/delegating.mdx rename to website/pages/zh/network/delegating.mdx diff --git a/website/pages/zh/roles-and-benefits/overview.mdx b/website/pages/zh/network/overview.mdx similarity index 100% rename from website/pages/zh/roles-and-benefits/overview.mdx rename to website/pages/zh/network/overview.mdx diff --git a/website/pages/zh/tokenomics.mdx b/website/pages/zh/network/tokenomics.mdx similarity index 100% rename from website/pages/zh/tokenomics.mdx rename to website/pages/zh/network/tokenomics.mdx diff --git a/website/pages/zh/roles-and-benefits/_meta.js b/website/pages/zh/roles-and-benefits/_meta.js deleted file mode 100644 index cc666d15a6ca..000000000000 --- a/website/pages/zh/roles-and-benefits/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/roles-and-benefits/_meta.js' - -export default { - ...meta, -} From 87b421375065f601cf568bca8e46c06f51a15fb2 Mon Sep 17 00:00:00 2001 From: benface Date: Mon, 16 Dec 2024 20:01:24 -0500 Subject: [PATCH 08/22] Move Supported Networks out of Developing --- website/pages/ar/{developing => }/supported-networks.json | 0 website/pages/ar/{developing => }/supported-networks.mdx | 0 website/pages/ar/translations.ts | 2 +- website/pages/cs/{developing => }/supported-networks.json | 0 website/pages/cs/{developing => }/supported-networks.mdx | 0 website/pages/cs/translations.ts | 2 +- website/pages/de/{developing => }/supported-networks.json | 0 website/pages/de/{developing => }/supported-networks.mdx | 0 website/pages/de/translations.ts | 2 +- website/pages/en/_meta.js | 1 + website/pages/en/developing/_meta.js | 1 - website/pages/en/{developing => }/supported-networks.json | 0 website/pages/en/{developing => }/supported-networks.mdx | 0 website/pages/en/translations.ts | 2 +- website/pages/es/{developing => }/supported-networks.json | 0 website/pages/es/{developing => }/supported-networks.mdx | 0 website/pages/es/translations.ts | 2 +- website/pages/fr/{developing => }/supported-networks.json | 0 website/pages/fr/{developing => }/supported-networks.mdx | 0 website/pages/fr/translations.ts | 2 +- website/pages/hi/{developing => }/supported-networks.json | 0 website/pages/hi/{developing => }/supported-networks.mdx | 0 website/pages/hi/translations.ts | 2 +- website/pages/it/{developing => }/supported-networks.json | 0 website/pages/it/{developing => }/supported-networks.mdx | 0 website/pages/it/translations.ts | 2 +- website/pages/ja/{developing => }/supported-networks.json | 0 website/pages/ja/{developing => }/supported-networks.mdx | 0 website/pages/ja/translations.ts | 2 +- website/pages/ko/{developing => }/supported-networks.json | 0 website/pages/ko/{developing => }/supported-networks.mdx | 0 website/pages/ko/translations.ts | 2 +- website/pages/mr/{developing => }/supported-networks.json | 0 website/pages/mr/{developing => }/supported-networks.mdx | 0 website/pages/mr/translations.ts | 2 +- website/pages/nl/{developing => }/supported-networks.json | 0 website/pages/nl/{developing => }/supported-networks.mdx | 0 website/pages/nl/translations.ts | 2 +- website/pages/pl/{developing => }/supported-networks.json | 0 website/pages/pl/{developing => }/supported-networks.mdx | 0 website/pages/pl/translations.ts | 2 +- website/pages/pt/{developing => }/supported-networks.json | 0 website/pages/pt/{developing => }/supported-networks.mdx | 0 website/pages/pt/translations.ts | 2 +- website/pages/ro/{developing => }/supported-networks.json | 0 website/pages/ro/{developing => }/supported-networks.mdx | 0 website/pages/ro/translations.ts | 2 +- website/pages/ru/{developing => }/supported-networks.json | 0 website/pages/ru/{developing => }/supported-networks.mdx | 0 website/pages/ru/translations.ts | 2 +- website/pages/sv/{developing => }/supported-networks.json | 0 website/pages/sv/{developing => }/supported-networks.mdx | 0 website/pages/sv/translations.ts | 2 +- website/pages/sw/{developing => }/supported-networks.json | 0 website/pages/sw/{developing => }/supported-networks.mdx | 0 website/pages/sw/translations.ts | 2 +- website/pages/tr/{developing => }/supported-networks.json | 0 website/pages/tr/{developing => }/supported-networks.mdx | 0 website/pages/tr/translations.ts | 2 +- website/pages/uk/{developing => }/supported-networks.json | 0 website/pages/uk/{developing => }/supported-networks.mdx | 0 website/pages/uk/translations.ts | 2 +- website/pages/ur/{developing => }/supported-networks.json | 0 website/pages/ur/{developing => }/supported-networks.mdx | 0 website/pages/ur/translations.ts | 2 +- website/pages/vi/{developing => }/supported-networks.json | 0 website/pages/vi/{developing => }/supported-networks.mdx | 0 website/pages/vi/translations.ts | 2 +- website/pages/zh/{developing => }/supported-networks.json | 0 website/pages/zh/{developing => }/supported-networks.mdx | 0 website/pages/zh/translations.ts | 2 +- 71 files changed, 24 insertions(+), 24 deletions(-) rename website/pages/ar/{developing => }/supported-networks.json (100%) rename website/pages/ar/{developing => }/supported-networks.mdx (100%) rename website/pages/cs/{developing => }/supported-networks.json (100%) rename website/pages/cs/{developing => }/supported-networks.mdx (100%) rename website/pages/de/{developing => }/supported-networks.json (100%) rename website/pages/de/{developing => }/supported-networks.mdx (100%) rename website/pages/en/{developing => }/supported-networks.json (100%) rename website/pages/en/{developing => }/supported-networks.mdx (100%) rename website/pages/es/{developing => }/supported-networks.json (100%) rename website/pages/es/{developing => }/supported-networks.mdx (100%) rename website/pages/fr/{developing => }/supported-networks.json (100%) rename website/pages/fr/{developing => }/supported-networks.mdx (100%) rename website/pages/hi/{developing => }/supported-networks.json (100%) rename website/pages/hi/{developing => }/supported-networks.mdx (100%) rename website/pages/it/{developing => }/supported-networks.json (100%) rename website/pages/it/{developing => }/supported-networks.mdx (100%) rename website/pages/ja/{developing => }/supported-networks.json (100%) rename website/pages/ja/{developing => }/supported-networks.mdx (100%) rename website/pages/ko/{developing => }/supported-networks.json (100%) rename website/pages/ko/{developing => }/supported-networks.mdx (100%) rename website/pages/mr/{developing => }/supported-networks.json (100%) rename website/pages/mr/{developing => }/supported-networks.mdx (100%) rename website/pages/nl/{developing => }/supported-networks.json (100%) rename website/pages/nl/{developing => }/supported-networks.mdx (100%) rename website/pages/pl/{developing => }/supported-networks.json (100%) rename website/pages/pl/{developing => }/supported-networks.mdx (100%) rename website/pages/pt/{developing => }/supported-networks.json (100%) rename website/pages/pt/{developing => }/supported-networks.mdx (100%) rename website/pages/ro/{developing => }/supported-networks.json (100%) rename website/pages/ro/{developing => }/supported-networks.mdx (100%) rename website/pages/ru/{developing => }/supported-networks.json (100%) rename website/pages/ru/{developing => }/supported-networks.mdx (100%) rename website/pages/sv/{developing => }/supported-networks.json (100%) rename website/pages/sv/{developing => }/supported-networks.mdx (100%) rename website/pages/sw/{developing => }/supported-networks.json (100%) rename website/pages/sw/{developing => }/supported-networks.mdx (100%) rename website/pages/tr/{developing => }/supported-networks.json (100%) rename website/pages/tr/{developing => }/supported-networks.mdx (100%) rename website/pages/uk/{developing => }/supported-networks.json (100%) rename website/pages/uk/{developing => }/supported-networks.mdx (100%) rename website/pages/ur/{developing => }/supported-networks.json (100%) rename website/pages/ur/{developing => }/supported-networks.mdx (100%) rename website/pages/vi/{developing => }/supported-networks.json (100%) rename website/pages/vi/{developing => }/supported-networks.mdx (100%) rename website/pages/zh/{developing => }/supported-networks.json (100%) rename website/pages/zh/{developing => }/supported-networks.mdx (100%) diff --git a/website/pages/ar/developing/supported-networks.json b/website/pages/ar/supported-networks.json similarity index 100% rename from website/pages/ar/developing/supported-networks.json rename to website/pages/ar/supported-networks.json diff --git a/website/pages/ar/developing/supported-networks.mdx b/website/pages/ar/supported-networks.mdx similarity index 100% rename from website/pages/ar/developing/supported-networks.mdx rename to website/pages/ar/supported-networks.mdx diff --git a/website/pages/ar/translations.ts b/website/pages/ar/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/ar/translations.ts +++ b/website/pages/ar/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/cs/developing/supported-networks.json b/website/pages/cs/supported-networks.json similarity index 100% rename from website/pages/cs/developing/supported-networks.json rename to website/pages/cs/supported-networks.json diff --git a/website/pages/cs/developing/supported-networks.mdx b/website/pages/cs/supported-networks.mdx similarity index 100% rename from website/pages/cs/developing/supported-networks.mdx rename to website/pages/cs/supported-networks.mdx diff --git a/website/pages/cs/translations.ts b/website/pages/cs/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/cs/translations.ts +++ b/website/pages/cs/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/de/developing/supported-networks.json b/website/pages/de/supported-networks.json similarity index 100% rename from website/pages/de/developing/supported-networks.json rename to website/pages/de/supported-networks.json diff --git a/website/pages/de/developing/supported-networks.mdx b/website/pages/de/supported-networks.mdx similarity index 100% rename from website/pages/de/developing/supported-networks.mdx rename to website/pages/de/supported-networks.mdx diff --git a/website/pages/de/translations.ts b/website/pages/de/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/de/translations.ts +++ b/website/pages/de/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index 926203946230..e56d381a2681 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -1,6 +1,7 @@ export default { index: '', about: '', + 'supported-networks': '', contracts: '', '---1': { type: 'separator', diff --git a/website/pages/en/developing/_meta.js b/website/pages/en/developing/_meta.js index b961003946cc..219e5d2c446f 100644 --- a/website/pages/en/developing/_meta.js +++ b/website/pages/en/developing/_meta.js @@ -1,5 +1,4 @@ export default { - 'supported-networks': '', developing: 'Introduction to Development', subgraphs: '', 'creating-a-subgraph': 'Create a Subgraph', diff --git a/website/pages/en/developing/supported-networks.json b/website/pages/en/supported-networks.json similarity index 100% rename from website/pages/en/developing/supported-networks.json rename to website/pages/en/supported-networks.json diff --git a/website/pages/en/developing/supported-networks.mdx b/website/pages/en/supported-networks.mdx similarity index 100% rename from website/pages/en/developing/supported-networks.mdx rename to website/pages/en/supported-networks.mdx diff --git a/website/pages/en/translations.ts b/website/pages/en/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/en/translations.ts +++ b/website/pages/en/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/es/developing/supported-networks.json b/website/pages/es/supported-networks.json similarity index 100% rename from website/pages/es/developing/supported-networks.json rename to website/pages/es/supported-networks.json diff --git a/website/pages/es/developing/supported-networks.mdx b/website/pages/es/supported-networks.mdx similarity index 100% rename from website/pages/es/developing/supported-networks.mdx rename to website/pages/es/supported-networks.mdx diff --git a/website/pages/es/translations.ts b/website/pages/es/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/es/translations.ts +++ b/website/pages/es/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/fr/developing/supported-networks.json b/website/pages/fr/supported-networks.json similarity index 100% rename from website/pages/fr/developing/supported-networks.json rename to website/pages/fr/supported-networks.json diff --git a/website/pages/fr/developing/supported-networks.mdx b/website/pages/fr/supported-networks.mdx similarity index 100% rename from website/pages/fr/developing/supported-networks.mdx rename to website/pages/fr/supported-networks.mdx diff --git a/website/pages/fr/translations.ts b/website/pages/fr/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/fr/translations.ts +++ b/website/pages/fr/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/hi/developing/supported-networks.json b/website/pages/hi/supported-networks.json similarity index 100% rename from website/pages/hi/developing/supported-networks.json rename to website/pages/hi/supported-networks.json diff --git a/website/pages/hi/developing/supported-networks.mdx b/website/pages/hi/supported-networks.mdx similarity index 100% rename from website/pages/hi/developing/supported-networks.mdx rename to website/pages/hi/supported-networks.mdx diff --git a/website/pages/hi/translations.ts b/website/pages/hi/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/hi/translations.ts +++ b/website/pages/hi/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/it/developing/supported-networks.json b/website/pages/it/supported-networks.json similarity index 100% rename from website/pages/it/developing/supported-networks.json rename to website/pages/it/supported-networks.json diff --git a/website/pages/it/developing/supported-networks.mdx b/website/pages/it/supported-networks.mdx similarity index 100% rename from website/pages/it/developing/supported-networks.mdx rename to website/pages/it/supported-networks.mdx diff --git a/website/pages/it/translations.ts b/website/pages/it/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/it/translations.ts +++ b/website/pages/it/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/ja/developing/supported-networks.json b/website/pages/ja/supported-networks.json similarity index 100% rename from website/pages/ja/developing/supported-networks.json rename to website/pages/ja/supported-networks.json diff --git a/website/pages/ja/developing/supported-networks.mdx b/website/pages/ja/supported-networks.mdx similarity index 100% rename from website/pages/ja/developing/supported-networks.mdx rename to website/pages/ja/supported-networks.mdx diff --git a/website/pages/ja/translations.ts b/website/pages/ja/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/ja/translations.ts +++ b/website/pages/ja/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/ko/developing/supported-networks.json b/website/pages/ko/supported-networks.json similarity index 100% rename from website/pages/ko/developing/supported-networks.json rename to website/pages/ko/supported-networks.json diff --git a/website/pages/ko/developing/supported-networks.mdx b/website/pages/ko/supported-networks.mdx similarity index 100% rename from website/pages/ko/developing/supported-networks.mdx rename to website/pages/ko/supported-networks.mdx diff --git a/website/pages/ko/translations.ts b/website/pages/ko/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/ko/translations.ts +++ b/website/pages/ko/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/mr/developing/supported-networks.json b/website/pages/mr/supported-networks.json similarity index 100% rename from website/pages/mr/developing/supported-networks.json rename to website/pages/mr/supported-networks.json diff --git a/website/pages/mr/developing/supported-networks.mdx b/website/pages/mr/supported-networks.mdx similarity index 100% rename from website/pages/mr/developing/supported-networks.mdx rename to website/pages/mr/supported-networks.mdx diff --git a/website/pages/mr/translations.ts b/website/pages/mr/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/mr/translations.ts +++ b/website/pages/mr/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/nl/developing/supported-networks.json b/website/pages/nl/supported-networks.json similarity index 100% rename from website/pages/nl/developing/supported-networks.json rename to website/pages/nl/supported-networks.json diff --git a/website/pages/nl/developing/supported-networks.mdx b/website/pages/nl/supported-networks.mdx similarity index 100% rename from website/pages/nl/developing/supported-networks.mdx rename to website/pages/nl/supported-networks.mdx diff --git a/website/pages/nl/translations.ts b/website/pages/nl/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/nl/translations.ts +++ b/website/pages/nl/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/pl/developing/supported-networks.json b/website/pages/pl/supported-networks.json similarity index 100% rename from website/pages/pl/developing/supported-networks.json rename to website/pages/pl/supported-networks.json diff --git a/website/pages/pl/developing/supported-networks.mdx b/website/pages/pl/supported-networks.mdx similarity index 100% rename from website/pages/pl/developing/supported-networks.mdx rename to website/pages/pl/supported-networks.mdx diff --git a/website/pages/pl/translations.ts b/website/pages/pl/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/pl/translations.ts +++ b/website/pages/pl/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/pt/developing/supported-networks.json b/website/pages/pt/supported-networks.json similarity index 100% rename from website/pages/pt/developing/supported-networks.json rename to website/pages/pt/supported-networks.json diff --git a/website/pages/pt/developing/supported-networks.mdx b/website/pages/pt/supported-networks.mdx similarity index 100% rename from website/pages/pt/developing/supported-networks.mdx rename to website/pages/pt/supported-networks.mdx diff --git a/website/pages/pt/translations.ts b/website/pages/pt/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/pt/translations.ts +++ b/website/pages/pt/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/ro/developing/supported-networks.json b/website/pages/ro/supported-networks.json similarity index 100% rename from website/pages/ro/developing/supported-networks.json rename to website/pages/ro/supported-networks.json diff --git a/website/pages/ro/developing/supported-networks.mdx b/website/pages/ro/supported-networks.mdx similarity index 100% rename from website/pages/ro/developing/supported-networks.mdx rename to website/pages/ro/supported-networks.mdx diff --git a/website/pages/ro/translations.ts b/website/pages/ro/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/ro/translations.ts +++ b/website/pages/ro/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/ru/developing/supported-networks.json b/website/pages/ru/supported-networks.json similarity index 100% rename from website/pages/ru/developing/supported-networks.json rename to website/pages/ru/supported-networks.json diff --git a/website/pages/ru/developing/supported-networks.mdx b/website/pages/ru/supported-networks.mdx similarity index 100% rename from website/pages/ru/developing/supported-networks.mdx rename to website/pages/ru/supported-networks.mdx diff --git a/website/pages/ru/translations.ts b/website/pages/ru/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/ru/translations.ts +++ b/website/pages/ru/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/sv/developing/supported-networks.json b/website/pages/sv/supported-networks.json similarity index 100% rename from website/pages/sv/developing/supported-networks.json rename to website/pages/sv/supported-networks.json diff --git a/website/pages/sv/developing/supported-networks.mdx b/website/pages/sv/supported-networks.mdx similarity index 100% rename from website/pages/sv/developing/supported-networks.mdx rename to website/pages/sv/supported-networks.mdx diff --git a/website/pages/sv/translations.ts b/website/pages/sv/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/sv/translations.ts +++ b/website/pages/sv/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/sw/developing/supported-networks.json b/website/pages/sw/supported-networks.json similarity index 100% rename from website/pages/sw/developing/supported-networks.json rename to website/pages/sw/supported-networks.json diff --git a/website/pages/sw/developing/supported-networks.mdx b/website/pages/sw/supported-networks.mdx similarity index 100% rename from website/pages/sw/developing/supported-networks.mdx rename to website/pages/sw/supported-networks.mdx diff --git a/website/pages/sw/translations.ts b/website/pages/sw/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/sw/translations.ts +++ b/website/pages/sw/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/tr/developing/supported-networks.json b/website/pages/tr/supported-networks.json similarity index 100% rename from website/pages/tr/developing/supported-networks.json rename to website/pages/tr/supported-networks.json diff --git a/website/pages/tr/developing/supported-networks.mdx b/website/pages/tr/supported-networks.mdx similarity index 100% rename from website/pages/tr/developing/supported-networks.mdx rename to website/pages/tr/supported-networks.mdx diff --git a/website/pages/tr/translations.ts b/website/pages/tr/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/tr/translations.ts +++ b/website/pages/tr/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/uk/developing/supported-networks.json b/website/pages/uk/supported-networks.json similarity index 100% rename from website/pages/uk/developing/supported-networks.json rename to website/pages/uk/supported-networks.json diff --git a/website/pages/uk/developing/supported-networks.mdx b/website/pages/uk/supported-networks.mdx similarity index 100% rename from website/pages/uk/developing/supported-networks.mdx rename to website/pages/uk/supported-networks.mdx diff --git a/website/pages/uk/translations.ts b/website/pages/uk/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/uk/translations.ts +++ b/website/pages/uk/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/ur/developing/supported-networks.json b/website/pages/ur/supported-networks.json similarity index 100% rename from website/pages/ur/developing/supported-networks.json rename to website/pages/ur/supported-networks.json diff --git a/website/pages/ur/developing/supported-networks.mdx b/website/pages/ur/supported-networks.mdx similarity index 100% rename from website/pages/ur/developing/supported-networks.mdx rename to website/pages/ur/supported-networks.mdx diff --git a/website/pages/ur/translations.ts b/website/pages/ur/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/ur/translations.ts +++ b/website/pages/ur/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/vi/developing/supported-networks.json b/website/pages/vi/supported-networks.json similarity index 100% rename from website/pages/vi/developing/supported-networks.json rename to website/pages/vi/supported-networks.json diff --git a/website/pages/vi/developing/supported-networks.mdx b/website/pages/vi/supported-networks.mdx similarity index 100% rename from website/pages/vi/developing/supported-networks.mdx rename to website/pages/vi/supported-networks.mdx diff --git a/website/pages/vi/translations.ts b/website/pages/vi/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/vi/translations.ts +++ b/website/pages/vi/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, diff --git a/website/pages/zh/developing/supported-networks.json b/website/pages/zh/supported-networks.json similarity index 100% rename from website/pages/zh/developing/supported-networks.json rename to website/pages/zh/supported-networks.json diff --git a/website/pages/zh/developing/supported-networks.mdx b/website/pages/zh/supported-networks.mdx similarity index 100% rename from website/pages/zh/developing/supported-networks.mdx rename to website/pages/zh/supported-networks.mdx diff --git a/website/pages/zh/translations.ts b/website/pages/zh/translations.ts index 340f7eeea339..f240cce94778 100644 --- a/website/pages/zh/translations.ts +++ b/website/pages/zh/translations.ts @@ -1,7 +1,7 @@ -import supportedNetworks from './developing/supported-networks.json' import docsearch from './docsearch.json' import global from './global.json' import index from './index.json' +import supportedNetworks from './supported-networks.json' const translations = { global, From dde16c08b54112ce8a458202d3006175a68a743f Mon Sep 17 00:00:00 2001 From: benface Date: Mon, 16 Dec 2024 20:13:09 -0500 Subject: [PATCH 09/22] Tweaks --- ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 website/pages/en/_meta.js | 2 +- website/pages/en/developing/_meta.js | 2 +- website/pages/en/developing/deploying/_meta.js | 2 +- .../developing/deploying/using-subgraph-studio.mdx} | 2 +- ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 .../developing/deploying/using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 .../developing/deploying/using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 ...ploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} | 0 26 files changed, 4 insertions(+), 4 deletions(-) rename website/pages/ar/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/cs/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/de/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/{sw/developing/deploying/deploy-using-subgraph-studio.mdx => en/developing/deploying/using-subgraph-studio.mdx} (99%) rename website/pages/es/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/fr/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/hi/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/it/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/ja/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/{en/developing/deploying/deploy-using-subgraph-studio.mdx => ko/developing/deploying/using-subgraph-studio.mdx} (100%) rename website/pages/mr/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/nl/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/pl/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/pt/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/ro/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/ru/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/sv/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/{ko/developing/deploying/deploy-using-subgraph-studio.mdx => sw/developing/deploying/using-subgraph-studio.mdx} (100%) rename website/pages/tr/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/uk/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/ur/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/vi/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) rename website/pages/zh/developing/deploying/{deploy-using-subgraph-studio.mdx => using-subgraph-studio.mdx} (100%) diff --git a/website/pages/ar/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ar/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ar/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ar/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/cs/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/cs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/cs/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/cs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/de/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/de/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/de/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/de/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index e56d381a2681..dc747d7df3a6 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -46,8 +46,8 @@ export default { type: 'heading', title: 'Resources', }, - network: 'Network', glossary: '', + network: 'Network', 'release-notes': 'Release Notes & Upgrade Guides', archived: 'Archived', } diff --git a/website/pages/en/developing/_meta.js b/website/pages/en/developing/_meta.js index 219e5d2c446f..fb2cb08c1118 100644 --- a/website/pages/en/developing/_meta.js +++ b/website/pages/en/developing/_meta.js @@ -1,7 +1,7 @@ export default { developing: 'Introduction to Development', subgraphs: '', - 'creating-a-subgraph': 'Create a Subgraph', + 'creating-a-subgraph': 'Creating a Subgraph', deploying: 'Deploying', publishing: 'Publishing', managing: 'Managing', diff --git a/website/pages/en/developing/deploying/_meta.js b/website/pages/en/developing/deploying/_meta.js index 6021e41ec7ae..fb67773ec729 100644 --- a/website/pages/en/developing/deploying/_meta.js +++ b/website/pages/en/developing/deploying/_meta.js @@ -1,5 +1,5 @@ export default { - 'deploy-using-subgraph-studio': '', + 'using-subgraph-studio': '', 'subgraph-studio-faqs': '', 'multiple-networks': '', } diff --git a/website/pages/sw/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/en/developing/deploying/using-subgraph-studio.mdx similarity index 99% rename from website/pages/sw/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/en/developing/deploying/using-subgraph-studio.mdx index a3b2f150a79c..3835d29cf548 100644 --- a/website/pages/sw/developing/deploying/deploy-using-subgraph-studio.mdx +++ b/website/pages/en/developing/deploying/using-subgraph-studio.mdx @@ -1,5 +1,5 @@ --- -title: Deploy Using Subgraph Studio +title: Deploying Using Subgraph Studio --- Learn how to deploy your subgraph to Subgraph Studio. diff --git a/website/pages/es/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/es/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/es/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/es/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/fr/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/fr/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/fr/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/fr/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/hi/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/hi/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/hi/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/hi/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/it/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/it/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/it/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/it/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ja/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ja/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ja/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ja/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/en/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ko/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/en/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ko/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/mr/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/mr/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/mr/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/mr/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/nl/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/nl/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/nl/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/nl/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/pl/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/pl/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/pl/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/pl/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/pt/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/pt/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/pt/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/pt/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ro/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ro/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ro/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ro/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ru/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ru/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ru/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ru/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/sv/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/sv/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/sv/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/sv/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ko/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/sw/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ko/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/sw/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/tr/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/tr/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/tr/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/tr/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/uk/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/uk/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/uk/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/uk/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ur/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ur/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ur/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/ur/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/vi/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/vi/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/vi/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/vi/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/zh/developing/deploying/deploy-using-subgraph-studio.mdx b/website/pages/zh/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/zh/developing/deploying/deploy-using-subgraph-studio.mdx rename to website/pages/zh/developing/deploying/using-subgraph-studio.mdx From 0ad12ddef5cbe869f1951274bad4fbc7891bb39e Mon Sep 17 00:00:00 2001 From: Idalith Bustos Date: Tue, 17 Dec 2024 12:43:01 -0800 Subject: [PATCH 10/22] Additional Adjustments --- website/pages/en/developing/_meta.js | 2 +- .../creating-a-subgraph/advanced.mdx | 2 +- website/pages/en/network/_meta.js | 3 +-- website/pages/en/network/benefits.mdx | 2 +- website/pages/en/network/overview.mdx | 21 ------------------- 5 files changed, 4 insertions(+), 26 deletions(-) delete mode 100644 website/pages/en/network/overview.mdx diff --git a/website/pages/en/developing/_meta.js b/website/pages/en/developing/_meta.js index fb2cb08c1118..72fe0cc49af1 100644 --- a/website/pages/en/developing/_meta.js +++ b/website/pages/en/developing/_meta.js @@ -1,7 +1,7 @@ export default { developing: 'Introduction to Development', subgraphs: '', - 'creating-a-subgraph': 'Creating a Subgraph', + 'creating-a-subgraph': 'Creating', deploying: 'Deploying', publishing: 'Publishing', managing: 'Managing', diff --git a/website/pages/en/developing/creating-a-subgraph/advanced.mdx b/website/pages/en/developing/creating-a-subgraph/advanced.mdx index 45acd610f237..7e0ca41c5c18 100644 --- a/website/pages/en/developing/creating-a-subgraph/advanced.mdx +++ b/website/pages/en/developing/creating-a-subgraph/advanced.mdx @@ -1,5 +1,5 @@ --- -title: Advance Subgraph Features +title: Advanced Subgraph Features --- ## Overview diff --git a/website/pages/en/network/_meta.js b/website/pages/en/network/_meta.js index 4cda16e151d4..4e004cf4984a 100644 --- a/website/pages/en/network/_meta.js +++ b/website/pages/en/network/_meta.js @@ -1,6 +1,5 @@ export default { - overview: 'Overview', - benefits: 'Benefits', + benefits: 'The Graph vs Self Hosting', tokenomics: 'Tokenomics', delegating: '', curating: '', diff --git a/website/pages/en/network/benefits.mdx b/website/pages/en/network/benefits.mdx index 7b50daa789a4..51f56543d484 100644 --- a/website/pages/en/network/benefits.mdx +++ b/website/pages/en/network/benefits.mdx @@ -1,5 +1,5 @@ --- -title: The Graph Network vs. Self Hosting +title: The Graph vs. Self Hosting socialImage: https://thegraph.com/docs/img/seo/benefits.jpg --- diff --git a/website/pages/en/network/overview.mdx b/website/pages/en/network/overview.mdx deleted file mode 100644 index 0779d9a6cb00..000000000000 --- a/website/pages/en/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. From 293036fec745b71efa07cc67b28c1f959e8fe827 Mon Sep 17 00:00:00 2001 From: benface Date: Tue, 17 Dec 2024 22:35:07 -0500 Subject: [PATCH 11/22] Tweak scripts --- website/scripts/fix-pages-structure.ts | 2 ++ website/scripts/move-pages.ts | 16 ++++++++++------ 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/website/scripts/fix-pages-structure.ts b/website/scripts/fix-pages-structure.ts index 2b9ae955e70b..8192a93b531e 100644 --- a/website/scripts/fix-pages-structure.ts +++ b/website/scripts/fix-pages-structure.ts @@ -102,6 +102,7 @@ async function main() { (file.endsWith('.md') || file.endsWith('.mdx')), ) .map((file) => path.basename(file, path.extname(file))) + console.log(`Creating meta file ${path.join(SOURCE_LOCALE, directory, META_FILENAME)}`) await fs.writeFile( sourceMetaPath, `export default {\n${filesInDirectory.map((page) => ` '${page}': '',`).join('\n')}\n}\n`, @@ -122,6 +123,7 @@ async function main() { if (FORCE_META || !(await fileExists(translatedMetaPath))) { const depth = path.relative(PAGES_DIRECTORY, translatedDirectory).split(path.sep).length const importPath = path.posix.join('../'.repeat(depth), SOURCE_LOCALE, directory, META_FILENAME) + console.log(`Creating meta file ${path.join(locale, directory, META_FILENAME)}`) await fs.writeFile(translatedMetaPath, `import meta from '${importPath}'\n\nexport default {\n ...meta,\n}\n`) } } diff --git a/website/scripts/move-pages.ts b/website/scripts/move-pages.ts index 543fc7a84d88..e38983e69158 100644 --- a/website/scripts/move-pages.ts +++ b/website/scripts/move-pages.ts @@ -9,6 +9,7 @@ * 2. Moves files in all locales: * - Creates destination directories as needed * - Skips files that don't exist or would be overwritten + * - When moving a directory, moves _meta.js in English and recreates it in other locales * * 3. Runs `fix-pages-structure` to: * - Clean up any orphaned directories @@ -152,11 +153,14 @@ async function main() { const sourceFile = path.join(localeDirectory, sourcePath) const destinationFile = path.join(localeDirectory, destinationPath) - // Skip if source doesn't exist or would overwrite an existing _meta.js - if ( - !(await fileExists(sourceFile)) || - (path.basename(destinationPath) === META_FILENAME && (await fileExists(destinationFile))) - ) { + // Skip if source doesn't exist or destination would be overwritten + if (!(await fileExists(sourceFile)) || (await fileExists(destinationFile))) { + continue + } + + // For translations, skip _meta.js (they'll be recreated by `fix-pages-structure`) + // For English, move _meta.js to preserve customizations + if (locale !== SOURCE_LOCALE && path.basename(destinationPath) === META_FILENAME) { continue } @@ -167,7 +171,7 @@ async function main() { console.log() // Add blank line between locales } - // Run fix-pages-structure to clean up and update meta files + // Run `fix-pages-structure` to clean up and update meta files console.log('\nRunning fix-pages-structure...') await execFileAsync('tsx', ['scripts/fix-pages-structure.ts']) } From 5df6408f1a6a7f76356c464b7363014f2f21d935 Mon Sep 17 00:00:00 2001 From: benface Date: Tue, 17 Dec 2024 22:35:49 -0500 Subject: [PATCH 12/22] Proposing some more nav changes --- website/pages/ar/cookbook/_meta.js | 5 - website/pages/ar/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/ar/developing/deploying/_meta.js | 5 - website/pages/ar/developing/managing/_meta.js | 5 - .../pages/ar/developing/publishing/_meta.js | 5 - website/pages/ar/indexer-tooling/_meta.js | 5 - website/pages/ar/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/ar/{ => indexing}/tap.mdx | 0 website/pages/ar/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/ar/network/_meta.js | 5 - website/pages/ar/network/overview.mdx | 21 - website/pages/ar/querying/_meta.js | 5 - .../pages/ar/querying/graph-client/_meta.js | 5 - website/pages/ar/release-notes/_meta.js | 5 - website/pages/ar/resources/_meta.js | 5 + .../ar/{network => resources}/benefits.mdx | 0 website/pages/ar/{ => resources}/glossary.mdx | 0 .../pages/ar/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/ar/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../ar/{network => resources}/tokenomics.mdx | 0 website/pages/ar/sps/_meta.js | 5 - website/pages/ar/subgraphs/_meta.js | 5 + website/pages/ar/{ => subgraphs}/billing.mdx | 0 website/pages/ar/subgraphs/cookbook/_meta.js | 5 + .../ar/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../ar/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../ar/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../ar/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../ar/{ => subgraphs}/cookbook/near.mdx | 0 .../ar/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/ar/subgraphs/developing/_meta.js | 5 + .../ar/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../ar/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/ar/{ => subgraphs}/explorer.mdx | 0 website/pages/ar/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/ar/{ => subgraphs}/quick-start.mdx | 0 website/pages/ar/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/ar/substreams/sps/_meta.js | 5 + .../ar/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../ar/{ => substreams}/sps/triggers.mdx | 0 website/pages/cs/cookbook/_meta.js | 5 - website/pages/cs/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/cs/developing/deploying/_meta.js | 5 - website/pages/cs/developing/managing/_meta.js | 5 - .../pages/cs/developing/publishing/_meta.js | 5 - website/pages/cs/indexer-tooling/_meta.js | 5 - website/pages/cs/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/cs/{ => indexing}/tap.mdx | 0 website/pages/cs/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/cs/network/_meta.js | 5 - website/pages/cs/network/overview.mdx | 21 - website/pages/cs/querying/_meta.js | 5 - .../pages/cs/querying/graph-client/_meta.js | 5 - website/pages/cs/release-notes/_meta.js | 5 - website/pages/cs/resources/_meta.js | 5 + .../cs/{network => resources}/benefits.mdx | 0 website/pages/cs/{ => resources}/glossary.mdx | 0 .../pages/cs/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/cs/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../cs/{network => resources}/tokenomics.mdx | 0 website/pages/cs/sps/_meta.js | 5 - website/pages/cs/subgraphs/_meta.js | 5 + website/pages/cs/{ => subgraphs}/billing.mdx | 0 website/pages/cs/subgraphs/cookbook/_meta.js | 5 + .../cs/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../cs/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../cs/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../cs/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../cs/{ => subgraphs}/cookbook/near.mdx | 0 .../cs/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/cs/subgraphs/developing/_meta.js | 5 + .../cs/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../cs/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/cs/{ => subgraphs}/explorer.mdx | 0 website/pages/cs/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/cs/{ => subgraphs}/quick-start.mdx | 0 website/pages/cs/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/cs/substreams/sps/_meta.js | 5 + .../cs/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../cs/{ => substreams}/sps/triggers.mdx | 0 website/pages/de/cookbook/_meta.js | 5 - website/pages/de/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/de/developing/deploying/_meta.js | 5 - website/pages/de/developing/managing/_meta.js | 5 - .../pages/de/developing/publishing/_meta.js | 5 - website/pages/de/indexer-tooling/_meta.js | 5 - website/pages/de/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/de/{ => indexing}/tap.mdx | 0 website/pages/de/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/de/network/_meta.js | 5 - website/pages/de/network/overview.mdx | 21 - website/pages/de/querying/_meta.js | 5 - .../pages/de/querying/graph-client/_meta.js | 5 - website/pages/de/release-notes/_meta.js | 5 - website/pages/de/resources/_meta.js | 5 + .../de/{network => resources}/benefits.mdx | 0 website/pages/de/{ => resources}/glossary.mdx | 0 .../pages/de/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/de/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../de/{network => resources}/tokenomics.mdx | 0 website/pages/de/sps/_meta.js | 5 - website/pages/de/subgraphs/_meta.js | 5 + website/pages/de/{ => subgraphs}/billing.mdx | 0 website/pages/de/subgraphs/cookbook/_meta.js | 5 + .../de/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../de/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../de/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../de/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../de/{ => subgraphs}/cookbook/near.mdx | 0 .../de/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/de/subgraphs/developing/_meta.js | 5 + .../de/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../de/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/de/{ => subgraphs}/explorer.mdx | 0 website/pages/de/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/de/{ => subgraphs}/quick-start.mdx | 0 website/pages/de/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/de/substreams/sps/_meta.js | 5 + .../de/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../de/{ => substreams}/sps/triggers.mdx | 0 website/pages/en/_meta.js | 30 +- website/pages/en/developing/managing/_meta.js | 4 - website/pages/en/indexing/_meta.js | 8 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/en/{ => indexing}/tap.mdx | 0 .../tooling}/_meta.js | 0 .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/en/network/_meta.js | 6 - website/pages/en/querying/_meta.js | 11 - website/pages/en/resources/_meta.js | 7 + .../en/{network => resources}/benefits.mdx | 0 website/pages/en/{ => resources}/glossary.mdx | 0 .../en/{ => resources}/release-notes/_meta.js | 0 .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/en/resources/roles/_meta.js | 4 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../en/{network => resources}/tokenomics.mdx | 0 website/pages/en/subgraphs/_meta.js | 8 + website/pages/en/{ => subgraphs}/billing.mdx | 0 .../en/{ => subgraphs}/cookbook/_meta.js | 0 .../en/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../en/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../en/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../en/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../en/{ => subgraphs}/cookbook/near.mdx | 0 .../en/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../en/{ => subgraphs}/developing/_meta.js | 4 +- .../developing/creating}/_meta.js | 0 .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../creating}/graph-ts/[[...slug]].mdx | 0 .../developing/creating}/graph-ts/_meta.js | 2 +- .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../developing/deploying/_meta.js | 0 .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../en/subgraphs/developing/managing/_meta.js | 4 + .../managing/deleting-a-subgraph.mdx} | 2 +- .../managing/transferring-a-subgraph.mdx} | 2 +- .../developing/publishing/_meta.js | 0 .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/en/{ => subgraphs}/explorer.mdx | 0 website/pages/en/subgraphs/querying/_meta.js | 11 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../querying/graph-client/[[...slug]].mdx | 0 .../querying/graph-client/_meta.js | 2 +- .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/en/{ => subgraphs}/quick-start.mdx | 0 website/pages/en/substreams/_meta.js | 4 + .../introduction.mdx} | 0 .../pages/en/{ => substreams}/sps/_meta.js | 0 .../en/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../en/{ => substreams}/sps/triggers.mdx | 0 website/pages/es/cookbook/_meta.js | 5 - website/pages/es/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/es/developing/deploying/_meta.js | 5 - website/pages/es/developing/managing/_meta.js | 5 - .../pages/es/developing/publishing/_meta.js | 5 - website/pages/es/indexer-tooling/_meta.js | 5 - website/pages/es/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/es/{ => indexing}/tap.mdx | 0 website/pages/es/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/es/network/_meta.js | 5 - website/pages/es/network/overview.mdx | 21 - website/pages/es/querying/_meta.js | 5 - .../pages/es/querying/graph-client/_meta.js | 5 - website/pages/es/release-notes/_meta.js | 5 - website/pages/es/resources/_meta.js | 5 + .../es/{network => resources}/benefits.mdx | 0 website/pages/es/{ => resources}/glossary.mdx | 0 .../pages/es/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/es/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../es/{network => resources}/tokenomics.mdx | 0 website/pages/es/sps/_meta.js | 5 - website/pages/es/subgraphs/_meta.js | 5 + website/pages/es/{ => subgraphs}/billing.mdx | 0 website/pages/es/subgraphs/cookbook/_meta.js | 5 + .../es/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../es/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../es/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../es/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../es/{ => subgraphs}/cookbook/near.mdx | 0 .../es/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/es/subgraphs/developing/_meta.js | 5 + .../es/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../es/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/es/{ => subgraphs}/explorer.mdx | 0 website/pages/es/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/es/{ => subgraphs}/quick-start.mdx | 0 website/pages/es/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/es/substreams/sps/_meta.js | 5 + .../es/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../es/{ => substreams}/sps/triggers.mdx | 0 website/pages/fr/cookbook/_meta.js | 5 - website/pages/fr/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/fr/developing/deploying/_meta.js | 5 - website/pages/fr/developing/managing/_meta.js | 5 - .../pages/fr/developing/publishing/_meta.js | 5 - website/pages/fr/indexer-tooling/_meta.js | 5 - website/pages/fr/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/fr/{ => indexing}/tap.mdx | 0 website/pages/fr/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/fr/network/_meta.js | 5 - website/pages/fr/network/overview.mdx | 21 - website/pages/fr/querying/_meta.js | 5 - .../pages/fr/querying/graph-client/_meta.js | 5 - website/pages/fr/release-notes/_meta.js | 5 - website/pages/fr/resources/_meta.js | 5 + .../fr/{network => resources}/benefits.mdx | 0 website/pages/fr/{ => resources}/glossary.mdx | 0 .../pages/fr/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/fr/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../fr/{network => resources}/tokenomics.mdx | 0 website/pages/fr/sps/_meta.js | 5 - website/pages/fr/subgraphs/_meta.js | 5 + website/pages/fr/{ => subgraphs}/billing.mdx | 0 website/pages/fr/subgraphs/cookbook/_meta.js | 5 + .../fr/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../fr/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../fr/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../fr/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../fr/{ => subgraphs}/cookbook/near.mdx | 0 .../fr/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/fr/subgraphs/developing/_meta.js | 5 + .../fr/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../fr/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/fr/{ => subgraphs}/explorer.mdx | 0 website/pages/fr/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/fr/{ => subgraphs}/quick-start.mdx | 0 website/pages/fr/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/fr/substreams/sps/_meta.js | 5 + .../fr/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../fr/{ => substreams}/sps/triggers.mdx | 0 website/pages/hi/cookbook/_meta.js | 5 - website/pages/hi/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/hi/developing/deploying/_meta.js | 5 - website/pages/hi/developing/managing/_meta.js | 5 - .../pages/hi/developing/publishing/_meta.js | 5 - website/pages/hi/indexer-tooling/_meta.js | 5 - website/pages/hi/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/hi/{ => indexing}/tap.mdx | 0 website/pages/hi/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/hi/network/_meta.js | 5 - website/pages/hi/network/overview.mdx | 21 - website/pages/hi/querying/_meta.js | 5 - .../pages/hi/querying/graph-client/_meta.js | 5 - website/pages/hi/release-notes/_meta.js | 5 - website/pages/hi/resources/_meta.js | 5 + .../hi/{network => resources}/benefits.mdx | 0 website/pages/hi/{ => resources}/glossary.mdx | 0 .../pages/hi/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/hi/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../hi/{network => resources}/tokenomics.mdx | 0 website/pages/hi/sps/_meta.js | 5 - website/pages/hi/subgraphs/_meta.js | 5 + website/pages/hi/{ => subgraphs}/billing.mdx | 0 website/pages/hi/subgraphs/cookbook/_meta.js | 5 + .../hi/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../hi/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../hi/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../hi/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../hi/{ => subgraphs}/cookbook/near.mdx | 0 .../hi/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/hi/subgraphs/developing/_meta.js | 5 + .../hi/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../hi/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/hi/{ => subgraphs}/explorer.mdx | 0 website/pages/hi/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/hi/{ => subgraphs}/quick-start.mdx | 0 website/pages/hi/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/hi/substreams/sps/_meta.js | 5 + .../hi/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../hi/{ => substreams}/sps/triggers.mdx | 0 website/pages/it/cookbook/_meta.js | 5 - website/pages/it/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/it/developing/deploying/_meta.js | 5 - website/pages/it/developing/managing/_meta.js | 5 - .../pages/it/developing/publishing/_meta.js | 5 - website/pages/it/indexer-tooling/_meta.js | 5 - website/pages/it/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/it/{ => indexing}/tap.mdx | 0 website/pages/it/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/it/network/_meta.js | 5 - website/pages/it/network/overview.mdx | 21 - website/pages/it/querying/_meta.js | 5 - .../pages/it/querying/graph-client/_meta.js | 5 - website/pages/it/release-notes/_meta.js | 5 - website/pages/it/resources/_meta.js | 5 + .../it/{network => resources}/benefits.mdx | 0 website/pages/it/{ => resources}/glossary.mdx | 0 .../pages/it/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/it/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../it/{network => resources}/tokenomics.mdx | 0 website/pages/it/sps/_meta.js | 5 - website/pages/it/subgraphs/_meta.js | 5 + website/pages/it/{ => subgraphs}/billing.mdx | 0 website/pages/it/subgraphs/cookbook/_meta.js | 5 + .../it/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../it/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../it/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../it/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../it/{ => subgraphs}/cookbook/near.mdx | 0 .../it/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/it/subgraphs/developing/_meta.js | 5 + .../it/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../it/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/it/{ => subgraphs}/explorer.mdx | 0 website/pages/it/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/it/{ => subgraphs}/quick-start.mdx | 0 website/pages/it/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/it/substreams/sps/_meta.js | 5 + .../it/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../it/{ => substreams}/sps/triggers.mdx | 0 website/pages/ja/cookbook/_meta.js | 5 - website/pages/ja/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/ja/developing/deploying/_meta.js | 5 - website/pages/ja/developing/managing/_meta.js | 5 - .../pages/ja/developing/publishing/_meta.js | 5 - website/pages/ja/indexer-tooling/_meta.js | 5 - website/pages/ja/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/ja/{ => indexing}/tap.mdx | 0 website/pages/ja/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/ja/network/_meta.js | 5 - website/pages/ja/network/overview.mdx | 21 - website/pages/ja/querying/_meta.js | 5 - .../pages/ja/querying/graph-client/_meta.js | 5 - website/pages/ja/release-notes/_meta.js | 5 - website/pages/ja/resources/_meta.js | 5 + .../ja/{network => resources}/benefits.mdx | 0 website/pages/ja/{ => resources}/glossary.mdx | 0 .../pages/ja/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/ja/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../ja/{network => resources}/tokenomics.mdx | 0 website/pages/ja/sps/_meta.js | 5 - website/pages/ja/subgraphs/_meta.js | 5 + website/pages/ja/{ => subgraphs}/billing.mdx | 0 website/pages/ja/subgraphs/cookbook/_meta.js | 5 + .../ja/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../ja/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../ja/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../ja/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../ja/{ => subgraphs}/cookbook/near.mdx | 0 .../ja/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/ja/subgraphs/developing/_meta.js | 5 + .../ja/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../ja/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/ja/{ => subgraphs}/explorer.mdx | 0 website/pages/ja/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/ja/{ => subgraphs}/quick-start.mdx | 0 website/pages/ja/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/ja/substreams/sps/_meta.js | 5 + .../ja/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../ja/{ => substreams}/sps/triggers.mdx | 0 website/pages/ko/cookbook/_meta.js | 5 - website/pages/ko/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/ko/developing/deploying/_meta.js | 5 - website/pages/ko/developing/managing/_meta.js | 5 - .../pages/ko/developing/publishing/_meta.js | 5 - website/pages/ko/indexer-tooling/_meta.js | 5 - website/pages/ko/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/ko/{ => indexing}/tap.mdx | 0 website/pages/ko/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/ko/network/_meta.js | 5 - website/pages/ko/network/overview.mdx | 21 - website/pages/ko/querying/_meta.js | 5 - .../pages/ko/querying/graph-client/_meta.js | 5 - website/pages/ko/release-notes/_meta.js | 5 - website/pages/ko/resources/_meta.js | 5 + .../ko/{network => resources}/benefits.mdx | 0 website/pages/ko/{ => resources}/glossary.mdx | 0 .../pages/ko/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/ko/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../ko/{network => resources}/tokenomics.mdx | 0 website/pages/ko/sps/_meta.js | 5 - website/pages/ko/subgraphs/_meta.js | 5 + website/pages/ko/{ => subgraphs}/billing.mdx | 0 website/pages/ko/subgraphs/cookbook/_meta.js | 5 + .../ko/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../ko/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../ko/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../ko/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../ko/{ => subgraphs}/cookbook/near.mdx | 0 .../ko/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/ko/subgraphs/developing/_meta.js | 5 + .../ko/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../ko/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/ko/{ => subgraphs}/explorer.mdx | 0 website/pages/ko/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/ko/{ => subgraphs}/quick-start.mdx | 0 website/pages/ko/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/ko/substreams/sps/_meta.js | 5 + .../ko/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../ko/{ => substreams}/sps/triggers.mdx | 0 website/pages/mr/cookbook/_meta.js | 5 - website/pages/mr/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/mr/developing/deploying/_meta.js | 5 - website/pages/mr/developing/managing/_meta.js | 5 - .../pages/mr/developing/publishing/_meta.js | 5 - website/pages/mr/indexer-tooling/_meta.js | 5 - website/pages/mr/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/mr/{ => indexing}/tap.mdx | 0 website/pages/mr/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/mr/network/_meta.js | 5 - website/pages/mr/network/overview.mdx | 21 - website/pages/mr/querying/_meta.js | 5 - .../pages/mr/querying/graph-client/_meta.js | 5 - website/pages/mr/release-notes/_meta.js | 5 - website/pages/mr/resources/_meta.js | 5 + .../mr/{network => resources}/benefits.mdx | 0 website/pages/mr/{ => resources}/glossary.mdx | 0 .../pages/mr/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/mr/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../mr/{network => resources}/tokenomics.mdx | 0 website/pages/mr/sps/_meta.js | 5 - website/pages/mr/subgraphs/_meta.js | 5 + website/pages/mr/{ => subgraphs}/billing.mdx | 0 website/pages/mr/subgraphs/cookbook/_meta.js | 5 + .../mr/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../mr/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../mr/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../mr/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../mr/{ => subgraphs}/cookbook/near.mdx | 0 .../mr/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/mr/subgraphs/developing/_meta.js | 5 + .../mr/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../mr/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/mr/{ => subgraphs}/explorer.mdx | 0 website/pages/mr/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/mr/{ => subgraphs}/quick-start.mdx | 0 website/pages/mr/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/mr/substreams/sps/_meta.js | 5 + .../mr/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../mr/{ => substreams}/sps/triggers.mdx | 0 website/pages/nl/cookbook/_meta.js | 5 - website/pages/nl/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/nl/developing/deploying/_meta.js | 5 - website/pages/nl/developing/managing/_meta.js | 5 - .../pages/nl/developing/publishing/_meta.js | 5 - website/pages/nl/indexer-tooling/_meta.js | 5 - website/pages/nl/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/nl/{ => indexing}/tap.mdx | 0 website/pages/nl/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/nl/network/_meta.js | 5 - website/pages/nl/network/overview.mdx | 21 - website/pages/nl/querying/_meta.js | 5 - .../pages/nl/querying/graph-client/_meta.js | 5 - website/pages/nl/release-notes/_meta.js | 5 - website/pages/nl/resources/_meta.js | 5 + .../nl/{network => resources}/benefits.mdx | 0 website/pages/nl/{ => resources}/glossary.mdx | 0 .../pages/nl/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/nl/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../nl/{network => resources}/tokenomics.mdx | 0 website/pages/nl/sps/_meta.js | 5 - website/pages/nl/subgraphs/_meta.js | 5 + website/pages/nl/{ => subgraphs}/billing.mdx | 0 website/pages/nl/subgraphs/cookbook/_meta.js | 5 + .../nl/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../nl/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../nl/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../nl/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../nl/{ => subgraphs}/cookbook/near.mdx | 0 .../nl/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/nl/subgraphs/developing/_meta.js | 5 + .../nl/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../nl/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/nl/{ => subgraphs}/explorer.mdx | 0 website/pages/nl/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/nl/{ => subgraphs}/quick-start.mdx | 0 website/pages/nl/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/nl/substreams/sps/_meta.js | 5 + .../nl/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../nl/{ => substreams}/sps/triggers.mdx | 0 website/pages/pl/cookbook/_meta.js | 5 - website/pages/pl/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/pl/developing/deploying/_meta.js | 5 - website/pages/pl/developing/managing/_meta.js | 5 - .../pages/pl/developing/publishing/_meta.js | 5 - website/pages/pl/indexer-tooling/_meta.js | 5 - website/pages/pl/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/pl/{ => indexing}/tap.mdx | 0 website/pages/pl/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/pl/network/_meta.js | 5 - website/pages/pl/network/overview.mdx | 21 - website/pages/pl/querying/_meta.js | 5 - .../pages/pl/querying/graph-client/_meta.js | 5 - website/pages/pl/release-notes/_meta.js | 5 - website/pages/pl/resources/_meta.js | 5 + .../pl/{network => resources}/benefits.mdx | 0 website/pages/pl/{ => resources}/glossary.mdx | 0 .../pages/pl/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/pl/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../pl/{network => resources}/tokenomics.mdx | 0 website/pages/pl/sps/_meta.js | 5 - website/pages/pl/subgraphs/_meta.js | 5 + website/pages/pl/{ => subgraphs}/billing.mdx | 0 website/pages/pl/subgraphs/cookbook/_meta.js | 5 + .../pl/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../pl/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../pl/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../pl/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../pl/{ => subgraphs}/cookbook/near.mdx | 0 .../pl/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/pl/subgraphs/developing/_meta.js | 5 + .../pl/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../pl/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/pl/{ => subgraphs}/explorer.mdx | 0 website/pages/pl/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/pl/{ => subgraphs}/quick-start.mdx | 0 website/pages/pl/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/pl/substreams/sps/_meta.js | 5 + .../pl/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../pl/{ => substreams}/sps/triggers.mdx | 0 website/pages/pt/cookbook/_meta.js | 5 - website/pages/pt/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/pt/developing/deploying/_meta.js | 5 - website/pages/pt/developing/managing/_meta.js | 5 - .../pages/pt/developing/publishing/_meta.js | 5 - website/pages/pt/indexer-tooling/_meta.js | 5 - website/pages/pt/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/pt/{ => indexing}/tap.mdx | 0 website/pages/pt/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/pt/network/_meta.js | 5 - website/pages/pt/network/overview.mdx | 21 - website/pages/pt/querying/_meta.js | 5 - .../pages/pt/querying/graph-client/_meta.js | 5 - website/pages/pt/release-notes/_meta.js | 5 - website/pages/pt/resources/_meta.js | 5 + .../pt/{network => resources}/benefits.mdx | 0 website/pages/pt/{ => resources}/glossary.mdx | 0 .../pages/pt/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/pt/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../pt/{network => resources}/tokenomics.mdx | 0 website/pages/pt/sps/_meta.js | 5 - website/pages/pt/subgraphs/_meta.js | 5 + website/pages/pt/{ => subgraphs}/billing.mdx | 0 website/pages/pt/subgraphs/cookbook/_meta.js | 5 + .../pt/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../pt/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../pt/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../pt/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../pt/{ => subgraphs}/cookbook/near.mdx | 0 .../pt/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/pt/subgraphs/developing/_meta.js | 5 + .../pt/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../pt/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/pt/{ => subgraphs}/explorer.mdx | 0 website/pages/pt/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/pt/{ => subgraphs}/quick-start.mdx | 0 website/pages/pt/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/pt/substreams/sps/_meta.js | 5 + .../pt/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../pt/{ => substreams}/sps/triggers.mdx | 0 website/pages/ro/cookbook/_meta.js | 5 - website/pages/ro/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/ro/developing/deploying/_meta.js | 5 - website/pages/ro/developing/managing/_meta.js | 5 - .../pages/ro/developing/publishing/_meta.js | 5 - website/pages/ro/indexer-tooling/_meta.js | 5 - website/pages/ro/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/ro/{ => indexing}/tap.mdx | 0 website/pages/ro/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/ro/network/_meta.js | 5 - website/pages/ro/network/overview.mdx | 21 - website/pages/ro/querying/_meta.js | 5 - .../pages/ro/querying/graph-client/_meta.js | 5 - website/pages/ro/release-notes/_meta.js | 5 - website/pages/ro/resources/_meta.js | 5 + .../ro/{network => resources}/benefits.mdx | 0 website/pages/ro/{ => resources}/glossary.mdx | 0 .../pages/ro/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/ro/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../ro/{network => resources}/tokenomics.mdx | 0 website/pages/ro/sps/_meta.js | 5 - website/pages/ro/subgraphs/_meta.js | 5 + website/pages/ro/{ => subgraphs}/billing.mdx | 0 website/pages/ro/subgraphs/cookbook/_meta.js | 5 + .../ro/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../ro/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../ro/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../ro/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../ro/{ => subgraphs}/cookbook/near.mdx | 0 .../ro/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/ro/subgraphs/developing/_meta.js | 5 + .../ro/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../ro/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/ro/{ => subgraphs}/explorer.mdx | 0 website/pages/ro/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/ro/{ => subgraphs}/quick-start.mdx | 0 website/pages/ro/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/ro/substreams/sps/_meta.js | 5 + .../ro/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../ro/{ => substreams}/sps/triggers.mdx | 0 website/pages/ru/cookbook/_meta.js | 5 - website/pages/ru/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/ru/developing/deploying/_meta.js | 5 - website/pages/ru/developing/managing/_meta.js | 5 - .../pages/ru/developing/publishing/_meta.js | 5 - website/pages/ru/indexer-tooling/_meta.js | 5 - website/pages/ru/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/ru/{ => indexing}/tap.mdx | 0 website/pages/ru/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/ru/network/_meta.js | 5 - website/pages/ru/network/overview.mdx | 21 - website/pages/ru/querying/_meta.js | 5 - .../pages/ru/querying/graph-client/_meta.js | 5 - website/pages/ru/release-notes/_meta.js | 5 - website/pages/ru/resources/_meta.js | 5 + .../ru/{network => resources}/benefits.mdx | 0 website/pages/ru/{ => resources}/glossary.mdx | 0 .../pages/ru/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/ru/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../ru/{network => resources}/tokenomics.mdx | 0 website/pages/ru/sps/_meta.js | 5 - website/pages/ru/subgraphs/_meta.js | 5 + website/pages/ru/{ => subgraphs}/billing.mdx | 0 website/pages/ru/subgraphs/cookbook/_meta.js | 5 + .../ru/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../ru/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../ru/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../ru/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../ru/{ => subgraphs}/cookbook/near.mdx | 0 .../ru/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/ru/subgraphs/developing/_meta.js | 5 + .../ru/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../ru/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/ru/{ => subgraphs}/explorer.mdx | 0 website/pages/ru/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/ru/{ => subgraphs}/quick-start.mdx | 0 website/pages/ru/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/ru/substreams/sps/_meta.js | 5 + .../ru/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../ru/{ => substreams}/sps/triggers.mdx | 0 website/pages/sv/cookbook/_meta.js | 5 - website/pages/sv/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/sv/developing/deploying/_meta.js | 5 - website/pages/sv/developing/managing/_meta.js | 5 - .../pages/sv/developing/publishing/_meta.js | 5 - website/pages/sv/indexer-tooling/_meta.js | 5 - website/pages/sv/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/sv/{ => indexing}/tap.mdx | 0 website/pages/sv/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/sv/network/_meta.js | 5 - website/pages/sv/network/overview.mdx | 21 - website/pages/sv/querying/_meta.js | 5 - .../pages/sv/querying/graph-client/_meta.js | 5 - website/pages/sv/release-notes/_meta.js | 5 - website/pages/sv/resources/_meta.js | 5 + .../sv/{network => resources}/benefits.mdx | 0 website/pages/sv/{ => resources}/glossary.mdx | 0 .../pages/sv/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/sv/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../sv/{network => resources}/tokenomics.mdx | 0 website/pages/sv/sps/_meta.js | 5 - website/pages/sv/subgraphs/_meta.js | 5 + website/pages/sv/{ => subgraphs}/billing.mdx | 0 website/pages/sv/subgraphs/cookbook/_meta.js | 5 + .../sv/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../sv/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../sv/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../sv/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../sv/{ => subgraphs}/cookbook/near.mdx | 0 .../sv/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/sv/subgraphs/developing/_meta.js | 5 + .../sv/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../sv/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/sv/{ => subgraphs}/explorer.mdx | 0 website/pages/sv/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/sv/{ => subgraphs}/quick-start.mdx | 0 website/pages/sv/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/sv/substreams/sps/_meta.js | 5 + .../sv/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../sv/{ => substreams}/sps/triggers.mdx | 0 website/pages/sw/cookbook/_meta.js | 5 - website/pages/sw/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/sw/developing/deploying/_meta.js | 5 - website/pages/sw/developing/managing/_meta.js | 5 - .../pages/sw/developing/publishing/_meta.js | 5 - website/pages/sw/indexer-tooling/_meta.js | 5 - website/pages/sw/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/sw/{ => indexing}/tap.mdx | 0 website/pages/sw/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/sw/network/_meta.js | 5 - website/pages/sw/network/overview.mdx | 21 - website/pages/sw/querying/_meta.js | 5 - .../pages/sw/querying/graph-client/_meta.js | 5 - website/pages/sw/release-notes/_meta.js | 5 - website/pages/sw/resources/_meta.js | 5 + .../sw/{network => resources}/benefits.mdx | 0 website/pages/sw/{ => resources}/glossary.mdx | 0 .../pages/sw/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/sw/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../sw/{network => resources}/tokenomics.mdx | 0 website/pages/sw/sps/_meta.js | 5 - website/pages/sw/subgraphs/_meta.js | 5 + website/pages/sw/{ => subgraphs}/billing.mdx | 0 website/pages/sw/subgraphs/cookbook/_meta.js | 5 + .../sw/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../sw/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../sw/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../sw/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../sw/{ => subgraphs}/cookbook/near.mdx | 0 .../sw/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/sw/subgraphs/developing/_meta.js | 5 + .../sw/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../sw/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/sw/{ => subgraphs}/explorer.mdx | 0 website/pages/sw/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/sw/{ => subgraphs}/quick-start.mdx | 0 website/pages/sw/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/sw/substreams/sps/_meta.js | 5 + .../sw/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../sw/{ => substreams}/sps/triggers.mdx | 0 website/pages/tr/cookbook/_meta.js | 5 - website/pages/tr/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/tr/developing/deploying/_meta.js | 5 - website/pages/tr/developing/managing/_meta.js | 5 - .../pages/tr/developing/publishing/_meta.js | 5 - website/pages/tr/indexer-tooling/_meta.js | 5 - website/pages/tr/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/tr/{ => indexing}/tap.mdx | 0 website/pages/tr/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/tr/network/_meta.js | 5 - website/pages/tr/network/overview.mdx | 21 - website/pages/tr/querying/_meta.js | 5 - .../pages/tr/querying/graph-client/_meta.js | 5 - website/pages/tr/release-notes/_meta.js | 5 - website/pages/tr/resources/_meta.js | 5 + .../tr/{network => resources}/benefits.mdx | 0 website/pages/tr/{ => resources}/glossary.mdx | 0 .../pages/tr/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/tr/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../tr/{network => resources}/tokenomics.mdx | 0 website/pages/tr/sps/_meta.js | 5 - website/pages/tr/subgraphs/_meta.js | 5 + website/pages/tr/{ => subgraphs}/billing.mdx | 0 website/pages/tr/subgraphs/cookbook/_meta.js | 5 + .../tr/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../tr/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../tr/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../tr/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../tr/{ => subgraphs}/cookbook/near.mdx | 0 .../tr/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/tr/subgraphs/developing/_meta.js | 5 + .../tr/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../tr/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/tr/{ => subgraphs}/explorer.mdx | 0 website/pages/tr/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/tr/{ => subgraphs}/quick-start.mdx | 0 website/pages/tr/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/tr/substreams/sps/_meta.js | 5 + .../tr/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../tr/{ => substreams}/sps/triggers.mdx | 0 website/pages/uk/cookbook/_meta.js | 5 - website/pages/uk/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/uk/developing/deploying/_meta.js | 5 - website/pages/uk/developing/managing/_meta.js | 5 - .../pages/uk/developing/publishing/_meta.js | 5 - website/pages/uk/indexer-tooling/_meta.js | 5 - website/pages/uk/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/uk/{ => indexing}/tap.mdx | 0 website/pages/uk/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/uk/network/_meta.js | 5 - website/pages/uk/network/overview.mdx | 21 - website/pages/uk/querying/_meta.js | 5 - .../pages/uk/querying/graph-client/_meta.js | 5 - website/pages/uk/release-notes/_meta.js | 5 - website/pages/uk/resources/_meta.js | 5 + .../uk/{network => resources}/benefits.mdx | 0 website/pages/uk/{ => resources}/glossary.mdx | 0 .../pages/uk/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/uk/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../uk/{network => resources}/tokenomics.mdx | 0 website/pages/uk/sps/_meta.js | 5 - website/pages/uk/subgraphs/_meta.js | 5 + website/pages/uk/{ => subgraphs}/billing.mdx | 0 website/pages/uk/subgraphs/cookbook/_meta.js | 5 + .../uk/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../uk/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../uk/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../uk/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../uk/{ => subgraphs}/cookbook/near.mdx | 0 .../uk/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/uk/subgraphs/developing/_meta.js | 5 + .../uk/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../uk/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/uk/{ => subgraphs}/explorer.mdx | 0 website/pages/uk/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/uk/{ => subgraphs}/quick-start.mdx | 0 website/pages/uk/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/uk/substreams/sps/_meta.js | 5 + .../uk/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../uk/{ => substreams}/sps/triggers.mdx | 0 website/pages/ur/cookbook/_meta.js | 5 - website/pages/ur/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/ur/developing/deploying/_meta.js | 5 - website/pages/ur/developing/managing/_meta.js | 5 - .../pages/ur/developing/publishing/_meta.js | 5 - website/pages/ur/indexer-tooling/_meta.js | 5 - website/pages/ur/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/ur/{ => indexing}/tap.mdx | 0 website/pages/ur/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/ur/network/_meta.js | 5 - website/pages/ur/network/overview.mdx | 21 - website/pages/ur/querying/_meta.js | 5 - .../pages/ur/querying/graph-client/_meta.js | 5 - website/pages/ur/release-notes/_meta.js | 5 - website/pages/ur/resources/_meta.js | 5 + .../ur/{network => resources}/benefits.mdx | 0 website/pages/ur/{ => resources}/glossary.mdx | 0 .../pages/ur/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/ur/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../ur/{network => resources}/tokenomics.mdx | 0 website/pages/ur/sps/_meta.js | 5 - website/pages/ur/subgraphs/_meta.js | 5 + website/pages/ur/{ => subgraphs}/billing.mdx | 0 website/pages/ur/subgraphs/cookbook/_meta.js | 5 + .../ur/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../ur/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../ur/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../ur/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../ur/{ => subgraphs}/cookbook/near.mdx | 0 .../ur/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/ur/subgraphs/developing/_meta.js | 5 + .../ur/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../ur/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/ur/{ => subgraphs}/explorer.mdx | 0 website/pages/ur/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/ur/{ => subgraphs}/quick-start.mdx | 0 website/pages/ur/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/ur/substreams/sps/_meta.js | 5 + .../ur/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../ur/{ => substreams}/sps/triggers.mdx | 0 website/pages/vi/cookbook/_meta.js | 5 - website/pages/vi/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/vi/developing/deploying/_meta.js | 5 - website/pages/vi/developing/managing/_meta.js | 5 - .../pages/vi/developing/publishing/_meta.js | 5 - website/pages/vi/indexer-tooling/_meta.js | 5 - website/pages/vi/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/vi/{ => indexing}/tap.mdx | 0 website/pages/vi/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/vi/network/_meta.js | 5 - website/pages/vi/network/overview.mdx | 21 - website/pages/vi/querying/_meta.js | 5 - .../pages/vi/querying/graph-client/_meta.js | 5 - website/pages/vi/release-notes/_meta.js | 5 - website/pages/vi/resources/_meta.js | 5 + .../vi/{network => resources}/benefits.mdx | 0 website/pages/vi/{ => resources}/glossary.mdx | 0 .../pages/vi/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/vi/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../vi/{network => resources}/tokenomics.mdx | 0 website/pages/vi/sps/_meta.js | 5 - website/pages/vi/subgraphs/_meta.js | 5 + website/pages/vi/{ => subgraphs}/billing.mdx | 0 website/pages/vi/subgraphs/cookbook/_meta.js | 5 + .../vi/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../vi/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../vi/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../vi/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../vi/{ => subgraphs}/cookbook/near.mdx | 0 .../vi/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/vi/subgraphs/developing/_meta.js | 5 + .../vi/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../vi/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/vi/{ => subgraphs}/explorer.mdx | 0 website/pages/vi/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/vi/{ => subgraphs}/quick-start.mdx | 0 website/pages/vi/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/vi/substreams/sps/_meta.js | 5 + .../vi/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../vi/{ => substreams}/sps/triggers.mdx | 0 website/pages/zh/cookbook/_meta.js | 5 - website/pages/zh/developing/_meta.js | 5 - .../developing/creating-a-subgraph/_meta.js | 5 - .../creating-a-subgraph/graph-ts/_meta.js | 5 - .../pages/zh/developing/deploying/_meta.js | 5 - website/pages/zh/developing/managing/_meta.js | 5 - .../pages/zh/developing/publishing/_meta.js | 5 - website/pages/zh/indexer-tooling/_meta.js | 5 - website/pages/zh/indexing/_meta.js | 5 + .../chain-integration-overview.mdx | 0 .../introduction.mdx} | 0 .../{ => indexing}/new-chain-integration.mdx | 0 .../supported-network-requirements.mdx | 0 website/pages/zh/{ => indexing}/tap.mdx | 0 website/pages/zh/indexing/tooling/_meta.js | 5 + .../tooling}/firehose.mdx | 0 .../tooling}/graphcast.mdx | 0 .../tooling}/operating-graph-node.mdx | 0 website/pages/zh/network/_meta.js | 5 - website/pages/zh/network/overview.mdx | 21 - website/pages/zh/querying/_meta.js | 5 - .../pages/zh/querying/graph-client/_meta.js | 5 - website/pages/zh/release-notes/_meta.js | 5 - website/pages/zh/resources/_meta.js | 5 + .../zh/{network => resources}/benefits.mdx | 0 website/pages/zh/{ => resources}/glossary.mdx | 0 .../pages/zh/resources/release-notes/_meta.js | 5 + .../assemblyscript-migration-guide.mdx | 0 .../graphql-validations-migration-guide.mdx | 0 website/pages/zh/resources/roles/_meta.js | 5 + .../{network => resources/roles}/curating.mdx | 0 .../roles}/delegating.mdx | 0 .../zh/{network => resources}/tokenomics.mdx | 0 website/pages/zh/sps/_meta.js | 5 - website/pages/zh/subgraphs/_meta.js | 5 + website/pages/zh/{ => subgraphs}/billing.mdx | 0 website/pages/zh/subgraphs/cookbook/_meta.js | 5 + .../zh/{ => subgraphs}/cookbook/arweave.mdx | 0 .../cookbook/avoid-eth-calls.mdx | 0 .../zh/{ => subgraphs}/cookbook/cosmos.mdx | 0 .../{ => subgraphs}/cookbook/derivedfrom.mdx | 0 .../zh/{ => subgraphs}/cookbook/enums.mdx | 0 .../cookbook/grafting-hotfix.mdx | 0 .../zh/{ => subgraphs}/cookbook/grafting.mdx | 0 ...pi-keys-using-nextjs-server-components.mdx | 0 .../immutable-entities-bytes-as-ids.mdx | 0 .../zh/{ => subgraphs}/cookbook/near.mdx | 0 .../zh/{ => subgraphs}/cookbook/pruning.mdx | 0 .../cookbook/subgraph-debug-forking.mdx | 0 .../cookbook/subgraph-uncrashable.mdx | 0 .../cookbook/substreams-powered-subgraphs.mdx | 0 .../{ => subgraphs}/cookbook/timeseries.mdx | 0 .../cookbook/transfer-to-the-graph.mdx | 0 .../pages/zh/subgraphs/developing/_meta.js | 5 + .../zh/subgraphs/developing/creating/_meta.js | 5 + .../developing/creating}/advanced.mdx | 0 .../creating}/assemblyscript-mappings.mdx | 0 .../developing/creating/graph-ts/_meta.js | 5 + .../developing/creating}/graph-ts/api.mdx | 0 .../creating}/graph-ts/common-issues.mdx | 0 .../developing/creating}/install-the-cli.mdx | 0 .../developing/creating}/ql-schema.mdx | 0 .../creating}/starting-your-subgraph.mdx | 0 .../creating}/subgraph-manifest.mdx | 0 .../creating}/unit-testing-framework.mdx | 0 .../subgraphs/developing/deploying/_meta.js | 5 + .../deploying/multiple-networks.mdx | 0 .../deploying/subgraph-studio-faqs.mdx | 0 .../deploying/using-subgraph-studio.mdx | 0 .../developing/developer-faqs.mdx | 0 .../developing/introduction.mdx} | 0 .../zh/subgraphs/developing/managing/_meta.js | 5 + .../managing/deleting-a-subgraph.mdx} | 0 .../managing/transferring-a-subgraph.mdx} | 0 .../subgraphs/developing/publishing/_meta.js | 5 + .../publishing/publishing-a-subgraph.mdx | 0 .../{ => subgraphs}/developing/subgraphs.mdx | 0 website/pages/zh/{ => subgraphs}/explorer.mdx | 0 website/pages/zh/subgraphs/querying/_meta.js | 5 + .../querying/best-practices.mdx} | 0 .../querying/distributed-systems.mdx | 0 .../querying/from-an-application.mdx} | 0 .../subgraphs/querying/graph-client/_meta.js | 5 + .../{ => subgraphs}/querying/graphql-api.mdx | 0 .../querying/introduction.mdx} | 0 .../querying/managing-api-keys.mdx | 0 .../querying/python.mdx} | 0 .../subgraph-id-vs-deployment-id.mdx} | 0 .../pages/zh/{ => subgraphs}/quick-start.mdx | 0 website/pages/zh/substreams/_meta.js | 5 + .../introduction.mdx} | 0 website/pages/zh/substreams/sps/_meta.js | 5 + .../zh/{ => substreams}/sps/introduction.mdx | 0 .../sps/substreams-powered-subgraphs-faq.mdx | 0 .../{ => substreams}/sps/triggers-example.mdx | 0 .../zh/{ => substreams}/sps/triggers.mdx | 0 website/route-lockfile.txt | 3069 ++++++++--------- 2201 files changed, 3457 insertions(+), 3483 deletions(-) delete mode 100644 website/pages/ar/cookbook/_meta.js delete mode 100644 website/pages/ar/developing/_meta.js delete mode 100644 website/pages/ar/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/ar/developing/deploying/_meta.js delete mode 100644 website/pages/ar/developing/managing/_meta.js delete mode 100644 website/pages/ar/developing/publishing/_meta.js delete mode 100644 website/pages/ar/indexer-tooling/_meta.js create mode 100644 website/pages/ar/indexing/_meta.js rename website/pages/ar/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/ar/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/ar/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/ar/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/ar/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/ar/indexing/tooling/_meta.js rename website/pages/ar/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/ar/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/ar/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/ar/network/_meta.js delete mode 100644 website/pages/ar/network/overview.mdx delete mode 100644 website/pages/ar/querying/_meta.js delete mode 100644 website/pages/ar/querying/graph-client/_meta.js delete mode 100644 website/pages/ar/release-notes/_meta.js create mode 100644 website/pages/ar/resources/_meta.js rename website/pages/ar/{network => resources}/benefits.mdx (100%) rename website/pages/ar/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/ar/resources/release-notes/_meta.js rename website/pages/ar/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/ar/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/ar/resources/roles/_meta.js rename website/pages/ar/{network => resources/roles}/curating.mdx (100%) rename website/pages/ar/{network => resources/roles}/delegating.mdx (100%) rename website/pages/ar/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/ar/sps/_meta.js create mode 100644 website/pages/ar/subgraphs/_meta.js rename website/pages/ar/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/ar/subgraphs/cookbook/_meta.js rename website/pages/ar/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/ar/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/ar/subgraphs/developing/_meta.js create mode 100644 website/pages/ar/subgraphs/developing/creating/_meta.js rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/ar/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/ar/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ar/subgraphs/developing/deploying/_meta.js rename website/pages/ar/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/ar/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ar/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/ar/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/ar/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/ar/subgraphs/developing/managing/_meta.js rename website/pages/ar/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/ar/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/ar/subgraphs/developing/publishing/_meta.js rename website/pages/ar/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ar/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/ar/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/ar/subgraphs/querying/_meta.js rename website/pages/ar/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/ar/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/ar/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/ar/subgraphs/querying/graph-client/_meta.js rename website/pages/ar/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/ar/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/ar/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/ar/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/ar/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/ar/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/ar/substreams/_meta.js rename website/pages/ar/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/ar/substreams/sps/_meta.js rename website/pages/ar/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/ar/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/ar/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/ar/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/cs/cookbook/_meta.js delete mode 100644 website/pages/cs/developing/_meta.js delete mode 100644 website/pages/cs/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/cs/developing/deploying/_meta.js delete mode 100644 website/pages/cs/developing/managing/_meta.js delete mode 100644 website/pages/cs/developing/publishing/_meta.js delete mode 100644 website/pages/cs/indexer-tooling/_meta.js create mode 100644 website/pages/cs/indexing/_meta.js rename website/pages/cs/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/cs/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/cs/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/cs/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/cs/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/cs/indexing/tooling/_meta.js rename website/pages/cs/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/cs/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/cs/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/cs/network/_meta.js delete mode 100644 website/pages/cs/network/overview.mdx delete mode 100644 website/pages/cs/querying/_meta.js delete mode 100644 website/pages/cs/querying/graph-client/_meta.js delete mode 100644 website/pages/cs/release-notes/_meta.js create mode 100644 website/pages/cs/resources/_meta.js rename website/pages/cs/{network => resources}/benefits.mdx (100%) rename website/pages/cs/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/cs/resources/release-notes/_meta.js rename website/pages/cs/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/cs/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/cs/resources/roles/_meta.js rename website/pages/cs/{network => resources/roles}/curating.mdx (100%) rename website/pages/cs/{network => resources/roles}/delegating.mdx (100%) rename website/pages/cs/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/cs/sps/_meta.js create mode 100644 website/pages/cs/subgraphs/_meta.js rename website/pages/cs/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/cs/subgraphs/cookbook/_meta.js rename website/pages/cs/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/cs/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/cs/subgraphs/developing/_meta.js create mode 100644 website/pages/cs/subgraphs/developing/creating/_meta.js rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/cs/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/cs/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/cs/subgraphs/developing/deploying/_meta.js rename website/pages/cs/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/cs/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/cs/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/cs/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/cs/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/cs/subgraphs/developing/managing/_meta.js rename website/pages/cs/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/cs/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/cs/subgraphs/developing/publishing/_meta.js rename website/pages/cs/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/cs/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/cs/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/cs/subgraphs/querying/_meta.js rename website/pages/cs/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/cs/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/cs/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/cs/subgraphs/querying/graph-client/_meta.js rename website/pages/cs/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/cs/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/cs/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/cs/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/cs/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/cs/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/cs/substreams/_meta.js rename website/pages/cs/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/cs/substreams/sps/_meta.js rename website/pages/cs/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/cs/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/cs/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/cs/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/de/cookbook/_meta.js delete mode 100644 website/pages/de/developing/_meta.js delete mode 100644 website/pages/de/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/de/developing/deploying/_meta.js delete mode 100644 website/pages/de/developing/managing/_meta.js delete mode 100644 website/pages/de/developing/publishing/_meta.js delete mode 100644 website/pages/de/indexer-tooling/_meta.js create mode 100644 website/pages/de/indexing/_meta.js rename website/pages/de/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/de/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/de/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/de/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/de/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/de/indexing/tooling/_meta.js rename website/pages/de/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/de/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/de/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/de/network/_meta.js delete mode 100644 website/pages/de/network/overview.mdx delete mode 100644 website/pages/de/querying/_meta.js delete mode 100644 website/pages/de/querying/graph-client/_meta.js delete mode 100644 website/pages/de/release-notes/_meta.js create mode 100644 website/pages/de/resources/_meta.js rename website/pages/de/{network => resources}/benefits.mdx (100%) rename website/pages/de/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/de/resources/release-notes/_meta.js rename website/pages/de/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/de/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/de/resources/roles/_meta.js rename website/pages/de/{network => resources/roles}/curating.mdx (100%) rename website/pages/de/{network => resources/roles}/delegating.mdx (100%) rename website/pages/de/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/de/sps/_meta.js create mode 100644 website/pages/de/subgraphs/_meta.js rename website/pages/de/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/de/subgraphs/cookbook/_meta.js rename website/pages/de/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/de/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/de/subgraphs/developing/_meta.js create mode 100644 website/pages/de/subgraphs/developing/creating/_meta.js rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/de/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/de/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/de/subgraphs/developing/deploying/_meta.js rename website/pages/de/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/de/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/de/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/de/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/de/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/de/subgraphs/developing/managing/_meta.js rename website/pages/de/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/de/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/de/subgraphs/developing/publishing/_meta.js rename website/pages/de/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/de/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/de/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/de/subgraphs/querying/_meta.js rename website/pages/de/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/de/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/de/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/de/subgraphs/querying/graph-client/_meta.js rename website/pages/de/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/de/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/de/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/de/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/de/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/de/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/de/substreams/_meta.js rename website/pages/de/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/de/substreams/sps/_meta.js rename website/pages/de/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/de/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/de/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/de/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/en/developing/managing/_meta.js create mode 100644 website/pages/en/indexing/_meta.js rename website/pages/en/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/en/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/en/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/en/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/en/{ => indexing}/tap.mdx (100%) rename website/pages/en/{indexer-tooling => indexing/tooling}/_meta.js (100%) rename website/pages/en/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/en/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/en/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/en/network/_meta.js delete mode 100644 website/pages/en/querying/_meta.js create mode 100644 website/pages/en/resources/_meta.js rename website/pages/en/{network => resources}/benefits.mdx (100%) rename website/pages/en/{ => resources}/glossary.mdx (100%) rename website/pages/en/{ => resources}/release-notes/_meta.js (100%) rename website/pages/en/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/en/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/en/resources/roles/_meta.js rename website/pages/en/{network => resources/roles}/curating.mdx (100%) rename website/pages/en/{network => resources/roles}/delegating.mdx (100%) rename website/pages/en/{network => resources}/tokenomics.mdx (100%) create mode 100644 website/pages/en/subgraphs/_meta.js rename website/pages/en/{ => subgraphs}/billing.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/_meta.js (100%) rename website/pages/en/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/en/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) rename website/pages/en/{ => subgraphs}/developing/_meta.js (62%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/_meta.js (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/[[...slug]].mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/_meta.js (70%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/en/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) rename website/pages/en/{ => subgraphs}/developing/deploying/_meta.js (100%) rename website/pages/en/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/en/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/en/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/en/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/en/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/en/subgraphs/developing/managing/_meta.js rename website/pages/en/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (98%) rename website/pages/en/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (97%) rename website/pages/en/{ => subgraphs}/developing/publishing/_meta.js (100%) rename website/pages/en/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/en/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/en/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/en/subgraphs/querying/_meta.js rename website/pages/en/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/en/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/en/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) rename website/pages/en/{ => subgraphs}/querying/graph-client/[[...slug]].mdx (100%) rename website/pages/en/{ => subgraphs}/querying/graph-client/_meta.js (62%) rename website/pages/en/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/en/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/en/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/en/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/en/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/en/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/en/substreams/_meta.js rename website/pages/en/{substreams.mdx => substreams/introduction.mdx} (100%) rename website/pages/en/{ => substreams}/sps/_meta.js (100%) rename website/pages/en/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/en/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/en/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/en/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/es/cookbook/_meta.js delete mode 100644 website/pages/es/developing/_meta.js delete mode 100644 website/pages/es/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/es/developing/deploying/_meta.js delete mode 100644 website/pages/es/developing/managing/_meta.js delete mode 100644 website/pages/es/developing/publishing/_meta.js delete mode 100644 website/pages/es/indexer-tooling/_meta.js create mode 100644 website/pages/es/indexing/_meta.js rename website/pages/es/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/es/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/es/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/es/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/es/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/es/indexing/tooling/_meta.js rename website/pages/es/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/es/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/es/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/es/network/_meta.js delete mode 100644 website/pages/es/network/overview.mdx delete mode 100644 website/pages/es/querying/_meta.js delete mode 100644 website/pages/es/querying/graph-client/_meta.js delete mode 100644 website/pages/es/release-notes/_meta.js create mode 100644 website/pages/es/resources/_meta.js rename website/pages/es/{network => resources}/benefits.mdx (100%) rename website/pages/es/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/es/resources/release-notes/_meta.js rename website/pages/es/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/es/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/es/resources/roles/_meta.js rename website/pages/es/{network => resources/roles}/curating.mdx (100%) rename website/pages/es/{network => resources/roles}/delegating.mdx (100%) rename website/pages/es/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/es/sps/_meta.js create mode 100644 website/pages/es/subgraphs/_meta.js rename website/pages/es/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/es/subgraphs/cookbook/_meta.js rename website/pages/es/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/es/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/es/subgraphs/developing/_meta.js create mode 100644 website/pages/es/subgraphs/developing/creating/_meta.js rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/es/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/es/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/es/subgraphs/developing/deploying/_meta.js rename website/pages/es/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/es/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/es/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/es/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/es/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/es/subgraphs/developing/managing/_meta.js rename website/pages/es/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/es/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/es/subgraphs/developing/publishing/_meta.js rename website/pages/es/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/es/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/es/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/es/subgraphs/querying/_meta.js rename website/pages/es/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/es/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/es/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/es/subgraphs/querying/graph-client/_meta.js rename website/pages/es/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/es/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/es/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/es/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/es/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/es/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/es/substreams/_meta.js rename website/pages/es/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/es/substreams/sps/_meta.js rename website/pages/es/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/es/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/es/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/es/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/fr/cookbook/_meta.js delete mode 100644 website/pages/fr/developing/_meta.js delete mode 100644 website/pages/fr/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/fr/developing/deploying/_meta.js delete mode 100644 website/pages/fr/developing/managing/_meta.js delete mode 100644 website/pages/fr/developing/publishing/_meta.js delete mode 100644 website/pages/fr/indexer-tooling/_meta.js create mode 100644 website/pages/fr/indexing/_meta.js rename website/pages/fr/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/fr/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/fr/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/fr/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/fr/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/fr/indexing/tooling/_meta.js rename website/pages/fr/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/fr/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/fr/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/fr/network/_meta.js delete mode 100644 website/pages/fr/network/overview.mdx delete mode 100644 website/pages/fr/querying/_meta.js delete mode 100644 website/pages/fr/querying/graph-client/_meta.js delete mode 100644 website/pages/fr/release-notes/_meta.js create mode 100644 website/pages/fr/resources/_meta.js rename website/pages/fr/{network => resources}/benefits.mdx (100%) rename website/pages/fr/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/fr/resources/release-notes/_meta.js rename website/pages/fr/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/fr/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/fr/resources/roles/_meta.js rename website/pages/fr/{network => resources/roles}/curating.mdx (100%) rename website/pages/fr/{network => resources/roles}/delegating.mdx (100%) rename website/pages/fr/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/fr/sps/_meta.js create mode 100644 website/pages/fr/subgraphs/_meta.js rename website/pages/fr/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/fr/subgraphs/cookbook/_meta.js rename website/pages/fr/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/fr/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/fr/subgraphs/developing/_meta.js create mode 100644 website/pages/fr/subgraphs/developing/creating/_meta.js rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/fr/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/fr/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/fr/subgraphs/developing/deploying/_meta.js rename website/pages/fr/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/fr/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/fr/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/fr/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/fr/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/fr/subgraphs/developing/managing/_meta.js rename website/pages/fr/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/fr/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/fr/subgraphs/developing/publishing/_meta.js rename website/pages/fr/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/fr/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/fr/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/fr/subgraphs/querying/_meta.js rename website/pages/fr/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/fr/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/fr/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/fr/subgraphs/querying/graph-client/_meta.js rename website/pages/fr/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/fr/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/fr/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/fr/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/fr/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/fr/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/fr/substreams/_meta.js rename website/pages/fr/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/fr/substreams/sps/_meta.js rename website/pages/fr/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/fr/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/fr/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/fr/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/hi/cookbook/_meta.js delete mode 100644 website/pages/hi/developing/_meta.js delete mode 100644 website/pages/hi/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/hi/developing/deploying/_meta.js delete mode 100644 website/pages/hi/developing/managing/_meta.js delete mode 100644 website/pages/hi/developing/publishing/_meta.js delete mode 100644 website/pages/hi/indexer-tooling/_meta.js create mode 100644 website/pages/hi/indexing/_meta.js rename website/pages/hi/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/hi/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/hi/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/hi/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/hi/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/hi/indexing/tooling/_meta.js rename website/pages/hi/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/hi/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/hi/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/hi/network/_meta.js delete mode 100644 website/pages/hi/network/overview.mdx delete mode 100644 website/pages/hi/querying/_meta.js delete mode 100644 website/pages/hi/querying/graph-client/_meta.js delete mode 100644 website/pages/hi/release-notes/_meta.js create mode 100644 website/pages/hi/resources/_meta.js rename website/pages/hi/{network => resources}/benefits.mdx (100%) rename website/pages/hi/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/hi/resources/release-notes/_meta.js rename website/pages/hi/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/hi/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/hi/resources/roles/_meta.js rename website/pages/hi/{network => resources/roles}/curating.mdx (100%) rename website/pages/hi/{network => resources/roles}/delegating.mdx (100%) rename website/pages/hi/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/hi/sps/_meta.js create mode 100644 website/pages/hi/subgraphs/_meta.js rename website/pages/hi/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/hi/subgraphs/cookbook/_meta.js rename website/pages/hi/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/hi/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/hi/subgraphs/developing/_meta.js create mode 100644 website/pages/hi/subgraphs/developing/creating/_meta.js rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/hi/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/hi/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/hi/subgraphs/developing/deploying/_meta.js rename website/pages/hi/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/hi/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/hi/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/hi/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/hi/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/hi/subgraphs/developing/managing/_meta.js rename website/pages/hi/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/hi/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/hi/subgraphs/developing/publishing/_meta.js rename website/pages/hi/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/hi/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/hi/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/hi/subgraphs/querying/_meta.js rename website/pages/hi/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/hi/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/hi/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/hi/subgraphs/querying/graph-client/_meta.js rename website/pages/hi/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/hi/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/hi/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/hi/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/hi/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/hi/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/hi/substreams/_meta.js rename website/pages/hi/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/hi/substreams/sps/_meta.js rename website/pages/hi/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/hi/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/hi/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/hi/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/it/cookbook/_meta.js delete mode 100644 website/pages/it/developing/_meta.js delete mode 100644 website/pages/it/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/it/developing/deploying/_meta.js delete mode 100644 website/pages/it/developing/managing/_meta.js delete mode 100644 website/pages/it/developing/publishing/_meta.js delete mode 100644 website/pages/it/indexer-tooling/_meta.js create mode 100644 website/pages/it/indexing/_meta.js rename website/pages/it/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/it/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/it/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/it/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/it/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/it/indexing/tooling/_meta.js rename website/pages/it/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/it/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/it/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/it/network/_meta.js delete mode 100644 website/pages/it/network/overview.mdx delete mode 100644 website/pages/it/querying/_meta.js delete mode 100644 website/pages/it/querying/graph-client/_meta.js delete mode 100644 website/pages/it/release-notes/_meta.js create mode 100644 website/pages/it/resources/_meta.js rename website/pages/it/{network => resources}/benefits.mdx (100%) rename website/pages/it/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/it/resources/release-notes/_meta.js rename website/pages/it/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/it/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/it/resources/roles/_meta.js rename website/pages/it/{network => resources/roles}/curating.mdx (100%) rename website/pages/it/{network => resources/roles}/delegating.mdx (100%) rename website/pages/it/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/it/sps/_meta.js create mode 100644 website/pages/it/subgraphs/_meta.js rename website/pages/it/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/it/subgraphs/cookbook/_meta.js rename website/pages/it/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/it/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/it/subgraphs/developing/_meta.js create mode 100644 website/pages/it/subgraphs/developing/creating/_meta.js rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/it/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/it/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/it/subgraphs/developing/deploying/_meta.js rename website/pages/it/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/it/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/it/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/it/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/it/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/it/subgraphs/developing/managing/_meta.js rename website/pages/it/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/it/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/it/subgraphs/developing/publishing/_meta.js rename website/pages/it/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/it/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/it/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/it/subgraphs/querying/_meta.js rename website/pages/it/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/it/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/it/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/it/subgraphs/querying/graph-client/_meta.js rename website/pages/it/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/it/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/it/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/it/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/it/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/it/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/it/substreams/_meta.js rename website/pages/it/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/it/substreams/sps/_meta.js rename website/pages/it/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/it/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/it/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/it/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/ja/cookbook/_meta.js delete mode 100644 website/pages/ja/developing/_meta.js delete mode 100644 website/pages/ja/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/ja/developing/deploying/_meta.js delete mode 100644 website/pages/ja/developing/managing/_meta.js delete mode 100644 website/pages/ja/developing/publishing/_meta.js delete mode 100644 website/pages/ja/indexer-tooling/_meta.js create mode 100644 website/pages/ja/indexing/_meta.js rename website/pages/ja/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/ja/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/ja/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/ja/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/ja/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/ja/indexing/tooling/_meta.js rename website/pages/ja/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/ja/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/ja/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/ja/network/_meta.js delete mode 100644 website/pages/ja/network/overview.mdx delete mode 100644 website/pages/ja/querying/_meta.js delete mode 100644 website/pages/ja/querying/graph-client/_meta.js delete mode 100644 website/pages/ja/release-notes/_meta.js create mode 100644 website/pages/ja/resources/_meta.js rename website/pages/ja/{network => resources}/benefits.mdx (100%) rename website/pages/ja/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/ja/resources/release-notes/_meta.js rename website/pages/ja/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/ja/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/ja/resources/roles/_meta.js rename website/pages/ja/{network => resources/roles}/curating.mdx (100%) rename website/pages/ja/{network => resources/roles}/delegating.mdx (100%) rename website/pages/ja/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/ja/sps/_meta.js create mode 100644 website/pages/ja/subgraphs/_meta.js rename website/pages/ja/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/ja/subgraphs/cookbook/_meta.js rename website/pages/ja/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/ja/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/ja/subgraphs/developing/_meta.js create mode 100644 website/pages/ja/subgraphs/developing/creating/_meta.js rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/ja/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/ja/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ja/subgraphs/developing/deploying/_meta.js rename website/pages/ja/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/ja/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ja/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/ja/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/ja/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/ja/subgraphs/developing/managing/_meta.js rename website/pages/ja/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/ja/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/ja/subgraphs/developing/publishing/_meta.js rename website/pages/ja/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ja/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/ja/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/ja/subgraphs/querying/_meta.js rename website/pages/ja/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/ja/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/ja/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/ja/subgraphs/querying/graph-client/_meta.js rename website/pages/ja/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/ja/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/ja/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/ja/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/ja/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/ja/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/ja/substreams/_meta.js rename website/pages/ja/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/ja/substreams/sps/_meta.js rename website/pages/ja/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/ja/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/ja/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/ja/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/ko/cookbook/_meta.js delete mode 100644 website/pages/ko/developing/_meta.js delete mode 100644 website/pages/ko/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/ko/developing/deploying/_meta.js delete mode 100644 website/pages/ko/developing/managing/_meta.js delete mode 100644 website/pages/ko/developing/publishing/_meta.js delete mode 100644 website/pages/ko/indexer-tooling/_meta.js create mode 100644 website/pages/ko/indexing/_meta.js rename website/pages/ko/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/ko/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/ko/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/ko/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/ko/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/ko/indexing/tooling/_meta.js rename website/pages/ko/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/ko/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/ko/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/ko/network/_meta.js delete mode 100644 website/pages/ko/network/overview.mdx delete mode 100644 website/pages/ko/querying/_meta.js delete mode 100644 website/pages/ko/querying/graph-client/_meta.js delete mode 100644 website/pages/ko/release-notes/_meta.js create mode 100644 website/pages/ko/resources/_meta.js rename website/pages/ko/{network => resources}/benefits.mdx (100%) rename website/pages/ko/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/ko/resources/release-notes/_meta.js rename website/pages/ko/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/ko/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/ko/resources/roles/_meta.js rename website/pages/ko/{network => resources/roles}/curating.mdx (100%) rename website/pages/ko/{network => resources/roles}/delegating.mdx (100%) rename website/pages/ko/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/ko/sps/_meta.js create mode 100644 website/pages/ko/subgraphs/_meta.js rename website/pages/ko/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/ko/subgraphs/cookbook/_meta.js rename website/pages/ko/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/ko/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/ko/subgraphs/developing/_meta.js create mode 100644 website/pages/ko/subgraphs/developing/creating/_meta.js rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/ko/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/ko/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ko/subgraphs/developing/deploying/_meta.js rename website/pages/ko/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/ko/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ko/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/ko/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/ko/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/ko/subgraphs/developing/managing/_meta.js rename website/pages/ko/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/ko/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/ko/subgraphs/developing/publishing/_meta.js rename website/pages/ko/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ko/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/ko/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/ko/subgraphs/querying/_meta.js rename website/pages/ko/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/ko/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/ko/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/ko/subgraphs/querying/graph-client/_meta.js rename website/pages/ko/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/ko/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/ko/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/ko/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/ko/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/ko/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/ko/substreams/_meta.js rename website/pages/ko/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/ko/substreams/sps/_meta.js rename website/pages/ko/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/ko/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/ko/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/ko/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/mr/cookbook/_meta.js delete mode 100644 website/pages/mr/developing/_meta.js delete mode 100644 website/pages/mr/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/mr/developing/deploying/_meta.js delete mode 100644 website/pages/mr/developing/managing/_meta.js delete mode 100644 website/pages/mr/developing/publishing/_meta.js delete mode 100644 website/pages/mr/indexer-tooling/_meta.js create mode 100644 website/pages/mr/indexing/_meta.js rename website/pages/mr/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/mr/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/mr/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/mr/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/mr/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/mr/indexing/tooling/_meta.js rename website/pages/mr/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/mr/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/mr/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/mr/network/_meta.js delete mode 100644 website/pages/mr/network/overview.mdx delete mode 100644 website/pages/mr/querying/_meta.js delete mode 100644 website/pages/mr/querying/graph-client/_meta.js delete mode 100644 website/pages/mr/release-notes/_meta.js create mode 100644 website/pages/mr/resources/_meta.js rename website/pages/mr/{network => resources}/benefits.mdx (100%) rename website/pages/mr/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/mr/resources/release-notes/_meta.js rename website/pages/mr/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/mr/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/mr/resources/roles/_meta.js rename website/pages/mr/{network => resources/roles}/curating.mdx (100%) rename website/pages/mr/{network => resources/roles}/delegating.mdx (100%) rename website/pages/mr/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/mr/sps/_meta.js create mode 100644 website/pages/mr/subgraphs/_meta.js rename website/pages/mr/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/mr/subgraphs/cookbook/_meta.js rename website/pages/mr/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/mr/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/mr/subgraphs/developing/_meta.js create mode 100644 website/pages/mr/subgraphs/developing/creating/_meta.js rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/mr/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/mr/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/mr/subgraphs/developing/deploying/_meta.js rename website/pages/mr/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/mr/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/mr/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/mr/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/mr/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/mr/subgraphs/developing/managing/_meta.js rename website/pages/mr/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/mr/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/mr/subgraphs/developing/publishing/_meta.js rename website/pages/mr/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/mr/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/mr/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/mr/subgraphs/querying/_meta.js rename website/pages/mr/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/mr/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/mr/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/mr/subgraphs/querying/graph-client/_meta.js rename website/pages/mr/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/mr/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/mr/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/mr/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/mr/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/mr/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/mr/substreams/_meta.js rename website/pages/mr/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/mr/substreams/sps/_meta.js rename website/pages/mr/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/mr/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/mr/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/mr/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/nl/cookbook/_meta.js delete mode 100644 website/pages/nl/developing/_meta.js delete mode 100644 website/pages/nl/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/nl/developing/deploying/_meta.js delete mode 100644 website/pages/nl/developing/managing/_meta.js delete mode 100644 website/pages/nl/developing/publishing/_meta.js delete mode 100644 website/pages/nl/indexer-tooling/_meta.js create mode 100644 website/pages/nl/indexing/_meta.js rename website/pages/nl/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/nl/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/nl/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/nl/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/nl/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/nl/indexing/tooling/_meta.js rename website/pages/nl/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/nl/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/nl/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/nl/network/_meta.js delete mode 100644 website/pages/nl/network/overview.mdx delete mode 100644 website/pages/nl/querying/_meta.js delete mode 100644 website/pages/nl/querying/graph-client/_meta.js delete mode 100644 website/pages/nl/release-notes/_meta.js create mode 100644 website/pages/nl/resources/_meta.js rename website/pages/nl/{network => resources}/benefits.mdx (100%) rename website/pages/nl/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/nl/resources/release-notes/_meta.js rename website/pages/nl/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/nl/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/nl/resources/roles/_meta.js rename website/pages/nl/{network => resources/roles}/curating.mdx (100%) rename website/pages/nl/{network => resources/roles}/delegating.mdx (100%) rename website/pages/nl/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/nl/sps/_meta.js create mode 100644 website/pages/nl/subgraphs/_meta.js rename website/pages/nl/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/nl/subgraphs/cookbook/_meta.js rename website/pages/nl/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/nl/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/nl/subgraphs/developing/_meta.js create mode 100644 website/pages/nl/subgraphs/developing/creating/_meta.js rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/nl/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/nl/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/nl/subgraphs/developing/deploying/_meta.js rename website/pages/nl/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/nl/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/nl/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/nl/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/nl/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/nl/subgraphs/developing/managing/_meta.js rename website/pages/nl/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/nl/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/nl/subgraphs/developing/publishing/_meta.js rename website/pages/nl/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/nl/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/nl/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/nl/subgraphs/querying/_meta.js rename website/pages/nl/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/nl/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/nl/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/nl/subgraphs/querying/graph-client/_meta.js rename website/pages/nl/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/nl/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/nl/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/nl/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/nl/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/nl/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/nl/substreams/_meta.js rename website/pages/nl/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/nl/substreams/sps/_meta.js rename website/pages/nl/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/nl/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/nl/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/nl/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/pl/cookbook/_meta.js delete mode 100644 website/pages/pl/developing/_meta.js delete mode 100644 website/pages/pl/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/pl/developing/deploying/_meta.js delete mode 100644 website/pages/pl/developing/managing/_meta.js delete mode 100644 website/pages/pl/developing/publishing/_meta.js delete mode 100644 website/pages/pl/indexer-tooling/_meta.js create mode 100644 website/pages/pl/indexing/_meta.js rename website/pages/pl/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/pl/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/pl/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/pl/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/pl/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/pl/indexing/tooling/_meta.js rename website/pages/pl/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/pl/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/pl/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/pl/network/_meta.js delete mode 100644 website/pages/pl/network/overview.mdx delete mode 100644 website/pages/pl/querying/_meta.js delete mode 100644 website/pages/pl/querying/graph-client/_meta.js delete mode 100644 website/pages/pl/release-notes/_meta.js create mode 100644 website/pages/pl/resources/_meta.js rename website/pages/pl/{network => resources}/benefits.mdx (100%) rename website/pages/pl/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/pl/resources/release-notes/_meta.js rename website/pages/pl/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/pl/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/pl/resources/roles/_meta.js rename website/pages/pl/{network => resources/roles}/curating.mdx (100%) rename website/pages/pl/{network => resources/roles}/delegating.mdx (100%) rename website/pages/pl/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/pl/sps/_meta.js create mode 100644 website/pages/pl/subgraphs/_meta.js rename website/pages/pl/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/pl/subgraphs/cookbook/_meta.js rename website/pages/pl/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/pl/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/pl/subgraphs/developing/_meta.js create mode 100644 website/pages/pl/subgraphs/developing/creating/_meta.js rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/pl/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/pl/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/pl/subgraphs/developing/deploying/_meta.js rename website/pages/pl/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/pl/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/pl/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/pl/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/pl/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/pl/subgraphs/developing/managing/_meta.js rename website/pages/pl/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/pl/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/pl/subgraphs/developing/publishing/_meta.js rename website/pages/pl/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/pl/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/pl/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/pl/subgraphs/querying/_meta.js rename website/pages/pl/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/pl/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/pl/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/pl/subgraphs/querying/graph-client/_meta.js rename website/pages/pl/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/pl/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/pl/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/pl/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/pl/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/pl/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/pl/substreams/_meta.js rename website/pages/pl/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/pl/substreams/sps/_meta.js rename website/pages/pl/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/pl/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/pl/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/pl/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/pt/cookbook/_meta.js delete mode 100644 website/pages/pt/developing/_meta.js delete mode 100644 website/pages/pt/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/pt/developing/deploying/_meta.js delete mode 100644 website/pages/pt/developing/managing/_meta.js delete mode 100644 website/pages/pt/developing/publishing/_meta.js delete mode 100644 website/pages/pt/indexer-tooling/_meta.js create mode 100644 website/pages/pt/indexing/_meta.js rename website/pages/pt/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/pt/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/pt/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/pt/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/pt/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/pt/indexing/tooling/_meta.js rename website/pages/pt/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/pt/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/pt/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/pt/network/_meta.js delete mode 100644 website/pages/pt/network/overview.mdx delete mode 100644 website/pages/pt/querying/_meta.js delete mode 100644 website/pages/pt/querying/graph-client/_meta.js delete mode 100644 website/pages/pt/release-notes/_meta.js create mode 100644 website/pages/pt/resources/_meta.js rename website/pages/pt/{network => resources}/benefits.mdx (100%) rename website/pages/pt/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/pt/resources/release-notes/_meta.js rename website/pages/pt/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/pt/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/pt/resources/roles/_meta.js rename website/pages/pt/{network => resources/roles}/curating.mdx (100%) rename website/pages/pt/{network => resources/roles}/delegating.mdx (100%) rename website/pages/pt/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/pt/sps/_meta.js create mode 100644 website/pages/pt/subgraphs/_meta.js rename website/pages/pt/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/pt/subgraphs/cookbook/_meta.js rename website/pages/pt/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/pt/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/pt/subgraphs/developing/_meta.js create mode 100644 website/pages/pt/subgraphs/developing/creating/_meta.js rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/pt/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/pt/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/pt/subgraphs/developing/deploying/_meta.js rename website/pages/pt/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/pt/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/pt/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/pt/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/pt/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/pt/subgraphs/developing/managing/_meta.js rename website/pages/pt/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/pt/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/pt/subgraphs/developing/publishing/_meta.js rename website/pages/pt/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/pt/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/pt/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/pt/subgraphs/querying/_meta.js rename website/pages/pt/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/pt/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/pt/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/pt/subgraphs/querying/graph-client/_meta.js rename website/pages/pt/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/pt/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/pt/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/pt/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/pt/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/pt/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/pt/substreams/_meta.js rename website/pages/pt/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/pt/substreams/sps/_meta.js rename website/pages/pt/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/pt/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/pt/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/pt/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/ro/cookbook/_meta.js delete mode 100644 website/pages/ro/developing/_meta.js delete mode 100644 website/pages/ro/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/ro/developing/deploying/_meta.js delete mode 100644 website/pages/ro/developing/managing/_meta.js delete mode 100644 website/pages/ro/developing/publishing/_meta.js delete mode 100644 website/pages/ro/indexer-tooling/_meta.js create mode 100644 website/pages/ro/indexing/_meta.js rename website/pages/ro/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/ro/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/ro/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/ro/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/ro/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/ro/indexing/tooling/_meta.js rename website/pages/ro/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/ro/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/ro/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/ro/network/_meta.js delete mode 100644 website/pages/ro/network/overview.mdx delete mode 100644 website/pages/ro/querying/_meta.js delete mode 100644 website/pages/ro/querying/graph-client/_meta.js delete mode 100644 website/pages/ro/release-notes/_meta.js create mode 100644 website/pages/ro/resources/_meta.js rename website/pages/ro/{network => resources}/benefits.mdx (100%) rename website/pages/ro/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/ro/resources/release-notes/_meta.js rename website/pages/ro/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/ro/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/ro/resources/roles/_meta.js rename website/pages/ro/{network => resources/roles}/curating.mdx (100%) rename website/pages/ro/{network => resources/roles}/delegating.mdx (100%) rename website/pages/ro/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/ro/sps/_meta.js create mode 100644 website/pages/ro/subgraphs/_meta.js rename website/pages/ro/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/ro/subgraphs/cookbook/_meta.js rename website/pages/ro/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/ro/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/ro/subgraphs/developing/_meta.js create mode 100644 website/pages/ro/subgraphs/developing/creating/_meta.js rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/ro/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/ro/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ro/subgraphs/developing/deploying/_meta.js rename website/pages/ro/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/ro/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ro/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/ro/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/ro/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/ro/subgraphs/developing/managing/_meta.js rename website/pages/ro/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/ro/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/ro/subgraphs/developing/publishing/_meta.js rename website/pages/ro/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ro/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/ro/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/ro/subgraphs/querying/_meta.js rename website/pages/ro/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/ro/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/ro/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/ro/subgraphs/querying/graph-client/_meta.js rename website/pages/ro/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/ro/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/ro/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/ro/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/ro/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/ro/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/ro/substreams/_meta.js rename website/pages/ro/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/ro/substreams/sps/_meta.js rename website/pages/ro/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/ro/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/ro/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/ro/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/ru/cookbook/_meta.js delete mode 100644 website/pages/ru/developing/_meta.js delete mode 100644 website/pages/ru/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/ru/developing/deploying/_meta.js delete mode 100644 website/pages/ru/developing/managing/_meta.js delete mode 100644 website/pages/ru/developing/publishing/_meta.js delete mode 100644 website/pages/ru/indexer-tooling/_meta.js create mode 100644 website/pages/ru/indexing/_meta.js rename website/pages/ru/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/ru/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/ru/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/ru/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/ru/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/ru/indexing/tooling/_meta.js rename website/pages/ru/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/ru/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/ru/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/ru/network/_meta.js delete mode 100644 website/pages/ru/network/overview.mdx delete mode 100644 website/pages/ru/querying/_meta.js delete mode 100644 website/pages/ru/querying/graph-client/_meta.js delete mode 100644 website/pages/ru/release-notes/_meta.js create mode 100644 website/pages/ru/resources/_meta.js rename website/pages/ru/{network => resources}/benefits.mdx (100%) rename website/pages/ru/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/ru/resources/release-notes/_meta.js rename website/pages/ru/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/ru/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/ru/resources/roles/_meta.js rename website/pages/ru/{network => resources/roles}/curating.mdx (100%) rename website/pages/ru/{network => resources/roles}/delegating.mdx (100%) rename website/pages/ru/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/ru/sps/_meta.js create mode 100644 website/pages/ru/subgraphs/_meta.js rename website/pages/ru/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/ru/subgraphs/cookbook/_meta.js rename website/pages/ru/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/ru/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/ru/subgraphs/developing/_meta.js create mode 100644 website/pages/ru/subgraphs/developing/creating/_meta.js rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/ru/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/ru/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ru/subgraphs/developing/deploying/_meta.js rename website/pages/ru/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/ru/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ru/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/ru/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/ru/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/ru/subgraphs/developing/managing/_meta.js rename website/pages/ru/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/ru/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/ru/subgraphs/developing/publishing/_meta.js rename website/pages/ru/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ru/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/ru/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/ru/subgraphs/querying/_meta.js rename website/pages/ru/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/ru/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/ru/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/ru/subgraphs/querying/graph-client/_meta.js rename website/pages/ru/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/ru/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/ru/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/ru/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/ru/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/ru/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/ru/substreams/_meta.js rename website/pages/ru/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/ru/substreams/sps/_meta.js rename website/pages/ru/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/ru/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/ru/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/ru/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/sv/cookbook/_meta.js delete mode 100644 website/pages/sv/developing/_meta.js delete mode 100644 website/pages/sv/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/sv/developing/deploying/_meta.js delete mode 100644 website/pages/sv/developing/managing/_meta.js delete mode 100644 website/pages/sv/developing/publishing/_meta.js delete mode 100644 website/pages/sv/indexer-tooling/_meta.js create mode 100644 website/pages/sv/indexing/_meta.js rename website/pages/sv/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/sv/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/sv/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/sv/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/sv/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/sv/indexing/tooling/_meta.js rename website/pages/sv/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/sv/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/sv/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/sv/network/_meta.js delete mode 100644 website/pages/sv/network/overview.mdx delete mode 100644 website/pages/sv/querying/_meta.js delete mode 100644 website/pages/sv/querying/graph-client/_meta.js delete mode 100644 website/pages/sv/release-notes/_meta.js create mode 100644 website/pages/sv/resources/_meta.js rename website/pages/sv/{network => resources}/benefits.mdx (100%) rename website/pages/sv/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/sv/resources/release-notes/_meta.js rename website/pages/sv/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/sv/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/sv/resources/roles/_meta.js rename website/pages/sv/{network => resources/roles}/curating.mdx (100%) rename website/pages/sv/{network => resources/roles}/delegating.mdx (100%) rename website/pages/sv/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/sv/sps/_meta.js create mode 100644 website/pages/sv/subgraphs/_meta.js rename website/pages/sv/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/sv/subgraphs/cookbook/_meta.js rename website/pages/sv/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/sv/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/sv/subgraphs/developing/_meta.js create mode 100644 website/pages/sv/subgraphs/developing/creating/_meta.js rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/sv/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/sv/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/sv/subgraphs/developing/deploying/_meta.js rename website/pages/sv/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/sv/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/sv/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/sv/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/sv/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/sv/subgraphs/developing/managing/_meta.js rename website/pages/sv/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/sv/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/sv/subgraphs/developing/publishing/_meta.js rename website/pages/sv/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/sv/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/sv/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/sv/subgraphs/querying/_meta.js rename website/pages/sv/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/sv/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/sv/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/sv/subgraphs/querying/graph-client/_meta.js rename website/pages/sv/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/sv/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/sv/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/sv/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/sv/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/sv/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/sv/substreams/_meta.js rename website/pages/sv/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/sv/substreams/sps/_meta.js rename website/pages/sv/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/sv/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/sv/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/sv/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/sw/cookbook/_meta.js delete mode 100644 website/pages/sw/developing/_meta.js delete mode 100644 website/pages/sw/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/sw/developing/deploying/_meta.js delete mode 100644 website/pages/sw/developing/managing/_meta.js delete mode 100644 website/pages/sw/developing/publishing/_meta.js delete mode 100644 website/pages/sw/indexer-tooling/_meta.js create mode 100644 website/pages/sw/indexing/_meta.js rename website/pages/sw/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/sw/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/sw/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/sw/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/sw/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/sw/indexing/tooling/_meta.js rename website/pages/sw/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/sw/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/sw/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/sw/network/_meta.js delete mode 100644 website/pages/sw/network/overview.mdx delete mode 100644 website/pages/sw/querying/_meta.js delete mode 100644 website/pages/sw/querying/graph-client/_meta.js delete mode 100644 website/pages/sw/release-notes/_meta.js create mode 100644 website/pages/sw/resources/_meta.js rename website/pages/sw/{network => resources}/benefits.mdx (100%) rename website/pages/sw/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/sw/resources/release-notes/_meta.js rename website/pages/sw/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/sw/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/sw/resources/roles/_meta.js rename website/pages/sw/{network => resources/roles}/curating.mdx (100%) rename website/pages/sw/{network => resources/roles}/delegating.mdx (100%) rename website/pages/sw/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/sw/sps/_meta.js create mode 100644 website/pages/sw/subgraphs/_meta.js rename website/pages/sw/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/sw/subgraphs/cookbook/_meta.js rename website/pages/sw/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/sw/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/sw/subgraphs/developing/_meta.js create mode 100644 website/pages/sw/subgraphs/developing/creating/_meta.js rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/sw/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/sw/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/sw/subgraphs/developing/deploying/_meta.js rename website/pages/sw/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/sw/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/sw/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/sw/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/sw/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/sw/subgraphs/developing/managing/_meta.js rename website/pages/sw/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/sw/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/sw/subgraphs/developing/publishing/_meta.js rename website/pages/sw/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/sw/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/sw/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/sw/subgraphs/querying/_meta.js rename website/pages/sw/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/sw/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/sw/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/sw/subgraphs/querying/graph-client/_meta.js rename website/pages/sw/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/sw/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/sw/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/sw/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/sw/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/sw/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/sw/substreams/_meta.js rename website/pages/sw/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/sw/substreams/sps/_meta.js rename website/pages/sw/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/sw/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/sw/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/sw/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/tr/cookbook/_meta.js delete mode 100644 website/pages/tr/developing/_meta.js delete mode 100644 website/pages/tr/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/tr/developing/deploying/_meta.js delete mode 100644 website/pages/tr/developing/managing/_meta.js delete mode 100644 website/pages/tr/developing/publishing/_meta.js delete mode 100644 website/pages/tr/indexer-tooling/_meta.js create mode 100644 website/pages/tr/indexing/_meta.js rename website/pages/tr/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/tr/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/tr/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/tr/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/tr/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/tr/indexing/tooling/_meta.js rename website/pages/tr/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/tr/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/tr/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/tr/network/_meta.js delete mode 100644 website/pages/tr/network/overview.mdx delete mode 100644 website/pages/tr/querying/_meta.js delete mode 100644 website/pages/tr/querying/graph-client/_meta.js delete mode 100644 website/pages/tr/release-notes/_meta.js create mode 100644 website/pages/tr/resources/_meta.js rename website/pages/tr/{network => resources}/benefits.mdx (100%) rename website/pages/tr/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/tr/resources/release-notes/_meta.js rename website/pages/tr/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/tr/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/tr/resources/roles/_meta.js rename website/pages/tr/{network => resources/roles}/curating.mdx (100%) rename website/pages/tr/{network => resources/roles}/delegating.mdx (100%) rename website/pages/tr/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/tr/sps/_meta.js create mode 100644 website/pages/tr/subgraphs/_meta.js rename website/pages/tr/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/tr/subgraphs/cookbook/_meta.js rename website/pages/tr/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/tr/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/tr/subgraphs/developing/_meta.js create mode 100644 website/pages/tr/subgraphs/developing/creating/_meta.js rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/tr/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/tr/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/tr/subgraphs/developing/deploying/_meta.js rename website/pages/tr/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/tr/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/tr/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/tr/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/tr/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/tr/subgraphs/developing/managing/_meta.js rename website/pages/tr/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/tr/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/tr/subgraphs/developing/publishing/_meta.js rename website/pages/tr/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/tr/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/tr/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/tr/subgraphs/querying/_meta.js rename website/pages/tr/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/tr/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/tr/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/tr/subgraphs/querying/graph-client/_meta.js rename website/pages/tr/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/tr/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/tr/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/tr/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/tr/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/tr/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/tr/substreams/_meta.js rename website/pages/tr/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/tr/substreams/sps/_meta.js rename website/pages/tr/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/tr/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/tr/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/tr/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/uk/cookbook/_meta.js delete mode 100644 website/pages/uk/developing/_meta.js delete mode 100644 website/pages/uk/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/uk/developing/deploying/_meta.js delete mode 100644 website/pages/uk/developing/managing/_meta.js delete mode 100644 website/pages/uk/developing/publishing/_meta.js delete mode 100644 website/pages/uk/indexer-tooling/_meta.js create mode 100644 website/pages/uk/indexing/_meta.js rename website/pages/uk/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/uk/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/uk/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/uk/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/uk/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/uk/indexing/tooling/_meta.js rename website/pages/uk/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/uk/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/uk/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/uk/network/_meta.js delete mode 100644 website/pages/uk/network/overview.mdx delete mode 100644 website/pages/uk/querying/_meta.js delete mode 100644 website/pages/uk/querying/graph-client/_meta.js delete mode 100644 website/pages/uk/release-notes/_meta.js create mode 100644 website/pages/uk/resources/_meta.js rename website/pages/uk/{network => resources}/benefits.mdx (100%) rename website/pages/uk/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/uk/resources/release-notes/_meta.js rename website/pages/uk/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/uk/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/uk/resources/roles/_meta.js rename website/pages/uk/{network => resources/roles}/curating.mdx (100%) rename website/pages/uk/{network => resources/roles}/delegating.mdx (100%) rename website/pages/uk/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/uk/sps/_meta.js create mode 100644 website/pages/uk/subgraphs/_meta.js rename website/pages/uk/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/uk/subgraphs/cookbook/_meta.js rename website/pages/uk/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/uk/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/uk/subgraphs/developing/_meta.js create mode 100644 website/pages/uk/subgraphs/developing/creating/_meta.js rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/uk/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/uk/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/uk/subgraphs/developing/deploying/_meta.js rename website/pages/uk/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/uk/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/uk/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/uk/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/uk/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/uk/subgraphs/developing/managing/_meta.js rename website/pages/uk/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/uk/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/uk/subgraphs/developing/publishing/_meta.js rename website/pages/uk/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/uk/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/uk/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/uk/subgraphs/querying/_meta.js rename website/pages/uk/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/uk/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/uk/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/uk/subgraphs/querying/graph-client/_meta.js rename website/pages/uk/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/uk/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/uk/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/uk/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/uk/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/uk/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/uk/substreams/_meta.js rename website/pages/uk/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/uk/substreams/sps/_meta.js rename website/pages/uk/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/uk/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/uk/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/uk/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/ur/cookbook/_meta.js delete mode 100644 website/pages/ur/developing/_meta.js delete mode 100644 website/pages/ur/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/ur/developing/deploying/_meta.js delete mode 100644 website/pages/ur/developing/managing/_meta.js delete mode 100644 website/pages/ur/developing/publishing/_meta.js delete mode 100644 website/pages/ur/indexer-tooling/_meta.js create mode 100644 website/pages/ur/indexing/_meta.js rename website/pages/ur/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/ur/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/ur/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/ur/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/ur/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/ur/indexing/tooling/_meta.js rename website/pages/ur/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/ur/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/ur/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/ur/network/_meta.js delete mode 100644 website/pages/ur/network/overview.mdx delete mode 100644 website/pages/ur/querying/_meta.js delete mode 100644 website/pages/ur/querying/graph-client/_meta.js delete mode 100644 website/pages/ur/release-notes/_meta.js create mode 100644 website/pages/ur/resources/_meta.js rename website/pages/ur/{network => resources}/benefits.mdx (100%) rename website/pages/ur/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/ur/resources/release-notes/_meta.js rename website/pages/ur/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/ur/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/ur/resources/roles/_meta.js rename website/pages/ur/{network => resources/roles}/curating.mdx (100%) rename website/pages/ur/{network => resources/roles}/delegating.mdx (100%) rename website/pages/ur/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/ur/sps/_meta.js create mode 100644 website/pages/ur/subgraphs/_meta.js rename website/pages/ur/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/ur/subgraphs/cookbook/_meta.js rename website/pages/ur/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/ur/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/ur/subgraphs/developing/_meta.js create mode 100644 website/pages/ur/subgraphs/developing/creating/_meta.js rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/ur/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/ur/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/ur/subgraphs/developing/deploying/_meta.js rename website/pages/ur/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/ur/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/ur/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/ur/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/ur/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/ur/subgraphs/developing/managing/_meta.js rename website/pages/ur/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/ur/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/ur/subgraphs/developing/publishing/_meta.js rename website/pages/ur/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/ur/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/ur/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/ur/subgraphs/querying/_meta.js rename website/pages/ur/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/ur/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/ur/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/ur/subgraphs/querying/graph-client/_meta.js rename website/pages/ur/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/ur/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/ur/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/ur/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/ur/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/ur/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/ur/substreams/_meta.js rename website/pages/ur/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/ur/substreams/sps/_meta.js rename website/pages/ur/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/ur/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/ur/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/ur/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/vi/cookbook/_meta.js delete mode 100644 website/pages/vi/developing/_meta.js delete mode 100644 website/pages/vi/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/vi/developing/deploying/_meta.js delete mode 100644 website/pages/vi/developing/managing/_meta.js delete mode 100644 website/pages/vi/developing/publishing/_meta.js delete mode 100644 website/pages/vi/indexer-tooling/_meta.js create mode 100644 website/pages/vi/indexing/_meta.js rename website/pages/vi/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/vi/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/vi/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/vi/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/vi/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/vi/indexing/tooling/_meta.js rename website/pages/vi/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/vi/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/vi/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/vi/network/_meta.js delete mode 100644 website/pages/vi/network/overview.mdx delete mode 100644 website/pages/vi/querying/_meta.js delete mode 100644 website/pages/vi/querying/graph-client/_meta.js delete mode 100644 website/pages/vi/release-notes/_meta.js create mode 100644 website/pages/vi/resources/_meta.js rename website/pages/vi/{network => resources}/benefits.mdx (100%) rename website/pages/vi/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/vi/resources/release-notes/_meta.js rename website/pages/vi/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/vi/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/vi/resources/roles/_meta.js rename website/pages/vi/{network => resources/roles}/curating.mdx (100%) rename website/pages/vi/{network => resources/roles}/delegating.mdx (100%) rename website/pages/vi/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/vi/sps/_meta.js create mode 100644 website/pages/vi/subgraphs/_meta.js rename website/pages/vi/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/vi/subgraphs/cookbook/_meta.js rename website/pages/vi/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/vi/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/vi/subgraphs/developing/_meta.js create mode 100644 website/pages/vi/subgraphs/developing/creating/_meta.js rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/vi/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/vi/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/vi/subgraphs/developing/deploying/_meta.js rename website/pages/vi/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/vi/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/vi/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/vi/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/vi/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/vi/subgraphs/developing/managing/_meta.js rename website/pages/vi/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/vi/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/vi/subgraphs/developing/publishing/_meta.js rename website/pages/vi/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/vi/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/vi/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/vi/subgraphs/querying/_meta.js rename website/pages/vi/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/vi/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/vi/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/vi/subgraphs/querying/graph-client/_meta.js rename website/pages/vi/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/vi/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/vi/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/vi/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/vi/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/vi/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/vi/substreams/_meta.js rename website/pages/vi/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/vi/substreams/sps/_meta.js rename website/pages/vi/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/vi/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/vi/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/vi/{ => substreams}/sps/triggers.mdx (100%) delete mode 100644 website/pages/zh/cookbook/_meta.js delete mode 100644 website/pages/zh/developing/_meta.js delete mode 100644 website/pages/zh/developing/creating-a-subgraph/_meta.js delete mode 100644 website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js delete mode 100644 website/pages/zh/developing/deploying/_meta.js delete mode 100644 website/pages/zh/developing/managing/_meta.js delete mode 100644 website/pages/zh/developing/publishing/_meta.js delete mode 100644 website/pages/zh/indexer-tooling/_meta.js create mode 100644 website/pages/zh/indexing/_meta.js rename website/pages/zh/{ => indexing}/chain-integration-overview.mdx (100%) rename website/pages/zh/{indexing.mdx => indexing/introduction.mdx} (100%) rename website/pages/zh/{ => indexing}/new-chain-integration.mdx (100%) rename website/pages/zh/{ => indexing}/supported-network-requirements.mdx (100%) rename website/pages/zh/{ => indexing}/tap.mdx (100%) create mode 100644 website/pages/zh/indexing/tooling/_meta.js rename website/pages/zh/{indexer-tooling => indexing/tooling}/firehose.mdx (100%) rename website/pages/zh/{indexer-tooling => indexing/tooling}/graphcast.mdx (100%) rename website/pages/zh/{indexer-tooling => indexing/tooling}/operating-graph-node.mdx (100%) delete mode 100644 website/pages/zh/network/_meta.js delete mode 100644 website/pages/zh/network/overview.mdx delete mode 100644 website/pages/zh/querying/_meta.js delete mode 100644 website/pages/zh/querying/graph-client/_meta.js delete mode 100644 website/pages/zh/release-notes/_meta.js create mode 100644 website/pages/zh/resources/_meta.js rename website/pages/zh/{network => resources}/benefits.mdx (100%) rename website/pages/zh/{ => resources}/glossary.mdx (100%) create mode 100644 website/pages/zh/resources/release-notes/_meta.js rename website/pages/zh/{ => resources}/release-notes/assemblyscript-migration-guide.mdx (100%) rename website/pages/zh/{ => resources}/release-notes/graphql-validations-migration-guide.mdx (100%) create mode 100644 website/pages/zh/resources/roles/_meta.js rename website/pages/zh/{network => resources/roles}/curating.mdx (100%) rename website/pages/zh/{network => resources/roles}/delegating.mdx (100%) rename website/pages/zh/{network => resources}/tokenomics.mdx (100%) delete mode 100644 website/pages/zh/sps/_meta.js create mode 100644 website/pages/zh/subgraphs/_meta.js rename website/pages/zh/{ => subgraphs}/billing.mdx (100%) create mode 100644 website/pages/zh/subgraphs/cookbook/_meta.js rename website/pages/zh/{ => subgraphs}/cookbook/arweave.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/avoid-eth-calls.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/cosmos.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/derivedfrom.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/enums.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/grafting-hotfix.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/grafting.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/immutable-entities-bytes-as-ids.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/near.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/pruning.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/subgraph-debug-forking.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/subgraph-uncrashable.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/substreams-powered-subgraphs.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/timeseries.mdx (100%) rename website/pages/zh/{ => subgraphs}/cookbook/transfer-to-the-graph.mdx (100%) create mode 100644 website/pages/zh/subgraphs/developing/_meta.js create mode 100644 website/pages/zh/subgraphs/developing/creating/_meta.js rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/advanced.mdx (100%) rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/assemblyscript-mappings.mdx (100%) create mode 100644 website/pages/zh/subgraphs/developing/creating/graph-ts/_meta.js rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/api.mdx (100%) rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/graph-ts/common-issues.mdx (100%) rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/install-the-cli.mdx (100%) rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/ql-schema.mdx (100%) rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/starting-your-subgraph.mdx (100%) rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/subgraph-manifest.mdx (100%) rename website/pages/zh/{developing/creating-a-subgraph => subgraphs/developing/creating}/unit-testing-framework.mdx (100%) create mode 100644 website/pages/zh/subgraphs/developing/deploying/_meta.js rename website/pages/zh/{ => subgraphs}/developing/deploying/multiple-networks.mdx (100%) rename website/pages/zh/{ => subgraphs}/developing/deploying/subgraph-studio-faqs.mdx (100%) rename website/pages/zh/{ => subgraphs}/developing/deploying/using-subgraph-studio.mdx (100%) rename website/pages/zh/{ => subgraphs}/developing/developer-faqs.mdx (100%) rename website/pages/zh/{developing/developing.mdx => subgraphs/developing/introduction.mdx} (100%) create mode 100644 website/pages/zh/subgraphs/developing/managing/_meta.js rename website/pages/zh/{developing/managing/delete-a-subgraph.mdx => subgraphs/developing/managing/deleting-a-subgraph.mdx} (100%) rename website/pages/zh/{developing/managing/transfer-a-subgraph.mdx => subgraphs/developing/managing/transferring-a-subgraph.mdx} (100%) create mode 100644 website/pages/zh/subgraphs/developing/publishing/_meta.js rename website/pages/zh/{ => subgraphs}/developing/publishing/publishing-a-subgraph.mdx (100%) rename website/pages/zh/{ => subgraphs}/developing/subgraphs.mdx (100%) rename website/pages/zh/{ => subgraphs}/explorer.mdx (100%) create mode 100644 website/pages/zh/subgraphs/querying/_meta.js rename website/pages/zh/{querying/querying-best-practices.mdx => subgraphs/querying/best-practices.mdx} (100%) rename website/pages/zh/{ => subgraphs}/querying/distributed-systems.mdx (100%) rename website/pages/zh/{querying/querying-from-an-application.mdx => subgraphs/querying/from-an-application.mdx} (100%) create mode 100644 website/pages/zh/subgraphs/querying/graph-client/_meta.js rename website/pages/zh/{ => subgraphs}/querying/graphql-api.mdx (100%) rename website/pages/zh/{querying/querying-the-graph.mdx => subgraphs/querying/introduction.mdx} (100%) rename website/pages/zh/{ => subgraphs}/querying/managing-api-keys.mdx (100%) rename website/pages/zh/{querying/querying-with-python.mdx => subgraphs/querying/python.mdx} (100%) rename website/pages/zh/{querying/querying-by-subgraph-id-vs-deployment-id.mdx => subgraphs/querying/subgraph-id-vs-deployment-id.mdx} (100%) rename website/pages/zh/{ => subgraphs}/quick-start.mdx (100%) create mode 100644 website/pages/zh/substreams/_meta.js rename website/pages/zh/{substreams.mdx => substreams/introduction.mdx} (100%) create mode 100644 website/pages/zh/substreams/sps/_meta.js rename website/pages/zh/{ => substreams}/sps/introduction.mdx (100%) rename website/pages/zh/{ => substreams}/sps/substreams-powered-subgraphs-faq.mdx (100%) rename website/pages/zh/{ => substreams}/sps/triggers-example.mdx (100%) rename website/pages/zh/{ => substreams}/sps/triggers.mdx (100%) diff --git a/website/pages/ar/cookbook/_meta.js b/website/pages/ar/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/ar/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/_meta.js b/website/pages/ar/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/ar/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/creating-a-subgraph/_meta.js b/website/pages/ar/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/ar/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/ar/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/deploying/_meta.js b/website/pages/ar/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/ar/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/managing/_meta.js b/website/pages/ar/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/ar/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/developing/publishing/_meta.js b/website/pages/ar/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/ar/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/indexer-tooling/_meta.js b/website/pages/ar/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/ar/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/indexing/_meta.js b/website/pages/ar/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/ar/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/chain-integration-overview.mdx b/website/pages/ar/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/ar/chain-integration-overview.mdx rename to website/pages/ar/indexing/chain-integration-overview.mdx diff --git a/website/pages/ar/indexing.mdx b/website/pages/ar/indexing/introduction.mdx similarity index 100% rename from website/pages/ar/indexing.mdx rename to website/pages/ar/indexing/introduction.mdx diff --git a/website/pages/ar/new-chain-integration.mdx b/website/pages/ar/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/ar/new-chain-integration.mdx rename to website/pages/ar/indexing/new-chain-integration.mdx diff --git a/website/pages/ar/supported-network-requirements.mdx b/website/pages/ar/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/ar/supported-network-requirements.mdx rename to website/pages/ar/indexing/supported-network-requirements.mdx diff --git a/website/pages/ar/tap.mdx b/website/pages/ar/indexing/tap.mdx similarity index 100% rename from website/pages/ar/tap.mdx rename to website/pages/ar/indexing/tap.mdx diff --git a/website/pages/ar/indexing/tooling/_meta.js b/website/pages/ar/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/ar/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/indexer-tooling/firehose.mdx b/website/pages/ar/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/ar/indexer-tooling/firehose.mdx rename to website/pages/ar/indexing/tooling/firehose.mdx diff --git a/website/pages/ar/indexer-tooling/graphcast.mdx b/website/pages/ar/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/ar/indexer-tooling/graphcast.mdx rename to website/pages/ar/indexing/tooling/graphcast.mdx diff --git a/website/pages/ar/indexer-tooling/operating-graph-node.mdx b/website/pages/ar/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ar/indexer-tooling/operating-graph-node.mdx rename to website/pages/ar/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/ar/network/_meta.js b/website/pages/ar/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ar/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/network/overview.mdx b/website/pages/ar/network/overview.mdx deleted file mode 100644 index c6fdf2fdc81f..000000000000 --- a/website/pages/ar/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![اقتصاد الـ Token](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/ar/querying/_meta.js b/website/pages/ar/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/ar/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/querying/graph-client/_meta.js b/website/pages/ar/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/ar/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/release-notes/_meta.js b/website/pages/ar/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/ar/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/resources/_meta.js b/website/pages/ar/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/ar/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/network/benefits.mdx b/website/pages/ar/resources/benefits.mdx similarity index 100% rename from website/pages/ar/network/benefits.mdx rename to website/pages/ar/resources/benefits.mdx diff --git a/website/pages/ar/glossary.mdx b/website/pages/ar/resources/glossary.mdx similarity index 100% rename from website/pages/ar/glossary.mdx rename to website/pages/ar/resources/glossary.mdx diff --git a/website/pages/ar/resources/release-notes/_meta.js b/website/pages/ar/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/ar/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ar/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/ar/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/ar/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/ar/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ar/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/ar/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/ar/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/ar/resources/roles/_meta.js b/website/pages/ar/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/ar/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/network/curating.mdx b/website/pages/ar/resources/roles/curating.mdx similarity index 100% rename from website/pages/ar/network/curating.mdx rename to website/pages/ar/resources/roles/curating.mdx diff --git a/website/pages/ar/network/delegating.mdx b/website/pages/ar/resources/roles/delegating.mdx similarity index 100% rename from website/pages/ar/network/delegating.mdx rename to website/pages/ar/resources/roles/delegating.mdx diff --git a/website/pages/ar/network/tokenomics.mdx b/website/pages/ar/resources/tokenomics.mdx similarity index 100% rename from website/pages/ar/network/tokenomics.mdx rename to website/pages/ar/resources/tokenomics.mdx diff --git a/website/pages/ar/sps/_meta.js b/website/pages/ar/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/ar/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ar/subgraphs/_meta.js b/website/pages/ar/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/ar/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/billing.mdx b/website/pages/ar/subgraphs/billing.mdx similarity index 100% rename from website/pages/ar/billing.mdx rename to website/pages/ar/subgraphs/billing.mdx diff --git a/website/pages/ar/subgraphs/cookbook/_meta.js b/website/pages/ar/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/ar/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/cookbook/arweave.mdx b/website/pages/ar/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/ar/cookbook/arweave.mdx rename to website/pages/ar/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/ar/cookbook/avoid-eth-calls.mdx b/website/pages/ar/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/ar/cookbook/avoid-eth-calls.mdx rename to website/pages/ar/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/ar/cookbook/cosmos.mdx b/website/pages/ar/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/ar/cookbook/cosmos.mdx rename to website/pages/ar/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/ar/cookbook/derivedfrom.mdx b/website/pages/ar/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/ar/cookbook/derivedfrom.mdx rename to website/pages/ar/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/ar/cookbook/enums.mdx b/website/pages/ar/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/ar/cookbook/enums.mdx rename to website/pages/ar/subgraphs/cookbook/enums.mdx diff --git a/website/pages/ar/cookbook/grafting-hotfix.mdx b/website/pages/ar/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/ar/cookbook/grafting-hotfix.mdx rename to website/pages/ar/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/ar/cookbook/grafting.mdx b/website/pages/ar/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/ar/cookbook/grafting.mdx rename to website/pages/ar/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/ar/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ar/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/ar/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ar/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/ar/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ar/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/ar/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/ar/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/ar/cookbook/near.mdx b/website/pages/ar/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/ar/cookbook/near.mdx rename to website/pages/ar/subgraphs/cookbook/near.mdx diff --git a/website/pages/ar/cookbook/pruning.mdx b/website/pages/ar/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/ar/cookbook/pruning.mdx rename to website/pages/ar/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/ar/cookbook/subgraph-debug-forking.mdx b/website/pages/ar/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/ar/cookbook/subgraph-debug-forking.mdx rename to website/pages/ar/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/ar/cookbook/subgraph-uncrashable.mdx b/website/pages/ar/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/ar/cookbook/subgraph-uncrashable.mdx rename to website/pages/ar/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/ar/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/ar/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/ar/cookbook/timeseries.mdx b/website/pages/ar/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/ar/cookbook/timeseries.mdx rename to website/pages/ar/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/ar/cookbook/transfer-to-the-graph.mdx b/website/pages/ar/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/ar/cookbook/transfer-to-the-graph.mdx rename to website/pages/ar/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/ar/subgraphs/developing/_meta.js b/website/pages/ar/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/ar/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/subgraphs/developing/creating/_meta.js b/website/pages/ar/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/ar/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/developing/creating-a-subgraph/advanced.mdx b/website/pages/ar/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/advanced.mdx rename to website/pages/ar/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/ar/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ar/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/ar/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/ar/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/ar/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/ar/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/ar/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/ar/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/ar/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/ar/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/ar/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/ar/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/ar/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ar/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/ar/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/ar/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ar/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/ar/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/ar/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/ar/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/ar/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/ar/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/ar/subgraphs/developing/deploying/_meta.js b/website/pages/ar/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/ar/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/developing/deploying/multiple-networks.mdx b/website/pages/ar/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ar/developing/deploying/multiple-networks.mdx rename to website/pages/ar/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ar/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ar/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ar/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ar/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ar/developing/deploying/using-subgraph-studio.mdx b/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ar/developing/deploying/using-subgraph-studio.mdx rename to website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ar/developing/developer-faqs.mdx b/website/pages/ar/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/ar/developing/developer-faqs.mdx rename to website/pages/ar/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/ar/developing/developing.mdx b/website/pages/ar/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/ar/developing/developing.mdx rename to website/pages/ar/subgraphs/developing/introduction.mdx diff --git a/website/pages/ar/subgraphs/developing/managing/_meta.js b/website/pages/ar/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/ar/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/developing/managing/delete-a-subgraph.mdx b/website/pages/ar/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/ar/developing/managing/delete-a-subgraph.mdx rename to website/pages/ar/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/ar/developing/managing/transfer-a-subgraph.mdx b/website/pages/ar/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/ar/developing/managing/transfer-a-subgraph.mdx rename to website/pages/ar/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/ar/subgraphs/developing/publishing/_meta.js b/website/pages/ar/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/ar/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ar/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ar/developing/subgraphs.mdx b/website/pages/ar/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/ar/developing/subgraphs.mdx rename to website/pages/ar/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/ar/explorer.mdx b/website/pages/ar/subgraphs/explorer.mdx similarity index 100% rename from website/pages/ar/explorer.mdx rename to website/pages/ar/subgraphs/explorer.mdx diff --git a/website/pages/ar/subgraphs/querying/_meta.js b/website/pages/ar/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/ar/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/querying/querying-best-practices.mdx b/website/pages/ar/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/ar/querying/querying-best-practices.mdx rename to website/pages/ar/subgraphs/querying/best-practices.mdx diff --git a/website/pages/ar/querying/distributed-systems.mdx b/website/pages/ar/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/ar/querying/distributed-systems.mdx rename to website/pages/ar/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/ar/querying/querying-from-an-application.mdx b/website/pages/ar/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/ar/querying/querying-from-an-application.mdx rename to website/pages/ar/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/ar/subgraphs/querying/graph-client/_meta.js b/website/pages/ar/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/ar/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/querying/graphql-api.mdx b/website/pages/ar/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/ar/querying/graphql-api.mdx rename to website/pages/ar/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/ar/querying/querying-the-graph.mdx b/website/pages/ar/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/ar/querying/querying-the-graph.mdx rename to website/pages/ar/subgraphs/querying/introduction.mdx diff --git a/website/pages/ar/querying/managing-api-keys.mdx b/website/pages/ar/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/ar/querying/managing-api-keys.mdx rename to website/pages/ar/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/ar/querying/querying-with-python.mdx b/website/pages/ar/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/ar/querying/querying-with-python.mdx rename to website/pages/ar/subgraphs/querying/python.mdx diff --git a/website/pages/ar/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/ar/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/ar/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/ar/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/ar/quick-start.mdx b/website/pages/ar/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/ar/quick-start.mdx rename to website/pages/ar/subgraphs/quick-start.mdx diff --git a/website/pages/ar/substreams/_meta.js b/website/pages/ar/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/ar/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/substreams.mdx b/website/pages/ar/substreams/introduction.mdx similarity index 100% rename from website/pages/ar/substreams.mdx rename to website/pages/ar/substreams/introduction.mdx diff --git a/website/pages/ar/substreams/sps/_meta.js b/website/pages/ar/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/ar/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ar/sps/introduction.mdx b/website/pages/ar/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/ar/sps/introduction.mdx rename to website/pages/ar/substreams/sps/introduction.mdx diff --git a/website/pages/ar/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ar/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ar/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ar/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ar/sps/triggers-example.mdx b/website/pages/ar/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/ar/sps/triggers-example.mdx rename to website/pages/ar/substreams/sps/triggers-example.mdx diff --git a/website/pages/ar/sps/triggers.mdx b/website/pages/ar/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/ar/sps/triggers.mdx rename to website/pages/ar/substreams/sps/triggers.mdx diff --git a/website/pages/cs/cookbook/_meta.js b/website/pages/cs/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/cs/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/_meta.js b/website/pages/cs/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/cs/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/creating-a-subgraph/_meta.js b/website/pages/cs/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/cs/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/cs/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/deploying/_meta.js b/website/pages/cs/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/cs/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/managing/_meta.js b/website/pages/cs/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/cs/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/developing/publishing/_meta.js b/website/pages/cs/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/cs/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/indexer-tooling/_meta.js b/website/pages/cs/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/cs/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/indexing/_meta.js b/website/pages/cs/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/cs/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/chain-integration-overview.mdx b/website/pages/cs/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/cs/chain-integration-overview.mdx rename to website/pages/cs/indexing/chain-integration-overview.mdx diff --git a/website/pages/cs/indexing.mdx b/website/pages/cs/indexing/introduction.mdx similarity index 100% rename from website/pages/cs/indexing.mdx rename to website/pages/cs/indexing/introduction.mdx diff --git a/website/pages/cs/new-chain-integration.mdx b/website/pages/cs/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/cs/new-chain-integration.mdx rename to website/pages/cs/indexing/new-chain-integration.mdx diff --git a/website/pages/cs/supported-network-requirements.mdx b/website/pages/cs/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/cs/supported-network-requirements.mdx rename to website/pages/cs/indexing/supported-network-requirements.mdx diff --git a/website/pages/cs/tap.mdx b/website/pages/cs/indexing/tap.mdx similarity index 100% rename from website/pages/cs/tap.mdx rename to website/pages/cs/indexing/tap.mdx diff --git a/website/pages/cs/indexing/tooling/_meta.js b/website/pages/cs/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/cs/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/indexer-tooling/firehose.mdx b/website/pages/cs/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/cs/indexer-tooling/firehose.mdx rename to website/pages/cs/indexing/tooling/firehose.mdx diff --git a/website/pages/cs/indexer-tooling/graphcast.mdx b/website/pages/cs/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/cs/indexer-tooling/graphcast.mdx rename to website/pages/cs/indexing/tooling/graphcast.mdx diff --git a/website/pages/cs/indexer-tooling/operating-graph-node.mdx b/website/pages/cs/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/cs/indexer-tooling/operating-graph-node.mdx rename to website/pages/cs/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/cs/network/_meta.js b/website/pages/cs/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/cs/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/network/overview.mdx b/website/pages/cs/network/overview.mdx deleted file mode 100644 index aeb16e0d488e..000000000000 --- a/website/pages/cs/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Přehled sítě ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/cs/querying/_meta.js b/website/pages/cs/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/cs/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/querying/graph-client/_meta.js b/website/pages/cs/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/cs/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/release-notes/_meta.js b/website/pages/cs/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/cs/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/resources/_meta.js b/website/pages/cs/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/cs/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/network/benefits.mdx b/website/pages/cs/resources/benefits.mdx similarity index 100% rename from website/pages/cs/network/benefits.mdx rename to website/pages/cs/resources/benefits.mdx diff --git a/website/pages/cs/glossary.mdx b/website/pages/cs/resources/glossary.mdx similarity index 100% rename from website/pages/cs/glossary.mdx rename to website/pages/cs/resources/glossary.mdx diff --git a/website/pages/cs/resources/release-notes/_meta.js b/website/pages/cs/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/cs/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx b/website/pages/cs/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/cs/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/cs/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/cs/release-notes/graphql-validations-migration-guide.mdx b/website/pages/cs/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/cs/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/cs/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/cs/resources/roles/_meta.js b/website/pages/cs/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/cs/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/network/curating.mdx b/website/pages/cs/resources/roles/curating.mdx similarity index 100% rename from website/pages/cs/network/curating.mdx rename to website/pages/cs/resources/roles/curating.mdx diff --git a/website/pages/cs/network/delegating.mdx b/website/pages/cs/resources/roles/delegating.mdx similarity index 100% rename from website/pages/cs/network/delegating.mdx rename to website/pages/cs/resources/roles/delegating.mdx diff --git a/website/pages/cs/network/tokenomics.mdx b/website/pages/cs/resources/tokenomics.mdx similarity index 100% rename from website/pages/cs/network/tokenomics.mdx rename to website/pages/cs/resources/tokenomics.mdx diff --git a/website/pages/cs/sps/_meta.js b/website/pages/cs/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/cs/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/cs/subgraphs/_meta.js b/website/pages/cs/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/cs/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/billing.mdx b/website/pages/cs/subgraphs/billing.mdx similarity index 100% rename from website/pages/cs/billing.mdx rename to website/pages/cs/subgraphs/billing.mdx diff --git a/website/pages/cs/subgraphs/cookbook/_meta.js b/website/pages/cs/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/cs/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/cookbook/arweave.mdx b/website/pages/cs/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/cs/cookbook/arweave.mdx rename to website/pages/cs/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/cs/cookbook/avoid-eth-calls.mdx b/website/pages/cs/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/cs/cookbook/avoid-eth-calls.mdx rename to website/pages/cs/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/cs/cookbook/cosmos.mdx b/website/pages/cs/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/cs/cookbook/cosmos.mdx rename to website/pages/cs/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/cs/cookbook/derivedfrom.mdx b/website/pages/cs/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/cs/cookbook/derivedfrom.mdx rename to website/pages/cs/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/cs/cookbook/enums.mdx b/website/pages/cs/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/cs/cookbook/enums.mdx rename to website/pages/cs/subgraphs/cookbook/enums.mdx diff --git a/website/pages/cs/cookbook/grafting-hotfix.mdx b/website/pages/cs/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/cs/cookbook/grafting-hotfix.mdx rename to website/pages/cs/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/cs/cookbook/grafting.mdx b/website/pages/cs/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/cs/cookbook/grafting.mdx rename to website/pages/cs/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/cs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/cs/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/cs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/cs/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/cs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/cs/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/cs/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/cs/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/cs/cookbook/near.mdx b/website/pages/cs/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/cs/cookbook/near.mdx rename to website/pages/cs/subgraphs/cookbook/near.mdx diff --git a/website/pages/cs/cookbook/pruning.mdx b/website/pages/cs/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/cs/cookbook/pruning.mdx rename to website/pages/cs/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/cs/cookbook/subgraph-debug-forking.mdx b/website/pages/cs/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/cs/cookbook/subgraph-debug-forking.mdx rename to website/pages/cs/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/cs/cookbook/subgraph-uncrashable.mdx b/website/pages/cs/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/cs/cookbook/subgraph-uncrashable.mdx rename to website/pages/cs/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/cs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/cs/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/cs/cookbook/timeseries.mdx b/website/pages/cs/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/cs/cookbook/timeseries.mdx rename to website/pages/cs/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/cs/cookbook/transfer-to-the-graph.mdx b/website/pages/cs/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/cs/cookbook/transfer-to-the-graph.mdx rename to website/pages/cs/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/cs/subgraphs/developing/_meta.js b/website/pages/cs/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/cs/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/subgraphs/developing/creating/_meta.js b/website/pages/cs/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/cs/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/developing/creating-a-subgraph/advanced.mdx b/website/pages/cs/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/advanced.mdx rename to website/pages/cs/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/cs/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/cs/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/cs/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/cs/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/cs/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/cs/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/cs/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/cs/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/cs/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/cs/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/cs/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/cs/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/cs/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/cs/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/cs/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/cs/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/cs/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/cs/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/cs/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/cs/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/cs/subgraphs/developing/deploying/_meta.js b/website/pages/cs/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/cs/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/developing/deploying/multiple-networks.mdx b/website/pages/cs/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/cs/developing/deploying/multiple-networks.mdx rename to website/pages/cs/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/cs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/cs/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/cs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/cs/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/cs/developing/deploying/using-subgraph-studio.mdx b/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/cs/developing/deploying/using-subgraph-studio.mdx rename to website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/cs/developing/developer-faqs.mdx b/website/pages/cs/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/cs/developing/developer-faqs.mdx rename to website/pages/cs/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/cs/developing/developing.mdx b/website/pages/cs/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/cs/developing/developing.mdx rename to website/pages/cs/subgraphs/developing/introduction.mdx diff --git a/website/pages/cs/subgraphs/developing/managing/_meta.js b/website/pages/cs/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/cs/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/developing/managing/delete-a-subgraph.mdx b/website/pages/cs/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/cs/developing/managing/delete-a-subgraph.mdx rename to website/pages/cs/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/cs/developing/managing/transfer-a-subgraph.mdx b/website/pages/cs/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/cs/developing/managing/transfer-a-subgraph.mdx rename to website/pages/cs/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/cs/subgraphs/developing/publishing/_meta.js b/website/pages/cs/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/cs/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/cs/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/cs/developing/subgraphs.mdx b/website/pages/cs/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/cs/developing/subgraphs.mdx rename to website/pages/cs/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/cs/explorer.mdx b/website/pages/cs/subgraphs/explorer.mdx similarity index 100% rename from website/pages/cs/explorer.mdx rename to website/pages/cs/subgraphs/explorer.mdx diff --git a/website/pages/cs/subgraphs/querying/_meta.js b/website/pages/cs/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/cs/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/querying/querying-best-practices.mdx b/website/pages/cs/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/cs/querying/querying-best-practices.mdx rename to website/pages/cs/subgraphs/querying/best-practices.mdx diff --git a/website/pages/cs/querying/distributed-systems.mdx b/website/pages/cs/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/cs/querying/distributed-systems.mdx rename to website/pages/cs/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/cs/querying/querying-from-an-application.mdx b/website/pages/cs/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/cs/querying/querying-from-an-application.mdx rename to website/pages/cs/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/cs/subgraphs/querying/graph-client/_meta.js b/website/pages/cs/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/cs/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/querying/graphql-api.mdx b/website/pages/cs/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/cs/querying/graphql-api.mdx rename to website/pages/cs/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/cs/querying/querying-the-graph.mdx b/website/pages/cs/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/cs/querying/querying-the-graph.mdx rename to website/pages/cs/subgraphs/querying/introduction.mdx diff --git a/website/pages/cs/querying/managing-api-keys.mdx b/website/pages/cs/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/cs/querying/managing-api-keys.mdx rename to website/pages/cs/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/cs/querying/querying-with-python.mdx b/website/pages/cs/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/cs/querying/querying-with-python.mdx rename to website/pages/cs/subgraphs/querying/python.mdx diff --git a/website/pages/cs/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/cs/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/cs/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/cs/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/cs/quick-start.mdx b/website/pages/cs/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/cs/quick-start.mdx rename to website/pages/cs/subgraphs/quick-start.mdx diff --git a/website/pages/cs/substreams/_meta.js b/website/pages/cs/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/cs/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/substreams.mdx b/website/pages/cs/substreams/introduction.mdx similarity index 100% rename from website/pages/cs/substreams.mdx rename to website/pages/cs/substreams/introduction.mdx diff --git a/website/pages/cs/substreams/sps/_meta.js b/website/pages/cs/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/cs/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/cs/sps/introduction.mdx b/website/pages/cs/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/cs/sps/introduction.mdx rename to website/pages/cs/substreams/sps/introduction.mdx diff --git a/website/pages/cs/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/cs/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/cs/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/cs/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/cs/sps/triggers-example.mdx b/website/pages/cs/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/cs/sps/triggers-example.mdx rename to website/pages/cs/substreams/sps/triggers-example.mdx diff --git a/website/pages/cs/sps/triggers.mdx b/website/pages/cs/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/cs/sps/triggers.mdx rename to website/pages/cs/substreams/sps/triggers.mdx diff --git a/website/pages/de/cookbook/_meta.js b/website/pages/de/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/de/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/_meta.js b/website/pages/de/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/de/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/creating-a-subgraph/_meta.js b/website/pages/de/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/de/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/de/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/deploying/_meta.js b/website/pages/de/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/de/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/managing/_meta.js b/website/pages/de/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/de/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/developing/publishing/_meta.js b/website/pages/de/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/de/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/indexer-tooling/_meta.js b/website/pages/de/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/de/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/indexing/_meta.js b/website/pages/de/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/de/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/chain-integration-overview.mdx b/website/pages/de/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/de/chain-integration-overview.mdx rename to website/pages/de/indexing/chain-integration-overview.mdx diff --git a/website/pages/de/indexing.mdx b/website/pages/de/indexing/introduction.mdx similarity index 100% rename from website/pages/de/indexing.mdx rename to website/pages/de/indexing/introduction.mdx diff --git a/website/pages/de/new-chain-integration.mdx b/website/pages/de/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/de/new-chain-integration.mdx rename to website/pages/de/indexing/new-chain-integration.mdx diff --git a/website/pages/de/supported-network-requirements.mdx b/website/pages/de/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/de/supported-network-requirements.mdx rename to website/pages/de/indexing/supported-network-requirements.mdx diff --git a/website/pages/de/tap.mdx b/website/pages/de/indexing/tap.mdx similarity index 100% rename from website/pages/de/tap.mdx rename to website/pages/de/indexing/tap.mdx diff --git a/website/pages/de/indexing/tooling/_meta.js b/website/pages/de/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/de/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/indexer-tooling/firehose.mdx b/website/pages/de/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/de/indexer-tooling/firehose.mdx rename to website/pages/de/indexing/tooling/firehose.mdx diff --git a/website/pages/de/indexer-tooling/graphcast.mdx b/website/pages/de/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/de/indexer-tooling/graphcast.mdx rename to website/pages/de/indexing/tooling/graphcast.mdx diff --git a/website/pages/de/indexer-tooling/operating-graph-node.mdx b/website/pages/de/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/de/indexer-tooling/operating-graph-node.mdx rename to website/pages/de/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/de/network/_meta.js b/website/pages/de/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/de/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/network/overview.mdx b/website/pages/de/network/overview.mdx deleted file mode 100644 index e89a12cde9bd..000000000000 --- a/website/pages/de/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Besonderheiten - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/de/querying/_meta.js b/website/pages/de/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/de/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/querying/graph-client/_meta.js b/website/pages/de/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/de/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/release-notes/_meta.js b/website/pages/de/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/de/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/resources/_meta.js b/website/pages/de/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/de/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/network/benefits.mdx b/website/pages/de/resources/benefits.mdx similarity index 100% rename from website/pages/de/network/benefits.mdx rename to website/pages/de/resources/benefits.mdx diff --git a/website/pages/de/glossary.mdx b/website/pages/de/resources/glossary.mdx similarity index 100% rename from website/pages/de/glossary.mdx rename to website/pages/de/resources/glossary.mdx diff --git a/website/pages/de/resources/release-notes/_meta.js b/website/pages/de/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/de/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/release-notes/assemblyscript-migration-guide.mdx b/website/pages/de/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/de/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/de/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/de/release-notes/graphql-validations-migration-guide.mdx b/website/pages/de/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/de/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/de/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/de/resources/roles/_meta.js b/website/pages/de/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/de/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/network/curating.mdx b/website/pages/de/resources/roles/curating.mdx similarity index 100% rename from website/pages/de/network/curating.mdx rename to website/pages/de/resources/roles/curating.mdx diff --git a/website/pages/de/network/delegating.mdx b/website/pages/de/resources/roles/delegating.mdx similarity index 100% rename from website/pages/de/network/delegating.mdx rename to website/pages/de/resources/roles/delegating.mdx diff --git a/website/pages/de/network/tokenomics.mdx b/website/pages/de/resources/tokenomics.mdx similarity index 100% rename from website/pages/de/network/tokenomics.mdx rename to website/pages/de/resources/tokenomics.mdx diff --git a/website/pages/de/sps/_meta.js b/website/pages/de/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/de/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/de/subgraphs/_meta.js b/website/pages/de/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/de/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/billing.mdx b/website/pages/de/subgraphs/billing.mdx similarity index 100% rename from website/pages/de/billing.mdx rename to website/pages/de/subgraphs/billing.mdx diff --git a/website/pages/de/subgraphs/cookbook/_meta.js b/website/pages/de/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/de/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/cookbook/arweave.mdx b/website/pages/de/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/de/cookbook/arweave.mdx rename to website/pages/de/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/de/cookbook/avoid-eth-calls.mdx b/website/pages/de/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/de/cookbook/avoid-eth-calls.mdx rename to website/pages/de/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/de/cookbook/cosmos.mdx b/website/pages/de/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/de/cookbook/cosmos.mdx rename to website/pages/de/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/de/cookbook/derivedfrom.mdx b/website/pages/de/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/de/cookbook/derivedfrom.mdx rename to website/pages/de/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/de/cookbook/enums.mdx b/website/pages/de/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/de/cookbook/enums.mdx rename to website/pages/de/subgraphs/cookbook/enums.mdx diff --git a/website/pages/de/cookbook/grafting-hotfix.mdx b/website/pages/de/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/de/cookbook/grafting-hotfix.mdx rename to website/pages/de/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/de/cookbook/grafting.mdx b/website/pages/de/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/de/cookbook/grafting.mdx rename to website/pages/de/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/de/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/de/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/de/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/de/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/de/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/de/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/de/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/de/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/de/cookbook/near.mdx b/website/pages/de/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/de/cookbook/near.mdx rename to website/pages/de/subgraphs/cookbook/near.mdx diff --git a/website/pages/de/cookbook/pruning.mdx b/website/pages/de/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/de/cookbook/pruning.mdx rename to website/pages/de/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/de/cookbook/subgraph-debug-forking.mdx b/website/pages/de/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/de/cookbook/subgraph-debug-forking.mdx rename to website/pages/de/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/de/cookbook/subgraph-uncrashable.mdx b/website/pages/de/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/de/cookbook/subgraph-uncrashable.mdx rename to website/pages/de/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/de/cookbook/substreams-powered-subgraphs.mdx b/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/de/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/de/cookbook/timeseries.mdx b/website/pages/de/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/de/cookbook/timeseries.mdx rename to website/pages/de/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/de/cookbook/transfer-to-the-graph.mdx b/website/pages/de/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/de/cookbook/transfer-to-the-graph.mdx rename to website/pages/de/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/de/subgraphs/developing/_meta.js b/website/pages/de/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/de/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/subgraphs/developing/creating/_meta.js b/website/pages/de/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/de/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/developing/creating-a-subgraph/advanced.mdx b/website/pages/de/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/advanced.mdx rename to website/pages/de/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/de/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/de/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/de/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/de/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/de/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/de/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/de/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/de/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/de/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/de/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/de/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/de/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/de/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/de/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/de/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/de/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/de/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/de/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/de/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/de/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/de/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/de/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/de/subgraphs/developing/deploying/_meta.js b/website/pages/de/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/de/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/developing/deploying/multiple-networks.mdx b/website/pages/de/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/de/developing/deploying/multiple-networks.mdx rename to website/pages/de/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/de/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/de/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/de/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/de/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/de/developing/deploying/using-subgraph-studio.mdx b/website/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/de/developing/deploying/using-subgraph-studio.mdx rename to website/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/de/developing/developer-faqs.mdx b/website/pages/de/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/de/developing/developer-faqs.mdx rename to website/pages/de/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/de/developing/developing.mdx b/website/pages/de/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/de/developing/developing.mdx rename to website/pages/de/subgraphs/developing/introduction.mdx diff --git a/website/pages/de/subgraphs/developing/managing/_meta.js b/website/pages/de/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/de/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/developing/managing/delete-a-subgraph.mdx b/website/pages/de/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/de/developing/managing/delete-a-subgraph.mdx rename to website/pages/de/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/de/developing/managing/transfer-a-subgraph.mdx b/website/pages/de/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/de/developing/managing/transfer-a-subgraph.mdx rename to website/pages/de/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/de/subgraphs/developing/publishing/_meta.js b/website/pages/de/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/de/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/developing/publishing/publishing-a-subgraph.mdx b/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/de/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/de/developing/subgraphs.mdx b/website/pages/de/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/de/developing/subgraphs.mdx rename to website/pages/de/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/de/explorer.mdx b/website/pages/de/subgraphs/explorer.mdx similarity index 100% rename from website/pages/de/explorer.mdx rename to website/pages/de/subgraphs/explorer.mdx diff --git a/website/pages/de/subgraphs/querying/_meta.js b/website/pages/de/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/de/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/querying/querying-best-practices.mdx b/website/pages/de/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/de/querying/querying-best-practices.mdx rename to website/pages/de/subgraphs/querying/best-practices.mdx diff --git a/website/pages/de/querying/distributed-systems.mdx b/website/pages/de/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/de/querying/distributed-systems.mdx rename to website/pages/de/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/de/querying/querying-from-an-application.mdx b/website/pages/de/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/de/querying/querying-from-an-application.mdx rename to website/pages/de/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/de/subgraphs/querying/graph-client/_meta.js b/website/pages/de/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/de/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/querying/graphql-api.mdx b/website/pages/de/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/de/querying/graphql-api.mdx rename to website/pages/de/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/de/querying/querying-the-graph.mdx b/website/pages/de/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/de/querying/querying-the-graph.mdx rename to website/pages/de/subgraphs/querying/introduction.mdx diff --git a/website/pages/de/querying/managing-api-keys.mdx b/website/pages/de/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/de/querying/managing-api-keys.mdx rename to website/pages/de/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/de/querying/querying-with-python.mdx b/website/pages/de/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/de/querying/querying-with-python.mdx rename to website/pages/de/subgraphs/querying/python.mdx diff --git a/website/pages/de/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/de/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/de/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/de/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/de/quick-start.mdx b/website/pages/de/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/de/quick-start.mdx rename to website/pages/de/subgraphs/quick-start.mdx diff --git a/website/pages/de/substreams/_meta.js b/website/pages/de/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/de/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/substreams.mdx b/website/pages/de/substreams/introduction.mdx similarity index 100% rename from website/pages/de/substreams.mdx rename to website/pages/de/substreams/introduction.mdx diff --git a/website/pages/de/substreams/sps/_meta.js b/website/pages/de/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/de/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/de/sps/introduction.mdx b/website/pages/de/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/de/sps/introduction.mdx rename to website/pages/de/substreams/sps/introduction.mdx diff --git a/website/pages/de/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/de/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/de/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/de/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/de/sps/triggers-example.mdx b/website/pages/de/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/de/sps/triggers-example.mdx rename to website/pages/de/substreams/sps/triggers-example.mdx diff --git a/website/pages/de/sps/triggers.mdx b/website/pages/de/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/de/sps/triggers.mdx rename to website/pages/de/substreams/sps/triggers.mdx diff --git a/website/pages/en/_meta.js b/website/pages/en/_meta.js index dc747d7df3a6..096e98263be9 100644 --- a/website/pages/en/_meta.js +++ b/website/pages/en/_meta.js @@ -10,12 +10,9 @@ export default { type: 'heading', title: 'Subgraphs', }, - 'quick-start': '', - explorer: '', - querying: 'Querying', - developing: 'Developing', - billing: '', - cookbook: 'Cookbook', + subgraphs: { + type: 'children', + }, '---2': { type: 'separator', }, @@ -23,9 +20,9 @@ export default { type: 'heading', title: 'Substreams', }, - substreams: '', - sps: 'Substreams Powered Subgraphs', - cookbook: 'Cookbooks', + substreams: { + type: 'children', + }, '---3': { type: 'separator', }, @@ -33,12 +30,9 @@ export default { type: 'heading', title: 'Indexing', }, - indexing: '', - 'indexer-tooling': 'Indexer Tooling', - tap: '', - 'supported-network-requirements': '', - 'chain-integration-overview': '', - 'new-chain-integration': '', + indexing: { + type: 'children', + }, '---4': { type: 'separator', }, @@ -46,8 +40,8 @@ export default { type: 'heading', title: 'Resources', }, - glossary: '', - network: 'Network', - 'release-notes': 'Release Notes & Upgrade Guides', + resources: { + type: 'children', + }, archived: 'Archived', } diff --git a/website/pages/en/developing/managing/_meta.js b/website/pages/en/developing/managing/_meta.js deleted file mode 100644 index 99095b5ac996..000000000000 --- a/website/pages/en/developing/managing/_meta.js +++ /dev/null @@ -1,4 +0,0 @@ -export default { - 'transfer-a-subgraph': '', - 'delete-a-subgraph': '', -} diff --git a/website/pages/en/indexing/_meta.js b/website/pages/en/indexing/_meta.js new file mode 100644 index 000000000000..9f6f8f332ccd --- /dev/null +++ b/website/pages/en/indexing/_meta.js @@ -0,0 +1,8 @@ +export default { + introduction: 'Introduction', + tooling: 'Indexer Tooling', + tap: '', + 'supported-network-requirements': '', + 'chain-integration-overview': '', + 'new-chain-integration': '', +} diff --git a/website/pages/en/chain-integration-overview.mdx b/website/pages/en/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/en/chain-integration-overview.mdx rename to website/pages/en/indexing/chain-integration-overview.mdx diff --git a/website/pages/en/indexing.mdx b/website/pages/en/indexing/introduction.mdx similarity index 100% rename from website/pages/en/indexing.mdx rename to website/pages/en/indexing/introduction.mdx diff --git a/website/pages/en/new-chain-integration.mdx b/website/pages/en/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/en/new-chain-integration.mdx rename to website/pages/en/indexing/new-chain-integration.mdx diff --git a/website/pages/en/supported-network-requirements.mdx b/website/pages/en/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/en/supported-network-requirements.mdx rename to website/pages/en/indexing/supported-network-requirements.mdx diff --git a/website/pages/en/tap.mdx b/website/pages/en/indexing/tap.mdx similarity index 100% rename from website/pages/en/tap.mdx rename to website/pages/en/indexing/tap.mdx diff --git a/website/pages/en/indexer-tooling/_meta.js b/website/pages/en/indexing/tooling/_meta.js similarity index 100% rename from website/pages/en/indexer-tooling/_meta.js rename to website/pages/en/indexing/tooling/_meta.js diff --git a/website/pages/en/indexer-tooling/firehose.mdx b/website/pages/en/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/en/indexer-tooling/firehose.mdx rename to website/pages/en/indexing/tooling/firehose.mdx diff --git a/website/pages/en/indexer-tooling/graphcast.mdx b/website/pages/en/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/en/indexer-tooling/graphcast.mdx rename to website/pages/en/indexing/tooling/graphcast.mdx diff --git a/website/pages/en/indexer-tooling/operating-graph-node.mdx b/website/pages/en/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/en/indexer-tooling/operating-graph-node.mdx rename to website/pages/en/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/en/network/_meta.js b/website/pages/en/network/_meta.js deleted file mode 100644 index 4e004cf4984a..000000000000 --- a/website/pages/en/network/_meta.js +++ /dev/null @@ -1,6 +0,0 @@ -export default { - benefits: 'The Graph vs Self Hosting', - tokenomics: 'Tokenomics', - delegating: '', - curating: '', -} diff --git a/website/pages/en/querying/_meta.js b/website/pages/en/querying/_meta.js deleted file mode 100644 index 00bad821d5cb..000000000000 --- a/website/pages/en/querying/_meta.js +++ /dev/null @@ -1,11 +0,0 @@ -export default { - 'querying-the-graph': '', - 'managing-api-keys': '', - 'querying-best-practices': '', - 'querying-from-an-application': '', - 'distributed-systems': '', - 'graphql-api': '', - 'querying-by-subgraph-id-vs-deployment-id': '', - 'graph-client': 'Graph Client', - 'querying-with-python': 'Python (Subgrounds)', -} diff --git a/website/pages/en/resources/_meta.js b/website/pages/en/resources/_meta.js new file mode 100644 index 000000000000..0c2022498337 --- /dev/null +++ b/website/pages/en/resources/_meta.js @@ -0,0 +1,7 @@ +export default { + glossary: '', + tokenomics: 'Tokenomics', + benefits: '', + roles: 'Network Roles', + 'release-notes': 'Release Notes & Upgrade Guides', +} diff --git a/website/pages/en/network/benefits.mdx b/website/pages/en/resources/benefits.mdx similarity index 100% rename from website/pages/en/network/benefits.mdx rename to website/pages/en/resources/benefits.mdx diff --git a/website/pages/en/glossary.mdx b/website/pages/en/resources/glossary.mdx similarity index 100% rename from website/pages/en/glossary.mdx rename to website/pages/en/resources/glossary.mdx diff --git a/website/pages/en/release-notes/_meta.js b/website/pages/en/resources/release-notes/_meta.js similarity index 100% rename from website/pages/en/release-notes/_meta.js rename to website/pages/en/resources/release-notes/_meta.js diff --git a/website/pages/en/release-notes/assemblyscript-migration-guide.mdx b/website/pages/en/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/en/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/en/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/en/release-notes/graphql-validations-migration-guide.mdx b/website/pages/en/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/en/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/en/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/en/resources/roles/_meta.js b/website/pages/en/resources/roles/_meta.js new file mode 100644 index 000000000000..bf461d597f0a --- /dev/null +++ b/website/pages/en/resources/roles/_meta.js @@ -0,0 +1,4 @@ +export default { + delegating: '', + curating: '', +} diff --git a/website/pages/en/network/curating.mdx b/website/pages/en/resources/roles/curating.mdx similarity index 100% rename from website/pages/en/network/curating.mdx rename to website/pages/en/resources/roles/curating.mdx diff --git a/website/pages/en/network/delegating.mdx b/website/pages/en/resources/roles/delegating.mdx similarity index 100% rename from website/pages/en/network/delegating.mdx rename to website/pages/en/resources/roles/delegating.mdx diff --git a/website/pages/en/network/tokenomics.mdx b/website/pages/en/resources/tokenomics.mdx similarity index 100% rename from website/pages/en/network/tokenomics.mdx rename to website/pages/en/resources/tokenomics.mdx diff --git a/website/pages/en/subgraphs/_meta.js b/website/pages/en/subgraphs/_meta.js new file mode 100644 index 000000000000..70be9cdd8f59 --- /dev/null +++ b/website/pages/en/subgraphs/_meta.js @@ -0,0 +1,8 @@ +export default { + 'quick-start': '', + explorer: '', + querying: 'Querying', + developing: 'Developing', + billing: '', + cookbook: 'Cookbook', +} diff --git a/website/pages/en/billing.mdx b/website/pages/en/subgraphs/billing.mdx similarity index 100% rename from website/pages/en/billing.mdx rename to website/pages/en/subgraphs/billing.mdx diff --git a/website/pages/en/cookbook/_meta.js b/website/pages/en/subgraphs/cookbook/_meta.js similarity index 100% rename from website/pages/en/cookbook/_meta.js rename to website/pages/en/subgraphs/cookbook/_meta.js diff --git a/website/pages/en/cookbook/arweave.mdx b/website/pages/en/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/en/cookbook/arweave.mdx rename to website/pages/en/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/en/cookbook/avoid-eth-calls.mdx b/website/pages/en/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/en/cookbook/avoid-eth-calls.mdx rename to website/pages/en/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/en/cookbook/cosmos.mdx b/website/pages/en/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/en/cookbook/cosmos.mdx rename to website/pages/en/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/en/cookbook/derivedfrom.mdx b/website/pages/en/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/en/cookbook/derivedfrom.mdx rename to website/pages/en/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/en/cookbook/enums.mdx b/website/pages/en/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/en/cookbook/enums.mdx rename to website/pages/en/subgraphs/cookbook/enums.mdx diff --git a/website/pages/en/cookbook/grafting-hotfix.mdx b/website/pages/en/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/en/cookbook/grafting-hotfix.mdx rename to website/pages/en/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/en/cookbook/grafting.mdx b/website/pages/en/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/en/cookbook/grafting.mdx rename to website/pages/en/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/en/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/en/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/en/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/en/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/en/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/en/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/en/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/en/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/en/cookbook/near.mdx b/website/pages/en/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/en/cookbook/near.mdx rename to website/pages/en/subgraphs/cookbook/near.mdx diff --git a/website/pages/en/cookbook/pruning.mdx b/website/pages/en/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/en/cookbook/pruning.mdx rename to website/pages/en/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/en/cookbook/subgraph-debug-forking.mdx b/website/pages/en/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/en/cookbook/subgraph-debug-forking.mdx rename to website/pages/en/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/en/cookbook/subgraph-uncrashable.mdx b/website/pages/en/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/en/cookbook/subgraph-uncrashable.mdx rename to website/pages/en/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/en/cookbook/substreams-powered-subgraphs.mdx b/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/en/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/en/cookbook/timeseries.mdx b/website/pages/en/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/en/cookbook/timeseries.mdx rename to website/pages/en/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/en/cookbook/transfer-to-the-graph.mdx b/website/pages/en/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/en/cookbook/transfer-to-the-graph.mdx rename to website/pages/en/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/en/developing/_meta.js b/website/pages/en/subgraphs/developing/_meta.js similarity index 62% rename from website/pages/en/developing/_meta.js rename to website/pages/en/subgraphs/developing/_meta.js index 72fe0cc49af1..e14fdf572f74 100644 --- a/website/pages/en/developing/_meta.js +++ b/website/pages/en/subgraphs/developing/_meta.js @@ -1,7 +1,7 @@ export default { - developing: 'Introduction to Development', + introduction: 'Introduction', subgraphs: '', - 'creating-a-subgraph': 'Creating', + creating: 'Creating', deploying: 'Deploying', publishing: 'Publishing', managing: 'Managing', diff --git a/website/pages/en/developing/creating-a-subgraph/_meta.js b/website/pages/en/subgraphs/developing/creating/_meta.js similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/_meta.js rename to website/pages/en/subgraphs/developing/creating/_meta.js diff --git a/website/pages/en/developing/creating-a-subgraph/advanced.mdx b/website/pages/en/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/advanced.mdx rename to website/pages/en/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/en/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/en/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/graph-ts/[[...slug]].mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/[[...slug]].mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/graph-ts/[[...slug]].mdx rename to website/pages/en/subgraphs/developing/creating/graph-ts/[[...slug]].mdx diff --git a/website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/en/subgraphs/developing/creating/graph-ts/_meta.js similarity index 70% rename from website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js rename to website/pages/en/subgraphs/developing/creating/graph-ts/_meta.js index 05a81c9d14c3..72ba1cca43cc 100644 --- a/website/pages/en/developing/creating-a-subgraph/graph-ts/_meta.js +++ b/website/pages/en/subgraphs/developing/creating/graph-ts/_meta.js @@ -1,6 +1,6 @@ import { createCatchAllMeta } from 'nextra/catch-all' -import json from '../../../../../remote-files/graph-ts.json' assert { type: 'json' } +import json from '../../../../../../remote-files/graph-ts.json' assert { type: 'json' } export default () => createCatchAllMeta(json.filePaths, { diff --git a/website/pages/en/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/en/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/en/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/en/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/en/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/en/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/en/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/en/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/en/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/en/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/en/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/en/developing/deploying/_meta.js b/website/pages/en/subgraphs/developing/deploying/_meta.js similarity index 100% rename from website/pages/en/developing/deploying/_meta.js rename to website/pages/en/subgraphs/developing/deploying/_meta.js diff --git a/website/pages/en/developing/deploying/multiple-networks.mdx b/website/pages/en/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/en/developing/deploying/multiple-networks.mdx rename to website/pages/en/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/en/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/en/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/en/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/en/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/en/developing/deploying/using-subgraph-studio.mdx b/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/en/developing/deploying/using-subgraph-studio.mdx rename to website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/en/developing/developer-faqs.mdx b/website/pages/en/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/en/developing/developer-faqs.mdx rename to website/pages/en/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/en/developing/developing.mdx b/website/pages/en/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/en/developing/developing.mdx rename to website/pages/en/subgraphs/developing/introduction.mdx diff --git a/website/pages/en/subgraphs/developing/managing/_meta.js b/website/pages/en/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..7f23e3ebfcfc --- /dev/null +++ b/website/pages/en/subgraphs/developing/managing/_meta.js @@ -0,0 +1,4 @@ +export default { + 'transferring-a-subgraph': '', + 'deleting-a-subgraph': '', +} diff --git a/website/pages/en/developing/managing/delete-a-subgraph.mdx b/website/pages/en/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 98% rename from website/pages/en/developing/managing/delete-a-subgraph.mdx rename to website/pages/en/subgraphs/developing/managing/deleting-a-subgraph.mdx index 68ef0a37da75..f400044bb8fb 100644 --- a/website/pages/en/developing/managing/delete-a-subgraph.mdx +++ b/website/pages/en/subgraphs/developing/managing/deleting-a-subgraph.mdx @@ -1,5 +1,5 @@ --- -title: Delete a Subgraph +title: Deleting a Subgraph --- Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/). diff --git a/website/pages/en/developing/managing/transfer-a-subgraph.mdx b/website/pages/en/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 97% rename from website/pages/en/developing/managing/transfer-a-subgraph.mdx rename to website/pages/en/subgraphs/developing/managing/transferring-a-subgraph.mdx index 7a88c4c598a5..6afcdeeb303d 100644 --- a/website/pages/en/developing/managing/transfer-a-subgraph.mdx +++ b/website/pages/en/subgraphs/developing/managing/transferring-a-subgraph.mdx @@ -1,5 +1,5 @@ --- -title: Transfer a Subgraph +title: Transferring 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. diff --git a/website/pages/en/developing/publishing/_meta.js b/website/pages/en/subgraphs/developing/publishing/_meta.js similarity index 100% rename from website/pages/en/developing/publishing/_meta.js rename to website/pages/en/subgraphs/developing/publishing/_meta.js diff --git a/website/pages/en/developing/publishing/publishing-a-subgraph.mdx b/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/en/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/en/developing/subgraphs.mdx b/website/pages/en/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/en/developing/subgraphs.mdx rename to website/pages/en/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/en/explorer.mdx b/website/pages/en/subgraphs/explorer.mdx similarity index 100% rename from website/pages/en/explorer.mdx rename to website/pages/en/subgraphs/explorer.mdx diff --git a/website/pages/en/subgraphs/querying/_meta.js b/website/pages/en/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..eb6757cbf845 --- /dev/null +++ b/website/pages/en/subgraphs/querying/_meta.js @@ -0,0 +1,11 @@ +export default { + introduction: 'Introduction', + 'managing-api-keys': '', + 'best-practices': '', + 'from-an-application': '', + 'distributed-systems': '', + 'graphql-api': '', + 'subgraph-id-vs-deployment-id': '', + 'graph-client': 'Graph Client', + python: 'Python (Subgrounds)', +} diff --git a/website/pages/en/querying/querying-best-practices.mdx b/website/pages/en/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/en/querying/querying-best-practices.mdx rename to website/pages/en/subgraphs/querying/best-practices.mdx diff --git a/website/pages/en/querying/distributed-systems.mdx b/website/pages/en/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/en/querying/distributed-systems.mdx rename to website/pages/en/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/en/querying/querying-from-an-application.mdx b/website/pages/en/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/en/querying/querying-from-an-application.mdx rename to website/pages/en/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/en/querying/graph-client/[[...slug]].mdx b/website/pages/en/subgraphs/querying/graph-client/[[...slug]].mdx similarity index 100% rename from website/pages/en/querying/graph-client/[[...slug]].mdx rename to website/pages/en/subgraphs/querying/graph-client/[[...slug]].mdx diff --git a/website/pages/en/querying/graph-client/_meta.js b/website/pages/en/subgraphs/querying/graph-client/_meta.js similarity index 62% rename from website/pages/en/querying/graph-client/_meta.js rename to website/pages/en/subgraphs/querying/graph-client/_meta.js index 9ca9e8379f19..244882f66351 100644 --- a/website/pages/en/querying/graph-client/_meta.js +++ b/website/pages/en/subgraphs/querying/graph-client/_meta.js @@ -1,6 +1,6 @@ import { createCatchAllMeta } from 'nextra/catch-all' -import json from '../../../../remote-files/graph-client.json' assert { type: 'json' } +import json from '../../../../../remote-files/graph-client.json' assert { type: 'json' } export default () => createCatchAllMeta(json.filePaths, { diff --git a/website/pages/en/querying/graphql-api.mdx b/website/pages/en/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/en/querying/graphql-api.mdx rename to website/pages/en/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/en/querying/querying-the-graph.mdx b/website/pages/en/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/en/querying/querying-the-graph.mdx rename to website/pages/en/subgraphs/querying/introduction.mdx diff --git a/website/pages/en/querying/managing-api-keys.mdx b/website/pages/en/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/en/querying/managing-api-keys.mdx rename to website/pages/en/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/en/querying/querying-with-python.mdx b/website/pages/en/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/en/querying/querying-with-python.mdx rename to website/pages/en/subgraphs/querying/python.mdx diff --git a/website/pages/en/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/en/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/en/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/en/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/en/quick-start.mdx b/website/pages/en/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/en/quick-start.mdx rename to website/pages/en/subgraphs/quick-start.mdx diff --git a/website/pages/en/substreams/_meta.js b/website/pages/en/substreams/_meta.js new file mode 100644 index 000000000000..fc586ec6c05b --- /dev/null +++ b/website/pages/en/substreams/_meta.js @@ -0,0 +1,4 @@ +export default { + introduction: 'Introduction', + sps: 'Substreams-Powered Subgraphs', +} diff --git a/website/pages/en/substreams.mdx b/website/pages/en/substreams/introduction.mdx similarity index 100% rename from website/pages/en/substreams.mdx rename to website/pages/en/substreams/introduction.mdx diff --git a/website/pages/en/sps/_meta.js b/website/pages/en/substreams/sps/_meta.js similarity index 100% rename from website/pages/en/sps/_meta.js rename to website/pages/en/substreams/sps/_meta.js diff --git a/website/pages/en/sps/introduction.mdx b/website/pages/en/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/en/sps/introduction.mdx rename to website/pages/en/substreams/sps/introduction.mdx diff --git a/website/pages/en/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/en/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/en/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/en/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/en/sps/triggers-example.mdx b/website/pages/en/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/en/sps/triggers-example.mdx rename to website/pages/en/substreams/sps/triggers-example.mdx diff --git a/website/pages/en/sps/triggers.mdx b/website/pages/en/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/en/sps/triggers.mdx rename to website/pages/en/substreams/sps/triggers.mdx diff --git a/website/pages/es/cookbook/_meta.js b/website/pages/es/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/es/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/_meta.js b/website/pages/es/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/es/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/creating-a-subgraph/_meta.js b/website/pages/es/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/es/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/es/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/deploying/_meta.js b/website/pages/es/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/es/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/managing/_meta.js b/website/pages/es/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/es/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/developing/publishing/_meta.js b/website/pages/es/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/es/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/indexer-tooling/_meta.js b/website/pages/es/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/es/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/indexing/_meta.js b/website/pages/es/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/es/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/chain-integration-overview.mdx b/website/pages/es/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/es/chain-integration-overview.mdx rename to website/pages/es/indexing/chain-integration-overview.mdx diff --git a/website/pages/es/indexing.mdx b/website/pages/es/indexing/introduction.mdx similarity index 100% rename from website/pages/es/indexing.mdx rename to website/pages/es/indexing/introduction.mdx diff --git a/website/pages/es/new-chain-integration.mdx b/website/pages/es/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/es/new-chain-integration.mdx rename to website/pages/es/indexing/new-chain-integration.mdx diff --git a/website/pages/es/supported-network-requirements.mdx b/website/pages/es/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/es/supported-network-requirements.mdx rename to website/pages/es/indexing/supported-network-requirements.mdx diff --git a/website/pages/es/tap.mdx b/website/pages/es/indexing/tap.mdx similarity index 100% rename from website/pages/es/tap.mdx rename to website/pages/es/indexing/tap.mdx diff --git a/website/pages/es/indexing/tooling/_meta.js b/website/pages/es/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/es/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/indexer-tooling/firehose.mdx b/website/pages/es/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/es/indexer-tooling/firehose.mdx rename to website/pages/es/indexing/tooling/firehose.mdx diff --git a/website/pages/es/indexer-tooling/graphcast.mdx b/website/pages/es/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/es/indexer-tooling/graphcast.mdx rename to website/pages/es/indexing/tooling/graphcast.mdx diff --git a/website/pages/es/indexer-tooling/operating-graph-node.mdx b/website/pages/es/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/es/indexer-tooling/operating-graph-node.mdx rename to website/pages/es/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/es/network/_meta.js b/website/pages/es/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/es/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/network/overview.mdx b/website/pages/es/network/overview.mdx deleted file mode 100644 index 79bf2e4c1921..000000000000 --- a/website/pages/es/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Visión general de la red ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Economía de los tokens](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/es/querying/_meta.js b/website/pages/es/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/es/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/querying/graph-client/_meta.js b/website/pages/es/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/es/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/release-notes/_meta.js b/website/pages/es/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/es/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/resources/_meta.js b/website/pages/es/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/es/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/network/benefits.mdx b/website/pages/es/resources/benefits.mdx similarity index 100% rename from website/pages/es/network/benefits.mdx rename to website/pages/es/resources/benefits.mdx diff --git a/website/pages/es/glossary.mdx b/website/pages/es/resources/glossary.mdx similarity index 100% rename from website/pages/es/glossary.mdx rename to website/pages/es/resources/glossary.mdx diff --git a/website/pages/es/resources/release-notes/_meta.js b/website/pages/es/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/es/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/release-notes/assemblyscript-migration-guide.mdx b/website/pages/es/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/es/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/es/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/es/release-notes/graphql-validations-migration-guide.mdx b/website/pages/es/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/es/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/es/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/es/resources/roles/_meta.js b/website/pages/es/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/es/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/network/curating.mdx b/website/pages/es/resources/roles/curating.mdx similarity index 100% rename from website/pages/es/network/curating.mdx rename to website/pages/es/resources/roles/curating.mdx diff --git a/website/pages/es/network/delegating.mdx b/website/pages/es/resources/roles/delegating.mdx similarity index 100% rename from website/pages/es/network/delegating.mdx rename to website/pages/es/resources/roles/delegating.mdx diff --git a/website/pages/es/network/tokenomics.mdx b/website/pages/es/resources/tokenomics.mdx similarity index 100% rename from website/pages/es/network/tokenomics.mdx rename to website/pages/es/resources/tokenomics.mdx diff --git a/website/pages/es/sps/_meta.js b/website/pages/es/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/es/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/es/subgraphs/_meta.js b/website/pages/es/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/es/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/billing.mdx b/website/pages/es/subgraphs/billing.mdx similarity index 100% rename from website/pages/es/billing.mdx rename to website/pages/es/subgraphs/billing.mdx diff --git a/website/pages/es/subgraphs/cookbook/_meta.js b/website/pages/es/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/es/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/cookbook/arweave.mdx b/website/pages/es/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/es/cookbook/arweave.mdx rename to website/pages/es/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/es/cookbook/avoid-eth-calls.mdx b/website/pages/es/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/es/cookbook/avoid-eth-calls.mdx rename to website/pages/es/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/es/cookbook/cosmos.mdx b/website/pages/es/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/es/cookbook/cosmos.mdx rename to website/pages/es/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/es/cookbook/derivedfrom.mdx b/website/pages/es/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/es/cookbook/derivedfrom.mdx rename to website/pages/es/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/es/cookbook/enums.mdx b/website/pages/es/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/es/cookbook/enums.mdx rename to website/pages/es/subgraphs/cookbook/enums.mdx diff --git a/website/pages/es/cookbook/grafting-hotfix.mdx b/website/pages/es/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/es/cookbook/grafting-hotfix.mdx rename to website/pages/es/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/es/cookbook/grafting.mdx b/website/pages/es/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/es/cookbook/grafting.mdx rename to website/pages/es/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/es/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/es/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/es/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/es/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/es/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/es/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/es/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/es/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/es/cookbook/near.mdx b/website/pages/es/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/es/cookbook/near.mdx rename to website/pages/es/subgraphs/cookbook/near.mdx diff --git a/website/pages/es/cookbook/pruning.mdx b/website/pages/es/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/es/cookbook/pruning.mdx rename to website/pages/es/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/es/cookbook/subgraph-debug-forking.mdx b/website/pages/es/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/es/cookbook/subgraph-debug-forking.mdx rename to website/pages/es/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/es/cookbook/subgraph-uncrashable.mdx b/website/pages/es/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/es/cookbook/subgraph-uncrashable.mdx rename to website/pages/es/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/es/cookbook/substreams-powered-subgraphs.mdx b/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/es/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/es/cookbook/timeseries.mdx b/website/pages/es/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/es/cookbook/timeseries.mdx rename to website/pages/es/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/es/cookbook/transfer-to-the-graph.mdx b/website/pages/es/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/es/cookbook/transfer-to-the-graph.mdx rename to website/pages/es/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/es/subgraphs/developing/_meta.js b/website/pages/es/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/es/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/subgraphs/developing/creating/_meta.js b/website/pages/es/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/es/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/developing/creating-a-subgraph/advanced.mdx b/website/pages/es/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/advanced.mdx rename to website/pages/es/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/es/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/es/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/es/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/es/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/es/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/es/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/es/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/es/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/es/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/es/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/es/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/es/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/es/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/es/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/es/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/es/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/es/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/es/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/es/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/es/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/es/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/es/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/es/subgraphs/developing/deploying/_meta.js b/website/pages/es/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/es/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/developing/deploying/multiple-networks.mdx b/website/pages/es/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/es/developing/deploying/multiple-networks.mdx rename to website/pages/es/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/es/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/es/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/es/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/es/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/es/developing/deploying/using-subgraph-studio.mdx b/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/es/developing/deploying/using-subgraph-studio.mdx rename to website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/es/developing/developer-faqs.mdx b/website/pages/es/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/es/developing/developer-faqs.mdx rename to website/pages/es/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/es/developing/developing.mdx b/website/pages/es/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/es/developing/developing.mdx rename to website/pages/es/subgraphs/developing/introduction.mdx diff --git a/website/pages/es/subgraphs/developing/managing/_meta.js b/website/pages/es/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/es/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/developing/managing/delete-a-subgraph.mdx b/website/pages/es/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/es/developing/managing/delete-a-subgraph.mdx rename to website/pages/es/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/es/developing/managing/transfer-a-subgraph.mdx b/website/pages/es/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/es/developing/managing/transfer-a-subgraph.mdx rename to website/pages/es/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/es/subgraphs/developing/publishing/_meta.js b/website/pages/es/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/es/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/developing/publishing/publishing-a-subgraph.mdx b/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/es/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/es/developing/subgraphs.mdx b/website/pages/es/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/es/developing/subgraphs.mdx rename to website/pages/es/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/es/explorer.mdx b/website/pages/es/subgraphs/explorer.mdx similarity index 100% rename from website/pages/es/explorer.mdx rename to website/pages/es/subgraphs/explorer.mdx diff --git a/website/pages/es/subgraphs/querying/_meta.js b/website/pages/es/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/es/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/querying/querying-best-practices.mdx b/website/pages/es/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/es/querying/querying-best-practices.mdx rename to website/pages/es/subgraphs/querying/best-practices.mdx diff --git a/website/pages/es/querying/distributed-systems.mdx b/website/pages/es/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/es/querying/distributed-systems.mdx rename to website/pages/es/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/es/querying/querying-from-an-application.mdx b/website/pages/es/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/es/querying/querying-from-an-application.mdx rename to website/pages/es/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/es/subgraphs/querying/graph-client/_meta.js b/website/pages/es/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/es/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/querying/graphql-api.mdx b/website/pages/es/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/es/querying/graphql-api.mdx rename to website/pages/es/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/es/querying/querying-the-graph.mdx b/website/pages/es/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/es/querying/querying-the-graph.mdx rename to website/pages/es/subgraphs/querying/introduction.mdx diff --git a/website/pages/es/querying/managing-api-keys.mdx b/website/pages/es/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/es/querying/managing-api-keys.mdx rename to website/pages/es/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/es/querying/querying-with-python.mdx b/website/pages/es/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/es/querying/querying-with-python.mdx rename to website/pages/es/subgraphs/querying/python.mdx diff --git a/website/pages/es/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/es/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/es/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/es/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/es/quick-start.mdx b/website/pages/es/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/es/quick-start.mdx rename to website/pages/es/subgraphs/quick-start.mdx diff --git a/website/pages/es/substreams/_meta.js b/website/pages/es/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/es/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/substreams.mdx b/website/pages/es/substreams/introduction.mdx similarity index 100% rename from website/pages/es/substreams.mdx rename to website/pages/es/substreams/introduction.mdx diff --git a/website/pages/es/substreams/sps/_meta.js b/website/pages/es/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/es/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/es/sps/introduction.mdx b/website/pages/es/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/es/sps/introduction.mdx rename to website/pages/es/substreams/sps/introduction.mdx diff --git a/website/pages/es/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/es/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/es/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/es/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/es/sps/triggers-example.mdx b/website/pages/es/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/es/sps/triggers-example.mdx rename to website/pages/es/substreams/sps/triggers-example.mdx diff --git a/website/pages/es/sps/triggers.mdx b/website/pages/es/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/es/sps/triggers.mdx rename to website/pages/es/substreams/sps/triggers.mdx diff --git a/website/pages/fr/cookbook/_meta.js b/website/pages/fr/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/fr/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/_meta.js b/website/pages/fr/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/fr/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/creating-a-subgraph/_meta.js b/website/pages/fr/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/fr/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/fr/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/deploying/_meta.js b/website/pages/fr/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/fr/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/managing/_meta.js b/website/pages/fr/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/fr/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/developing/publishing/_meta.js b/website/pages/fr/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/fr/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/indexer-tooling/_meta.js b/website/pages/fr/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/fr/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/indexing/_meta.js b/website/pages/fr/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/fr/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/chain-integration-overview.mdx b/website/pages/fr/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/fr/chain-integration-overview.mdx rename to website/pages/fr/indexing/chain-integration-overview.mdx diff --git a/website/pages/fr/indexing.mdx b/website/pages/fr/indexing/introduction.mdx similarity index 100% rename from website/pages/fr/indexing.mdx rename to website/pages/fr/indexing/introduction.mdx diff --git a/website/pages/fr/new-chain-integration.mdx b/website/pages/fr/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/fr/new-chain-integration.mdx rename to website/pages/fr/indexing/new-chain-integration.mdx diff --git a/website/pages/fr/supported-network-requirements.mdx b/website/pages/fr/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/fr/supported-network-requirements.mdx rename to website/pages/fr/indexing/supported-network-requirements.mdx diff --git a/website/pages/fr/tap.mdx b/website/pages/fr/indexing/tap.mdx similarity index 100% rename from website/pages/fr/tap.mdx rename to website/pages/fr/indexing/tap.mdx diff --git a/website/pages/fr/indexing/tooling/_meta.js b/website/pages/fr/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/fr/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/indexer-tooling/firehose.mdx b/website/pages/fr/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/fr/indexer-tooling/firehose.mdx rename to website/pages/fr/indexing/tooling/firehose.mdx diff --git a/website/pages/fr/indexer-tooling/graphcast.mdx b/website/pages/fr/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/fr/indexer-tooling/graphcast.mdx rename to website/pages/fr/indexing/tooling/graphcast.mdx diff --git a/website/pages/fr/indexer-tooling/operating-graph-node.mdx b/website/pages/fr/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/fr/indexer-tooling/operating-graph-node.mdx rename to website/pages/fr/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/fr/network/_meta.js b/website/pages/fr/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/fr/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/network/overview.mdx b/website/pages/fr/network/overview.mdx deleted file mode 100644 index 44bb43d7f444..000000000000 --- a/website/pages/fr/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Présentation du réseau ---- - -The Graph Network est un protocole d'indexation décentralisé pour organiser les données de la blockchain. - -## Comment ça marche ? - -Les applications utilisent [GraphQL](/querying/graphql-api/) pour interroger des API ouvertes appelées subgraphs et récupérer les données indexées sur le réseau. Avec The Graph, les développeurs peuvent créer des applications sans serveur qui fonctionnent entièrement sur une infrastructure publique. - -## Spécificités⁠ - -The Graph Network est composé d'Indexeurs, de Curateurs et de Délégateurs qui fournissent des services au réseau et servent des données aux applications web3. - -![Économie des jetons](/img/Network-roles@2x.png) - -### Économie - -Pour garantir la sécurité économique de The Graph Network et l'intégrité des données interrogées, les participants stakent et utilisent des Graph Tokens ([GRT](/tokenomics)). Le GRT est un jeton utilitaire de travail qui est un ERC-20, utilisé pour allouer des ressources dans le réseau. - -Les Indexeurs, Curateurs et Déléguateurs actifs peuvent fournir des services et tirer des revenus du réseau. Le revenu qu'ils perçoivent est proportionnel à la quantité de travail qu'ils effectuent et à leur GRT stakés. diff --git a/website/pages/fr/querying/_meta.js b/website/pages/fr/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/fr/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/querying/graph-client/_meta.js b/website/pages/fr/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/fr/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/release-notes/_meta.js b/website/pages/fr/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/fr/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/resources/_meta.js b/website/pages/fr/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/fr/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/network/benefits.mdx b/website/pages/fr/resources/benefits.mdx similarity index 100% rename from website/pages/fr/network/benefits.mdx rename to website/pages/fr/resources/benefits.mdx diff --git a/website/pages/fr/glossary.mdx b/website/pages/fr/resources/glossary.mdx similarity index 100% rename from website/pages/fr/glossary.mdx rename to website/pages/fr/resources/glossary.mdx diff --git a/website/pages/fr/resources/release-notes/_meta.js b/website/pages/fr/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/fr/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/fr/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/fr/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/fr/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx b/website/pages/fr/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/fr/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/fr/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/fr/resources/roles/_meta.js b/website/pages/fr/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/fr/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/network/curating.mdx b/website/pages/fr/resources/roles/curating.mdx similarity index 100% rename from website/pages/fr/network/curating.mdx rename to website/pages/fr/resources/roles/curating.mdx diff --git a/website/pages/fr/network/delegating.mdx b/website/pages/fr/resources/roles/delegating.mdx similarity index 100% rename from website/pages/fr/network/delegating.mdx rename to website/pages/fr/resources/roles/delegating.mdx diff --git a/website/pages/fr/network/tokenomics.mdx b/website/pages/fr/resources/tokenomics.mdx similarity index 100% rename from website/pages/fr/network/tokenomics.mdx rename to website/pages/fr/resources/tokenomics.mdx diff --git a/website/pages/fr/sps/_meta.js b/website/pages/fr/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/fr/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/fr/subgraphs/_meta.js b/website/pages/fr/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/fr/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/billing.mdx b/website/pages/fr/subgraphs/billing.mdx similarity index 100% rename from website/pages/fr/billing.mdx rename to website/pages/fr/subgraphs/billing.mdx diff --git a/website/pages/fr/subgraphs/cookbook/_meta.js b/website/pages/fr/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/fr/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/cookbook/arweave.mdx b/website/pages/fr/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/fr/cookbook/arweave.mdx rename to website/pages/fr/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/fr/cookbook/avoid-eth-calls.mdx b/website/pages/fr/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/fr/cookbook/avoid-eth-calls.mdx rename to website/pages/fr/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/fr/cookbook/cosmos.mdx b/website/pages/fr/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/fr/cookbook/cosmos.mdx rename to website/pages/fr/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/fr/cookbook/derivedfrom.mdx b/website/pages/fr/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/fr/cookbook/derivedfrom.mdx rename to website/pages/fr/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/fr/cookbook/enums.mdx b/website/pages/fr/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/fr/cookbook/enums.mdx rename to website/pages/fr/subgraphs/cookbook/enums.mdx diff --git a/website/pages/fr/cookbook/grafting-hotfix.mdx b/website/pages/fr/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/fr/cookbook/grafting-hotfix.mdx rename to website/pages/fr/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/fr/cookbook/grafting.mdx b/website/pages/fr/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/fr/cookbook/grafting.mdx rename to website/pages/fr/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/fr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/fr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/fr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/fr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/fr/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/fr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/fr/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/fr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/fr/cookbook/near.mdx b/website/pages/fr/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/fr/cookbook/near.mdx rename to website/pages/fr/subgraphs/cookbook/near.mdx diff --git a/website/pages/fr/cookbook/pruning.mdx b/website/pages/fr/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/fr/cookbook/pruning.mdx rename to website/pages/fr/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/fr/cookbook/subgraph-debug-forking.mdx b/website/pages/fr/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/fr/cookbook/subgraph-debug-forking.mdx rename to website/pages/fr/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/fr/cookbook/subgraph-uncrashable.mdx b/website/pages/fr/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/fr/cookbook/subgraph-uncrashable.mdx rename to website/pages/fr/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/fr/cookbook/substreams-powered-subgraphs.mdx b/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/fr/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/fr/cookbook/timeseries.mdx b/website/pages/fr/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/fr/cookbook/timeseries.mdx rename to website/pages/fr/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/fr/cookbook/transfer-to-the-graph.mdx b/website/pages/fr/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/fr/cookbook/transfer-to-the-graph.mdx rename to website/pages/fr/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/fr/subgraphs/developing/_meta.js b/website/pages/fr/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/fr/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/subgraphs/developing/creating/_meta.js b/website/pages/fr/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/fr/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/developing/creating-a-subgraph/advanced.mdx b/website/pages/fr/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/advanced.mdx rename to website/pages/fr/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/fr/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/fr/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/fr/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/fr/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/fr/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/fr/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/fr/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/fr/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/fr/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/fr/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/fr/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/fr/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/fr/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/fr/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/fr/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/fr/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/fr/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/fr/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/fr/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/fr/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/fr/subgraphs/developing/deploying/_meta.js b/website/pages/fr/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/fr/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/developing/deploying/multiple-networks.mdx b/website/pages/fr/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/fr/developing/deploying/multiple-networks.mdx rename to website/pages/fr/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/fr/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/fr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/fr/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/fr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/fr/developing/deploying/using-subgraph-studio.mdx b/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/fr/developing/deploying/using-subgraph-studio.mdx rename to website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/fr/developing/developer-faqs.mdx b/website/pages/fr/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/fr/developing/developer-faqs.mdx rename to website/pages/fr/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/fr/developing/developing.mdx b/website/pages/fr/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/fr/developing/developing.mdx rename to website/pages/fr/subgraphs/developing/introduction.mdx diff --git a/website/pages/fr/subgraphs/developing/managing/_meta.js b/website/pages/fr/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/fr/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/developing/managing/delete-a-subgraph.mdx b/website/pages/fr/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/fr/developing/managing/delete-a-subgraph.mdx rename to website/pages/fr/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/fr/developing/managing/transfer-a-subgraph.mdx b/website/pages/fr/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/fr/developing/managing/transfer-a-subgraph.mdx rename to website/pages/fr/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/fr/subgraphs/developing/publishing/_meta.js b/website/pages/fr/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/fr/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/developing/publishing/publishing-a-subgraph.mdx b/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/fr/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/fr/developing/subgraphs.mdx b/website/pages/fr/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/fr/developing/subgraphs.mdx rename to website/pages/fr/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/fr/explorer.mdx b/website/pages/fr/subgraphs/explorer.mdx similarity index 100% rename from website/pages/fr/explorer.mdx rename to website/pages/fr/subgraphs/explorer.mdx diff --git a/website/pages/fr/subgraphs/querying/_meta.js b/website/pages/fr/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/fr/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/querying/querying-best-practices.mdx b/website/pages/fr/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/fr/querying/querying-best-practices.mdx rename to website/pages/fr/subgraphs/querying/best-practices.mdx diff --git a/website/pages/fr/querying/distributed-systems.mdx b/website/pages/fr/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/fr/querying/distributed-systems.mdx rename to website/pages/fr/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/fr/querying/querying-from-an-application.mdx b/website/pages/fr/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/fr/querying/querying-from-an-application.mdx rename to website/pages/fr/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/fr/subgraphs/querying/graph-client/_meta.js b/website/pages/fr/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/fr/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/querying/graphql-api.mdx b/website/pages/fr/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/fr/querying/graphql-api.mdx rename to website/pages/fr/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/fr/querying/querying-the-graph.mdx b/website/pages/fr/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/fr/querying/querying-the-graph.mdx rename to website/pages/fr/subgraphs/querying/introduction.mdx diff --git a/website/pages/fr/querying/managing-api-keys.mdx b/website/pages/fr/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/fr/querying/managing-api-keys.mdx rename to website/pages/fr/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/fr/querying/querying-with-python.mdx b/website/pages/fr/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/fr/querying/querying-with-python.mdx rename to website/pages/fr/subgraphs/querying/python.mdx diff --git a/website/pages/fr/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/fr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/fr/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/fr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/fr/quick-start.mdx b/website/pages/fr/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/fr/quick-start.mdx rename to website/pages/fr/subgraphs/quick-start.mdx diff --git a/website/pages/fr/substreams/_meta.js b/website/pages/fr/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/fr/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/substreams.mdx b/website/pages/fr/substreams/introduction.mdx similarity index 100% rename from website/pages/fr/substreams.mdx rename to website/pages/fr/substreams/introduction.mdx diff --git a/website/pages/fr/substreams/sps/_meta.js b/website/pages/fr/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/fr/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/fr/sps/introduction.mdx b/website/pages/fr/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/fr/sps/introduction.mdx rename to website/pages/fr/substreams/sps/introduction.mdx diff --git a/website/pages/fr/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/fr/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/fr/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/fr/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/fr/sps/triggers-example.mdx b/website/pages/fr/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/fr/sps/triggers-example.mdx rename to website/pages/fr/substreams/sps/triggers-example.mdx diff --git a/website/pages/fr/sps/triggers.mdx b/website/pages/fr/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/fr/sps/triggers.mdx rename to website/pages/fr/substreams/sps/triggers.mdx diff --git a/website/pages/hi/cookbook/_meta.js b/website/pages/hi/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/hi/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/_meta.js b/website/pages/hi/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/hi/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/creating-a-subgraph/_meta.js b/website/pages/hi/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/hi/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/hi/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/deploying/_meta.js b/website/pages/hi/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/hi/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/managing/_meta.js b/website/pages/hi/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/hi/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/developing/publishing/_meta.js b/website/pages/hi/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/hi/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/indexer-tooling/_meta.js b/website/pages/hi/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/hi/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/indexing/_meta.js b/website/pages/hi/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/hi/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/chain-integration-overview.mdx b/website/pages/hi/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/hi/chain-integration-overview.mdx rename to website/pages/hi/indexing/chain-integration-overview.mdx diff --git a/website/pages/hi/indexing.mdx b/website/pages/hi/indexing/introduction.mdx similarity index 100% rename from website/pages/hi/indexing.mdx rename to website/pages/hi/indexing/introduction.mdx diff --git a/website/pages/hi/new-chain-integration.mdx b/website/pages/hi/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/hi/new-chain-integration.mdx rename to website/pages/hi/indexing/new-chain-integration.mdx diff --git a/website/pages/hi/supported-network-requirements.mdx b/website/pages/hi/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/hi/supported-network-requirements.mdx rename to website/pages/hi/indexing/supported-network-requirements.mdx diff --git a/website/pages/hi/tap.mdx b/website/pages/hi/indexing/tap.mdx similarity index 100% rename from website/pages/hi/tap.mdx rename to website/pages/hi/indexing/tap.mdx diff --git a/website/pages/hi/indexing/tooling/_meta.js b/website/pages/hi/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/hi/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/indexer-tooling/firehose.mdx b/website/pages/hi/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/hi/indexer-tooling/firehose.mdx rename to website/pages/hi/indexing/tooling/firehose.mdx diff --git a/website/pages/hi/indexer-tooling/graphcast.mdx b/website/pages/hi/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/hi/indexer-tooling/graphcast.mdx rename to website/pages/hi/indexing/tooling/graphcast.mdx diff --git a/website/pages/hi/indexer-tooling/operating-graph-node.mdx b/website/pages/hi/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/hi/indexer-tooling/operating-graph-node.mdx rename to website/pages/hi/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/hi/network/_meta.js b/website/pages/hi/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/hi/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/network/overview.mdx b/website/pages/hi/network/overview.mdx deleted file mode 100644 index a6e15286eced..000000000000 --- a/website/pages/hi/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: नेटवर्क अवलोकन ---- - -The Graph Network एक विकेन्द्रीकृत अनुक्रमण प्रोटोकॉल है जो ब्लॉकचेन डेटा को व्यवस्थित करने के लिए है। - -## यह कैसे काम करता है? - -ऐप्लिकेशन [GraphQL](/querying/graphql-api/) का उपयोग करके सबग्राफ़ कहलाने वाले ओपन एपीआई को क्वेरी करते हैं और नेटवर्क पर अनुक्रमित डेटा को पुनः प्राप्त करते हैं। The Graph के साथ, डेवलपर्स बिना सर्वर वाले एप्लिकेशन बना सकते हैं जो पूरी तरह से सार्वजनिक बुनियादी ढांचे पर चलते हैं। - -## विशिष्टताएँ - -The Graph Network में Indexers, Curators और Delegators शामिल हैं जो नेटवर्क को सेवाएँ प्रदान करते हैं और वेब3 अनुप्रयोगों को डेटा सेवा करते हैं। - -![टोकन अर्थशास्त्र](/img/Network-roles@2x.png) - -### अर्थशास्त्र - -The Graph Network की आर्थिक सुरक्षा सुनिश्चित करने और डेटा की सत्यता को बनाए रखने के लिए, प्रतिभागी Graph Tokens ([GRT](/tokenomics)) का स्टेक करते हैं और उनका उपयोग करते हैं। GRT एक कार्य उपयोगिता टोकन है जो ERC-20 है, जिसका उपयोग नेटवर्क में संसाधनों को आवंटित करने के लिए किया जाता है। - -सक्रिय Indexers, Curators, और Delegators सेवाएँ प्रदान कर सकते हैं और नेटवर्क से आय अर्जित कर सकते हैं। वे जो आय अर्जित करते हैं, वह उनके द्वारा किए गए कार्य की मात्रा और उनके GRT हिस्सेदारी के अनुपात में होती है। diff --git a/website/pages/hi/querying/_meta.js b/website/pages/hi/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/hi/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/querying/graph-client/_meta.js b/website/pages/hi/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/hi/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/release-notes/_meta.js b/website/pages/hi/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/hi/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/resources/_meta.js b/website/pages/hi/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/hi/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/network/benefits.mdx b/website/pages/hi/resources/benefits.mdx similarity index 100% rename from website/pages/hi/network/benefits.mdx rename to website/pages/hi/resources/benefits.mdx diff --git a/website/pages/hi/glossary.mdx b/website/pages/hi/resources/glossary.mdx similarity index 100% rename from website/pages/hi/glossary.mdx rename to website/pages/hi/resources/glossary.mdx diff --git a/website/pages/hi/resources/release-notes/_meta.js b/website/pages/hi/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/hi/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx b/website/pages/hi/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/hi/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/hi/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/hi/release-notes/graphql-validations-migration-guide.mdx b/website/pages/hi/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/hi/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/hi/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/hi/resources/roles/_meta.js b/website/pages/hi/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/hi/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/network/curating.mdx b/website/pages/hi/resources/roles/curating.mdx similarity index 100% rename from website/pages/hi/network/curating.mdx rename to website/pages/hi/resources/roles/curating.mdx diff --git a/website/pages/hi/network/delegating.mdx b/website/pages/hi/resources/roles/delegating.mdx similarity index 100% rename from website/pages/hi/network/delegating.mdx rename to website/pages/hi/resources/roles/delegating.mdx diff --git a/website/pages/hi/network/tokenomics.mdx b/website/pages/hi/resources/tokenomics.mdx similarity index 100% rename from website/pages/hi/network/tokenomics.mdx rename to website/pages/hi/resources/tokenomics.mdx diff --git a/website/pages/hi/sps/_meta.js b/website/pages/hi/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/hi/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/hi/subgraphs/_meta.js b/website/pages/hi/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/hi/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/billing.mdx b/website/pages/hi/subgraphs/billing.mdx similarity index 100% rename from website/pages/hi/billing.mdx rename to website/pages/hi/subgraphs/billing.mdx diff --git a/website/pages/hi/subgraphs/cookbook/_meta.js b/website/pages/hi/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/hi/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/cookbook/arweave.mdx b/website/pages/hi/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/hi/cookbook/arweave.mdx rename to website/pages/hi/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/hi/cookbook/avoid-eth-calls.mdx b/website/pages/hi/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/hi/cookbook/avoid-eth-calls.mdx rename to website/pages/hi/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/hi/cookbook/cosmos.mdx b/website/pages/hi/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/hi/cookbook/cosmos.mdx rename to website/pages/hi/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/hi/cookbook/derivedfrom.mdx b/website/pages/hi/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/hi/cookbook/derivedfrom.mdx rename to website/pages/hi/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/hi/cookbook/enums.mdx b/website/pages/hi/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/hi/cookbook/enums.mdx rename to website/pages/hi/subgraphs/cookbook/enums.mdx diff --git a/website/pages/hi/cookbook/grafting-hotfix.mdx b/website/pages/hi/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/hi/cookbook/grafting-hotfix.mdx rename to website/pages/hi/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/hi/cookbook/grafting.mdx b/website/pages/hi/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/hi/cookbook/grafting.mdx rename to website/pages/hi/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/hi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/hi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/hi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/hi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/hi/cookbook/near.mdx b/website/pages/hi/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/hi/cookbook/near.mdx rename to website/pages/hi/subgraphs/cookbook/near.mdx diff --git a/website/pages/hi/cookbook/pruning.mdx b/website/pages/hi/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/hi/cookbook/pruning.mdx rename to website/pages/hi/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/hi/cookbook/subgraph-debug-forking.mdx b/website/pages/hi/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/hi/cookbook/subgraph-debug-forking.mdx rename to website/pages/hi/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/hi/cookbook/subgraph-uncrashable.mdx b/website/pages/hi/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/hi/cookbook/subgraph-uncrashable.mdx rename to website/pages/hi/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/hi/cookbook/substreams-powered-subgraphs.mdx b/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/hi/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/hi/cookbook/timeseries.mdx b/website/pages/hi/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/hi/cookbook/timeseries.mdx rename to website/pages/hi/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/hi/cookbook/transfer-to-the-graph.mdx b/website/pages/hi/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/hi/cookbook/transfer-to-the-graph.mdx rename to website/pages/hi/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/hi/subgraphs/developing/_meta.js b/website/pages/hi/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/hi/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/subgraphs/developing/creating/_meta.js b/website/pages/hi/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/hi/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/developing/creating-a-subgraph/advanced.mdx b/website/pages/hi/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/advanced.mdx rename to website/pages/hi/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/hi/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/hi/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/hi/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/hi/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/hi/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/hi/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/hi/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/hi/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/hi/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/hi/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/hi/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/hi/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/hi/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/hi/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/hi/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/hi/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/hi/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/hi/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/hi/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/hi/subgraphs/developing/deploying/_meta.js b/website/pages/hi/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/hi/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/developing/deploying/multiple-networks.mdx b/website/pages/hi/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/hi/developing/deploying/multiple-networks.mdx rename to website/pages/hi/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/hi/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/hi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/hi/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/hi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/hi/developing/deploying/using-subgraph-studio.mdx b/website/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/hi/developing/deploying/using-subgraph-studio.mdx rename to website/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/hi/developing/developer-faqs.mdx b/website/pages/hi/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/hi/developing/developer-faqs.mdx rename to website/pages/hi/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/hi/developing/developing.mdx b/website/pages/hi/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/hi/developing/developing.mdx rename to website/pages/hi/subgraphs/developing/introduction.mdx diff --git a/website/pages/hi/subgraphs/developing/managing/_meta.js b/website/pages/hi/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/hi/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/developing/managing/delete-a-subgraph.mdx b/website/pages/hi/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/hi/developing/managing/delete-a-subgraph.mdx rename to website/pages/hi/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/hi/developing/managing/transfer-a-subgraph.mdx b/website/pages/hi/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/hi/developing/managing/transfer-a-subgraph.mdx rename to website/pages/hi/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/hi/subgraphs/developing/publishing/_meta.js b/website/pages/hi/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/hi/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/developing/publishing/publishing-a-subgraph.mdx b/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/hi/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/hi/developing/subgraphs.mdx b/website/pages/hi/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/hi/developing/subgraphs.mdx rename to website/pages/hi/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/hi/explorer.mdx b/website/pages/hi/subgraphs/explorer.mdx similarity index 100% rename from website/pages/hi/explorer.mdx rename to website/pages/hi/subgraphs/explorer.mdx diff --git a/website/pages/hi/subgraphs/querying/_meta.js b/website/pages/hi/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/hi/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/querying/querying-best-practices.mdx b/website/pages/hi/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/hi/querying/querying-best-practices.mdx rename to website/pages/hi/subgraphs/querying/best-practices.mdx diff --git a/website/pages/hi/querying/distributed-systems.mdx b/website/pages/hi/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/hi/querying/distributed-systems.mdx rename to website/pages/hi/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/hi/querying/querying-from-an-application.mdx b/website/pages/hi/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/hi/querying/querying-from-an-application.mdx rename to website/pages/hi/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/hi/subgraphs/querying/graph-client/_meta.js b/website/pages/hi/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/hi/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/querying/graphql-api.mdx b/website/pages/hi/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/hi/querying/graphql-api.mdx rename to website/pages/hi/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/hi/querying/querying-the-graph.mdx b/website/pages/hi/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/hi/querying/querying-the-graph.mdx rename to website/pages/hi/subgraphs/querying/introduction.mdx diff --git a/website/pages/hi/querying/managing-api-keys.mdx b/website/pages/hi/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/hi/querying/managing-api-keys.mdx rename to website/pages/hi/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/hi/querying/querying-with-python.mdx b/website/pages/hi/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/hi/querying/querying-with-python.mdx rename to website/pages/hi/subgraphs/querying/python.mdx diff --git a/website/pages/hi/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/hi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/hi/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/hi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/hi/quick-start.mdx b/website/pages/hi/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/hi/quick-start.mdx rename to website/pages/hi/subgraphs/quick-start.mdx diff --git a/website/pages/hi/substreams/_meta.js b/website/pages/hi/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/hi/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/substreams.mdx b/website/pages/hi/substreams/introduction.mdx similarity index 100% rename from website/pages/hi/substreams.mdx rename to website/pages/hi/substreams/introduction.mdx diff --git a/website/pages/hi/substreams/sps/_meta.js b/website/pages/hi/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/hi/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/hi/sps/introduction.mdx b/website/pages/hi/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/hi/sps/introduction.mdx rename to website/pages/hi/substreams/sps/introduction.mdx diff --git a/website/pages/hi/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/hi/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/hi/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/hi/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/hi/sps/triggers-example.mdx b/website/pages/hi/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/hi/sps/triggers-example.mdx rename to website/pages/hi/substreams/sps/triggers-example.mdx diff --git a/website/pages/hi/sps/triggers.mdx b/website/pages/hi/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/hi/sps/triggers.mdx rename to website/pages/hi/substreams/sps/triggers.mdx diff --git a/website/pages/it/cookbook/_meta.js b/website/pages/it/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/it/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/_meta.js b/website/pages/it/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/it/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/creating-a-subgraph/_meta.js b/website/pages/it/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/it/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/it/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/deploying/_meta.js b/website/pages/it/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/it/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/managing/_meta.js b/website/pages/it/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/it/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/developing/publishing/_meta.js b/website/pages/it/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/it/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/indexer-tooling/_meta.js b/website/pages/it/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/it/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/indexing/_meta.js b/website/pages/it/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/it/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/chain-integration-overview.mdx b/website/pages/it/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/it/chain-integration-overview.mdx rename to website/pages/it/indexing/chain-integration-overview.mdx diff --git a/website/pages/it/indexing.mdx b/website/pages/it/indexing/introduction.mdx similarity index 100% rename from website/pages/it/indexing.mdx rename to website/pages/it/indexing/introduction.mdx diff --git a/website/pages/it/new-chain-integration.mdx b/website/pages/it/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/it/new-chain-integration.mdx rename to website/pages/it/indexing/new-chain-integration.mdx diff --git a/website/pages/it/supported-network-requirements.mdx b/website/pages/it/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/it/supported-network-requirements.mdx rename to website/pages/it/indexing/supported-network-requirements.mdx diff --git a/website/pages/it/tap.mdx b/website/pages/it/indexing/tap.mdx similarity index 100% rename from website/pages/it/tap.mdx rename to website/pages/it/indexing/tap.mdx diff --git a/website/pages/it/indexing/tooling/_meta.js b/website/pages/it/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/it/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/indexer-tooling/firehose.mdx b/website/pages/it/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/it/indexer-tooling/firehose.mdx rename to website/pages/it/indexing/tooling/firehose.mdx diff --git a/website/pages/it/indexer-tooling/graphcast.mdx b/website/pages/it/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/it/indexer-tooling/graphcast.mdx rename to website/pages/it/indexing/tooling/graphcast.mdx diff --git a/website/pages/it/indexer-tooling/operating-graph-node.mdx b/website/pages/it/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/it/indexer-tooling/operating-graph-node.mdx rename to website/pages/it/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/it/network/_meta.js b/website/pages/it/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/it/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/network/overview.mdx b/website/pages/it/network/overview.mdx deleted file mode 100644 index 298945cefa41..000000000000 --- a/website/pages/it/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Panoramica della rete ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Economia del token](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/it/querying/_meta.js b/website/pages/it/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/it/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/querying/graph-client/_meta.js b/website/pages/it/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/it/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/release-notes/_meta.js b/website/pages/it/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/it/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/resources/_meta.js b/website/pages/it/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/it/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/network/benefits.mdx b/website/pages/it/resources/benefits.mdx similarity index 100% rename from website/pages/it/network/benefits.mdx rename to website/pages/it/resources/benefits.mdx diff --git a/website/pages/it/glossary.mdx b/website/pages/it/resources/glossary.mdx similarity index 100% rename from website/pages/it/glossary.mdx rename to website/pages/it/resources/glossary.mdx diff --git a/website/pages/it/resources/release-notes/_meta.js b/website/pages/it/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/it/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/release-notes/assemblyscript-migration-guide.mdx b/website/pages/it/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/it/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/it/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/it/release-notes/graphql-validations-migration-guide.mdx b/website/pages/it/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/it/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/it/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/it/resources/roles/_meta.js b/website/pages/it/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/it/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/network/curating.mdx b/website/pages/it/resources/roles/curating.mdx similarity index 100% rename from website/pages/it/network/curating.mdx rename to website/pages/it/resources/roles/curating.mdx diff --git a/website/pages/it/network/delegating.mdx b/website/pages/it/resources/roles/delegating.mdx similarity index 100% rename from website/pages/it/network/delegating.mdx rename to website/pages/it/resources/roles/delegating.mdx diff --git a/website/pages/it/network/tokenomics.mdx b/website/pages/it/resources/tokenomics.mdx similarity index 100% rename from website/pages/it/network/tokenomics.mdx rename to website/pages/it/resources/tokenomics.mdx diff --git a/website/pages/it/sps/_meta.js b/website/pages/it/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/it/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/it/subgraphs/_meta.js b/website/pages/it/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/it/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/billing.mdx b/website/pages/it/subgraphs/billing.mdx similarity index 100% rename from website/pages/it/billing.mdx rename to website/pages/it/subgraphs/billing.mdx diff --git a/website/pages/it/subgraphs/cookbook/_meta.js b/website/pages/it/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/it/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/cookbook/arweave.mdx b/website/pages/it/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/it/cookbook/arweave.mdx rename to website/pages/it/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/it/cookbook/avoid-eth-calls.mdx b/website/pages/it/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/it/cookbook/avoid-eth-calls.mdx rename to website/pages/it/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/it/cookbook/cosmos.mdx b/website/pages/it/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/it/cookbook/cosmos.mdx rename to website/pages/it/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/it/cookbook/derivedfrom.mdx b/website/pages/it/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/it/cookbook/derivedfrom.mdx rename to website/pages/it/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/it/cookbook/enums.mdx b/website/pages/it/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/it/cookbook/enums.mdx rename to website/pages/it/subgraphs/cookbook/enums.mdx diff --git a/website/pages/it/cookbook/grafting-hotfix.mdx b/website/pages/it/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/it/cookbook/grafting-hotfix.mdx rename to website/pages/it/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/it/cookbook/grafting.mdx b/website/pages/it/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/it/cookbook/grafting.mdx rename to website/pages/it/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/it/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/it/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/it/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/it/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/it/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/it/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/it/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/it/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/it/cookbook/near.mdx b/website/pages/it/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/it/cookbook/near.mdx rename to website/pages/it/subgraphs/cookbook/near.mdx diff --git a/website/pages/it/cookbook/pruning.mdx b/website/pages/it/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/it/cookbook/pruning.mdx rename to website/pages/it/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/it/cookbook/subgraph-debug-forking.mdx b/website/pages/it/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/it/cookbook/subgraph-debug-forking.mdx rename to website/pages/it/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/it/cookbook/subgraph-uncrashable.mdx b/website/pages/it/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/it/cookbook/subgraph-uncrashable.mdx rename to website/pages/it/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/it/cookbook/substreams-powered-subgraphs.mdx b/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/it/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/it/cookbook/timeseries.mdx b/website/pages/it/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/it/cookbook/timeseries.mdx rename to website/pages/it/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/it/cookbook/transfer-to-the-graph.mdx b/website/pages/it/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/it/cookbook/transfer-to-the-graph.mdx rename to website/pages/it/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/it/subgraphs/developing/_meta.js b/website/pages/it/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/it/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/subgraphs/developing/creating/_meta.js b/website/pages/it/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/it/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/developing/creating-a-subgraph/advanced.mdx b/website/pages/it/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/advanced.mdx rename to website/pages/it/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/it/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/it/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/it/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/it/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/it/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/it/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/it/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/it/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/it/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/it/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/it/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/it/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/it/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/it/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/it/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/it/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/it/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/it/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/it/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/it/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/it/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/it/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/it/subgraphs/developing/deploying/_meta.js b/website/pages/it/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/it/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/developing/deploying/multiple-networks.mdx b/website/pages/it/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/it/developing/deploying/multiple-networks.mdx rename to website/pages/it/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/it/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/it/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/it/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/it/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/it/developing/deploying/using-subgraph-studio.mdx b/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/it/developing/deploying/using-subgraph-studio.mdx rename to website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/it/developing/developer-faqs.mdx b/website/pages/it/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/it/developing/developer-faqs.mdx rename to website/pages/it/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/it/developing/developing.mdx b/website/pages/it/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/it/developing/developing.mdx rename to website/pages/it/subgraphs/developing/introduction.mdx diff --git a/website/pages/it/subgraphs/developing/managing/_meta.js b/website/pages/it/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/it/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/developing/managing/delete-a-subgraph.mdx b/website/pages/it/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/it/developing/managing/delete-a-subgraph.mdx rename to website/pages/it/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/it/developing/managing/transfer-a-subgraph.mdx b/website/pages/it/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/it/developing/managing/transfer-a-subgraph.mdx rename to website/pages/it/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/it/subgraphs/developing/publishing/_meta.js b/website/pages/it/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/it/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/developing/publishing/publishing-a-subgraph.mdx b/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/it/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/it/developing/subgraphs.mdx b/website/pages/it/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/it/developing/subgraphs.mdx rename to website/pages/it/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/it/explorer.mdx b/website/pages/it/subgraphs/explorer.mdx similarity index 100% rename from website/pages/it/explorer.mdx rename to website/pages/it/subgraphs/explorer.mdx diff --git a/website/pages/it/subgraphs/querying/_meta.js b/website/pages/it/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/it/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/querying/querying-best-practices.mdx b/website/pages/it/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/it/querying/querying-best-practices.mdx rename to website/pages/it/subgraphs/querying/best-practices.mdx diff --git a/website/pages/it/querying/distributed-systems.mdx b/website/pages/it/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/it/querying/distributed-systems.mdx rename to website/pages/it/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/it/querying/querying-from-an-application.mdx b/website/pages/it/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/it/querying/querying-from-an-application.mdx rename to website/pages/it/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/it/subgraphs/querying/graph-client/_meta.js b/website/pages/it/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/it/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/querying/graphql-api.mdx b/website/pages/it/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/it/querying/graphql-api.mdx rename to website/pages/it/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/it/querying/querying-the-graph.mdx b/website/pages/it/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/it/querying/querying-the-graph.mdx rename to website/pages/it/subgraphs/querying/introduction.mdx diff --git a/website/pages/it/querying/managing-api-keys.mdx b/website/pages/it/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/it/querying/managing-api-keys.mdx rename to website/pages/it/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/it/querying/querying-with-python.mdx b/website/pages/it/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/it/querying/querying-with-python.mdx rename to website/pages/it/subgraphs/querying/python.mdx diff --git a/website/pages/it/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/it/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/it/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/it/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/it/quick-start.mdx b/website/pages/it/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/it/quick-start.mdx rename to website/pages/it/subgraphs/quick-start.mdx diff --git a/website/pages/it/substreams/_meta.js b/website/pages/it/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/it/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/substreams.mdx b/website/pages/it/substreams/introduction.mdx similarity index 100% rename from website/pages/it/substreams.mdx rename to website/pages/it/substreams/introduction.mdx diff --git a/website/pages/it/substreams/sps/_meta.js b/website/pages/it/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/it/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/it/sps/introduction.mdx b/website/pages/it/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/it/sps/introduction.mdx rename to website/pages/it/substreams/sps/introduction.mdx diff --git a/website/pages/it/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/it/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/it/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/it/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/it/sps/triggers-example.mdx b/website/pages/it/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/it/sps/triggers-example.mdx rename to website/pages/it/substreams/sps/triggers-example.mdx diff --git a/website/pages/it/sps/triggers.mdx b/website/pages/it/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/it/sps/triggers.mdx rename to website/pages/it/substreams/sps/triggers.mdx diff --git a/website/pages/ja/cookbook/_meta.js b/website/pages/ja/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/ja/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/_meta.js b/website/pages/ja/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/ja/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/creating-a-subgraph/_meta.js b/website/pages/ja/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/ja/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/ja/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/deploying/_meta.js b/website/pages/ja/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/ja/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/managing/_meta.js b/website/pages/ja/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/ja/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/developing/publishing/_meta.js b/website/pages/ja/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/ja/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/indexer-tooling/_meta.js b/website/pages/ja/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/ja/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/indexing/_meta.js b/website/pages/ja/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/ja/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/chain-integration-overview.mdx b/website/pages/ja/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/ja/chain-integration-overview.mdx rename to website/pages/ja/indexing/chain-integration-overview.mdx diff --git a/website/pages/ja/indexing.mdx b/website/pages/ja/indexing/introduction.mdx similarity index 100% rename from website/pages/ja/indexing.mdx rename to website/pages/ja/indexing/introduction.mdx diff --git a/website/pages/ja/new-chain-integration.mdx b/website/pages/ja/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/ja/new-chain-integration.mdx rename to website/pages/ja/indexing/new-chain-integration.mdx diff --git a/website/pages/ja/supported-network-requirements.mdx b/website/pages/ja/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/ja/supported-network-requirements.mdx rename to website/pages/ja/indexing/supported-network-requirements.mdx diff --git a/website/pages/ja/tap.mdx b/website/pages/ja/indexing/tap.mdx similarity index 100% rename from website/pages/ja/tap.mdx rename to website/pages/ja/indexing/tap.mdx diff --git a/website/pages/ja/indexing/tooling/_meta.js b/website/pages/ja/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/ja/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/indexer-tooling/firehose.mdx b/website/pages/ja/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/ja/indexer-tooling/firehose.mdx rename to website/pages/ja/indexing/tooling/firehose.mdx diff --git a/website/pages/ja/indexer-tooling/graphcast.mdx b/website/pages/ja/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/ja/indexer-tooling/graphcast.mdx rename to website/pages/ja/indexing/tooling/graphcast.mdx diff --git a/website/pages/ja/indexer-tooling/operating-graph-node.mdx b/website/pages/ja/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ja/indexer-tooling/operating-graph-node.mdx rename to website/pages/ja/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/ja/network/_meta.js b/website/pages/ja/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ja/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/network/overview.mdx b/website/pages/ja/network/overview.mdx deleted file mode 100644 index d46303b4c294..000000000000 --- a/website/pages/ja/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: ネットワークの概要 ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![トークンエコノミクス](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/ja/querying/_meta.js b/website/pages/ja/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/ja/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/querying/graph-client/_meta.js b/website/pages/ja/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/ja/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/release-notes/_meta.js b/website/pages/ja/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/ja/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/resources/_meta.js b/website/pages/ja/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/ja/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/network/benefits.mdx b/website/pages/ja/resources/benefits.mdx similarity index 100% rename from website/pages/ja/network/benefits.mdx rename to website/pages/ja/resources/benefits.mdx diff --git a/website/pages/ja/glossary.mdx b/website/pages/ja/resources/glossary.mdx similarity index 100% rename from website/pages/ja/glossary.mdx rename to website/pages/ja/resources/glossary.mdx diff --git a/website/pages/ja/resources/release-notes/_meta.js b/website/pages/ja/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/ja/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ja/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/ja/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/ja/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ja/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/ja/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/ja/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/ja/resources/roles/_meta.js b/website/pages/ja/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/ja/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/network/curating.mdx b/website/pages/ja/resources/roles/curating.mdx similarity index 100% rename from website/pages/ja/network/curating.mdx rename to website/pages/ja/resources/roles/curating.mdx diff --git a/website/pages/ja/network/delegating.mdx b/website/pages/ja/resources/roles/delegating.mdx similarity index 100% rename from website/pages/ja/network/delegating.mdx rename to website/pages/ja/resources/roles/delegating.mdx diff --git a/website/pages/ja/network/tokenomics.mdx b/website/pages/ja/resources/tokenomics.mdx similarity index 100% rename from website/pages/ja/network/tokenomics.mdx rename to website/pages/ja/resources/tokenomics.mdx diff --git a/website/pages/ja/sps/_meta.js b/website/pages/ja/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/ja/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ja/subgraphs/_meta.js b/website/pages/ja/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/ja/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/billing.mdx b/website/pages/ja/subgraphs/billing.mdx similarity index 100% rename from website/pages/ja/billing.mdx rename to website/pages/ja/subgraphs/billing.mdx diff --git a/website/pages/ja/subgraphs/cookbook/_meta.js b/website/pages/ja/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/ja/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/cookbook/arweave.mdx b/website/pages/ja/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/ja/cookbook/arweave.mdx rename to website/pages/ja/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/ja/cookbook/avoid-eth-calls.mdx b/website/pages/ja/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/ja/cookbook/avoid-eth-calls.mdx rename to website/pages/ja/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/ja/cookbook/cosmos.mdx b/website/pages/ja/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/ja/cookbook/cosmos.mdx rename to website/pages/ja/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/ja/cookbook/derivedfrom.mdx b/website/pages/ja/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/ja/cookbook/derivedfrom.mdx rename to website/pages/ja/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/ja/cookbook/enums.mdx b/website/pages/ja/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/ja/cookbook/enums.mdx rename to website/pages/ja/subgraphs/cookbook/enums.mdx diff --git a/website/pages/ja/cookbook/grafting-hotfix.mdx b/website/pages/ja/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/ja/cookbook/grafting-hotfix.mdx rename to website/pages/ja/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/ja/cookbook/grafting.mdx b/website/pages/ja/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/ja/cookbook/grafting.mdx rename to website/pages/ja/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/ja/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ja/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/ja/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ja/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/ja/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ja/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/ja/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/ja/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/ja/cookbook/near.mdx b/website/pages/ja/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/ja/cookbook/near.mdx rename to website/pages/ja/subgraphs/cookbook/near.mdx diff --git a/website/pages/ja/cookbook/pruning.mdx b/website/pages/ja/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/ja/cookbook/pruning.mdx rename to website/pages/ja/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/ja/cookbook/subgraph-debug-forking.mdx b/website/pages/ja/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/ja/cookbook/subgraph-debug-forking.mdx rename to website/pages/ja/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/ja/cookbook/subgraph-uncrashable.mdx b/website/pages/ja/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/ja/cookbook/subgraph-uncrashable.mdx rename to website/pages/ja/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/ja/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/ja/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/ja/cookbook/timeseries.mdx b/website/pages/ja/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/ja/cookbook/timeseries.mdx rename to website/pages/ja/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/ja/cookbook/transfer-to-the-graph.mdx b/website/pages/ja/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/ja/cookbook/transfer-to-the-graph.mdx rename to website/pages/ja/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/ja/subgraphs/developing/_meta.js b/website/pages/ja/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/ja/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/subgraphs/developing/creating/_meta.js b/website/pages/ja/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/ja/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/developing/creating-a-subgraph/advanced.mdx b/website/pages/ja/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/advanced.mdx rename to website/pages/ja/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/ja/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ja/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/ja/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/ja/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/ja/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/ja/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/ja/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/ja/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/ja/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/ja/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/ja/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ja/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/ja/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/ja/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ja/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/ja/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/ja/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/ja/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/ja/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/ja/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/ja/subgraphs/developing/deploying/_meta.js b/website/pages/ja/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/ja/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/developing/deploying/multiple-networks.mdx b/website/pages/ja/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ja/developing/deploying/multiple-networks.mdx rename to website/pages/ja/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ja/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ja/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ja/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ja/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ja/developing/deploying/using-subgraph-studio.mdx b/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ja/developing/deploying/using-subgraph-studio.mdx rename to website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ja/developing/developer-faqs.mdx b/website/pages/ja/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/ja/developing/developer-faqs.mdx rename to website/pages/ja/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/ja/developing/developing.mdx b/website/pages/ja/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/ja/developing/developing.mdx rename to website/pages/ja/subgraphs/developing/introduction.mdx diff --git a/website/pages/ja/subgraphs/developing/managing/_meta.js b/website/pages/ja/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/ja/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/developing/managing/delete-a-subgraph.mdx b/website/pages/ja/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/ja/developing/managing/delete-a-subgraph.mdx rename to website/pages/ja/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/ja/developing/managing/transfer-a-subgraph.mdx b/website/pages/ja/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/ja/developing/managing/transfer-a-subgraph.mdx rename to website/pages/ja/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/ja/subgraphs/developing/publishing/_meta.js b/website/pages/ja/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/ja/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ja/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ja/developing/subgraphs.mdx b/website/pages/ja/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/ja/developing/subgraphs.mdx rename to website/pages/ja/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/ja/explorer.mdx b/website/pages/ja/subgraphs/explorer.mdx similarity index 100% rename from website/pages/ja/explorer.mdx rename to website/pages/ja/subgraphs/explorer.mdx diff --git a/website/pages/ja/subgraphs/querying/_meta.js b/website/pages/ja/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/ja/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/querying/querying-best-practices.mdx b/website/pages/ja/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/ja/querying/querying-best-practices.mdx rename to website/pages/ja/subgraphs/querying/best-practices.mdx diff --git a/website/pages/ja/querying/distributed-systems.mdx b/website/pages/ja/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/ja/querying/distributed-systems.mdx rename to website/pages/ja/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/ja/querying/querying-from-an-application.mdx b/website/pages/ja/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/ja/querying/querying-from-an-application.mdx rename to website/pages/ja/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/ja/subgraphs/querying/graph-client/_meta.js b/website/pages/ja/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/ja/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/querying/graphql-api.mdx b/website/pages/ja/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/ja/querying/graphql-api.mdx rename to website/pages/ja/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/ja/querying/querying-the-graph.mdx b/website/pages/ja/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/ja/querying/querying-the-graph.mdx rename to website/pages/ja/subgraphs/querying/introduction.mdx diff --git a/website/pages/ja/querying/managing-api-keys.mdx b/website/pages/ja/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/ja/querying/managing-api-keys.mdx rename to website/pages/ja/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/ja/querying/querying-with-python.mdx b/website/pages/ja/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/ja/querying/querying-with-python.mdx rename to website/pages/ja/subgraphs/querying/python.mdx diff --git a/website/pages/ja/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/ja/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/ja/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/ja/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/ja/quick-start.mdx b/website/pages/ja/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/ja/quick-start.mdx rename to website/pages/ja/subgraphs/quick-start.mdx diff --git a/website/pages/ja/substreams/_meta.js b/website/pages/ja/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/ja/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/substreams.mdx b/website/pages/ja/substreams/introduction.mdx similarity index 100% rename from website/pages/ja/substreams.mdx rename to website/pages/ja/substreams/introduction.mdx diff --git a/website/pages/ja/substreams/sps/_meta.js b/website/pages/ja/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/ja/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ja/sps/introduction.mdx b/website/pages/ja/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/ja/sps/introduction.mdx rename to website/pages/ja/substreams/sps/introduction.mdx diff --git a/website/pages/ja/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ja/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ja/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ja/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ja/sps/triggers-example.mdx b/website/pages/ja/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/ja/sps/triggers-example.mdx rename to website/pages/ja/substreams/sps/triggers-example.mdx diff --git a/website/pages/ja/sps/triggers.mdx b/website/pages/ja/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/ja/sps/triggers.mdx rename to website/pages/ja/substreams/sps/triggers.mdx diff --git a/website/pages/ko/cookbook/_meta.js b/website/pages/ko/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/ko/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/_meta.js b/website/pages/ko/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/ko/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/creating-a-subgraph/_meta.js b/website/pages/ko/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/ko/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/ko/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/deploying/_meta.js b/website/pages/ko/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/ko/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/managing/_meta.js b/website/pages/ko/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/ko/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/developing/publishing/_meta.js b/website/pages/ko/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/ko/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/indexer-tooling/_meta.js b/website/pages/ko/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/ko/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/indexing/_meta.js b/website/pages/ko/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/ko/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/chain-integration-overview.mdx b/website/pages/ko/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/ko/chain-integration-overview.mdx rename to website/pages/ko/indexing/chain-integration-overview.mdx diff --git a/website/pages/ko/indexing.mdx b/website/pages/ko/indexing/introduction.mdx similarity index 100% rename from website/pages/ko/indexing.mdx rename to website/pages/ko/indexing/introduction.mdx diff --git a/website/pages/ko/new-chain-integration.mdx b/website/pages/ko/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/ko/new-chain-integration.mdx rename to website/pages/ko/indexing/new-chain-integration.mdx diff --git a/website/pages/ko/supported-network-requirements.mdx b/website/pages/ko/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/ko/supported-network-requirements.mdx rename to website/pages/ko/indexing/supported-network-requirements.mdx diff --git a/website/pages/ko/tap.mdx b/website/pages/ko/indexing/tap.mdx similarity index 100% rename from website/pages/ko/tap.mdx rename to website/pages/ko/indexing/tap.mdx diff --git a/website/pages/ko/indexing/tooling/_meta.js b/website/pages/ko/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/ko/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/indexer-tooling/firehose.mdx b/website/pages/ko/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/ko/indexer-tooling/firehose.mdx rename to website/pages/ko/indexing/tooling/firehose.mdx diff --git a/website/pages/ko/indexer-tooling/graphcast.mdx b/website/pages/ko/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/ko/indexer-tooling/graphcast.mdx rename to website/pages/ko/indexing/tooling/graphcast.mdx diff --git a/website/pages/ko/indexer-tooling/operating-graph-node.mdx b/website/pages/ko/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ko/indexer-tooling/operating-graph-node.mdx rename to website/pages/ko/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/ko/network/_meta.js b/website/pages/ko/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ko/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/network/overview.mdx b/website/pages/ko/network/overview.mdx deleted file mode 100644 index 0779d9a6cb00..000000000000 --- a/website/pages/ko/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/ko/querying/_meta.js b/website/pages/ko/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/ko/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/querying/graph-client/_meta.js b/website/pages/ko/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/ko/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/release-notes/_meta.js b/website/pages/ko/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/ko/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/resources/_meta.js b/website/pages/ko/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/ko/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/network/benefits.mdx b/website/pages/ko/resources/benefits.mdx similarity index 100% rename from website/pages/ko/network/benefits.mdx rename to website/pages/ko/resources/benefits.mdx diff --git a/website/pages/ko/glossary.mdx b/website/pages/ko/resources/glossary.mdx similarity index 100% rename from website/pages/ko/glossary.mdx rename to website/pages/ko/resources/glossary.mdx diff --git a/website/pages/ko/resources/release-notes/_meta.js b/website/pages/ko/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/ko/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ko/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/ko/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/ko/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/ko/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ko/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/ko/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/ko/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/ko/resources/roles/_meta.js b/website/pages/ko/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/ko/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/network/curating.mdx b/website/pages/ko/resources/roles/curating.mdx similarity index 100% rename from website/pages/ko/network/curating.mdx rename to website/pages/ko/resources/roles/curating.mdx diff --git a/website/pages/ko/network/delegating.mdx b/website/pages/ko/resources/roles/delegating.mdx similarity index 100% rename from website/pages/ko/network/delegating.mdx rename to website/pages/ko/resources/roles/delegating.mdx diff --git a/website/pages/ko/network/tokenomics.mdx b/website/pages/ko/resources/tokenomics.mdx similarity index 100% rename from website/pages/ko/network/tokenomics.mdx rename to website/pages/ko/resources/tokenomics.mdx diff --git a/website/pages/ko/sps/_meta.js b/website/pages/ko/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/ko/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ko/subgraphs/_meta.js b/website/pages/ko/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/ko/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/billing.mdx b/website/pages/ko/subgraphs/billing.mdx similarity index 100% rename from website/pages/ko/billing.mdx rename to website/pages/ko/subgraphs/billing.mdx diff --git a/website/pages/ko/subgraphs/cookbook/_meta.js b/website/pages/ko/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/ko/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/cookbook/arweave.mdx b/website/pages/ko/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/ko/cookbook/arweave.mdx rename to website/pages/ko/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/ko/cookbook/avoid-eth-calls.mdx b/website/pages/ko/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/ko/cookbook/avoid-eth-calls.mdx rename to website/pages/ko/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/ko/cookbook/cosmos.mdx b/website/pages/ko/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/ko/cookbook/cosmos.mdx rename to website/pages/ko/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/ko/cookbook/derivedfrom.mdx b/website/pages/ko/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/ko/cookbook/derivedfrom.mdx rename to website/pages/ko/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/ko/cookbook/enums.mdx b/website/pages/ko/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/ko/cookbook/enums.mdx rename to website/pages/ko/subgraphs/cookbook/enums.mdx diff --git a/website/pages/ko/cookbook/grafting-hotfix.mdx b/website/pages/ko/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/ko/cookbook/grafting-hotfix.mdx rename to website/pages/ko/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/ko/cookbook/grafting.mdx b/website/pages/ko/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/ko/cookbook/grafting.mdx rename to website/pages/ko/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/ko/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ko/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/ko/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ko/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/ko/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ko/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/ko/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/ko/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/ko/cookbook/near.mdx b/website/pages/ko/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/ko/cookbook/near.mdx rename to website/pages/ko/subgraphs/cookbook/near.mdx diff --git a/website/pages/ko/cookbook/pruning.mdx b/website/pages/ko/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/ko/cookbook/pruning.mdx rename to website/pages/ko/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/ko/cookbook/subgraph-debug-forking.mdx b/website/pages/ko/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/ko/cookbook/subgraph-debug-forking.mdx rename to website/pages/ko/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/ko/cookbook/subgraph-uncrashable.mdx b/website/pages/ko/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/ko/cookbook/subgraph-uncrashable.mdx rename to website/pages/ko/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/ko/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/ko/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/ko/cookbook/timeseries.mdx b/website/pages/ko/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/ko/cookbook/timeseries.mdx rename to website/pages/ko/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/ko/cookbook/transfer-to-the-graph.mdx b/website/pages/ko/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/ko/cookbook/transfer-to-the-graph.mdx rename to website/pages/ko/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/ko/subgraphs/developing/_meta.js b/website/pages/ko/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/ko/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/subgraphs/developing/creating/_meta.js b/website/pages/ko/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/ko/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/developing/creating-a-subgraph/advanced.mdx b/website/pages/ko/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/advanced.mdx rename to website/pages/ko/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/ko/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ko/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/ko/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/ko/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/ko/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/ko/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/ko/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/ko/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/ko/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/ko/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/ko/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ko/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/ko/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/ko/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ko/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/ko/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/ko/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/ko/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/ko/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/ko/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/ko/subgraphs/developing/deploying/_meta.js b/website/pages/ko/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/ko/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/developing/deploying/multiple-networks.mdx b/website/pages/ko/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ko/developing/deploying/multiple-networks.mdx rename to website/pages/ko/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ko/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ko/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ko/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ko/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ko/developing/deploying/using-subgraph-studio.mdx b/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ko/developing/deploying/using-subgraph-studio.mdx rename to website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ko/developing/developer-faqs.mdx b/website/pages/ko/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/ko/developing/developer-faqs.mdx rename to website/pages/ko/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/ko/developing/developing.mdx b/website/pages/ko/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/ko/developing/developing.mdx rename to website/pages/ko/subgraphs/developing/introduction.mdx diff --git a/website/pages/ko/subgraphs/developing/managing/_meta.js b/website/pages/ko/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/ko/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/developing/managing/delete-a-subgraph.mdx b/website/pages/ko/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/ko/developing/managing/delete-a-subgraph.mdx rename to website/pages/ko/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/ko/developing/managing/transfer-a-subgraph.mdx b/website/pages/ko/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/ko/developing/managing/transfer-a-subgraph.mdx rename to website/pages/ko/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/ko/subgraphs/developing/publishing/_meta.js b/website/pages/ko/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/ko/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ko/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ko/developing/subgraphs.mdx b/website/pages/ko/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/ko/developing/subgraphs.mdx rename to website/pages/ko/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/ko/explorer.mdx b/website/pages/ko/subgraphs/explorer.mdx similarity index 100% rename from website/pages/ko/explorer.mdx rename to website/pages/ko/subgraphs/explorer.mdx diff --git a/website/pages/ko/subgraphs/querying/_meta.js b/website/pages/ko/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/ko/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/querying/querying-best-practices.mdx b/website/pages/ko/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/ko/querying/querying-best-practices.mdx rename to website/pages/ko/subgraphs/querying/best-practices.mdx diff --git a/website/pages/ko/querying/distributed-systems.mdx b/website/pages/ko/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/ko/querying/distributed-systems.mdx rename to website/pages/ko/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/ko/querying/querying-from-an-application.mdx b/website/pages/ko/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/ko/querying/querying-from-an-application.mdx rename to website/pages/ko/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/ko/subgraphs/querying/graph-client/_meta.js b/website/pages/ko/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/ko/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/querying/graphql-api.mdx b/website/pages/ko/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/ko/querying/graphql-api.mdx rename to website/pages/ko/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/ko/querying/querying-the-graph.mdx b/website/pages/ko/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/ko/querying/querying-the-graph.mdx rename to website/pages/ko/subgraphs/querying/introduction.mdx diff --git a/website/pages/ko/querying/managing-api-keys.mdx b/website/pages/ko/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/ko/querying/managing-api-keys.mdx rename to website/pages/ko/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/ko/querying/querying-with-python.mdx b/website/pages/ko/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/ko/querying/querying-with-python.mdx rename to website/pages/ko/subgraphs/querying/python.mdx diff --git a/website/pages/ko/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/ko/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/ko/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/ko/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/ko/quick-start.mdx b/website/pages/ko/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/ko/quick-start.mdx rename to website/pages/ko/subgraphs/quick-start.mdx diff --git a/website/pages/ko/substreams/_meta.js b/website/pages/ko/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/ko/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/substreams.mdx b/website/pages/ko/substreams/introduction.mdx similarity index 100% rename from website/pages/ko/substreams.mdx rename to website/pages/ko/substreams/introduction.mdx diff --git a/website/pages/ko/substreams/sps/_meta.js b/website/pages/ko/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/ko/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ko/sps/introduction.mdx b/website/pages/ko/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/ko/sps/introduction.mdx rename to website/pages/ko/substreams/sps/introduction.mdx diff --git a/website/pages/ko/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ko/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ko/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ko/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ko/sps/triggers-example.mdx b/website/pages/ko/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/ko/sps/triggers-example.mdx rename to website/pages/ko/substreams/sps/triggers-example.mdx diff --git a/website/pages/ko/sps/triggers.mdx b/website/pages/ko/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/ko/sps/triggers.mdx rename to website/pages/ko/substreams/sps/triggers.mdx diff --git a/website/pages/mr/cookbook/_meta.js b/website/pages/mr/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/mr/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/_meta.js b/website/pages/mr/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/mr/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/creating-a-subgraph/_meta.js b/website/pages/mr/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/mr/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/mr/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/deploying/_meta.js b/website/pages/mr/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/mr/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/managing/_meta.js b/website/pages/mr/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/mr/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/developing/publishing/_meta.js b/website/pages/mr/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/mr/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/indexer-tooling/_meta.js b/website/pages/mr/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/mr/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/indexing/_meta.js b/website/pages/mr/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/mr/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/chain-integration-overview.mdx b/website/pages/mr/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/mr/chain-integration-overview.mdx rename to website/pages/mr/indexing/chain-integration-overview.mdx diff --git a/website/pages/mr/indexing.mdx b/website/pages/mr/indexing/introduction.mdx similarity index 100% rename from website/pages/mr/indexing.mdx rename to website/pages/mr/indexing/introduction.mdx diff --git a/website/pages/mr/new-chain-integration.mdx b/website/pages/mr/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/mr/new-chain-integration.mdx rename to website/pages/mr/indexing/new-chain-integration.mdx diff --git a/website/pages/mr/supported-network-requirements.mdx b/website/pages/mr/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/mr/supported-network-requirements.mdx rename to website/pages/mr/indexing/supported-network-requirements.mdx diff --git a/website/pages/mr/tap.mdx b/website/pages/mr/indexing/tap.mdx similarity index 100% rename from website/pages/mr/tap.mdx rename to website/pages/mr/indexing/tap.mdx diff --git a/website/pages/mr/indexing/tooling/_meta.js b/website/pages/mr/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/mr/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/indexer-tooling/firehose.mdx b/website/pages/mr/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/mr/indexer-tooling/firehose.mdx rename to website/pages/mr/indexing/tooling/firehose.mdx diff --git a/website/pages/mr/indexer-tooling/graphcast.mdx b/website/pages/mr/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/mr/indexer-tooling/graphcast.mdx rename to website/pages/mr/indexing/tooling/graphcast.mdx diff --git a/website/pages/mr/indexer-tooling/operating-graph-node.mdx b/website/pages/mr/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/mr/indexer-tooling/operating-graph-node.mdx rename to website/pages/mr/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/mr/network/_meta.js b/website/pages/mr/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/mr/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/network/overview.mdx b/website/pages/mr/network/overview.mdx deleted file mode 100644 index f3726794f033..000000000000 --- a/website/pages/mr/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: नेटवर्क विहंगावलोकन ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![टोकन इकॉनॉमिक्स](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/mr/querying/_meta.js b/website/pages/mr/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/mr/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/querying/graph-client/_meta.js b/website/pages/mr/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/mr/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/release-notes/_meta.js b/website/pages/mr/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/mr/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/resources/_meta.js b/website/pages/mr/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/mr/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/network/benefits.mdx b/website/pages/mr/resources/benefits.mdx similarity index 100% rename from website/pages/mr/network/benefits.mdx rename to website/pages/mr/resources/benefits.mdx diff --git a/website/pages/mr/glossary.mdx b/website/pages/mr/resources/glossary.mdx similarity index 100% rename from website/pages/mr/glossary.mdx rename to website/pages/mr/resources/glossary.mdx diff --git a/website/pages/mr/resources/release-notes/_meta.js b/website/pages/mr/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/mr/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/mr/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/mr/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/mr/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/mr/release-notes/graphql-validations-migration-guide.mdx b/website/pages/mr/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/mr/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/mr/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/mr/resources/roles/_meta.js b/website/pages/mr/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/mr/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/network/curating.mdx b/website/pages/mr/resources/roles/curating.mdx similarity index 100% rename from website/pages/mr/network/curating.mdx rename to website/pages/mr/resources/roles/curating.mdx diff --git a/website/pages/mr/network/delegating.mdx b/website/pages/mr/resources/roles/delegating.mdx similarity index 100% rename from website/pages/mr/network/delegating.mdx rename to website/pages/mr/resources/roles/delegating.mdx diff --git a/website/pages/mr/network/tokenomics.mdx b/website/pages/mr/resources/tokenomics.mdx similarity index 100% rename from website/pages/mr/network/tokenomics.mdx rename to website/pages/mr/resources/tokenomics.mdx diff --git a/website/pages/mr/sps/_meta.js b/website/pages/mr/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/mr/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/mr/subgraphs/_meta.js b/website/pages/mr/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/mr/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/billing.mdx b/website/pages/mr/subgraphs/billing.mdx similarity index 100% rename from website/pages/mr/billing.mdx rename to website/pages/mr/subgraphs/billing.mdx diff --git a/website/pages/mr/subgraphs/cookbook/_meta.js b/website/pages/mr/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/mr/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/cookbook/arweave.mdx b/website/pages/mr/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/mr/cookbook/arweave.mdx rename to website/pages/mr/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/mr/cookbook/avoid-eth-calls.mdx b/website/pages/mr/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/mr/cookbook/avoid-eth-calls.mdx rename to website/pages/mr/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/mr/cookbook/cosmos.mdx b/website/pages/mr/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/mr/cookbook/cosmos.mdx rename to website/pages/mr/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/mr/cookbook/derivedfrom.mdx b/website/pages/mr/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/mr/cookbook/derivedfrom.mdx rename to website/pages/mr/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/mr/cookbook/enums.mdx b/website/pages/mr/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/mr/cookbook/enums.mdx rename to website/pages/mr/subgraphs/cookbook/enums.mdx diff --git a/website/pages/mr/cookbook/grafting-hotfix.mdx b/website/pages/mr/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/mr/cookbook/grafting-hotfix.mdx rename to website/pages/mr/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/mr/cookbook/grafting.mdx b/website/pages/mr/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/mr/cookbook/grafting.mdx rename to website/pages/mr/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/mr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/mr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/mr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/mr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/mr/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/mr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/mr/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/mr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/mr/cookbook/near.mdx b/website/pages/mr/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/mr/cookbook/near.mdx rename to website/pages/mr/subgraphs/cookbook/near.mdx diff --git a/website/pages/mr/cookbook/pruning.mdx b/website/pages/mr/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/mr/cookbook/pruning.mdx rename to website/pages/mr/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/mr/cookbook/subgraph-debug-forking.mdx b/website/pages/mr/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/mr/cookbook/subgraph-debug-forking.mdx rename to website/pages/mr/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/mr/cookbook/subgraph-uncrashable.mdx b/website/pages/mr/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/mr/cookbook/subgraph-uncrashable.mdx rename to website/pages/mr/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/mr/cookbook/substreams-powered-subgraphs.mdx b/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/mr/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/mr/cookbook/timeseries.mdx b/website/pages/mr/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/mr/cookbook/timeseries.mdx rename to website/pages/mr/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/mr/cookbook/transfer-to-the-graph.mdx b/website/pages/mr/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/mr/cookbook/transfer-to-the-graph.mdx rename to website/pages/mr/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/mr/subgraphs/developing/_meta.js b/website/pages/mr/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/mr/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/subgraphs/developing/creating/_meta.js b/website/pages/mr/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/mr/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/developing/creating-a-subgraph/advanced.mdx b/website/pages/mr/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/advanced.mdx rename to website/pages/mr/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/mr/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/mr/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/mr/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/mr/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/mr/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/mr/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/mr/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/mr/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/mr/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/mr/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/mr/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/mr/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/mr/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/mr/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/mr/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/mr/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/mr/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/mr/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/mr/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/mr/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/mr/subgraphs/developing/deploying/_meta.js b/website/pages/mr/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/mr/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/developing/deploying/multiple-networks.mdx b/website/pages/mr/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/mr/developing/deploying/multiple-networks.mdx rename to website/pages/mr/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/mr/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/mr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/mr/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/mr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/mr/developing/deploying/using-subgraph-studio.mdx b/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/mr/developing/deploying/using-subgraph-studio.mdx rename to website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/mr/developing/developer-faqs.mdx b/website/pages/mr/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/mr/developing/developer-faqs.mdx rename to website/pages/mr/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/mr/developing/developing.mdx b/website/pages/mr/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/mr/developing/developing.mdx rename to website/pages/mr/subgraphs/developing/introduction.mdx diff --git a/website/pages/mr/subgraphs/developing/managing/_meta.js b/website/pages/mr/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/mr/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/developing/managing/delete-a-subgraph.mdx b/website/pages/mr/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/mr/developing/managing/delete-a-subgraph.mdx rename to website/pages/mr/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/mr/developing/managing/transfer-a-subgraph.mdx b/website/pages/mr/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/mr/developing/managing/transfer-a-subgraph.mdx rename to website/pages/mr/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/mr/subgraphs/developing/publishing/_meta.js b/website/pages/mr/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/mr/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/developing/publishing/publishing-a-subgraph.mdx b/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/mr/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/mr/developing/subgraphs.mdx b/website/pages/mr/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/mr/developing/subgraphs.mdx rename to website/pages/mr/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/mr/explorer.mdx b/website/pages/mr/subgraphs/explorer.mdx similarity index 100% rename from website/pages/mr/explorer.mdx rename to website/pages/mr/subgraphs/explorer.mdx diff --git a/website/pages/mr/subgraphs/querying/_meta.js b/website/pages/mr/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/mr/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/querying/querying-best-practices.mdx b/website/pages/mr/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/mr/querying/querying-best-practices.mdx rename to website/pages/mr/subgraphs/querying/best-practices.mdx diff --git a/website/pages/mr/querying/distributed-systems.mdx b/website/pages/mr/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/mr/querying/distributed-systems.mdx rename to website/pages/mr/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/mr/querying/querying-from-an-application.mdx b/website/pages/mr/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/mr/querying/querying-from-an-application.mdx rename to website/pages/mr/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/mr/subgraphs/querying/graph-client/_meta.js b/website/pages/mr/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/mr/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/querying/graphql-api.mdx b/website/pages/mr/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/mr/querying/graphql-api.mdx rename to website/pages/mr/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/mr/querying/querying-the-graph.mdx b/website/pages/mr/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/mr/querying/querying-the-graph.mdx rename to website/pages/mr/subgraphs/querying/introduction.mdx diff --git a/website/pages/mr/querying/managing-api-keys.mdx b/website/pages/mr/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/mr/querying/managing-api-keys.mdx rename to website/pages/mr/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/mr/querying/querying-with-python.mdx b/website/pages/mr/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/mr/querying/querying-with-python.mdx rename to website/pages/mr/subgraphs/querying/python.mdx diff --git a/website/pages/mr/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/mr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/mr/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/mr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/mr/quick-start.mdx b/website/pages/mr/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/mr/quick-start.mdx rename to website/pages/mr/subgraphs/quick-start.mdx diff --git a/website/pages/mr/substreams/_meta.js b/website/pages/mr/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/mr/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/substreams.mdx b/website/pages/mr/substreams/introduction.mdx similarity index 100% rename from website/pages/mr/substreams.mdx rename to website/pages/mr/substreams/introduction.mdx diff --git a/website/pages/mr/substreams/sps/_meta.js b/website/pages/mr/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/mr/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/mr/sps/introduction.mdx b/website/pages/mr/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/mr/sps/introduction.mdx rename to website/pages/mr/substreams/sps/introduction.mdx diff --git a/website/pages/mr/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/mr/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/mr/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/mr/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/mr/sps/triggers-example.mdx b/website/pages/mr/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/mr/sps/triggers-example.mdx rename to website/pages/mr/substreams/sps/triggers-example.mdx diff --git a/website/pages/mr/sps/triggers.mdx b/website/pages/mr/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/mr/sps/triggers.mdx rename to website/pages/mr/substreams/sps/triggers.mdx diff --git a/website/pages/nl/cookbook/_meta.js b/website/pages/nl/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/nl/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/_meta.js b/website/pages/nl/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/nl/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/creating-a-subgraph/_meta.js b/website/pages/nl/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/nl/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/nl/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/deploying/_meta.js b/website/pages/nl/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/nl/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/managing/_meta.js b/website/pages/nl/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/nl/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/developing/publishing/_meta.js b/website/pages/nl/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/nl/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/indexer-tooling/_meta.js b/website/pages/nl/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/nl/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/indexing/_meta.js b/website/pages/nl/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/nl/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/chain-integration-overview.mdx b/website/pages/nl/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/nl/chain-integration-overview.mdx rename to website/pages/nl/indexing/chain-integration-overview.mdx diff --git a/website/pages/nl/indexing.mdx b/website/pages/nl/indexing/introduction.mdx similarity index 100% rename from website/pages/nl/indexing.mdx rename to website/pages/nl/indexing/introduction.mdx diff --git a/website/pages/nl/new-chain-integration.mdx b/website/pages/nl/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/nl/new-chain-integration.mdx rename to website/pages/nl/indexing/new-chain-integration.mdx diff --git a/website/pages/nl/supported-network-requirements.mdx b/website/pages/nl/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/nl/supported-network-requirements.mdx rename to website/pages/nl/indexing/supported-network-requirements.mdx diff --git a/website/pages/nl/tap.mdx b/website/pages/nl/indexing/tap.mdx similarity index 100% rename from website/pages/nl/tap.mdx rename to website/pages/nl/indexing/tap.mdx diff --git a/website/pages/nl/indexing/tooling/_meta.js b/website/pages/nl/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/nl/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/indexer-tooling/firehose.mdx b/website/pages/nl/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/nl/indexer-tooling/firehose.mdx rename to website/pages/nl/indexing/tooling/firehose.mdx diff --git a/website/pages/nl/indexer-tooling/graphcast.mdx b/website/pages/nl/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/nl/indexer-tooling/graphcast.mdx rename to website/pages/nl/indexing/tooling/graphcast.mdx diff --git a/website/pages/nl/indexer-tooling/operating-graph-node.mdx b/website/pages/nl/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/nl/indexer-tooling/operating-graph-node.mdx rename to website/pages/nl/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/nl/network/_meta.js b/website/pages/nl/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/nl/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/network/overview.mdx b/website/pages/nl/network/overview.mdx deleted file mode 100644 index 0779d9a6cb00..000000000000 --- a/website/pages/nl/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/nl/querying/_meta.js b/website/pages/nl/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/nl/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/querying/graph-client/_meta.js b/website/pages/nl/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/nl/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/release-notes/_meta.js b/website/pages/nl/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/nl/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/resources/_meta.js b/website/pages/nl/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/nl/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/network/benefits.mdx b/website/pages/nl/resources/benefits.mdx similarity index 100% rename from website/pages/nl/network/benefits.mdx rename to website/pages/nl/resources/benefits.mdx diff --git a/website/pages/nl/glossary.mdx b/website/pages/nl/resources/glossary.mdx similarity index 100% rename from website/pages/nl/glossary.mdx rename to website/pages/nl/resources/glossary.mdx diff --git a/website/pages/nl/resources/release-notes/_meta.js b/website/pages/nl/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/nl/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx b/website/pages/nl/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/nl/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/nl/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/nl/release-notes/graphql-validations-migration-guide.mdx b/website/pages/nl/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/nl/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/nl/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/nl/resources/roles/_meta.js b/website/pages/nl/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/nl/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/network/curating.mdx b/website/pages/nl/resources/roles/curating.mdx similarity index 100% rename from website/pages/nl/network/curating.mdx rename to website/pages/nl/resources/roles/curating.mdx diff --git a/website/pages/nl/network/delegating.mdx b/website/pages/nl/resources/roles/delegating.mdx similarity index 100% rename from website/pages/nl/network/delegating.mdx rename to website/pages/nl/resources/roles/delegating.mdx diff --git a/website/pages/nl/network/tokenomics.mdx b/website/pages/nl/resources/tokenomics.mdx similarity index 100% rename from website/pages/nl/network/tokenomics.mdx rename to website/pages/nl/resources/tokenomics.mdx diff --git a/website/pages/nl/sps/_meta.js b/website/pages/nl/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/nl/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/nl/subgraphs/_meta.js b/website/pages/nl/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/nl/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/billing.mdx b/website/pages/nl/subgraphs/billing.mdx similarity index 100% rename from website/pages/nl/billing.mdx rename to website/pages/nl/subgraphs/billing.mdx diff --git a/website/pages/nl/subgraphs/cookbook/_meta.js b/website/pages/nl/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/nl/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/cookbook/arweave.mdx b/website/pages/nl/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/nl/cookbook/arweave.mdx rename to website/pages/nl/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/nl/cookbook/avoid-eth-calls.mdx b/website/pages/nl/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/nl/cookbook/avoid-eth-calls.mdx rename to website/pages/nl/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/nl/cookbook/cosmos.mdx b/website/pages/nl/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/nl/cookbook/cosmos.mdx rename to website/pages/nl/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/nl/cookbook/derivedfrom.mdx b/website/pages/nl/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/nl/cookbook/derivedfrom.mdx rename to website/pages/nl/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/nl/cookbook/enums.mdx b/website/pages/nl/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/nl/cookbook/enums.mdx rename to website/pages/nl/subgraphs/cookbook/enums.mdx diff --git a/website/pages/nl/cookbook/grafting-hotfix.mdx b/website/pages/nl/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/nl/cookbook/grafting-hotfix.mdx rename to website/pages/nl/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/nl/cookbook/grafting.mdx b/website/pages/nl/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/nl/cookbook/grafting.mdx rename to website/pages/nl/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/nl/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/nl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/nl/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/nl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/nl/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/nl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/nl/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/nl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/nl/cookbook/near.mdx b/website/pages/nl/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/nl/cookbook/near.mdx rename to website/pages/nl/subgraphs/cookbook/near.mdx diff --git a/website/pages/nl/cookbook/pruning.mdx b/website/pages/nl/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/nl/cookbook/pruning.mdx rename to website/pages/nl/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/nl/cookbook/subgraph-debug-forking.mdx b/website/pages/nl/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/nl/cookbook/subgraph-debug-forking.mdx rename to website/pages/nl/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/nl/cookbook/subgraph-uncrashable.mdx b/website/pages/nl/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/nl/cookbook/subgraph-uncrashable.mdx rename to website/pages/nl/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/nl/cookbook/substreams-powered-subgraphs.mdx b/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/nl/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/nl/cookbook/timeseries.mdx b/website/pages/nl/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/nl/cookbook/timeseries.mdx rename to website/pages/nl/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/nl/cookbook/transfer-to-the-graph.mdx b/website/pages/nl/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/nl/cookbook/transfer-to-the-graph.mdx rename to website/pages/nl/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/nl/subgraphs/developing/_meta.js b/website/pages/nl/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/nl/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/subgraphs/developing/creating/_meta.js b/website/pages/nl/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/nl/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/developing/creating-a-subgraph/advanced.mdx b/website/pages/nl/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/advanced.mdx rename to website/pages/nl/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/nl/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/nl/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/nl/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/nl/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/nl/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/nl/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/nl/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/nl/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/nl/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/nl/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/nl/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/nl/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/nl/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/nl/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/nl/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/nl/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/nl/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/nl/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/nl/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/nl/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/nl/subgraphs/developing/deploying/_meta.js b/website/pages/nl/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/nl/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/developing/deploying/multiple-networks.mdx b/website/pages/nl/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/nl/developing/deploying/multiple-networks.mdx rename to website/pages/nl/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/nl/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/nl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/nl/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/nl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/nl/developing/deploying/using-subgraph-studio.mdx b/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/nl/developing/deploying/using-subgraph-studio.mdx rename to website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/nl/developing/developer-faqs.mdx b/website/pages/nl/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/nl/developing/developer-faqs.mdx rename to website/pages/nl/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/nl/developing/developing.mdx b/website/pages/nl/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/nl/developing/developing.mdx rename to website/pages/nl/subgraphs/developing/introduction.mdx diff --git a/website/pages/nl/subgraphs/developing/managing/_meta.js b/website/pages/nl/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/nl/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/developing/managing/delete-a-subgraph.mdx b/website/pages/nl/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/nl/developing/managing/delete-a-subgraph.mdx rename to website/pages/nl/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/nl/developing/managing/transfer-a-subgraph.mdx b/website/pages/nl/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/nl/developing/managing/transfer-a-subgraph.mdx rename to website/pages/nl/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/nl/subgraphs/developing/publishing/_meta.js b/website/pages/nl/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/nl/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/developing/publishing/publishing-a-subgraph.mdx b/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/nl/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/nl/developing/subgraphs.mdx b/website/pages/nl/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/nl/developing/subgraphs.mdx rename to website/pages/nl/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/nl/explorer.mdx b/website/pages/nl/subgraphs/explorer.mdx similarity index 100% rename from website/pages/nl/explorer.mdx rename to website/pages/nl/subgraphs/explorer.mdx diff --git a/website/pages/nl/subgraphs/querying/_meta.js b/website/pages/nl/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/nl/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/querying/querying-best-practices.mdx b/website/pages/nl/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/nl/querying/querying-best-practices.mdx rename to website/pages/nl/subgraphs/querying/best-practices.mdx diff --git a/website/pages/nl/querying/distributed-systems.mdx b/website/pages/nl/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/nl/querying/distributed-systems.mdx rename to website/pages/nl/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/nl/querying/querying-from-an-application.mdx b/website/pages/nl/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/nl/querying/querying-from-an-application.mdx rename to website/pages/nl/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/nl/subgraphs/querying/graph-client/_meta.js b/website/pages/nl/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/nl/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/querying/graphql-api.mdx b/website/pages/nl/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/nl/querying/graphql-api.mdx rename to website/pages/nl/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/nl/querying/querying-the-graph.mdx b/website/pages/nl/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/nl/querying/querying-the-graph.mdx rename to website/pages/nl/subgraphs/querying/introduction.mdx diff --git a/website/pages/nl/querying/managing-api-keys.mdx b/website/pages/nl/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/nl/querying/managing-api-keys.mdx rename to website/pages/nl/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/nl/querying/querying-with-python.mdx b/website/pages/nl/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/nl/querying/querying-with-python.mdx rename to website/pages/nl/subgraphs/querying/python.mdx diff --git a/website/pages/nl/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/nl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/nl/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/nl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/nl/quick-start.mdx b/website/pages/nl/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/nl/quick-start.mdx rename to website/pages/nl/subgraphs/quick-start.mdx diff --git a/website/pages/nl/substreams/_meta.js b/website/pages/nl/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/nl/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/substreams.mdx b/website/pages/nl/substreams/introduction.mdx similarity index 100% rename from website/pages/nl/substreams.mdx rename to website/pages/nl/substreams/introduction.mdx diff --git a/website/pages/nl/substreams/sps/_meta.js b/website/pages/nl/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/nl/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/nl/sps/introduction.mdx b/website/pages/nl/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/nl/sps/introduction.mdx rename to website/pages/nl/substreams/sps/introduction.mdx diff --git a/website/pages/nl/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/nl/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/nl/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/nl/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/nl/sps/triggers-example.mdx b/website/pages/nl/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/nl/sps/triggers-example.mdx rename to website/pages/nl/substreams/sps/triggers-example.mdx diff --git a/website/pages/nl/sps/triggers.mdx b/website/pages/nl/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/nl/sps/triggers.mdx rename to website/pages/nl/substreams/sps/triggers.mdx diff --git a/website/pages/pl/cookbook/_meta.js b/website/pages/pl/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/pl/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/_meta.js b/website/pages/pl/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/pl/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/creating-a-subgraph/_meta.js b/website/pages/pl/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/pl/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/pl/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/deploying/_meta.js b/website/pages/pl/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/pl/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/managing/_meta.js b/website/pages/pl/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/pl/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/developing/publishing/_meta.js b/website/pages/pl/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/pl/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/indexer-tooling/_meta.js b/website/pages/pl/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/pl/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/indexing/_meta.js b/website/pages/pl/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/pl/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/chain-integration-overview.mdx b/website/pages/pl/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/pl/chain-integration-overview.mdx rename to website/pages/pl/indexing/chain-integration-overview.mdx diff --git a/website/pages/pl/indexing.mdx b/website/pages/pl/indexing/introduction.mdx similarity index 100% rename from website/pages/pl/indexing.mdx rename to website/pages/pl/indexing/introduction.mdx diff --git a/website/pages/pl/new-chain-integration.mdx b/website/pages/pl/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/pl/new-chain-integration.mdx rename to website/pages/pl/indexing/new-chain-integration.mdx diff --git a/website/pages/pl/supported-network-requirements.mdx b/website/pages/pl/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/pl/supported-network-requirements.mdx rename to website/pages/pl/indexing/supported-network-requirements.mdx diff --git a/website/pages/pl/tap.mdx b/website/pages/pl/indexing/tap.mdx similarity index 100% rename from website/pages/pl/tap.mdx rename to website/pages/pl/indexing/tap.mdx diff --git a/website/pages/pl/indexing/tooling/_meta.js b/website/pages/pl/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/pl/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/indexer-tooling/firehose.mdx b/website/pages/pl/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/pl/indexer-tooling/firehose.mdx rename to website/pages/pl/indexing/tooling/firehose.mdx diff --git a/website/pages/pl/indexer-tooling/graphcast.mdx b/website/pages/pl/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/pl/indexer-tooling/graphcast.mdx rename to website/pages/pl/indexing/tooling/graphcast.mdx diff --git a/website/pages/pl/indexer-tooling/operating-graph-node.mdx b/website/pages/pl/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/pl/indexer-tooling/operating-graph-node.mdx rename to website/pages/pl/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/pl/network/_meta.js b/website/pages/pl/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/pl/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/network/overview.mdx b/website/pages/pl/network/overview.mdx deleted file mode 100644 index 0779d9a6cb00..000000000000 --- a/website/pages/pl/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/pl/querying/_meta.js b/website/pages/pl/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/pl/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/querying/graph-client/_meta.js b/website/pages/pl/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/pl/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/release-notes/_meta.js b/website/pages/pl/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/pl/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/resources/_meta.js b/website/pages/pl/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/pl/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/network/benefits.mdx b/website/pages/pl/resources/benefits.mdx similarity index 100% rename from website/pages/pl/network/benefits.mdx rename to website/pages/pl/resources/benefits.mdx diff --git a/website/pages/pl/glossary.mdx b/website/pages/pl/resources/glossary.mdx similarity index 100% rename from website/pages/pl/glossary.mdx rename to website/pages/pl/resources/glossary.mdx diff --git a/website/pages/pl/resources/release-notes/_meta.js b/website/pages/pl/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/pl/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx b/website/pages/pl/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/pl/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/pl/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/pl/release-notes/graphql-validations-migration-guide.mdx b/website/pages/pl/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/pl/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/pl/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/pl/resources/roles/_meta.js b/website/pages/pl/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/pl/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/network/curating.mdx b/website/pages/pl/resources/roles/curating.mdx similarity index 100% rename from website/pages/pl/network/curating.mdx rename to website/pages/pl/resources/roles/curating.mdx diff --git a/website/pages/pl/network/delegating.mdx b/website/pages/pl/resources/roles/delegating.mdx similarity index 100% rename from website/pages/pl/network/delegating.mdx rename to website/pages/pl/resources/roles/delegating.mdx diff --git a/website/pages/pl/network/tokenomics.mdx b/website/pages/pl/resources/tokenomics.mdx similarity index 100% rename from website/pages/pl/network/tokenomics.mdx rename to website/pages/pl/resources/tokenomics.mdx diff --git a/website/pages/pl/sps/_meta.js b/website/pages/pl/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/pl/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pl/subgraphs/_meta.js b/website/pages/pl/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/pl/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/billing.mdx b/website/pages/pl/subgraphs/billing.mdx similarity index 100% rename from website/pages/pl/billing.mdx rename to website/pages/pl/subgraphs/billing.mdx diff --git a/website/pages/pl/subgraphs/cookbook/_meta.js b/website/pages/pl/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/pl/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/cookbook/arweave.mdx b/website/pages/pl/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/pl/cookbook/arweave.mdx rename to website/pages/pl/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/pl/cookbook/avoid-eth-calls.mdx b/website/pages/pl/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/pl/cookbook/avoid-eth-calls.mdx rename to website/pages/pl/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/pl/cookbook/cosmos.mdx b/website/pages/pl/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/pl/cookbook/cosmos.mdx rename to website/pages/pl/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/pl/cookbook/derivedfrom.mdx b/website/pages/pl/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/pl/cookbook/derivedfrom.mdx rename to website/pages/pl/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/pl/cookbook/enums.mdx b/website/pages/pl/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/pl/cookbook/enums.mdx rename to website/pages/pl/subgraphs/cookbook/enums.mdx diff --git a/website/pages/pl/cookbook/grafting-hotfix.mdx b/website/pages/pl/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/pl/cookbook/grafting-hotfix.mdx rename to website/pages/pl/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/pl/cookbook/grafting.mdx b/website/pages/pl/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/pl/cookbook/grafting.mdx rename to website/pages/pl/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/pl/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/pl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/pl/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/pl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/pl/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/pl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/pl/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/pl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/pl/cookbook/near.mdx b/website/pages/pl/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/pl/cookbook/near.mdx rename to website/pages/pl/subgraphs/cookbook/near.mdx diff --git a/website/pages/pl/cookbook/pruning.mdx b/website/pages/pl/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/pl/cookbook/pruning.mdx rename to website/pages/pl/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/pl/cookbook/subgraph-debug-forking.mdx b/website/pages/pl/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/pl/cookbook/subgraph-debug-forking.mdx rename to website/pages/pl/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/pl/cookbook/subgraph-uncrashable.mdx b/website/pages/pl/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/pl/cookbook/subgraph-uncrashable.mdx rename to website/pages/pl/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/pl/cookbook/substreams-powered-subgraphs.mdx b/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/pl/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/pl/cookbook/timeseries.mdx b/website/pages/pl/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/pl/cookbook/timeseries.mdx rename to website/pages/pl/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/pl/cookbook/transfer-to-the-graph.mdx b/website/pages/pl/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/pl/cookbook/transfer-to-the-graph.mdx rename to website/pages/pl/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/pl/subgraphs/developing/_meta.js b/website/pages/pl/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/pl/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/subgraphs/developing/creating/_meta.js b/website/pages/pl/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/pl/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/developing/creating-a-subgraph/advanced.mdx b/website/pages/pl/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/advanced.mdx rename to website/pages/pl/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/pl/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/pl/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/pl/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/pl/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/pl/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/pl/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/pl/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/pl/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/pl/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/pl/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/pl/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/pl/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/pl/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/pl/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/pl/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/pl/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/pl/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/pl/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/pl/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/pl/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/pl/subgraphs/developing/deploying/_meta.js b/website/pages/pl/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/pl/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/developing/deploying/multiple-networks.mdx b/website/pages/pl/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/pl/developing/deploying/multiple-networks.mdx rename to website/pages/pl/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/pl/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/pl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/pl/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/pl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/pl/developing/deploying/using-subgraph-studio.mdx b/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/pl/developing/deploying/using-subgraph-studio.mdx rename to website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/pl/developing/developer-faqs.mdx b/website/pages/pl/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/pl/developing/developer-faqs.mdx rename to website/pages/pl/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/pl/developing/developing.mdx b/website/pages/pl/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/pl/developing/developing.mdx rename to website/pages/pl/subgraphs/developing/introduction.mdx diff --git a/website/pages/pl/subgraphs/developing/managing/_meta.js b/website/pages/pl/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/pl/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/developing/managing/delete-a-subgraph.mdx b/website/pages/pl/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/pl/developing/managing/delete-a-subgraph.mdx rename to website/pages/pl/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/pl/developing/managing/transfer-a-subgraph.mdx b/website/pages/pl/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/pl/developing/managing/transfer-a-subgraph.mdx rename to website/pages/pl/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/pl/subgraphs/developing/publishing/_meta.js b/website/pages/pl/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/pl/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/developing/publishing/publishing-a-subgraph.mdx b/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/pl/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/pl/developing/subgraphs.mdx b/website/pages/pl/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/pl/developing/subgraphs.mdx rename to website/pages/pl/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/pl/explorer.mdx b/website/pages/pl/subgraphs/explorer.mdx similarity index 100% rename from website/pages/pl/explorer.mdx rename to website/pages/pl/subgraphs/explorer.mdx diff --git a/website/pages/pl/subgraphs/querying/_meta.js b/website/pages/pl/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/pl/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/querying/querying-best-practices.mdx b/website/pages/pl/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/pl/querying/querying-best-practices.mdx rename to website/pages/pl/subgraphs/querying/best-practices.mdx diff --git a/website/pages/pl/querying/distributed-systems.mdx b/website/pages/pl/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/pl/querying/distributed-systems.mdx rename to website/pages/pl/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/pl/querying/querying-from-an-application.mdx b/website/pages/pl/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/pl/querying/querying-from-an-application.mdx rename to website/pages/pl/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/pl/subgraphs/querying/graph-client/_meta.js b/website/pages/pl/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/pl/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/querying/graphql-api.mdx b/website/pages/pl/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/pl/querying/graphql-api.mdx rename to website/pages/pl/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/pl/querying/querying-the-graph.mdx b/website/pages/pl/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/pl/querying/querying-the-graph.mdx rename to website/pages/pl/subgraphs/querying/introduction.mdx diff --git a/website/pages/pl/querying/managing-api-keys.mdx b/website/pages/pl/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/pl/querying/managing-api-keys.mdx rename to website/pages/pl/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/pl/querying/querying-with-python.mdx b/website/pages/pl/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/pl/querying/querying-with-python.mdx rename to website/pages/pl/subgraphs/querying/python.mdx diff --git a/website/pages/pl/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/pl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/pl/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/pl/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/pl/quick-start.mdx b/website/pages/pl/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/pl/quick-start.mdx rename to website/pages/pl/subgraphs/quick-start.mdx diff --git a/website/pages/pl/substreams/_meta.js b/website/pages/pl/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/pl/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/substreams.mdx b/website/pages/pl/substreams/introduction.mdx similarity index 100% rename from website/pages/pl/substreams.mdx rename to website/pages/pl/substreams/introduction.mdx diff --git a/website/pages/pl/substreams/sps/_meta.js b/website/pages/pl/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/pl/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pl/sps/introduction.mdx b/website/pages/pl/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/pl/sps/introduction.mdx rename to website/pages/pl/substreams/sps/introduction.mdx diff --git a/website/pages/pl/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/pl/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/pl/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/pl/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/pl/sps/triggers-example.mdx b/website/pages/pl/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/pl/sps/triggers-example.mdx rename to website/pages/pl/substreams/sps/triggers-example.mdx diff --git a/website/pages/pl/sps/triggers.mdx b/website/pages/pl/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/pl/sps/triggers.mdx rename to website/pages/pl/substreams/sps/triggers.mdx diff --git a/website/pages/pt/cookbook/_meta.js b/website/pages/pt/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/pt/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/_meta.js b/website/pages/pt/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/pt/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/creating-a-subgraph/_meta.js b/website/pages/pt/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/pt/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/pt/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/deploying/_meta.js b/website/pages/pt/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/pt/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/managing/_meta.js b/website/pages/pt/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/pt/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/developing/publishing/_meta.js b/website/pages/pt/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/pt/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/indexer-tooling/_meta.js b/website/pages/pt/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/pt/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/indexing/_meta.js b/website/pages/pt/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/pt/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/chain-integration-overview.mdx b/website/pages/pt/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/pt/chain-integration-overview.mdx rename to website/pages/pt/indexing/chain-integration-overview.mdx diff --git a/website/pages/pt/indexing.mdx b/website/pages/pt/indexing/introduction.mdx similarity index 100% rename from website/pages/pt/indexing.mdx rename to website/pages/pt/indexing/introduction.mdx diff --git a/website/pages/pt/new-chain-integration.mdx b/website/pages/pt/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/pt/new-chain-integration.mdx rename to website/pages/pt/indexing/new-chain-integration.mdx diff --git a/website/pages/pt/supported-network-requirements.mdx b/website/pages/pt/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/pt/supported-network-requirements.mdx rename to website/pages/pt/indexing/supported-network-requirements.mdx diff --git a/website/pages/pt/tap.mdx b/website/pages/pt/indexing/tap.mdx similarity index 100% rename from website/pages/pt/tap.mdx rename to website/pages/pt/indexing/tap.mdx diff --git a/website/pages/pt/indexing/tooling/_meta.js b/website/pages/pt/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/pt/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/indexer-tooling/firehose.mdx b/website/pages/pt/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/pt/indexer-tooling/firehose.mdx rename to website/pages/pt/indexing/tooling/firehose.mdx diff --git a/website/pages/pt/indexer-tooling/graphcast.mdx b/website/pages/pt/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/pt/indexer-tooling/graphcast.mdx rename to website/pages/pt/indexing/tooling/graphcast.mdx diff --git a/website/pages/pt/indexer-tooling/operating-graph-node.mdx b/website/pages/pt/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/pt/indexer-tooling/operating-graph-node.mdx rename to website/pages/pt/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/pt/network/_meta.js b/website/pages/pt/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/pt/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/network/overview.mdx b/website/pages/pt/network/overview.mdx deleted file mode 100644 index f2cff6868d75..000000000000 --- a/website/pages/pt/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Visão Geral da Rede ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Especificações - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Economia de Token](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/pt/querying/_meta.js b/website/pages/pt/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/pt/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/querying/graph-client/_meta.js b/website/pages/pt/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/pt/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/release-notes/_meta.js b/website/pages/pt/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/pt/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/resources/_meta.js b/website/pages/pt/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/pt/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/network/benefits.mdx b/website/pages/pt/resources/benefits.mdx similarity index 100% rename from website/pages/pt/network/benefits.mdx rename to website/pages/pt/resources/benefits.mdx diff --git a/website/pages/pt/glossary.mdx b/website/pages/pt/resources/glossary.mdx similarity index 100% rename from website/pages/pt/glossary.mdx rename to website/pages/pt/resources/glossary.mdx diff --git a/website/pages/pt/resources/release-notes/_meta.js b/website/pages/pt/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/pt/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx b/website/pages/pt/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/pt/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/pt/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx b/website/pages/pt/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/pt/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/pt/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/pt/resources/roles/_meta.js b/website/pages/pt/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/pt/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/network/curating.mdx b/website/pages/pt/resources/roles/curating.mdx similarity index 100% rename from website/pages/pt/network/curating.mdx rename to website/pages/pt/resources/roles/curating.mdx diff --git a/website/pages/pt/network/delegating.mdx b/website/pages/pt/resources/roles/delegating.mdx similarity index 100% rename from website/pages/pt/network/delegating.mdx rename to website/pages/pt/resources/roles/delegating.mdx diff --git a/website/pages/pt/network/tokenomics.mdx b/website/pages/pt/resources/tokenomics.mdx similarity index 100% rename from website/pages/pt/network/tokenomics.mdx rename to website/pages/pt/resources/tokenomics.mdx diff --git a/website/pages/pt/sps/_meta.js b/website/pages/pt/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/pt/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/pt/subgraphs/_meta.js b/website/pages/pt/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/pt/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/billing.mdx b/website/pages/pt/subgraphs/billing.mdx similarity index 100% rename from website/pages/pt/billing.mdx rename to website/pages/pt/subgraphs/billing.mdx diff --git a/website/pages/pt/subgraphs/cookbook/_meta.js b/website/pages/pt/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/pt/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/cookbook/arweave.mdx b/website/pages/pt/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/pt/cookbook/arweave.mdx rename to website/pages/pt/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/pt/cookbook/avoid-eth-calls.mdx b/website/pages/pt/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/pt/cookbook/avoid-eth-calls.mdx rename to website/pages/pt/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/pt/cookbook/cosmos.mdx b/website/pages/pt/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/pt/cookbook/cosmos.mdx rename to website/pages/pt/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/pt/cookbook/derivedfrom.mdx b/website/pages/pt/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/pt/cookbook/derivedfrom.mdx rename to website/pages/pt/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/pt/cookbook/enums.mdx b/website/pages/pt/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/pt/cookbook/enums.mdx rename to website/pages/pt/subgraphs/cookbook/enums.mdx diff --git a/website/pages/pt/cookbook/grafting-hotfix.mdx b/website/pages/pt/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/pt/cookbook/grafting-hotfix.mdx rename to website/pages/pt/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/pt/cookbook/grafting.mdx b/website/pages/pt/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/pt/cookbook/grafting.mdx rename to website/pages/pt/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/pt/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/pt/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/pt/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/pt/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/pt/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/pt/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/pt/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/pt/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/pt/cookbook/near.mdx b/website/pages/pt/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/pt/cookbook/near.mdx rename to website/pages/pt/subgraphs/cookbook/near.mdx diff --git a/website/pages/pt/cookbook/pruning.mdx b/website/pages/pt/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/pt/cookbook/pruning.mdx rename to website/pages/pt/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/pt/cookbook/subgraph-debug-forking.mdx b/website/pages/pt/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/pt/cookbook/subgraph-debug-forking.mdx rename to website/pages/pt/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/pt/cookbook/subgraph-uncrashable.mdx b/website/pages/pt/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/pt/cookbook/subgraph-uncrashable.mdx rename to website/pages/pt/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/pt/cookbook/substreams-powered-subgraphs.mdx b/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/pt/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/pt/cookbook/timeseries.mdx b/website/pages/pt/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/pt/cookbook/timeseries.mdx rename to website/pages/pt/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/pt/cookbook/transfer-to-the-graph.mdx b/website/pages/pt/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/pt/cookbook/transfer-to-the-graph.mdx rename to website/pages/pt/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/pt/subgraphs/developing/_meta.js b/website/pages/pt/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/pt/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/subgraphs/developing/creating/_meta.js b/website/pages/pt/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/pt/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/developing/creating-a-subgraph/advanced.mdx b/website/pages/pt/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/advanced.mdx rename to website/pages/pt/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/pt/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/pt/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/pt/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/pt/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/pt/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/pt/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/pt/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/pt/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/pt/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/pt/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/pt/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/pt/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/pt/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/pt/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/pt/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/pt/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/pt/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/pt/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/pt/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/pt/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/pt/subgraphs/developing/deploying/_meta.js b/website/pages/pt/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/pt/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/developing/deploying/multiple-networks.mdx b/website/pages/pt/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/pt/developing/deploying/multiple-networks.mdx rename to website/pages/pt/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/pt/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/pt/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/pt/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/pt/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/pt/developing/deploying/using-subgraph-studio.mdx b/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/pt/developing/deploying/using-subgraph-studio.mdx rename to website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/pt/developing/developer-faqs.mdx b/website/pages/pt/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/pt/developing/developer-faqs.mdx rename to website/pages/pt/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/pt/developing/developing.mdx b/website/pages/pt/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/pt/developing/developing.mdx rename to website/pages/pt/subgraphs/developing/introduction.mdx diff --git a/website/pages/pt/subgraphs/developing/managing/_meta.js b/website/pages/pt/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/pt/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/developing/managing/delete-a-subgraph.mdx b/website/pages/pt/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/pt/developing/managing/delete-a-subgraph.mdx rename to website/pages/pt/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/pt/developing/managing/transfer-a-subgraph.mdx b/website/pages/pt/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/pt/developing/managing/transfer-a-subgraph.mdx rename to website/pages/pt/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/pt/subgraphs/developing/publishing/_meta.js b/website/pages/pt/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/pt/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/developing/publishing/publishing-a-subgraph.mdx b/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/pt/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/pt/developing/subgraphs.mdx b/website/pages/pt/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/pt/developing/subgraphs.mdx rename to website/pages/pt/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/pt/explorer.mdx b/website/pages/pt/subgraphs/explorer.mdx similarity index 100% rename from website/pages/pt/explorer.mdx rename to website/pages/pt/subgraphs/explorer.mdx diff --git a/website/pages/pt/subgraphs/querying/_meta.js b/website/pages/pt/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/pt/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/querying/querying-best-practices.mdx b/website/pages/pt/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/pt/querying/querying-best-practices.mdx rename to website/pages/pt/subgraphs/querying/best-practices.mdx diff --git a/website/pages/pt/querying/distributed-systems.mdx b/website/pages/pt/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/pt/querying/distributed-systems.mdx rename to website/pages/pt/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/pt/querying/querying-from-an-application.mdx b/website/pages/pt/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/pt/querying/querying-from-an-application.mdx rename to website/pages/pt/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/pt/subgraphs/querying/graph-client/_meta.js b/website/pages/pt/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/pt/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/querying/graphql-api.mdx b/website/pages/pt/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/pt/querying/graphql-api.mdx rename to website/pages/pt/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/pt/querying/querying-the-graph.mdx b/website/pages/pt/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/pt/querying/querying-the-graph.mdx rename to website/pages/pt/subgraphs/querying/introduction.mdx diff --git a/website/pages/pt/querying/managing-api-keys.mdx b/website/pages/pt/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/pt/querying/managing-api-keys.mdx rename to website/pages/pt/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/pt/querying/querying-with-python.mdx b/website/pages/pt/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/pt/querying/querying-with-python.mdx rename to website/pages/pt/subgraphs/querying/python.mdx diff --git a/website/pages/pt/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/pt/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/pt/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/pt/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/pt/quick-start.mdx b/website/pages/pt/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/pt/quick-start.mdx rename to website/pages/pt/subgraphs/quick-start.mdx diff --git a/website/pages/pt/substreams/_meta.js b/website/pages/pt/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/pt/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/substreams.mdx b/website/pages/pt/substreams/introduction.mdx similarity index 100% rename from website/pages/pt/substreams.mdx rename to website/pages/pt/substreams/introduction.mdx diff --git a/website/pages/pt/substreams/sps/_meta.js b/website/pages/pt/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/pt/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/pt/sps/introduction.mdx b/website/pages/pt/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/pt/sps/introduction.mdx rename to website/pages/pt/substreams/sps/introduction.mdx diff --git a/website/pages/pt/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/pt/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/pt/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/pt/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/pt/sps/triggers-example.mdx b/website/pages/pt/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/pt/sps/triggers-example.mdx rename to website/pages/pt/substreams/sps/triggers-example.mdx diff --git a/website/pages/pt/sps/triggers.mdx b/website/pages/pt/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/pt/sps/triggers.mdx rename to website/pages/pt/substreams/sps/triggers.mdx diff --git a/website/pages/ro/cookbook/_meta.js b/website/pages/ro/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/ro/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/_meta.js b/website/pages/ro/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/ro/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/creating-a-subgraph/_meta.js b/website/pages/ro/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/ro/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/ro/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/deploying/_meta.js b/website/pages/ro/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/ro/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/managing/_meta.js b/website/pages/ro/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/ro/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/developing/publishing/_meta.js b/website/pages/ro/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/ro/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/indexer-tooling/_meta.js b/website/pages/ro/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/ro/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/indexing/_meta.js b/website/pages/ro/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/ro/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/chain-integration-overview.mdx b/website/pages/ro/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/ro/chain-integration-overview.mdx rename to website/pages/ro/indexing/chain-integration-overview.mdx diff --git a/website/pages/ro/indexing.mdx b/website/pages/ro/indexing/introduction.mdx similarity index 100% rename from website/pages/ro/indexing.mdx rename to website/pages/ro/indexing/introduction.mdx diff --git a/website/pages/ro/new-chain-integration.mdx b/website/pages/ro/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/ro/new-chain-integration.mdx rename to website/pages/ro/indexing/new-chain-integration.mdx diff --git a/website/pages/ro/supported-network-requirements.mdx b/website/pages/ro/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/ro/supported-network-requirements.mdx rename to website/pages/ro/indexing/supported-network-requirements.mdx diff --git a/website/pages/ro/tap.mdx b/website/pages/ro/indexing/tap.mdx similarity index 100% rename from website/pages/ro/tap.mdx rename to website/pages/ro/indexing/tap.mdx diff --git a/website/pages/ro/indexing/tooling/_meta.js b/website/pages/ro/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/ro/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/indexer-tooling/firehose.mdx b/website/pages/ro/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/ro/indexer-tooling/firehose.mdx rename to website/pages/ro/indexing/tooling/firehose.mdx diff --git a/website/pages/ro/indexer-tooling/graphcast.mdx b/website/pages/ro/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/ro/indexer-tooling/graphcast.mdx rename to website/pages/ro/indexing/tooling/graphcast.mdx diff --git a/website/pages/ro/indexer-tooling/operating-graph-node.mdx b/website/pages/ro/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ro/indexer-tooling/operating-graph-node.mdx rename to website/pages/ro/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/ro/network/_meta.js b/website/pages/ro/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ro/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/network/overview.mdx b/website/pages/ro/network/overview.mdx deleted file mode 100644 index 0779d9a6cb00..000000000000 --- a/website/pages/ro/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/ro/querying/_meta.js b/website/pages/ro/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/ro/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/querying/graph-client/_meta.js b/website/pages/ro/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/ro/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/release-notes/_meta.js b/website/pages/ro/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/ro/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/resources/_meta.js b/website/pages/ro/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/ro/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/network/benefits.mdx b/website/pages/ro/resources/benefits.mdx similarity index 100% rename from website/pages/ro/network/benefits.mdx rename to website/pages/ro/resources/benefits.mdx diff --git a/website/pages/ro/glossary.mdx b/website/pages/ro/resources/glossary.mdx similarity index 100% rename from website/pages/ro/glossary.mdx rename to website/pages/ro/resources/glossary.mdx diff --git a/website/pages/ro/resources/release-notes/_meta.js b/website/pages/ro/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/ro/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ro/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/ro/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/ro/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/ro/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ro/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/ro/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/ro/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/ro/resources/roles/_meta.js b/website/pages/ro/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/ro/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/network/curating.mdx b/website/pages/ro/resources/roles/curating.mdx similarity index 100% rename from website/pages/ro/network/curating.mdx rename to website/pages/ro/resources/roles/curating.mdx diff --git a/website/pages/ro/network/delegating.mdx b/website/pages/ro/resources/roles/delegating.mdx similarity index 100% rename from website/pages/ro/network/delegating.mdx rename to website/pages/ro/resources/roles/delegating.mdx diff --git a/website/pages/ro/network/tokenomics.mdx b/website/pages/ro/resources/tokenomics.mdx similarity index 100% rename from website/pages/ro/network/tokenomics.mdx rename to website/pages/ro/resources/tokenomics.mdx diff --git a/website/pages/ro/sps/_meta.js b/website/pages/ro/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/ro/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ro/subgraphs/_meta.js b/website/pages/ro/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/ro/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/billing.mdx b/website/pages/ro/subgraphs/billing.mdx similarity index 100% rename from website/pages/ro/billing.mdx rename to website/pages/ro/subgraphs/billing.mdx diff --git a/website/pages/ro/subgraphs/cookbook/_meta.js b/website/pages/ro/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/ro/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/cookbook/arweave.mdx b/website/pages/ro/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/ro/cookbook/arweave.mdx rename to website/pages/ro/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/ro/cookbook/avoid-eth-calls.mdx b/website/pages/ro/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/ro/cookbook/avoid-eth-calls.mdx rename to website/pages/ro/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/ro/cookbook/cosmos.mdx b/website/pages/ro/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/ro/cookbook/cosmos.mdx rename to website/pages/ro/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/ro/cookbook/derivedfrom.mdx b/website/pages/ro/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/ro/cookbook/derivedfrom.mdx rename to website/pages/ro/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/ro/cookbook/enums.mdx b/website/pages/ro/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/ro/cookbook/enums.mdx rename to website/pages/ro/subgraphs/cookbook/enums.mdx diff --git a/website/pages/ro/cookbook/grafting-hotfix.mdx b/website/pages/ro/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/ro/cookbook/grafting-hotfix.mdx rename to website/pages/ro/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/ro/cookbook/grafting.mdx b/website/pages/ro/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/ro/cookbook/grafting.mdx rename to website/pages/ro/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/ro/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ro/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/ro/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ro/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/ro/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ro/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/ro/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/ro/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/ro/cookbook/near.mdx b/website/pages/ro/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/ro/cookbook/near.mdx rename to website/pages/ro/subgraphs/cookbook/near.mdx diff --git a/website/pages/ro/cookbook/pruning.mdx b/website/pages/ro/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/ro/cookbook/pruning.mdx rename to website/pages/ro/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/ro/cookbook/subgraph-debug-forking.mdx b/website/pages/ro/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/ro/cookbook/subgraph-debug-forking.mdx rename to website/pages/ro/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/ro/cookbook/subgraph-uncrashable.mdx b/website/pages/ro/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/ro/cookbook/subgraph-uncrashable.mdx rename to website/pages/ro/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/ro/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/ro/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/ro/cookbook/timeseries.mdx b/website/pages/ro/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/ro/cookbook/timeseries.mdx rename to website/pages/ro/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/ro/cookbook/transfer-to-the-graph.mdx b/website/pages/ro/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/ro/cookbook/transfer-to-the-graph.mdx rename to website/pages/ro/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/ro/subgraphs/developing/_meta.js b/website/pages/ro/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/ro/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/subgraphs/developing/creating/_meta.js b/website/pages/ro/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/ro/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/developing/creating-a-subgraph/advanced.mdx b/website/pages/ro/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/advanced.mdx rename to website/pages/ro/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/ro/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ro/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/ro/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/ro/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/ro/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/ro/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/ro/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/ro/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/ro/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/ro/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/ro/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ro/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/ro/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/ro/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ro/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/ro/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/ro/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/ro/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/ro/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/ro/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/ro/subgraphs/developing/deploying/_meta.js b/website/pages/ro/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/ro/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/developing/deploying/multiple-networks.mdx b/website/pages/ro/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ro/developing/deploying/multiple-networks.mdx rename to website/pages/ro/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ro/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ro/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ro/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ro/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ro/developing/deploying/using-subgraph-studio.mdx b/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ro/developing/deploying/using-subgraph-studio.mdx rename to website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ro/developing/developer-faqs.mdx b/website/pages/ro/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/ro/developing/developer-faqs.mdx rename to website/pages/ro/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/ro/developing/developing.mdx b/website/pages/ro/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/ro/developing/developing.mdx rename to website/pages/ro/subgraphs/developing/introduction.mdx diff --git a/website/pages/ro/subgraphs/developing/managing/_meta.js b/website/pages/ro/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/ro/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/developing/managing/delete-a-subgraph.mdx b/website/pages/ro/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/ro/developing/managing/delete-a-subgraph.mdx rename to website/pages/ro/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/ro/developing/managing/transfer-a-subgraph.mdx b/website/pages/ro/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/ro/developing/managing/transfer-a-subgraph.mdx rename to website/pages/ro/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/ro/subgraphs/developing/publishing/_meta.js b/website/pages/ro/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/ro/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ro/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ro/developing/subgraphs.mdx b/website/pages/ro/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/ro/developing/subgraphs.mdx rename to website/pages/ro/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/ro/explorer.mdx b/website/pages/ro/subgraphs/explorer.mdx similarity index 100% rename from website/pages/ro/explorer.mdx rename to website/pages/ro/subgraphs/explorer.mdx diff --git a/website/pages/ro/subgraphs/querying/_meta.js b/website/pages/ro/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/ro/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/querying/querying-best-practices.mdx b/website/pages/ro/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/ro/querying/querying-best-practices.mdx rename to website/pages/ro/subgraphs/querying/best-practices.mdx diff --git a/website/pages/ro/querying/distributed-systems.mdx b/website/pages/ro/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/ro/querying/distributed-systems.mdx rename to website/pages/ro/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/ro/querying/querying-from-an-application.mdx b/website/pages/ro/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/ro/querying/querying-from-an-application.mdx rename to website/pages/ro/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/ro/subgraphs/querying/graph-client/_meta.js b/website/pages/ro/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/ro/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/querying/graphql-api.mdx b/website/pages/ro/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/ro/querying/graphql-api.mdx rename to website/pages/ro/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/ro/querying/querying-the-graph.mdx b/website/pages/ro/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/ro/querying/querying-the-graph.mdx rename to website/pages/ro/subgraphs/querying/introduction.mdx diff --git a/website/pages/ro/querying/managing-api-keys.mdx b/website/pages/ro/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/ro/querying/managing-api-keys.mdx rename to website/pages/ro/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/ro/querying/querying-with-python.mdx b/website/pages/ro/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/ro/querying/querying-with-python.mdx rename to website/pages/ro/subgraphs/querying/python.mdx diff --git a/website/pages/ro/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/ro/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/ro/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/ro/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/ro/quick-start.mdx b/website/pages/ro/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/ro/quick-start.mdx rename to website/pages/ro/subgraphs/quick-start.mdx diff --git a/website/pages/ro/substreams/_meta.js b/website/pages/ro/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/ro/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/substreams.mdx b/website/pages/ro/substreams/introduction.mdx similarity index 100% rename from website/pages/ro/substreams.mdx rename to website/pages/ro/substreams/introduction.mdx diff --git a/website/pages/ro/substreams/sps/_meta.js b/website/pages/ro/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/ro/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ro/sps/introduction.mdx b/website/pages/ro/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/ro/sps/introduction.mdx rename to website/pages/ro/substreams/sps/introduction.mdx diff --git a/website/pages/ro/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ro/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ro/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ro/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ro/sps/triggers-example.mdx b/website/pages/ro/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/ro/sps/triggers-example.mdx rename to website/pages/ro/substreams/sps/triggers-example.mdx diff --git a/website/pages/ro/sps/triggers.mdx b/website/pages/ro/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/ro/sps/triggers.mdx rename to website/pages/ro/substreams/sps/triggers.mdx diff --git a/website/pages/ru/cookbook/_meta.js b/website/pages/ru/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/ru/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/_meta.js b/website/pages/ru/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/ru/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/creating-a-subgraph/_meta.js b/website/pages/ru/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/ru/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/ru/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/deploying/_meta.js b/website/pages/ru/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/ru/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/managing/_meta.js b/website/pages/ru/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/ru/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/developing/publishing/_meta.js b/website/pages/ru/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/ru/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/indexer-tooling/_meta.js b/website/pages/ru/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/ru/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/indexing/_meta.js b/website/pages/ru/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/ru/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/chain-integration-overview.mdx b/website/pages/ru/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/ru/chain-integration-overview.mdx rename to website/pages/ru/indexing/chain-integration-overview.mdx diff --git a/website/pages/ru/indexing.mdx b/website/pages/ru/indexing/introduction.mdx similarity index 100% rename from website/pages/ru/indexing.mdx rename to website/pages/ru/indexing/introduction.mdx diff --git a/website/pages/ru/new-chain-integration.mdx b/website/pages/ru/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/ru/new-chain-integration.mdx rename to website/pages/ru/indexing/new-chain-integration.mdx diff --git a/website/pages/ru/supported-network-requirements.mdx b/website/pages/ru/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/ru/supported-network-requirements.mdx rename to website/pages/ru/indexing/supported-network-requirements.mdx diff --git a/website/pages/ru/tap.mdx b/website/pages/ru/indexing/tap.mdx similarity index 100% rename from website/pages/ru/tap.mdx rename to website/pages/ru/indexing/tap.mdx diff --git a/website/pages/ru/indexing/tooling/_meta.js b/website/pages/ru/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/ru/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/indexer-tooling/firehose.mdx b/website/pages/ru/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/ru/indexer-tooling/firehose.mdx rename to website/pages/ru/indexing/tooling/firehose.mdx diff --git a/website/pages/ru/indexer-tooling/graphcast.mdx b/website/pages/ru/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/ru/indexer-tooling/graphcast.mdx rename to website/pages/ru/indexing/tooling/graphcast.mdx diff --git a/website/pages/ru/indexer-tooling/operating-graph-node.mdx b/website/pages/ru/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ru/indexer-tooling/operating-graph-node.mdx rename to website/pages/ru/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/ru/network/_meta.js b/website/pages/ru/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ru/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/network/overview.mdx b/website/pages/ru/network/overview.mdx deleted file mode 100644 index d201c743d2f4..000000000000 --- a/website/pages/ru/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Специфические особенности - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Токеномика](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/ru/querying/_meta.js b/website/pages/ru/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/ru/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/querying/graph-client/_meta.js b/website/pages/ru/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/ru/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/release-notes/_meta.js b/website/pages/ru/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/ru/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/resources/_meta.js b/website/pages/ru/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/ru/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/network/benefits.mdx b/website/pages/ru/resources/benefits.mdx similarity index 100% rename from website/pages/ru/network/benefits.mdx rename to website/pages/ru/resources/benefits.mdx diff --git a/website/pages/ru/glossary.mdx b/website/pages/ru/resources/glossary.mdx similarity index 100% rename from website/pages/ru/glossary.mdx rename to website/pages/ru/resources/glossary.mdx diff --git a/website/pages/ru/resources/release-notes/_meta.js b/website/pages/ru/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/ru/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ru/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/ru/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/ru/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ru/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/ru/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/ru/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/ru/resources/roles/_meta.js b/website/pages/ru/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/ru/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/network/curating.mdx b/website/pages/ru/resources/roles/curating.mdx similarity index 100% rename from website/pages/ru/network/curating.mdx rename to website/pages/ru/resources/roles/curating.mdx diff --git a/website/pages/ru/network/delegating.mdx b/website/pages/ru/resources/roles/delegating.mdx similarity index 100% rename from website/pages/ru/network/delegating.mdx rename to website/pages/ru/resources/roles/delegating.mdx diff --git a/website/pages/ru/network/tokenomics.mdx b/website/pages/ru/resources/tokenomics.mdx similarity index 100% rename from website/pages/ru/network/tokenomics.mdx rename to website/pages/ru/resources/tokenomics.mdx diff --git a/website/pages/ru/sps/_meta.js b/website/pages/ru/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/ru/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ru/subgraphs/_meta.js b/website/pages/ru/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/ru/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/billing.mdx b/website/pages/ru/subgraphs/billing.mdx similarity index 100% rename from website/pages/ru/billing.mdx rename to website/pages/ru/subgraphs/billing.mdx diff --git a/website/pages/ru/subgraphs/cookbook/_meta.js b/website/pages/ru/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/ru/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/cookbook/arweave.mdx b/website/pages/ru/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/ru/cookbook/arweave.mdx rename to website/pages/ru/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/ru/cookbook/avoid-eth-calls.mdx b/website/pages/ru/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/ru/cookbook/avoid-eth-calls.mdx rename to website/pages/ru/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/ru/cookbook/cosmos.mdx b/website/pages/ru/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/ru/cookbook/cosmos.mdx rename to website/pages/ru/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/ru/cookbook/derivedfrom.mdx b/website/pages/ru/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/ru/cookbook/derivedfrom.mdx rename to website/pages/ru/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/ru/cookbook/enums.mdx b/website/pages/ru/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/ru/cookbook/enums.mdx rename to website/pages/ru/subgraphs/cookbook/enums.mdx diff --git a/website/pages/ru/cookbook/grafting-hotfix.mdx b/website/pages/ru/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/ru/cookbook/grafting-hotfix.mdx rename to website/pages/ru/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/ru/cookbook/grafting.mdx b/website/pages/ru/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/ru/cookbook/grafting.mdx rename to website/pages/ru/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/ru/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ru/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/ru/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ru/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/ru/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ru/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/ru/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/ru/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/ru/cookbook/near.mdx b/website/pages/ru/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/ru/cookbook/near.mdx rename to website/pages/ru/subgraphs/cookbook/near.mdx diff --git a/website/pages/ru/cookbook/pruning.mdx b/website/pages/ru/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/ru/cookbook/pruning.mdx rename to website/pages/ru/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/ru/cookbook/subgraph-debug-forking.mdx b/website/pages/ru/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/ru/cookbook/subgraph-debug-forking.mdx rename to website/pages/ru/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/ru/cookbook/subgraph-uncrashable.mdx b/website/pages/ru/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/ru/cookbook/subgraph-uncrashable.mdx rename to website/pages/ru/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/ru/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/ru/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/ru/cookbook/timeseries.mdx b/website/pages/ru/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/ru/cookbook/timeseries.mdx rename to website/pages/ru/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/ru/cookbook/transfer-to-the-graph.mdx b/website/pages/ru/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/ru/cookbook/transfer-to-the-graph.mdx rename to website/pages/ru/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/ru/subgraphs/developing/_meta.js b/website/pages/ru/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/ru/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/subgraphs/developing/creating/_meta.js b/website/pages/ru/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/ru/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/developing/creating-a-subgraph/advanced.mdx b/website/pages/ru/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/advanced.mdx rename to website/pages/ru/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/ru/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ru/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/ru/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/ru/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/ru/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/ru/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/ru/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/ru/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/ru/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/ru/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/ru/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/ru/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/ru/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ru/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/ru/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/ru/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ru/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/ru/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/ru/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/ru/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/ru/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/ru/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/ru/subgraphs/developing/deploying/_meta.js b/website/pages/ru/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/ru/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/developing/deploying/multiple-networks.mdx b/website/pages/ru/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ru/developing/deploying/multiple-networks.mdx rename to website/pages/ru/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ru/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ru/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ru/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ru/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ru/developing/deploying/using-subgraph-studio.mdx b/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ru/developing/deploying/using-subgraph-studio.mdx rename to website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ru/developing/developer-faqs.mdx b/website/pages/ru/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/ru/developing/developer-faqs.mdx rename to website/pages/ru/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/ru/developing/developing.mdx b/website/pages/ru/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/ru/developing/developing.mdx rename to website/pages/ru/subgraphs/developing/introduction.mdx diff --git a/website/pages/ru/subgraphs/developing/managing/_meta.js b/website/pages/ru/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/ru/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/developing/managing/delete-a-subgraph.mdx b/website/pages/ru/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/ru/developing/managing/delete-a-subgraph.mdx rename to website/pages/ru/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/ru/developing/managing/transfer-a-subgraph.mdx b/website/pages/ru/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/ru/developing/managing/transfer-a-subgraph.mdx rename to website/pages/ru/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/ru/subgraphs/developing/publishing/_meta.js b/website/pages/ru/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/ru/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ru/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ru/developing/subgraphs.mdx b/website/pages/ru/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/ru/developing/subgraphs.mdx rename to website/pages/ru/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/ru/explorer.mdx b/website/pages/ru/subgraphs/explorer.mdx similarity index 100% rename from website/pages/ru/explorer.mdx rename to website/pages/ru/subgraphs/explorer.mdx diff --git a/website/pages/ru/subgraphs/querying/_meta.js b/website/pages/ru/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/ru/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/querying/querying-best-practices.mdx b/website/pages/ru/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/ru/querying/querying-best-practices.mdx rename to website/pages/ru/subgraphs/querying/best-practices.mdx diff --git a/website/pages/ru/querying/distributed-systems.mdx b/website/pages/ru/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/ru/querying/distributed-systems.mdx rename to website/pages/ru/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/ru/querying/querying-from-an-application.mdx b/website/pages/ru/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/ru/querying/querying-from-an-application.mdx rename to website/pages/ru/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/ru/subgraphs/querying/graph-client/_meta.js b/website/pages/ru/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/ru/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/querying/graphql-api.mdx b/website/pages/ru/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/ru/querying/graphql-api.mdx rename to website/pages/ru/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/ru/querying/querying-the-graph.mdx b/website/pages/ru/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/ru/querying/querying-the-graph.mdx rename to website/pages/ru/subgraphs/querying/introduction.mdx diff --git a/website/pages/ru/querying/managing-api-keys.mdx b/website/pages/ru/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/ru/querying/managing-api-keys.mdx rename to website/pages/ru/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/ru/querying/querying-with-python.mdx b/website/pages/ru/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/ru/querying/querying-with-python.mdx rename to website/pages/ru/subgraphs/querying/python.mdx diff --git a/website/pages/ru/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/ru/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/ru/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/ru/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/ru/quick-start.mdx b/website/pages/ru/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/ru/quick-start.mdx rename to website/pages/ru/subgraphs/quick-start.mdx diff --git a/website/pages/ru/substreams/_meta.js b/website/pages/ru/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/ru/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/substreams.mdx b/website/pages/ru/substreams/introduction.mdx similarity index 100% rename from website/pages/ru/substreams.mdx rename to website/pages/ru/substreams/introduction.mdx diff --git a/website/pages/ru/substreams/sps/_meta.js b/website/pages/ru/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/ru/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ru/sps/introduction.mdx b/website/pages/ru/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/ru/sps/introduction.mdx rename to website/pages/ru/substreams/sps/introduction.mdx diff --git a/website/pages/ru/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ru/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ru/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ru/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ru/sps/triggers-example.mdx b/website/pages/ru/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/ru/sps/triggers-example.mdx rename to website/pages/ru/substreams/sps/triggers-example.mdx diff --git a/website/pages/ru/sps/triggers.mdx b/website/pages/ru/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/ru/sps/triggers.mdx rename to website/pages/ru/substreams/sps/triggers.mdx diff --git a/website/pages/sv/cookbook/_meta.js b/website/pages/sv/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/sv/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/_meta.js b/website/pages/sv/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/sv/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/creating-a-subgraph/_meta.js b/website/pages/sv/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/sv/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/sv/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/deploying/_meta.js b/website/pages/sv/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/sv/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/managing/_meta.js b/website/pages/sv/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/sv/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/developing/publishing/_meta.js b/website/pages/sv/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/sv/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/indexer-tooling/_meta.js b/website/pages/sv/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/sv/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/indexing/_meta.js b/website/pages/sv/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/sv/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/chain-integration-overview.mdx b/website/pages/sv/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/sv/chain-integration-overview.mdx rename to website/pages/sv/indexing/chain-integration-overview.mdx diff --git a/website/pages/sv/indexing.mdx b/website/pages/sv/indexing/introduction.mdx similarity index 100% rename from website/pages/sv/indexing.mdx rename to website/pages/sv/indexing/introduction.mdx diff --git a/website/pages/sv/new-chain-integration.mdx b/website/pages/sv/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/sv/new-chain-integration.mdx rename to website/pages/sv/indexing/new-chain-integration.mdx diff --git a/website/pages/sv/supported-network-requirements.mdx b/website/pages/sv/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/sv/supported-network-requirements.mdx rename to website/pages/sv/indexing/supported-network-requirements.mdx diff --git a/website/pages/sv/tap.mdx b/website/pages/sv/indexing/tap.mdx similarity index 100% rename from website/pages/sv/tap.mdx rename to website/pages/sv/indexing/tap.mdx diff --git a/website/pages/sv/indexing/tooling/_meta.js b/website/pages/sv/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/sv/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/indexer-tooling/firehose.mdx b/website/pages/sv/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/sv/indexer-tooling/firehose.mdx rename to website/pages/sv/indexing/tooling/firehose.mdx diff --git a/website/pages/sv/indexer-tooling/graphcast.mdx b/website/pages/sv/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/sv/indexer-tooling/graphcast.mdx rename to website/pages/sv/indexing/tooling/graphcast.mdx diff --git a/website/pages/sv/indexer-tooling/operating-graph-node.mdx b/website/pages/sv/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/sv/indexer-tooling/operating-graph-node.mdx rename to website/pages/sv/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/sv/network/_meta.js b/website/pages/sv/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/sv/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/network/overview.mdx b/website/pages/sv/network/overview.mdx deleted file mode 100644 index a8af86bb9142..000000000000 --- a/website/pages/sv/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Nätverksöversikt ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Tokenekonomi](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/sv/querying/_meta.js b/website/pages/sv/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/sv/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/querying/graph-client/_meta.js b/website/pages/sv/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/sv/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/release-notes/_meta.js b/website/pages/sv/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/sv/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/resources/_meta.js b/website/pages/sv/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/sv/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/network/benefits.mdx b/website/pages/sv/resources/benefits.mdx similarity index 100% rename from website/pages/sv/network/benefits.mdx rename to website/pages/sv/resources/benefits.mdx diff --git a/website/pages/sv/glossary.mdx b/website/pages/sv/resources/glossary.mdx similarity index 100% rename from website/pages/sv/glossary.mdx rename to website/pages/sv/resources/glossary.mdx diff --git a/website/pages/sv/resources/release-notes/_meta.js b/website/pages/sv/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/sv/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx b/website/pages/sv/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/sv/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/sv/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/sv/release-notes/graphql-validations-migration-guide.mdx b/website/pages/sv/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/sv/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/sv/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/sv/resources/roles/_meta.js b/website/pages/sv/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/sv/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/network/curating.mdx b/website/pages/sv/resources/roles/curating.mdx similarity index 100% rename from website/pages/sv/network/curating.mdx rename to website/pages/sv/resources/roles/curating.mdx diff --git a/website/pages/sv/network/delegating.mdx b/website/pages/sv/resources/roles/delegating.mdx similarity index 100% rename from website/pages/sv/network/delegating.mdx rename to website/pages/sv/resources/roles/delegating.mdx diff --git a/website/pages/sv/network/tokenomics.mdx b/website/pages/sv/resources/tokenomics.mdx similarity index 100% rename from website/pages/sv/network/tokenomics.mdx rename to website/pages/sv/resources/tokenomics.mdx diff --git a/website/pages/sv/sps/_meta.js b/website/pages/sv/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/sv/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sv/subgraphs/_meta.js b/website/pages/sv/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/sv/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/billing.mdx b/website/pages/sv/subgraphs/billing.mdx similarity index 100% rename from website/pages/sv/billing.mdx rename to website/pages/sv/subgraphs/billing.mdx diff --git a/website/pages/sv/subgraphs/cookbook/_meta.js b/website/pages/sv/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/sv/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/cookbook/arweave.mdx b/website/pages/sv/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/sv/cookbook/arweave.mdx rename to website/pages/sv/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/sv/cookbook/avoid-eth-calls.mdx b/website/pages/sv/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/sv/cookbook/avoid-eth-calls.mdx rename to website/pages/sv/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/sv/cookbook/cosmos.mdx b/website/pages/sv/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/sv/cookbook/cosmos.mdx rename to website/pages/sv/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/sv/cookbook/derivedfrom.mdx b/website/pages/sv/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/sv/cookbook/derivedfrom.mdx rename to website/pages/sv/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/sv/cookbook/enums.mdx b/website/pages/sv/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/sv/cookbook/enums.mdx rename to website/pages/sv/subgraphs/cookbook/enums.mdx diff --git a/website/pages/sv/cookbook/grafting-hotfix.mdx b/website/pages/sv/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/sv/cookbook/grafting-hotfix.mdx rename to website/pages/sv/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/sv/cookbook/grafting.mdx b/website/pages/sv/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/sv/cookbook/grafting.mdx rename to website/pages/sv/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/sv/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/sv/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/sv/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/sv/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/sv/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/sv/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/sv/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/sv/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/sv/cookbook/near.mdx b/website/pages/sv/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/sv/cookbook/near.mdx rename to website/pages/sv/subgraphs/cookbook/near.mdx diff --git a/website/pages/sv/cookbook/pruning.mdx b/website/pages/sv/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/sv/cookbook/pruning.mdx rename to website/pages/sv/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/sv/cookbook/subgraph-debug-forking.mdx b/website/pages/sv/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/sv/cookbook/subgraph-debug-forking.mdx rename to website/pages/sv/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/sv/cookbook/subgraph-uncrashable.mdx b/website/pages/sv/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/sv/cookbook/subgraph-uncrashable.mdx rename to website/pages/sv/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/sv/cookbook/substreams-powered-subgraphs.mdx b/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/sv/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/sv/cookbook/timeseries.mdx b/website/pages/sv/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/sv/cookbook/timeseries.mdx rename to website/pages/sv/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/sv/cookbook/transfer-to-the-graph.mdx b/website/pages/sv/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/sv/cookbook/transfer-to-the-graph.mdx rename to website/pages/sv/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/sv/subgraphs/developing/_meta.js b/website/pages/sv/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/sv/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/subgraphs/developing/creating/_meta.js b/website/pages/sv/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/sv/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/developing/creating-a-subgraph/advanced.mdx b/website/pages/sv/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/advanced.mdx rename to website/pages/sv/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/sv/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/sv/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/sv/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/sv/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/sv/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/sv/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/sv/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/sv/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/sv/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/sv/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/sv/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/sv/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/sv/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/sv/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/sv/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/sv/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/sv/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/sv/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/sv/subgraphs/developing/deploying/_meta.js b/website/pages/sv/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/sv/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/developing/deploying/multiple-networks.mdx b/website/pages/sv/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/sv/developing/deploying/multiple-networks.mdx rename to website/pages/sv/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/sv/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/sv/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/sv/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/sv/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/sv/developing/deploying/using-subgraph-studio.mdx b/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/sv/developing/deploying/using-subgraph-studio.mdx rename to website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/sv/developing/developer-faqs.mdx b/website/pages/sv/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/sv/developing/developer-faqs.mdx rename to website/pages/sv/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/sv/developing/developing.mdx b/website/pages/sv/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/sv/developing/developing.mdx rename to website/pages/sv/subgraphs/developing/introduction.mdx diff --git a/website/pages/sv/subgraphs/developing/managing/_meta.js b/website/pages/sv/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/sv/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/developing/managing/delete-a-subgraph.mdx b/website/pages/sv/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/sv/developing/managing/delete-a-subgraph.mdx rename to website/pages/sv/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/sv/developing/managing/transfer-a-subgraph.mdx b/website/pages/sv/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/sv/developing/managing/transfer-a-subgraph.mdx rename to website/pages/sv/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/sv/subgraphs/developing/publishing/_meta.js b/website/pages/sv/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/sv/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/developing/publishing/publishing-a-subgraph.mdx b/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/sv/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/sv/developing/subgraphs.mdx b/website/pages/sv/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/sv/developing/subgraphs.mdx rename to website/pages/sv/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/sv/explorer.mdx b/website/pages/sv/subgraphs/explorer.mdx similarity index 100% rename from website/pages/sv/explorer.mdx rename to website/pages/sv/subgraphs/explorer.mdx diff --git a/website/pages/sv/subgraphs/querying/_meta.js b/website/pages/sv/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/sv/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/querying/querying-best-practices.mdx b/website/pages/sv/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/sv/querying/querying-best-practices.mdx rename to website/pages/sv/subgraphs/querying/best-practices.mdx diff --git a/website/pages/sv/querying/distributed-systems.mdx b/website/pages/sv/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/sv/querying/distributed-systems.mdx rename to website/pages/sv/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/sv/querying/querying-from-an-application.mdx b/website/pages/sv/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/sv/querying/querying-from-an-application.mdx rename to website/pages/sv/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/sv/subgraphs/querying/graph-client/_meta.js b/website/pages/sv/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/sv/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/querying/graphql-api.mdx b/website/pages/sv/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/sv/querying/graphql-api.mdx rename to website/pages/sv/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/sv/querying/querying-the-graph.mdx b/website/pages/sv/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/sv/querying/querying-the-graph.mdx rename to website/pages/sv/subgraphs/querying/introduction.mdx diff --git a/website/pages/sv/querying/managing-api-keys.mdx b/website/pages/sv/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/sv/querying/managing-api-keys.mdx rename to website/pages/sv/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/sv/querying/querying-with-python.mdx b/website/pages/sv/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/sv/querying/querying-with-python.mdx rename to website/pages/sv/subgraphs/querying/python.mdx diff --git a/website/pages/sv/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/sv/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/sv/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/sv/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/sv/quick-start.mdx b/website/pages/sv/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/sv/quick-start.mdx rename to website/pages/sv/subgraphs/quick-start.mdx diff --git a/website/pages/sv/substreams/_meta.js b/website/pages/sv/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/sv/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/substreams.mdx b/website/pages/sv/substreams/introduction.mdx similarity index 100% rename from website/pages/sv/substreams.mdx rename to website/pages/sv/substreams/introduction.mdx diff --git a/website/pages/sv/substreams/sps/_meta.js b/website/pages/sv/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/sv/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sv/sps/introduction.mdx b/website/pages/sv/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/sv/sps/introduction.mdx rename to website/pages/sv/substreams/sps/introduction.mdx diff --git a/website/pages/sv/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/sv/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/sv/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/sv/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/sv/sps/triggers-example.mdx b/website/pages/sv/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/sv/sps/triggers-example.mdx rename to website/pages/sv/substreams/sps/triggers-example.mdx diff --git a/website/pages/sv/sps/triggers.mdx b/website/pages/sv/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/sv/sps/triggers.mdx rename to website/pages/sv/substreams/sps/triggers.mdx diff --git a/website/pages/sw/cookbook/_meta.js b/website/pages/sw/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/sw/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/_meta.js b/website/pages/sw/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/sw/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/creating-a-subgraph/_meta.js b/website/pages/sw/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/sw/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/sw/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/deploying/_meta.js b/website/pages/sw/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/sw/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/managing/_meta.js b/website/pages/sw/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/sw/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/developing/publishing/_meta.js b/website/pages/sw/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/sw/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/indexer-tooling/_meta.js b/website/pages/sw/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/sw/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/indexing/_meta.js b/website/pages/sw/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/sw/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/chain-integration-overview.mdx b/website/pages/sw/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/sw/chain-integration-overview.mdx rename to website/pages/sw/indexing/chain-integration-overview.mdx diff --git a/website/pages/sw/indexing.mdx b/website/pages/sw/indexing/introduction.mdx similarity index 100% rename from website/pages/sw/indexing.mdx rename to website/pages/sw/indexing/introduction.mdx diff --git a/website/pages/sw/new-chain-integration.mdx b/website/pages/sw/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/sw/new-chain-integration.mdx rename to website/pages/sw/indexing/new-chain-integration.mdx diff --git a/website/pages/sw/supported-network-requirements.mdx b/website/pages/sw/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/sw/supported-network-requirements.mdx rename to website/pages/sw/indexing/supported-network-requirements.mdx diff --git a/website/pages/sw/tap.mdx b/website/pages/sw/indexing/tap.mdx similarity index 100% rename from website/pages/sw/tap.mdx rename to website/pages/sw/indexing/tap.mdx diff --git a/website/pages/sw/indexing/tooling/_meta.js b/website/pages/sw/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/sw/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/indexer-tooling/firehose.mdx b/website/pages/sw/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/sw/indexer-tooling/firehose.mdx rename to website/pages/sw/indexing/tooling/firehose.mdx diff --git a/website/pages/sw/indexer-tooling/graphcast.mdx b/website/pages/sw/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/sw/indexer-tooling/graphcast.mdx rename to website/pages/sw/indexing/tooling/graphcast.mdx diff --git a/website/pages/sw/indexer-tooling/operating-graph-node.mdx b/website/pages/sw/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/sw/indexer-tooling/operating-graph-node.mdx rename to website/pages/sw/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/sw/network/_meta.js b/website/pages/sw/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/sw/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/network/overview.mdx b/website/pages/sw/network/overview.mdx deleted file mode 100644 index 0779d9a6cb00..000000000000 --- a/website/pages/sw/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/sw/querying/_meta.js b/website/pages/sw/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/sw/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/querying/graph-client/_meta.js b/website/pages/sw/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/sw/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/release-notes/_meta.js b/website/pages/sw/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/sw/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/resources/_meta.js b/website/pages/sw/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/sw/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/network/benefits.mdx b/website/pages/sw/resources/benefits.mdx similarity index 100% rename from website/pages/sw/network/benefits.mdx rename to website/pages/sw/resources/benefits.mdx diff --git a/website/pages/sw/glossary.mdx b/website/pages/sw/resources/glossary.mdx similarity index 100% rename from website/pages/sw/glossary.mdx rename to website/pages/sw/resources/glossary.mdx diff --git a/website/pages/sw/resources/release-notes/_meta.js b/website/pages/sw/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/sw/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx b/website/pages/sw/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/sw/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/sw/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/sw/release-notes/graphql-validations-migration-guide.mdx b/website/pages/sw/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/sw/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/sw/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/sw/resources/roles/_meta.js b/website/pages/sw/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/sw/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/network/curating.mdx b/website/pages/sw/resources/roles/curating.mdx similarity index 100% rename from website/pages/sw/network/curating.mdx rename to website/pages/sw/resources/roles/curating.mdx diff --git a/website/pages/sw/network/delegating.mdx b/website/pages/sw/resources/roles/delegating.mdx similarity index 100% rename from website/pages/sw/network/delegating.mdx rename to website/pages/sw/resources/roles/delegating.mdx diff --git a/website/pages/sw/network/tokenomics.mdx b/website/pages/sw/resources/tokenomics.mdx similarity index 100% rename from website/pages/sw/network/tokenomics.mdx rename to website/pages/sw/resources/tokenomics.mdx diff --git a/website/pages/sw/sps/_meta.js b/website/pages/sw/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/sw/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/sw/subgraphs/_meta.js b/website/pages/sw/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/sw/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/billing.mdx b/website/pages/sw/subgraphs/billing.mdx similarity index 100% rename from website/pages/sw/billing.mdx rename to website/pages/sw/subgraphs/billing.mdx diff --git a/website/pages/sw/subgraphs/cookbook/_meta.js b/website/pages/sw/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/sw/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/cookbook/arweave.mdx b/website/pages/sw/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/sw/cookbook/arweave.mdx rename to website/pages/sw/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/sw/cookbook/avoid-eth-calls.mdx b/website/pages/sw/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/sw/cookbook/avoid-eth-calls.mdx rename to website/pages/sw/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/sw/cookbook/cosmos.mdx b/website/pages/sw/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/sw/cookbook/cosmos.mdx rename to website/pages/sw/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/sw/cookbook/derivedfrom.mdx b/website/pages/sw/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/sw/cookbook/derivedfrom.mdx rename to website/pages/sw/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/sw/cookbook/enums.mdx b/website/pages/sw/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/sw/cookbook/enums.mdx rename to website/pages/sw/subgraphs/cookbook/enums.mdx diff --git a/website/pages/sw/cookbook/grafting-hotfix.mdx b/website/pages/sw/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/sw/cookbook/grafting-hotfix.mdx rename to website/pages/sw/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/sw/cookbook/grafting.mdx b/website/pages/sw/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/sw/cookbook/grafting.mdx rename to website/pages/sw/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/sw/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/sw/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/sw/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/sw/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/sw/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/sw/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/sw/cookbook/near.mdx b/website/pages/sw/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/sw/cookbook/near.mdx rename to website/pages/sw/subgraphs/cookbook/near.mdx diff --git a/website/pages/sw/cookbook/pruning.mdx b/website/pages/sw/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/sw/cookbook/pruning.mdx rename to website/pages/sw/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/sw/cookbook/subgraph-debug-forking.mdx b/website/pages/sw/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/sw/cookbook/subgraph-debug-forking.mdx rename to website/pages/sw/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/sw/cookbook/subgraph-uncrashable.mdx b/website/pages/sw/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/sw/cookbook/subgraph-uncrashable.mdx rename to website/pages/sw/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/sw/cookbook/substreams-powered-subgraphs.mdx b/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/sw/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/sw/cookbook/timeseries.mdx b/website/pages/sw/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/sw/cookbook/timeseries.mdx rename to website/pages/sw/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/sw/cookbook/transfer-to-the-graph.mdx b/website/pages/sw/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/sw/cookbook/transfer-to-the-graph.mdx rename to website/pages/sw/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/sw/subgraphs/developing/_meta.js b/website/pages/sw/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/sw/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/subgraphs/developing/creating/_meta.js b/website/pages/sw/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/sw/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/developing/creating-a-subgraph/advanced.mdx b/website/pages/sw/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/advanced.mdx rename to website/pages/sw/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/sw/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/sw/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/sw/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/sw/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/sw/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/sw/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/sw/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/sw/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/sw/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/sw/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/sw/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/sw/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/sw/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/sw/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/sw/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/sw/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/sw/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/sw/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/sw/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/sw/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/sw/subgraphs/developing/deploying/_meta.js b/website/pages/sw/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/sw/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/developing/deploying/multiple-networks.mdx b/website/pages/sw/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/sw/developing/deploying/multiple-networks.mdx rename to website/pages/sw/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/sw/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/sw/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/sw/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/sw/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/sw/developing/deploying/using-subgraph-studio.mdx b/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/sw/developing/deploying/using-subgraph-studio.mdx rename to website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/sw/developing/developer-faqs.mdx b/website/pages/sw/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/sw/developing/developer-faqs.mdx rename to website/pages/sw/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/sw/developing/developing.mdx b/website/pages/sw/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/sw/developing/developing.mdx rename to website/pages/sw/subgraphs/developing/introduction.mdx diff --git a/website/pages/sw/subgraphs/developing/managing/_meta.js b/website/pages/sw/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/sw/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/developing/managing/delete-a-subgraph.mdx b/website/pages/sw/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/sw/developing/managing/delete-a-subgraph.mdx rename to website/pages/sw/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/sw/developing/managing/transfer-a-subgraph.mdx b/website/pages/sw/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/sw/developing/managing/transfer-a-subgraph.mdx rename to website/pages/sw/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/sw/subgraphs/developing/publishing/_meta.js b/website/pages/sw/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/sw/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/developing/publishing/publishing-a-subgraph.mdx b/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/sw/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/sw/developing/subgraphs.mdx b/website/pages/sw/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/sw/developing/subgraphs.mdx rename to website/pages/sw/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/sw/explorer.mdx b/website/pages/sw/subgraphs/explorer.mdx similarity index 100% rename from website/pages/sw/explorer.mdx rename to website/pages/sw/subgraphs/explorer.mdx diff --git a/website/pages/sw/subgraphs/querying/_meta.js b/website/pages/sw/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/sw/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/querying/querying-best-practices.mdx b/website/pages/sw/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/sw/querying/querying-best-practices.mdx rename to website/pages/sw/subgraphs/querying/best-practices.mdx diff --git a/website/pages/sw/querying/distributed-systems.mdx b/website/pages/sw/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/sw/querying/distributed-systems.mdx rename to website/pages/sw/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/sw/querying/querying-from-an-application.mdx b/website/pages/sw/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/sw/querying/querying-from-an-application.mdx rename to website/pages/sw/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/sw/subgraphs/querying/graph-client/_meta.js b/website/pages/sw/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/sw/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/querying/graphql-api.mdx b/website/pages/sw/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/sw/querying/graphql-api.mdx rename to website/pages/sw/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/sw/querying/querying-the-graph.mdx b/website/pages/sw/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/sw/querying/querying-the-graph.mdx rename to website/pages/sw/subgraphs/querying/introduction.mdx diff --git a/website/pages/sw/querying/managing-api-keys.mdx b/website/pages/sw/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/sw/querying/managing-api-keys.mdx rename to website/pages/sw/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/sw/querying/querying-with-python.mdx b/website/pages/sw/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/sw/querying/querying-with-python.mdx rename to website/pages/sw/subgraphs/querying/python.mdx diff --git a/website/pages/sw/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/sw/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/sw/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/sw/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/sw/quick-start.mdx b/website/pages/sw/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/sw/quick-start.mdx rename to website/pages/sw/subgraphs/quick-start.mdx diff --git a/website/pages/sw/substreams/_meta.js b/website/pages/sw/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/sw/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/substreams.mdx b/website/pages/sw/substreams/introduction.mdx similarity index 100% rename from website/pages/sw/substreams.mdx rename to website/pages/sw/substreams/introduction.mdx diff --git a/website/pages/sw/substreams/sps/_meta.js b/website/pages/sw/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/sw/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/sw/sps/introduction.mdx b/website/pages/sw/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/sw/sps/introduction.mdx rename to website/pages/sw/substreams/sps/introduction.mdx diff --git a/website/pages/sw/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/sw/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/sw/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/sw/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/sw/sps/triggers-example.mdx b/website/pages/sw/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/sw/sps/triggers-example.mdx rename to website/pages/sw/substreams/sps/triggers-example.mdx diff --git a/website/pages/sw/sps/triggers.mdx b/website/pages/sw/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/sw/sps/triggers.mdx rename to website/pages/sw/substreams/sps/triggers.mdx diff --git a/website/pages/tr/cookbook/_meta.js b/website/pages/tr/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/tr/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/_meta.js b/website/pages/tr/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/tr/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/creating-a-subgraph/_meta.js b/website/pages/tr/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/tr/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/tr/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/deploying/_meta.js b/website/pages/tr/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/tr/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/managing/_meta.js b/website/pages/tr/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/tr/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/developing/publishing/_meta.js b/website/pages/tr/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/tr/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/indexer-tooling/_meta.js b/website/pages/tr/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/tr/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/indexing/_meta.js b/website/pages/tr/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/tr/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/chain-integration-overview.mdx b/website/pages/tr/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/tr/chain-integration-overview.mdx rename to website/pages/tr/indexing/chain-integration-overview.mdx diff --git a/website/pages/tr/indexing.mdx b/website/pages/tr/indexing/introduction.mdx similarity index 100% rename from website/pages/tr/indexing.mdx rename to website/pages/tr/indexing/introduction.mdx diff --git a/website/pages/tr/new-chain-integration.mdx b/website/pages/tr/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/tr/new-chain-integration.mdx rename to website/pages/tr/indexing/new-chain-integration.mdx diff --git a/website/pages/tr/supported-network-requirements.mdx b/website/pages/tr/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/tr/supported-network-requirements.mdx rename to website/pages/tr/indexing/supported-network-requirements.mdx diff --git a/website/pages/tr/tap.mdx b/website/pages/tr/indexing/tap.mdx similarity index 100% rename from website/pages/tr/tap.mdx rename to website/pages/tr/indexing/tap.mdx diff --git a/website/pages/tr/indexing/tooling/_meta.js b/website/pages/tr/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/tr/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/indexer-tooling/firehose.mdx b/website/pages/tr/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/tr/indexer-tooling/firehose.mdx rename to website/pages/tr/indexing/tooling/firehose.mdx diff --git a/website/pages/tr/indexer-tooling/graphcast.mdx b/website/pages/tr/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/tr/indexer-tooling/graphcast.mdx rename to website/pages/tr/indexing/tooling/graphcast.mdx diff --git a/website/pages/tr/indexer-tooling/operating-graph-node.mdx b/website/pages/tr/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/tr/indexer-tooling/operating-graph-node.mdx rename to website/pages/tr/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/tr/network/_meta.js b/website/pages/tr/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/tr/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/network/overview.mdx b/website/pages/tr/network/overview.mdx deleted file mode 100644 index 9b46dfc882bf..000000000000 --- a/website/pages/tr/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Ayrıntılar - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/tr/querying/_meta.js b/website/pages/tr/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/tr/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/querying/graph-client/_meta.js b/website/pages/tr/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/tr/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/release-notes/_meta.js b/website/pages/tr/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/tr/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/resources/_meta.js b/website/pages/tr/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/tr/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/network/benefits.mdx b/website/pages/tr/resources/benefits.mdx similarity index 100% rename from website/pages/tr/network/benefits.mdx rename to website/pages/tr/resources/benefits.mdx diff --git a/website/pages/tr/glossary.mdx b/website/pages/tr/resources/glossary.mdx similarity index 100% rename from website/pages/tr/glossary.mdx rename to website/pages/tr/resources/glossary.mdx diff --git a/website/pages/tr/resources/release-notes/_meta.js b/website/pages/tr/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/tr/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/tr/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/tr/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/tr/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/tr/release-notes/graphql-validations-migration-guide.mdx b/website/pages/tr/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/tr/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/tr/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/tr/resources/roles/_meta.js b/website/pages/tr/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/tr/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/network/curating.mdx b/website/pages/tr/resources/roles/curating.mdx similarity index 100% rename from website/pages/tr/network/curating.mdx rename to website/pages/tr/resources/roles/curating.mdx diff --git a/website/pages/tr/network/delegating.mdx b/website/pages/tr/resources/roles/delegating.mdx similarity index 100% rename from website/pages/tr/network/delegating.mdx rename to website/pages/tr/resources/roles/delegating.mdx diff --git a/website/pages/tr/network/tokenomics.mdx b/website/pages/tr/resources/tokenomics.mdx similarity index 100% rename from website/pages/tr/network/tokenomics.mdx rename to website/pages/tr/resources/tokenomics.mdx diff --git a/website/pages/tr/sps/_meta.js b/website/pages/tr/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/tr/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/tr/subgraphs/_meta.js b/website/pages/tr/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/tr/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/billing.mdx b/website/pages/tr/subgraphs/billing.mdx similarity index 100% rename from website/pages/tr/billing.mdx rename to website/pages/tr/subgraphs/billing.mdx diff --git a/website/pages/tr/subgraphs/cookbook/_meta.js b/website/pages/tr/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/tr/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/cookbook/arweave.mdx b/website/pages/tr/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/tr/cookbook/arweave.mdx rename to website/pages/tr/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/tr/cookbook/avoid-eth-calls.mdx b/website/pages/tr/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/tr/cookbook/avoid-eth-calls.mdx rename to website/pages/tr/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/tr/cookbook/cosmos.mdx b/website/pages/tr/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/tr/cookbook/cosmos.mdx rename to website/pages/tr/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/tr/cookbook/derivedfrom.mdx b/website/pages/tr/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/tr/cookbook/derivedfrom.mdx rename to website/pages/tr/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/tr/cookbook/enums.mdx b/website/pages/tr/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/tr/cookbook/enums.mdx rename to website/pages/tr/subgraphs/cookbook/enums.mdx diff --git a/website/pages/tr/cookbook/grafting-hotfix.mdx b/website/pages/tr/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/tr/cookbook/grafting-hotfix.mdx rename to website/pages/tr/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/tr/cookbook/grafting.mdx b/website/pages/tr/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/tr/cookbook/grafting.mdx rename to website/pages/tr/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/tr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/tr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/tr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/tr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/tr/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/tr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/tr/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/tr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/tr/cookbook/near.mdx b/website/pages/tr/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/tr/cookbook/near.mdx rename to website/pages/tr/subgraphs/cookbook/near.mdx diff --git a/website/pages/tr/cookbook/pruning.mdx b/website/pages/tr/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/tr/cookbook/pruning.mdx rename to website/pages/tr/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/tr/cookbook/subgraph-debug-forking.mdx b/website/pages/tr/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/tr/cookbook/subgraph-debug-forking.mdx rename to website/pages/tr/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/tr/cookbook/subgraph-uncrashable.mdx b/website/pages/tr/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/tr/cookbook/subgraph-uncrashable.mdx rename to website/pages/tr/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/tr/cookbook/substreams-powered-subgraphs.mdx b/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/tr/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/tr/cookbook/timeseries.mdx b/website/pages/tr/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/tr/cookbook/timeseries.mdx rename to website/pages/tr/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/tr/cookbook/transfer-to-the-graph.mdx b/website/pages/tr/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/tr/cookbook/transfer-to-the-graph.mdx rename to website/pages/tr/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/tr/subgraphs/developing/_meta.js b/website/pages/tr/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/tr/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/subgraphs/developing/creating/_meta.js b/website/pages/tr/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/tr/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/developing/creating-a-subgraph/advanced.mdx b/website/pages/tr/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/advanced.mdx rename to website/pages/tr/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/tr/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/tr/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/tr/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/tr/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/tr/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/tr/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/tr/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/tr/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/tr/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/tr/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/tr/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/tr/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/tr/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/tr/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/tr/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/tr/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/tr/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/tr/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/tr/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/tr/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/tr/subgraphs/developing/deploying/_meta.js b/website/pages/tr/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/tr/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/developing/deploying/multiple-networks.mdx b/website/pages/tr/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/tr/developing/deploying/multiple-networks.mdx rename to website/pages/tr/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/tr/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/tr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/tr/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/tr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/tr/developing/deploying/using-subgraph-studio.mdx b/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/tr/developing/deploying/using-subgraph-studio.mdx rename to website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/tr/developing/developer-faqs.mdx b/website/pages/tr/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/tr/developing/developer-faqs.mdx rename to website/pages/tr/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/tr/developing/developing.mdx b/website/pages/tr/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/tr/developing/developing.mdx rename to website/pages/tr/subgraphs/developing/introduction.mdx diff --git a/website/pages/tr/subgraphs/developing/managing/_meta.js b/website/pages/tr/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/tr/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/developing/managing/delete-a-subgraph.mdx b/website/pages/tr/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/tr/developing/managing/delete-a-subgraph.mdx rename to website/pages/tr/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/tr/developing/managing/transfer-a-subgraph.mdx b/website/pages/tr/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/tr/developing/managing/transfer-a-subgraph.mdx rename to website/pages/tr/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/tr/subgraphs/developing/publishing/_meta.js b/website/pages/tr/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/tr/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/developing/publishing/publishing-a-subgraph.mdx b/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/tr/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/tr/developing/subgraphs.mdx b/website/pages/tr/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/tr/developing/subgraphs.mdx rename to website/pages/tr/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/tr/explorer.mdx b/website/pages/tr/subgraphs/explorer.mdx similarity index 100% rename from website/pages/tr/explorer.mdx rename to website/pages/tr/subgraphs/explorer.mdx diff --git a/website/pages/tr/subgraphs/querying/_meta.js b/website/pages/tr/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/tr/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/querying/querying-best-practices.mdx b/website/pages/tr/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/tr/querying/querying-best-practices.mdx rename to website/pages/tr/subgraphs/querying/best-practices.mdx diff --git a/website/pages/tr/querying/distributed-systems.mdx b/website/pages/tr/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/tr/querying/distributed-systems.mdx rename to website/pages/tr/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/tr/querying/querying-from-an-application.mdx b/website/pages/tr/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/tr/querying/querying-from-an-application.mdx rename to website/pages/tr/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/tr/subgraphs/querying/graph-client/_meta.js b/website/pages/tr/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/tr/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/querying/graphql-api.mdx b/website/pages/tr/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/tr/querying/graphql-api.mdx rename to website/pages/tr/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/tr/querying/querying-the-graph.mdx b/website/pages/tr/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/tr/querying/querying-the-graph.mdx rename to website/pages/tr/subgraphs/querying/introduction.mdx diff --git a/website/pages/tr/querying/managing-api-keys.mdx b/website/pages/tr/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/tr/querying/managing-api-keys.mdx rename to website/pages/tr/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/tr/querying/querying-with-python.mdx b/website/pages/tr/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/tr/querying/querying-with-python.mdx rename to website/pages/tr/subgraphs/querying/python.mdx diff --git a/website/pages/tr/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/tr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/tr/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/tr/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/tr/quick-start.mdx b/website/pages/tr/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/tr/quick-start.mdx rename to website/pages/tr/subgraphs/quick-start.mdx diff --git a/website/pages/tr/substreams/_meta.js b/website/pages/tr/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/tr/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/substreams.mdx b/website/pages/tr/substreams/introduction.mdx similarity index 100% rename from website/pages/tr/substreams.mdx rename to website/pages/tr/substreams/introduction.mdx diff --git a/website/pages/tr/substreams/sps/_meta.js b/website/pages/tr/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/tr/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/tr/sps/introduction.mdx b/website/pages/tr/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/tr/sps/introduction.mdx rename to website/pages/tr/substreams/sps/introduction.mdx diff --git a/website/pages/tr/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/tr/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/tr/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/tr/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/tr/sps/triggers-example.mdx b/website/pages/tr/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/tr/sps/triggers-example.mdx rename to website/pages/tr/substreams/sps/triggers-example.mdx diff --git a/website/pages/tr/sps/triggers.mdx b/website/pages/tr/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/tr/sps/triggers.mdx rename to website/pages/tr/substreams/sps/triggers.mdx diff --git a/website/pages/uk/cookbook/_meta.js b/website/pages/uk/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/uk/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/_meta.js b/website/pages/uk/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/uk/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/creating-a-subgraph/_meta.js b/website/pages/uk/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/uk/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/uk/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/deploying/_meta.js b/website/pages/uk/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/uk/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/managing/_meta.js b/website/pages/uk/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/uk/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/developing/publishing/_meta.js b/website/pages/uk/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/uk/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/indexer-tooling/_meta.js b/website/pages/uk/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/uk/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/indexing/_meta.js b/website/pages/uk/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/uk/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/chain-integration-overview.mdx b/website/pages/uk/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/uk/chain-integration-overview.mdx rename to website/pages/uk/indexing/chain-integration-overview.mdx diff --git a/website/pages/uk/indexing.mdx b/website/pages/uk/indexing/introduction.mdx similarity index 100% rename from website/pages/uk/indexing.mdx rename to website/pages/uk/indexing/introduction.mdx diff --git a/website/pages/uk/new-chain-integration.mdx b/website/pages/uk/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/uk/new-chain-integration.mdx rename to website/pages/uk/indexing/new-chain-integration.mdx diff --git a/website/pages/uk/supported-network-requirements.mdx b/website/pages/uk/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/uk/supported-network-requirements.mdx rename to website/pages/uk/indexing/supported-network-requirements.mdx diff --git a/website/pages/uk/tap.mdx b/website/pages/uk/indexing/tap.mdx similarity index 100% rename from website/pages/uk/tap.mdx rename to website/pages/uk/indexing/tap.mdx diff --git a/website/pages/uk/indexing/tooling/_meta.js b/website/pages/uk/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/uk/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/indexer-tooling/firehose.mdx b/website/pages/uk/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/uk/indexer-tooling/firehose.mdx rename to website/pages/uk/indexing/tooling/firehose.mdx diff --git a/website/pages/uk/indexer-tooling/graphcast.mdx b/website/pages/uk/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/uk/indexer-tooling/graphcast.mdx rename to website/pages/uk/indexing/tooling/graphcast.mdx diff --git a/website/pages/uk/indexer-tooling/operating-graph-node.mdx b/website/pages/uk/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/uk/indexer-tooling/operating-graph-node.mdx rename to website/pages/uk/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/uk/network/_meta.js b/website/pages/uk/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/uk/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/network/overview.mdx b/website/pages/uk/network/overview.mdx deleted file mode 100644 index 60c044309f09..000000000000 --- a/website/pages/uk/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Загальний огляд мережі ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Економіка токенів](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/uk/querying/_meta.js b/website/pages/uk/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/uk/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/querying/graph-client/_meta.js b/website/pages/uk/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/uk/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/release-notes/_meta.js b/website/pages/uk/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/uk/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/resources/_meta.js b/website/pages/uk/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/uk/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/network/benefits.mdx b/website/pages/uk/resources/benefits.mdx similarity index 100% rename from website/pages/uk/network/benefits.mdx rename to website/pages/uk/resources/benefits.mdx diff --git a/website/pages/uk/glossary.mdx b/website/pages/uk/resources/glossary.mdx similarity index 100% rename from website/pages/uk/glossary.mdx rename to website/pages/uk/resources/glossary.mdx diff --git a/website/pages/uk/resources/release-notes/_meta.js b/website/pages/uk/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/uk/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx b/website/pages/uk/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/uk/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/uk/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/uk/release-notes/graphql-validations-migration-guide.mdx b/website/pages/uk/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/uk/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/uk/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/uk/resources/roles/_meta.js b/website/pages/uk/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/uk/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/network/curating.mdx b/website/pages/uk/resources/roles/curating.mdx similarity index 100% rename from website/pages/uk/network/curating.mdx rename to website/pages/uk/resources/roles/curating.mdx diff --git a/website/pages/uk/network/delegating.mdx b/website/pages/uk/resources/roles/delegating.mdx similarity index 100% rename from website/pages/uk/network/delegating.mdx rename to website/pages/uk/resources/roles/delegating.mdx diff --git a/website/pages/uk/network/tokenomics.mdx b/website/pages/uk/resources/tokenomics.mdx similarity index 100% rename from website/pages/uk/network/tokenomics.mdx rename to website/pages/uk/resources/tokenomics.mdx diff --git a/website/pages/uk/sps/_meta.js b/website/pages/uk/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/uk/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/uk/subgraphs/_meta.js b/website/pages/uk/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/uk/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/billing.mdx b/website/pages/uk/subgraphs/billing.mdx similarity index 100% rename from website/pages/uk/billing.mdx rename to website/pages/uk/subgraphs/billing.mdx diff --git a/website/pages/uk/subgraphs/cookbook/_meta.js b/website/pages/uk/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/uk/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/cookbook/arweave.mdx b/website/pages/uk/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/uk/cookbook/arweave.mdx rename to website/pages/uk/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/uk/cookbook/avoid-eth-calls.mdx b/website/pages/uk/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/uk/cookbook/avoid-eth-calls.mdx rename to website/pages/uk/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/uk/cookbook/cosmos.mdx b/website/pages/uk/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/uk/cookbook/cosmos.mdx rename to website/pages/uk/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/uk/cookbook/derivedfrom.mdx b/website/pages/uk/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/uk/cookbook/derivedfrom.mdx rename to website/pages/uk/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/uk/cookbook/enums.mdx b/website/pages/uk/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/uk/cookbook/enums.mdx rename to website/pages/uk/subgraphs/cookbook/enums.mdx diff --git a/website/pages/uk/cookbook/grafting-hotfix.mdx b/website/pages/uk/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/uk/cookbook/grafting-hotfix.mdx rename to website/pages/uk/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/uk/cookbook/grafting.mdx b/website/pages/uk/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/uk/cookbook/grafting.mdx rename to website/pages/uk/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/uk/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/uk/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/uk/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/uk/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/uk/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/uk/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/uk/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/uk/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/uk/cookbook/near.mdx b/website/pages/uk/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/uk/cookbook/near.mdx rename to website/pages/uk/subgraphs/cookbook/near.mdx diff --git a/website/pages/uk/cookbook/pruning.mdx b/website/pages/uk/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/uk/cookbook/pruning.mdx rename to website/pages/uk/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/uk/cookbook/subgraph-debug-forking.mdx b/website/pages/uk/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/uk/cookbook/subgraph-debug-forking.mdx rename to website/pages/uk/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/uk/cookbook/subgraph-uncrashable.mdx b/website/pages/uk/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/uk/cookbook/subgraph-uncrashable.mdx rename to website/pages/uk/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/uk/cookbook/substreams-powered-subgraphs.mdx b/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/uk/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/uk/cookbook/timeseries.mdx b/website/pages/uk/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/uk/cookbook/timeseries.mdx rename to website/pages/uk/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/uk/cookbook/transfer-to-the-graph.mdx b/website/pages/uk/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/uk/cookbook/transfer-to-the-graph.mdx rename to website/pages/uk/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/uk/subgraphs/developing/_meta.js b/website/pages/uk/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/uk/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/subgraphs/developing/creating/_meta.js b/website/pages/uk/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/uk/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/developing/creating-a-subgraph/advanced.mdx b/website/pages/uk/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/advanced.mdx rename to website/pages/uk/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/uk/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/uk/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/uk/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/uk/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/uk/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/uk/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/uk/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/uk/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/uk/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/uk/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/uk/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/uk/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/uk/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/uk/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/uk/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/uk/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/uk/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/uk/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/uk/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/uk/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/uk/subgraphs/developing/deploying/_meta.js b/website/pages/uk/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/uk/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/developing/deploying/multiple-networks.mdx b/website/pages/uk/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/uk/developing/deploying/multiple-networks.mdx rename to website/pages/uk/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/uk/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/uk/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/uk/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/uk/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/uk/developing/deploying/using-subgraph-studio.mdx b/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/uk/developing/deploying/using-subgraph-studio.mdx rename to website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/uk/developing/developer-faqs.mdx b/website/pages/uk/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/uk/developing/developer-faqs.mdx rename to website/pages/uk/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/uk/developing/developing.mdx b/website/pages/uk/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/uk/developing/developing.mdx rename to website/pages/uk/subgraphs/developing/introduction.mdx diff --git a/website/pages/uk/subgraphs/developing/managing/_meta.js b/website/pages/uk/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/uk/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/developing/managing/delete-a-subgraph.mdx b/website/pages/uk/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/uk/developing/managing/delete-a-subgraph.mdx rename to website/pages/uk/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/uk/developing/managing/transfer-a-subgraph.mdx b/website/pages/uk/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/uk/developing/managing/transfer-a-subgraph.mdx rename to website/pages/uk/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/uk/subgraphs/developing/publishing/_meta.js b/website/pages/uk/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/uk/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/developing/publishing/publishing-a-subgraph.mdx b/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/uk/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/uk/developing/subgraphs.mdx b/website/pages/uk/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/uk/developing/subgraphs.mdx rename to website/pages/uk/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/uk/explorer.mdx b/website/pages/uk/subgraphs/explorer.mdx similarity index 100% rename from website/pages/uk/explorer.mdx rename to website/pages/uk/subgraphs/explorer.mdx diff --git a/website/pages/uk/subgraphs/querying/_meta.js b/website/pages/uk/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/uk/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/querying/querying-best-practices.mdx b/website/pages/uk/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/uk/querying/querying-best-practices.mdx rename to website/pages/uk/subgraphs/querying/best-practices.mdx diff --git a/website/pages/uk/querying/distributed-systems.mdx b/website/pages/uk/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/uk/querying/distributed-systems.mdx rename to website/pages/uk/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/uk/querying/querying-from-an-application.mdx b/website/pages/uk/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/uk/querying/querying-from-an-application.mdx rename to website/pages/uk/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/uk/subgraphs/querying/graph-client/_meta.js b/website/pages/uk/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/uk/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/querying/graphql-api.mdx b/website/pages/uk/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/uk/querying/graphql-api.mdx rename to website/pages/uk/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/uk/querying/querying-the-graph.mdx b/website/pages/uk/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/uk/querying/querying-the-graph.mdx rename to website/pages/uk/subgraphs/querying/introduction.mdx diff --git a/website/pages/uk/querying/managing-api-keys.mdx b/website/pages/uk/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/uk/querying/managing-api-keys.mdx rename to website/pages/uk/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/uk/querying/querying-with-python.mdx b/website/pages/uk/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/uk/querying/querying-with-python.mdx rename to website/pages/uk/subgraphs/querying/python.mdx diff --git a/website/pages/uk/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/uk/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/uk/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/uk/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/uk/quick-start.mdx b/website/pages/uk/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/uk/quick-start.mdx rename to website/pages/uk/subgraphs/quick-start.mdx diff --git a/website/pages/uk/substreams/_meta.js b/website/pages/uk/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/uk/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/substreams.mdx b/website/pages/uk/substreams/introduction.mdx similarity index 100% rename from website/pages/uk/substreams.mdx rename to website/pages/uk/substreams/introduction.mdx diff --git a/website/pages/uk/substreams/sps/_meta.js b/website/pages/uk/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/uk/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/uk/sps/introduction.mdx b/website/pages/uk/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/uk/sps/introduction.mdx rename to website/pages/uk/substreams/sps/introduction.mdx diff --git a/website/pages/uk/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/uk/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/uk/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/uk/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/uk/sps/triggers-example.mdx b/website/pages/uk/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/uk/sps/triggers-example.mdx rename to website/pages/uk/substreams/sps/triggers-example.mdx diff --git a/website/pages/uk/sps/triggers.mdx b/website/pages/uk/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/uk/sps/triggers.mdx rename to website/pages/uk/substreams/sps/triggers.mdx diff --git a/website/pages/ur/cookbook/_meta.js b/website/pages/ur/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/ur/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/_meta.js b/website/pages/ur/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/ur/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/creating-a-subgraph/_meta.js b/website/pages/ur/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/ur/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/ur/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/deploying/_meta.js b/website/pages/ur/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/ur/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/managing/_meta.js b/website/pages/ur/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/ur/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/developing/publishing/_meta.js b/website/pages/ur/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/ur/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/indexer-tooling/_meta.js b/website/pages/ur/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/ur/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/indexing/_meta.js b/website/pages/ur/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/ur/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/chain-integration-overview.mdx b/website/pages/ur/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/ur/chain-integration-overview.mdx rename to website/pages/ur/indexing/chain-integration-overview.mdx diff --git a/website/pages/ur/indexing.mdx b/website/pages/ur/indexing/introduction.mdx similarity index 100% rename from website/pages/ur/indexing.mdx rename to website/pages/ur/indexing/introduction.mdx diff --git a/website/pages/ur/new-chain-integration.mdx b/website/pages/ur/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/ur/new-chain-integration.mdx rename to website/pages/ur/indexing/new-chain-integration.mdx diff --git a/website/pages/ur/supported-network-requirements.mdx b/website/pages/ur/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/ur/supported-network-requirements.mdx rename to website/pages/ur/indexing/supported-network-requirements.mdx diff --git a/website/pages/ur/tap.mdx b/website/pages/ur/indexing/tap.mdx similarity index 100% rename from website/pages/ur/tap.mdx rename to website/pages/ur/indexing/tap.mdx diff --git a/website/pages/ur/indexing/tooling/_meta.js b/website/pages/ur/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/ur/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/indexer-tooling/firehose.mdx b/website/pages/ur/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/ur/indexer-tooling/firehose.mdx rename to website/pages/ur/indexing/tooling/firehose.mdx diff --git a/website/pages/ur/indexer-tooling/graphcast.mdx b/website/pages/ur/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/ur/indexer-tooling/graphcast.mdx rename to website/pages/ur/indexing/tooling/graphcast.mdx diff --git a/website/pages/ur/indexer-tooling/operating-graph-node.mdx b/website/pages/ur/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/ur/indexer-tooling/operating-graph-node.mdx rename to website/pages/ur/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/ur/network/_meta.js b/website/pages/ur/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/ur/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/network/overview.mdx b/website/pages/ur/network/overview.mdx deleted file mode 100644 index 4ad830a6a841..000000000000 --- a/website/pages/ur/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: نیٹ ورک کا جائزہ ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![ٹوکن اکنامکس](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/ur/querying/_meta.js b/website/pages/ur/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/ur/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/querying/graph-client/_meta.js b/website/pages/ur/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/ur/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/release-notes/_meta.js b/website/pages/ur/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/ur/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/resources/_meta.js b/website/pages/ur/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/ur/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/network/benefits.mdx b/website/pages/ur/resources/benefits.mdx similarity index 100% rename from website/pages/ur/network/benefits.mdx rename to website/pages/ur/resources/benefits.mdx diff --git a/website/pages/ur/glossary.mdx b/website/pages/ur/resources/glossary.mdx similarity index 100% rename from website/pages/ur/glossary.mdx rename to website/pages/ur/resources/glossary.mdx diff --git a/website/pages/ur/resources/release-notes/_meta.js b/website/pages/ur/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/ur/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ur/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/ur/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/ur/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ur/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/ur/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/ur/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/ur/resources/roles/_meta.js b/website/pages/ur/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/ur/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/network/curating.mdx b/website/pages/ur/resources/roles/curating.mdx similarity index 100% rename from website/pages/ur/network/curating.mdx rename to website/pages/ur/resources/roles/curating.mdx diff --git a/website/pages/ur/network/delegating.mdx b/website/pages/ur/resources/roles/delegating.mdx similarity index 100% rename from website/pages/ur/network/delegating.mdx rename to website/pages/ur/resources/roles/delegating.mdx diff --git a/website/pages/ur/network/tokenomics.mdx b/website/pages/ur/resources/tokenomics.mdx similarity index 100% rename from website/pages/ur/network/tokenomics.mdx rename to website/pages/ur/resources/tokenomics.mdx diff --git a/website/pages/ur/sps/_meta.js b/website/pages/ur/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/ur/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/ur/subgraphs/_meta.js b/website/pages/ur/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/ur/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/billing.mdx b/website/pages/ur/subgraphs/billing.mdx similarity index 100% rename from website/pages/ur/billing.mdx rename to website/pages/ur/subgraphs/billing.mdx diff --git a/website/pages/ur/subgraphs/cookbook/_meta.js b/website/pages/ur/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/ur/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/cookbook/arweave.mdx b/website/pages/ur/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/ur/cookbook/arweave.mdx rename to website/pages/ur/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/ur/cookbook/avoid-eth-calls.mdx b/website/pages/ur/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/ur/cookbook/avoid-eth-calls.mdx rename to website/pages/ur/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/ur/cookbook/cosmos.mdx b/website/pages/ur/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/ur/cookbook/cosmos.mdx rename to website/pages/ur/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/ur/cookbook/derivedfrom.mdx b/website/pages/ur/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/ur/cookbook/derivedfrom.mdx rename to website/pages/ur/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/ur/cookbook/enums.mdx b/website/pages/ur/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/ur/cookbook/enums.mdx rename to website/pages/ur/subgraphs/cookbook/enums.mdx diff --git a/website/pages/ur/cookbook/grafting-hotfix.mdx b/website/pages/ur/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/ur/cookbook/grafting-hotfix.mdx rename to website/pages/ur/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/ur/cookbook/grafting.mdx b/website/pages/ur/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/ur/cookbook/grafting.mdx rename to website/pages/ur/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/ur/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ur/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/ur/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ur/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/ur/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ur/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/ur/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/ur/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/ur/cookbook/near.mdx b/website/pages/ur/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/ur/cookbook/near.mdx rename to website/pages/ur/subgraphs/cookbook/near.mdx diff --git a/website/pages/ur/cookbook/pruning.mdx b/website/pages/ur/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/ur/cookbook/pruning.mdx rename to website/pages/ur/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/ur/cookbook/subgraph-debug-forking.mdx b/website/pages/ur/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/ur/cookbook/subgraph-debug-forking.mdx rename to website/pages/ur/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/ur/cookbook/subgraph-uncrashable.mdx b/website/pages/ur/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/ur/cookbook/subgraph-uncrashable.mdx rename to website/pages/ur/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/ur/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/ur/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/ur/cookbook/timeseries.mdx b/website/pages/ur/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/ur/cookbook/timeseries.mdx rename to website/pages/ur/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/ur/cookbook/transfer-to-the-graph.mdx b/website/pages/ur/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/ur/cookbook/transfer-to-the-graph.mdx rename to website/pages/ur/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/ur/subgraphs/developing/_meta.js b/website/pages/ur/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/ur/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/subgraphs/developing/creating/_meta.js b/website/pages/ur/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/ur/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/developing/creating-a-subgraph/advanced.mdx b/website/pages/ur/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/advanced.mdx rename to website/pages/ur/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/ur/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ur/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/ur/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/ur/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/ur/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/ur/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/ur/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/ur/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/ur/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/ur/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/ur/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/ur/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/ur/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ur/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/ur/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/ur/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ur/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/ur/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/ur/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/ur/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/ur/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/ur/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/ur/subgraphs/developing/deploying/_meta.js b/website/pages/ur/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/ur/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/developing/deploying/multiple-networks.mdx b/website/pages/ur/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/ur/developing/deploying/multiple-networks.mdx rename to website/pages/ur/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/ur/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ur/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/ur/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ur/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/ur/developing/deploying/using-subgraph-studio.mdx b/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/ur/developing/deploying/using-subgraph-studio.mdx rename to website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/ur/developing/developer-faqs.mdx b/website/pages/ur/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/ur/developing/developer-faqs.mdx rename to website/pages/ur/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/ur/developing/developing.mdx b/website/pages/ur/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/ur/developing/developing.mdx rename to website/pages/ur/subgraphs/developing/introduction.mdx diff --git a/website/pages/ur/subgraphs/developing/managing/_meta.js b/website/pages/ur/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/ur/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/developing/managing/delete-a-subgraph.mdx b/website/pages/ur/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/ur/developing/managing/delete-a-subgraph.mdx rename to website/pages/ur/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/ur/developing/managing/transfer-a-subgraph.mdx b/website/pages/ur/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/ur/developing/managing/transfer-a-subgraph.mdx rename to website/pages/ur/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/ur/subgraphs/developing/publishing/_meta.js b/website/pages/ur/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/ur/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/ur/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/ur/developing/subgraphs.mdx b/website/pages/ur/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/ur/developing/subgraphs.mdx rename to website/pages/ur/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/ur/explorer.mdx b/website/pages/ur/subgraphs/explorer.mdx similarity index 100% rename from website/pages/ur/explorer.mdx rename to website/pages/ur/subgraphs/explorer.mdx diff --git a/website/pages/ur/subgraphs/querying/_meta.js b/website/pages/ur/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/ur/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/querying/querying-best-practices.mdx b/website/pages/ur/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/ur/querying/querying-best-practices.mdx rename to website/pages/ur/subgraphs/querying/best-practices.mdx diff --git a/website/pages/ur/querying/distributed-systems.mdx b/website/pages/ur/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/ur/querying/distributed-systems.mdx rename to website/pages/ur/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/ur/querying/querying-from-an-application.mdx b/website/pages/ur/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/ur/querying/querying-from-an-application.mdx rename to website/pages/ur/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/ur/subgraphs/querying/graph-client/_meta.js b/website/pages/ur/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/ur/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/querying/graphql-api.mdx b/website/pages/ur/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/ur/querying/graphql-api.mdx rename to website/pages/ur/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/ur/querying/querying-the-graph.mdx b/website/pages/ur/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/ur/querying/querying-the-graph.mdx rename to website/pages/ur/subgraphs/querying/introduction.mdx diff --git a/website/pages/ur/querying/managing-api-keys.mdx b/website/pages/ur/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/ur/querying/managing-api-keys.mdx rename to website/pages/ur/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/ur/querying/querying-with-python.mdx b/website/pages/ur/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/ur/querying/querying-with-python.mdx rename to website/pages/ur/subgraphs/querying/python.mdx diff --git a/website/pages/ur/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/ur/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/ur/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/ur/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/ur/quick-start.mdx b/website/pages/ur/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/ur/quick-start.mdx rename to website/pages/ur/subgraphs/quick-start.mdx diff --git a/website/pages/ur/substreams/_meta.js b/website/pages/ur/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/ur/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/substreams.mdx b/website/pages/ur/substreams/introduction.mdx similarity index 100% rename from website/pages/ur/substreams.mdx rename to website/pages/ur/substreams/introduction.mdx diff --git a/website/pages/ur/substreams/sps/_meta.js b/website/pages/ur/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/ur/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/ur/sps/introduction.mdx b/website/pages/ur/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/ur/sps/introduction.mdx rename to website/pages/ur/substreams/sps/introduction.mdx diff --git a/website/pages/ur/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ur/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/ur/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ur/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/ur/sps/triggers-example.mdx b/website/pages/ur/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/ur/sps/triggers-example.mdx rename to website/pages/ur/substreams/sps/triggers-example.mdx diff --git a/website/pages/ur/sps/triggers.mdx b/website/pages/ur/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/ur/sps/triggers.mdx rename to website/pages/ur/substreams/sps/triggers.mdx diff --git a/website/pages/vi/cookbook/_meta.js b/website/pages/vi/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/vi/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/_meta.js b/website/pages/vi/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/vi/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/creating-a-subgraph/_meta.js b/website/pages/vi/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/vi/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/vi/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/deploying/_meta.js b/website/pages/vi/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/vi/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/managing/_meta.js b/website/pages/vi/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/vi/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/developing/publishing/_meta.js b/website/pages/vi/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/vi/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/indexer-tooling/_meta.js b/website/pages/vi/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/vi/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/indexing/_meta.js b/website/pages/vi/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/vi/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/chain-integration-overview.mdx b/website/pages/vi/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/vi/chain-integration-overview.mdx rename to website/pages/vi/indexing/chain-integration-overview.mdx diff --git a/website/pages/vi/indexing.mdx b/website/pages/vi/indexing/introduction.mdx similarity index 100% rename from website/pages/vi/indexing.mdx rename to website/pages/vi/indexing/introduction.mdx diff --git a/website/pages/vi/new-chain-integration.mdx b/website/pages/vi/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/vi/new-chain-integration.mdx rename to website/pages/vi/indexing/new-chain-integration.mdx diff --git a/website/pages/vi/supported-network-requirements.mdx b/website/pages/vi/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/vi/supported-network-requirements.mdx rename to website/pages/vi/indexing/supported-network-requirements.mdx diff --git a/website/pages/vi/tap.mdx b/website/pages/vi/indexing/tap.mdx similarity index 100% rename from website/pages/vi/tap.mdx rename to website/pages/vi/indexing/tap.mdx diff --git a/website/pages/vi/indexing/tooling/_meta.js b/website/pages/vi/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/vi/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/indexer-tooling/firehose.mdx b/website/pages/vi/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/vi/indexer-tooling/firehose.mdx rename to website/pages/vi/indexing/tooling/firehose.mdx diff --git a/website/pages/vi/indexer-tooling/graphcast.mdx b/website/pages/vi/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/vi/indexer-tooling/graphcast.mdx rename to website/pages/vi/indexing/tooling/graphcast.mdx diff --git a/website/pages/vi/indexer-tooling/operating-graph-node.mdx b/website/pages/vi/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/vi/indexer-tooling/operating-graph-node.mdx rename to website/pages/vi/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/vi/network/_meta.js b/website/pages/vi/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/vi/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/network/overview.mdx b/website/pages/vi/network/overview.mdx deleted file mode 100644 index 0779d9a6cb00..000000000000 --- a/website/pages/vi/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: Network Overview ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![Token Economics](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/vi/querying/_meta.js b/website/pages/vi/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/vi/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/querying/graph-client/_meta.js b/website/pages/vi/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/vi/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/release-notes/_meta.js b/website/pages/vi/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/vi/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/resources/_meta.js b/website/pages/vi/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/vi/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/network/benefits.mdx b/website/pages/vi/resources/benefits.mdx similarity index 100% rename from website/pages/vi/network/benefits.mdx rename to website/pages/vi/resources/benefits.mdx diff --git a/website/pages/vi/glossary.mdx b/website/pages/vi/resources/glossary.mdx similarity index 100% rename from website/pages/vi/glossary.mdx rename to website/pages/vi/resources/glossary.mdx diff --git a/website/pages/vi/resources/release-notes/_meta.js b/website/pages/vi/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/vi/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx b/website/pages/vi/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/vi/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/vi/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/vi/release-notes/graphql-validations-migration-guide.mdx b/website/pages/vi/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/vi/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/vi/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/vi/resources/roles/_meta.js b/website/pages/vi/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/vi/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/network/curating.mdx b/website/pages/vi/resources/roles/curating.mdx similarity index 100% rename from website/pages/vi/network/curating.mdx rename to website/pages/vi/resources/roles/curating.mdx diff --git a/website/pages/vi/network/delegating.mdx b/website/pages/vi/resources/roles/delegating.mdx similarity index 100% rename from website/pages/vi/network/delegating.mdx rename to website/pages/vi/resources/roles/delegating.mdx diff --git a/website/pages/vi/network/tokenomics.mdx b/website/pages/vi/resources/tokenomics.mdx similarity index 100% rename from website/pages/vi/network/tokenomics.mdx rename to website/pages/vi/resources/tokenomics.mdx diff --git a/website/pages/vi/sps/_meta.js b/website/pages/vi/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/vi/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/vi/subgraphs/_meta.js b/website/pages/vi/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/vi/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/billing.mdx b/website/pages/vi/subgraphs/billing.mdx similarity index 100% rename from website/pages/vi/billing.mdx rename to website/pages/vi/subgraphs/billing.mdx diff --git a/website/pages/vi/subgraphs/cookbook/_meta.js b/website/pages/vi/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/vi/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/cookbook/arweave.mdx b/website/pages/vi/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/vi/cookbook/arweave.mdx rename to website/pages/vi/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/vi/cookbook/avoid-eth-calls.mdx b/website/pages/vi/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/vi/cookbook/avoid-eth-calls.mdx rename to website/pages/vi/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/vi/cookbook/cosmos.mdx b/website/pages/vi/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/vi/cookbook/cosmos.mdx rename to website/pages/vi/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/vi/cookbook/derivedfrom.mdx b/website/pages/vi/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/vi/cookbook/derivedfrom.mdx rename to website/pages/vi/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/vi/cookbook/enums.mdx b/website/pages/vi/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/vi/cookbook/enums.mdx rename to website/pages/vi/subgraphs/cookbook/enums.mdx diff --git a/website/pages/vi/cookbook/grafting-hotfix.mdx b/website/pages/vi/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/vi/cookbook/grafting-hotfix.mdx rename to website/pages/vi/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/vi/cookbook/grafting.mdx b/website/pages/vi/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/vi/cookbook/grafting.mdx rename to website/pages/vi/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/vi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/vi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/vi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/vi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/vi/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/vi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/vi/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/vi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/vi/cookbook/near.mdx b/website/pages/vi/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/vi/cookbook/near.mdx rename to website/pages/vi/subgraphs/cookbook/near.mdx diff --git a/website/pages/vi/cookbook/pruning.mdx b/website/pages/vi/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/vi/cookbook/pruning.mdx rename to website/pages/vi/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/vi/cookbook/subgraph-debug-forking.mdx b/website/pages/vi/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/vi/cookbook/subgraph-debug-forking.mdx rename to website/pages/vi/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/vi/cookbook/subgraph-uncrashable.mdx b/website/pages/vi/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/vi/cookbook/subgraph-uncrashable.mdx rename to website/pages/vi/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/vi/cookbook/substreams-powered-subgraphs.mdx b/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/vi/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/vi/cookbook/timeseries.mdx b/website/pages/vi/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/vi/cookbook/timeseries.mdx rename to website/pages/vi/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/vi/cookbook/transfer-to-the-graph.mdx b/website/pages/vi/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/vi/cookbook/transfer-to-the-graph.mdx rename to website/pages/vi/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/vi/subgraphs/developing/_meta.js b/website/pages/vi/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/vi/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/subgraphs/developing/creating/_meta.js b/website/pages/vi/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/vi/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/developing/creating-a-subgraph/advanced.mdx b/website/pages/vi/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/advanced.mdx rename to website/pages/vi/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/vi/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/vi/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/vi/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/vi/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/vi/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/vi/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/vi/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/vi/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/vi/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/vi/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/vi/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/vi/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/vi/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/vi/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/vi/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/vi/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/vi/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/vi/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/vi/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/vi/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/vi/subgraphs/developing/deploying/_meta.js b/website/pages/vi/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/vi/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/developing/deploying/multiple-networks.mdx b/website/pages/vi/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/vi/developing/deploying/multiple-networks.mdx rename to website/pages/vi/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/vi/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/vi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/vi/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/vi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/vi/developing/deploying/using-subgraph-studio.mdx b/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/vi/developing/deploying/using-subgraph-studio.mdx rename to website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/vi/developing/developer-faqs.mdx b/website/pages/vi/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/vi/developing/developer-faqs.mdx rename to website/pages/vi/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/vi/developing/developing.mdx b/website/pages/vi/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/vi/developing/developing.mdx rename to website/pages/vi/subgraphs/developing/introduction.mdx diff --git a/website/pages/vi/subgraphs/developing/managing/_meta.js b/website/pages/vi/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/vi/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/developing/managing/delete-a-subgraph.mdx b/website/pages/vi/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/vi/developing/managing/delete-a-subgraph.mdx rename to website/pages/vi/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/vi/developing/managing/transfer-a-subgraph.mdx b/website/pages/vi/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/vi/developing/managing/transfer-a-subgraph.mdx rename to website/pages/vi/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/vi/subgraphs/developing/publishing/_meta.js b/website/pages/vi/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/vi/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/developing/publishing/publishing-a-subgraph.mdx b/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/vi/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/vi/developing/subgraphs.mdx b/website/pages/vi/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/vi/developing/subgraphs.mdx rename to website/pages/vi/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/vi/explorer.mdx b/website/pages/vi/subgraphs/explorer.mdx similarity index 100% rename from website/pages/vi/explorer.mdx rename to website/pages/vi/subgraphs/explorer.mdx diff --git a/website/pages/vi/subgraphs/querying/_meta.js b/website/pages/vi/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/vi/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/querying/querying-best-practices.mdx b/website/pages/vi/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/vi/querying/querying-best-practices.mdx rename to website/pages/vi/subgraphs/querying/best-practices.mdx diff --git a/website/pages/vi/querying/distributed-systems.mdx b/website/pages/vi/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/vi/querying/distributed-systems.mdx rename to website/pages/vi/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/vi/querying/querying-from-an-application.mdx b/website/pages/vi/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/vi/querying/querying-from-an-application.mdx rename to website/pages/vi/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/vi/subgraphs/querying/graph-client/_meta.js b/website/pages/vi/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/vi/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/querying/graphql-api.mdx b/website/pages/vi/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/vi/querying/graphql-api.mdx rename to website/pages/vi/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/vi/querying/querying-the-graph.mdx b/website/pages/vi/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/vi/querying/querying-the-graph.mdx rename to website/pages/vi/subgraphs/querying/introduction.mdx diff --git a/website/pages/vi/querying/managing-api-keys.mdx b/website/pages/vi/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/vi/querying/managing-api-keys.mdx rename to website/pages/vi/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/vi/querying/querying-with-python.mdx b/website/pages/vi/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/vi/querying/querying-with-python.mdx rename to website/pages/vi/subgraphs/querying/python.mdx diff --git a/website/pages/vi/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/vi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/vi/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/vi/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/vi/quick-start.mdx b/website/pages/vi/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/vi/quick-start.mdx rename to website/pages/vi/subgraphs/quick-start.mdx diff --git a/website/pages/vi/substreams/_meta.js b/website/pages/vi/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/vi/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/substreams.mdx b/website/pages/vi/substreams/introduction.mdx similarity index 100% rename from website/pages/vi/substreams.mdx rename to website/pages/vi/substreams/introduction.mdx diff --git a/website/pages/vi/substreams/sps/_meta.js b/website/pages/vi/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/vi/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/vi/sps/introduction.mdx b/website/pages/vi/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/vi/sps/introduction.mdx rename to website/pages/vi/substreams/sps/introduction.mdx diff --git a/website/pages/vi/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/vi/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/vi/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/vi/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/vi/sps/triggers-example.mdx b/website/pages/vi/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/vi/sps/triggers-example.mdx rename to website/pages/vi/substreams/sps/triggers-example.mdx diff --git a/website/pages/vi/sps/triggers.mdx b/website/pages/vi/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/vi/sps/triggers.mdx rename to website/pages/vi/substreams/sps/triggers.mdx diff --git a/website/pages/zh/cookbook/_meta.js b/website/pages/zh/cookbook/_meta.js deleted file mode 100644 index 7fc5602ab4d2..000000000000 --- a/website/pages/zh/cookbook/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/cookbook/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/_meta.js b/website/pages/zh/developing/_meta.js deleted file mode 100644 index 48d6b89bb3fe..000000000000 --- a/website/pages/zh/developing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/developing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/creating-a-subgraph/_meta.js b/website/pages/zh/developing/creating-a-subgraph/_meta.js deleted file mode 100644 index a904468b50a2..000000000000 --- a/website/pages/zh/developing/creating-a-subgraph/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/creating-a-subgraph/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js b/website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js deleted file mode 100644 index 9c23f4f1b1a1..000000000000 --- a/website/pages/zh/developing/creating-a-subgraph/graph-ts/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../../en/developing/creating-a-subgraph/graph-ts/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/deploying/_meta.js b/website/pages/zh/developing/deploying/_meta.js deleted file mode 100644 index 7d696b40205a..000000000000 --- a/website/pages/zh/developing/deploying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/deploying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/managing/_meta.js b/website/pages/zh/developing/managing/_meta.js deleted file mode 100644 index faa0447a3553..000000000000 --- a/website/pages/zh/developing/managing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/managing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/developing/publishing/_meta.js b/website/pages/zh/developing/publishing/_meta.js deleted file mode 100644 index 5fa714a2763a..000000000000 --- a/website/pages/zh/developing/publishing/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/developing/publishing/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/indexer-tooling/_meta.js b/website/pages/zh/indexer-tooling/_meta.js deleted file mode 100644 index 3d6a0e72ad23..000000000000 --- a/website/pages/zh/indexer-tooling/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/indexer-tooling/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/indexing/_meta.js b/website/pages/zh/indexing/_meta.js new file mode 100644 index 000000000000..de19e80d5f5a --- /dev/null +++ b/website/pages/zh/indexing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/indexing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/chain-integration-overview.mdx b/website/pages/zh/indexing/chain-integration-overview.mdx similarity index 100% rename from website/pages/zh/chain-integration-overview.mdx rename to website/pages/zh/indexing/chain-integration-overview.mdx diff --git a/website/pages/zh/indexing.mdx b/website/pages/zh/indexing/introduction.mdx similarity index 100% rename from website/pages/zh/indexing.mdx rename to website/pages/zh/indexing/introduction.mdx diff --git a/website/pages/zh/new-chain-integration.mdx b/website/pages/zh/indexing/new-chain-integration.mdx similarity index 100% rename from website/pages/zh/new-chain-integration.mdx rename to website/pages/zh/indexing/new-chain-integration.mdx diff --git a/website/pages/zh/supported-network-requirements.mdx b/website/pages/zh/indexing/supported-network-requirements.mdx similarity index 100% rename from website/pages/zh/supported-network-requirements.mdx rename to website/pages/zh/indexing/supported-network-requirements.mdx diff --git a/website/pages/zh/tap.mdx b/website/pages/zh/indexing/tap.mdx similarity index 100% rename from website/pages/zh/tap.mdx rename to website/pages/zh/indexing/tap.mdx diff --git a/website/pages/zh/indexing/tooling/_meta.js b/website/pages/zh/indexing/tooling/_meta.js new file mode 100644 index 000000000000..d644d6025b92 --- /dev/null +++ b/website/pages/zh/indexing/tooling/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/indexing/tooling/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/indexer-tooling/firehose.mdx b/website/pages/zh/indexing/tooling/firehose.mdx similarity index 100% rename from website/pages/zh/indexer-tooling/firehose.mdx rename to website/pages/zh/indexing/tooling/firehose.mdx diff --git a/website/pages/zh/indexer-tooling/graphcast.mdx b/website/pages/zh/indexing/tooling/graphcast.mdx similarity index 100% rename from website/pages/zh/indexer-tooling/graphcast.mdx rename to website/pages/zh/indexing/tooling/graphcast.mdx diff --git a/website/pages/zh/indexer-tooling/operating-graph-node.mdx b/website/pages/zh/indexing/tooling/operating-graph-node.mdx similarity index 100% rename from website/pages/zh/indexer-tooling/operating-graph-node.mdx rename to website/pages/zh/indexing/tooling/operating-graph-node.mdx diff --git a/website/pages/zh/network/_meta.js b/website/pages/zh/network/_meta.js deleted file mode 100644 index 49858537c885..000000000000 --- a/website/pages/zh/network/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/network/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/network/overview.mdx b/website/pages/zh/network/overview.mdx deleted file mode 100644 index b2ab6df18b27..000000000000 --- a/website/pages/zh/network/overview.mdx +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: 网络概述 ---- - -The Graph Network is a decentralized indexing protocol for organizing blockchain data. - -## How does it work? - -Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure. - -## Specifics - -The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications. - -![代币经济学](/img/Network-roles@2x.png) - -### Economics - -To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network. - -Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake. diff --git a/website/pages/zh/querying/_meta.js b/website/pages/zh/querying/_meta.js deleted file mode 100644 index e52da8f399fb..000000000000 --- a/website/pages/zh/querying/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/querying/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/querying/graph-client/_meta.js b/website/pages/zh/querying/graph-client/_meta.js deleted file mode 100644 index f00c8556ac1b..000000000000 --- a/website/pages/zh/querying/graph-client/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../../en/querying/graph-client/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/release-notes/_meta.js b/website/pages/zh/release-notes/_meta.js deleted file mode 100644 index 1df59d0049cf..000000000000 --- a/website/pages/zh/release-notes/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/release-notes/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/resources/_meta.js b/website/pages/zh/resources/_meta.js new file mode 100644 index 000000000000..8b68e54fed72 --- /dev/null +++ b/website/pages/zh/resources/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/resources/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/network/benefits.mdx b/website/pages/zh/resources/benefits.mdx similarity index 100% rename from website/pages/zh/network/benefits.mdx rename to website/pages/zh/resources/benefits.mdx diff --git a/website/pages/zh/glossary.mdx b/website/pages/zh/resources/glossary.mdx similarity index 100% rename from website/pages/zh/glossary.mdx rename to website/pages/zh/resources/glossary.mdx diff --git a/website/pages/zh/resources/release-notes/_meta.js b/website/pages/zh/resources/release-notes/_meta.js new file mode 100644 index 000000000000..4b596c4b4aad --- /dev/null +++ b/website/pages/zh/resources/release-notes/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/release-notes/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx b/website/pages/zh/resources/release-notes/assemblyscript-migration-guide.mdx similarity index 100% rename from website/pages/zh/release-notes/assemblyscript-migration-guide.mdx rename to website/pages/zh/resources/release-notes/assemblyscript-migration-guide.mdx diff --git a/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx b/website/pages/zh/resources/release-notes/graphql-validations-migration-guide.mdx similarity index 100% rename from website/pages/zh/release-notes/graphql-validations-migration-guide.mdx rename to website/pages/zh/resources/release-notes/graphql-validations-migration-guide.mdx diff --git a/website/pages/zh/resources/roles/_meta.js b/website/pages/zh/resources/roles/_meta.js new file mode 100644 index 000000000000..f4a2c3b75766 --- /dev/null +++ b/website/pages/zh/resources/roles/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/resources/roles/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/network/curating.mdx b/website/pages/zh/resources/roles/curating.mdx similarity index 100% rename from website/pages/zh/network/curating.mdx rename to website/pages/zh/resources/roles/curating.mdx diff --git a/website/pages/zh/network/delegating.mdx b/website/pages/zh/resources/roles/delegating.mdx similarity index 100% rename from website/pages/zh/network/delegating.mdx rename to website/pages/zh/resources/roles/delegating.mdx diff --git a/website/pages/zh/network/tokenomics.mdx b/website/pages/zh/resources/tokenomics.mdx similarity index 100% rename from website/pages/zh/network/tokenomics.mdx rename to website/pages/zh/resources/tokenomics.mdx diff --git a/website/pages/zh/sps/_meta.js b/website/pages/zh/sps/_meta.js deleted file mode 100644 index 4ebd7d55a84f..000000000000 --- a/website/pages/zh/sps/_meta.js +++ /dev/null @@ -1,5 +0,0 @@ -import meta from '../../en/sps/_meta.js' - -export default { - ...meta, -} diff --git a/website/pages/zh/subgraphs/_meta.js b/website/pages/zh/subgraphs/_meta.js new file mode 100644 index 000000000000..ac1bc143b117 --- /dev/null +++ b/website/pages/zh/subgraphs/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/subgraphs/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/billing.mdx b/website/pages/zh/subgraphs/billing.mdx similarity index 100% rename from website/pages/zh/billing.mdx rename to website/pages/zh/subgraphs/billing.mdx diff --git a/website/pages/zh/subgraphs/cookbook/_meta.js b/website/pages/zh/subgraphs/cookbook/_meta.js new file mode 100644 index 000000000000..ac622be33d72 --- /dev/null +++ b/website/pages/zh/subgraphs/cookbook/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/cookbook/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/cookbook/arweave.mdx b/website/pages/zh/subgraphs/cookbook/arweave.mdx similarity index 100% rename from website/pages/zh/cookbook/arweave.mdx rename to website/pages/zh/subgraphs/cookbook/arweave.mdx diff --git a/website/pages/zh/cookbook/avoid-eth-calls.mdx b/website/pages/zh/subgraphs/cookbook/avoid-eth-calls.mdx similarity index 100% rename from website/pages/zh/cookbook/avoid-eth-calls.mdx rename to website/pages/zh/subgraphs/cookbook/avoid-eth-calls.mdx diff --git a/website/pages/zh/cookbook/cosmos.mdx b/website/pages/zh/subgraphs/cookbook/cosmos.mdx similarity index 100% rename from website/pages/zh/cookbook/cosmos.mdx rename to website/pages/zh/subgraphs/cookbook/cosmos.mdx diff --git a/website/pages/zh/cookbook/derivedfrom.mdx b/website/pages/zh/subgraphs/cookbook/derivedfrom.mdx similarity index 100% rename from website/pages/zh/cookbook/derivedfrom.mdx rename to website/pages/zh/subgraphs/cookbook/derivedfrom.mdx diff --git a/website/pages/zh/cookbook/enums.mdx b/website/pages/zh/subgraphs/cookbook/enums.mdx similarity index 100% rename from website/pages/zh/cookbook/enums.mdx rename to website/pages/zh/subgraphs/cookbook/enums.mdx diff --git a/website/pages/zh/cookbook/grafting-hotfix.mdx b/website/pages/zh/subgraphs/cookbook/grafting-hotfix.mdx similarity index 100% rename from website/pages/zh/cookbook/grafting-hotfix.mdx rename to website/pages/zh/subgraphs/cookbook/grafting-hotfix.mdx diff --git a/website/pages/zh/cookbook/grafting.mdx b/website/pages/zh/subgraphs/cookbook/grafting.mdx similarity index 100% rename from website/pages/zh/cookbook/grafting.mdx rename to website/pages/zh/subgraphs/cookbook/grafting.mdx diff --git a/website/pages/zh/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/zh/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx similarity index 100% rename from website/pages/zh/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/zh/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx diff --git a/website/pages/zh/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/zh/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx similarity index 100% rename from website/pages/zh/cookbook/immutable-entities-bytes-as-ids.mdx rename to website/pages/zh/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx diff --git a/website/pages/zh/cookbook/near.mdx b/website/pages/zh/subgraphs/cookbook/near.mdx similarity index 100% rename from website/pages/zh/cookbook/near.mdx rename to website/pages/zh/subgraphs/cookbook/near.mdx diff --git a/website/pages/zh/cookbook/pruning.mdx b/website/pages/zh/subgraphs/cookbook/pruning.mdx similarity index 100% rename from website/pages/zh/cookbook/pruning.mdx rename to website/pages/zh/subgraphs/cookbook/pruning.mdx diff --git a/website/pages/zh/cookbook/subgraph-debug-forking.mdx b/website/pages/zh/subgraphs/cookbook/subgraph-debug-forking.mdx similarity index 100% rename from website/pages/zh/cookbook/subgraph-debug-forking.mdx rename to website/pages/zh/subgraphs/cookbook/subgraph-debug-forking.mdx diff --git a/website/pages/zh/cookbook/subgraph-uncrashable.mdx b/website/pages/zh/subgraphs/cookbook/subgraph-uncrashable.mdx similarity index 100% rename from website/pages/zh/cookbook/subgraph-uncrashable.mdx rename to website/pages/zh/subgraphs/cookbook/subgraph-uncrashable.mdx diff --git a/website/pages/zh/cookbook/substreams-powered-subgraphs.mdx b/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx similarity index 100% rename from website/pages/zh/cookbook/substreams-powered-subgraphs.mdx rename to website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx diff --git a/website/pages/zh/cookbook/timeseries.mdx b/website/pages/zh/subgraphs/cookbook/timeseries.mdx similarity index 100% rename from website/pages/zh/cookbook/timeseries.mdx rename to website/pages/zh/subgraphs/cookbook/timeseries.mdx diff --git a/website/pages/zh/cookbook/transfer-to-the-graph.mdx b/website/pages/zh/subgraphs/cookbook/transfer-to-the-graph.mdx similarity index 100% rename from website/pages/zh/cookbook/transfer-to-the-graph.mdx rename to website/pages/zh/subgraphs/cookbook/transfer-to-the-graph.mdx diff --git a/website/pages/zh/subgraphs/developing/_meta.js b/website/pages/zh/subgraphs/developing/_meta.js new file mode 100644 index 000000000000..950b13d010ee --- /dev/null +++ b/website/pages/zh/subgraphs/developing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/developing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/subgraphs/developing/creating/_meta.js b/website/pages/zh/subgraphs/developing/creating/_meta.js new file mode 100644 index 000000000000..ff0dbb4ae292 --- /dev/null +++ b/website/pages/zh/subgraphs/developing/creating/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/creating/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/developing/creating-a-subgraph/advanced.mdx b/website/pages/zh/subgraphs/developing/creating/advanced.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/advanced.mdx rename to website/pages/zh/subgraphs/developing/creating/advanced.mdx diff --git a/website/pages/zh/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/zh/subgraphs/developing/creating/assemblyscript-mappings.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/assemblyscript-mappings.mdx rename to website/pages/zh/subgraphs/developing/creating/assemblyscript-mappings.mdx diff --git a/website/pages/zh/subgraphs/developing/creating/graph-ts/_meta.js b/website/pages/zh/subgraphs/developing/creating/graph-ts/_meta.js new file mode 100644 index 000000000000..5d9333d5a00c --- /dev/null +++ b/website/pages/zh/subgraphs/developing/creating/graph-ts/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../../en/subgraphs/developing/creating/graph-ts/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/developing/creating-a-subgraph/graph-ts/api.mdx b/website/pages/zh/subgraphs/developing/creating/graph-ts/api.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/graph-ts/api.mdx rename to website/pages/zh/subgraphs/developing/creating/graph-ts/api.mdx diff --git a/website/pages/zh/developing/creating-a-subgraph/graph-ts/common-issues.mdx b/website/pages/zh/subgraphs/developing/creating/graph-ts/common-issues.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/graph-ts/common-issues.mdx rename to website/pages/zh/subgraphs/developing/creating/graph-ts/common-issues.mdx diff --git a/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx rename to website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx diff --git a/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx rename to website/pages/zh/subgraphs/developing/creating/ql-schema.mdx diff --git a/website/pages/zh/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/zh/subgraphs/developing/creating/starting-your-subgraph.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/starting-your-subgraph.mdx rename to website/pages/zh/subgraphs/developing/creating/starting-your-subgraph.mdx diff --git a/website/pages/zh/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/zh/subgraphs/developing/creating/subgraph-manifest.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/subgraph-manifest.mdx rename to website/pages/zh/subgraphs/developing/creating/subgraph-manifest.mdx diff --git a/website/pages/zh/developing/creating-a-subgraph/unit-testing-framework.mdx b/website/pages/zh/subgraphs/developing/creating/unit-testing-framework.mdx similarity index 100% rename from website/pages/zh/developing/creating-a-subgraph/unit-testing-framework.mdx rename to website/pages/zh/subgraphs/developing/creating/unit-testing-framework.mdx diff --git a/website/pages/zh/subgraphs/developing/deploying/_meta.js b/website/pages/zh/subgraphs/developing/deploying/_meta.js new file mode 100644 index 000000000000..e8d95c5b5d12 --- /dev/null +++ b/website/pages/zh/subgraphs/developing/deploying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/deploying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/developing/deploying/multiple-networks.mdx b/website/pages/zh/subgraphs/developing/deploying/multiple-networks.mdx similarity index 100% rename from website/pages/zh/developing/deploying/multiple-networks.mdx rename to website/pages/zh/subgraphs/developing/deploying/multiple-networks.mdx diff --git a/website/pages/zh/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/zh/subgraphs/developing/deploying/subgraph-studio-faqs.mdx similarity index 100% rename from website/pages/zh/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/zh/subgraphs/developing/deploying/subgraph-studio-faqs.mdx diff --git a/website/pages/zh/developing/deploying/using-subgraph-studio.mdx b/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx similarity index 100% rename from website/pages/zh/developing/deploying/using-subgraph-studio.mdx rename to website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx diff --git a/website/pages/zh/developing/developer-faqs.mdx b/website/pages/zh/subgraphs/developing/developer-faqs.mdx similarity index 100% rename from website/pages/zh/developing/developer-faqs.mdx rename to website/pages/zh/subgraphs/developing/developer-faqs.mdx diff --git a/website/pages/zh/developing/developing.mdx b/website/pages/zh/subgraphs/developing/introduction.mdx similarity index 100% rename from website/pages/zh/developing/developing.mdx rename to website/pages/zh/subgraphs/developing/introduction.mdx diff --git a/website/pages/zh/subgraphs/developing/managing/_meta.js b/website/pages/zh/subgraphs/developing/managing/_meta.js new file mode 100644 index 000000000000..1388734118a0 --- /dev/null +++ b/website/pages/zh/subgraphs/developing/managing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/managing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/developing/managing/delete-a-subgraph.mdx b/website/pages/zh/subgraphs/developing/managing/deleting-a-subgraph.mdx similarity index 100% rename from website/pages/zh/developing/managing/delete-a-subgraph.mdx rename to website/pages/zh/subgraphs/developing/managing/deleting-a-subgraph.mdx diff --git a/website/pages/zh/developing/managing/transfer-a-subgraph.mdx b/website/pages/zh/subgraphs/developing/managing/transferring-a-subgraph.mdx similarity index 100% rename from website/pages/zh/developing/managing/transfer-a-subgraph.mdx rename to website/pages/zh/subgraphs/developing/managing/transferring-a-subgraph.mdx diff --git a/website/pages/zh/subgraphs/developing/publishing/_meta.js b/website/pages/zh/subgraphs/developing/publishing/_meta.js new file mode 100644 index 000000000000..ca2713212888 --- /dev/null +++ b/website/pages/zh/subgraphs/developing/publishing/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/developing/publishing/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/developing/publishing/publishing-a-subgraph.mdx b/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx similarity index 100% rename from website/pages/zh/developing/publishing/publishing-a-subgraph.mdx rename to website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx diff --git a/website/pages/zh/developing/subgraphs.mdx b/website/pages/zh/subgraphs/developing/subgraphs.mdx similarity index 100% rename from website/pages/zh/developing/subgraphs.mdx rename to website/pages/zh/subgraphs/developing/subgraphs.mdx diff --git a/website/pages/zh/explorer.mdx b/website/pages/zh/subgraphs/explorer.mdx similarity index 100% rename from website/pages/zh/explorer.mdx rename to website/pages/zh/subgraphs/explorer.mdx diff --git a/website/pages/zh/subgraphs/querying/_meta.js b/website/pages/zh/subgraphs/querying/_meta.js new file mode 100644 index 000000000000..59a543bdc726 --- /dev/null +++ b/website/pages/zh/subgraphs/querying/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/subgraphs/querying/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/querying/querying-best-practices.mdx b/website/pages/zh/subgraphs/querying/best-practices.mdx similarity index 100% rename from website/pages/zh/querying/querying-best-practices.mdx rename to website/pages/zh/subgraphs/querying/best-practices.mdx diff --git a/website/pages/zh/querying/distributed-systems.mdx b/website/pages/zh/subgraphs/querying/distributed-systems.mdx similarity index 100% rename from website/pages/zh/querying/distributed-systems.mdx rename to website/pages/zh/subgraphs/querying/distributed-systems.mdx diff --git a/website/pages/zh/querying/querying-from-an-application.mdx b/website/pages/zh/subgraphs/querying/from-an-application.mdx similarity index 100% rename from website/pages/zh/querying/querying-from-an-application.mdx rename to website/pages/zh/subgraphs/querying/from-an-application.mdx diff --git a/website/pages/zh/subgraphs/querying/graph-client/_meta.js b/website/pages/zh/subgraphs/querying/graph-client/_meta.js new file mode 100644 index 000000000000..4cc10319cdeb --- /dev/null +++ b/website/pages/zh/subgraphs/querying/graph-client/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../../en/subgraphs/querying/graph-client/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/querying/graphql-api.mdx b/website/pages/zh/subgraphs/querying/graphql-api.mdx similarity index 100% rename from website/pages/zh/querying/graphql-api.mdx rename to website/pages/zh/subgraphs/querying/graphql-api.mdx diff --git a/website/pages/zh/querying/querying-the-graph.mdx b/website/pages/zh/subgraphs/querying/introduction.mdx similarity index 100% rename from website/pages/zh/querying/querying-the-graph.mdx rename to website/pages/zh/subgraphs/querying/introduction.mdx diff --git a/website/pages/zh/querying/managing-api-keys.mdx b/website/pages/zh/subgraphs/querying/managing-api-keys.mdx similarity index 100% rename from website/pages/zh/querying/managing-api-keys.mdx rename to website/pages/zh/subgraphs/querying/managing-api-keys.mdx diff --git a/website/pages/zh/querying/querying-with-python.mdx b/website/pages/zh/subgraphs/querying/python.mdx similarity index 100% rename from website/pages/zh/querying/querying-with-python.mdx rename to website/pages/zh/subgraphs/querying/python.mdx diff --git a/website/pages/zh/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/zh/subgraphs/querying/subgraph-id-vs-deployment-id.mdx similarity index 100% rename from website/pages/zh/querying/querying-by-subgraph-id-vs-deployment-id.mdx rename to website/pages/zh/subgraphs/querying/subgraph-id-vs-deployment-id.mdx diff --git a/website/pages/zh/quick-start.mdx b/website/pages/zh/subgraphs/quick-start.mdx similarity index 100% rename from website/pages/zh/quick-start.mdx rename to website/pages/zh/subgraphs/quick-start.mdx diff --git a/website/pages/zh/substreams/_meta.js b/website/pages/zh/substreams/_meta.js new file mode 100644 index 000000000000..58ac9bfc2a80 --- /dev/null +++ b/website/pages/zh/substreams/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../en/substreams/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/substreams.mdx b/website/pages/zh/substreams/introduction.mdx similarity index 100% rename from website/pages/zh/substreams.mdx rename to website/pages/zh/substreams/introduction.mdx diff --git a/website/pages/zh/substreams/sps/_meta.js b/website/pages/zh/substreams/sps/_meta.js new file mode 100644 index 000000000000..71552a5e078a --- /dev/null +++ b/website/pages/zh/substreams/sps/_meta.js @@ -0,0 +1,5 @@ +import meta from '../../../en/substreams/sps/_meta.js' + +export default { + ...meta, +} diff --git a/website/pages/zh/sps/introduction.mdx b/website/pages/zh/substreams/sps/introduction.mdx similarity index 100% rename from website/pages/zh/sps/introduction.mdx rename to website/pages/zh/substreams/sps/introduction.mdx diff --git a/website/pages/zh/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/zh/substreams/sps/substreams-powered-subgraphs-faq.mdx similarity index 100% rename from website/pages/zh/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/zh/substreams/sps/substreams-powered-subgraphs-faq.mdx diff --git a/website/pages/zh/sps/triggers-example.mdx b/website/pages/zh/substreams/sps/triggers-example.mdx similarity index 100% rename from website/pages/zh/sps/triggers-example.mdx rename to website/pages/zh/substreams/sps/triggers-example.mdx diff --git a/website/pages/zh/sps/triggers.mdx b/website/pages/zh/substreams/sps/triggers.mdx similarity index 100% rename from website/pages/zh/sps/triggers.mdx rename to website/pages/zh/substreams/sps/triggers.mdx diff --git a/website/route-lockfile.txt b/website/route-lockfile.txt index 5483dda68765..6461e6890411 100644 --- a/website/route-lockfile.txt +++ b/website/route-lockfile.txt @@ -6,74 +6,73 @@ /ar/archived/arbitrum/l2-transfer-tools-faq/ /ar/archived/arbitrum/l2-transfer-tools-guide/ /ar/archived/sunrise/ -/ar/billing/ -/ar/chain-integration-overview/ /ar/contracts/ -/ar/cookbook/arweave/ -/ar/cookbook/avoid-eth-calls/ -/ar/cookbook/cosmos/ -/ar/cookbook/derivedfrom/ -/ar/cookbook/enums/ -/ar/cookbook/grafting-hotfix/ -/ar/cookbook/grafting/ -/ar/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/ar/cookbook/immutable-entities-bytes-as-ids/ -/ar/cookbook/near/ -/ar/cookbook/pruning/ -/ar/cookbook/subgraph-debug-forking/ -/ar/cookbook/subgraph-uncrashable/ -/ar/cookbook/substreams-powered-subgraphs/ -/ar/cookbook/timeseries/ -/ar/cookbook/transfer-to-the-graph/ -/ar/developing/creating-a-subgraph/advanced/ -/ar/developing/creating-a-subgraph/assemblyscript-mappings/ -/ar/developing/creating-a-subgraph/graph-ts/api/ -/ar/developing/creating-a-subgraph/graph-ts/common-issues/ -/ar/developing/creating-a-subgraph/install-the-cli/ -/ar/developing/creating-a-subgraph/ql-schema/ -/ar/developing/creating-a-subgraph/starting-your-subgraph/ -/ar/developing/creating-a-subgraph/subgraph-manifest/ -/ar/developing/creating-a-subgraph/unit-testing-framework/ -/ar/developing/deploying/deploy-using-subgraph-studio/ -/ar/developing/deploying/multiple-networks/ -/ar/developing/deploying/subgraph-studio-faqs/ -/ar/developing/developer-faqs/ -/ar/developing/developing/ -/ar/developing/managing/delete-a-subgraph/ -/ar/developing/managing/transfer-a-subgraph/ -/ar/developing/publishing/publishing-a-subgraph/ -/ar/developing/subgraphs/ -/ar/developing/supported-networks/ -/ar/explorer/ -/ar/glossary/ -/ar/indexer-tooling/firehose/ -/ar/indexer-tooling/graphcast/ -/ar/indexer-tooling/operating-graph-node/ -/ar/indexing/ -/ar/new-chain-integration/ -/ar/querying/distributed-systems/ -/ar/querying/graphql-api/ -/ar/querying/managing-api-keys/ -/ar/querying/querying-best-practices/ -/ar/querying/querying-by-subgraph-id-vs-deployment-id/ -/ar/querying/querying-from-an-application/ -/ar/querying/querying-the-graph/ -/ar/querying/querying-with-python/ -/ar/quick-start/ -/ar/release-notes/assemblyscript-migration-guide/ -/ar/release-notes/graphql-validations-migration-guide/ -/ar/roles-and-benefits/benefits/ -/ar/roles-and-benefits/curating/ -/ar/roles-and-benefits/delegating/ -/ar/roles-and-benefits/overview/ -/ar/sps/introduction/ -/ar/sps/substreams-powered-subgraphs-faq/ -/ar/sps/triggers-example/ -/ar/sps/triggers/ -/ar/substreams/ -/ar/supported-network-requirements/ -/ar/tap/ -/ar/tokenomics/ +/ar/indexing/chain-integration-overview/ +/ar/indexing/introduction/ +/ar/indexing/new-chain-integration/ +/ar/indexing/supported-network-requirements/ +/ar/indexing/tap/ +/ar/indexing/tooling/firehose/ +/ar/indexing/tooling/graphcast/ +/ar/indexing/tooling/operating-graph-node/ +/ar/resources/benefits/ +/ar/resources/glossary/ +/ar/resources/release-notes/assemblyscript-migration-guide/ +/ar/resources/release-notes/graphql-validations-migration-guide/ +/ar/resources/roles/curating/ +/ar/resources/roles/delegating/ +/ar/resources/tokenomics/ +/ar/subgraphs/billing/ +/ar/subgraphs/cookbook/arweave/ +/ar/subgraphs/cookbook/avoid-eth-calls/ +/ar/subgraphs/cookbook/cosmos/ +/ar/subgraphs/cookbook/derivedfrom/ +/ar/subgraphs/cookbook/enums/ +/ar/subgraphs/cookbook/grafting-hotfix/ +/ar/subgraphs/cookbook/grafting/ +/ar/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/ar/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/ar/subgraphs/cookbook/near/ +/ar/subgraphs/cookbook/pruning/ +/ar/subgraphs/cookbook/subgraph-debug-forking/ +/ar/subgraphs/cookbook/subgraph-uncrashable/ +/ar/subgraphs/cookbook/substreams-powered-subgraphs/ +/ar/subgraphs/cookbook/timeseries/ +/ar/subgraphs/cookbook/transfer-to-the-graph/ +/ar/subgraphs/developing/creating/advanced/ +/ar/subgraphs/developing/creating/assemblyscript-mappings/ +/ar/subgraphs/developing/creating/graph-ts/api/ +/ar/subgraphs/developing/creating/graph-ts/common-issues/ +/ar/subgraphs/developing/creating/install-the-cli/ +/ar/subgraphs/developing/creating/ql-schema/ +/ar/subgraphs/developing/creating/starting-your-subgraph/ +/ar/subgraphs/developing/creating/subgraph-manifest/ +/ar/subgraphs/developing/creating/unit-testing-framework/ +/ar/subgraphs/developing/deploying/multiple-networks/ +/ar/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ar/subgraphs/developing/deploying/using-subgraph-studio/ +/ar/subgraphs/developing/developer-faqs/ +/ar/subgraphs/developing/introduction/ +/ar/subgraphs/developing/managing/deleting-a-subgraph/ +/ar/subgraphs/developing/managing/transferring-a-subgraph/ +/ar/subgraphs/developing/publishing/publishing-a-subgraph/ +/ar/subgraphs/developing/subgraphs/ +/ar/subgraphs/explorer/ +/ar/subgraphs/querying/best-practices/ +/ar/subgraphs/querying/distributed-systems/ +/ar/subgraphs/querying/from-an-application/ +/ar/subgraphs/querying/graphql-api/ +/ar/subgraphs/querying/introduction/ +/ar/subgraphs/querying/managing-api-keys/ +/ar/subgraphs/querying/python/ +/ar/subgraphs/querying/subgraph-id-vs-deployment-id/ +/ar/subgraphs/quick-start/ +/ar/substreams/introduction/ +/ar/substreams/sps/introduction/ +/ar/substreams/sps/substreams-powered-subgraphs-faq/ +/ar/substreams/sps/triggers-example/ +/ar/substreams/sps/triggers/ +/ar/supported-networks/ /cs/ /cs/404/ /cs/about/ @@ -81,147 +80,145 @@ /cs/archived/arbitrum/l2-transfer-tools-faq/ /cs/archived/arbitrum/l2-transfer-tools-guide/ /cs/archived/sunrise/ -/cs/billing/ -/cs/chain-integration-overview/ /cs/contracts/ -/cs/cookbook/arweave/ -/cs/cookbook/avoid-eth-calls/ -/cs/cookbook/cosmos/ -/cs/cookbook/derivedfrom/ -/cs/cookbook/enums/ -/cs/cookbook/grafting-hotfix/ -/cs/cookbook/grafting/ -/cs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/cs/cookbook/immutable-entities-bytes-as-ids/ -/cs/cookbook/near/ -/cs/cookbook/pruning/ -/cs/cookbook/subgraph-debug-forking/ -/cs/cookbook/subgraph-uncrashable/ -/cs/cookbook/substreams-powered-subgraphs/ -/cs/cookbook/timeseries/ -/cs/cookbook/transfer-to-the-graph/ -/cs/developing/creating-a-subgraph/advanced/ -/cs/developing/creating-a-subgraph/assemblyscript-mappings/ -/cs/developing/creating-a-subgraph/graph-ts/api/ -/cs/developing/creating-a-subgraph/graph-ts/common-issues/ -/cs/developing/creating-a-subgraph/install-the-cli/ -/cs/developing/creating-a-subgraph/ql-schema/ -/cs/developing/creating-a-subgraph/starting-your-subgraph/ -/cs/developing/creating-a-subgraph/subgraph-manifest/ -/cs/developing/creating-a-subgraph/unit-testing-framework/ -/cs/developing/deploying/deploy-using-subgraph-studio/ -/cs/developing/deploying/multiple-networks/ -/cs/developing/deploying/subgraph-studio-faqs/ -/cs/developing/developer-faqs/ -/cs/developing/developing/ -/cs/developing/managing/delete-a-subgraph/ -/cs/developing/managing/transfer-a-subgraph/ -/cs/developing/publishing/publishing-a-subgraph/ -/cs/developing/subgraphs/ -/cs/developing/supported-networks/ -/cs/explorer/ -/cs/glossary/ -/cs/indexer-tooling/firehose/ -/cs/indexer-tooling/graphcast/ -/cs/indexer-tooling/operating-graph-node/ -/cs/indexing/ -/cs/new-chain-integration/ -/cs/querying/distributed-systems/ -/cs/querying/graphql-api/ -/cs/querying/managing-api-keys/ -/cs/querying/querying-best-practices/ -/cs/querying/querying-by-subgraph-id-vs-deployment-id/ -/cs/querying/querying-from-an-application/ -/cs/querying/querying-the-graph/ -/cs/querying/querying-with-python/ -/cs/quick-start/ -/cs/release-notes/assemblyscript-migration-guide/ -/cs/release-notes/graphql-validations-migration-guide/ -/cs/roles-and-benefits/benefits/ -/cs/roles-and-benefits/curating/ -/cs/roles-and-benefits/delegating/ -/cs/roles-and-benefits/overview/ -/cs/sps/introduction/ -/cs/sps/substreams-powered-subgraphs-faq/ -/cs/sps/triggers-example/ -/cs/sps/triggers/ -/cs/substreams/ -/cs/supported-network-requirements/ -/cs/tap/ -/cs/tokenomics/ +/cs/indexing/chain-integration-overview/ +/cs/indexing/introduction/ +/cs/indexing/new-chain-integration/ +/cs/indexing/supported-network-requirements/ +/cs/indexing/tap/ +/cs/indexing/tooling/firehose/ +/cs/indexing/tooling/graphcast/ +/cs/indexing/tooling/operating-graph-node/ +/cs/resources/benefits/ +/cs/resources/glossary/ +/cs/resources/release-notes/assemblyscript-migration-guide/ +/cs/resources/release-notes/graphql-validations-migration-guide/ +/cs/resources/roles/curating/ +/cs/resources/roles/delegating/ +/cs/resources/tokenomics/ +/cs/subgraphs/billing/ +/cs/subgraphs/cookbook/arweave/ +/cs/subgraphs/cookbook/avoid-eth-calls/ +/cs/subgraphs/cookbook/cosmos/ +/cs/subgraphs/cookbook/derivedfrom/ +/cs/subgraphs/cookbook/enums/ +/cs/subgraphs/cookbook/grafting-hotfix/ +/cs/subgraphs/cookbook/grafting/ +/cs/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/cs/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/cs/subgraphs/cookbook/near/ +/cs/subgraphs/cookbook/pruning/ +/cs/subgraphs/cookbook/subgraph-debug-forking/ +/cs/subgraphs/cookbook/subgraph-uncrashable/ +/cs/subgraphs/cookbook/substreams-powered-subgraphs/ +/cs/subgraphs/cookbook/timeseries/ +/cs/subgraphs/cookbook/transfer-to-the-graph/ +/cs/subgraphs/developing/creating/advanced/ +/cs/subgraphs/developing/creating/assemblyscript-mappings/ +/cs/subgraphs/developing/creating/graph-ts/api/ +/cs/subgraphs/developing/creating/graph-ts/common-issues/ +/cs/subgraphs/developing/creating/install-the-cli/ +/cs/subgraphs/developing/creating/ql-schema/ +/cs/subgraphs/developing/creating/starting-your-subgraph/ +/cs/subgraphs/developing/creating/subgraph-manifest/ +/cs/subgraphs/developing/creating/unit-testing-framework/ +/cs/subgraphs/developing/deploying/multiple-networks/ +/cs/subgraphs/developing/deploying/subgraph-studio-faqs/ +/cs/subgraphs/developing/deploying/using-subgraph-studio/ +/cs/subgraphs/developing/developer-faqs/ +/cs/subgraphs/developing/introduction/ +/cs/subgraphs/developing/managing/deleting-a-subgraph/ +/cs/subgraphs/developing/managing/transferring-a-subgraph/ +/cs/subgraphs/developing/publishing/publishing-a-subgraph/ +/cs/subgraphs/developing/subgraphs/ +/cs/subgraphs/explorer/ +/cs/subgraphs/querying/best-practices/ +/cs/subgraphs/querying/distributed-systems/ +/cs/subgraphs/querying/from-an-application/ +/cs/subgraphs/querying/graphql-api/ +/cs/subgraphs/querying/introduction/ +/cs/subgraphs/querying/managing-api-keys/ +/cs/subgraphs/querying/python/ +/cs/subgraphs/querying/subgraph-id-vs-deployment-id/ +/cs/subgraphs/quick-start/ +/cs/substreams/introduction/ +/cs/substreams/sps/introduction/ +/cs/substreams/sps/substreams-powered-subgraphs-faq/ +/cs/substreams/sps/triggers-example/ +/cs/substreams/sps/triggers/ +/cs/supported-networks/ /de/about/ /de/archived/arbitrum/arbitrum-faq/ /de/archived/arbitrum/l2-transfer-tools-faq/ /de/archived/arbitrum/l2-transfer-tools-guide/ /de/archived/sunrise/ -/de/billing/ -/de/chain-integration-overview/ /de/contracts/ -/de/cookbook/arweave/ -/de/cookbook/avoid-eth-calls/ -/de/cookbook/cosmos/ -/de/cookbook/derivedfrom/ -/de/cookbook/enums/ -/de/cookbook/grafting-hotfix/ -/de/cookbook/grafting/ -/de/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/de/cookbook/immutable-entities-bytes-as-ids/ -/de/cookbook/near/ -/de/cookbook/pruning/ -/de/cookbook/subgraph-debug-forking/ -/de/cookbook/subgraph-uncrashable/ -/de/cookbook/substreams-powered-subgraphs/ -/de/cookbook/timeseries/ -/de/cookbook/transfer-to-the-graph/ -/de/developing/creating-a-subgraph/advanced/ -/de/developing/creating-a-subgraph/assemblyscript-mappings/ -/de/developing/creating-a-subgraph/graph-ts/api/ -/de/developing/creating-a-subgraph/graph-ts/common-issues/ -/de/developing/creating-a-subgraph/install-the-cli/ -/de/developing/creating-a-subgraph/ql-schema/ -/de/developing/creating-a-subgraph/starting-your-subgraph/ -/de/developing/creating-a-subgraph/subgraph-manifest/ -/de/developing/creating-a-subgraph/unit-testing-framework/ -/de/developing/deploying/deploy-using-subgraph-studio/ -/de/developing/deploying/multiple-networks/ -/de/developing/deploying/subgraph-studio-faqs/ -/de/developing/developer-faqs/ -/de/developing/developing/ -/de/developing/managing/delete-a-subgraph/ -/de/developing/managing/transfer-a-subgraph/ -/de/developing/publishing/publishing-a-subgraph/ -/de/developing/subgraphs/ -/de/developing/supported-networks/ -/de/explorer/ -/de/glossary/ -/de/indexer-tooling/firehose/ -/de/indexer-tooling/graphcast/ -/de/indexer-tooling/operating-graph-node/ -/de/indexing/ -/de/new-chain-integration/ -/de/querying/distributed-systems/ -/de/querying/graphql-api/ -/de/querying/managing-api-keys/ -/de/querying/querying-best-practices/ -/de/querying/querying-by-subgraph-id-vs-deployment-id/ -/de/querying/querying-from-an-application/ -/de/querying/querying-the-graph/ -/de/querying/querying-with-python/ -/de/quick-start/ -/de/release-notes/assemblyscript-migration-guide/ -/de/release-notes/graphql-validations-migration-guide/ -/de/roles-and-benefits/benefits/ -/de/roles-and-benefits/curating/ -/de/roles-and-benefits/delegating/ -/de/roles-and-benefits/overview/ -/de/sps/introduction/ -/de/sps/substreams-powered-subgraphs-faq/ -/de/sps/triggers-example/ -/de/sps/triggers/ -/de/substreams/ -/de/supported-network-requirements/ -/de/tap/ -/de/tokenomics/ +/de/indexing/chain-integration-overview/ +/de/indexing/introduction/ +/de/indexing/new-chain-integration/ +/de/indexing/supported-network-requirements/ +/de/indexing/tap/ +/de/indexing/tooling/firehose/ +/de/indexing/tooling/graphcast/ +/de/indexing/tooling/operating-graph-node/ +/de/resources/benefits/ +/de/resources/glossary/ +/de/resources/release-notes/assemblyscript-migration-guide/ +/de/resources/release-notes/graphql-validations-migration-guide/ +/de/resources/roles/curating/ +/de/resources/roles/delegating/ +/de/resources/tokenomics/ +/de/subgraphs/billing/ +/de/subgraphs/cookbook/arweave/ +/de/subgraphs/cookbook/avoid-eth-calls/ +/de/subgraphs/cookbook/cosmos/ +/de/subgraphs/cookbook/derivedfrom/ +/de/subgraphs/cookbook/enums/ +/de/subgraphs/cookbook/grafting-hotfix/ +/de/subgraphs/cookbook/grafting/ +/de/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/de/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/de/subgraphs/cookbook/near/ +/de/subgraphs/cookbook/pruning/ +/de/subgraphs/cookbook/subgraph-debug-forking/ +/de/subgraphs/cookbook/subgraph-uncrashable/ +/de/subgraphs/cookbook/substreams-powered-subgraphs/ +/de/subgraphs/cookbook/timeseries/ +/de/subgraphs/cookbook/transfer-to-the-graph/ +/de/subgraphs/developing/creating/advanced/ +/de/subgraphs/developing/creating/assemblyscript-mappings/ +/de/subgraphs/developing/creating/graph-ts/api/ +/de/subgraphs/developing/creating/graph-ts/common-issues/ +/de/subgraphs/developing/creating/install-the-cli/ +/de/subgraphs/developing/creating/ql-schema/ +/de/subgraphs/developing/creating/starting-your-subgraph/ +/de/subgraphs/developing/creating/subgraph-manifest/ +/de/subgraphs/developing/creating/unit-testing-framework/ +/de/subgraphs/developing/deploying/multiple-networks/ +/de/subgraphs/developing/deploying/subgraph-studio-faqs/ +/de/subgraphs/developing/deploying/using-subgraph-studio/ +/de/subgraphs/developing/developer-faqs/ +/de/subgraphs/developing/introduction/ +/de/subgraphs/developing/managing/deleting-a-subgraph/ +/de/subgraphs/developing/managing/transferring-a-subgraph/ +/de/subgraphs/developing/publishing/publishing-a-subgraph/ +/de/subgraphs/developing/subgraphs/ +/de/subgraphs/explorer/ +/de/subgraphs/querying/best-practices/ +/de/subgraphs/querying/distributed-systems/ +/de/subgraphs/querying/from-an-application/ +/de/subgraphs/querying/graphql-api/ +/de/subgraphs/querying/introduction/ +/de/subgraphs/querying/managing-api-keys/ +/de/subgraphs/querying/python/ +/de/subgraphs/querying/subgraph-id-vs-deployment-id/ +/de/subgraphs/quick-start/ +/de/substreams/introduction/ +/de/substreams/sps/introduction/ +/de/substreams/sps/substreams-powered-subgraphs-faq/ +/de/substreams/sps/triggers-example/ +/de/substreams/sps/triggers/ +/de/supported-networks/ /en/ /en/404/ /en/about/ @@ -229,79 +226,78 @@ /en/archived/arbitrum/l2-transfer-tools-faq/ /en/archived/arbitrum/l2-transfer-tools-guide/ /en/archived/sunrise/ -/en/billing/ -/en/chain-integration-overview/ /en/contracts/ -/en/cookbook/arweave/ -/en/cookbook/avoid-eth-calls/ -/en/cookbook/cosmos/ -/en/cookbook/derivedfrom/ -/en/cookbook/enums/ -/en/cookbook/grafting-hotfix/ -/en/cookbook/grafting/ -/en/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/en/cookbook/immutable-entities-bytes-as-ids/ -/en/cookbook/near/ -/en/cookbook/pruning/ -/en/cookbook/subgraph-debug-forking/ -/en/cookbook/subgraph-uncrashable/ -/en/cookbook/substreams-powered-subgraphs/ -/en/cookbook/timeseries/ -/en/cookbook/transfer-to-the-graph/ -/en/developing/creating-a-subgraph/advanced/ -/en/developing/creating-a-subgraph/assemblyscript-mappings/ -/en/developing/creating-a-subgraph/graph-ts/CHANGELOG/ -/en/developing/creating-a-subgraph/graph-ts/README/ -/en/developing/creating-a-subgraph/graph-ts/api/ -/en/developing/creating-a-subgraph/graph-ts/common-issues/ -/en/developing/creating-a-subgraph/install-the-cli/ -/en/developing/creating-a-subgraph/ql-schema/ -/en/developing/creating-a-subgraph/starting-your-subgraph/ -/en/developing/creating-a-subgraph/subgraph-manifest/ -/en/developing/creating-a-subgraph/unit-testing-framework/ -/en/developing/deploying/deploy-using-subgraph-studio/ -/en/developing/deploying/multiple-networks/ -/en/developing/deploying/subgraph-studio-faqs/ -/en/developing/developer-faqs/ -/en/developing/developing/ -/en/developing/managing/delete-a-subgraph/ -/en/developing/managing/transfer-a-subgraph/ -/en/developing/publishing/publishing-a-subgraph/ -/en/developing/subgraphs/ -/en/developing/supported-networks/ -/en/explorer/ -/en/glossary/ -/en/indexer-tooling/firehose/ -/en/indexer-tooling/graphcast/ -/en/indexer-tooling/operating-graph-node/ -/en/indexing/ -/en/new-chain-integration/ -/en/querying/distributed-systems/ -/en/querying/graph-client/README/ -/en/querying/graph-client/architecture/ -/en/querying/graph-client/live/ -/en/querying/graphql-api/ -/en/querying/managing-api-keys/ -/en/querying/querying-best-practices/ -/en/querying/querying-by-subgraph-id-vs-deployment-id/ -/en/querying/querying-from-an-application/ -/en/querying/querying-the-graph/ -/en/querying/querying-with-python/ -/en/quick-start/ -/en/release-notes/assemblyscript-migration-guide/ -/en/release-notes/graphql-validations-migration-guide/ -/en/roles-and-benefits/benefits/ -/en/roles-and-benefits/curating/ -/en/roles-and-benefits/delegating/ -/en/roles-and-benefits/overview/ -/en/sps/introduction/ -/en/sps/substreams-powered-subgraphs-faq/ -/en/sps/triggers-example/ -/en/sps/triggers/ -/en/substreams/ -/en/supported-network-requirements/ -/en/tap/ -/en/tokenomics/ +/en/indexing/chain-integration-overview/ +/en/indexing/introduction/ +/en/indexing/new-chain-integration/ +/en/indexing/supported-network-requirements/ +/en/indexing/tap/ +/en/indexing/tooling/firehose/ +/en/indexing/tooling/graphcast/ +/en/indexing/tooling/operating-graph-node/ +/en/resources/benefits/ +/en/resources/glossary/ +/en/resources/release-notes/assemblyscript-migration-guide/ +/en/resources/release-notes/graphql-validations-migration-guide/ +/en/resources/roles/curating/ +/en/resources/roles/delegating/ +/en/resources/tokenomics/ +/en/subgraphs/billing/ +/en/subgraphs/cookbook/arweave/ +/en/subgraphs/cookbook/avoid-eth-calls/ +/en/subgraphs/cookbook/cosmos/ +/en/subgraphs/cookbook/derivedfrom/ +/en/subgraphs/cookbook/enums/ +/en/subgraphs/cookbook/grafting-hotfix/ +/en/subgraphs/cookbook/grafting/ +/en/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/en/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/en/subgraphs/cookbook/near/ +/en/subgraphs/cookbook/pruning/ +/en/subgraphs/cookbook/subgraph-debug-forking/ +/en/subgraphs/cookbook/subgraph-uncrashable/ +/en/subgraphs/cookbook/substreams-powered-subgraphs/ +/en/subgraphs/cookbook/timeseries/ +/en/subgraphs/cookbook/transfer-to-the-graph/ +/en/subgraphs/developing/creating/advanced/ +/en/subgraphs/developing/creating/assemblyscript-mappings/ +/en/subgraphs/developing/creating/graph-ts/CHANGELOG/ +/en/subgraphs/developing/creating/graph-ts/README/ +/en/subgraphs/developing/creating/graph-ts/api/ +/en/subgraphs/developing/creating/graph-ts/common-issues/ +/en/subgraphs/developing/creating/install-the-cli/ +/en/subgraphs/developing/creating/ql-schema/ +/en/subgraphs/developing/creating/starting-your-subgraph/ +/en/subgraphs/developing/creating/subgraph-manifest/ +/en/subgraphs/developing/creating/unit-testing-framework/ +/en/subgraphs/developing/deploying/multiple-networks/ +/en/subgraphs/developing/deploying/subgraph-studio-faqs/ +/en/subgraphs/developing/deploying/using-subgraph-studio/ +/en/subgraphs/developing/developer-faqs/ +/en/subgraphs/developing/introduction/ +/en/subgraphs/developing/managing/deleting-a-subgraph/ +/en/subgraphs/developing/managing/transferring-a-subgraph/ +/en/subgraphs/developing/publishing/publishing-a-subgraph/ +/en/subgraphs/developing/subgraphs/ +/en/subgraphs/explorer/ +/en/subgraphs/querying/best-practices/ +/en/subgraphs/querying/distributed-systems/ +/en/subgraphs/querying/from-an-application/ +/en/subgraphs/querying/graph-client/README/ +/en/subgraphs/querying/graph-client/architecture/ +/en/subgraphs/querying/graph-client/live/ +/en/subgraphs/querying/graphql-api/ +/en/subgraphs/querying/introduction/ +/en/subgraphs/querying/managing-api-keys/ +/en/subgraphs/querying/python/ +/en/subgraphs/querying/subgraph-id-vs-deployment-id/ +/en/subgraphs/quick-start/ +/en/substreams/introduction/ +/en/substreams/sps/introduction/ +/en/substreams/sps/substreams-powered-subgraphs-faq/ +/en/substreams/sps/triggers-example/ +/en/substreams/sps/triggers/ +/en/supported-networks/ /es/ /es/404/ /es/about/ @@ -309,74 +305,73 @@ /es/archived/arbitrum/l2-transfer-tools-faq/ /es/archived/arbitrum/l2-transfer-tools-guide/ /es/archived/sunrise/ -/es/billing/ -/es/chain-integration-overview/ /es/contracts/ -/es/cookbook/arweave/ -/es/cookbook/avoid-eth-calls/ -/es/cookbook/cosmos/ -/es/cookbook/derivedfrom/ -/es/cookbook/enums/ -/es/cookbook/grafting-hotfix/ -/es/cookbook/grafting/ -/es/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/es/cookbook/immutable-entities-bytes-as-ids/ -/es/cookbook/near/ -/es/cookbook/pruning/ -/es/cookbook/subgraph-debug-forking/ -/es/cookbook/subgraph-uncrashable/ -/es/cookbook/substreams-powered-subgraphs/ -/es/cookbook/timeseries/ -/es/cookbook/transfer-to-the-graph/ -/es/developing/creating-a-subgraph/advanced/ -/es/developing/creating-a-subgraph/assemblyscript-mappings/ -/es/developing/creating-a-subgraph/graph-ts/api/ -/es/developing/creating-a-subgraph/graph-ts/common-issues/ -/es/developing/creating-a-subgraph/install-the-cli/ -/es/developing/creating-a-subgraph/ql-schema/ -/es/developing/creating-a-subgraph/starting-your-subgraph/ -/es/developing/creating-a-subgraph/subgraph-manifest/ -/es/developing/creating-a-subgraph/unit-testing-framework/ -/es/developing/deploying/deploy-using-subgraph-studio/ -/es/developing/deploying/multiple-networks/ -/es/developing/deploying/subgraph-studio-faqs/ -/es/developing/developer-faqs/ -/es/developing/developing/ -/es/developing/managing/delete-a-subgraph/ -/es/developing/managing/transfer-a-subgraph/ -/es/developing/publishing/publishing-a-subgraph/ -/es/developing/subgraphs/ -/es/developing/supported-networks/ -/es/explorer/ -/es/glossary/ -/es/indexer-tooling/firehose/ -/es/indexer-tooling/graphcast/ -/es/indexer-tooling/operating-graph-node/ -/es/indexing/ -/es/new-chain-integration/ -/es/querying/distributed-systems/ -/es/querying/graphql-api/ -/es/querying/managing-api-keys/ -/es/querying/querying-best-practices/ -/es/querying/querying-by-subgraph-id-vs-deployment-id/ -/es/querying/querying-from-an-application/ -/es/querying/querying-the-graph/ -/es/querying/querying-with-python/ -/es/quick-start/ -/es/release-notes/assemblyscript-migration-guide/ -/es/release-notes/graphql-validations-migration-guide/ -/es/roles-and-benefits/benefits/ -/es/roles-and-benefits/curating/ -/es/roles-and-benefits/delegating/ -/es/roles-and-benefits/overview/ -/es/sps/introduction/ -/es/sps/substreams-powered-subgraphs-faq/ -/es/sps/triggers-example/ -/es/sps/triggers/ -/es/substreams/ -/es/supported-network-requirements/ -/es/tap/ -/es/tokenomics/ +/es/indexing/chain-integration-overview/ +/es/indexing/introduction/ +/es/indexing/new-chain-integration/ +/es/indexing/supported-network-requirements/ +/es/indexing/tap/ +/es/indexing/tooling/firehose/ +/es/indexing/tooling/graphcast/ +/es/indexing/tooling/operating-graph-node/ +/es/resources/benefits/ +/es/resources/glossary/ +/es/resources/release-notes/assemblyscript-migration-guide/ +/es/resources/release-notes/graphql-validations-migration-guide/ +/es/resources/roles/curating/ +/es/resources/roles/delegating/ +/es/resources/tokenomics/ +/es/subgraphs/billing/ +/es/subgraphs/cookbook/arweave/ +/es/subgraphs/cookbook/avoid-eth-calls/ +/es/subgraphs/cookbook/cosmos/ +/es/subgraphs/cookbook/derivedfrom/ +/es/subgraphs/cookbook/enums/ +/es/subgraphs/cookbook/grafting-hotfix/ +/es/subgraphs/cookbook/grafting/ +/es/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/es/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/es/subgraphs/cookbook/near/ +/es/subgraphs/cookbook/pruning/ +/es/subgraphs/cookbook/subgraph-debug-forking/ +/es/subgraphs/cookbook/subgraph-uncrashable/ +/es/subgraphs/cookbook/substreams-powered-subgraphs/ +/es/subgraphs/cookbook/timeseries/ +/es/subgraphs/cookbook/transfer-to-the-graph/ +/es/subgraphs/developing/creating/advanced/ +/es/subgraphs/developing/creating/assemblyscript-mappings/ +/es/subgraphs/developing/creating/graph-ts/api/ +/es/subgraphs/developing/creating/graph-ts/common-issues/ +/es/subgraphs/developing/creating/install-the-cli/ +/es/subgraphs/developing/creating/ql-schema/ +/es/subgraphs/developing/creating/starting-your-subgraph/ +/es/subgraphs/developing/creating/subgraph-manifest/ +/es/subgraphs/developing/creating/unit-testing-framework/ +/es/subgraphs/developing/deploying/multiple-networks/ +/es/subgraphs/developing/deploying/subgraph-studio-faqs/ +/es/subgraphs/developing/deploying/using-subgraph-studio/ +/es/subgraphs/developing/developer-faqs/ +/es/subgraphs/developing/introduction/ +/es/subgraphs/developing/managing/deleting-a-subgraph/ +/es/subgraphs/developing/managing/transferring-a-subgraph/ +/es/subgraphs/developing/publishing/publishing-a-subgraph/ +/es/subgraphs/developing/subgraphs/ +/es/subgraphs/explorer/ +/es/subgraphs/querying/best-practices/ +/es/subgraphs/querying/distributed-systems/ +/es/subgraphs/querying/from-an-application/ +/es/subgraphs/querying/graphql-api/ +/es/subgraphs/querying/introduction/ +/es/subgraphs/querying/managing-api-keys/ +/es/subgraphs/querying/python/ +/es/subgraphs/querying/subgraph-id-vs-deployment-id/ +/es/subgraphs/quick-start/ +/es/substreams/introduction/ +/es/substreams/sps/introduction/ +/es/substreams/sps/substreams-powered-subgraphs-faq/ +/es/substreams/sps/triggers-example/ +/es/substreams/sps/triggers/ +/es/supported-networks/ /fr/ /fr/404/ /fr/about/ @@ -384,74 +379,73 @@ /fr/archived/arbitrum/l2-transfer-tools-faq/ /fr/archived/arbitrum/l2-transfer-tools-guide/ /fr/archived/sunrise/ -/fr/billing/ -/fr/chain-integration-overview/ /fr/contracts/ -/fr/cookbook/arweave/ -/fr/cookbook/avoid-eth-calls/ -/fr/cookbook/cosmos/ -/fr/cookbook/derivedfrom/ -/fr/cookbook/enums/ -/fr/cookbook/grafting-hotfix/ -/fr/cookbook/grafting/ -/fr/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/fr/cookbook/immutable-entities-bytes-as-ids/ -/fr/cookbook/near/ -/fr/cookbook/pruning/ -/fr/cookbook/subgraph-debug-forking/ -/fr/cookbook/subgraph-uncrashable/ -/fr/cookbook/substreams-powered-subgraphs/ -/fr/cookbook/timeseries/ -/fr/cookbook/transfer-to-the-graph/ -/fr/developing/creating-a-subgraph/advanced/ -/fr/developing/creating-a-subgraph/assemblyscript-mappings/ -/fr/developing/creating-a-subgraph/graph-ts/api/ -/fr/developing/creating-a-subgraph/graph-ts/common-issues/ -/fr/developing/creating-a-subgraph/install-the-cli/ -/fr/developing/creating-a-subgraph/ql-schema/ -/fr/developing/creating-a-subgraph/starting-your-subgraph/ -/fr/developing/creating-a-subgraph/subgraph-manifest/ -/fr/developing/creating-a-subgraph/unit-testing-framework/ -/fr/developing/deploying/deploy-using-subgraph-studio/ -/fr/developing/deploying/multiple-networks/ -/fr/developing/deploying/subgraph-studio-faqs/ -/fr/developing/developer-faqs/ -/fr/developing/developing/ -/fr/developing/managing/delete-a-subgraph/ -/fr/developing/managing/transfer-a-subgraph/ -/fr/developing/publishing/publishing-a-subgraph/ -/fr/developing/subgraphs/ -/fr/developing/supported-networks/ -/fr/explorer/ -/fr/glossary/ -/fr/indexer-tooling/firehose/ -/fr/indexer-tooling/graphcast/ -/fr/indexer-tooling/operating-graph-node/ -/fr/indexing/ -/fr/new-chain-integration/ -/fr/querying/distributed-systems/ -/fr/querying/graphql-api/ -/fr/querying/managing-api-keys/ -/fr/querying/querying-best-practices/ -/fr/querying/querying-by-subgraph-id-vs-deployment-id/ -/fr/querying/querying-from-an-application/ -/fr/querying/querying-the-graph/ -/fr/querying/querying-with-python/ -/fr/quick-start/ -/fr/release-notes/assemblyscript-migration-guide/ -/fr/release-notes/graphql-validations-migration-guide/ -/fr/roles-and-benefits/benefits/ -/fr/roles-and-benefits/curating/ -/fr/roles-and-benefits/delegating/ -/fr/roles-and-benefits/overview/ -/fr/sps/introduction/ -/fr/sps/substreams-powered-subgraphs-faq/ -/fr/sps/triggers-example/ -/fr/sps/triggers/ -/fr/substreams/ -/fr/supported-network-requirements/ -/fr/tap/ -/fr/tokenomics/ +/fr/indexing/chain-integration-overview/ +/fr/indexing/introduction/ +/fr/indexing/new-chain-integration/ +/fr/indexing/supported-network-requirements/ +/fr/indexing/tap/ +/fr/indexing/tooling/firehose/ +/fr/indexing/tooling/graphcast/ +/fr/indexing/tooling/operating-graph-node/ +/fr/resources/benefits/ +/fr/resources/glossary/ +/fr/resources/release-notes/assemblyscript-migration-guide/ +/fr/resources/release-notes/graphql-validations-migration-guide/ +/fr/resources/roles/curating/ +/fr/resources/roles/delegating/ +/fr/resources/tokenomics/ +/fr/subgraphs/billing/ +/fr/subgraphs/cookbook/arweave/ +/fr/subgraphs/cookbook/avoid-eth-calls/ +/fr/subgraphs/cookbook/cosmos/ +/fr/subgraphs/cookbook/derivedfrom/ +/fr/subgraphs/cookbook/enums/ +/fr/subgraphs/cookbook/grafting-hotfix/ +/fr/subgraphs/cookbook/grafting/ +/fr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/fr/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/fr/subgraphs/cookbook/near/ +/fr/subgraphs/cookbook/pruning/ +/fr/subgraphs/cookbook/subgraph-debug-forking/ +/fr/subgraphs/cookbook/subgraph-uncrashable/ +/fr/subgraphs/cookbook/substreams-powered-subgraphs/ +/fr/subgraphs/cookbook/timeseries/ +/fr/subgraphs/cookbook/transfer-to-the-graph/ +/fr/subgraphs/developing/creating/advanced/ +/fr/subgraphs/developing/creating/assemblyscript-mappings/ +/fr/subgraphs/developing/creating/graph-ts/api/ +/fr/subgraphs/developing/creating/graph-ts/common-issues/ +/fr/subgraphs/developing/creating/install-the-cli/ +/fr/subgraphs/developing/creating/ql-schema/ +/fr/subgraphs/developing/creating/starting-your-subgraph/ +/fr/subgraphs/developing/creating/subgraph-manifest/ +/fr/subgraphs/developing/creating/unit-testing-framework/ +/fr/subgraphs/developing/deploying/multiple-networks/ +/fr/subgraphs/developing/deploying/subgraph-studio-faqs/ +/fr/subgraphs/developing/deploying/using-subgraph-studio/ +/fr/subgraphs/developing/developer-faqs/ +/fr/subgraphs/developing/introduction/ +/fr/subgraphs/developing/managing/deleting-a-subgraph/ +/fr/subgraphs/developing/managing/transferring-a-subgraph/ +/fr/subgraphs/developing/publishing/publishing-a-subgraph/ +/fr/subgraphs/developing/subgraphs/ +/fr/subgraphs/explorer/ +/fr/subgraphs/querying/best-practices/ +/fr/subgraphs/querying/distributed-systems/ +/fr/subgraphs/querying/from-an-application/ +/fr/subgraphs/querying/graphql-api/ +/fr/subgraphs/querying/introduction/ +/fr/subgraphs/querying/managing-api-keys/ +/fr/subgraphs/querying/python/ +/fr/subgraphs/querying/subgraph-id-vs-deployment-id/ +/fr/subgraphs/quick-start/ +/fr/substreams/introduction/ +/fr/substreams/sps/introduction/ +/fr/substreams/sps/substreams-powered-subgraphs-faq/ +/fr/substreams/sps/triggers-example/ +/fr/substreams/sps/triggers/ +/fr/supported-networks/ /hi/ /hi/404/ /hi/about/ @@ -459,74 +453,73 @@ /hi/archived/arbitrum/l2-transfer-tools-faq/ /hi/archived/arbitrum/l2-transfer-tools-guide/ /hi/archived/sunrise/ -/hi/billing/ -/hi/chain-integration-overview/ /hi/contracts/ -/hi/cookbook/arweave/ -/hi/cookbook/avoid-eth-calls/ -/hi/cookbook/cosmos/ -/hi/cookbook/derivedfrom/ -/hi/cookbook/enums/ -/hi/cookbook/grafting-hotfix/ -/hi/cookbook/grafting/ -/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/hi/cookbook/immutable-entities-bytes-as-ids/ -/hi/cookbook/near/ -/hi/cookbook/pruning/ -/hi/cookbook/subgraph-debug-forking/ -/hi/cookbook/subgraph-uncrashable/ -/hi/cookbook/substreams-powered-subgraphs/ -/hi/cookbook/timeseries/ -/hi/cookbook/transfer-to-the-graph/ -/hi/developing/creating-a-subgraph/advanced/ -/hi/developing/creating-a-subgraph/assemblyscript-mappings/ -/hi/developing/creating-a-subgraph/graph-ts/api/ -/hi/developing/creating-a-subgraph/graph-ts/common-issues/ -/hi/developing/creating-a-subgraph/install-the-cli/ -/hi/developing/creating-a-subgraph/ql-schema/ -/hi/developing/creating-a-subgraph/starting-your-subgraph/ -/hi/developing/creating-a-subgraph/subgraph-manifest/ -/hi/developing/creating-a-subgraph/unit-testing-framework/ -/hi/developing/deploying/deploy-using-subgraph-studio/ -/hi/developing/deploying/multiple-networks/ -/hi/developing/deploying/subgraph-studio-faqs/ -/hi/developing/developer-faqs/ -/hi/developing/developing/ -/hi/developing/managing/delete-a-subgraph/ -/hi/developing/managing/transfer-a-subgraph/ -/hi/developing/publishing/publishing-a-subgraph/ -/hi/developing/subgraphs/ -/hi/developing/supported-networks/ -/hi/explorer/ -/hi/glossary/ -/hi/indexer-tooling/firehose/ -/hi/indexer-tooling/graphcast/ -/hi/indexer-tooling/operating-graph-node/ -/hi/indexing/ -/hi/new-chain-integration/ -/hi/querying/distributed-systems/ -/hi/querying/graphql-api/ -/hi/querying/managing-api-keys/ -/hi/querying/querying-best-practices/ -/hi/querying/querying-by-subgraph-id-vs-deployment-id/ -/hi/querying/querying-from-an-application/ -/hi/querying/querying-the-graph/ -/hi/querying/querying-with-python/ -/hi/quick-start/ -/hi/release-notes/assemblyscript-migration-guide/ -/hi/release-notes/graphql-validations-migration-guide/ -/hi/roles-and-benefits/benefits/ -/hi/roles-and-benefits/curating/ -/hi/roles-and-benefits/delegating/ -/hi/roles-and-benefits/overview/ -/hi/sps/introduction/ -/hi/sps/substreams-powered-subgraphs-faq/ -/hi/sps/triggers-example/ -/hi/sps/triggers/ -/hi/substreams/ -/hi/supported-network-requirements/ -/hi/tap/ -/hi/tokenomics/ +/hi/indexing/chain-integration-overview/ +/hi/indexing/introduction/ +/hi/indexing/new-chain-integration/ +/hi/indexing/supported-network-requirements/ +/hi/indexing/tap/ +/hi/indexing/tooling/firehose/ +/hi/indexing/tooling/graphcast/ +/hi/indexing/tooling/operating-graph-node/ +/hi/resources/benefits/ +/hi/resources/glossary/ +/hi/resources/release-notes/assemblyscript-migration-guide/ +/hi/resources/release-notes/graphql-validations-migration-guide/ +/hi/resources/roles/curating/ +/hi/resources/roles/delegating/ +/hi/resources/tokenomics/ +/hi/subgraphs/billing/ +/hi/subgraphs/cookbook/arweave/ +/hi/subgraphs/cookbook/avoid-eth-calls/ +/hi/subgraphs/cookbook/cosmos/ +/hi/subgraphs/cookbook/derivedfrom/ +/hi/subgraphs/cookbook/enums/ +/hi/subgraphs/cookbook/grafting-hotfix/ +/hi/subgraphs/cookbook/grafting/ +/hi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/hi/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/hi/subgraphs/cookbook/near/ +/hi/subgraphs/cookbook/pruning/ +/hi/subgraphs/cookbook/subgraph-debug-forking/ +/hi/subgraphs/cookbook/subgraph-uncrashable/ +/hi/subgraphs/cookbook/substreams-powered-subgraphs/ +/hi/subgraphs/cookbook/timeseries/ +/hi/subgraphs/cookbook/transfer-to-the-graph/ +/hi/subgraphs/developing/creating/advanced/ +/hi/subgraphs/developing/creating/assemblyscript-mappings/ +/hi/subgraphs/developing/creating/graph-ts/api/ +/hi/subgraphs/developing/creating/graph-ts/common-issues/ +/hi/subgraphs/developing/creating/install-the-cli/ +/hi/subgraphs/developing/creating/ql-schema/ +/hi/subgraphs/developing/creating/starting-your-subgraph/ +/hi/subgraphs/developing/creating/subgraph-manifest/ +/hi/subgraphs/developing/creating/unit-testing-framework/ +/hi/subgraphs/developing/deploying/multiple-networks/ +/hi/subgraphs/developing/deploying/subgraph-studio-faqs/ +/hi/subgraphs/developing/deploying/using-subgraph-studio/ +/hi/subgraphs/developing/developer-faqs/ +/hi/subgraphs/developing/introduction/ +/hi/subgraphs/developing/managing/deleting-a-subgraph/ +/hi/subgraphs/developing/managing/transferring-a-subgraph/ +/hi/subgraphs/developing/publishing/publishing-a-subgraph/ +/hi/subgraphs/developing/subgraphs/ +/hi/subgraphs/explorer/ +/hi/subgraphs/querying/best-practices/ +/hi/subgraphs/querying/distributed-systems/ +/hi/subgraphs/querying/from-an-application/ +/hi/subgraphs/querying/graphql-api/ +/hi/subgraphs/querying/introduction/ +/hi/subgraphs/querying/managing-api-keys/ +/hi/subgraphs/querying/python/ +/hi/subgraphs/querying/subgraph-id-vs-deployment-id/ +/hi/subgraphs/quick-start/ +/hi/substreams/introduction/ +/hi/substreams/sps/introduction/ +/hi/substreams/sps/substreams-powered-subgraphs-faq/ +/hi/substreams/sps/triggers-example/ +/hi/substreams/sps/triggers/ +/hi/supported-networks/ /it/ /it/404/ /it/about/ @@ -534,74 +527,73 @@ /it/archived/arbitrum/l2-transfer-tools-faq/ /it/archived/arbitrum/l2-transfer-tools-guide/ /it/archived/sunrise/ -/it/billing/ -/it/chain-integration-overview/ /it/contracts/ -/it/cookbook/arweave/ -/it/cookbook/avoid-eth-calls/ -/it/cookbook/cosmos/ -/it/cookbook/derivedfrom/ -/it/cookbook/enums/ -/it/cookbook/grafting-hotfix/ -/it/cookbook/grafting/ -/it/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/it/cookbook/immutable-entities-bytes-as-ids/ -/it/cookbook/near/ -/it/cookbook/pruning/ -/it/cookbook/subgraph-debug-forking/ -/it/cookbook/subgraph-uncrashable/ -/it/cookbook/substreams-powered-subgraphs/ -/it/cookbook/timeseries/ -/it/cookbook/transfer-to-the-graph/ -/it/developing/creating-a-subgraph/advanced/ -/it/developing/creating-a-subgraph/assemblyscript-mappings/ -/it/developing/creating-a-subgraph/graph-ts/api/ -/it/developing/creating-a-subgraph/graph-ts/common-issues/ -/it/developing/creating-a-subgraph/install-the-cli/ -/it/developing/creating-a-subgraph/ql-schema/ -/it/developing/creating-a-subgraph/starting-your-subgraph/ -/it/developing/creating-a-subgraph/subgraph-manifest/ -/it/developing/creating-a-subgraph/unit-testing-framework/ -/it/developing/deploying/deploy-using-subgraph-studio/ -/it/developing/deploying/multiple-networks/ -/it/developing/deploying/subgraph-studio-faqs/ -/it/developing/developer-faqs/ -/it/developing/developing/ -/it/developing/managing/delete-a-subgraph/ -/it/developing/managing/transfer-a-subgraph/ -/it/developing/publishing/publishing-a-subgraph/ -/it/developing/subgraphs/ -/it/developing/supported-networks/ -/it/explorer/ -/it/glossary/ -/it/indexer-tooling/firehose/ -/it/indexer-tooling/graphcast/ -/it/indexer-tooling/operating-graph-node/ -/it/indexing/ -/it/new-chain-integration/ -/it/querying/distributed-systems/ -/it/querying/graphql-api/ -/it/querying/managing-api-keys/ -/it/querying/querying-best-practices/ -/it/querying/querying-by-subgraph-id-vs-deployment-id/ -/it/querying/querying-from-an-application/ -/it/querying/querying-the-graph/ -/it/querying/querying-with-python/ -/it/quick-start/ -/it/release-notes/assemblyscript-migration-guide/ -/it/release-notes/graphql-validations-migration-guide/ -/it/roles-and-benefits/benefits/ -/it/roles-and-benefits/curating/ -/it/roles-and-benefits/delegating/ -/it/roles-and-benefits/overview/ -/it/sps/introduction/ -/it/sps/substreams-powered-subgraphs-faq/ -/it/sps/triggers-example/ -/it/sps/triggers/ -/it/substreams/ -/it/supported-network-requirements/ -/it/tap/ -/it/tokenomics/ +/it/indexing/chain-integration-overview/ +/it/indexing/introduction/ +/it/indexing/new-chain-integration/ +/it/indexing/supported-network-requirements/ +/it/indexing/tap/ +/it/indexing/tooling/firehose/ +/it/indexing/tooling/graphcast/ +/it/indexing/tooling/operating-graph-node/ +/it/resources/benefits/ +/it/resources/glossary/ +/it/resources/release-notes/assemblyscript-migration-guide/ +/it/resources/release-notes/graphql-validations-migration-guide/ +/it/resources/roles/curating/ +/it/resources/roles/delegating/ +/it/resources/tokenomics/ +/it/subgraphs/billing/ +/it/subgraphs/cookbook/arweave/ +/it/subgraphs/cookbook/avoid-eth-calls/ +/it/subgraphs/cookbook/cosmos/ +/it/subgraphs/cookbook/derivedfrom/ +/it/subgraphs/cookbook/enums/ +/it/subgraphs/cookbook/grafting-hotfix/ +/it/subgraphs/cookbook/grafting/ +/it/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/it/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/it/subgraphs/cookbook/near/ +/it/subgraphs/cookbook/pruning/ +/it/subgraphs/cookbook/subgraph-debug-forking/ +/it/subgraphs/cookbook/subgraph-uncrashable/ +/it/subgraphs/cookbook/substreams-powered-subgraphs/ +/it/subgraphs/cookbook/timeseries/ +/it/subgraphs/cookbook/transfer-to-the-graph/ +/it/subgraphs/developing/creating/advanced/ +/it/subgraphs/developing/creating/assemblyscript-mappings/ +/it/subgraphs/developing/creating/graph-ts/api/ +/it/subgraphs/developing/creating/graph-ts/common-issues/ +/it/subgraphs/developing/creating/install-the-cli/ +/it/subgraphs/developing/creating/ql-schema/ +/it/subgraphs/developing/creating/starting-your-subgraph/ +/it/subgraphs/developing/creating/subgraph-manifest/ +/it/subgraphs/developing/creating/unit-testing-framework/ +/it/subgraphs/developing/deploying/multiple-networks/ +/it/subgraphs/developing/deploying/subgraph-studio-faqs/ +/it/subgraphs/developing/deploying/using-subgraph-studio/ +/it/subgraphs/developing/developer-faqs/ +/it/subgraphs/developing/introduction/ +/it/subgraphs/developing/managing/deleting-a-subgraph/ +/it/subgraphs/developing/managing/transferring-a-subgraph/ +/it/subgraphs/developing/publishing/publishing-a-subgraph/ +/it/subgraphs/developing/subgraphs/ +/it/subgraphs/explorer/ +/it/subgraphs/querying/best-practices/ +/it/subgraphs/querying/distributed-systems/ +/it/subgraphs/querying/from-an-application/ +/it/subgraphs/querying/graphql-api/ +/it/subgraphs/querying/introduction/ +/it/subgraphs/querying/managing-api-keys/ +/it/subgraphs/querying/python/ +/it/subgraphs/querying/subgraph-id-vs-deployment-id/ +/it/subgraphs/quick-start/ +/it/substreams/introduction/ +/it/substreams/sps/introduction/ +/it/substreams/sps/substreams-powered-subgraphs-faq/ +/it/substreams/sps/triggers-example/ +/it/substreams/sps/triggers/ +/it/supported-networks/ /ja/ /ja/404/ /ja/about/ @@ -609,147 +601,145 @@ /ja/archived/arbitrum/l2-transfer-tools-faq/ /ja/archived/arbitrum/l2-transfer-tools-guide/ /ja/archived/sunrise/ -/ja/billing/ -/ja/chain-integration-overview/ /ja/contracts/ -/ja/cookbook/arweave/ -/ja/cookbook/avoid-eth-calls/ -/ja/cookbook/cosmos/ -/ja/cookbook/derivedfrom/ -/ja/cookbook/enums/ -/ja/cookbook/grafting-hotfix/ -/ja/cookbook/grafting/ -/ja/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/ja/cookbook/immutable-entities-bytes-as-ids/ -/ja/cookbook/near/ -/ja/cookbook/pruning/ -/ja/cookbook/subgraph-debug-forking/ -/ja/cookbook/subgraph-uncrashable/ -/ja/cookbook/substreams-powered-subgraphs/ -/ja/cookbook/timeseries/ -/ja/cookbook/transfer-to-the-graph/ -/ja/developing/creating-a-subgraph/advanced/ -/ja/developing/creating-a-subgraph/assemblyscript-mappings/ -/ja/developing/creating-a-subgraph/graph-ts/api/ -/ja/developing/creating-a-subgraph/graph-ts/common-issues/ -/ja/developing/creating-a-subgraph/install-the-cli/ -/ja/developing/creating-a-subgraph/ql-schema/ -/ja/developing/creating-a-subgraph/starting-your-subgraph/ -/ja/developing/creating-a-subgraph/subgraph-manifest/ -/ja/developing/creating-a-subgraph/unit-testing-framework/ -/ja/developing/deploying/deploy-using-subgraph-studio/ -/ja/developing/deploying/multiple-networks/ -/ja/developing/deploying/subgraph-studio-faqs/ -/ja/developing/developer-faqs/ -/ja/developing/developing/ -/ja/developing/managing/delete-a-subgraph/ -/ja/developing/managing/transfer-a-subgraph/ -/ja/developing/publishing/publishing-a-subgraph/ -/ja/developing/subgraphs/ -/ja/developing/supported-networks/ -/ja/explorer/ -/ja/glossary/ -/ja/indexer-tooling/firehose/ -/ja/indexer-tooling/graphcast/ -/ja/indexer-tooling/operating-graph-node/ -/ja/indexing/ -/ja/new-chain-integration/ -/ja/querying/distributed-systems/ -/ja/querying/graphql-api/ -/ja/querying/managing-api-keys/ -/ja/querying/querying-best-practices/ -/ja/querying/querying-by-subgraph-id-vs-deployment-id/ -/ja/querying/querying-from-an-application/ -/ja/querying/querying-the-graph/ -/ja/querying/querying-with-python/ -/ja/quick-start/ -/ja/release-notes/assemblyscript-migration-guide/ -/ja/release-notes/graphql-validations-migration-guide/ -/ja/roles-and-benefits/benefits/ -/ja/roles-and-benefits/curating/ -/ja/roles-and-benefits/delegating/ -/ja/roles-and-benefits/overview/ -/ja/sps/introduction/ -/ja/sps/substreams-powered-subgraphs-faq/ -/ja/sps/triggers-example/ -/ja/sps/triggers/ -/ja/substreams/ -/ja/supported-network-requirements/ -/ja/tap/ -/ja/tokenomics/ +/ja/indexing/chain-integration-overview/ +/ja/indexing/introduction/ +/ja/indexing/new-chain-integration/ +/ja/indexing/supported-network-requirements/ +/ja/indexing/tap/ +/ja/indexing/tooling/firehose/ +/ja/indexing/tooling/graphcast/ +/ja/indexing/tooling/operating-graph-node/ +/ja/resources/benefits/ +/ja/resources/glossary/ +/ja/resources/release-notes/assemblyscript-migration-guide/ +/ja/resources/release-notes/graphql-validations-migration-guide/ +/ja/resources/roles/curating/ +/ja/resources/roles/delegating/ +/ja/resources/tokenomics/ +/ja/subgraphs/billing/ +/ja/subgraphs/cookbook/arweave/ +/ja/subgraphs/cookbook/avoid-eth-calls/ +/ja/subgraphs/cookbook/cosmos/ +/ja/subgraphs/cookbook/derivedfrom/ +/ja/subgraphs/cookbook/enums/ +/ja/subgraphs/cookbook/grafting-hotfix/ +/ja/subgraphs/cookbook/grafting/ +/ja/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/ja/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/ja/subgraphs/cookbook/near/ +/ja/subgraphs/cookbook/pruning/ +/ja/subgraphs/cookbook/subgraph-debug-forking/ +/ja/subgraphs/cookbook/subgraph-uncrashable/ +/ja/subgraphs/cookbook/substreams-powered-subgraphs/ +/ja/subgraphs/cookbook/timeseries/ +/ja/subgraphs/cookbook/transfer-to-the-graph/ +/ja/subgraphs/developing/creating/advanced/ +/ja/subgraphs/developing/creating/assemblyscript-mappings/ +/ja/subgraphs/developing/creating/graph-ts/api/ +/ja/subgraphs/developing/creating/graph-ts/common-issues/ +/ja/subgraphs/developing/creating/install-the-cli/ +/ja/subgraphs/developing/creating/ql-schema/ +/ja/subgraphs/developing/creating/starting-your-subgraph/ +/ja/subgraphs/developing/creating/subgraph-manifest/ +/ja/subgraphs/developing/creating/unit-testing-framework/ +/ja/subgraphs/developing/deploying/multiple-networks/ +/ja/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ja/subgraphs/developing/deploying/using-subgraph-studio/ +/ja/subgraphs/developing/developer-faqs/ +/ja/subgraphs/developing/introduction/ +/ja/subgraphs/developing/managing/deleting-a-subgraph/ +/ja/subgraphs/developing/managing/transferring-a-subgraph/ +/ja/subgraphs/developing/publishing/publishing-a-subgraph/ +/ja/subgraphs/developing/subgraphs/ +/ja/subgraphs/explorer/ +/ja/subgraphs/querying/best-practices/ +/ja/subgraphs/querying/distributed-systems/ +/ja/subgraphs/querying/from-an-application/ +/ja/subgraphs/querying/graphql-api/ +/ja/subgraphs/querying/introduction/ +/ja/subgraphs/querying/managing-api-keys/ +/ja/subgraphs/querying/python/ +/ja/subgraphs/querying/subgraph-id-vs-deployment-id/ +/ja/subgraphs/quick-start/ +/ja/substreams/introduction/ +/ja/substreams/sps/introduction/ +/ja/substreams/sps/substreams-powered-subgraphs-faq/ +/ja/substreams/sps/triggers-example/ +/ja/substreams/sps/triggers/ +/ja/supported-networks/ /ko/about/ /ko/archived/arbitrum/arbitrum-faq/ /ko/archived/arbitrum/l2-transfer-tools-faq/ /ko/archived/arbitrum/l2-transfer-tools-guide/ /ko/archived/sunrise/ -/ko/billing/ -/ko/chain-integration-overview/ /ko/contracts/ -/ko/cookbook/arweave/ -/ko/cookbook/avoid-eth-calls/ -/ko/cookbook/cosmos/ -/ko/cookbook/derivedfrom/ -/ko/cookbook/enums/ -/ko/cookbook/grafting-hotfix/ -/ko/cookbook/grafting/ -/ko/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/ko/cookbook/immutable-entities-bytes-as-ids/ -/ko/cookbook/near/ -/ko/cookbook/pruning/ -/ko/cookbook/subgraph-debug-forking/ -/ko/cookbook/subgraph-uncrashable/ -/ko/cookbook/substreams-powered-subgraphs/ -/ko/cookbook/timeseries/ -/ko/cookbook/transfer-to-the-graph/ -/ko/developing/creating-a-subgraph/advanced/ -/ko/developing/creating-a-subgraph/assemblyscript-mappings/ -/ko/developing/creating-a-subgraph/graph-ts/api/ -/ko/developing/creating-a-subgraph/graph-ts/common-issues/ -/ko/developing/creating-a-subgraph/install-the-cli/ -/ko/developing/creating-a-subgraph/ql-schema/ -/ko/developing/creating-a-subgraph/starting-your-subgraph/ -/ko/developing/creating-a-subgraph/subgraph-manifest/ -/ko/developing/creating-a-subgraph/unit-testing-framework/ -/ko/developing/deploying/deploy-using-subgraph-studio/ -/ko/developing/deploying/multiple-networks/ -/ko/developing/deploying/subgraph-studio-faqs/ -/ko/developing/developer-faqs/ -/ko/developing/developing/ -/ko/developing/managing/delete-a-subgraph/ -/ko/developing/managing/transfer-a-subgraph/ -/ko/developing/publishing/publishing-a-subgraph/ -/ko/developing/subgraphs/ -/ko/developing/supported-networks/ -/ko/explorer/ -/ko/glossary/ -/ko/indexer-tooling/firehose/ -/ko/indexer-tooling/graphcast/ -/ko/indexer-tooling/operating-graph-node/ -/ko/indexing/ -/ko/new-chain-integration/ -/ko/querying/distributed-systems/ -/ko/querying/graphql-api/ -/ko/querying/managing-api-keys/ -/ko/querying/querying-best-practices/ -/ko/querying/querying-by-subgraph-id-vs-deployment-id/ -/ko/querying/querying-from-an-application/ -/ko/querying/querying-the-graph/ -/ko/querying/querying-with-python/ -/ko/quick-start/ -/ko/release-notes/assemblyscript-migration-guide/ -/ko/release-notes/graphql-validations-migration-guide/ -/ko/roles-and-benefits/benefits/ -/ko/roles-and-benefits/curating/ -/ko/roles-and-benefits/delegating/ -/ko/roles-and-benefits/overview/ -/ko/sps/introduction/ -/ko/sps/substreams-powered-subgraphs-faq/ -/ko/sps/triggers-example/ -/ko/sps/triggers/ -/ko/substreams/ -/ko/supported-network-requirements/ -/ko/tap/ -/ko/tokenomics/ +/ko/indexing/chain-integration-overview/ +/ko/indexing/introduction/ +/ko/indexing/new-chain-integration/ +/ko/indexing/supported-network-requirements/ +/ko/indexing/tap/ +/ko/indexing/tooling/firehose/ +/ko/indexing/tooling/graphcast/ +/ko/indexing/tooling/operating-graph-node/ +/ko/resources/benefits/ +/ko/resources/glossary/ +/ko/resources/release-notes/assemblyscript-migration-guide/ +/ko/resources/release-notes/graphql-validations-migration-guide/ +/ko/resources/roles/curating/ +/ko/resources/roles/delegating/ +/ko/resources/tokenomics/ +/ko/subgraphs/billing/ +/ko/subgraphs/cookbook/arweave/ +/ko/subgraphs/cookbook/avoid-eth-calls/ +/ko/subgraphs/cookbook/cosmos/ +/ko/subgraphs/cookbook/derivedfrom/ +/ko/subgraphs/cookbook/enums/ +/ko/subgraphs/cookbook/grafting-hotfix/ +/ko/subgraphs/cookbook/grafting/ +/ko/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/ko/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/ko/subgraphs/cookbook/near/ +/ko/subgraphs/cookbook/pruning/ +/ko/subgraphs/cookbook/subgraph-debug-forking/ +/ko/subgraphs/cookbook/subgraph-uncrashable/ +/ko/subgraphs/cookbook/substreams-powered-subgraphs/ +/ko/subgraphs/cookbook/timeseries/ +/ko/subgraphs/cookbook/transfer-to-the-graph/ +/ko/subgraphs/developing/creating/advanced/ +/ko/subgraphs/developing/creating/assemblyscript-mappings/ +/ko/subgraphs/developing/creating/graph-ts/api/ +/ko/subgraphs/developing/creating/graph-ts/common-issues/ +/ko/subgraphs/developing/creating/install-the-cli/ +/ko/subgraphs/developing/creating/ql-schema/ +/ko/subgraphs/developing/creating/starting-your-subgraph/ +/ko/subgraphs/developing/creating/subgraph-manifest/ +/ko/subgraphs/developing/creating/unit-testing-framework/ +/ko/subgraphs/developing/deploying/multiple-networks/ +/ko/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ko/subgraphs/developing/deploying/using-subgraph-studio/ +/ko/subgraphs/developing/developer-faqs/ +/ko/subgraphs/developing/introduction/ +/ko/subgraphs/developing/managing/deleting-a-subgraph/ +/ko/subgraphs/developing/managing/transferring-a-subgraph/ +/ko/subgraphs/developing/publishing/publishing-a-subgraph/ +/ko/subgraphs/developing/subgraphs/ +/ko/subgraphs/explorer/ +/ko/subgraphs/querying/best-practices/ +/ko/subgraphs/querying/distributed-systems/ +/ko/subgraphs/querying/from-an-application/ +/ko/subgraphs/querying/graphql-api/ +/ko/subgraphs/querying/introduction/ +/ko/subgraphs/querying/managing-api-keys/ +/ko/subgraphs/querying/python/ +/ko/subgraphs/querying/subgraph-id-vs-deployment-id/ +/ko/subgraphs/quick-start/ +/ko/substreams/introduction/ +/ko/substreams/sps/introduction/ +/ko/substreams/sps/substreams-powered-subgraphs-faq/ +/ko/substreams/sps/triggers-example/ +/ko/substreams/sps/triggers/ +/ko/supported-networks/ /mr/ /mr/404/ /mr/about/ @@ -757,220 +747,217 @@ /mr/archived/arbitrum/l2-transfer-tools-faq/ /mr/archived/arbitrum/l2-transfer-tools-guide/ /mr/archived/sunrise/ -/mr/billing/ -/mr/chain-integration-overview/ /mr/contracts/ -/mr/cookbook/arweave/ -/mr/cookbook/avoid-eth-calls/ -/mr/cookbook/cosmos/ -/mr/cookbook/derivedfrom/ -/mr/cookbook/enums/ -/mr/cookbook/grafting-hotfix/ -/mr/cookbook/grafting/ -/mr/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/mr/cookbook/immutable-entities-bytes-as-ids/ -/mr/cookbook/near/ -/mr/cookbook/pruning/ -/mr/cookbook/subgraph-debug-forking/ -/mr/cookbook/subgraph-uncrashable/ -/mr/cookbook/substreams-powered-subgraphs/ -/mr/cookbook/timeseries/ -/mr/cookbook/transfer-to-the-graph/ -/mr/developing/creating-a-subgraph/advanced/ -/mr/developing/creating-a-subgraph/assemblyscript-mappings/ -/mr/developing/creating-a-subgraph/graph-ts/api/ -/mr/developing/creating-a-subgraph/graph-ts/common-issues/ -/mr/developing/creating-a-subgraph/install-the-cli/ -/mr/developing/creating-a-subgraph/ql-schema/ -/mr/developing/creating-a-subgraph/starting-your-subgraph/ -/mr/developing/creating-a-subgraph/subgraph-manifest/ -/mr/developing/creating-a-subgraph/unit-testing-framework/ -/mr/developing/deploying/deploy-using-subgraph-studio/ -/mr/developing/deploying/multiple-networks/ -/mr/developing/deploying/subgraph-studio-faqs/ -/mr/developing/developer-faqs/ -/mr/developing/developing/ -/mr/developing/managing/delete-a-subgraph/ -/mr/developing/managing/transfer-a-subgraph/ -/mr/developing/publishing/publishing-a-subgraph/ -/mr/developing/subgraphs/ -/mr/developing/supported-networks/ -/mr/explorer/ -/mr/glossary/ -/mr/indexer-tooling/firehose/ -/mr/indexer-tooling/graphcast/ -/mr/indexer-tooling/operating-graph-node/ -/mr/indexing/ -/mr/new-chain-integration/ -/mr/querying/distributed-systems/ -/mr/querying/graphql-api/ -/mr/querying/managing-api-keys/ -/mr/querying/querying-best-practices/ -/mr/querying/querying-by-subgraph-id-vs-deployment-id/ -/mr/querying/querying-from-an-application/ -/mr/querying/querying-the-graph/ -/mr/querying/querying-with-python/ -/mr/quick-start/ -/mr/release-notes/assemblyscript-migration-guide/ -/mr/release-notes/graphql-validations-migration-guide/ -/mr/roles-and-benefits/benefits/ -/mr/roles-and-benefits/curating/ -/mr/roles-and-benefits/delegating/ -/mr/roles-and-benefits/overview/ -/mr/sps/introduction/ -/mr/sps/substreams-powered-subgraphs-faq/ -/mr/sps/triggers-example/ -/mr/sps/triggers/ -/mr/substreams/ -/mr/supported-network-requirements/ -/mr/tap/ -/mr/tokenomics/ +/mr/indexing/chain-integration-overview/ +/mr/indexing/introduction/ +/mr/indexing/new-chain-integration/ +/mr/indexing/supported-network-requirements/ +/mr/indexing/tap/ +/mr/indexing/tooling/firehose/ +/mr/indexing/tooling/graphcast/ +/mr/indexing/tooling/operating-graph-node/ +/mr/resources/benefits/ +/mr/resources/glossary/ +/mr/resources/release-notes/assemblyscript-migration-guide/ +/mr/resources/release-notes/graphql-validations-migration-guide/ +/mr/resources/roles/curating/ +/mr/resources/roles/delegating/ +/mr/resources/tokenomics/ +/mr/subgraphs/billing/ +/mr/subgraphs/cookbook/arweave/ +/mr/subgraphs/cookbook/avoid-eth-calls/ +/mr/subgraphs/cookbook/cosmos/ +/mr/subgraphs/cookbook/derivedfrom/ +/mr/subgraphs/cookbook/enums/ +/mr/subgraphs/cookbook/grafting-hotfix/ +/mr/subgraphs/cookbook/grafting/ +/mr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/mr/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/mr/subgraphs/cookbook/near/ +/mr/subgraphs/cookbook/pruning/ +/mr/subgraphs/cookbook/subgraph-debug-forking/ +/mr/subgraphs/cookbook/subgraph-uncrashable/ +/mr/subgraphs/cookbook/substreams-powered-subgraphs/ +/mr/subgraphs/cookbook/timeseries/ +/mr/subgraphs/cookbook/transfer-to-the-graph/ +/mr/subgraphs/developing/creating/advanced/ +/mr/subgraphs/developing/creating/assemblyscript-mappings/ +/mr/subgraphs/developing/creating/graph-ts/api/ +/mr/subgraphs/developing/creating/graph-ts/common-issues/ +/mr/subgraphs/developing/creating/install-the-cli/ +/mr/subgraphs/developing/creating/ql-schema/ +/mr/subgraphs/developing/creating/starting-your-subgraph/ +/mr/subgraphs/developing/creating/subgraph-manifest/ +/mr/subgraphs/developing/creating/unit-testing-framework/ +/mr/subgraphs/developing/deploying/multiple-networks/ +/mr/subgraphs/developing/deploying/subgraph-studio-faqs/ +/mr/subgraphs/developing/deploying/using-subgraph-studio/ +/mr/subgraphs/developing/developer-faqs/ +/mr/subgraphs/developing/introduction/ +/mr/subgraphs/developing/managing/deleting-a-subgraph/ +/mr/subgraphs/developing/managing/transferring-a-subgraph/ +/mr/subgraphs/developing/publishing/publishing-a-subgraph/ +/mr/subgraphs/developing/subgraphs/ +/mr/subgraphs/explorer/ +/mr/subgraphs/querying/best-practices/ +/mr/subgraphs/querying/distributed-systems/ +/mr/subgraphs/querying/from-an-application/ +/mr/subgraphs/querying/graphql-api/ +/mr/subgraphs/querying/introduction/ +/mr/subgraphs/querying/managing-api-keys/ +/mr/subgraphs/querying/python/ +/mr/subgraphs/querying/subgraph-id-vs-deployment-id/ +/mr/subgraphs/quick-start/ +/mr/substreams/introduction/ +/mr/substreams/sps/introduction/ +/mr/substreams/sps/substreams-powered-subgraphs-faq/ +/mr/substreams/sps/triggers-example/ +/mr/substreams/sps/triggers/ +/mr/supported-networks/ /nl/about/ /nl/archived/arbitrum/arbitrum-faq/ /nl/archived/arbitrum/l2-transfer-tools-faq/ /nl/archived/arbitrum/l2-transfer-tools-guide/ /nl/archived/sunrise/ -/nl/billing/ -/nl/chain-integration-overview/ /nl/contracts/ -/nl/cookbook/arweave/ -/nl/cookbook/avoid-eth-calls/ -/nl/cookbook/cosmos/ -/nl/cookbook/derivedfrom/ -/nl/cookbook/enums/ -/nl/cookbook/grafting-hotfix/ -/nl/cookbook/grafting/ -/nl/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/nl/cookbook/immutable-entities-bytes-as-ids/ -/nl/cookbook/near/ -/nl/cookbook/pruning/ -/nl/cookbook/subgraph-debug-forking/ -/nl/cookbook/subgraph-uncrashable/ -/nl/cookbook/substreams-powered-subgraphs/ -/nl/cookbook/timeseries/ -/nl/cookbook/transfer-to-the-graph/ -/nl/developing/creating-a-subgraph/advanced/ -/nl/developing/creating-a-subgraph/assemblyscript-mappings/ -/nl/developing/creating-a-subgraph/graph-ts/api/ -/nl/developing/creating-a-subgraph/graph-ts/common-issues/ -/nl/developing/creating-a-subgraph/install-the-cli/ -/nl/developing/creating-a-subgraph/ql-schema/ -/nl/developing/creating-a-subgraph/starting-your-subgraph/ -/nl/developing/creating-a-subgraph/subgraph-manifest/ -/nl/developing/creating-a-subgraph/unit-testing-framework/ -/nl/developing/deploying/deploy-using-subgraph-studio/ -/nl/developing/deploying/multiple-networks/ -/nl/developing/deploying/subgraph-studio-faqs/ -/nl/developing/developer-faqs/ -/nl/developing/developing/ -/nl/developing/managing/delete-a-subgraph/ -/nl/developing/managing/transfer-a-subgraph/ -/nl/developing/publishing/publishing-a-subgraph/ -/nl/developing/subgraphs/ -/nl/developing/supported-networks/ -/nl/explorer/ -/nl/glossary/ -/nl/indexer-tooling/firehose/ -/nl/indexer-tooling/graphcast/ -/nl/indexer-tooling/operating-graph-node/ -/nl/indexing/ -/nl/new-chain-integration/ -/nl/querying/distributed-systems/ -/nl/querying/graphql-api/ -/nl/querying/managing-api-keys/ -/nl/querying/querying-best-practices/ -/nl/querying/querying-by-subgraph-id-vs-deployment-id/ -/nl/querying/querying-from-an-application/ -/nl/querying/querying-the-graph/ -/nl/querying/querying-with-python/ -/nl/quick-start/ -/nl/release-notes/assemblyscript-migration-guide/ -/nl/release-notes/graphql-validations-migration-guide/ -/nl/roles-and-benefits/benefits/ -/nl/roles-and-benefits/curating/ -/nl/roles-and-benefits/delegating/ -/nl/roles-and-benefits/overview/ -/nl/sps/introduction/ -/nl/sps/substreams-powered-subgraphs-faq/ -/nl/sps/triggers-example/ -/nl/sps/triggers/ -/nl/substreams/ -/nl/supported-network-requirements/ -/nl/tap/ -/nl/tokenomics/ +/nl/indexing/chain-integration-overview/ +/nl/indexing/introduction/ +/nl/indexing/new-chain-integration/ +/nl/indexing/supported-network-requirements/ +/nl/indexing/tap/ +/nl/indexing/tooling/firehose/ +/nl/indexing/tooling/graphcast/ +/nl/indexing/tooling/operating-graph-node/ +/nl/resources/benefits/ +/nl/resources/glossary/ +/nl/resources/release-notes/assemblyscript-migration-guide/ +/nl/resources/release-notes/graphql-validations-migration-guide/ +/nl/resources/roles/curating/ +/nl/resources/roles/delegating/ +/nl/resources/tokenomics/ +/nl/subgraphs/billing/ +/nl/subgraphs/cookbook/arweave/ +/nl/subgraphs/cookbook/avoid-eth-calls/ +/nl/subgraphs/cookbook/cosmos/ +/nl/subgraphs/cookbook/derivedfrom/ +/nl/subgraphs/cookbook/enums/ +/nl/subgraphs/cookbook/grafting-hotfix/ +/nl/subgraphs/cookbook/grafting/ +/nl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/nl/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/nl/subgraphs/cookbook/near/ +/nl/subgraphs/cookbook/pruning/ +/nl/subgraphs/cookbook/subgraph-debug-forking/ +/nl/subgraphs/cookbook/subgraph-uncrashable/ +/nl/subgraphs/cookbook/substreams-powered-subgraphs/ +/nl/subgraphs/cookbook/timeseries/ +/nl/subgraphs/cookbook/transfer-to-the-graph/ +/nl/subgraphs/developing/creating/advanced/ +/nl/subgraphs/developing/creating/assemblyscript-mappings/ +/nl/subgraphs/developing/creating/graph-ts/api/ +/nl/subgraphs/developing/creating/graph-ts/common-issues/ +/nl/subgraphs/developing/creating/install-the-cli/ +/nl/subgraphs/developing/creating/ql-schema/ +/nl/subgraphs/developing/creating/starting-your-subgraph/ +/nl/subgraphs/developing/creating/subgraph-manifest/ +/nl/subgraphs/developing/creating/unit-testing-framework/ +/nl/subgraphs/developing/deploying/multiple-networks/ +/nl/subgraphs/developing/deploying/subgraph-studio-faqs/ +/nl/subgraphs/developing/deploying/using-subgraph-studio/ +/nl/subgraphs/developing/developer-faqs/ +/nl/subgraphs/developing/introduction/ +/nl/subgraphs/developing/managing/deleting-a-subgraph/ +/nl/subgraphs/developing/managing/transferring-a-subgraph/ +/nl/subgraphs/developing/publishing/publishing-a-subgraph/ +/nl/subgraphs/developing/subgraphs/ +/nl/subgraphs/explorer/ +/nl/subgraphs/querying/best-practices/ +/nl/subgraphs/querying/distributed-systems/ +/nl/subgraphs/querying/from-an-application/ +/nl/subgraphs/querying/graphql-api/ +/nl/subgraphs/querying/introduction/ +/nl/subgraphs/querying/managing-api-keys/ +/nl/subgraphs/querying/python/ +/nl/subgraphs/querying/subgraph-id-vs-deployment-id/ +/nl/subgraphs/quick-start/ +/nl/substreams/introduction/ +/nl/substreams/sps/introduction/ +/nl/substreams/sps/substreams-powered-subgraphs-faq/ +/nl/substreams/sps/triggers-example/ +/nl/substreams/sps/triggers/ +/nl/supported-networks/ /pl/about/ /pl/archived/arbitrum/arbitrum-faq/ /pl/archived/arbitrum/l2-transfer-tools-faq/ /pl/archived/arbitrum/l2-transfer-tools-guide/ /pl/archived/sunrise/ -/pl/billing/ -/pl/chain-integration-overview/ /pl/contracts/ -/pl/cookbook/arweave/ -/pl/cookbook/avoid-eth-calls/ -/pl/cookbook/cosmos/ -/pl/cookbook/derivedfrom/ -/pl/cookbook/enums/ -/pl/cookbook/grafting-hotfix/ -/pl/cookbook/grafting/ -/pl/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/pl/cookbook/immutable-entities-bytes-as-ids/ -/pl/cookbook/near/ -/pl/cookbook/pruning/ -/pl/cookbook/subgraph-debug-forking/ -/pl/cookbook/subgraph-uncrashable/ -/pl/cookbook/substreams-powered-subgraphs/ -/pl/cookbook/timeseries/ -/pl/cookbook/transfer-to-the-graph/ -/pl/developing/creating-a-subgraph/advanced/ -/pl/developing/creating-a-subgraph/assemblyscript-mappings/ -/pl/developing/creating-a-subgraph/graph-ts/api/ -/pl/developing/creating-a-subgraph/graph-ts/common-issues/ -/pl/developing/creating-a-subgraph/install-the-cli/ -/pl/developing/creating-a-subgraph/ql-schema/ -/pl/developing/creating-a-subgraph/starting-your-subgraph/ -/pl/developing/creating-a-subgraph/subgraph-manifest/ -/pl/developing/creating-a-subgraph/unit-testing-framework/ -/pl/developing/deploying/deploy-using-subgraph-studio/ -/pl/developing/deploying/multiple-networks/ -/pl/developing/deploying/subgraph-studio-faqs/ -/pl/developing/developer-faqs/ -/pl/developing/developing/ -/pl/developing/managing/delete-a-subgraph/ -/pl/developing/managing/transfer-a-subgraph/ -/pl/developing/publishing/publishing-a-subgraph/ -/pl/developing/subgraphs/ -/pl/developing/supported-networks/ -/pl/explorer/ -/pl/glossary/ -/pl/indexer-tooling/firehose/ -/pl/indexer-tooling/graphcast/ -/pl/indexer-tooling/operating-graph-node/ -/pl/indexing/ -/pl/new-chain-integration/ -/pl/querying/distributed-systems/ -/pl/querying/graphql-api/ -/pl/querying/managing-api-keys/ -/pl/querying/querying-best-practices/ -/pl/querying/querying-by-subgraph-id-vs-deployment-id/ -/pl/querying/querying-from-an-application/ -/pl/querying/querying-the-graph/ -/pl/querying/querying-with-python/ -/pl/quick-start/ -/pl/release-notes/assemblyscript-migration-guide/ -/pl/release-notes/graphql-validations-migration-guide/ -/pl/roles-and-benefits/benefits/ -/pl/roles-and-benefits/curating/ -/pl/roles-and-benefits/delegating/ -/pl/roles-and-benefits/overview/ -/pl/sps/introduction/ -/pl/sps/substreams-powered-subgraphs-faq/ -/pl/sps/triggers-example/ -/pl/sps/triggers/ -/pl/substreams/ -/pl/supported-network-requirements/ -/pl/tap/ -/pl/tokenomics/ +/pl/indexing/chain-integration-overview/ +/pl/indexing/introduction/ +/pl/indexing/new-chain-integration/ +/pl/indexing/supported-network-requirements/ +/pl/indexing/tap/ +/pl/indexing/tooling/firehose/ +/pl/indexing/tooling/graphcast/ +/pl/indexing/tooling/operating-graph-node/ +/pl/resources/benefits/ +/pl/resources/glossary/ +/pl/resources/release-notes/assemblyscript-migration-guide/ +/pl/resources/release-notes/graphql-validations-migration-guide/ +/pl/resources/roles/curating/ +/pl/resources/roles/delegating/ +/pl/resources/tokenomics/ +/pl/subgraphs/billing/ +/pl/subgraphs/cookbook/arweave/ +/pl/subgraphs/cookbook/avoid-eth-calls/ +/pl/subgraphs/cookbook/cosmos/ +/pl/subgraphs/cookbook/derivedfrom/ +/pl/subgraphs/cookbook/enums/ +/pl/subgraphs/cookbook/grafting-hotfix/ +/pl/subgraphs/cookbook/grafting/ +/pl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/pl/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/pl/subgraphs/cookbook/near/ +/pl/subgraphs/cookbook/pruning/ +/pl/subgraphs/cookbook/subgraph-debug-forking/ +/pl/subgraphs/cookbook/subgraph-uncrashable/ +/pl/subgraphs/cookbook/substreams-powered-subgraphs/ +/pl/subgraphs/cookbook/timeseries/ +/pl/subgraphs/cookbook/transfer-to-the-graph/ +/pl/subgraphs/developing/creating/advanced/ +/pl/subgraphs/developing/creating/assemblyscript-mappings/ +/pl/subgraphs/developing/creating/graph-ts/api/ +/pl/subgraphs/developing/creating/graph-ts/common-issues/ +/pl/subgraphs/developing/creating/install-the-cli/ +/pl/subgraphs/developing/creating/ql-schema/ +/pl/subgraphs/developing/creating/starting-your-subgraph/ +/pl/subgraphs/developing/creating/subgraph-manifest/ +/pl/subgraphs/developing/creating/unit-testing-framework/ +/pl/subgraphs/developing/deploying/multiple-networks/ +/pl/subgraphs/developing/deploying/subgraph-studio-faqs/ +/pl/subgraphs/developing/deploying/using-subgraph-studio/ +/pl/subgraphs/developing/developer-faqs/ +/pl/subgraphs/developing/introduction/ +/pl/subgraphs/developing/managing/deleting-a-subgraph/ +/pl/subgraphs/developing/managing/transferring-a-subgraph/ +/pl/subgraphs/developing/publishing/publishing-a-subgraph/ +/pl/subgraphs/developing/subgraphs/ +/pl/subgraphs/explorer/ +/pl/subgraphs/querying/best-practices/ +/pl/subgraphs/querying/distributed-systems/ +/pl/subgraphs/querying/from-an-application/ +/pl/subgraphs/querying/graphql-api/ +/pl/subgraphs/querying/introduction/ +/pl/subgraphs/querying/managing-api-keys/ +/pl/subgraphs/querying/python/ +/pl/subgraphs/querying/subgraph-id-vs-deployment-id/ +/pl/subgraphs/quick-start/ +/pl/substreams/introduction/ +/pl/substreams/sps/introduction/ +/pl/substreams/sps/substreams-powered-subgraphs-faq/ +/pl/substreams/sps/triggers-example/ +/pl/substreams/sps/triggers/ +/pl/supported-networks/ /pt/ /pt/404/ /pt/about/ @@ -978,147 +965,145 @@ /pt/archived/arbitrum/l2-transfer-tools-faq/ /pt/archived/arbitrum/l2-transfer-tools-guide/ /pt/archived/sunrise/ -/pt/billing/ -/pt/chain-integration-overview/ /pt/contracts/ -/pt/cookbook/arweave/ -/pt/cookbook/avoid-eth-calls/ -/pt/cookbook/cosmos/ -/pt/cookbook/derivedfrom/ -/pt/cookbook/enums/ -/pt/cookbook/grafting-hotfix/ -/pt/cookbook/grafting/ -/pt/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/pt/cookbook/immutable-entities-bytes-as-ids/ -/pt/cookbook/near/ -/pt/cookbook/pruning/ -/pt/cookbook/subgraph-debug-forking/ -/pt/cookbook/subgraph-uncrashable/ -/pt/cookbook/substreams-powered-subgraphs/ -/pt/cookbook/timeseries/ -/pt/cookbook/transfer-to-the-graph/ -/pt/developing/creating-a-subgraph/advanced/ -/pt/developing/creating-a-subgraph/assemblyscript-mappings/ -/pt/developing/creating-a-subgraph/graph-ts/api/ -/pt/developing/creating-a-subgraph/graph-ts/common-issues/ -/pt/developing/creating-a-subgraph/install-the-cli/ -/pt/developing/creating-a-subgraph/ql-schema/ -/pt/developing/creating-a-subgraph/starting-your-subgraph/ -/pt/developing/creating-a-subgraph/subgraph-manifest/ -/pt/developing/creating-a-subgraph/unit-testing-framework/ -/pt/developing/deploying/deploy-using-subgraph-studio/ -/pt/developing/deploying/multiple-networks/ -/pt/developing/deploying/subgraph-studio-faqs/ -/pt/developing/developer-faqs/ -/pt/developing/developing/ -/pt/developing/managing/delete-a-subgraph/ -/pt/developing/managing/transfer-a-subgraph/ -/pt/developing/publishing/publishing-a-subgraph/ -/pt/developing/subgraphs/ -/pt/developing/supported-networks/ -/pt/explorer/ -/pt/glossary/ -/pt/indexer-tooling/firehose/ -/pt/indexer-tooling/graphcast/ -/pt/indexer-tooling/operating-graph-node/ -/pt/indexing/ -/pt/new-chain-integration/ -/pt/querying/distributed-systems/ -/pt/querying/graphql-api/ -/pt/querying/managing-api-keys/ -/pt/querying/querying-best-practices/ -/pt/querying/querying-by-subgraph-id-vs-deployment-id/ -/pt/querying/querying-from-an-application/ -/pt/querying/querying-the-graph/ -/pt/querying/querying-with-python/ -/pt/quick-start/ -/pt/release-notes/assemblyscript-migration-guide/ -/pt/release-notes/graphql-validations-migration-guide/ -/pt/roles-and-benefits/benefits/ -/pt/roles-and-benefits/curating/ -/pt/roles-and-benefits/delegating/ -/pt/roles-and-benefits/overview/ -/pt/sps/introduction/ -/pt/sps/substreams-powered-subgraphs-faq/ -/pt/sps/triggers-example/ -/pt/sps/triggers/ -/pt/substreams/ -/pt/supported-network-requirements/ -/pt/tap/ -/pt/tokenomics/ +/pt/indexing/chain-integration-overview/ +/pt/indexing/introduction/ +/pt/indexing/new-chain-integration/ +/pt/indexing/supported-network-requirements/ +/pt/indexing/tap/ +/pt/indexing/tooling/firehose/ +/pt/indexing/tooling/graphcast/ +/pt/indexing/tooling/operating-graph-node/ +/pt/resources/benefits/ +/pt/resources/glossary/ +/pt/resources/release-notes/assemblyscript-migration-guide/ +/pt/resources/release-notes/graphql-validations-migration-guide/ +/pt/resources/roles/curating/ +/pt/resources/roles/delegating/ +/pt/resources/tokenomics/ +/pt/subgraphs/billing/ +/pt/subgraphs/cookbook/arweave/ +/pt/subgraphs/cookbook/avoid-eth-calls/ +/pt/subgraphs/cookbook/cosmos/ +/pt/subgraphs/cookbook/derivedfrom/ +/pt/subgraphs/cookbook/enums/ +/pt/subgraphs/cookbook/grafting-hotfix/ +/pt/subgraphs/cookbook/grafting/ +/pt/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/pt/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/pt/subgraphs/cookbook/near/ +/pt/subgraphs/cookbook/pruning/ +/pt/subgraphs/cookbook/subgraph-debug-forking/ +/pt/subgraphs/cookbook/subgraph-uncrashable/ +/pt/subgraphs/cookbook/substreams-powered-subgraphs/ +/pt/subgraphs/cookbook/timeseries/ +/pt/subgraphs/cookbook/transfer-to-the-graph/ +/pt/subgraphs/developing/creating/advanced/ +/pt/subgraphs/developing/creating/assemblyscript-mappings/ +/pt/subgraphs/developing/creating/graph-ts/api/ +/pt/subgraphs/developing/creating/graph-ts/common-issues/ +/pt/subgraphs/developing/creating/install-the-cli/ +/pt/subgraphs/developing/creating/ql-schema/ +/pt/subgraphs/developing/creating/starting-your-subgraph/ +/pt/subgraphs/developing/creating/subgraph-manifest/ +/pt/subgraphs/developing/creating/unit-testing-framework/ +/pt/subgraphs/developing/deploying/multiple-networks/ +/pt/subgraphs/developing/deploying/subgraph-studio-faqs/ +/pt/subgraphs/developing/deploying/using-subgraph-studio/ +/pt/subgraphs/developing/developer-faqs/ +/pt/subgraphs/developing/introduction/ +/pt/subgraphs/developing/managing/deleting-a-subgraph/ +/pt/subgraphs/developing/managing/transferring-a-subgraph/ +/pt/subgraphs/developing/publishing/publishing-a-subgraph/ +/pt/subgraphs/developing/subgraphs/ +/pt/subgraphs/explorer/ +/pt/subgraphs/querying/best-practices/ +/pt/subgraphs/querying/distributed-systems/ +/pt/subgraphs/querying/from-an-application/ +/pt/subgraphs/querying/graphql-api/ +/pt/subgraphs/querying/introduction/ +/pt/subgraphs/querying/managing-api-keys/ +/pt/subgraphs/querying/python/ +/pt/subgraphs/querying/subgraph-id-vs-deployment-id/ +/pt/subgraphs/quick-start/ +/pt/substreams/introduction/ +/pt/substreams/sps/introduction/ +/pt/substreams/sps/substreams-powered-subgraphs-faq/ +/pt/substreams/sps/triggers-example/ +/pt/substreams/sps/triggers/ +/pt/supported-networks/ /ro/about/ /ro/archived/arbitrum/arbitrum-faq/ /ro/archived/arbitrum/l2-transfer-tools-faq/ /ro/archived/arbitrum/l2-transfer-tools-guide/ /ro/archived/sunrise/ -/ro/billing/ -/ro/chain-integration-overview/ /ro/contracts/ -/ro/cookbook/arweave/ -/ro/cookbook/avoid-eth-calls/ -/ro/cookbook/cosmos/ -/ro/cookbook/derivedfrom/ -/ro/cookbook/enums/ -/ro/cookbook/grafting-hotfix/ -/ro/cookbook/grafting/ -/ro/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/ro/cookbook/immutable-entities-bytes-as-ids/ -/ro/cookbook/near/ -/ro/cookbook/pruning/ -/ro/cookbook/subgraph-debug-forking/ -/ro/cookbook/subgraph-uncrashable/ -/ro/cookbook/substreams-powered-subgraphs/ -/ro/cookbook/timeseries/ -/ro/cookbook/transfer-to-the-graph/ -/ro/developing/creating-a-subgraph/advanced/ -/ro/developing/creating-a-subgraph/assemblyscript-mappings/ -/ro/developing/creating-a-subgraph/graph-ts/api/ -/ro/developing/creating-a-subgraph/graph-ts/common-issues/ -/ro/developing/creating-a-subgraph/install-the-cli/ -/ro/developing/creating-a-subgraph/ql-schema/ -/ro/developing/creating-a-subgraph/starting-your-subgraph/ -/ro/developing/creating-a-subgraph/subgraph-manifest/ -/ro/developing/creating-a-subgraph/unit-testing-framework/ -/ro/developing/deploying/deploy-using-subgraph-studio/ -/ro/developing/deploying/multiple-networks/ -/ro/developing/deploying/subgraph-studio-faqs/ -/ro/developing/developer-faqs/ -/ro/developing/developing/ -/ro/developing/managing/delete-a-subgraph/ -/ro/developing/managing/transfer-a-subgraph/ -/ro/developing/publishing/publishing-a-subgraph/ -/ro/developing/subgraphs/ -/ro/developing/supported-networks/ -/ro/explorer/ -/ro/glossary/ -/ro/indexer-tooling/firehose/ -/ro/indexer-tooling/graphcast/ -/ro/indexer-tooling/operating-graph-node/ -/ro/indexing/ -/ro/new-chain-integration/ -/ro/querying/distributed-systems/ -/ro/querying/graphql-api/ -/ro/querying/managing-api-keys/ -/ro/querying/querying-best-practices/ -/ro/querying/querying-by-subgraph-id-vs-deployment-id/ -/ro/querying/querying-from-an-application/ -/ro/querying/querying-the-graph/ -/ro/querying/querying-with-python/ -/ro/quick-start/ -/ro/release-notes/assemblyscript-migration-guide/ -/ro/release-notes/graphql-validations-migration-guide/ -/ro/roles-and-benefits/benefits/ -/ro/roles-and-benefits/curating/ -/ro/roles-and-benefits/delegating/ -/ro/roles-and-benefits/overview/ -/ro/sps/introduction/ -/ro/sps/substreams-powered-subgraphs-faq/ -/ro/sps/triggers-example/ -/ro/sps/triggers/ -/ro/substreams/ -/ro/supported-network-requirements/ -/ro/tap/ -/ro/tokenomics/ +/ro/indexing/chain-integration-overview/ +/ro/indexing/introduction/ +/ro/indexing/new-chain-integration/ +/ro/indexing/supported-network-requirements/ +/ro/indexing/tap/ +/ro/indexing/tooling/firehose/ +/ro/indexing/tooling/graphcast/ +/ro/indexing/tooling/operating-graph-node/ +/ro/resources/benefits/ +/ro/resources/glossary/ +/ro/resources/release-notes/assemblyscript-migration-guide/ +/ro/resources/release-notes/graphql-validations-migration-guide/ +/ro/resources/roles/curating/ +/ro/resources/roles/delegating/ +/ro/resources/tokenomics/ +/ro/subgraphs/billing/ +/ro/subgraphs/cookbook/arweave/ +/ro/subgraphs/cookbook/avoid-eth-calls/ +/ro/subgraphs/cookbook/cosmos/ +/ro/subgraphs/cookbook/derivedfrom/ +/ro/subgraphs/cookbook/enums/ +/ro/subgraphs/cookbook/grafting-hotfix/ +/ro/subgraphs/cookbook/grafting/ +/ro/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/ro/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/ro/subgraphs/cookbook/near/ +/ro/subgraphs/cookbook/pruning/ +/ro/subgraphs/cookbook/subgraph-debug-forking/ +/ro/subgraphs/cookbook/subgraph-uncrashable/ +/ro/subgraphs/cookbook/substreams-powered-subgraphs/ +/ro/subgraphs/cookbook/timeseries/ +/ro/subgraphs/cookbook/transfer-to-the-graph/ +/ro/subgraphs/developing/creating/advanced/ +/ro/subgraphs/developing/creating/assemblyscript-mappings/ +/ro/subgraphs/developing/creating/graph-ts/api/ +/ro/subgraphs/developing/creating/graph-ts/common-issues/ +/ro/subgraphs/developing/creating/install-the-cli/ +/ro/subgraphs/developing/creating/ql-schema/ +/ro/subgraphs/developing/creating/starting-your-subgraph/ +/ro/subgraphs/developing/creating/subgraph-manifest/ +/ro/subgraphs/developing/creating/unit-testing-framework/ +/ro/subgraphs/developing/deploying/multiple-networks/ +/ro/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ro/subgraphs/developing/deploying/using-subgraph-studio/ +/ro/subgraphs/developing/developer-faqs/ +/ro/subgraphs/developing/introduction/ +/ro/subgraphs/developing/managing/deleting-a-subgraph/ +/ro/subgraphs/developing/managing/transferring-a-subgraph/ +/ro/subgraphs/developing/publishing/publishing-a-subgraph/ +/ro/subgraphs/developing/subgraphs/ +/ro/subgraphs/explorer/ +/ro/subgraphs/querying/best-practices/ +/ro/subgraphs/querying/distributed-systems/ +/ro/subgraphs/querying/from-an-application/ +/ro/subgraphs/querying/graphql-api/ +/ro/subgraphs/querying/introduction/ +/ro/subgraphs/querying/managing-api-keys/ +/ro/subgraphs/querying/python/ +/ro/subgraphs/querying/subgraph-id-vs-deployment-id/ +/ro/subgraphs/quick-start/ +/ro/substreams/introduction/ +/ro/substreams/sps/introduction/ +/ro/substreams/sps/substreams-powered-subgraphs-faq/ +/ro/substreams/sps/triggers-example/ +/ro/substreams/sps/triggers/ +/ro/supported-networks/ /ru/ /ru/404/ /ru/about/ @@ -1126,74 +1111,73 @@ /ru/archived/arbitrum/l2-transfer-tools-faq/ /ru/archived/arbitrum/l2-transfer-tools-guide/ /ru/archived/sunrise/ -/ru/billing/ -/ru/chain-integration-overview/ /ru/contracts/ -/ru/cookbook/arweave/ -/ru/cookbook/avoid-eth-calls/ -/ru/cookbook/cosmos/ -/ru/cookbook/derivedfrom/ -/ru/cookbook/enums/ -/ru/cookbook/grafting-hotfix/ -/ru/cookbook/grafting/ -/ru/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/ru/cookbook/immutable-entities-bytes-as-ids/ -/ru/cookbook/near/ -/ru/cookbook/pruning/ -/ru/cookbook/subgraph-debug-forking/ -/ru/cookbook/subgraph-uncrashable/ -/ru/cookbook/substreams-powered-subgraphs/ -/ru/cookbook/timeseries/ -/ru/cookbook/transfer-to-the-graph/ -/ru/developing/creating-a-subgraph/advanced/ -/ru/developing/creating-a-subgraph/assemblyscript-mappings/ -/ru/developing/creating-a-subgraph/graph-ts/api/ -/ru/developing/creating-a-subgraph/graph-ts/common-issues/ -/ru/developing/creating-a-subgraph/install-the-cli/ -/ru/developing/creating-a-subgraph/ql-schema/ -/ru/developing/creating-a-subgraph/starting-your-subgraph/ -/ru/developing/creating-a-subgraph/subgraph-manifest/ -/ru/developing/creating-a-subgraph/unit-testing-framework/ -/ru/developing/deploying/deploy-using-subgraph-studio/ -/ru/developing/deploying/multiple-networks/ -/ru/developing/deploying/subgraph-studio-faqs/ -/ru/developing/developer-faqs/ -/ru/developing/developing/ -/ru/developing/managing/delete-a-subgraph/ -/ru/developing/managing/transfer-a-subgraph/ -/ru/developing/publishing/publishing-a-subgraph/ -/ru/developing/subgraphs/ -/ru/developing/supported-networks/ -/ru/explorer/ -/ru/glossary/ -/ru/indexer-tooling/firehose/ -/ru/indexer-tooling/graphcast/ -/ru/indexer-tooling/operating-graph-node/ -/ru/indexing/ -/ru/new-chain-integration/ -/ru/querying/distributed-systems/ -/ru/querying/graphql-api/ -/ru/querying/managing-api-keys/ -/ru/querying/querying-best-practices/ -/ru/querying/querying-by-subgraph-id-vs-deployment-id/ -/ru/querying/querying-from-an-application/ -/ru/querying/querying-the-graph/ -/ru/querying/querying-with-python/ -/ru/quick-start/ -/ru/release-notes/assemblyscript-migration-guide/ -/ru/release-notes/graphql-validations-migration-guide/ -/ru/roles-and-benefits/benefits/ -/ru/roles-and-benefits/curating/ -/ru/roles-and-benefits/delegating/ -/ru/roles-and-benefits/overview/ -/ru/sps/introduction/ -/ru/sps/substreams-powered-subgraphs-faq/ -/ru/sps/triggers-example/ -/ru/sps/triggers/ -/ru/substreams/ -/ru/supported-network-requirements/ -/ru/tap/ -/ru/tokenomics/ +/ru/indexing/chain-integration-overview/ +/ru/indexing/introduction/ +/ru/indexing/new-chain-integration/ +/ru/indexing/supported-network-requirements/ +/ru/indexing/tap/ +/ru/indexing/tooling/firehose/ +/ru/indexing/tooling/graphcast/ +/ru/indexing/tooling/operating-graph-node/ +/ru/resources/benefits/ +/ru/resources/glossary/ +/ru/resources/release-notes/assemblyscript-migration-guide/ +/ru/resources/release-notes/graphql-validations-migration-guide/ +/ru/resources/roles/curating/ +/ru/resources/roles/delegating/ +/ru/resources/tokenomics/ +/ru/subgraphs/billing/ +/ru/subgraphs/cookbook/arweave/ +/ru/subgraphs/cookbook/avoid-eth-calls/ +/ru/subgraphs/cookbook/cosmos/ +/ru/subgraphs/cookbook/derivedfrom/ +/ru/subgraphs/cookbook/enums/ +/ru/subgraphs/cookbook/grafting-hotfix/ +/ru/subgraphs/cookbook/grafting/ +/ru/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/ru/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/ru/subgraphs/cookbook/near/ +/ru/subgraphs/cookbook/pruning/ +/ru/subgraphs/cookbook/subgraph-debug-forking/ +/ru/subgraphs/cookbook/subgraph-uncrashable/ +/ru/subgraphs/cookbook/substreams-powered-subgraphs/ +/ru/subgraphs/cookbook/timeseries/ +/ru/subgraphs/cookbook/transfer-to-the-graph/ +/ru/subgraphs/developing/creating/advanced/ +/ru/subgraphs/developing/creating/assemblyscript-mappings/ +/ru/subgraphs/developing/creating/graph-ts/api/ +/ru/subgraphs/developing/creating/graph-ts/common-issues/ +/ru/subgraphs/developing/creating/install-the-cli/ +/ru/subgraphs/developing/creating/ql-schema/ +/ru/subgraphs/developing/creating/starting-your-subgraph/ +/ru/subgraphs/developing/creating/subgraph-manifest/ +/ru/subgraphs/developing/creating/unit-testing-framework/ +/ru/subgraphs/developing/deploying/multiple-networks/ +/ru/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ru/subgraphs/developing/deploying/using-subgraph-studio/ +/ru/subgraphs/developing/developer-faqs/ +/ru/subgraphs/developing/introduction/ +/ru/subgraphs/developing/managing/deleting-a-subgraph/ +/ru/subgraphs/developing/managing/transferring-a-subgraph/ +/ru/subgraphs/developing/publishing/publishing-a-subgraph/ +/ru/subgraphs/developing/subgraphs/ +/ru/subgraphs/explorer/ +/ru/subgraphs/querying/best-practices/ +/ru/subgraphs/querying/distributed-systems/ +/ru/subgraphs/querying/from-an-application/ +/ru/subgraphs/querying/graphql-api/ +/ru/subgraphs/querying/introduction/ +/ru/subgraphs/querying/managing-api-keys/ +/ru/subgraphs/querying/python/ +/ru/subgraphs/querying/subgraph-id-vs-deployment-id/ +/ru/subgraphs/quick-start/ +/ru/substreams/introduction/ +/ru/substreams/sps/introduction/ +/ru/substreams/sps/substreams-powered-subgraphs-faq/ +/ru/substreams/sps/triggers-example/ +/ru/substreams/sps/triggers/ +/ru/supported-networks/ /sv/ /sv/404/ /sv/about/ @@ -1201,147 +1185,145 @@ /sv/archived/arbitrum/l2-transfer-tools-faq/ /sv/archived/arbitrum/l2-transfer-tools-guide/ /sv/archived/sunrise/ -/sv/billing/ -/sv/chain-integration-overview/ /sv/contracts/ -/sv/cookbook/arweave/ -/sv/cookbook/avoid-eth-calls/ -/sv/cookbook/cosmos/ -/sv/cookbook/derivedfrom/ -/sv/cookbook/enums/ -/sv/cookbook/grafting-hotfix/ -/sv/cookbook/grafting/ -/sv/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/sv/cookbook/immutable-entities-bytes-as-ids/ -/sv/cookbook/near/ -/sv/cookbook/pruning/ -/sv/cookbook/subgraph-debug-forking/ -/sv/cookbook/subgraph-uncrashable/ -/sv/cookbook/substreams-powered-subgraphs/ -/sv/cookbook/timeseries/ -/sv/cookbook/transfer-to-the-graph/ -/sv/developing/creating-a-subgraph/advanced/ -/sv/developing/creating-a-subgraph/assemblyscript-mappings/ -/sv/developing/creating-a-subgraph/graph-ts/api/ -/sv/developing/creating-a-subgraph/graph-ts/common-issues/ -/sv/developing/creating-a-subgraph/install-the-cli/ -/sv/developing/creating-a-subgraph/ql-schema/ -/sv/developing/creating-a-subgraph/starting-your-subgraph/ -/sv/developing/creating-a-subgraph/subgraph-manifest/ -/sv/developing/creating-a-subgraph/unit-testing-framework/ -/sv/developing/deploying/deploy-using-subgraph-studio/ -/sv/developing/deploying/multiple-networks/ -/sv/developing/deploying/subgraph-studio-faqs/ -/sv/developing/developer-faqs/ -/sv/developing/developing/ -/sv/developing/managing/delete-a-subgraph/ -/sv/developing/managing/transfer-a-subgraph/ -/sv/developing/publishing/publishing-a-subgraph/ -/sv/developing/subgraphs/ -/sv/developing/supported-networks/ -/sv/explorer/ -/sv/glossary/ -/sv/indexer-tooling/firehose/ -/sv/indexer-tooling/graphcast/ -/sv/indexer-tooling/operating-graph-node/ -/sv/indexing/ -/sv/new-chain-integration/ -/sv/querying/distributed-systems/ -/sv/querying/graphql-api/ -/sv/querying/managing-api-keys/ -/sv/querying/querying-best-practices/ -/sv/querying/querying-by-subgraph-id-vs-deployment-id/ -/sv/querying/querying-from-an-application/ -/sv/querying/querying-the-graph/ -/sv/querying/querying-with-python/ -/sv/quick-start/ -/sv/release-notes/assemblyscript-migration-guide/ -/sv/release-notes/graphql-validations-migration-guide/ -/sv/roles-and-benefits/benefits/ -/sv/roles-and-benefits/curating/ -/sv/roles-and-benefits/delegating/ -/sv/roles-and-benefits/overview/ -/sv/sps/introduction/ -/sv/sps/substreams-powered-subgraphs-faq/ -/sv/sps/triggers-example/ -/sv/sps/triggers/ -/sv/substreams/ -/sv/supported-network-requirements/ -/sv/tap/ -/sv/tokenomics/ +/sv/indexing/chain-integration-overview/ +/sv/indexing/introduction/ +/sv/indexing/new-chain-integration/ +/sv/indexing/supported-network-requirements/ +/sv/indexing/tap/ +/sv/indexing/tooling/firehose/ +/sv/indexing/tooling/graphcast/ +/sv/indexing/tooling/operating-graph-node/ +/sv/resources/benefits/ +/sv/resources/glossary/ +/sv/resources/release-notes/assemblyscript-migration-guide/ +/sv/resources/release-notes/graphql-validations-migration-guide/ +/sv/resources/roles/curating/ +/sv/resources/roles/delegating/ +/sv/resources/tokenomics/ +/sv/subgraphs/billing/ +/sv/subgraphs/cookbook/arweave/ +/sv/subgraphs/cookbook/avoid-eth-calls/ +/sv/subgraphs/cookbook/cosmos/ +/sv/subgraphs/cookbook/derivedfrom/ +/sv/subgraphs/cookbook/enums/ +/sv/subgraphs/cookbook/grafting-hotfix/ +/sv/subgraphs/cookbook/grafting/ +/sv/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/sv/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/sv/subgraphs/cookbook/near/ +/sv/subgraphs/cookbook/pruning/ +/sv/subgraphs/cookbook/subgraph-debug-forking/ +/sv/subgraphs/cookbook/subgraph-uncrashable/ +/sv/subgraphs/cookbook/substreams-powered-subgraphs/ +/sv/subgraphs/cookbook/timeseries/ +/sv/subgraphs/cookbook/transfer-to-the-graph/ +/sv/subgraphs/developing/creating/advanced/ +/sv/subgraphs/developing/creating/assemblyscript-mappings/ +/sv/subgraphs/developing/creating/graph-ts/api/ +/sv/subgraphs/developing/creating/graph-ts/common-issues/ +/sv/subgraphs/developing/creating/install-the-cli/ +/sv/subgraphs/developing/creating/ql-schema/ +/sv/subgraphs/developing/creating/starting-your-subgraph/ +/sv/subgraphs/developing/creating/subgraph-manifest/ +/sv/subgraphs/developing/creating/unit-testing-framework/ +/sv/subgraphs/developing/deploying/multiple-networks/ +/sv/subgraphs/developing/deploying/subgraph-studio-faqs/ +/sv/subgraphs/developing/deploying/using-subgraph-studio/ +/sv/subgraphs/developing/developer-faqs/ +/sv/subgraphs/developing/introduction/ +/sv/subgraphs/developing/managing/deleting-a-subgraph/ +/sv/subgraphs/developing/managing/transferring-a-subgraph/ +/sv/subgraphs/developing/publishing/publishing-a-subgraph/ +/sv/subgraphs/developing/subgraphs/ +/sv/subgraphs/explorer/ +/sv/subgraphs/querying/best-practices/ +/sv/subgraphs/querying/distributed-systems/ +/sv/subgraphs/querying/from-an-application/ +/sv/subgraphs/querying/graphql-api/ +/sv/subgraphs/querying/introduction/ +/sv/subgraphs/querying/managing-api-keys/ +/sv/subgraphs/querying/python/ +/sv/subgraphs/querying/subgraph-id-vs-deployment-id/ +/sv/subgraphs/quick-start/ +/sv/substreams/introduction/ +/sv/substreams/sps/introduction/ +/sv/substreams/sps/substreams-powered-subgraphs-faq/ +/sv/substreams/sps/triggers-example/ +/sv/substreams/sps/triggers/ +/sv/supported-networks/ /sw/about/ /sw/archived/arbitrum/arbitrum-faq/ /sw/archived/arbitrum/l2-transfer-tools-faq/ /sw/archived/arbitrum/l2-transfer-tools-guide/ /sw/archived/sunrise/ -/sw/billing/ -/sw/chain-integration-overview/ /sw/contracts/ -/sw/cookbook/arweave/ -/sw/cookbook/avoid-eth-calls/ -/sw/cookbook/cosmos/ -/sw/cookbook/derivedfrom/ -/sw/cookbook/enums/ -/sw/cookbook/grafting-hotfix/ -/sw/cookbook/grafting/ -/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/sw/cookbook/immutable-entities-bytes-as-ids/ -/sw/cookbook/near/ -/sw/cookbook/pruning/ -/sw/cookbook/subgraph-debug-forking/ -/sw/cookbook/subgraph-uncrashable/ -/sw/cookbook/substreams-powered-subgraphs/ -/sw/cookbook/timeseries/ -/sw/cookbook/transfer-to-the-graph/ -/sw/developing/creating-a-subgraph/advanced/ -/sw/developing/creating-a-subgraph/assemblyscript-mappings/ -/sw/developing/creating-a-subgraph/graph-ts/api/ -/sw/developing/creating-a-subgraph/graph-ts/common-issues/ -/sw/developing/creating-a-subgraph/install-the-cli/ -/sw/developing/creating-a-subgraph/ql-schema/ -/sw/developing/creating-a-subgraph/starting-your-subgraph/ -/sw/developing/creating-a-subgraph/subgraph-manifest/ -/sw/developing/creating-a-subgraph/unit-testing-framework/ -/sw/developing/deploying/deploy-using-subgraph-studio/ -/sw/developing/deploying/multiple-networks/ -/sw/developing/deploying/subgraph-studio-faqs/ -/sw/developing/developer-faqs/ -/sw/developing/developing/ -/sw/developing/managing/delete-a-subgraph/ -/sw/developing/managing/transfer-a-subgraph/ -/sw/developing/publishing/publishing-a-subgraph/ -/sw/developing/subgraphs/ -/sw/developing/supported-networks/ -/sw/explorer/ -/sw/glossary/ -/sw/indexer-tooling/firehose/ -/sw/indexer-tooling/graphcast/ -/sw/indexer-tooling/operating-graph-node/ -/sw/indexing/ -/sw/new-chain-integration/ -/sw/querying/distributed-systems/ -/sw/querying/graphql-api/ -/sw/querying/managing-api-keys/ -/sw/querying/querying-best-practices/ -/sw/querying/querying-by-subgraph-id-vs-deployment-id/ -/sw/querying/querying-from-an-application/ -/sw/querying/querying-the-graph/ -/sw/querying/querying-with-python/ -/sw/quick-start/ -/sw/release-notes/assemblyscript-migration-guide/ -/sw/release-notes/graphql-validations-migration-guide/ -/sw/roles-and-benefits/benefits/ -/sw/roles-and-benefits/curating/ -/sw/roles-and-benefits/delegating/ -/sw/roles-and-benefits/overview/ -/sw/sps/introduction/ -/sw/sps/substreams-powered-subgraphs-faq/ -/sw/sps/triggers-example/ -/sw/sps/triggers/ -/sw/substreams/ -/sw/supported-network-requirements/ -/sw/tap/ -/sw/tokenomics/ +/sw/indexing/chain-integration-overview/ +/sw/indexing/introduction/ +/sw/indexing/new-chain-integration/ +/sw/indexing/supported-network-requirements/ +/sw/indexing/tap/ +/sw/indexing/tooling/firehose/ +/sw/indexing/tooling/graphcast/ +/sw/indexing/tooling/operating-graph-node/ +/sw/resources/benefits/ +/sw/resources/glossary/ +/sw/resources/release-notes/assemblyscript-migration-guide/ +/sw/resources/release-notes/graphql-validations-migration-guide/ +/sw/resources/roles/curating/ +/sw/resources/roles/delegating/ +/sw/resources/tokenomics/ +/sw/subgraphs/billing/ +/sw/subgraphs/cookbook/arweave/ +/sw/subgraphs/cookbook/avoid-eth-calls/ +/sw/subgraphs/cookbook/cosmos/ +/sw/subgraphs/cookbook/derivedfrom/ +/sw/subgraphs/cookbook/enums/ +/sw/subgraphs/cookbook/grafting-hotfix/ +/sw/subgraphs/cookbook/grafting/ +/sw/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/sw/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/sw/subgraphs/cookbook/near/ +/sw/subgraphs/cookbook/pruning/ +/sw/subgraphs/cookbook/subgraph-debug-forking/ +/sw/subgraphs/cookbook/subgraph-uncrashable/ +/sw/subgraphs/cookbook/substreams-powered-subgraphs/ +/sw/subgraphs/cookbook/timeseries/ +/sw/subgraphs/cookbook/transfer-to-the-graph/ +/sw/subgraphs/developing/creating/advanced/ +/sw/subgraphs/developing/creating/assemblyscript-mappings/ +/sw/subgraphs/developing/creating/graph-ts/api/ +/sw/subgraphs/developing/creating/graph-ts/common-issues/ +/sw/subgraphs/developing/creating/install-the-cli/ +/sw/subgraphs/developing/creating/ql-schema/ +/sw/subgraphs/developing/creating/starting-your-subgraph/ +/sw/subgraphs/developing/creating/subgraph-manifest/ +/sw/subgraphs/developing/creating/unit-testing-framework/ +/sw/subgraphs/developing/deploying/multiple-networks/ +/sw/subgraphs/developing/deploying/subgraph-studio-faqs/ +/sw/subgraphs/developing/deploying/using-subgraph-studio/ +/sw/subgraphs/developing/developer-faqs/ +/sw/subgraphs/developing/introduction/ +/sw/subgraphs/developing/managing/deleting-a-subgraph/ +/sw/subgraphs/developing/managing/transferring-a-subgraph/ +/sw/subgraphs/developing/publishing/publishing-a-subgraph/ +/sw/subgraphs/developing/subgraphs/ +/sw/subgraphs/explorer/ +/sw/subgraphs/querying/best-practices/ +/sw/subgraphs/querying/distributed-systems/ +/sw/subgraphs/querying/from-an-application/ +/sw/subgraphs/querying/graphql-api/ +/sw/subgraphs/querying/introduction/ +/sw/subgraphs/querying/managing-api-keys/ +/sw/subgraphs/querying/python/ +/sw/subgraphs/querying/subgraph-id-vs-deployment-id/ +/sw/subgraphs/quick-start/ +/sw/substreams/introduction/ +/sw/substreams/sps/introduction/ +/sw/substreams/sps/substreams-powered-subgraphs-faq/ +/sw/substreams/sps/triggers-example/ +/sw/substreams/sps/triggers/ +/sw/supported-networks/ /tr/ /tr/404/ /tr/about/ @@ -1349,147 +1331,145 @@ /tr/archived/arbitrum/l2-transfer-tools-faq/ /tr/archived/arbitrum/l2-transfer-tools-guide/ /tr/archived/sunrise/ -/tr/billing/ -/tr/chain-integration-overview/ /tr/contracts/ -/tr/cookbook/arweave/ -/tr/cookbook/avoid-eth-calls/ -/tr/cookbook/cosmos/ -/tr/cookbook/derivedfrom/ -/tr/cookbook/enums/ -/tr/cookbook/grafting-hotfix/ -/tr/cookbook/grafting/ -/tr/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/tr/cookbook/immutable-entities-bytes-as-ids/ -/tr/cookbook/near/ -/tr/cookbook/pruning/ -/tr/cookbook/subgraph-debug-forking/ -/tr/cookbook/subgraph-uncrashable/ -/tr/cookbook/substreams-powered-subgraphs/ -/tr/cookbook/timeseries/ -/tr/cookbook/transfer-to-the-graph/ -/tr/developing/creating-a-subgraph/advanced/ -/tr/developing/creating-a-subgraph/assemblyscript-mappings/ -/tr/developing/creating-a-subgraph/graph-ts/api/ -/tr/developing/creating-a-subgraph/graph-ts/common-issues/ -/tr/developing/creating-a-subgraph/install-the-cli/ -/tr/developing/creating-a-subgraph/ql-schema/ -/tr/developing/creating-a-subgraph/starting-your-subgraph/ -/tr/developing/creating-a-subgraph/subgraph-manifest/ -/tr/developing/creating-a-subgraph/unit-testing-framework/ -/tr/developing/deploying/deploy-using-subgraph-studio/ -/tr/developing/deploying/multiple-networks/ -/tr/developing/deploying/subgraph-studio-faqs/ -/tr/developing/developer-faqs/ -/tr/developing/developing/ -/tr/developing/managing/delete-a-subgraph/ -/tr/developing/managing/transfer-a-subgraph/ -/tr/developing/publishing/publishing-a-subgraph/ -/tr/developing/subgraphs/ -/tr/developing/supported-networks/ -/tr/explorer/ -/tr/glossary/ -/tr/indexer-tooling/firehose/ -/tr/indexer-tooling/graphcast/ -/tr/indexer-tooling/operating-graph-node/ -/tr/indexing/ -/tr/new-chain-integration/ -/tr/querying/distributed-systems/ -/tr/querying/graphql-api/ -/tr/querying/managing-api-keys/ -/tr/querying/querying-best-practices/ -/tr/querying/querying-by-subgraph-id-vs-deployment-id/ -/tr/querying/querying-from-an-application/ -/tr/querying/querying-the-graph/ -/tr/querying/querying-with-python/ -/tr/quick-start/ -/tr/release-notes/assemblyscript-migration-guide/ -/tr/release-notes/graphql-validations-migration-guide/ -/tr/roles-and-benefits/benefits/ -/tr/roles-and-benefits/curating/ -/tr/roles-and-benefits/delegating/ -/tr/roles-and-benefits/overview/ -/tr/sps/introduction/ -/tr/sps/substreams-powered-subgraphs-faq/ -/tr/sps/triggers-example/ -/tr/sps/triggers/ -/tr/substreams/ -/tr/supported-network-requirements/ -/tr/tap/ -/tr/tokenomics/ +/tr/indexing/chain-integration-overview/ +/tr/indexing/introduction/ +/tr/indexing/new-chain-integration/ +/tr/indexing/supported-network-requirements/ +/tr/indexing/tap/ +/tr/indexing/tooling/firehose/ +/tr/indexing/tooling/graphcast/ +/tr/indexing/tooling/operating-graph-node/ +/tr/resources/benefits/ +/tr/resources/glossary/ +/tr/resources/release-notes/assemblyscript-migration-guide/ +/tr/resources/release-notes/graphql-validations-migration-guide/ +/tr/resources/roles/curating/ +/tr/resources/roles/delegating/ +/tr/resources/tokenomics/ +/tr/subgraphs/billing/ +/tr/subgraphs/cookbook/arweave/ +/tr/subgraphs/cookbook/avoid-eth-calls/ +/tr/subgraphs/cookbook/cosmos/ +/tr/subgraphs/cookbook/derivedfrom/ +/tr/subgraphs/cookbook/enums/ +/tr/subgraphs/cookbook/grafting-hotfix/ +/tr/subgraphs/cookbook/grafting/ +/tr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/tr/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/tr/subgraphs/cookbook/near/ +/tr/subgraphs/cookbook/pruning/ +/tr/subgraphs/cookbook/subgraph-debug-forking/ +/tr/subgraphs/cookbook/subgraph-uncrashable/ +/tr/subgraphs/cookbook/substreams-powered-subgraphs/ +/tr/subgraphs/cookbook/timeseries/ +/tr/subgraphs/cookbook/transfer-to-the-graph/ +/tr/subgraphs/developing/creating/advanced/ +/tr/subgraphs/developing/creating/assemblyscript-mappings/ +/tr/subgraphs/developing/creating/graph-ts/api/ +/tr/subgraphs/developing/creating/graph-ts/common-issues/ +/tr/subgraphs/developing/creating/install-the-cli/ +/tr/subgraphs/developing/creating/ql-schema/ +/tr/subgraphs/developing/creating/starting-your-subgraph/ +/tr/subgraphs/developing/creating/subgraph-manifest/ +/tr/subgraphs/developing/creating/unit-testing-framework/ +/tr/subgraphs/developing/deploying/multiple-networks/ +/tr/subgraphs/developing/deploying/subgraph-studio-faqs/ +/tr/subgraphs/developing/deploying/using-subgraph-studio/ +/tr/subgraphs/developing/developer-faqs/ +/tr/subgraphs/developing/introduction/ +/tr/subgraphs/developing/managing/deleting-a-subgraph/ +/tr/subgraphs/developing/managing/transferring-a-subgraph/ +/tr/subgraphs/developing/publishing/publishing-a-subgraph/ +/tr/subgraphs/developing/subgraphs/ +/tr/subgraphs/explorer/ +/tr/subgraphs/querying/best-practices/ +/tr/subgraphs/querying/distributed-systems/ +/tr/subgraphs/querying/from-an-application/ +/tr/subgraphs/querying/graphql-api/ +/tr/subgraphs/querying/introduction/ +/tr/subgraphs/querying/managing-api-keys/ +/tr/subgraphs/querying/python/ +/tr/subgraphs/querying/subgraph-id-vs-deployment-id/ +/tr/subgraphs/quick-start/ +/tr/substreams/introduction/ +/tr/substreams/sps/introduction/ +/tr/substreams/sps/substreams-powered-subgraphs-faq/ +/tr/substreams/sps/triggers-example/ +/tr/substreams/sps/triggers/ +/tr/supported-networks/ /uk/about/ /uk/archived/arbitrum/arbitrum-faq/ /uk/archived/arbitrum/l2-transfer-tools-faq/ /uk/archived/arbitrum/l2-transfer-tools-guide/ /uk/archived/sunrise/ -/uk/billing/ -/uk/chain-integration-overview/ /uk/contracts/ -/uk/cookbook/arweave/ -/uk/cookbook/avoid-eth-calls/ -/uk/cookbook/cosmos/ -/uk/cookbook/derivedfrom/ -/uk/cookbook/enums/ -/uk/cookbook/grafting-hotfix/ -/uk/cookbook/grafting/ -/uk/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/uk/cookbook/immutable-entities-bytes-as-ids/ -/uk/cookbook/near/ -/uk/cookbook/pruning/ -/uk/cookbook/subgraph-debug-forking/ -/uk/cookbook/subgraph-uncrashable/ -/uk/cookbook/substreams-powered-subgraphs/ -/uk/cookbook/timeseries/ -/uk/cookbook/transfer-to-the-graph/ -/uk/developing/creating-a-subgraph/advanced/ -/uk/developing/creating-a-subgraph/assemblyscript-mappings/ -/uk/developing/creating-a-subgraph/graph-ts/api/ -/uk/developing/creating-a-subgraph/graph-ts/common-issues/ -/uk/developing/creating-a-subgraph/install-the-cli/ -/uk/developing/creating-a-subgraph/ql-schema/ -/uk/developing/creating-a-subgraph/starting-your-subgraph/ -/uk/developing/creating-a-subgraph/subgraph-manifest/ -/uk/developing/creating-a-subgraph/unit-testing-framework/ -/uk/developing/deploying/deploy-using-subgraph-studio/ -/uk/developing/deploying/multiple-networks/ -/uk/developing/deploying/subgraph-studio-faqs/ -/uk/developing/developer-faqs/ -/uk/developing/developing/ -/uk/developing/managing/delete-a-subgraph/ -/uk/developing/managing/transfer-a-subgraph/ -/uk/developing/publishing/publishing-a-subgraph/ -/uk/developing/subgraphs/ -/uk/developing/supported-networks/ -/uk/explorer/ -/uk/glossary/ -/uk/indexer-tooling/firehose/ -/uk/indexer-tooling/graphcast/ -/uk/indexer-tooling/operating-graph-node/ -/uk/indexing/ -/uk/new-chain-integration/ -/uk/querying/distributed-systems/ -/uk/querying/graphql-api/ -/uk/querying/managing-api-keys/ -/uk/querying/querying-best-practices/ -/uk/querying/querying-by-subgraph-id-vs-deployment-id/ -/uk/querying/querying-from-an-application/ -/uk/querying/querying-the-graph/ -/uk/querying/querying-with-python/ -/uk/quick-start/ -/uk/release-notes/assemblyscript-migration-guide/ -/uk/release-notes/graphql-validations-migration-guide/ -/uk/roles-and-benefits/benefits/ -/uk/roles-and-benefits/curating/ -/uk/roles-and-benefits/delegating/ -/uk/roles-and-benefits/overview/ -/uk/sps/introduction/ -/uk/sps/substreams-powered-subgraphs-faq/ -/uk/sps/triggers-example/ -/uk/sps/triggers/ -/uk/substreams/ -/uk/supported-network-requirements/ -/uk/tap/ -/uk/tokenomics/ +/uk/indexing/chain-integration-overview/ +/uk/indexing/introduction/ +/uk/indexing/new-chain-integration/ +/uk/indexing/supported-network-requirements/ +/uk/indexing/tap/ +/uk/indexing/tooling/firehose/ +/uk/indexing/tooling/graphcast/ +/uk/indexing/tooling/operating-graph-node/ +/uk/resources/benefits/ +/uk/resources/glossary/ +/uk/resources/release-notes/assemblyscript-migration-guide/ +/uk/resources/release-notes/graphql-validations-migration-guide/ +/uk/resources/roles/curating/ +/uk/resources/roles/delegating/ +/uk/resources/tokenomics/ +/uk/subgraphs/billing/ +/uk/subgraphs/cookbook/arweave/ +/uk/subgraphs/cookbook/avoid-eth-calls/ +/uk/subgraphs/cookbook/cosmos/ +/uk/subgraphs/cookbook/derivedfrom/ +/uk/subgraphs/cookbook/enums/ +/uk/subgraphs/cookbook/grafting-hotfix/ +/uk/subgraphs/cookbook/grafting/ +/uk/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/uk/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/uk/subgraphs/cookbook/near/ +/uk/subgraphs/cookbook/pruning/ +/uk/subgraphs/cookbook/subgraph-debug-forking/ +/uk/subgraphs/cookbook/subgraph-uncrashable/ +/uk/subgraphs/cookbook/substreams-powered-subgraphs/ +/uk/subgraphs/cookbook/timeseries/ +/uk/subgraphs/cookbook/transfer-to-the-graph/ +/uk/subgraphs/developing/creating/advanced/ +/uk/subgraphs/developing/creating/assemblyscript-mappings/ +/uk/subgraphs/developing/creating/graph-ts/api/ +/uk/subgraphs/developing/creating/graph-ts/common-issues/ +/uk/subgraphs/developing/creating/install-the-cli/ +/uk/subgraphs/developing/creating/ql-schema/ +/uk/subgraphs/developing/creating/starting-your-subgraph/ +/uk/subgraphs/developing/creating/subgraph-manifest/ +/uk/subgraphs/developing/creating/unit-testing-framework/ +/uk/subgraphs/developing/deploying/multiple-networks/ +/uk/subgraphs/developing/deploying/subgraph-studio-faqs/ +/uk/subgraphs/developing/deploying/using-subgraph-studio/ +/uk/subgraphs/developing/developer-faqs/ +/uk/subgraphs/developing/introduction/ +/uk/subgraphs/developing/managing/deleting-a-subgraph/ +/uk/subgraphs/developing/managing/transferring-a-subgraph/ +/uk/subgraphs/developing/publishing/publishing-a-subgraph/ +/uk/subgraphs/developing/subgraphs/ +/uk/subgraphs/explorer/ +/uk/subgraphs/querying/best-practices/ +/uk/subgraphs/querying/distributed-systems/ +/uk/subgraphs/querying/from-an-application/ +/uk/subgraphs/querying/graphql-api/ +/uk/subgraphs/querying/introduction/ +/uk/subgraphs/querying/managing-api-keys/ +/uk/subgraphs/querying/python/ +/uk/subgraphs/querying/subgraph-id-vs-deployment-id/ +/uk/subgraphs/quick-start/ +/uk/substreams/introduction/ +/uk/substreams/sps/introduction/ +/uk/substreams/sps/substreams-powered-subgraphs-faq/ +/uk/substreams/sps/triggers-example/ +/uk/substreams/sps/triggers/ +/uk/supported-networks/ /ur/ /ur/404/ /ur/about/ @@ -1497,147 +1477,145 @@ /ur/archived/arbitrum/l2-transfer-tools-faq/ /ur/archived/arbitrum/l2-transfer-tools-guide/ /ur/archived/sunrise/ -/ur/billing/ -/ur/chain-integration-overview/ /ur/contracts/ -/ur/cookbook/arweave/ -/ur/cookbook/avoid-eth-calls/ -/ur/cookbook/cosmos/ -/ur/cookbook/derivedfrom/ -/ur/cookbook/enums/ -/ur/cookbook/grafting-hotfix/ -/ur/cookbook/grafting/ -/ur/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/ur/cookbook/immutable-entities-bytes-as-ids/ -/ur/cookbook/near/ -/ur/cookbook/pruning/ -/ur/cookbook/subgraph-debug-forking/ -/ur/cookbook/subgraph-uncrashable/ -/ur/cookbook/substreams-powered-subgraphs/ -/ur/cookbook/timeseries/ -/ur/cookbook/transfer-to-the-graph/ -/ur/developing/creating-a-subgraph/advanced/ -/ur/developing/creating-a-subgraph/assemblyscript-mappings/ -/ur/developing/creating-a-subgraph/graph-ts/api/ -/ur/developing/creating-a-subgraph/graph-ts/common-issues/ -/ur/developing/creating-a-subgraph/install-the-cli/ -/ur/developing/creating-a-subgraph/ql-schema/ -/ur/developing/creating-a-subgraph/starting-your-subgraph/ -/ur/developing/creating-a-subgraph/subgraph-manifest/ -/ur/developing/creating-a-subgraph/unit-testing-framework/ -/ur/developing/deploying/deploy-using-subgraph-studio/ -/ur/developing/deploying/multiple-networks/ -/ur/developing/deploying/subgraph-studio-faqs/ -/ur/developing/developer-faqs/ -/ur/developing/developing/ -/ur/developing/managing/delete-a-subgraph/ -/ur/developing/managing/transfer-a-subgraph/ -/ur/developing/publishing/publishing-a-subgraph/ -/ur/developing/subgraphs/ -/ur/developing/supported-networks/ -/ur/explorer/ -/ur/glossary/ -/ur/indexer-tooling/firehose/ -/ur/indexer-tooling/graphcast/ -/ur/indexer-tooling/operating-graph-node/ -/ur/indexing/ -/ur/new-chain-integration/ -/ur/querying/distributed-systems/ -/ur/querying/graphql-api/ -/ur/querying/managing-api-keys/ -/ur/querying/querying-best-practices/ -/ur/querying/querying-by-subgraph-id-vs-deployment-id/ -/ur/querying/querying-from-an-application/ -/ur/querying/querying-the-graph/ -/ur/querying/querying-with-python/ -/ur/quick-start/ -/ur/release-notes/assemblyscript-migration-guide/ -/ur/release-notes/graphql-validations-migration-guide/ -/ur/roles-and-benefits/benefits/ -/ur/roles-and-benefits/curating/ -/ur/roles-and-benefits/delegating/ -/ur/roles-and-benefits/overview/ -/ur/sps/introduction/ -/ur/sps/substreams-powered-subgraphs-faq/ -/ur/sps/triggers-example/ -/ur/sps/triggers/ -/ur/substreams/ -/ur/supported-network-requirements/ -/ur/tap/ -/ur/tokenomics/ +/ur/indexing/chain-integration-overview/ +/ur/indexing/introduction/ +/ur/indexing/new-chain-integration/ +/ur/indexing/supported-network-requirements/ +/ur/indexing/tap/ +/ur/indexing/tooling/firehose/ +/ur/indexing/tooling/graphcast/ +/ur/indexing/tooling/operating-graph-node/ +/ur/resources/benefits/ +/ur/resources/glossary/ +/ur/resources/release-notes/assemblyscript-migration-guide/ +/ur/resources/release-notes/graphql-validations-migration-guide/ +/ur/resources/roles/curating/ +/ur/resources/roles/delegating/ +/ur/resources/tokenomics/ +/ur/subgraphs/billing/ +/ur/subgraphs/cookbook/arweave/ +/ur/subgraphs/cookbook/avoid-eth-calls/ +/ur/subgraphs/cookbook/cosmos/ +/ur/subgraphs/cookbook/derivedfrom/ +/ur/subgraphs/cookbook/enums/ +/ur/subgraphs/cookbook/grafting-hotfix/ +/ur/subgraphs/cookbook/grafting/ +/ur/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/ur/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/ur/subgraphs/cookbook/near/ +/ur/subgraphs/cookbook/pruning/ +/ur/subgraphs/cookbook/subgraph-debug-forking/ +/ur/subgraphs/cookbook/subgraph-uncrashable/ +/ur/subgraphs/cookbook/substreams-powered-subgraphs/ +/ur/subgraphs/cookbook/timeseries/ +/ur/subgraphs/cookbook/transfer-to-the-graph/ +/ur/subgraphs/developing/creating/advanced/ +/ur/subgraphs/developing/creating/assemblyscript-mappings/ +/ur/subgraphs/developing/creating/graph-ts/api/ +/ur/subgraphs/developing/creating/graph-ts/common-issues/ +/ur/subgraphs/developing/creating/install-the-cli/ +/ur/subgraphs/developing/creating/ql-schema/ +/ur/subgraphs/developing/creating/starting-your-subgraph/ +/ur/subgraphs/developing/creating/subgraph-manifest/ +/ur/subgraphs/developing/creating/unit-testing-framework/ +/ur/subgraphs/developing/deploying/multiple-networks/ +/ur/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ur/subgraphs/developing/deploying/using-subgraph-studio/ +/ur/subgraphs/developing/developer-faqs/ +/ur/subgraphs/developing/introduction/ +/ur/subgraphs/developing/managing/deleting-a-subgraph/ +/ur/subgraphs/developing/managing/transferring-a-subgraph/ +/ur/subgraphs/developing/publishing/publishing-a-subgraph/ +/ur/subgraphs/developing/subgraphs/ +/ur/subgraphs/explorer/ +/ur/subgraphs/querying/best-practices/ +/ur/subgraphs/querying/distributed-systems/ +/ur/subgraphs/querying/from-an-application/ +/ur/subgraphs/querying/graphql-api/ +/ur/subgraphs/querying/introduction/ +/ur/subgraphs/querying/managing-api-keys/ +/ur/subgraphs/querying/python/ +/ur/subgraphs/querying/subgraph-id-vs-deployment-id/ +/ur/subgraphs/quick-start/ +/ur/substreams/introduction/ +/ur/substreams/sps/introduction/ +/ur/substreams/sps/substreams-powered-subgraphs-faq/ +/ur/substreams/sps/triggers-example/ +/ur/substreams/sps/triggers/ +/ur/supported-networks/ /vi/about/ /vi/archived/arbitrum/arbitrum-faq/ /vi/archived/arbitrum/l2-transfer-tools-faq/ /vi/archived/arbitrum/l2-transfer-tools-guide/ /vi/archived/sunrise/ -/vi/billing/ -/vi/chain-integration-overview/ /vi/contracts/ -/vi/cookbook/arweave/ -/vi/cookbook/avoid-eth-calls/ -/vi/cookbook/cosmos/ -/vi/cookbook/derivedfrom/ -/vi/cookbook/enums/ -/vi/cookbook/grafting-hotfix/ -/vi/cookbook/grafting/ -/vi/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/vi/cookbook/immutable-entities-bytes-as-ids/ -/vi/cookbook/near/ -/vi/cookbook/pruning/ -/vi/cookbook/subgraph-debug-forking/ -/vi/cookbook/subgraph-uncrashable/ -/vi/cookbook/substreams-powered-subgraphs/ -/vi/cookbook/timeseries/ -/vi/cookbook/transfer-to-the-graph/ -/vi/developing/creating-a-subgraph/advanced/ -/vi/developing/creating-a-subgraph/assemblyscript-mappings/ -/vi/developing/creating-a-subgraph/graph-ts/api/ -/vi/developing/creating-a-subgraph/graph-ts/common-issues/ -/vi/developing/creating-a-subgraph/install-the-cli/ -/vi/developing/creating-a-subgraph/ql-schema/ -/vi/developing/creating-a-subgraph/starting-your-subgraph/ -/vi/developing/creating-a-subgraph/subgraph-manifest/ -/vi/developing/creating-a-subgraph/unit-testing-framework/ -/vi/developing/deploying/deploy-using-subgraph-studio/ -/vi/developing/deploying/multiple-networks/ -/vi/developing/deploying/subgraph-studio-faqs/ -/vi/developing/developer-faqs/ -/vi/developing/developing/ -/vi/developing/managing/delete-a-subgraph/ -/vi/developing/managing/transfer-a-subgraph/ -/vi/developing/publishing/publishing-a-subgraph/ -/vi/developing/subgraphs/ -/vi/developing/supported-networks/ -/vi/explorer/ -/vi/glossary/ -/vi/indexer-tooling/firehose/ -/vi/indexer-tooling/graphcast/ -/vi/indexer-tooling/operating-graph-node/ -/vi/indexing/ -/vi/new-chain-integration/ -/vi/querying/distributed-systems/ -/vi/querying/graphql-api/ -/vi/querying/managing-api-keys/ -/vi/querying/querying-best-practices/ -/vi/querying/querying-by-subgraph-id-vs-deployment-id/ -/vi/querying/querying-from-an-application/ -/vi/querying/querying-the-graph/ -/vi/querying/querying-with-python/ -/vi/quick-start/ -/vi/release-notes/assemblyscript-migration-guide/ -/vi/release-notes/graphql-validations-migration-guide/ -/vi/roles-and-benefits/benefits/ -/vi/roles-and-benefits/curating/ -/vi/roles-and-benefits/delegating/ -/vi/roles-and-benefits/overview/ -/vi/sps/introduction/ -/vi/sps/substreams-powered-subgraphs-faq/ -/vi/sps/triggers-example/ -/vi/sps/triggers/ -/vi/substreams/ -/vi/supported-network-requirements/ -/vi/tap/ -/vi/tokenomics/ +/vi/indexing/chain-integration-overview/ +/vi/indexing/introduction/ +/vi/indexing/new-chain-integration/ +/vi/indexing/supported-network-requirements/ +/vi/indexing/tap/ +/vi/indexing/tooling/firehose/ +/vi/indexing/tooling/graphcast/ +/vi/indexing/tooling/operating-graph-node/ +/vi/resources/benefits/ +/vi/resources/glossary/ +/vi/resources/release-notes/assemblyscript-migration-guide/ +/vi/resources/release-notes/graphql-validations-migration-guide/ +/vi/resources/roles/curating/ +/vi/resources/roles/delegating/ +/vi/resources/tokenomics/ +/vi/subgraphs/billing/ +/vi/subgraphs/cookbook/arweave/ +/vi/subgraphs/cookbook/avoid-eth-calls/ +/vi/subgraphs/cookbook/cosmos/ +/vi/subgraphs/cookbook/derivedfrom/ +/vi/subgraphs/cookbook/enums/ +/vi/subgraphs/cookbook/grafting-hotfix/ +/vi/subgraphs/cookbook/grafting/ +/vi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/vi/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/vi/subgraphs/cookbook/near/ +/vi/subgraphs/cookbook/pruning/ +/vi/subgraphs/cookbook/subgraph-debug-forking/ +/vi/subgraphs/cookbook/subgraph-uncrashable/ +/vi/subgraphs/cookbook/substreams-powered-subgraphs/ +/vi/subgraphs/cookbook/timeseries/ +/vi/subgraphs/cookbook/transfer-to-the-graph/ +/vi/subgraphs/developing/creating/advanced/ +/vi/subgraphs/developing/creating/assemblyscript-mappings/ +/vi/subgraphs/developing/creating/graph-ts/api/ +/vi/subgraphs/developing/creating/graph-ts/common-issues/ +/vi/subgraphs/developing/creating/install-the-cli/ +/vi/subgraphs/developing/creating/ql-schema/ +/vi/subgraphs/developing/creating/starting-your-subgraph/ +/vi/subgraphs/developing/creating/subgraph-manifest/ +/vi/subgraphs/developing/creating/unit-testing-framework/ +/vi/subgraphs/developing/deploying/multiple-networks/ +/vi/subgraphs/developing/deploying/subgraph-studio-faqs/ +/vi/subgraphs/developing/deploying/using-subgraph-studio/ +/vi/subgraphs/developing/developer-faqs/ +/vi/subgraphs/developing/introduction/ +/vi/subgraphs/developing/managing/deleting-a-subgraph/ +/vi/subgraphs/developing/managing/transferring-a-subgraph/ +/vi/subgraphs/developing/publishing/publishing-a-subgraph/ +/vi/subgraphs/developing/subgraphs/ +/vi/subgraphs/explorer/ +/vi/subgraphs/querying/best-practices/ +/vi/subgraphs/querying/distributed-systems/ +/vi/subgraphs/querying/from-an-application/ +/vi/subgraphs/querying/graphql-api/ +/vi/subgraphs/querying/introduction/ +/vi/subgraphs/querying/managing-api-keys/ +/vi/subgraphs/querying/python/ +/vi/subgraphs/querying/subgraph-id-vs-deployment-id/ +/vi/subgraphs/quick-start/ +/vi/substreams/introduction/ +/vi/substreams/sps/introduction/ +/vi/substreams/sps/substreams-powered-subgraphs-faq/ +/vi/substreams/sps/triggers-example/ +/vi/substreams/sps/triggers/ +/vi/supported-networks/ /zh/ /zh/404/ /zh/about/ @@ -1645,71 +1623,70 @@ /zh/archived/arbitrum/l2-transfer-tools-faq/ /zh/archived/arbitrum/l2-transfer-tools-guide/ /zh/archived/sunrise/ -/zh/billing/ -/zh/chain-integration-overview/ /zh/contracts/ -/zh/cookbook/arweave/ -/zh/cookbook/avoid-eth-calls/ -/zh/cookbook/cosmos/ -/zh/cookbook/derivedfrom/ -/zh/cookbook/enums/ -/zh/cookbook/grafting-hotfix/ -/zh/cookbook/grafting/ -/zh/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ -/zh/cookbook/immutable-entities-bytes-as-ids/ -/zh/cookbook/near/ -/zh/cookbook/pruning/ -/zh/cookbook/subgraph-debug-forking/ -/zh/cookbook/subgraph-uncrashable/ -/zh/cookbook/substreams-powered-subgraphs/ -/zh/cookbook/timeseries/ -/zh/cookbook/transfer-to-the-graph/ -/zh/developing/creating-a-subgraph/advanced/ -/zh/developing/creating-a-subgraph/assemblyscript-mappings/ -/zh/developing/creating-a-subgraph/graph-ts/api/ -/zh/developing/creating-a-subgraph/graph-ts/common-issues/ -/zh/developing/creating-a-subgraph/install-the-cli/ -/zh/developing/creating-a-subgraph/ql-schema/ -/zh/developing/creating-a-subgraph/starting-your-subgraph/ -/zh/developing/creating-a-subgraph/subgraph-manifest/ -/zh/developing/creating-a-subgraph/unit-testing-framework/ -/zh/developing/deploying/deploy-using-subgraph-studio/ -/zh/developing/deploying/multiple-networks/ -/zh/developing/deploying/subgraph-studio-faqs/ -/zh/developing/developer-faqs/ -/zh/developing/developing/ -/zh/developing/managing/delete-a-subgraph/ -/zh/developing/managing/transfer-a-subgraph/ -/zh/developing/publishing/publishing-a-subgraph/ -/zh/developing/subgraphs/ -/zh/developing/supported-networks/ -/zh/explorer/ -/zh/glossary/ -/zh/indexer-tooling/firehose/ -/zh/indexer-tooling/graphcast/ -/zh/indexer-tooling/operating-graph-node/ -/zh/indexing/ -/zh/new-chain-integration/ -/zh/querying/distributed-systems/ -/zh/querying/graphql-api/ -/zh/querying/managing-api-keys/ -/zh/querying/querying-best-practices/ -/zh/querying/querying-by-subgraph-id-vs-deployment-id/ -/zh/querying/querying-from-an-application/ -/zh/querying/querying-the-graph/ -/zh/querying/querying-with-python/ -/zh/quick-start/ -/zh/release-notes/assemblyscript-migration-guide/ -/zh/release-notes/graphql-validations-migration-guide/ -/zh/roles-and-benefits/benefits/ -/zh/roles-and-benefits/curating/ -/zh/roles-and-benefits/delegating/ -/zh/roles-and-benefits/overview/ -/zh/sps/introduction/ -/zh/sps/substreams-powered-subgraphs-faq/ -/zh/sps/triggers-example/ -/zh/sps/triggers/ -/zh/substreams/ -/zh/supported-network-requirements/ -/zh/tap/ -/zh/tokenomics/ +/zh/indexing/chain-integration-overview/ +/zh/indexing/introduction/ +/zh/indexing/new-chain-integration/ +/zh/indexing/supported-network-requirements/ +/zh/indexing/tap/ +/zh/indexing/tooling/firehose/ +/zh/indexing/tooling/graphcast/ +/zh/indexing/tooling/operating-graph-node/ +/zh/resources/benefits/ +/zh/resources/glossary/ +/zh/resources/release-notes/assemblyscript-migration-guide/ +/zh/resources/release-notes/graphql-validations-migration-guide/ +/zh/resources/roles/curating/ +/zh/resources/roles/delegating/ +/zh/resources/tokenomics/ +/zh/subgraphs/billing/ +/zh/subgraphs/cookbook/arweave/ +/zh/subgraphs/cookbook/avoid-eth-calls/ +/zh/subgraphs/cookbook/cosmos/ +/zh/subgraphs/cookbook/derivedfrom/ +/zh/subgraphs/cookbook/enums/ +/zh/subgraphs/cookbook/grafting-hotfix/ +/zh/subgraphs/cookbook/grafting/ +/zh/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ +/zh/subgraphs/cookbook/immutable-entities-bytes-as-ids/ +/zh/subgraphs/cookbook/near/ +/zh/subgraphs/cookbook/pruning/ +/zh/subgraphs/cookbook/subgraph-debug-forking/ +/zh/subgraphs/cookbook/subgraph-uncrashable/ +/zh/subgraphs/cookbook/substreams-powered-subgraphs/ +/zh/subgraphs/cookbook/timeseries/ +/zh/subgraphs/cookbook/transfer-to-the-graph/ +/zh/subgraphs/developing/creating/advanced/ +/zh/subgraphs/developing/creating/assemblyscript-mappings/ +/zh/subgraphs/developing/creating/graph-ts/api/ +/zh/subgraphs/developing/creating/graph-ts/common-issues/ +/zh/subgraphs/developing/creating/install-the-cli/ +/zh/subgraphs/developing/creating/ql-schema/ +/zh/subgraphs/developing/creating/starting-your-subgraph/ +/zh/subgraphs/developing/creating/subgraph-manifest/ +/zh/subgraphs/developing/creating/unit-testing-framework/ +/zh/subgraphs/developing/deploying/multiple-networks/ +/zh/subgraphs/developing/deploying/subgraph-studio-faqs/ +/zh/subgraphs/developing/deploying/using-subgraph-studio/ +/zh/subgraphs/developing/developer-faqs/ +/zh/subgraphs/developing/introduction/ +/zh/subgraphs/developing/managing/deleting-a-subgraph/ +/zh/subgraphs/developing/managing/transferring-a-subgraph/ +/zh/subgraphs/developing/publishing/publishing-a-subgraph/ +/zh/subgraphs/developing/subgraphs/ +/zh/subgraphs/explorer/ +/zh/subgraphs/querying/best-practices/ +/zh/subgraphs/querying/distributed-systems/ +/zh/subgraphs/querying/from-an-application/ +/zh/subgraphs/querying/graphql-api/ +/zh/subgraphs/querying/introduction/ +/zh/subgraphs/querying/managing-api-keys/ +/zh/subgraphs/querying/python/ +/zh/subgraphs/querying/subgraph-id-vs-deployment-id/ +/zh/subgraphs/quick-start/ +/zh/substreams/introduction/ +/zh/substreams/sps/introduction/ +/zh/substreams/sps/substreams-powered-subgraphs-faq/ +/zh/substreams/sps/triggers-example/ +/zh/substreams/sps/triggers/ +/zh/supported-networks/ From fa26b784f65724e28b684f6f06a63d198fdcce6c Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 14:50:35 -0500 Subject: [PATCH 13/22] More changes --- website/pages/ar/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/cs/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/de/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/en/indexing/_meta.js | 2 +- website/pages/en/indexing/{introduction.mdx => overview.mdx} | 2 +- website/pages/en/indexing/tooling/_meta.js | 2 +- .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 website/pages/en/resources/_meta.js | 2 +- website/pages/en/subgraphs/developing/_meta.js | 2 +- website/pages/en/subgraphs/developing/deploying/_meta.js | 2 +- .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../subgraphs/developing/developer-faq.mdx} | 2 +- website/pages/en/substreams/introduction.mdx | 2 +- website/pages/en/substreams/sps/_meta.js | 2 +- website/pages/en/substreams/sps/introduction.mdx | 2 +- .../substreams/sps/sps-faq.mdx} | 2 +- website/pages/es/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/fr/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/hi/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/it/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../subgraphs/developing/developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/ja/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/ko/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../subgraphs/developing/developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/mr/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/nl/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/pl/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/pt/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/ro/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/ru/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/sv/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/sw/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../subgraphs/developing/developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/tr/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/uk/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/ur/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 website/pages/vi/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../substreams/sps/sps-faq.mdx} | 0 website/pages/zh/indexing/{introduction.mdx => overview.mdx} | 0 .../tooling/{operating-graph-node.mdx => graph-node.mdx} | 0 .../{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} | 0 .../developing/{developer-faqs.mdx => developer-faq.mdx} | 0 .../sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} | 0 123 files changed, 11 insertions(+), 11 deletions(-) rename website/pages/ar/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/ar/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/ar/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/ar/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/ar/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/cs/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/cs/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/cs/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/cs/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/cs/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/de/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/de/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/de/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/de/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/de/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/en/indexing/{introduction.mdx => overview.mdx} (99%) rename website/pages/en/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/en/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/{sw/subgraphs/developing/developer-faqs.mdx => en/subgraphs/developing/developer-faq.mdx} (99%) rename website/pages/{vi/substreams/sps/substreams-powered-subgraphs-faq.mdx => en/substreams/sps/sps-faq.mdx} (99%) rename website/pages/es/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/es/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/es/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/es/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/{en/substreams/sps/substreams-powered-subgraphs-faq.mdx => es/substreams/sps/sps-faq.mdx} (100%) rename website/pages/fr/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/fr/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/fr/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/fr/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/fr/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/hi/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/hi/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/hi/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/hi/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/hi/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/it/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/it/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/it/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/{en/subgraphs/developing/developer-faqs.mdx => it/subgraphs/developing/developer-faq.mdx} (100%) rename website/pages/{es/substreams/sps/substreams-powered-subgraphs-faq.mdx => it/substreams/sps/sps-faq.mdx} (100%) rename website/pages/ja/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/ja/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/ja/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/ja/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/ja/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/ko/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/ko/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/ko/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/{it/subgraphs/developing/developer-faqs.mdx => ko/subgraphs/developing/developer-faq.mdx} (100%) rename website/pages/{it/substreams/sps/substreams-powered-subgraphs-faq.mdx => ko/substreams/sps/sps-faq.mdx} (100%) rename website/pages/mr/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/mr/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/mr/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/mr/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/{ko/substreams/sps/substreams-powered-subgraphs-faq.mdx => mr/substreams/sps/sps-faq.mdx} (100%) rename website/pages/nl/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/nl/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/nl/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/nl/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/{mr/substreams/sps/substreams-powered-subgraphs-faq.mdx => nl/substreams/sps/sps-faq.mdx} (100%) rename website/pages/pl/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/pl/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/pl/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/pl/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/{nl/substreams/sps/substreams-powered-subgraphs-faq.mdx => pl/substreams/sps/sps-faq.mdx} (100%) rename website/pages/pt/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/pt/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/pt/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/pt/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/pt/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/ro/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/ro/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/ro/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/ro/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/{pl/substreams/sps/substreams-powered-subgraphs-faq.mdx => ro/substreams/sps/sps-faq.mdx} (100%) rename website/pages/ru/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/ru/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/ru/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/ru/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/ru/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/sv/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/sv/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/sv/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/sv/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/sv/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/sw/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/sw/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/sw/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/{ko/subgraphs/developing/developer-faqs.mdx => sw/subgraphs/developing/developer-faq.mdx} (100%) rename website/pages/{ro/substreams/sps/substreams-powered-subgraphs-faq.mdx => sw/substreams/sps/sps-faq.mdx} (100%) rename website/pages/tr/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/tr/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/tr/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/tr/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/tr/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/uk/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/uk/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/uk/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/uk/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/{sw/substreams/sps/substreams-powered-subgraphs-faq.mdx => uk/substreams/sps/sps-faq.mdx} (100%) rename website/pages/ur/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/ur/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/ur/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/ur/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/ur/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) rename website/pages/vi/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/vi/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/vi/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/vi/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/{uk/substreams/sps/substreams-powered-subgraphs-faq.mdx => vi/substreams/sps/sps-faq.mdx} (100%) rename website/pages/zh/indexing/{introduction.mdx => overview.mdx} (100%) rename website/pages/zh/indexing/tooling/{operating-graph-node.mdx => graph-node.mdx} (100%) rename website/pages/zh/subgraphs/developing/deploying/{subgraph-studio-faqs.mdx => subgraph-studio-faq.mdx} (100%) rename website/pages/zh/subgraphs/developing/{developer-faqs.mdx => developer-faq.mdx} (100%) rename website/pages/zh/substreams/sps/{substreams-powered-subgraphs-faq.mdx => sps-faq.mdx} (100%) diff --git a/website/pages/ar/indexing/introduction.mdx b/website/pages/ar/indexing/overview.mdx similarity index 100% rename from website/pages/ar/indexing/introduction.mdx rename to website/pages/ar/indexing/overview.mdx diff --git a/website/pages/ar/indexing/tooling/operating-graph-node.mdx b/website/pages/ar/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/ar/indexing/tooling/operating-graph-node.mdx rename to website/pages/ar/indexing/tooling/graph-node.mdx diff --git a/website/pages/ar/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ar/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/ar/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ar/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/ar/subgraphs/developing/developer-faqs.mdx b/website/pages/ar/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/ar/subgraphs/developing/developer-faqs.mdx rename to website/pages/ar/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/ar/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ar/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/ar/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ar/substreams/sps/sps-faq.mdx diff --git a/website/pages/cs/indexing/introduction.mdx b/website/pages/cs/indexing/overview.mdx similarity index 100% rename from website/pages/cs/indexing/introduction.mdx rename to website/pages/cs/indexing/overview.mdx diff --git a/website/pages/cs/indexing/tooling/operating-graph-node.mdx b/website/pages/cs/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/cs/indexing/tooling/operating-graph-node.mdx rename to website/pages/cs/indexing/tooling/graph-node.mdx diff --git a/website/pages/cs/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/cs/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/cs/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/cs/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/cs/subgraphs/developing/developer-faqs.mdx b/website/pages/cs/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/cs/subgraphs/developing/developer-faqs.mdx rename to website/pages/cs/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/cs/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/cs/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/cs/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/cs/substreams/sps/sps-faq.mdx diff --git a/website/pages/de/indexing/introduction.mdx b/website/pages/de/indexing/overview.mdx similarity index 100% rename from website/pages/de/indexing/introduction.mdx rename to website/pages/de/indexing/overview.mdx diff --git a/website/pages/de/indexing/tooling/operating-graph-node.mdx b/website/pages/de/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/de/indexing/tooling/operating-graph-node.mdx rename to website/pages/de/indexing/tooling/graph-node.mdx diff --git a/website/pages/de/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/de/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/de/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/de/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/de/subgraphs/developing/developer-faqs.mdx b/website/pages/de/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/de/subgraphs/developing/developer-faqs.mdx rename to website/pages/de/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/de/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/de/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/de/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/de/substreams/sps/sps-faq.mdx diff --git a/website/pages/en/indexing/_meta.js b/website/pages/en/indexing/_meta.js index 9f6f8f332ccd..e21b0bd98653 100644 --- a/website/pages/en/indexing/_meta.js +++ b/website/pages/en/indexing/_meta.js @@ -1,5 +1,5 @@ export default { - introduction: 'Introduction', + overview: 'Overview', tooling: 'Indexer Tooling', tap: '', 'supported-network-requirements': '', diff --git a/website/pages/en/indexing/introduction.mdx b/website/pages/en/indexing/overview.mdx similarity index 99% rename from website/pages/en/indexing/introduction.mdx rename to website/pages/en/indexing/overview.mdx index 86688337a43e..a73c3acfad2d 100644 --- a/website/pages/en/indexing/introduction.mdx +++ b/website/pages/en/indexing/overview.mdx @@ -1,5 +1,5 @@ --- -title: Indexing +title: Indexing Overview --- Indexers are node operators in The Graph Network that stake Graph Tokens (GRT) in order to provide indexing and query processing services. Indexers earn query fees and indexing rewards for their services. They also earn query fees that are rebated according to an exponential rebate function. diff --git a/website/pages/en/indexing/tooling/_meta.js b/website/pages/en/indexing/tooling/_meta.js index b3d8363c749c..0bbd5b4df3d3 100644 --- a/website/pages/en/indexing/tooling/_meta.js +++ b/website/pages/en/indexing/tooling/_meta.js @@ -1,5 +1,5 @@ export default { - 'operating-graph-node': '', + 'graph-node': '', firehose: '', graphcast: '', } diff --git a/website/pages/en/indexing/tooling/operating-graph-node.mdx b/website/pages/en/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/en/indexing/tooling/operating-graph-node.mdx rename to website/pages/en/indexing/tooling/graph-node.mdx diff --git a/website/pages/en/resources/_meta.js b/website/pages/en/resources/_meta.js index 0c2022498337..9a0ccc054a52 100644 --- a/website/pages/en/resources/_meta.js +++ b/website/pages/en/resources/_meta.js @@ -2,6 +2,6 @@ export default { glossary: '', tokenomics: 'Tokenomics', benefits: '', - roles: 'Network Roles', + roles: 'Additional Roles', 'release-notes': 'Release Notes & Upgrade Guides', } diff --git a/website/pages/en/subgraphs/developing/_meta.js b/website/pages/en/subgraphs/developing/_meta.js index e14fdf572f74..0d7079b3d1ea 100644 --- a/website/pages/en/subgraphs/developing/_meta.js +++ b/website/pages/en/subgraphs/developing/_meta.js @@ -5,5 +5,5 @@ export default { deploying: 'Deploying', publishing: 'Publishing', managing: 'Managing', - 'developer-faqs': '', + 'developer-faq': 'FAQ', } diff --git a/website/pages/en/subgraphs/developing/deploying/_meta.js b/website/pages/en/subgraphs/developing/deploying/_meta.js index fb67773ec729..c4faacb5e561 100644 --- a/website/pages/en/subgraphs/developing/deploying/_meta.js +++ b/website/pages/en/subgraphs/developing/deploying/_meta.js @@ -1,5 +1,5 @@ export default { 'using-subgraph-studio': '', - 'subgraph-studio-faqs': '', + 'subgraph-studio-faq': '', 'multiple-networks': '', } diff --git a/website/pages/en/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/en/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/en/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/en/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/sw/subgraphs/developing/developer-faqs.mdx b/website/pages/en/subgraphs/developing/developer-faq.mdx similarity index 99% rename from website/pages/sw/subgraphs/developing/developer-faqs.mdx rename to website/pages/en/subgraphs/developing/developer-faq.mdx index 244aae52d0f4..b93fddcd90f1 100644 --- a/website/pages/sw/subgraphs/developing/developer-faqs.mdx +++ b/website/pages/en/subgraphs/developing/developer-faq.mdx @@ -1,5 +1,5 @@ --- -title: Developer FAQs +title: Developer FAQ --- This page summarizes some of the most common questions for developers building on The Graph. diff --git a/website/pages/en/substreams/introduction.mdx b/website/pages/en/substreams/introduction.mdx index 6385439f89f0..4fd0efb697aa 100644 --- a/website/pages/en/substreams/introduction.mdx +++ b/website/pages/en/substreams/introduction.mdx @@ -1,5 +1,5 @@ --- -title: Substreams +title: Introduction to Substreams --- ![Substreams Logo](/img/substreams-logo.png) diff --git a/website/pages/en/substreams/sps/_meta.js b/website/pages/en/substreams/sps/_meta.js index 6f0dc9c346ea..5f93de2d56e3 100644 --- a/website/pages/en/substreams/sps/_meta.js +++ b/website/pages/en/substreams/sps/_meta.js @@ -2,5 +2,5 @@ export default { introduction: 'Introduction', triggers: '', 'triggers-example': 'Tutorial', - 'substreams-powered-subgraphs-faq': 'SPS FAQ', + 'sps-faq': 'FAQ', } diff --git a/website/pages/en/substreams/sps/introduction.mdx b/website/pages/en/substreams/sps/introduction.mdx index 12e3f81c6d53..2a4de802eaf1 100644 --- a/website/pages/en/substreams/sps/introduction.mdx +++ b/website/pages/en/substreams/sps/introduction.mdx @@ -1,5 +1,5 @@ --- -title: Introduction to Substreams-powered Subgraphs +title: Introduction to Substreams-Powered Subgraphs --- By using a Substreams package (`.spkg`) as a data source, your subgraph gains access to a stream of pre-indexed blockchain data. This enables more efficient and scalable data handling, especially with large or complex blockchain networks. diff --git a/website/pages/vi/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/en/substreams/sps/sps-faq.mdx similarity index 99% rename from website/pages/vi/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/en/substreams/sps/sps-faq.mdx index 92c6a8313a5f..26b2cae1127e 100644 --- a/website/pages/vi/substreams/sps/substreams-powered-subgraphs-faq.mdx +++ b/website/pages/en/substreams/sps/sps-faq.mdx @@ -1,5 +1,5 @@ --- -title: Substreams-powered subgraphs FAQ +title: Substreams-Powered Subgraphs FAQ --- ## What are Substreams? diff --git a/website/pages/es/indexing/introduction.mdx b/website/pages/es/indexing/overview.mdx similarity index 100% rename from website/pages/es/indexing/introduction.mdx rename to website/pages/es/indexing/overview.mdx diff --git a/website/pages/es/indexing/tooling/operating-graph-node.mdx b/website/pages/es/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/es/indexing/tooling/operating-graph-node.mdx rename to website/pages/es/indexing/tooling/graph-node.mdx diff --git a/website/pages/es/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/es/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/es/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/es/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/es/subgraphs/developing/developer-faqs.mdx b/website/pages/es/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/es/subgraphs/developing/developer-faqs.mdx rename to website/pages/es/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/en/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/es/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/en/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/es/substreams/sps/sps-faq.mdx diff --git a/website/pages/fr/indexing/introduction.mdx b/website/pages/fr/indexing/overview.mdx similarity index 100% rename from website/pages/fr/indexing/introduction.mdx rename to website/pages/fr/indexing/overview.mdx diff --git a/website/pages/fr/indexing/tooling/operating-graph-node.mdx b/website/pages/fr/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/fr/indexing/tooling/operating-graph-node.mdx rename to website/pages/fr/indexing/tooling/graph-node.mdx diff --git a/website/pages/fr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/fr/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/fr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/fr/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/fr/subgraphs/developing/developer-faqs.mdx b/website/pages/fr/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/fr/subgraphs/developing/developer-faqs.mdx rename to website/pages/fr/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/fr/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/fr/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/fr/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/fr/substreams/sps/sps-faq.mdx diff --git a/website/pages/hi/indexing/introduction.mdx b/website/pages/hi/indexing/overview.mdx similarity index 100% rename from website/pages/hi/indexing/introduction.mdx rename to website/pages/hi/indexing/overview.mdx diff --git a/website/pages/hi/indexing/tooling/operating-graph-node.mdx b/website/pages/hi/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/hi/indexing/tooling/operating-graph-node.mdx rename to website/pages/hi/indexing/tooling/graph-node.mdx diff --git a/website/pages/hi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/hi/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/hi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/hi/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/hi/subgraphs/developing/developer-faqs.mdx b/website/pages/hi/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/hi/subgraphs/developing/developer-faqs.mdx rename to website/pages/hi/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/hi/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/hi/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/hi/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/hi/substreams/sps/sps-faq.mdx diff --git a/website/pages/it/indexing/introduction.mdx b/website/pages/it/indexing/overview.mdx similarity index 100% rename from website/pages/it/indexing/introduction.mdx rename to website/pages/it/indexing/overview.mdx diff --git a/website/pages/it/indexing/tooling/operating-graph-node.mdx b/website/pages/it/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/it/indexing/tooling/operating-graph-node.mdx rename to website/pages/it/indexing/tooling/graph-node.mdx diff --git a/website/pages/it/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/it/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/it/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/it/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/en/subgraphs/developing/developer-faqs.mdx b/website/pages/it/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/en/subgraphs/developing/developer-faqs.mdx rename to website/pages/it/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/es/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/it/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/es/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/it/substreams/sps/sps-faq.mdx diff --git a/website/pages/ja/indexing/introduction.mdx b/website/pages/ja/indexing/overview.mdx similarity index 100% rename from website/pages/ja/indexing/introduction.mdx rename to website/pages/ja/indexing/overview.mdx diff --git a/website/pages/ja/indexing/tooling/operating-graph-node.mdx b/website/pages/ja/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/ja/indexing/tooling/operating-graph-node.mdx rename to website/pages/ja/indexing/tooling/graph-node.mdx diff --git a/website/pages/ja/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ja/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/ja/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ja/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/ja/subgraphs/developing/developer-faqs.mdx b/website/pages/ja/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/ja/subgraphs/developing/developer-faqs.mdx rename to website/pages/ja/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/ja/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ja/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/ja/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ja/substreams/sps/sps-faq.mdx diff --git a/website/pages/ko/indexing/introduction.mdx b/website/pages/ko/indexing/overview.mdx similarity index 100% rename from website/pages/ko/indexing/introduction.mdx rename to website/pages/ko/indexing/overview.mdx diff --git a/website/pages/ko/indexing/tooling/operating-graph-node.mdx b/website/pages/ko/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/ko/indexing/tooling/operating-graph-node.mdx rename to website/pages/ko/indexing/tooling/graph-node.mdx diff --git a/website/pages/ko/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ko/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/ko/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ko/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/it/subgraphs/developing/developer-faqs.mdx b/website/pages/ko/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/it/subgraphs/developing/developer-faqs.mdx rename to website/pages/ko/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/it/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ko/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/it/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ko/substreams/sps/sps-faq.mdx diff --git a/website/pages/mr/indexing/introduction.mdx b/website/pages/mr/indexing/overview.mdx similarity index 100% rename from website/pages/mr/indexing/introduction.mdx rename to website/pages/mr/indexing/overview.mdx diff --git a/website/pages/mr/indexing/tooling/operating-graph-node.mdx b/website/pages/mr/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/mr/indexing/tooling/operating-graph-node.mdx rename to website/pages/mr/indexing/tooling/graph-node.mdx diff --git a/website/pages/mr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/mr/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/mr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/mr/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/mr/subgraphs/developing/developer-faqs.mdx b/website/pages/mr/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/mr/subgraphs/developing/developer-faqs.mdx rename to website/pages/mr/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/ko/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/mr/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/ko/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/mr/substreams/sps/sps-faq.mdx diff --git a/website/pages/nl/indexing/introduction.mdx b/website/pages/nl/indexing/overview.mdx similarity index 100% rename from website/pages/nl/indexing/introduction.mdx rename to website/pages/nl/indexing/overview.mdx diff --git a/website/pages/nl/indexing/tooling/operating-graph-node.mdx b/website/pages/nl/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/nl/indexing/tooling/operating-graph-node.mdx rename to website/pages/nl/indexing/tooling/graph-node.mdx diff --git a/website/pages/nl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/nl/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/nl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/nl/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/nl/subgraphs/developing/developer-faqs.mdx b/website/pages/nl/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/nl/subgraphs/developing/developer-faqs.mdx rename to website/pages/nl/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/mr/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/nl/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/mr/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/nl/substreams/sps/sps-faq.mdx diff --git a/website/pages/pl/indexing/introduction.mdx b/website/pages/pl/indexing/overview.mdx similarity index 100% rename from website/pages/pl/indexing/introduction.mdx rename to website/pages/pl/indexing/overview.mdx diff --git a/website/pages/pl/indexing/tooling/operating-graph-node.mdx b/website/pages/pl/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/pl/indexing/tooling/operating-graph-node.mdx rename to website/pages/pl/indexing/tooling/graph-node.mdx diff --git a/website/pages/pl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/pl/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/pl/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/pl/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/pl/subgraphs/developing/developer-faqs.mdx b/website/pages/pl/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/pl/subgraphs/developing/developer-faqs.mdx rename to website/pages/pl/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/nl/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/pl/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/nl/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/pl/substreams/sps/sps-faq.mdx diff --git a/website/pages/pt/indexing/introduction.mdx b/website/pages/pt/indexing/overview.mdx similarity index 100% rename from website/pages/pt/indexing/introduction.mdx rename to website/pages/pt/indexing/overview.mdx diff --git a/website/pages/pt/indexing/tooling/operating-graph-node.mdx b/website/pages/pt/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/pt/indexing/tooling/operating-graph-node.mdx rename to website/pages/pt/indexing/tooling/graph-node.mdx diff --git a/website/pages/pt/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/pt/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/pt/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/pt/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/pt/subgraphs/developing/developer-faqs.mdx b/website/pages/pt/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/pt/subgraphs/developing/developer-faqs.mdx rename to website/pages/pt/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/pt/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/pt/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/pt/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/pt/substreams/sps/sps-faq.mdx diff --git a/website/pages/ro/indexing/introduction.mdx b/website/pages/ro/indexing/overview.mdx similarity index 100% rename from website/pages/ro/indexing/introduction.mdx rename to website/pages/ro/indexing/overview.mdx diff --git a/website/pages/ro/indexing/tooling/operating-graph-node.mdx b/website/pages/ro/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/ro/indexing/tooling/operating-graph-node.mdx rename to website/pages/ro/indexing/tooling/graph-node.mdx diff --git a/website/pages/ro/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ro/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/ro/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ro/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/ro/subgraphs/developing/developer-faqs.mdx b/website/pages/ro/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/ro/subgraphs/developing/developer-faqs.mdx rename to website/pages/ro/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/pl/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ro/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/pl/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ro/substreams/sps/sps-faq.mdx diff --git a/website/pages/ru/indexing/introduction.mdx b/website/pages/ru/indexing/overview.mdx similarity index 100% rename from website/pages/ru/indexing/introduction.mdx rename to website/pages/ru/indexing/overview.mdx diff --git a/website/pages/ru/indexing/tooling/operating-graph-node.mdx b/website/pages/ru/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/ru/indexing/tooling/operating-graph-node.mdx rename to website/pages/ru/indexing/tooling/graph-node.mdx diff --git a/website/pages/ru/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ru/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/ru/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ru/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/ru/subgraphs/developing/developer-faqs.mdx b/website/pages/ru/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/ru/subgraphs/developing/developer-faqs.mdx rename to website/pages/ru/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/ru/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ru/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/ru/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ru/substreams/sps/sps-faq.mdx diff --git a/website/pages/sv/indexing/introduction.mdx b/website/pages/sv/indexing/overview.mdx similarity index 100% rename from website/pages/sv/indexing/introduction.mdx rename to website/pages/sv/indexing/overview.mdx diff --git a/website/pages/sv/indexing/tooling/operating-graph-node.mdx b/website/pages/sv/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/sv/indexing/tooling/operating-graph-node.mdx rename to website/pages/sv/indexing/tooling/graph-node.mdx diff --git a/website/pages/sv/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/sv/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/sv/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/sv/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/sv/subgraphs/developing/developer-faqs.mdx b/website/pages/sv/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/sv/subgraphs/developing/developer-faqs.mdx rename to website/pages/sv/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/sv/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/sv/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/sv/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/sv/substreams/sps/sps-faq.mdx diff --git a/website/pages/sw/indexing/introduction.mdx b/website/pages/sw/indexing/overview.mdx similarity index 100% rename from website/pages/sw/indexing/introduction.mdx rename to website/pages/sw/indexing/overview.mdx diff --git a/website/pages/sw/indexing/tooling/operating-graph-node.mdx b/website/pages/sw/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/sw/indexing/tooling/operating-graph-node.mdx rename to website/pages/sw/indexing/tooling/graph-node.mdx diff --git a/website/pages/sw/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/sw/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/sw/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/sw/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/ko/subgraphs/developing/developer-faqs.mdx b/website/pages/sw/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/ko/subgraphs/developing/developer-faqs.mdx rename to website/pages/sw/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/ro/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/sw/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/ro/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/sw/substreams/sps/sps-faq.mdx diff --git a/website/pages/tr/indexing/introduction.mdx b/website/pages/tr/indexing/overview.mdx similarity index 100% rename from website/pages/tr/indexing/introduction.mdx rename to website/pages/tr/indexing/overview.mdx diff --git a/website/pages/tr/indexing/tooling/operating-graph-node.mdx b/website/pages/tr/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/tr/indexing/tooling/operating-graph-node.mdx rename to website/pages/tr/indexing/tooling/graph-node.mdx diff --git a/website/pages/tr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/tr/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/tr/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/tr/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/tr/subgraphs/developing/developer-faqs.mdx b/website/pages/tr/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/tr/subgraphs/developing/developer-faqs.mdx rename to website/pages/tr/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/tr/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/tr/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/tr/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/tr/substreams/sps/sps-faq.mdx diff --git a/website/pages/uk/indexing/introduction.mdx b/website/pages/uk/indexing/overview.mdx similarity index 100% rename from website/pages/uk/indexing/introduction.mdx rename to website/pages/uk/indexing/overview.mdx diff --git a/website/pages/uk/indexing/tooling/operating-graph-node.mdx b/website/pages/uk/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/uk/indexing/tooling/operating-graph-node.mdx rename to website/pages/uk/indexing/tooling/graph-node.mdx diff --git a/website/pages/uk/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/uk/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/uk/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/uk/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/uk/subgraphs/developing/developer-faqs.mdx b/website/pages/uk/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/uk/subgraphs/developing/developer-faqs.mdx rename to website/pages/uk/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/sw/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/uk/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/sw/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/uk/substreams/sps/sps-faq.mdx diff --git a/website/pages/ur/indexing/introduction.mdx b/website/pages/ur/indexing/overview.mdx similarity index 100% rename from website/pages/ur/indexing/introduction.mdx rename to website/pages/ur/indexing/overview.mdx diff --git a/website/pages/ur/indexing/tooling/operating-graph-node.mdx b/website/pages/ur/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/ur/indexing/tooling/operating-graph-node.mdx rename to website/pages/ur/indexing/tooling/graph-node.mdx diff --git a/website/pages/ur/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/ur/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/ur/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/ur/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/ur/subgraphs/developing/developer-faqs.mdx b/website/pages/ur/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/ur/subgraphs/developing/developer-faqs.mdx rename to website/pages/ur/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/ur/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/ur/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/ur/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/ur/substreams/sps/sps-faq.mdx diff --git a/website/pages/vi/indexing/introduction.mdx b/website/pages/vi/indexing/overview.mdx similarity index 100% rename from website/pages/vi/indexing/introduction.mdx rename to website/pages/vi/indexing/overview.mdx diff --git a/website/pages/vi/indexing/tooling/operating-graph-node.mdx b/website/pages/vi/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/vi/indexing/tooling/operating-graph-node.mdx rename to website/pages/vi/indexing/tooling/graph-node.mdx diff --git a/website/pages/vi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/vi/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/vi/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/vi/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/vi/subgraphs/developing/developer-faqs.mdx b/website/pages/vi/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/vi/subgraphs/developing/developer-faqs.mdx rename to website/pages/vi/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/uk/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/vi/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/uk/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/vi/substreams/sps/sps-faq.mdx diff --git a/website/pages/zh/indexing/introduction.mdx b/website/pages/zh/indexing/overview.mdx similarity index 100% rename from website/pages/zh/indexing/introduction.mdx rename to website/pages/zh/indexing/overview.mdx diff --git a/website/pages/zh/indexing/tooling/operating-graph-node.mdx b/website/pages/zh/indexing/tooling/graph-node.mdx similarity index 100% rename from website/pages/zh/indexing/tooling/operating-graph-node.mdx rename to website/pages/zh/indexing/tooling/graph-node.mdx diff --git a/website/pages/zh/subgraphs/developing/deploying/subgraph-studio-faqs.mdx b/website/pages/zh/subgraphs/developing/deploying/subgraph-studio-faq.mdx similarity index 100% rename from website/pages/zh/subgraphs/developing/deploying/subgraph-studio-faqs.mdx rename to website/pages/zh/subgraphs/developing/deploying/subgraph-studio-faq.mdx diff --git a/website/pages/zh/subgraphs/developing/developer-faqs.mdx b/website/pages/zh/subgraphs/developing/developer-faq.mdx similarity index 100% rename from website/pages/zh/subgraphs/developing/developer-faqs.mdx rename to website/pages/zh/subgraphs/developing/developer-faq.mdx diff --git a/website/pages/zh/substreams/sps/substreams-powered-subgraphs-faq.mdx b/website/pages/zh/substreams/sps/sps-faq.mdx similarity index 100% rename from website/pages/zh/substreams/sps/substreams-powered-subgraphs-faq.mdx rename to website/pages/zh/substreams/sps/sps-faq.mdx From 70b5267a46e093b6f9b8314e72ef8287af5e5338 Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 14:50:44 -0500 Subject: [PATCH 14/22] Update dependencies --- packages/nextra-theme/package.json | 6 +- packages/og-image/package.json | 4 +- pnpm-lock.yaml | 641 ++++++++++++++--------------- website/package.json | 10 +- 4 files changed, 327 insertions(+), 334 deletions(-) diff --git a/packages/nextra-theme/package.json b/packages/nextra-theme/package.json index bc410dd6d7c8..6a9f14556e32 100644 --- a/packages/nextra-theme/package.json +++ b/packages/nextra-theme/package.json @@ -35,7 +35,7 @@ "theme-ui": "^0.16" }, "dependencies": { - "@docsearch/react": "^3.8.1", + "@docsearch/react": "^3.8.2", "@radix-ui/react-collapsible": "^1.1.2", "@radix-ui/react-visually-hidden": "^1.1.1", "lodash": "^4.17.21", @@ -43,8 +43,8 @@ "react-use": "^17.6.0" }, "devDependencies": { - "@edgeandnode/gds": "^5.39.1", - "@edgeandnode/go": "^6.74.0", + "@edgeandnode/gds": "^5.39.2", + "@edgeandnode/go": "^6.75.0", "@emotion/react": "^11.14.0", "@types/lodash": "^4.17.13", "@types/react": "^18.3.17", diff --git a/packages/og-image/package.json b/packages/og-image/package.json index 14f0aebacb98..d12492d4b49d 100644 --- a/packages/og-image/package.json +++ b/packages/og-image/package.json @@ -16,12 +16,12 @@ "yoga-wasm-web": "0.3.3" }, "devDependencies": { - "@cloudflare/workers-types": "^4.20241216.0", + "@cloudflare/workers-types": "^4.20241218.0", "@types/react": "^18.3.17", "jest-image-snapshot": "^6.4.0", "tsx": "^4.19.2", "typescript": "^5.7.2", "vitest": "^1.6.0", - "wrangler": "^3.95.0" + "wrangler": "^3.97.0" } } diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 1acd88a0cacf..33fa06c0ea35 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -48,8 +48,8 @@ importers: packages/nextra-theme: dependencies: '@docsearch/react': - specifier: ^3.8.1 - version: 3.8.1(@algolia/client-search@5.17.1)(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3) + specifier: ^3.8.2 + version: 3.8.2(@algolia/client-search@5.18.0)(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3) '@radix-ui/react-collapsible': specifier: ^1.1.2 version: 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) @@ -67,11 +67,11 @@ importers: version: 17.6.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1) devDependencies: '@edgeandnode/gds': - specifier: ^5.39.1 - version: 5.39.1(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2) + specifier: ^5.39.2 + version: 5.39.2(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2) '@edgeandnode/go': - specifier: ^6.74.0 - version: 6.74.0(k3a5ck5km3cbp2dg3adcgi6xwe) + specifier: ^6.75.0 + version: 6.75.0(sgicwllcqwwzqtazwqh6qnnbhy) '@emotion/react': specifier: ^11.14.0 version: 11.14.0(@types/react@18.3.17)(react@18.3.1) @@ -104,7 +104,7 @@ importers: version: 0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1) tsup: specifier: ^8.3.5 - version: 8.3.5(jiti@1.21.6)(postcss@8.4.49)(tsx@4.19.2)(typescript@5.7.2)(yaml@2.6.1) + version: 8.3.5(jiti@1.21.7)(postcss@8.4.49)(tsx@4.19.2)(typescript@5.7.2)(yaml@2.6.1) packages/og-image: dependencies: @@ -122,8 +122,8 @@ importers: version: 0.3.3 devDependencies: '@cloudflare/workers-types': - specifier: ^4.20241216.0 - version: 4.20241216.0 + specifier: ^4.20241218.0 + version: 4.20241218.0 '@types/react': specifier: ^18.3.17 version: 18.3.17 @@ -140,8 +140,8 @@ importers: specifier: ^1.6.0 version: 1.6.0(@types/node@22.10.2)(jsdom@24.1.3) wrangler: - specifier: ^3.95.0 - version: 3.95.0(@cloudflare/workers-types@4.20241216.0) + specifier: ^3.97.0 + version: 3.97.0(@cloudflare/workers-types@4.20241218.0) packages/remark-lint-restrict-elements: dependencies: @@ -155,14 +155,14 @@ importers: website: dependencies: '@edgeandnode/common': - specifier: ^6.38.0 - version: 6.38.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) + specifier: ^6.39.0 + version: 6.39.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) '@edgeandnode/gds': - specifier: ^5.39.1 - version: 5.39.1(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2) + specifier: ^5.39.2 + version: 5.39.2(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2) '@edgeandnode/go': - specifier: ^6.74.0 - version: 6.74.0(k3a5ck5km3cbp2dg3adcgi6xwe) + specifier: ^6.75.0 + version: 6.75.0(sgicwllcqwwzqtazwqh6qnnbhy) '@emotion/react': specifier: ^11.14.0 version: 11.14.0(@types/react@18.3.17)(react@18.3.1) @@ -176,8 +176,8 @@ importers: specifier: ^2.1.7 version: 2.1.7(react-dom@18.3.1(react@18.3.1))(react@18.3.1) mixpanel-browser: - specifier: ^2.56.0 - version: 2.56.0 + specifier: ^2.57.1 + version: 2.57.1 next: specifier: ^14.2.20 version: 14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) @@ -234,8 +234,8 @@ importers: specifier: ^8.4.49 version: 8.4.49 tailwindcss: - specifier: ^3.4.16 - version: 3.4.16(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) + specifier: ^3.4.17 + version: 3.4.17(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) tsx: specifier: ^4.19.2 version: 4.19.2 @@ -265,56 +265,56 @@ packages: '@algolia/client-search': '>= 4.9.1 < 6' algoliasearch: '>= 4.9.1 < 6' - '@algolia/client-abtesting@5.17.1': - resolution: {integrity: sha512-Os/xkQbDp5A5RdGYq1yS3fF69GoBJH5FIfrkVh+fXxCSe714i1Xdl9XoXhS4xG76DGKm6EFMlUqP024qjps8cg==} + '@algolia/client-abtesting@5.18.0': + resolution: {integrity: sha512-DLIrAukjsSrdMNNDx1ZTks72o4RH/1kOn8Wx5zZm8nnqFexG+JzY4SANnCNEjnFQPJTTvC+KpgiNW/CP2lumng==} engines: {node: '>= 14.0.0'} - '@algolia/client-analytics@5.17.1': - resolution: {integrity: sha512-WKpGC+cUhmdm3wndIlTh8RJXoVabUH+4HrvZHC4hXtvCYojEXYeep8RZstatwSZ7Ocg6Y2u67bLw90NEINuYEw==} + '@algolia/client-analytics@5.18.0': + resolution: {integrity: sha512-0VpGG2uQW+h2aejxbG8VbnMCQ9ary9/ot7OASXi6OjE0SRkYQ/+pkW+q09+IScif3pmsVVYggmlMPtAsmYWHng==} engines: {node: '>= 14.0.0'} - '@algolia/client-common@5.17.1': - resolution: {integrity: sha512-5rb5+yPIie6912riAypTSyzbE23a7UM1UpESvD8GEPI4CcWQvA9DBlkRNx9qbq/nJ5pvv8VjZjUxJj7rFkzEAA==} + '@algolia/client-common@5.18.0': + resolution: {integrity: sha512-X1WMSC+1ve2qlMsemyTF5bIjwipOT+m99Ng1Tyl36ZjQKTa54oajBKE0BrmM8LD8jGdtukAgkUhFoYOaRbMcmQ==} engines: {node: '>= 14.0.0'} - '@algolia/client-insights@5.17.1': - resolution: {integrity: sha512-nb/tfwBMn209TzFv1DDTprBKt/wl5btHVKoAww9fdEVdoKK02R2KAqxe5tuXLdEzAsS+LevRyOM/YjXuLmPtjQ==} + '@algolia/client-insights@5.18.0': + resolution: {integrity: sha512-FAJRNANUOSs/FgYOJ/Njqp+YTe4TMz2GkeZtfsw1TMiA5mVNRS/nnMpxas9771aJz7KTEWvK9GwqPs0K6RMYWg==} engines: {node: '>= 14.0.0'} - '@algolia/client-personalization@5.17.1': - resolution: {integrity: sha512-JuNlZe1SdW9KbV0gcgdsiVkFfXt0mmPassdS3cBSGvZGbPB9JsHthD719k5Y6YOY4dGvw1JmC1i9CwCQHAS8hg==} + '@algolia/client-personalization@5.18.0': + resolution: {integrity: sha512-I2dc94Oiwic3SEbrRp8kvTZtYpJjGtg5y5XnqubgnA15AgX59YIY8frKsFG8SOH1n2rIhUClcuDkxYQNXJLg+w==} engines: {node: '>= 14.0.0'} - '@algolia/client-query-suggestions@5.17.1': - resolution: {integrity: sha512-RBIFIv1QE3IlAikJKWTOpd6pwE4d2dY6t02iXH7r/SLXWn0HzJtsAPPeFg/OKkFvWAXt0H7In2/Mp7a1/Dy2pw==} + '@algolia/client-query-suggestions@5.18.0': + resolution: {integrity: sha512-x6XKIQgKFTgK/bMasXhghoEjHhmgoP61pFPb9+TaUJ32aKOGc65b12usiGJ9A84yS73UDkXS452NjyP50Knh/g==} engines: {node: '>= 14.0.0'} - '@algolia/client-search@5.17.1': - resolution: {integrity: sha512-bd5JBUOP71kPsxwDcvOxqtqXXVo/706NFifZ/O5Rx5GB8ZNVAhg4l7aGoT6jBvEfgmrp2fqPbkdIZ6JnuOpGcw==} + '@algolia/client-search@5.18.0': + resolution: {integrity: sha512-qI3LcFsVgtvpsBGR7aNSJYxhsR+Zl46+958ODzg8aCxIcdxiK7QEVLMJMZAR57jGqW0Lg/vrjtuLFDMfSE53qA==} engines: {node: '>= 14.0.0'} - '@algolia/ingestion@1.17.1': - resolution: {integrity: sha512-T18tvePi1rjRYcIKhd82oRukrPWHxG/Iy1qFGaxCplgRm9Im5z96qnYOq75MSKGOUHkFxaBKJOLmtn8xDR+Mcw==} + '@algolia/ingestion@1.18.0': + resolution: {integrity: sha512-bGvJg7HnGGm+XWYMDruZXWgMDPVt4yCbBqq8DM6EoaMBK71SYC4WMfIdJaw+ABqttjBhe6aKNRkWf/bbvYOGyw==} engines: {node: '>= 14.0.0'} - '@algolia/monitoring@1.17.1': - resolution: {integrity: sha512-gDtow+AUywTehRP8S1tWKx2IvhcJOxldAoqBxzN3asuQobF7er5n72auBeL++HY4ImEuzMi7PDOA/Iuwxs2IcA==} + '@algolia/monitoring@1.18.0': + resolution: {integrity: sha512-lBssglINIeGIR+8KyzH05NAgAmn1BCrm5D2T6pMtr/8kbTHvvrm1Zvcltc5dKUQEFyyx3J5+MhNc7kfi8LdjVw==} engines: {node: '>= 14.0.0'} - '@algolia/recommend@5.17.1': - resolution: {integrity: sha512-2992tTHkRe18qmf5SP57N78kN1D3e5t4PO1rt10sJncWtXBZWiNOK6K/UcvWsFbNSGAogFcIcvIMAl5mNp6RWA==} + '@algolia/recommend@5.18.0': + resolution: {integrity: sha512-uSnkm0cdAuFwdMp4pGT5vHVQ84T6AYpTZ3I0b3k/M3wg4zXDhl3aCiY8NzokEyRLezz/kHLEEcgb/tTTobOYVw==} engines: {node: '>= 14.0.0'} - '@algolia/requester-browser-xhr@5.17.1': - resolution: {integrity: sha512-XpKgBfyczVesKgr7DOShNyPPu5kqlboimRRPjdqAw5grSyHhCmb8yoTIKy0TCqBABZeXRPMYT13SMruUVRXvHA==} + '@algolia/requester-browser-xhr@5.18.0': + resolution: {integrity: sha512-1XFjW0C3pV0dS/9zXbV44cKI+QM4ZIz9cpatXpsjRlq6SUCpLID3DZHsXyE6sTb8IhyPaUjk78GEJT8/3hviqg==} engines: {node: '>= 14.0.0'} - '@algolia/requester-fetch@5.17.1': - resolution: {integrity: sha512-EhUomH+DZP5vb6DnEjT0GvXaXBSwzZnuU6hPGNU1EYKRXDouRjII/bIWpVjt7ycMgL2D2oQruqDh6rAWUhQwRw==} + '@algolia/requester-fetch@5.18.0': + resolution: {integrity: sha512-0uodeNdAHz1YbzJh6C5xeQ4T6x5WGiUxUq3GOaT/R4njh5t78dq+Rb187elr7KtnjUmETVVuCvmEYaThfTHzNg==} engines: {node: '>= 14.0.0'} - '@algolia/requester-node-http@5.17.1': - resolution: {integrity: sha512-PSnENJtl4/wBWXlGyOODbLYm6lSiFqrtww7UpQRCJdsHXlJKF8XAP6AME8NxvbE0Qo/RJUxK0mvyEh9sQcx6bg==} + '@algolia/requester-node-http@5.18.0': + resolution: {integrity: sha512-tZCqDrqJ2YE2I5ukCQrYN8oiF6u3JIdCxrtKq+eniuLkjkO78TKRnXrVcKZTmfFJyyDK8q47SfDcHzAA3nHi6w==} engines: {node: '>= 14.0.0'} '@alloc/quick-lru@5.2.0': @@ -665,12 +665,8 @@ packages: cpu: [x64] os: [win32] - '@cloudflare/workers-shared@0.11.0': - resolution: {integrity: sha512-A+lQ8xp7992qSeMmuQ0ssL6CPmm+ZmAv6Ddikan0n1jjpMAic+97l7xtVIsswSn9iLMFPYQ9uNN/8Fl0AgARIQ==} - engines: {node: '>=16.7.0'} - - '@cloudflare/workers-types@4.20241216.0': - resolution: {integrity: sha512-PGIINXS+aE9vD2GYyWXfRG+VyxxceRkGDCoPxqwUweh1Bfv75HVotyL/adJ7mRVwh3XZDifGBdTaLReTT+Fcog==} + '@cloudflare/workers-types@4.20241218.0': + resolution: {integrity: sha512-Y0brjmJHcAZBXOPI7lU5hbiXglQWniA1kQjot2ata+HFimyjPPcz+4QWBRrmWcMPo0OadR2Vmac7WStDLpvz0w==} '@corex/deepmerge@4.0.43': resolution: {integrity: sha512-N8uEMrMPL0cu/bdboEWpQYb/0i2K5Qn8eCsxzOmxSggJbbQte7ljMRoXm917AbntqTGOzdTu+vP3KOOzoC70HQ==} @@ -679,11 +675,11 @@ packages: resolution: {integrity: sha512-IchNf6dN4tHoMFIn/7OE8LWZ19Y6q/67Bmf6vnGREv8RSbBVb9LPJxEcnwrcwX6ixSvaiGoomAUvu4YSxXrVgw==} engines: {node: '>=12'} - '@docsearch/css@3.8.1': - resolution: {integrity: sha512-XiPhKT+ghUi4pEi/ACE9iDmwWsLA6d6xSwtR5ab48iB63OtYWFLZHUKdH7jHKTmwOs0Eg22TX4Kb3H5liFm5bQ==} + '@docsearch/css@3.8.2': + resolution: {integrity: sha512-y05ayQFyUmCXze79+56v/4HpycYF3uFqB78pLPrSV5ZKAlDuIAAJNhaRi8tTdRNXh05yxX/TyNnzD6LwSM89vQ==} - '@docsearch/react@3.8.1': - resolution: {integrity: sha512-7vgQuktQNBQdNWO1jbkiwgIrTZ0r5nPIHqcO3Z2neAWgkdUuldvvMfEOEaPXT5lqcezEv7i0h+tC285nD3jpZg==} + '@docsearch/react@3.8.2': + resolution: {integrity: sha512-xCRrJQlTt8N9GU0DG4ptwHRkfnSnD/YpdeaXe02iKfqs97TkZJv60yE+1eq/tjPcVnTW8dP5qLP7itifFVV5eg==} peerDependencies: '@types/react': '>= 16.8.0 < 19.0.0' react: '>= 16.8.0 < 19.0.0' @@ -699,8 +695,8 @@ packages: search-insights: optional: true - '@edgeandnode/common@6.38.0': - resolution: {integrity: sha512-MghQ6o72e3bNtTuqUNiL2tZf5JPoY8gT2zXMRJeiLFaekzxF9CKHEghCG4JpqaIxsKqAcNZ9s/GLFDsyEg7MtA==} + '@edgeandnode/common@6.39.0': + resolution: {integrity: sha512-R1hm02HjD2fcaoanUKJy64p8M3OGG0RWyHI77+qtvo2u9faBaLqf/aI/+An75Yx82MTpAE4Wc2AKo4GrHYRoyQ==} '@edgeandnode/eslint-config@2.0.3': resolution: {integrity: sha512-I89EK3cJNmJqJH1zLwyoKFFP6lrOWnPnZDgo8/Ew7BpOOA1Qhqcu0ek6erAo+mDt/4/4hlEu0Agrewr80NcImA==} @@ -711,8 +707,8 @@ packages: typescript: optional: true - '@edgeandnode/gds@5.39.1': - resolution: {integrity: sha512-cJHuca1UcLT6Tu8kMbySusXzPWZJUI/Kq/F11jWeYpl4P63CJoVHJBea3+WavN4K5FwaIo/Op7OmIo4b9NBPTA==} + '@edgeandnode/gds@5.39.2': + resolution: {integrity: sha512-zfY3lVUffyEgY5UDi6gOEqrJ35IRKnoLXMg/WAAHX6bvkn8XSEwZeef/Bvs8+dROtgGvXyGaWGaelXrpf/OZKQ==} peerDependencies: '@emotion/react': ^11 dayjs: ^1.11 @@ -724,11 +720,11 @@ packages: next: optional: true - '@edgeandnode/go@6.74.0': - resolution: {integrity: sha512-VWzATmJ/4fcuTs6kWhkHOcnKN1NYNpMH3lw7bWx/KSkwzNnDEqyDmDD47gxG6mnaSSyPtPdTg7bf6jxyfrjg8A==} + '@edgeandnode/go@6.75.0': + resolution: {integrity: sha512-eLgJyM0q3VYLAELCK5y8iLIAZJdozAnB7o4TVuJt6R/bZhkhdJDRaasc0XAPxjIF5S7x6H4qdvFLoo8RoY1YUg==} peerDependencies: - '@edgeandnode/common': ^6.38.0 - '@edgeandnode/gds': ^5.39.1 + '@edgeandnode/common': ^6.39.0 + '@edgeandnode/gds': ^5.39.2 '@emotion/react': ^11 next: '>=13' react: ^18 @@ -2455,8 +2451,8 @@ packages: react: '>= 16.8' react-dom: '>= 16.8' - '@pinax/graph-networks-registry@0.6.5': - resolution: {integrity: sha512-Urm/C+phjJLP+W5OF7hCUMrlSqSNGfX8V2BmzXmVkME/NX1yBZCQinR3Zk2L2uedpOBjmp3o7vm7bdQy+DMHhA==} + '@pinax/graph-networks-registry@0.6.6': + resolution: {integrity: sha512-CTCxALFO5xny41yEVQqoR4GwIIyTPwkqLCPd6iiVnY64zQFDGLKbiVbIFqOuVH9Q6srx+pLqlnVQep/1zNeddg==} '@pkgjs/parseargs@0.11.0': resolution: {integrity: sha512-+1VkjdD0QBLPodGrJUeqarH8VAIvQODIbwh9XpP5Syisf7YoQgsJKPNFoqqLQlu+VQ/tVSshMR6loPMn8U+dPg==} @@ -2485,8 +2481,8 @@ packages: '@types/react-dom': optional: true - '@radix-ui/react-alert-dialog@1.1.3': - resolution: {integrity: sha512-5xzWppXTNZe6zFrTTwAJIoMJeZmdFe0l8ZqQrPGKAVvhdyOWR4r53/G7SZqx6/uf1J441oxK7GzmTkrrWDroHA==} + '@radix-ui/react-alert-dialog@1.1.4': + resolution: {integrity: sha512-A6Kh23qZDLy3PSU4bh2UJZznOrUdHImIXqF8YtUa6CN73f8EOO9XlXSCd9IHyPvIquTaa/kwaSWzZTtUvgXVGw==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2555,8 +2551,8 @@ packages: '@types/react': optional: true - '@radix-ui/react-dialog@1.1.3': - resolution: {integrity: sha512-ujGvqQNkZ0J7caQyl8XuZRj2/TIrYcOGwqz5TeD1OMcCdfBuEMP0D12ve+8J5F9XuNUth3FAKFWo/wt0E/GJrQ==} + '@radix-ui/react-dialog@1.1.4': + resolution: {integrity: sha512-Ur7EV1IwQGCyaAuyDRiOLA5JIUZxELJljF+MbM/2NC0BYwfuRrbpS30BiQBJrVruscgUkieKkqXYDOoByaxIoA==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2577,8 +2573,8 @@ packages: '@types/react': optional: true - '@radix-ui/react-dismissable-layer@1.1.2': - resolution: {integrity: sha512-kEHnlhv7wUggvhuJPkyw4qspXLJOdYoAP4dO2c8ngGuXTq1w/HZp1YeVB+NQ2KbH1iEG+pvOCGYSqh9HZOz6hg==} + '@radix-ui/react-dismissable-layer@1.1.3': + resolution: {integrity: sha512-onrWn/72lQoEucDmJnr8uczSNTujT0vJnA/X5+3AkChVPowr8n1yvIKIabhWyMQeMvvmdpsvcyDqx3X1LEXCPg==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2590,8 +2586,8 @@ packages: '@types/react-dom': optional: true - '@radix-ui/react-dropdown-menu@2.1.3': - resolution: {integrity: sha512-eKyAfA9e4HOavzyGJC6kiDIlHMPzAU0zqSqTg+VwS0Okvb9nkTo7L4TugkCUqM3I06ciSpdtYQ73cgB7tyUgVw==} + '@radix-ui/react-dropdown-menu@2.1.4': + resolution: {integrity: sha512-iXU1Ab5ecM+yEepGAWK8ZhMyKX4ubFdCNtol4sT9D0OVErG9PNElfx3TQhjw7n7BC5nFVz68/5//clWy+8TXzA==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2647,8 +2643,8 @@ packages: '@types/react-dom': optional: true - '@radix-ui/react-menu@2.1.3': - resolution: {integrity: sha512-wY5SY6yCiJYP+DMIy7RrjF4shoFpB9LJltliVwejBm8T2yepWDJgKBhIFYOGWYR/lFHOCtbstN9duZFu6gmveQ==} + '@radix-ui/react-menu@2.1.4': + resolution: {integrity: sha512-BnOgVoL6YYdHAG6DtXONaR29Eq4nvbi8rutrV/xlr3RQCMMb3yqP85Qiw/3NReozrSW+4dfLkK+rc1hb4wPU/A==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2660,8 +2656,8 @@ packages: '@types/react-dom': optional: true - '@radix-ui/react-navigation-menu@1.2.2': - resolution: {integrity: sha512-7wHxgyNzOjsexOHFTXGJK/RDhKgrqj0siWJpm5i+sb7h+A6auY7efph6eMg0kOU4sVCLcbhHK7ZVueAXxOzvZA==} + '@radix-ui/react-navigation-menu@1.2.3': + resolution: {integrity: sha512-IQWAsQ7dsLIYDrn0WqPU+cdM7MONTv9nqrLVYoie3BPiabSfUVDe6Fr+oEt0Cofsr9ONDcDe9xhmJbL1Uq1yKg==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2673,8 +2669,8 @@ packages: '@types/react-dom': optional: true - '@radix-ui/react-popover@1.1.3': - resolution: {integrity: sha512-MBDKFwRe6fi0LT8m/Jl4V8J3WbS/UfXJtsgg8Ym5w5AyPG3XfHH4zhBp1P8HmZK83T8J7UzVm6/JpDE3WMl1Dw==} + '@radix-ui/react-popover@1.1.4': + resolution: {integrity: sha512-aUACAkXx8LaFymDma+HQVji7WhvEhpFJ7+qPz17Nf4lLZqtreGOFRiNQWQmhzp7kEWg9cOyyQJpdIMUMPc/CPw==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2786,8 +2782,8 @@ packages: '@types/react-dom': optional: true - '@radix-ui/react-toast@1.2.3': - resolution: {integrity: sha512-oB8irs7CGAml6zWbum7MNySTH/sR7PM1ZQyLV8reO946u73sU83yZUKijrMLNbm4hTOrJY4tE8Oa/XUKrOr2Wg==} + '@radix-ui/react-toast@1.2.4': + resolution: {integrity: sha512-Sch9idFJHJTMH9YNpxxESqABcAFweJG4tKv+0zo0m5XBvUSL8FM5xKcJLFLXononpePs8IclyX1KieL5SDUNgA==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -2799,8 +2795,8 @@ packages: '@types/react-dom': optional: true - '@radix-ui/react-tooltip@1.1.5': - resolution: {integrity: sha512-IucoQPcK5nwUuztaxBQvudvYwH58wtRcJlv1qvaMSyIbL9dEBfFN0vRf/D8xDbu6HmAJLlNGty4z8Na+vIqe9Q==} + '@radix-ui/react-tooltip@1.1.6': + resolution: {integrity: sha512-TLB5D8QLExS1uDn7+wH/bjEmRurNMTzNrtq7IjaS4kjion9NtzsTGkvR5+i7yc9q01Pi2KMM2cN3f8UG4IvvXA==} peerDependencies: '@types/react': '*' '@types/react-dom': '*' @@ -3980,8 +3976,8 @@ packages: resolution: {integrity: sha512-OME7WR6+5QwQs45A2079r+/FS0zU944+JCQwUX9GyIriCxqw2pGu4F9IEqmlwD+zSIMml0+MJnJJ47pFgSyWDw==} engines: {node: '>=10'} - '@uniswap/sdk-core@6.1.0': - resolution: {integrity: sha512-pJVv8rJZwemcp9xINFG7hjxM4H+1FNiDqjpxBabwpCBsBFKfJPwe65Wa8pk8p1yT3QOgA0yFEQuavNsmTdtJ7w==} + '@uniswap/sdk-core@6.1.1': + resolution: {integrity: sha512-S9D5NTn7vV+wYwXbKOmYVjJidgmKY6zUsG5KGlQO4fNvcIde1TtVgtMXJl06qv1JeJKbGnzkIAZG4R82lSVZCg==} engines: {node: '>=10'} '@uniswap/swap-router-contracts@1.3.1': @@ -4072,8 +4068,8 @@ packages: resolution: {integrity: sha512-t7kGrt2fdfNvzy1LCAE9/OnIyMtizgFhgJmk7iLJwQsLmR7S86F8Q4aDRPbCfo7pISJP6Fx/tPdfFNjHS23WTA==} engines: {node: '>=18.0.0'} - '@whatwg-node/server@0.9.63': - resolution: {integrity: sha512-rHBN2murCcuuhQru/AQjA13lA9SzQAH9k8ENy4iZrAmY+C0yFYPud3HiFgPUgzR1B2KYUpIYKwC1UAUlkzASOQ==} + '@whatwg-node/server@0.9.64': + resolution: {integrity: sha512-4HSOWOjFvPLY7F6zqs/kbSBHInHIxd50xnwtp3NXUrI+d92iOBLHKm9aIULwAn2ABPcnfXb55VQwb4bEV3g6KA==} engines: {node: '>=18.0.0'} '@xobotyi/scrollbar-width@1.9.5': @@ -4160,8 +4156,8 @@ packages: ajv@8.17.1: resolution: {integrity: sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==} - algoliasearch@5.17.1: - resolution: {integrity: sha512-3CcbT5yTWJDIcBe9ZHgsPi184SkT1kyZi3GWlQU5EFgvq1V73X2sqHRkPCQMe0RA/uvZbB+1sFeAk73eWygeLg==} + algoliasearch@5.18.0: + resolution: {integrity: sha512-/tfpK2A4FpS0o+S78o3YSdlqXr0MavJIDlFK3XZrlXLy7vaRXJvW5jYg3v5e/wCaF8y0IpMjkYLhoV6QqfpOgw==} engines: {node: '>= 14.0.0'} ansi-align@3.0.1: @@ -4624,8 +4620,8 @@ packages: resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==} engines: {node: '>= 8.10.0'} - chokidar@4.0.1: - resolution: {integrity: sha512-n8enUVCED/KVRQlab1hr3MVpcVMvxtZjmEa956u+4YijlmQED223XMSYj2tLuKvr4jcCTzNNMpQDUer72MMmzA==} + chokidar@4.0.2: + resolution: {integrity: sha512-/b57FK+bblSU+dfewfFe0rT1YjVDfOmeLQwCAuC+vwvgLkXboATqqmy+Ipux6JrF6L5joe5CBnFOw+gLWH6yKg==} engines: {node: '>= 14.16.0'} chownr@2.0.0: @@ -5246,8 +5242,8 @@ packages: resolution: {integrity: sha512-2QF/g9/zTaPDc3BjNcVTGoBbXBgYfMTTceLaYcFJ/W9kggFUkhxD/hMEeuLKbugyef9SqAx8cpgwlIP/jinUTA==} engines: {node: '>=4'} - dunder-proto@1.0.0: - resolution: {integrity: sha512-9+Sj30DIu+4KvHqMfLUGLFYL2PkURSYMVXJyXe92nFRvlYq5hBjLEhblKB+vkd/WVlUYMWigiY07T91Fkk0+4A==} + dunder-proto@1.0.1: + resolution: {integrity: sha512-KIN/nDJBQRcXw0MLVhZE9iQHmG68qAVIBg9CqmUYjmQIhgij9U5MFvrqkUL5FbtyyzZuOeOt0zdeRe4UY7ct+A==} engines: {node: '>= 0.4'} duplexify@4.1.3: @@ -5259,8 +5255,8 @@ packages: ee-first@1.1.1: resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==} - electron-to-chromium@1.5.73: - resolution: {integrity: sha512-8wGNxG9tAG5KhGd3eeA0o6ixhiNdgr0DcHWm85XPCphwZgD1lIEoi6t3VERayWao7SF7AAZTw6oARGJeVjH8Kg==} + electron-to-chromium@1.5.74: + resolution: {integrity: sha512-ck3//9RC+6oss/1Bh9tiAVFy5vfSKbRHAFh7Z3/eTRkEqJeWgymloShB17Vg3Z4nmDNp35vAd1BZ6CMW4Wt6Iw==} elkjs@0.9.3: resolution: {integrity: sha512-f/ZeWvW/BCXbhGEf1Ujp29EASo/lk1FDnETgNKwJrsVvGZhUWCZyg3xLJjAsxfOmt8KjswHmI5EwCQcPMpOYhQ==} @@ -5905,8 +5901,8 @@ packages: resolution: {integrity: sha512-VaUJspBffn/LMCJVoMvSAdmscJyS1auj5Zulnn5UoYcY531UWmdwhRWkcGKnGU93m5HSXP9LP2usOryrBtQowA==} engines: {node: '>=16'} - get-symbol-description@1.0.2: - resolution: {integrity: sha512-g0QYk1dZBxGwk+Ngc+ltRH2IBp2f7zBkBMBJZCDerh6EhlhSR6+9irMCuT/09zD6qkarHUSn529sK/yL4S27mg==} + get-symbol-description@1.1.0: + resolution: {integrity: sha512-w9UMqWwJxHNOvoNzSJ2oPF5wvYcvP7jUvYzhp67yEhTi17ZDBBC1z9pTdGuzjD+EFIqLSYRweZjqfiPzQ06Ebg==} engines: {node: '>= 0.4'} get-tsconfig@4.8.1: @@ -6306,8 +6302,8 @@ packages: is-alphanumerical@2.0.1: resolution: {integrity: sha512-hmbYhX/9MUMF5uh7tOXyK/n0ZvWpad5caBA17GsC6vyuCqaWliRG5K1qS9inmUhEMaOBIW7/whAnSwveW/LtZw==} - is-array-buffer@3.0.4: - resolution: {integrity: sha512-wcjaerHw0ydZwfhiKbXJWLDY8A7yV7KhjQOpb83hGgGfId/aQa4TOvwyzn2PuswW2gPCYEL/nEAiSVpdOj1lXw==} + is-array-buffer@3.0.5: + resolution: {integrity: sha512-DDfANUiiG2wC1qawP66qlTugJeL5HyzMpfr8lLK+jMQirGzNod0B12cFB/9q838Ru27sBwfw78/rdoU7RERz6A==} engines: {node: '>= 0.4'} is-arrayish@0.2.1: @@ -6380,8 +6376,8 @@ packages: resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==} engines: {node: '>=0.10.0'} - is-finalizationregistry@1.1.0: - resolution: {integrity: sha512-qfMdqbAQEwBw78ZyReKnlA8ezmPdb9BemzIIip/JkjaZUhitfXDkkr+3QTboW0JrSXT1QWyYShpvnNHGZ4c4yA==} + is-finalizationregistry@1.1.1: + resolution: {integrity: sha512-1pC6N8qWJbWoPtEjgcL2xyhQOP491EQjeUo3qTKcmV8YSDDJrOepfG8pcC7h/QgnQHYSv0mJ3Z/ZWxmatVrysg==} engines: {node: '>= 0.4'} is-fullwidth-code-point@3.0.0: @@ -6493,8 +6489,8 @@ packages: resolution: {integrity: sha512-9gGx6GTtCQM73BgmHQXfDmLtfjjTUDSyoxTCbp5WtoixAhfgsDirWIcVQ/IHpvI5Vgd5i/J5F7B9cN/WlVbC/w==} engines: {node: '>= 0.4'} - is-typed-array@1.1.13: - resolution: {integrity: sha512-uZ25/bUAlUY5fR4OKT4rZQEBrzQWYV9ZJYGGsUmEJ6thodVJ1HX64ePQ6Z0qPWP+m+Uq6e9UugrE38jeYsDSMw==} + is-typed-array@1.1.14: + resolution: {integrity: sha512-lQUsHzcTb7rH57dajbOuZEuMDXjs9f04ZloER4QOpjpKcaw4f98BRUrs8aiO9Z4G7i7B0Xhgarg6SCgYcYi8Nw==} engines: {node: '>= 0.4'} is-unc-path@1.0.0: @@ -6516,8 +6512,8 @@ packages: resolution: {integrity: sha512-SXM8Nwyys6nT5WP6pltOwKytLV7FqQ4UiibxVmW+EIosHcmCqkkjViTb5SNssDlkCiEYRP1/pdWUKVvZBmsR2Q==} engines: {node: '>= 0.4'} - is-weakset@2.0.3: - resolution: {integrity: sha512-LvIm3/KWzS9oRFHugab7d+M/GcBXuXX5xZkzPmN+NxihdQlZUQ4dWuSV1xR/sq6upL1TJEDrfBgRepHFdBtSNQ==} + is-weakset@2.0.4: + resolution: {integrity: sha512-mfcwb6IzQyOKTs84CQMrOwW4gQcaTOAWJ0zzJCl2WSPDrWk/OzDaImWFH3djXhb24g4eudZfLRozAvPGw4d9hQ==} engines: {node: '>= 0.4'} is-windows@1.0.2: @@ -6562,8 +6558,8 @@ packages: jest: optional: true - jiti@1.21.6: - resolution: {integrity: sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w==} + jiti@1.21.7: + resolution: {integrity: sha512-/imKNG4EbWNrVjoNC/1H5/9GFy+tqjGBHCaSsN+P2RnPqjsLmv6UD3Ej+Kj8nBWaRAwyk7kK5ZUc+OEatnTR3A==} hasBin: true joycon@3.1.1: @@ -6672,8 +6668,8 @@ packages: resolution: {integrity: sha512-ZZow9HBI5O6EPgSJLUb8n2NKgmVWTwCvHGwFuJlMjvLFqlGG6pjirPhtdsseaLZjSibD8eegzmYpUZwoIlj2cQ==} engines: {node: '>=4.0'} - katex@0.16.15: - resolution: {integrity: sha512-yE9YJIEAk2aZ+FL/G8r+UGw0CTUzEA8ZFy6E+8tc3spHUKq3qBnzCkI1CQwGoI9atJhVyFPEypQsTY7mJ1Pi9w==} + katex@0.16.17: + resolution: {integrity: sha512-OyzSrXBllz+Jdc9Auiw0kt21gbZ4hkz8Q5srVAb2U9INcYIfGKbxe+bvNvEz1bQ/NrDeRRho5eLCyk/L03maAw==} hasBin: true keccak@3.0.4: @@ -7271,8 +7267,8 @@ packages: mitt@3.0.1: resolution: {integrity: sha512-vKivATfr97l2/QBCYAkXYDbrIWPM2IIKEl7YPhjCvKlG3kE2gm+uBo6nEXK3M5/Ffh/FLpKExzOQ3JJoJGFKBw==} - mixpanel-browser@2.56.0: - resolution: {integrity: sha512-GYeEz58pV2M9MZtK8vSPL4oJmCwGS08FDDRZvZwr5VJpWdT4Lgyg6zXhmNfCmSTEIw2coaarm7HZ4FL9dAVvnA==} + mixpanel-browser@2.57.1: + resolution: {integrity: sha512-Qd3S+hu1zocN+AQgKYYoBDYhFaRXaKXtVRLuaApB5j5Qhe25eqSDKtMzkki5AmmuXH68O9i2FW5HkgCWgzJLyg==} mkdirp@1.0.4: resolution: {integrity: sha512-vVqVZQyf3WLx2Shd0qJ9xuvqgAyKPLAiqITEtqW0oIUjzo3PePDd6fW9iFz30ef7Ysp/oiWqbhszeGWW2T6Gzw==} @@ -8185,21 +8181,21 @@ packages: '@types/react': optional: true - react-remove-scroll@2.6.0: - resolution: {integrity: sha512-I2U4JVEsQenxDAKaVa3VZ/JeJZe0/2DxPWL8Tj8yLKctQJQiZM52pn/GWFpSp8dftjM3pSAHVJZscAnC/y+ySQ==} + react-remove-scroll@2.6.2: + resolution: {integrity: sha512-KmONPx5fnlXYJQqC62Q+lwIeAk64ws/cUw6omIumRzMRPqgnYqhSSti99nbj0Ry13bv7dF+BKn7NB+OqkdZGTw==} engines: {node: '>=10'} peerDependencies: - '@types/react': ^16.8.0 || ^17.0.0 || ^18.0.0 - react: ^16.8.0 || ^17.0.0 || ^18.0.0 + '@types/react': '*' + react: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 || ^19.0.0-rc peerDependenciesMeta: '@types/react': optional: true - react-smooth@4.0.3: - resolution: {integrity: sha512-PyxIrra8WZWrMRFcCiJsZ+JqFaxEINAt+v/w++wQKQlmO99Eh3+JTLeKApdTsLX2roBdWYXqPsaS8sO4UmdzIg==} + react-smooth@4.0.4: + resolution: {integrity: sha512-gnGKTpYwqL0Iii09gHobNolvX4Kiq4PKx6eWBCYYix+8cdw+cGo3do906l1NBPKkSWx1DghC1dlWG9L2uGd61Q==} peerDependencies: - react: ^16.8.0 || ^17.0.0 || ^18.0.0 - react-dom: ^16.8.0 || ^17.0.0 || ^18.0.0 + react: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 + react-dom: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 react-style-singleton@2.2.3: resolution: {integrity: sha512-b6jSvxvVnyptAiLjbkWLE/lOnR4lfTtDAl+eUC7RZy+QQWc6wRzIV2CE6xBuMmDxc2qIihtDCZD5NPOFl7fRBQ==} @@ -8981,8 +8977,8 @@ packages: tabbable@6.2.0: resolution: {integrity: sha512-Cat63mxsVJlzYvN51JmVXIgNoUokrIaT2zLclCXjRd8boZ0004U4KCs/sToJ75C6sdlByWxpYnb5Boif1VSFew==} - tailwindcss@3.4.16: - resolution: {integrity: sha512-TI4Cyx7gDiZ6r44ewaJmt0o6BrMCT5aK5e0rmJ/G9Xq3w7CX/5VXl/zIPEJZFUK5VEqwByyhqNPycPlvcK4ZNw==} + tailwindcss@3.4.17: + resolution: {integrity: sha512-w33E2aCvSDP0tW9RZuNXadXlkHXqFzSkQew/aIa2i/Sj8fThxwovwlXHSPXTbAHwEIhBFXAedUhP2tueAKP8Og==} engines: {node: '>=14.0.0'} hasBin: true @@ -9277,8 +9273,8 @@ packages: resolution: {integrity: sha512-gEymJYKZtKXzzBzM4jqa9w6Q1Jjm7x2d+sh19AdsD4wqnMPDYyvwpsIc2Q/835kHuo3BEQ7CjelGhfTsoBb2MQ==} engines: {node: '>= 0.4'} - typed-array-byte-length@1.0.1: - resolution: {integrity: sha512-3iMJ9q0ao7WE9tWcaYKIptkNBuOIcZCCT0d4MRvuuH88fEoEH62IuQe0OtraD3ebQEoTRk8XCBoknUNc1Y67pw==} + typed-array-byte-length@1.0.3: + resolution: {integrity: sha512-BaXgOuIxz8n8pIq3e7Atg/7s+DpiYrxn4vdot3w9KbnBhcRQq6o3xemQdIfynqSeXeDrF32x+WvfzmOjPiY9lg==} engines: {node: '>= 0.4'} typed-array-byte-offset@1.0.3: @@ -9337,8 +9333,8 @@ packages: resolution: {integrity: sha512-72RFADWFqKmUb2hmmvNODKL3p9hcB6Gt2DOQMis1SEBaV6a4MH8soBvzg+95CYhCKPFedut2JY9bMfrDl9D23g==} engines: {node: '>=14.0'} - unenv-nightly@2.0.0-20241204-140205-a5d5190: - resolution: {integrity: sha512-jpmAytLeiiW01pl5bhVn9wYJ4vtiLdhGe10oXlJBuQEX8mxjxO8BlEXGHU4vr4yEikjFP1wsomTHt/CLU8kUwg==} + unenv-nightly@2.0.0-20241212-153011-af71c96: + resolution: {integrity: sha512-Yugb9yPs/EZsPOY+IHloqVVEcZeJ0uwwViTedsZjOtVeYO8I29B1rzU/p84FMT0R1Ht3bHsKkNV/rzrjSd07QA==} unicode-trie@2.0.0: resolution: {integrity: sha512-x7bc76x0bm4prf1VLg79uhAzKw8DVboClSN5VxJuQ+LKDOVEW9CdH+VY7SP+vX7xCYQqzzgQpFqz15zeLvAtZQ==} @@ -9467,12 +9463,12 @@ packages: urlpattern-polyfill@10.0.0: resolution: {integrity: sha512-H/A06tKD7sS1O1X2SshBVeA5FLycRpjqiBeqGKmBwBDBy28EnRjORxTNe269KSSr5un5qyWi1iL61wLxpd+ZOg==} - use-callback-ref@1.3.2: - resolution: {integrity: sha512-elOQwe6Q8gqZgDA8mrh44qRTQqpIHDcZ3hXTLjBe1i4ph8XpNJnO+aQf3NaG+lriLopI4HMx9VjQLfPQ6vhnoA==} + use-callback-ref@1.3.3: + resolution: {integrity: sha512-jQL3lRnocaFtu3V00JToYz/4QkNWswxijDaCVNZRiRTO3HQDLsdu1ZtmIUvV4yPp+rvWm5j0y0TG/S61cuijTg==} engines: {node: '>=10'} peerDependencies: - '@types/react': ^16.8.0 || ^17.0.0 || ^18.0.0 - react: ^16.8.0 || ^17.0.0 || ^18.0.0 + '@types/react': '*' + react: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 || ^19.0.0-rc peerDependenciesMeta: '@types/react': optional: true @@ -9740,9 +9736,10 @@ packages: workerpool@6.5.1: resolution: {integrity: sha512-Fs4dNYcsdpYSAfVxhnl1L5zTksjvOJxtC5hzMNl+1t9B8hTJTdKDyZ5ju7ztgPy+ft9tBFXoOlDNiOT9WUXZlA==} - wrangler@3.95.0: - resolution: {integrity: sha512-3w5852i3FNyDz421K2Qk4v5L8jjwegO5O8E1+VAQmjnm82HFNxpIRUBq0bmM7CTLvOPI/Jjcmj/eAWjQBL7QYg==} + wrangler@3.97.0: + resolution: {integrity: sha512-NkFAigqZWe4NOK0gYROcpvdugaYJE/JRFrIZ+c5Q5/uie+25WH8OVbRvvmiXhWVhso56cZs2W2TPmAxT/sgHkw==} engines: {node: '>=16.17.0'} + deprecated: Downgrade to 3.96.0 hasBin: true peerDependencies: '@cloudflare/workers-types': ^4.20241205.0 @@ -9903,110 +9900,110 @@ packages: snapshots: - '@algolia/autocomplete-core@1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1)(search-insights@2.17.3)': + '@algolia/autocomplete-core@1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0)(search-insights@2.17.3)': dependencies: - '@algolia/autocomplete-plugin-algolia-insights': 1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1)(search-insights@2.17.3) - '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1) + '@algolia/autocomplete-plugin-algolia-insights': 1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0)(search-insights@2.17.3) + '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0) transitivePeerDependencies: - '@algolia/client-search' - algoliasearch - search-insights - '@algolia/autocomplete-plugin-algolia-insights@1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1)(search-insights@2.17.3)': + '@algolia/autocomplete-plugin-algolia-insights@1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0)(search-insights@2.17.3)': dependencies: - '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1) + '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0) search-insights: 2.17.3 transitivePeerDependencies: - '@algolia/client-search' - algoliasearch - '@algolia/autocomplete-preset-algolia@1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1)': + '@algolia/autocomplete-preset-algolia@1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0)': dependencies: - '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1) - '@algolia/client-search': 5.17.1 - algoliasearch: 5.17.1 + '@algolia/autocomplete-shared': 1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0) + '@algolia/client-search': 5.18.0 + algoliasearch: 5.18.0 - '@algolia/autocomplete-shared@1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1)': + '@algolia/autocomplete-shared@1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0)': dependencies: - '@algolia/client-search': 5.17.1 - algoliasearch: 5.17.1 + '@algolia/client-search': 5.18.0 + algoliasearch: 5.18.0 - '@algolia/client-abtesting@5.17.1': + '@algolia/client-abtesting@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/client-analytics@5.17.1': + '@algolia/client-analytics@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/client-common@5.17.1': {} + '@algolia/client-common@5.18.0': {} - '@algolia/client-insights@5.17.1': + '@algolia/client-insights@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/client-personalization@5.17.1': + '@algolia/client-personalization@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/client-query-suggestions@5.17.1': + '@algolia/client-query-suggestions@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/client-search@5.17.1': + '@algolia/client-search@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/ingestion@1.17.1': + '@algolia/ingestion@1.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/monitoring@1.17.1': + '@algolia/monitoring@1.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/recommend@5.17.1': + '@algolia/recommend@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + '@algolia/client-common': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 - '@algolia/requester-browser-xhr@5.17.1': + '@algolia/requester-browser-xhr@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 + '@algolia/client-common': 5.18.0 - '@algolia/requester-fetch@5.17.1': + '@algolia/requester-fetch@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 + '@algolia/client-common': 5.18.0 - '@algolia/requester-node-http@5.17.1': + '@algolia/requester-node-http@5.18.0': dependencies: - '@algolia/client-common': 5.17.1 + '@algolia/client-common': 5.18.0 '@alloc/quick-lru@5.2.0': {} @@ -10436,12 +10433,7 @@ snapshots: '@cloudflare/workerd-windows-64@1.20241205.0': optional: true - '@cloudflare/workers-shared@0.11.0': - dependencies: - mime: 3.0.0 - zod: 3.24.1 - - '@cloudflare/workers-types@4.20241216.0': {} + '@cloudflare/workers-types@4.20241218.0': {} '@corex/deepmerge@4.0.43': {} @@ -10449,14 +10441,14 @@ snapshots: dependencies: '@jridgewell/trace-mapping': 0.3.9 - '@docsearch/css@3.8.1': {} + '@docsearch/css@3.8.2': {} - '@docsearch/react@3.8.1(@algolia/client-search@5.17.1)(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3)': + '@docsearch/react@3.8.2(@algolia/client-search@5.18.0)(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(search-insights@2.17.3)': dependencies: - '@algolia/autocomplete-core': 1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1)(search-insights@2.17.3) - '@algolia/autocomplete-preset-algolia': 1.17.7(@algolia/client-search@5.17.1)(algoliasearch@5.17.1) - '@docsearch/css': 3.8.1 - algoliasearch: 5.17.1 + '@algolia/autocomplete-core': 1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0)(search-insights@2.17.3) + '@algolia/autocomplete-preset-algolia': 1.17.7(@algolia/client-search@5.18.0)(algoliasearch@5.18.0) + '@docsearch/css': 3.8.2 + algoliasearch: 5.18.0 optionalDependencies: '@types/react': 18.3.17 react: 18.3.1 @@ -10465,10 +10457,10 @@ snapshots: transitivePeerDependencies: - '@algolia/client-search' - '@edgeandnode/common@6.38.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))': + '@edgeandnode/common@6.39.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))': dependencies: '@ethersproject/providers': 5.7.2 - '@pinax/graph-networks-registry': 0.6.5 + '@pinax/graph-networks-registry': 0.6.6 '@uniswap/sdk-core': 5.9.0 '@uniswap/v3-core': 1.0.1 '@uniswap/v3-sdk': 3.19.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) @@ -10508,28 +10500,28 @@ snapshots: - eslint-plugin-import-x - supports-color - '@edgeandnode/gds@5.39.1(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)': + '@edgeandnode/gds@5.39.2(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)': dependencies: - '@edgeandnode/common': 6.38.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) + '@edgeandnode/common': 6.39.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) '@emotion/react': 11.14.0(@types/react@18.3.17)(react@18.3.1) '@figma/code-connect': 1.2.4 '@floating-ui/react-dom': 2.1.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@headlessui/react': 2.2.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@phosphor-icons/react': 2.1.7(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-accordion': 1.2.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) - '@radix-ui/react-alert-dialog': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) - '@radix-ui/react-dialog': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-alert-dialog': 1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dialog': 1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-direction': 1.1.0(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dropdown-menu': 2.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dropdown-menu': 2.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-label': 2.1.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) - '@radix-ui/react-popover': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-popover': 1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-slider': 1.2.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-slot': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-switch': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) - '@radix-ui/react-toast': 1.2.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) - '@radix-ui/react-tooltip': 1.1.5(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-toast': 1.2.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-tooltip': 1.1.6(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@react-aria/utils': 3.26.0(react@18.3.1) - '@tailwindcss/container-queries': 0.1.1(tailwindcss@3.4.16(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))) + '@tailwindcss/container-queries': 0.1.1(tailwindcss@3.4.17(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))) '@tanem/react-nprogress': 5.0.53(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@theme-ui/core': 0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1) '@theme-ui/css': 0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1)) @@ -10558,7 +10550,7 @@ snapshots: react-virtuoso: 4.12.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1) recharts: 2.15.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1) shiki: 1.24.2 - tailwindcss: 3.4.16(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) + tailwindcss: 3.4.17(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) theme-ui: 0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1) typy: 3.3.0 universal-cookie: 7.2.2 @@ -10578,14 +10570,14 @@ snapshots: - typescript - utf-8-validate - '@edgeandnode/go@6.74.0(k3a5ck5km3cbp2dg3adcgi6xwe)': + '@edgeandnode/go@6.75.0(sgicwllcqwwzqtazwqh6qnnbhy)': dependencies: - '@edgeandnode/common': 6.38.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) - '@edgeandnode/gds': 5.39.1(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2) + '@edgeandnode/common': 6.39.0(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) + '@edgeandnode/gds': 5.39.2(@emotion/is-prop-valid@0.8.8)(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(dayjs@1.11.13)(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2))(next@14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1))(react-dom@18.3.1(react@18.3.1))(react@18.3.1)(theme-ui@0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1))(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2) '@emotion/react': 11.14.0(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-collapsible': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) - '@radix-ui/react-dialog': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) - '@radix-ui/react-navigation-menu': 1.2.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dialog': 1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-navigation-menu': 1.2.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-portal': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@theme-ui/core': 0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1) classnames: 2.5.1 @@ -10593,7 +10585,7 @@ snapshots: motion: 11.15.0(@emotion/is-prop-valid@0.8.8)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) react: 18.3.1 react-dom: 18.3.1(react@18.3.1) - tailwindcss: 3.4.16(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) + tailwindcss: 3.4.17(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) theme-ui: 0.17.1(@emotion/react@11.14.0(@types/react@18.3.17)(react@18.3.1))(react@18.3.1) optionalDependencies: next: 14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) @@ -11888,7 +11880,7 @@ snapshots: '@graphql-mesh/types': 0.98.10(@graphql-mesh/store@0.98.10)(@graphql-tools/utils@10.6.4(graphql@16.10.0))(graphql@16.10.0)(tslib@2.8.1) '@graphql-mesh/utils': 0.98.10(@graphql-mesh/cross-helpers@0.4.9(graphql@16.10.0))(@graphql-mesh/types@0.98.10)(@graphql-tools/utils@10.6.4(graphql@16.10.0))(graphql@16.10.0)(tslib@2.8.1) '@graphql-tools/utils': 10.6.4(graphql@16.10.0) - '@whatwg-node/server': 0.9.63 + '@whatwg-node/server': 0.9.64 graphql: 16.10.0 graphql-yoga: 5.10.6(graphql@16.10.0) tslib: 2.8.1 @@ -12831,7 +12823,7 @@ snapshots: react: 18.3.1 react-dom: 18.3.1(react@18.3.1) - '@pinax/graph-networks-registry@0.6.5': {} + '@pinax/graph-networks-registry@0.6.6': {} '@pkgjs/parseargs@0.11.0': optional: true @@ -12859,12 +12851,12 @@ snapshots: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) - '@radix-ui/react-alert-dialog@1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-alert-dialog@1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dialog': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dialog': 1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-primitive': 2.0.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-slot': 1.1.1(@types/react@18.3.17)(react@18.3.1) react: 18.3.1 @@ -12922,12 +12914,12 @@ snapshots: optionalDependencies: '@types/react': 18.3.17 - '@radix-ui/react-dialog@1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-dialog@1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dismissable-layer': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dismissable-layer': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-focus-guards': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-focus-scope': 1.1.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-id': 1.1.0(@types/react@18.3.17)(react@18.3.1) @@ -12939,7 +12931,7 @@ snapshots: aria-hidden: 1.2.4 react: 18.3.1 react-dom: 18.3.1(react@18.3.1) - react-remove-scroll: 2.6.0(@types/react@18.3.17)(react@18.3.1) + react-remove-scroll: 2.6.2(@types/react@18.3.17)(react@18.3.1) optionalDependencies: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) @@ -12950,7 +12942,7 @@ snapshots: optionalDependencies: '@types/react': 18.3.17 - '@radix-ui/react-dismissable-layer@1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-dismissable-layer@1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) @@ -12963,13 +12955,13 @@ snapshots: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) - '@radix-ui/react-dropdown-menu@2.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-dropdown-menu@2.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-id': 1.1.0(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-menu': 2.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-menu': 2.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-primitive': 2.0.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-use-controllable-state': 1.1.0(@types/react@18.3.17)(react@18.3.1) react: 18.3.1 @@ -13011,14 +13003,14 @@ snapshots: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) - '@radix-ui/react-menu@2.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-menu@2.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-collection': 1.1.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-direction': 1.1.0(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dismissable-layer': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dismissable-layer': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-focus-guards': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-focus-scope': 1.1.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-id': 1.1.0(@types/react@18.3.17)(react@18.3.1) @@ -13032,19 +13024,19 @@ snapshots: aria-hidden: 1.2.4 react: 18.3.1 react-dom: 18.3.1(react@18.3.1) - react-remove-scroll: 2.6.0(@types/react@18.3.17)(react@18.3.1) + react-remove-scroll: 2.6.2(@types/react@18.3.17)(react@18.3.1) optionalDependencies: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) - '@radix-ui/react-navigation-menu@1.2.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-navigation-menu@1.2.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-collection': 1.1.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-direction': 1.1.0(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dismissable-layer': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dismissable-layer': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-id': 1.1.0(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-presence': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-primitive': 2.0.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) @@ -13059,12 +13051,12 @@ snapshots: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) - '@radix-ui/react-popover@1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-popover@1.1.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dismissable-layer': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dismissable-layer': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-focus-guards': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-focus-scope': 1.1.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-id': 1.1.0(@types/react@18.3.17)(react@18.3.1) @@ -13077,7 +13069,7 @@ snapshots: aria-hidden: 1.2.4 react: 18.3.1 react-dom: 18.3.1(react@18.3.1) - react-remove-scroll: 2.6.0(@types/react@18.3.17)(react@18.3.1) + react-remove-scroll: 2.6.2(@types/react@18.3.17)(react@18.3.1) optionalDependencies: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) @@ -13187,13 +13179,13 @@ snapshots: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) - '@radix-ui/react-toast@1.2.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-toast@1.2.4(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-collection': 1.1.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dismissable-layer': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dismissable-layer': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-portal': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-presence': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-primitive': 2.0.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) @@ -13207,12 +13199,12 @@ snapshots: '@types/react': 18.3.17 '@types/react-dom': 18.3.5(@types/react@18.3.17) - '@radix-ui/react-tooltip@1.1.5(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': + '@radix-ui/react-tooltip@1.1.6(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: '@radix-ui/primitive': 1.1.1 '@radix-ui/react-compose-refs': 1.1.1(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-context': 1.1.1(@types/react@18.3.17)(react@18.3.1) - '@radix-ui/react-dismissable-layer': 1.1.2(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + '@radix-ui/react-dismissable-layer': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-id': 1.1.0(@types/react@18.3.17)(react@18.3.1) '@radix-ui/react-popper': 1.2.1(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) '@radix-ui/react-portal': 1.1.3(@types/react-dom@18.3.5(@types/react@18.3.17))(@types/react@18.3.17)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) @@ -14456,9 +14448,9 @@ snapshots: '@swc/counter': 0.1.3 tslib: 2.8.1 - '@tailwindcss/container-queries@0.1.1(tailwindcss@3.4.16(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)))': + '@tailwindcss/container-queries@0.1.1(tailwindcss@3.4.17(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)))': dependencies: - tailwindcss: 3.4.16(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) + tailwindcss: 3.4.17(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)) '@tanem/react-nprogress@5.0.53(react-dom@18.3.1(react@18.3.1))(react@18.3.1)': dependencies: @@ -14873,7 +14865,7 @@ snapshots: tiny-invariant: 1.3.3 toformat: 2.0.0 - '@uniswap/sdk-core@6.1.0': + '@uniswap/sdk-core@6.1.1': dependencies: '@ethersproject/address': 5.7.0 '@ethersproject/bytes': 5.7.0 @@ -14914,7 +14906,7 @@ snapshots: dependencies: '@ethersproject/abi': 5.7.0 '@ethersproject/solidity': 5.7.0 - '@uniswap/sdk-core': 6.1.0 + '@uniswap/sdk-core': 6.1.1 '@uniswap/swap-router-contracts': 1.3.1(hardhat@2.14.1(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2))(typescript@5.7.2)) '@uniswap/v3-periphery': 1.4.4 '@uniswap/v3-staker': 1.0.0 @@ -15013,7 +15005,7 @@ snapshots: fast-querystring: 1.1.2 tslib: 2.8.1 - '@whatwg-node/server@0.9.63': + '@whatwg-node/server@0.9.64': dependencies: '@whatwg-node/disposablestack': 0.0.5 '@whatwg-node/fetch': 0.10.1 @@ -15102,21 +15094,21 @@ snapshots: json-schema-traverse: 1.0.0 require-from-string: 2.0.2 - algoliasearch@5.17.1: - dependencies: - '@algolia/client-abtesting': 5.17.1 - '@algolia/client-analytics': 5.17.1 - '@algolia/client-common': 5.17.1 - '@algolia/client-insights': 5.17.1 - '@algolia/client-personalization': 5.17.1 - '@algolia/client-query-suggestions': 5.17.1 - '@algolia/client-search': 5.17.1 - '@algolia/ingestion': 1.17.1 - '@algolia/monitoring': 1.17.1 - '@algolia/recommend': 5.17.1 - '@algolia/requester-browser-xhr': 5.17.1 - '@algolia/requester-fetch': 5.17.1 - '@algolia/requester-node-http': 5.17.1 + algoliasearch@5.18.0: + dependencies: + '@algolia/client-abtesting': 5.18.0 + '@algolia/client-analytics': 5.18.0 + '@algolia/client-common': 5.18.0 + '@algolia/client-insights': 5.18.0 + '@algolia/client-personalization': 5.18.0 + '@algolia/client-query-suggestions': 5.18.0 + '@algolia/client-search': 5.18.0 + '@algolia/ingestion': 1.18.0 + '@algolia/monitoring': 1.18.0 + '@algolia/recommend': 5.18.0 + '@algolia/requester-browser-xhr': 5.18.0 + '@algolia/requester-fetch': 5.18.0 + '@algolia/requester-node-http': 5.18.0 ansi-align@3.0.1: dependencies: @@ -15190,7 +15182,7 @@ snapshots: array-buffer-byte-length@1.0.1: dependencies: call-bind: 1.0.8 - is-array-buffer: 3.0.4 + is-array-buffer: 3.0.5 array-flatten@1.1.1: {} @@ -15253,7 +15245,7 @@ snapshots: es-abstract: 1.23.6 es-errors: 1.3.0 get-intrinsic: 1.2.6 - is-array-buffer: 3.0.4 + is-array-buffer: 3.0.5 as-table@1.0.55: dependencies: @@ -15469,7 +15461,7 @@ snapshots: browserslist@4.24.3: dependencies: caniuse-lite: 1.0.30001689 - electron-to-chromium: 1.5.73 + electron-to-chromium: 1.5.74 node-releases: 2.0.19 update-browserslist-db: 1.1.1(browserslist@4.24.3) @@ -15691,7 +15683,7 @@ snapshots: optionalDependencies: fsevents: 2.3.3 - chokidar@4.0.1: + chokidar@4.0.2: dependencies: readdirp: 4.0.2 @@ -16310,7 +16302,7 @@ snapshots: dset@3.1.4: {} - dunder-proto@1.0.0: + dunder-proto@1.0.1: dependencies: call-bind-apply-helpers: 1.0.1 es-errors: 1.3.0 @@ -16327,7 +16319,7 @@ snapshots: ee-first@1.1.1: {} - electron-to-chromium@1.5.73: {} + electron-to-chromium@1.5.74: {} elkjs@0.9.3: {} @@ -16415,7 +16407,7 @@ snapshots: es-to-primitive: 1.3.0 function.prototype.name: 1.1.7 get-intrinsic: 1.2.6 - get-symbol-description: 1.0.2 + get-symbol-description: 1.1.0 globalthis: 1.0.4 gopd: 1.2.0 has-property-descriptors: 1.0.2 @@ -16423,14 +16415,14 @@ snapshots: has-symbols: 1.1.0 hasown: 2.0.2 internal-slot: 1.1.0 - is-array-buffer: 3.0.4 + is-array-buffer: 3.0.5 is-callable: 1.2.7 is-data-view: 1.0.2 is-negative-zero: 2.0.3 is-regex: 1.2.1 is-shared-array-buffer: 1.0.3 is-string: 1.1.1 - is-typed-array: 1.1.13 + is-typed-array: 1.1.14 is-weakref: 1.1.0 math-intrinsics: 1.0.0 object-inspect: 1.13.3 @@ -16443,7 +16435,7 @@ snapshots: string.prototype.trimend: 1.0.9 string.prototype.trimstart: 1.0.8 typed-array-buffer: 1.0.2 - typed-array-byte-length: 1.0.1 + typed-array-byte-length: 1.0.3 typed-array-byte-offset: 1.0.3 typed-array-length: 1.0.7 unbox-primitive: 1.1.0 @@ -17365,7 +17357,7 @@ snapshots: get-intrinsic@1.2.6: dependencies: call-bind-apply-helpers: 1.0.1 - dunder-proto: 1.0.0 + dunder-proto: 1.0.1 es-define-property: 1.0.1 es-errors: 1.3.0 es-object-atoms: 1.0.0 @@ -17388,9 +17380,9 @@ snapshots: get-stream@8.0.1: {} - get-symbol-description@1.0.2: + get-symbol-description@1.1.0: dependencies: - call-bind: 1.0.8 + call-bound: 1.0.3 es-errors: 1.3.0 get-intrinsic: 1.2.6 @@ -17535,7 +17527,7 @@ snapshots: '@graphql-yoga/logger': 2.0.0 '@graphql-yoga/subscription': 5.0.2 '@whatwg-node/fetch': 0.10.1 - '@whatwg-node/server': 0.9.63 + '@whatwg-node/server': 0.9.64 dset: 3.1.4 graphql: 16.10.0 lru-cache: 10.4.3 @@ -17643,7 +17635,7 @@ snapshots: has-proto@1.2.0: dependencies: - dunder-proto: 1.0.0 + dunder-proto: 1.0.1 has-symbols@1.1.0: {} @@ -17978,9 +17970,10 @@ snapshots: is-alphabetical: 2.0.1 is-decimal: 2.0.1 - is-array-buffer@3.0.4: + is-array-buffer@3.0.5: dependencies: call-bind: 1.0.8 + call-bound: 1.0.3 get-intrinsic: 1.2.6 is-arrayish@0.2.1: {} @@ -18022,7 +18015,7 @@ snapshots: dependencies: call-bound: 1.0.3 get-intrinsic: 1.2.6 - is-typed-array: 1.1.13 + is-typed-array: 1.1.14 is-date-object@1.1.0: dependencies: @@ -18041,9 +18034,9 @@ snapshots: is-extglob@2.1.1: {} - is-finalizationregistry@1.1.0: + is-finalizationregistry@1.1.1: dependencies: - call-bind: 1.0.8 + call-bound: 1.0.3 is-fullwidth-code-point@3.0.0: {} @@ -18131,7 +18124,7 @@ snapshots: has-symbols: 1.1.0 safe-regex-test: 1.1.0 - is-typed-array@1.1.13: + is-typed-array@1.1.14: dependencies: which-typed-array: 1.1.16 @@ -18151,9 +18144,9 @@ snapshots: dependencies: call-bound: 1.0.3 - is-weakset@2.0.3: + is-weakset@2.0.4: dependencies: - call-bind: 1.0.8 + call-bound: 1.0.3 get-intrinsic: 1.2.6 is-windows@1.0.2: {} @@ -18201,7 +18194,7 @@ snapshots: rimraf: 2.7.1 ssim.js: 3.5.0 - jiti@1.21.6: {} + jiti@1.21.7: {} joycon@3.1.1: {} @@ -18314,7 +18307,7 @@ snapshots: object.assign: 4.1.5 object.values: 1.2.0 - katex@0.16.15: + katex@0.16.17: dependencies: commander: 8.3.0 @@ -18787,7 +18780,7 @@ snapshots: dayjs: 1.11.13 dompurify: 3.1.6 elkjs: 0.9.3 - katex: 0.16.15 + katex: 0.16.17 khroma: 2.1.0 lodash-es: 4.17.21 mdast-util-from-markdown: 1.3.1 @@ -18911,7 +18904,7 @@ snapshots: micromark-extension-math@2.1.2: dependencies: '@types/katex': 0.16.7 - katex: 0.16.15 + katex: 0.16.17 micromark-factory-space: 1.1.0 micromark-util-character: 1.2.0 micromark-util-symbol: 1.1.0 @@ -19333,7 +19326,7 @@ snapshots: mitt@3.0.1: {} - mixpanel-browser@2.56.0: + mixpanel-browser@2.57.1: dependencies: rrweb: 2.0.0-alpha.13 @@ -19512,7 +19505,7 @@ snapshots: github-slugger: 2.0.0 graceful-fs: 4.2.11 gray-matter: 4.0.3 - katex: 0.16.15 + katex: 0.16.17 lodash.get: 4.4.2 next: 14.2.20(@babel/core@7.26.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1) next-mdx-remote: 4.4.1(react-dom@18.3.1(react@18.3.1))(react@18.3.1) @@ -20027,11 +20020,11 @@ snapshots: postcss: 8.4.49 ts-node: 10.9.2(@types/node@22.10.2)(typescript@5.7.2) - postcss-load-config@6.0.1(jiti@1.21.6)(postcss@8.4.49)(tsx@4.19.2)(yaml@2.6.1): + postcss-load-config@6.0.1(jiti@1.21.7)(postcss@8.4.49)(tsx@4.19.2)(yaml@2.6.1): dependencies: lilconfig: 3.1.3 optionalDependencies: - jiti: 1.21.6 + jiti: 1.21.7 postcss: 8.4.49 tsx: 4.19.2 yaml: 2.6.1 @@ -20280,18 +20273,18 @@ snapshots: optionalDependencies: '@types/react': 18.3.17 - react-remove-scroll@2.6.0(@types/react@18.3.17)(react@18.3.1): + react-remove-scroll@2.6.2(@types/react@18.3.17)(react@18.3.1): dependencies: react: 18.3.1 react-remove-scroll-bar: 2.3.8(@types/react@18.3.17)(react@18.3.1) react-style-singleton: 2.2.3(@types/react@18.3.17)(react@18.3.1) tslib: 2.8.1 - use-callback-ref: 1.3.2(@types/react@18.3.17)(react@18.3.1) + use-callback-ref: 1.3.3(@types/react@18.3.17)(react@18.3.1) use-sidecar: 1.1.3(@types/react@18.3.17)(react@18.3.1) optionalDependencies: '@types/react': 18.3.17 - react-smooth@4.0.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1): + react-smooth@4.0.4(react-dom@18.3.1(react@18.3.1))(react@18.3.1): dependencies: fast-equals: 5.0.1 prop-types: 15.8.1 @@ -20394,7 +20387,7 @@ snapshots: react: 18.3.1 react-dom: 18.3.1(react@18.3.1) react-is: 18.3.1 - react-smooth: 4.0.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1) + react-smooth: 4.0.4(react-dom@18.3.1(react@18.3.1))(react@18.3.1) recharts-scale: 0.4.5 tiny-invariant: 1.3.3 victory-vendor: 36.9.2 @@ -20403,7 +20396,7 @@ snapshots: dependencies: call-bind: 1.0.8 define-properties: 1.2.1 - dunder-proto: 1.0.0 + dunder-proto: 1.0.1 es-abstract: 1.23.6 es-errors: 1.3.0 get-intrinsic: 1.2.6 @@ -20435,7 +20428,7 @@ snapshots: '@types/katex': 0.16.7 hast-util-from-html-isomorphic: 2.0.0 hast-util-to-text: 4.0.2 - katex: 0.16.15 + katex: 0.16.17 unist-util-visit-parents: 6.0.1 vfile: 6.0.3 @@ -21265,7 +21258,7 @@ snapshots: tabbable@6.2.0: {} - tailwindcss@3.4.16(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)): + tailwindcss@3.4.17(ts-node@10.9.2(@types/node@22.10.2)(typescript@5.7.2)): dependencies: '@alloc/quick-lru': 5.2.0 arg: 5.0.2 @@ -21275,7 +21268,7 @@ snapshots: fast-glob: 3.3.2 glob-parent: 6.0.2 is-glob: 4.0.3 - jiti: 1.21.6 + jiti: 1.21.7 lilconfig: 3.1.3 micromatch: 4.0.8 normalize-path: 3.0.0 @@ -21482,17 +21475,17 @@ snapshots: tsort@0.0.1: {} - tsup@8.3.5(jiti@1.21.6)(postcss@8.4.49)(tsx@4.19.2)(typescript@5.7.2)(yaml@2.6.1): + tsup@8.3.5(jiti@1.21.7)(postcss@8.4.49)(tsx@4.19.2)(typescript@5.7.2)(yaml@2.6.1): dependencies: bundle-require: 5.0.0(esbuild@0.24.0) cac: 6.7.14 - chokidar: 4.0.1 + chokidar: 4.0.2 consola: 3.2.3 debug: 4.4.0(supports-color@8.1.1) esbuild: 0.24.0 joycon: 3.1.1 picocolors: 1.1.1 - postcss-load-config: 6.0.1(jiti@1.21.6)(postcss@8.4.49)(tsx@4.19.2)(yaml@2.6.1) + postcss-load-config: 6.0.1(jiti@1.21.7)(postcss@8.4.49)(tsx@4.19.2)(yaml@2.6.1) resolve-from: 5.0.0 rollup: 4.28.1 source-map: 0.8.0-beta.0 @@ -21572,15 +21565,15 @@ snapshots: dependencies: call-bind: 1.0.8 es-errors: 1.3.0 - is-typed-array: 1.1.13 + is-typed-array: 1.1.14 - typed-array-byte-length@1.0.1: + typed-array-byte-length@1.0.3: dependencies: call-bind: 1.0.8 for-each: 0.3.3 gopd: 1.2.0 has-proto: 1.2.0 - is-typed-array: 1.1.13 + is-typed-array: 1.1.14 typed-array-byte-offset@1.0.3: dependencies: @@ -21589,7 +21582,7 @@ snapshots: for-each: 0.3.3 gopd: 1.2.0 has-proto: 1.2.0 - is-typed-array: 1.1.13 + is-typed-array: 1.1.14 reflect.getprototypeof: 1.0.8 typed-array-length@1.0.7: @@ -21597,7 +21590,7 @@ snapshots: call-bind: 1.0.8 for-each: 0.3.3 gopd: 1.2.0 - is-typed-array: 1.1.13 + is-typed-array: 1.1.14 possible-typed-array-names: 1.0.0 reflect.getprototypeof: 1.0.8 @@ -21635,9 +21628,10 @@ snapshots: dependencies: '@fastify/busboy': 2.1.1 - unenv-nightly@2.0.0-20241204-140205-a5d5190: + unenv-nightly@2.0.0-20241212-153011-af71c96: dependencies: defu: 6.1.4 + mlly: 1.7.3 ohash: 1.1.4 pathe: 1.1.2 ufo: 1.5.4 @@ -21845,7 +21839,7 @@ snapshots: urlpattern-polyfill@10.0.0: {} - use-callback-ref@1.3.2(@types/react@18.3.17)(react@18.3.1): + use-callback-ref@1.3.3(@types/react@18.3.17)(react@18.3.1): dependencies: react: 18.3.1 tslib: 2.8.1 @@ -22087,7 +22081,7 @@ snapshots: has-tostringtag: 1.0.2 is-async-function: 2.0.0 is-date-object: 1.1.0 - is-finalizationregistry: 1.1.0 + is-finalizationregistry: 1.1.1 is-generator-function: 1.0.10 is-regex: 1.2.1 is-weakref: 1.1.0 @@ -22101,7 +22095,7 @@ snapshots: is-map: 2.0.3 is-set: 2.0.3 is-weakmap: 2.0.2 - is-weakset: 2.0.3 + is-weakset: 2.0.4 which-module@2.0.1: {} @@ -22158,14 +22152,13 @@ snapshots: workerpool@6.5.1: {} - wrangler@3.95.0(@cloudflare/workers-types@4.20241216.0): + wrangler@3.97.0(@cloudflare/workers-types@4.20241218.0): dependencies: '@cloudflare/kv-asset-handler': 0.3.4 - '@cloudflare/workers-shared': 0.11.0 '@esbuild-plugins/node-globals-polyfill': 0.2.3(esbuild@0.17.19) '@esbuild-plugins/node-modules-polyfill': 0.2.2(esbuild@0.17.19) blake3-wasm: 2.1.5 - chokidar: 4.0.1 + chokidar: 4.0.2 date-fns: 4.1.0 esbuild: 0.17.19 itty-time: 1.0.6 @@ -22175,11 +22168,11 @@ snapshots: resolve: 1.22.9 selfsigned: 2.4.1 source-map: 0.6.1 - unenv: unenv-nightly@2.0.0-20241204-140205-a5d5190 + unenv: unenv-nightly@2.0.0-20241212-153011-af71c96 workerd: 1.20241205.0 xxhash-wasm: 1.1.0 optionalDependencies: - '@cloudflare/workers-types': 4.20241216.0 + '@cloudflare/workers-types': 4.20241218.0 fsevents: 2.3.3 transitivePeerDependencies: - bufferutil diff --git a/website/package.json b/website/package.json index c2233f1de1ef..59630cce5734 100644 --- a/website/package.json +++ b/website/package.json @@ -15,14 +15,14 @@ "typecheck": "tsc --noEmit" }, "dependencies": { - "@edgeandnode/common": "^6.38.0", - "@edgeandnode/gds": "^5.39.1", - "@edgeandnode/go": "^6.74.0", + "@edgeandnode/common": "^6.39.0", + "@edgeandnode/gds": "^5.39.2", + "@edgeandnode/go": "^6.75.0", "@emotion/react": "^11.14.0", "@graphprotocol/contracts": "6.2.1", "@graphprotocol/nextra-theme": "workspace:*", "@phosphor-icons/react": "^2.1.7", - "mixpanel-browser": "^2.56.0", + "mixpanel-browser": "^2.57.1", "next": "^14.2.20", "next-seo": "^6.6.0", "next-sitemap": "^4.2.3", @@ -43,7 +43,7 @@ "fast-xml-parser": "^4.5.1", "graphql": "^16.10.0", "postcss": "^8.4.49", - "tailwindcss": "^3.4.16", + "tailwindcss": "^3.4.17", "tsx": "^4.19.2", "unified": "^11.0.5" } From 51b2de2ae73d1c7d82a96cf8890e86224191ec87 Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 15:45:30 -0500 Subject: [PATCH 15/22] Tweaks --- packages/nextra-theme/src/index.tsx | 4 +- .../en/subgraphs/developing/introduction.mdx | 2 +- website/route-lockfile.txt | 230 +++++++++--------- 3 files changed, 119 insertions(+), 117 deletions(-) diff --git a/packages/nextra-theme/src/index.tsx b/packages/nextra-theme/src/index.tsx index 4872f4a79e1b..9866ecdfb480 100644 --- a/packages/nextra-theme/src/index.tsx +++ b/packages/nextra-theme/src/index.tsx @@ -199,7 +199,9 @@ export default function NextraLayout({ children, pageOpts, pageProps }: NextraTh {args.activePath.map((item) => item.title).join(' > ')} ) : null} - {frontMatter.title ? {frontMatter.title} : null} + {frontMatter.title || args.activeIndex === 0 ? ( + {args.activeIndex === 0 ? 'The Graph Docs' : frontMatter.title} + ) : null} {lastUpdated || readingTime ? ( {lastUpdated ? ( diff --git a/website/pages/en/subgraphs/developing/introduction.mdx b/website/pages/en/subgraphs/developing/introduction.mdx index 7b630ce3a607..c23d6c0918fd 100644 --- a/website/pages/en/subgraphs/developing/introduction.mdx +++ b/website/pages/en/subgraphs/developing/introduction.mdx @@ -1,5 +1,5 @@ --- -title: Introduction to Development +title: Introduction to Subgraph Development --- To start coding right away, go to [Developer Quick Start](/quick-start/). diff --git a/website/route-lockfile.txt b/website/route-lockfile.txt index 6461e6890411..c0990f2b0712 100644 --- a/website/route-lockfile.txt +++ b/website/route-lockfile.txt @@ -8,13 +8,13 @@ /ar/archived/sunrise/ /ar/contracts/ /ar/indexing/chain-integration-overview/ -/ar/indexing/introduction/ /ar/indexing/new-chain-integration/ +/ar/indexing/overview/ /ar/indexing/supported-network-requirements/ /ar/indexing/tap/ /ar/indexing/tooling/firehose/ +/ar/indexing/tooling/graph-node/ /ar/indexing/tooling/graphcast/ -/ar/indexing/tooling/operating-graph-node/ /ar/resources/benefits/ /ar/resources/glossary/ /ar/resources/release-notes/assemblyscript-migration-guide/ @@ -49,9 +49,9 @@ /ar/subgraphs/developing/creating/subgraph-manifest/ /ar/subgraphs/developing/creating/unit-testing-framework/ /ar/subgraphs/developing/deploying/multiple-networks/ -/ar/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ar/subgraphs/developing/deploying/subgraph-studio-faq/ /ar/subgraphs/developing/deploying/using-subgraph-studio/ -/ar/subgraphs/developing/developer-faqs/ +/ar/subgraphs/developing/developer-faq/ /ar/subgraphs/developing/introduction/ /ar/subgraphs/developing/managing/deleting-a-subgraph/ /ar/subgraphs/developing/managing/transferring-a-subgraph/ @@ -69,7 +69,7 @@ /ar/subgraphs/quick-start/ /ar/substreams/introduction/ /ar/substreams/sps/introduction/ -/ar/substreams/sps/substreams-powered-subgraphs-faq/ +/ar/substreams/sps/sps-faq/ /ar/substreams/sps/triggers-example/ /ar/substreams/sps/triggers/ /ar/supported-networks/ @@ -82,13 +82,13 @@ /cs/archived/sunrise/ /cs/contracts/ /cs/indexing/chain-integration-overview/ -/cs/indexing/introduction/ /cs/indexing/new-chain-integration/ +/cs/indexing/overview/ /cs/indexing/supported-network-requirements/ /cs/indexing/tap/ /cs/indexing/tooling/firehose/ +/cs/indexing/tooling/graph-node/ /cs/indexing/tooling/graphcast/ -/cs/indexing/tooling/operating-graph-node/ /cs/resources/benefits/ /cs/resources/glossary/ /cs/resources/release-notes/assemblyscript-migration-guide/ @@ -123,9 +123,9 @@ /cs/subgraphs/developing/creating/subgraph-manifest/ /cs/subgraphs/developing/creating/unit-testing-framework/ /cs/subgraphs/developing/deploying/multiple-networks/ -/cs/subgraphs/developing/deploying/subgraph-studio-faqs/ +/cs/subgraphs/developing/deploying/subgraph-studio-faq/ /cs/subgraphs/developing/deploying/using-subgraph-studio/ -/cs/subgraphs/developing/developer-faqs/ +/cs/subgraphs/developing/developer-faq/ /cs/subgraphs/developing/introduction/ /cs/subgraphs/developing/managing/deleting-a-subgraph/ /cs/subgraphs/developing/managing/transferring-a-subgraph/ @@ -143,7 +143,7 @@ /cs/subgraphs/quick-start/ /cs/substreams/introduction/ /cs/substreams/sps/introduction/ -/cs/substreams/sps/substreams-powered-subgraphs-faq/ +/cs/substreams/sps/sps-faq/ /cs/substreams/sps/triggers-example/ /cs/substreams/sps/triggers/ /cs/supported-networks/ @@ -154,13 +154,13 @@ /de/archived/sunrise/ /de/contracts/ /de/indexing/chain-integration-overview/ -/de/indexing/introduction/ /de/indexing/new-chain-integration/ +/de/indexing/overview/ /de/indexing/supported-network-requirements/ /de/indexing/tap/ /de/indexing/tooling/firehose/ +/de/indexing/tooling/graph-node/ /de/indexing/tooling/graphcast/ -/de/indexing/tooling/operating-graph-node/ /de/resources/benefits/ /de/resources/glossary/ /de/resources/release-notes/assemblyscript-migration-guide/ @@ -195,9 +195,9 @@ /de/subgraphs/developing/creating/subgraph-manifest/ /de/subgraphs/developing/creating/unit-testing-framework/ /de/subgraphs/developing/deploying/multiple-networks/ -/de/subgraphs/developing/deploying/subgraph-studio-faqs/ +/de/subgraphs/developing/deploying/subgraph-studio-faq/ /de/subgraphs/developing/deploying/using-subgraph-studio/ -/de/subgraphs/developing/developer-faqs/ +/de/subgraphs/developing/developer-faq/ /de/subgraphs/developing/introduction/ /de/subgraphs/developing/managing/deleting-a-subgraph/ /de/subgraphs/developing/managing/transferring-a-subgraph/ @@ -215,7 +215,7 @@ /de/subgraphs/quick-start/ /de/substreams/introduction/ /de/substreams/sps/introduction/ -/de/substreams/sps/substreams-powered-subgraphs-faq/ +/de/substreams/sps/sps-faq/ /de/substreams/sps/triggers-example/ /de/substreams/sps/triggers/ /de/supported-networks/ @@ -228,13 +228,13 @@ /en/archived/sunrise/ /en/contracts/ /en/indexing/chain-integration-overview/ -/en/indexing/introduction/ /en/indexing/new-chain-integration/ +/en/indexing/overview/ /en/indexing/supported-network-requirements/ /en/indexing/tap/ /en/indexing/tooling/firehose/ +/en/indexing/tooling/graph-node/ /en/indexing/tooling/graphcast/ -/en/indexing/tooling/operating-graph-node/ /en/resources/benefits/ /en/resources/glossary/ /en/resources/release-notes/assemblyscript-migration-guide/ @@ -271,9 +271,9 @@ /en/subgraphs/developing/creating/subgraph-manifest/ /en/subgraphs/developing/creating/unit-testing-framework/ /en/subgraphs/developing/deploying/multiple-networks/ -/en/subgraphs/developing/deploying/subgraph-studio-faqs/ +/en/subgraphs/developing/deploying/subgraph-studio-faq/ /en/subgraphs/developing/deploying/using-subgraph-studio/ -/en/subgraphs/developing/developer-faqs/ +/en/subgraphs/developing/developer-faq/ /en/subgraphs/developing/introduction/ /en/subgraphs/developing/managing/deleting-a-subgraph/ /en/subgraphs/developing/managing/transferring-a-subgraph/ @@ -294,7 +294,7 @@ /en/subgraphs/quick-start/ /en/substreams/introduction/ /en/substreams/sps/introduction/ -/en/substreams/sps/substreams-powered-subgraphs-faq/ +/en/substreams/sps/sps-faq/ /en/substreams/sps/triggers-example/ /en/substreams/sps/triggers/ /en/supported-networks/ @@ -307,13 +307,13 @@ /es/archived/sunrise/ /es/contracts/ /es/indexing/chain-integration-overview/ -/es/indexing/introduction/ /es/indexing/new-chain-integration/ +/es/indexing/overview/ /es/indexing/supported-network-requirements/ /es/indexing/tap/ /es/indexing/tooling/firehose/ +/es/indexing/tooling/graph-node/ /es/indexing/tooling/graphcast/ -/es/indexing/tooling/operating-graph-node/ /es/resources/benefits/ /es/resources/glossary/ /es/resources/release-notes/assemblyscript-migration-guide/ @@ -348,9 +348,9 @@ /es/subgraphs/developing/creating/subgraph-manifest/ /es/subgraphs/developing/creating/unit-testing-framework/ /es/subgraphs/developing/deploying/multiple-networks/ -/es/subgraphs/developing/deploying/subgraph-studio-faqs/ +/es/subgraphs/developing/deploying/subgraph-studio-faq/ /es/subgraphs/developing/deploying/using-subgraph-studio/ -/es/subgraphs/developing/developer-faqs/ +/es/subgraphs/developing/developer-faq/ /es/subgraphs/developing/introduction/ /es/subgraphs/developing/managing/deleting-a-subgraph/ /es/subgraphs/developing/managing/transferring-a-subgraph/ @@ -368,7 +368,7 @@ /es/subgraphs/quick-start/ /es/substreams/introduction/ /es/substreams/sps/introduction/ -/es/substreams/sps/substreams-powered-subgraphs-faq/ +/es/substreams/sps/sps-faq/ /es/substreams/sps/triggers-example/ /es/substreams/sps/triggers/ /es/supported-networks/ @@ -381,13 +381,13 @@ /fr/archived/sunrise/ /fr/contracts/ /fr/indexing/chain-integration-overview/ -/fr/indexing/introduction/ /fr/indexing/new-chain-integration/ +/fr/indexing/overview/ /fr/indexing/supported-network-requirements/ /fr/indexing/tap/ /fr/indexing/tooling/firehose/ +/fr/indexing/tooling/graph-node/ /fr/indexing/tooling/graphcast/ -/fr/indexing/tooling/operating-graph-node/ /fr/resources/benefits/ /fr/resources/glossary/ /fr/resources/release-notes/assemblyscript-migration-guide/ @@ -422,9 +422,9 @@ /fr/subgraphs/developing/creating/subgraph-manifest/ /fr/subgraphs/developing/creating/unit-testing-framework/ /fr/subgraphs/developing/deploying/multiple-networks/ -/fr/subgraphs/developing/deploying/subgraph-studio-faqs/ +/fr/subgraphs/developing/deploying/subgraph-studio-faq/ /fr/subgraphs/developing/deploying/using-subgraph-studio/ -/fr/subgraphs/developing/developer-faqs/ +/fr/subgraphs/developing/developer-faq/ /fr/subgraphs/developing/introduction/ /fr/subgraphs/developing/managing/deleting-a-subgraph/ /fr/subgraphs/developing/managing/transferring-a-subgraph/ @@ -442,7 +442,7 @@ /fr/subgraphs/quick-start/ /fr/substreams/introduction/ /fr/substreams/sps/introduction/ -/fr/substreams/sps/substreams-powered-subgraphs-faq/ +/fr/substreams/sps/sps-faq/ /fr/substreams/sps/triggers-example/ /fr/substreams/sps/triggers/ /fr/supported-networks/ @@ -455,13 +455,13 @@ /hi/archived/sunrise/ /hi/contracts/ /hi/indexing/chain-integration-overview/ -/hi/indexing/introduction/ /hi/indexing/new-chain-integration/ +/hi/indexing/overview/ /hi/indexing/supported-network-requirements/ /hi/indexing/tap/ /hi/indexing/tooling/firehose/ +/hi/indexing/tooling/graph-node/ /hi/indexing/tooling/graphcast/ -/hi/indexing/tooling/operating-graph-node/ /hi/resources/benefits/ /hi/resources/glossary/ /hi/resources/release-notes/assemblyscript-migration-guide/ @@ -496,9 +496,9 @@ /hi/subgraphs/developing/creating/subgraph-manifest/ /hi/subgraphs/developing/creating/unit-testing-framework/ /hi/subgraphs/developing/deploying/multiple-networks/ -/hi/subgraphs/developing/deploying/subgraph-studio-faqs/ +/hi/subgraphs/developing/deploying/subgraph-studio-faq/ /hi/subgraphs/developing/deploying/using-subgraph-studio/ -/hi/subgraphs/developing/developer-faqs/ +/hi/subgraphs/developing/developer-faq/ /hi/subgraphs/developing/introduction/ /hi/subgraphs/developing/managing/deleting-a-subgraph/ /hi/subgraphs/developing/managing/transferring-a-subgraph/ @@ -516,7 +516,7 @@ /hi/subgraphs/quick-start/ /hi/substreams/introduction/ /hi/substreams/sps/introduction/ -/hi/substreams/sps/substreams-powered-subgraphs-faq/ +/hi/substreams/sps/sps-faq/ /hi/substreams/sps/triggers-example/ /hi/substreams/sps/triggers/ /hi/supported-networks/ @@ -529,13 +529,13 @@ /it/archived/sunrise/ /it/contracts/ /it/indexing/chain-integration-overview/ -/it/indexing/introduction/ /it/indexing/new-chain-integration/ +/it/indexing/overview/ /it/indexing/supported-network-requirements/ /it/indexing/tap/ /it/indexing/tooling/firehose/ +/it/indexing/tooling/graph-node/ /it/indexing/tooling/graphcast/ -/it/indexing/tooling/operating-graph-node/ /it/resources/benefits/ /it/resources/glossary/ /it/resources/release-notes/assemblyscript-migration-guide/ @@ -570,9 +570,9 @@ /it/subgraphs/developing/creating/subgraph-manifest/ /it/subgraphs/developing/creating/unit-testing-framework/ /it/subgraphs/developing/deploying/multiple-networks/ -/it/subgraphs/developing/deploying/subgraph-studio-faqs/ +/it/subgraphs/developing/deploying/subgraph-studio-faq/ /it/subgraphs/developing/deploying/using-subgraph-studio/ -/it/subgraphs/developing/developer-faqs/ +/it/subgraphs/developing/developer-faq/ /it/subgraphs/developing/introduction/ /it/subgraphs/developing/managing/deleting-a-subgraph/ /it/subgraphs/developing/managing/transferring-a-subgraph/ @@ -590,7 +590,7 @@ /it/subgraphs/quick-start/ /it/substreams/introduction/ /it/substreams/sps/introduction/ -/it/substreams/sps/substreams-powered-subgraphs-faq/ +/it/substreams/sps/sps-faq/ /it/substreams/sps/triggers-example/ /it/substreams/sps/triggers/ /it/supported-networks/ @@ -603,13 +603,13 @@ /ja/archived/sunrise/ /ja/contracts/ /ja/indexing/chain-integration-overview/ -/ja/indexing/introduction/ /ja/indexing/new-chain-integration/ +/ja/indexing/overview/ /ja/indexing/supported-network-requirements/ /ja/indexing/tap/ /ja/indexing/tooling/firehose/ +/ja/indexing/tooling/graph-node/ /ja/indexing/tooling/graphcast/ -/ja/indexing/tooling/operating-graph-node/ /ja/resources/benefits/ /ja/resources/glossary/ /ja/resources/release-notes/assemblyscript-migration-guide/ @@ -644,9 +644,9 @@ /ja/subgraphs/developing/creating/subgraph-manifest/ /ja/subgraphs/developing/creating/unit-testing-framework/ /ja/subgraphs/developing/deploying/multiple-networks/ -/ja/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ja/subgraphs/developing/deploying/subgraph-studio-faq/ /ja/subgraphs/developing/deploying/using-subgraph-studio/ -/ja/subgraphs/developing/developer-faqs/ +/ja/subgraphs/developing/developer-faq/ /ja/subgraphs/developing/introduction/ /ja/subgraphs/developing/managing/deleting-a-subgraph/ /ja/subgraphs/developing/managing/transferring-a-subgraph/ @@ -664,7 +664,7 @@ /ja/subgraphs/quick-start/ /ja/substreams/introduction/ /ja/substreams/sps/introduction/ -/ja/substreams/sps/substreams-powered-subgraphs-faq/ +/ja/substreams/sps/sps-faq/ /ja/substreams/sps/triggers-example/ /ja/substreams/sps/triggers/ /ja/supported-networks/ @@ -675,13 +675,13 @@ /ko/archived/sunrise/ /ko/contracts/ /ko/indexing/chain-integration-overview/ -/ko/indexing/introduction/ /ko/indexing/new-chain-integration/ +/ko/indexing/overview/ /ko/indexing/supported-network-requirements/ /ko/indexing/tap/ /ko/indexing/tooling/firehose/ +/ko/indexing/tooling/graph-node/ /ko/indexing/tooling/graphcast/ -/ko/indexing/tooling/operating-graph-node/ /ko/resources/benefits/ /ko/resources/glossary/ /ko/resources/release-notes/assemblyscript-migration-guide/ @@ -716,9 +716,9 @@ /ko/subgraphs/developing/creating/subgraph-manifest/ /ko/subgraphs/developing/creating/unit-testing-framework/ /ko/subgraphs/developing/deploying/multiple-networks/ -/ko/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ko/subgraphs/developing/deploying/subgraph-studio-faq/ /ko/subgraphs/developing/deploying/using-subgraph-studio/ -/ko/subgraphs/developing/developer-faqs/ +/ko/subgraphs/developing/developer-faq/ /ko/subgraphs/developing/introduction/ /ko/subgraphs/developing/managing/deleting-a-subgraph/ /ko/subgraphs/developing/managing/transferring-a-subgraph/ @@ -736,7 +736,7 @@ /ko/subgraphs/quick-start/ /ko/substreams/introduction/ /ko/substreams/sps/introduction/ -/ko/substreams/sps/substreams-powered-subgraphs-faq/ +/ko/substreams/sps/sps-faq/ /ko/substreams/sps/triggers-example/ /ko/substreams/sps/triggers/ /ko/supported-networks/ @@ -749,13 +749,13 @@ /mr/archived/sunrise/ /mr/contracts/ /mr/indexing/chain-integration-overview/ -/mr/indexing/introduction/ /mr/indexing/new-chain-integration/ +/mr/indexing/overview/ /mr/indexing/supported-network-requirements/ /mr/indexing/tap/ /mr/indexing/tooling/firehose/ +/mr/indexing/tooling/graph-node/ /mr/indexing/tooling/graphcast/ -/mr/indexing/tooling/operating-graph-node/ /mr/resources/benefits/ /mr/resources/glossary/ /mr/resources/release-notes/assemblyscript-migration-guide/ @@ -790,9 +790,9 @@ /mr/subgraphs/developing/creating/subgraph-manifest/ /mr/subgraphs/developing/creating/unit-testing-framework/ /mr/subgraphs/developing/deploying/multiple-networks/ -/mr/subgraphs/developing/deploying/subgraph-studio-faqs/ +/mr/subgraphs/developing/deploying/subgraph-studio-faq/ /mr/subgraphs/developing/deploying/using-subgraph-studio/ -/mr/subgraphs/developing/developer-faqs/ +/mr/subgraphs/developing/developer-faq/ /mr/subgraphs/developing/introduction/ /mr/subgraphs/developing/managing/deleting-a-subgraph/ /mr/subgraphs/developing/managing/transferring-a-subgraph/ @@ -810,7 +810,7 @@ /mr/subgraphs/quick-start/ /mr/substreams/introduction/ /mr/substreams/sps/introduction/ -/mr/substreams/sps/substreams-powered-subgraphs-faq/ +/mr/substreams/sps/sps-faq/ /mr/substreams/sps/triggers-example/ /mr/substreams/sps/triggers/ /mr/supported-networks/ @@ -821,13 +821,13 @@ /nl/archived/sunrise/ /nl/contracts/ /nl/indexing/chain-integration-overview/ -/nl/indexing/introduction/ /nl/indexing/new-chain-integration/ +/nl/indexing/overview/ /nl/indexing/supported-network-requirements/ /nl/indexing/tap/ /nl/indexing/tooling/firehose/ +/nl/indexing/tooling/graph-node/ /nl/indexing/tooling/graphcast/ -/nl/indexing/tooling/operating-graph-node/ /nl/resources/benefits/ /nl/resources/glossary/ /nl/resources/release-notes/assemblyscript-migration-guide/ @@ -862,9 +862,9 @@ /nl/subgraphs/developing/creating/subgraph-manifest/ /nl/subgraphs/developing/creating/unit-testing-framework/ /nl/subgraphs/developing/deploying/multiple-networks/ -/nl/subgraphs/developing/deploying/subgraph-studio-faqs/ +/nl/subgraphs/developing/deploying/subgraph-studio-faq/ /nl/subgraphs/developing/deploying/using-subgraph-studio/ -/nl/subgraphs/developing/developer-faqs/ +/nl/subgraphs/developing/developer-faq/ /nl/subgraphs/developing/introduction/ /nl/subgraphs/developing/managing/deleting-a-subgraph/ /nl/subgraphs/developing/managing/transferring-a-subgraph/ @@ -882,7 +882,7 @@ /nl/subgraphs/quick-start/ /nl/substreams/introduction/ /nl/substreams/sps/introduction/ -/nl/substreams/sps/substreams-powered-subgraphs-faq/ +/nl/substreams/sps/sps-faq/ /nl/substreams/sps/triggers-example/ /nl/substreams/sps/triggers/ /nl/supported-networks/ @@ -893,13 +893,13 @@ /pl/archived/sunrise/ /pl/contracts/ /pl/indexing/chain-integration-overview/ -/pl/indexing/introduction/ /pl/indexing/new-chain-integration/ +/pl/indexing/overview/ /pl/indexing/supported-network-requirements/ /pl/indexing/tap/ /pl/indexing/tooling/firehose/ +/pl/indexing/tooling/graph-node/ /pl/indexing/tooling/graphcast/ -/pl/indexing/tooling/operating-graph-node/ /pl/resources/benefits/ /pl/resources/glossary/ /pl/resources/release-notes/assemblyscript-migration-guide/ @@ -934,9 +934,9 @@ /pl/subgraphs/developing/creating/subgraph-manifest/ /pl/subgraphs/developing/creating/unit-testing-framework/ /pl/subgraphs/developing/deploying/multiple-networks/ -/pl/subgraphs/developing/deploying/subgraph-studio-faqs/ +/pl/subgraphs/developing/deploying/subgraph-studio-faq/ /pl/subgraphs/developing/deploying/using-subgraph-studio/ -/pl/subgraphs/developing/developer-faqs/ +/pl/subgraphs/developing/developer-faq/ /pl/subgraphs/developing/introduction/ /pl/subgraphs/developing/managing/deleting-a-subgraph/ /pl/subgraphs/developing/managing/transferring-a-subgraph/ @@ -954,7 +954,7 @@ /pl/subgraphs/quick-start/ /pl/substreams/introduction/ /pl/substreams/sps/introduction/ -/pl/substreams/sps/substreams-powered-subgraphs-faq/ +/pl/substreams/sps/sps-faq/ /pl/substreams/sps/triggers-example/ /pl/substreams/sps/triggers/ /pl/supported-networks/ @@ -967,13 +967,13 @@ /pt/archived/sunrise/ /pt/contracts/ /pt/indexing/chain-integration-overview/ -/pt/indexing/introduction/ /pt/indexing/new-chain-integration/ +/pt/indexing/overview/ /pt/indexing/supported-network-requirements/ /pt/indexing/tap/ /pt/indexing/tooling/firehose/ +/pt/indexing/tooling/graph-node/ /pt/indexing/tooling/graphcast/ -/pt/indexing/tooling/operating-graph-node/ /pt/resources/benefits/ /pt/resources/glossary/ /pt/resources/release-notes/assemblyscript-migration-guide/ @@ -1008,9 +1008,9 @@ /pt/subgraphs/developing/creating/subgraph-manifest/ /pt/subgraphs/developing/creating/unit-testing-framework/ /pt/subgraphs/developing/deploying/multiple-networks/ -/pt/subgraphs/developing/deploying/subgraph-studio-faqs/ +/pt/subgraphs/developing/deploying/subgraph-studio-faq/ /pt/subgraphs/developing/deploying/using-subgraph-studio/ -/pt/subgraphs/developing/developer-faqs/ +/pt/subgraphs/developing/developer-faq/ /pt/subgraphs/developing/introduction/ /pt/subgraphs/developing/managing/deleting-a-subgraph/ /pt/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1028,7 +1028,7 @@ /pt/subgraphs/quick-start/ /pt/substreams/introduction/ /pt/substreams/sps/introduction/ -/pt/substreams/sps/substreams-powered-subgraphs-faq/ +/pt/substreams/sps/sps-faq/ /pt/substreams/sps/triggers-example/ /pt/substreams/sps/triggers/ /pt/supported-networks/ @@ -1039,13 +1039,13 @@ /ro/archived/sunrise/ /ro/contracts/ /ro/indexing/chain-integration-overview/ -/ro/indexing/introduction/ /ro/indexing/new-chain-integration/ +/ro/indexing/overview/ /ro/indexing/supported-network-requirements/ /ro/indexing/tap/ /ro/indexing/tooling/firehose/ +/ro/indexing/tooling/graph-node/ /ro/indexing/tooling/graphcast/ -/ro/indexing/tooling/operating-graph-node/ /ro/resources/benefits/ /ro/resources/glossary/ /ro/resources/release-notes/assemblyscript-migration-guide/ @@ -1080,9 +1080,9 @@ /ro/subgraphs/developing/creating/subgraph-manifest/ /ro/subgraphs/developing/creating/unit-testing-framework/ /ro/subgraphs/developing/deploying/multiple-networks/ -/ro/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ro/subgraphs/developing/deploying/subgraph-studio-faq/ /ro/subgraphs/developing/deploying/using-subgraph-studio/ -/ro/subgraphs/developing/developer-faqs/ +/ro/subgraphs/developing/developer-faq/ /ro/subgraphs/developing/introduction/ /ro/subgraphs/developing/managing/deleting-a-subgraph/ /ro/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1100,7 +1100,7 @@ /ro/subgraphs/quick-start/ /ro/substreams/introduction/ /ro/substreams/sps/introduction/ -/ro/substreams/sps/substreams-powered-subgraphs-faq/ +/ro/substreams/sps/sps-faq/ /ro/substreams/sps/triggers-example/ /ro/substreams/sps/triggers/ /ro/supported-networks/ @@ -1113,13 +1113,13 @@ /ru/archived/sunrise/ /ru/contracts/ /ru/indexing/chain-integration-overview/ -/ru/indexing/introduction/ /ru/indexing/new-chain-integration/ +/ru/indexing/overview/ /ru/indexing/supported-network-requirements/ /ru/indexing/tap/ /ru/indexing/tooling/firehose/ +/ru/indexing/tooling/graph-node/ /ru/indexing/tooling/graphcast/ -/ru/indexing/tooling/operating-graph-node/ /ru/resources/benefits/ /ru/resources/glossary/ /ru/resources/release-notes/assemblyscript-migration-guide/ @@ -1154,9 +1154,9 @@ /ru/subgraphs/developing/creating/subgraph-manifest/ /ru/subgraphs/developing/creating/unit-testing-framework/ /ru/subgraphs/developing/deploying/multiple-networks/ -/ru/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ru/subgraphs/developing/deploying/subgraph-studio-faq/ /ru/subgraphs/developing/deploying/using-subgraph-studio/ -/ru/subgraphs/developing/developer-faqs/ +/ru/subgraphs/developing/developer-faq/ /ru/subgraphs/developing/introduction/ /ru/subgraphs/developing/managing/deleting-a-subgraph/ /ru/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1174,7 +1174,7 @@ /ru/subgraphs/quick-start/ /ru/substreams/introduction/ /ru/substreams/sps/introduction/ -/ru/substreams/sps/substreams-powered-subgraphs-faq/ +/ru/substreams/sps/sps-faq/ /ru/substreams/sps/triggers-example/ /ru/substreams/sps/triggers/ /ru/supported-networks/ @@ -1187,13 +1187,13 @@ /sv/archived/sunrise/ /sv/contracts/ /sv/indexing/chain-integration-overview/ -/sv/indexing/introduction/ /sv/indexing/new-chain-integration/ +/sv/indexing/overview/ /sv/indexing/supported-network-requirements/ /sv/indexing/tap/ /sv/indexing/tooling/firehose/ +/sv/indexing/tooling/graph-node/ /sv/indexing/tooling/graphcast/ -/sv/indexing/tooling/operating-graph-node/ /sv/resources/benefits/ /sv/resources/glossary/ /sv/resources/release-notes/assemblyscript-migration-guide/ @@ -1228,9 +1228,9 @@ /sv/subgraphs/developing/creating/subgraph-manifest/ /sv/subgraphs/developing/creating/unit-testing-framework/ /sv/subgraphs/developing/deploying/multiple-networks/ -/sv/subgraphs/developing/deploying/subgraph-studio-faqs/ +/sv/subgraphs/developing/deploying/subgraph-studio-faq/ /sv/subgraphs/developing/deploying/using-subgraph-studio/ -/sv/subgraphs/developing/developer-faqs/ +/sv/subgraphs/developing/developer-faq/ /sv/subgraphs/developing/introduction/ /sv/subgraphs/developing/managing/deleting-a-subgraph/ /sv/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1248,7 +1248,7 @@ /sv/subgraphs/quick-start/ /sv/substreams/introduction/ /sv/substreams/sps/introduction/ -/sv/substreams/sps/substreams-powered-subgraphs-faq/ +/sv/substreams/sps/sps-faq/ /sv/substreams/sps/triggers-example/ /sv/substreams/sps/triggers/ /sv/supported-networks/ @@ -1259,13 +1259,13 @@ /sw/archived/sunrise/ /sw/contracts/ /sw/indexing/chain-integration-overview/ -/sw/indexing/introduction/ /sw/indexing/new-chain-integration/ +/sw/indexing/overview/ /sw/indexing/supported-network-requirements/ /sw/indexing/tap/ /sw/indexing/tooling/firehose/ +/sw/indexing/tooling/graph-node/ /sw/indexing/tooling/graphcast/ -/sw/indexing/tooling/operating-graph-node/ /sw/resources/benefits/ /sw/resources/glossary/ /sw/resources/release-notes/assemblyscript-migration-guide/ @@ -1300,9 +1300,9 @@ /sw/subgraphs/developing/creating/subgraph-manifest/ /sw/subgraphs/developing/creating/unit-testing-framework/ /sw/subgraphs/developing/deploying/multiple-networks/ -/sw/subgraphs/developing/deploying/subgraph-studio-faqs/ +/sw/subgraphs/developing/deploying/subgraph-studio-faq/ /sw/subgraphs/developing/deploying/using-subgraph-studio/ -/sw/subgraphs/developing/developer-faqs/ +/sw/subgraphs/developing/developer-faq/ /sw/subgraphs/developing/introduction/ /sw/subgraphs/developing/managing/deleting-a-subgraph/ /sw/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1320,7 +1320,7 @@ /sw/subgraphs/quick-start/ /sw/substreams/introduction/ /sw/substreams/sps/introduction/ -/sw/substreams/sps/substreams-powered-subgraphs-faq/ +/sw/substreams/sps/sps-faq/ /sw/substreams/sps/triggers-example/ /sw/substreams/sps/triggers/ /sw/supported-networks/ @@ -1333,13 +1333,13 @@ /tr/archived/sunrise/ /tr/contracts/ /tr/indexing/chain-integration-overview/ -/tr/indexing/introduction/ /tr/indexing/new-chain-integration/ +/tr/indexing/overview/ /tr/indexing/supported-network-requirements/ /tr/indexing/tap/ /tr/indexing/tooling/firehose/ +/tr/indexing/tooling/graph-node/ /tr/indexing/tooling/graphcast/ -/tr/indexing/tooling/operating-graph-node/ /tr/resources/benefits/ /tr/resources/glossary/ /tr/resources/release-notes/assemblyscript-migration-guide/ @@ -1374,9 +1374,9 @@ /tr/subgraphs/developing/creating/subgraph-manifest/ /tr/subgraphs/developing/creating/unit-testing-framework/ /tr/subgraphs/developing/deploying/multiple-networks/ -/tr/subgraphs/developing/deploying/subgraph-studio-faqs/ +/tr/subgraphs/developing/deploying/subgraph-studio-faq/ /tr/subgraphs/developing/deploying/using-subgraph-studio/ -/tr/subgraphs/developing/developer-faqs/ +/tr/subgraphs/developing/developer-faq/ /tr/subgraphs/developing/introduction/ /tr/subgraphs/developing/managing/deleting-a-subgraph/ /tr/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1394,7 +1394,7 @@ /tr/subgraphs/quick-start/ /tr/substreams/introduction/ /tr/substreams/sps/introduction/ -/tr/substreams/sps/substreams-powered-subgraphs-faq/ +/tr/substreams/sps/sps-faq/ /tr/substreams/sps/triggers-example/ /tr/substreams/sps/triggers/ /tr/supported-networks/ @@ -1405,13 +1405,13 @@ /uk/archived/sunrise/ /uk/contracts/ /uk/indexing/chain-integration-overview/ -/uk/indexing/introduction/ /uk/indexing/new-chain-integration/ +/uk/indexing/overview/ /uk/indexing/supported-network-requirements/ /uk/indexing/tap/ /uk/indexing/tooling/firehose/ +/uk/indexing/tooling/graph-node/ /uk/indexing/tooling/graphcast/ -/uk/indexing/tooling/operating-graph-node/ /uk/resources/benefits/ /uk/resources/glossary/ /uk/resources/release-notes/assemblyscript-migration-guide/ @@ -1446,9 +1446,9 @@ /uk/subgraphs/developing/creating/subgraph-manifest/ /uk/subgraphs/developing/creating/unit-testing-framework/ /uk/subgraphs/developing/deploying/multiple-networks/ -/uk/subgraphs/developing/deploying/subgraph-studio-faqs/ +/uk/subgraphs/developing/deploying/subgraph-studio-faq/ /uk/subgraphs/developing/deploying/using-subgraph-studio/ -/uk/subgraphs/developing/developer-faqs/ +/uk/subgraphs/developing/developer-faq/ /uk/subgraphs/developing/introduction/ /uk/subgraphs/developing/managing/deleting-a-subgraph/ /uk/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1466,7 +1466,7 @@ /uk/subgraphs/quick-start/ /uk/substreams/introduction/ /uk/substreams/sps/introduction/ -/uk/substreams/sps/substreams-powered-subgraphs-faq/ +/uk/substreams/sps/sps-faq/ /uk/substreams/sps/triggers-example/ /uk/substreams/sps/triggers/ /uk/supported-networks/ @@ -1479,13 +1479,13 @@ /ur/archived/sunrise/ /ur/contracts/ /ur/indexing/chain-integration-overview/ -/ur/indexing/introduction/ /ur/indexing/new-chain-integration/ +/ur/indexing/overview/ /ur/indexing/supported-network-requirements/ /ur/indexing/tap/ /ur/indexing/tooling/firehose/ +/ur/indexing/tooling/graph-node/ /ur/indexing/tooling/graphcast/ -/ur/indexing/tooling/operating-graph-node/ /ur/resources/benefits/ /ur/resources/glossary/ /ur/resources/release-notes/assemblyscript-migration-guide/ @@ -1520,9 +1520,9 @@ /ur/subgraphs/developing/creating/subgraph-manifest/ /ur/subgraphs/developing/creating/unit-testing-framework/ /ur/subgraphs/developing/deploying/multiple-networks/ -/ur/subgraphs/developing/deploying/subgraph-studio-faqs/ +/ur/subgraphs/developing/deploying/subgraph-studio-faq/ /ur/subgraphs/developing/deploying/using-subgraph-studio/ -/ur/subgraphs/developing/developer-faqs/ +/ur/subgraphs/developing/developer-faq/ /ur/subgraphs/developing/introduction/ /ur/subgraphs/developing/managing/deleting-a-subgraph/ /ur/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1540,7 +1540,7 @@ /ur/subgraphs/quick-start/ /ur/substreams/introduction/ /ur/substreams/sps/introduction/ -/ur/substreams/sps/substreams-powered-subgraphs-faq/ +/ur/substreams/sps/sps-faq/ /ur/substreams/sps/triggers-example/ /ur/substreams/sps/triggers/ /ur/supported-networks/ @@ -1551,13 +1551,13 @@ /vi/archived/sunrise/ /vi/contracts/ /vi/indexing/chain-integration-overview/ -/vi/indexing/introduction/ /vi/indexing/new-chain-integration/ +/vi/indexing/overview/ /vi/indexing/supported-network-requirements/ /vi/indexing/tap/ /vi/indexing/tooling/firehose/ +/vi/indexing/tooling/graph-node/ /vi/indexing/tooling/graphcast/ -/vi/indexing/tooling/operating-graph-node/ /vi/resources/benefits/ /vi/resources/glossary/ /vi/resources/release-notes/assemblyscript-migration-guide/ @@ -1592,9 +1592,9 @@ /vi/subgraphs/developing/creating/subgraph-manifest/ /vi/subgraphs/developing/creating/unit-testing-framework/ /vi/subgraphs/developing/deploying/multiple-networks/ -/vi/subgraphs/developing/deploying/subgraph-studio-faqs/ +/vi/subgraphs/developing/deploying/subgraph-studio-faq/ /vi/subgraphs/developing/deploying/using-subgraph-studio/ -/vi/subgraphs/developing/developer-faqs/ +/vi/subgraphs/developing/developer-faq/ /vi/subgraphs/developing/introduction/ /vi/subgraphs/developing/managing/deleting-a-subgraph/ /vi/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1612,7 +1612,7 @@ /vi/subgraphs/quick-start/ /vi/substreams/introduction/ /vi/substreams/sps/introduction/ -/vi/substreams/sps/substreams-powered-subgraphs-faq/ +/vi/substreams/sps/sps-faq/ /vi/substreams/sps/triggers-example/ /vi/substreams/sps/triggers/ /vi/supported-networks/ @@ -1625,13 +1625,13 @@ /zh/archived/sunrise/ /zh/contracts/ /zh/indexing/chain-integration-overview/ -/zh/indexing/introduction/ /zh/indexing/new-chain-integration/ +/zh/indexing/overview/ /zh/indexing/supported-network-requirements/ /zh/indexing/tap/ /zh/indexing/tooling/firehose/ +/zh/indexing/tooling/graph-node/ /zh/indexing/tooling/graphcast/ -/zh/indexing/tooling/operating-graph-node/ /zh/resources/benefits/ /zh/resources/glossary/ /zh/resources/release-notes/assemblyscript-migration-guide/ @@ -1666,9 +1666,9 @@ /zh/subgraphs/developing/creating/subgraph-manifest/ /zh/subgraphs/developing/creating/unit-testing-framework/ /zh/subgraphs/developing/deploying/multiple-networks/ -/zh/subgraphs/developing/deploying/subgraph-studio-faqs/ +/zh/subgraphs/developing/deploying/subgraph-studio-faq/ /zh/subgraphs/developing/deploying/using-subgraph-studio/ -/zh/subgraphs/developing/developer-faqs/ +/zh/subgraphs/developing/developer-faq/ /zh/subgraphs/developing/introduction/ /zh/subgraphs/developing/managing/deleting-a-subgraph/ /zh/subgraphs/developing/managing/transferring-a-subgraph/ @@ -1686,7 +1686,7 @@ /zh/subgraphs/quick-start/ /zh/substreams/introduction/ /zh/substreams/sps/introduction/ -/zh/substreams/sps/substreams-powered-subgraphs-faq/ +/zh/substreams/sps/sps-faq/ /zh/substreams/sps/triggers-example/ /zh/substreams/sps/triggers/ /zh/supported-networks/ From 676f283b134a40897db4f168b6f1d4dace266ffd Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 17:02:37 -0500 Subject: [PATCH 16/22] One more page rename --- ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 website/pages/en/subgraphs/cookbook/_meta.js | 1 + ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 ...g-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} | 0 24 files changed, 1 insertion(+) rename website/pages/ar/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/cs/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/de/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/en/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/es/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/fr/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/hi/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/it/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/ja/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/ko/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/mr/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/nl/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/pl/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/pt/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/ro/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/ru/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/sv/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/sw/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/tr/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/uk/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/ur/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/vi/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) rename website/pages/zh/subgraphs/cookbook/{how-to-secure-api-keys-using-nextjs-server-components.mdx => secure-api-keys-nextjs.mdx} (100%) diff --git a/website/pages/ar/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ar/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/ar/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ar/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/cs/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/cs/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/cs/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/cs/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/de/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/de/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/de/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/de/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/en/subgraphs/cookbook/_meta.js b/website/pages/en/subgraphs/cookbook/_meta.js index 87b6b11ebd1c..f2f275dbd8af 100644 --- a/website/pages/en/subgraphs/cookbook/_meta.js +++ b/website/pages/en/subgraphs/cookbook/_meta.js @@ -14,4 +14,5 @@ export default { timeseries: 'Subgraph Best Practice 5: Simplify and Optimize with Timeseries and Aggregations', 'grafting-hotfix': 'Subgraph Best Practice 6: Grafting and Hotfixing', enums: '', + 'secure-api-keys-nextjs': '', } diff --git a/website/pages/en/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/en/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/en/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/en/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/es/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/es/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/es/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/es/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/fr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/fr/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/fr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/fr/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/hi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/hi/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/hi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/hi/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/it/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/it/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/it/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/it/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/ja/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ja/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/ja/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ja/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/ko/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ko/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/ko/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ko/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/mr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/mr/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/mr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/mr/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/nl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/nl/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/nl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/nl/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/pl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/pl/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/pl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/pl/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/pt/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/pt/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/pt/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/pt/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/ro/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ro/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/ro/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ro/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/ru/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ru/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/ru/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ru/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/sv/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/sv/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/sv/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/sv/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/sw/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/sw/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/sw/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/sw/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/tr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/tr/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/tr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/tr/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/uk/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/uk/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/uk/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/uk/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/ur/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/ur/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/ur/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/ur/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/vi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/vi/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/vi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/vi/subgraphs/cookbook/secure-api-keys-nextjs.mdx diff --git a/website/pages/zh/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/zh/subgraphs/cookbook/secure-api-keys-nextjs.mdx similarity index 100% rename from website/pages/zh/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx rename to website/pages/zh/subgraphs/cookbook/secure-api-keys-nextjs.mdx From 3d74a0a9d351c3ff4c913eba6f6f0e1a9dfdb565 Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 17:18:04 -0500 Subject: [PATCH 17/22] One more --- .../pages/ar/substreams/sps/introduction.mdx | 2 +- website/pages/ar/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/cs/substreams/sps/introduction.mdx | 2 +- website/pages/cs/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/de/substreams/sps/introduction.mdx | 2 +- website/pages/de/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 website/pages/en/substreams/sps/_meta.js | 2 +- .../pages/en/substreams/sps/introduction.mdx | 2 +- website/pages/en/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/es/substreams/sps/introduction.mdx | 2 +- website/pages/es/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/fr/substreams/sps/introduction.mdx | 2 +- website/pages/fr/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/hi/substreams/sps/introduction.mdx | 2 +- website/pages/hi/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/it/substreams/sps/introduction.mdx | 2 +- website/pages/it/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/ja/substreams/sps/introduction.mdx | 2 +- website/pages/ja/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/ko/substreams/sps/introduction.mdx | 2 +- website/pages/ko/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/mr/substreams/sps/introduction.mdx | 2 +- website/pages/mr/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/nl/substreams/sps/introduction.mdx | 2 +- website/pages/nl/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/pl/substreams/sps/introduction.mdx | 2 +- website/pages/pl/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/pt/substreams/sps/introduction.mdx | 2 +- website/pages/pt/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/ro/substreams/sps/introduction.mdx | 2 +- website/pages/ro/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/ru/substreams/sps/introduction.mdx | 2 +- website/pages/ru/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/sv/substreams/sps/introduction.mdx | 2 +- website/pages/sv/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/sw/substreams/sps/introduction.mdx | 2 +- website/pages/sw/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/tr/substreams/sps/introduction.mdx | 2 +- website/pages/tr/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/uk/substreams/sps/introduction.mdx | 2 +- website/pages/uk/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/ur/substreams/sps/introduction.mdx | 2 +- website/pages/ur/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/vi/substreams/sps/introduction.mdx | 2 +- website/pages/vi/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 .../pages/zh/substreams/sps/introduction.mdx | 2 +- website/pages/zh/substreams/sps/triggers.mdx | 4 +- .../{triggers-example.mdx => tutorial.mdx} | 0 website/route-lockfile.txt | 92 +++++++++---------- 71 files changed, 116 insertions(+), 116 deletions(-) rename website/pages/ar/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/cs/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/de/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/en/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/es/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/fr/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/hi/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/it/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/ja/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/ko/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/mr/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/nl/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/pl/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/pt/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/ro/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/ru/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/sv/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/sw/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/tr/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/uk/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/ur/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/vi/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) rename website/pages/zh/substreams/sps/{triggers-example.mdx => tutorial.mdx} (100%) diff --git a/website/pages/ar/substreams/sps/introduction.mdx b/website/pages/ar/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/ar/substreams/sps/introduction.mdx +++ b/website/pages/ar/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ar/substreams/sps/triggers.mdx b/website/pages/ar/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/ar/substreams/sps/triggers.mdx +++ b/website/pages/ar/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/ar/substreams/sps/triggers-example.mdx b/website/pages/ar/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/ar/substreams/sps/triggers-example.mdx rename to website/pages/ar/substreams/sps/tutorial.mdx diff --git a/website/pages/cs/substreams/sps/introduction.mdx b/website/pages/cs/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/cs/substreams/sps/introduction.mdx +++ b/website/pages/cs/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/cs/substreams/sps/triggers.mdx b/website/pages/cs/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/cs/substreams/sps/triggers.mdx +++ b/website/pages/cs/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/cs/substreams/sps/triggers-example.mdx b/website/pages/cs/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/cs/substreams/sps/triggers-example.mdx rename to website/pages/cs/substreams/sps/tutorial.mdx diff --git a/website/pages/de/substreams/sps/introduction.mdx b/website/pages/de/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/de/substreams/sps/introduction.mdx +++ b/website/pages/de/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/de/substreams/sps/triggers.mdx b/website/pages/de/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/de/substreams/sps/triggers.mdx +++ b/website/pages/de/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/de/substreams/sps/triggers-example.mdx b/website/pages/de/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/de/substreams/sps/triggers-example.mdx rename to website/pages/de/substreams/sps/tutorial.mdx diff --git a/website/pages/en/substreams/sps/_meta.js b/website/pages/en/substreams/sps/_meta.js index 5f93de2d56e3..47a55bd2c2b7 100644 --- a/website/pages/en/substreams/sps/_meta.js +++ b/website/pages/en/substreams/sps/_meta.js @@ -1,6 +1,6 @@ export default { introduction: 'Introduction', triggers: '', - 'triggers-example': 'Tutorial', + tutorial: 'Tutorial', 'sps-faq': 'FAQ', } diff --git a/website/pages/en/substreams/sps/introduction.mdx b/website/pages/en/substreams/sps/introduction.mdx index 2a4de802eaf1..27afab0946c2 100644 --- a/website/pages/en/substreams/sps/introduction.mdx +++ b/website/pages/en/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/en/substreams/sps/triggers.mdx b/website/pages/en/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/en/substreams/sps/triggers.mdx +++ b/website/pages/en/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/en/substreams/sps/triggers-example.mdx b/website/pages/en/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/en/substreams/sps/triggers-example.mdx rename to website/pages/en/substreams/sps/tutorial.mdx diff --git a/website/pages/es/substreams/sps/introduction.mdx b/website/pages/es/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/es/substreams/sps/introduction.mdx +++ b/website/pages/es/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/es/substreams/sps/triggers.mdx b/website/pages/es/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/es/substreams/sps/triggers.mdx +++ b/website/pages/es/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/es/substreams/sps/triggers-example.mdx b/website/pages/es/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/es/substreams/sps/triggers-example.mdx rename to website/pages/es/substreams/sps/tutorial.mdx diff --git a/website/pages/fr/substreams/sps/introduction.mdx b/website/pages/fr/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/fr/substreams/sps/introduction.mdx +++ b/website/pages/fr/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/fr/substreams/sps/triggers.mdx b/website/pages/fr/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/fr/substreams/sps/triggers.mdx +++ b/website/pages/fr/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/fr/substreams/sps/triggers-example.mdx b/website/pages/fr/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/fr/substreams/sps/triggers-example.mdx rename to website/pages/fr/substreams/sps/tutorial.mdx diff --git a/website/pages/hi/substreams/sps/introduction.mdx b/website/pages/hi/substreams/sps/introduction.mdx index d2e1f0179d40..3e7e817db516 100644 --- a/website/pages/hi/substreams/sps/introduction.mdx +++ b/website/pages/hi/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ Substreams पैकेज (.spkg) का उपयोग करके, आप इस तकनीक को सक्षम करने के दो तरीके हैं: -Using Substreams triggers(./triggers): किसी भी Substreams मॉड्यूल से उपभोग करें, Protobuf मॉडल को एक subgraph हैंडलर के माध्यम से आयात करके और सभी लॉजिक को एक subgraph में स्थानांतरित करें। यह विधि subgraph संस्थाओं को सीधे subgraph में बनाती है। +Using Substreams triggers(/substreams/sps/triggers): किसी भी Substreams मॉड्यूल से उपभोग करें, Protobuf मॉडल को एक subgraph हैंडलर के माध्यम से आयात करके और सभी लॉजिक को एक subgraph में स्थानांतरित करें। यह विधि subgraph संस्थाओं को सीधे subgraph में बनाती है। Entity Changes (https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out) का उपयोग करके: Substreams में अधिक लॉजिक लिखने से, आप सीधे graph-node में मॉड्यूल का आउटपुट प्राप्त कर सकते हैं। graph-node में, आप Substreams डेटा का उपयोग करके अपने उपग्रह संस्थाएं बना सकते हैं। diff --git a/website/pages/hi/substreams/sps/triggers.mdx b/website/pages/hi/substreams/sps/triggers.mdx index 2d5a8db77b60..4de0022baf7c 100644 --- a/website/pages/hi/substreams/sps/triggers.mdx +++ b/website/pages/hi/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: सबस्ट्रीम्स ट्रिगर्स कस्टम ट्रिगर्स आपको अपने subgraph मैपिंग फ़ाइल और इकाइयों (टेबल और फ़ील्ड के समान) में डेटा सीधे भेजने की अनुमति देते हैं, जो GraphQL परत का पूरा उपयोग करने में सक्षम बनाते हैं। अपने Substreams मॉड्यूल द्वारा उत्पन्न Protobuf परिभाषाओं को आयात करके, आप अपने subgraph के हैंडलर के भीतर इस डेटा को प्राप्त और प्रोसेस कर सकते हैं, जो subgraph ढांचे के भीतर कुशल और सुव्यवस्थित डेटा प्रबंधन सुनिश्चित करता है। -> नोट: यदि आपने पहले से ऐसा नहीं किया है, तो अपने पहले प्रोजेक्ट को Development Container में स्कैफोल्ड करने के लिए यहाँ (./introduction) पाए जाने वाले How-To Guides में से एक पर जाएं। +> नोट: यदि आपने पहले से ऐसा नहीं किया है, तो अपने पहले प्रोजेक्ट को Development Container में स्कैफोल्ड करने के लिए यहाँ (/substreams/sps/introduction) पाए जाने वाले How-To Guides में से एक पर जाएं। निम्नलिखित कोड यह दर्शाता है कि कैसे एक handleTransactions फ़ंक्शन को एक subgraph हैंडलर में परिभाषित किया जा सकता है। यह फ़ंक्शन कच्चे Substreams बाइट्स को एक पैरामीटर के रूप में प्राप्त करता है और उन्हें एक Transactions ऑब्जेक्ट में डिकोड करता है। प्रत्येक लेनदेन के लिए, एक नई subgraph एंटिटी बनाई जाती है। @@ -34,4 +34,4 @@ export function handleTransactions(bytes: Uint8Array): void { 2. लेनदेन पर लूप करना 3. प्रत्येक लेनदेन के लिए एक नया subgraph entity बनाएं -ड्रैगर-आधारित एक उपग्राफ के विस्तृत उदाहरण के लिए, यहां क्लिक करें(./triggers-example). +ड्रैगर-आधारित एक उपग्राफ के विस्तृत उदाहरण के लिए, यहां क्लिक करें(/substreams/sps/tutorial). diff --git a/website/pages/hi/substreams/sps/triggers-example.mdx b/website/pages/hi/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/hi/substreams/sps/triggers-example.mdx rename to website/pages/hi/substreams/sps/tutorial.mdx diff --git a/website/pages/it/substreams/sps/introduction.mdx b/website/pages/it/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/it/substreams/sps/introduction.mdx +++ b/website/pages/it/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/it/substreams/sps/triggers.mdx b/website/pages/it/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/it/substreams/sps/triggers.mdx +++ b/website/pages/it/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/it/substreams/sps/triggers-example.mdx b/website/pages/it/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/it/substreams/sps/triggers-example.mdx rename to website/pages/it/substreams/sps/tutorial.mdx diff --git a/website/pages/ja/substreams/sps/introduction.mdx b/website/pages/ja/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/ja/substreams/sps/introduction.mdx +++ b/website/pages/ja/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ja/substreams/sps/triggers.mdx b/website/pages/ja/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/ja/substreams/sps/triggers.mdx +++ b/website/pages/ja/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/ja/substreams/sps/triggers-example.mdx b/website/pages/ja/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/ja/substreams/sps/triggers-example.mdx rename to website/pages/ja/substreams/sps/tutorial.mdx diff --git a/website/pages/ko/substreams/sps/introduction.mdx b/website/pages/ko/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/ko/substreams/sps/introduction.mdx +++ b/website/pages/ko/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ko/substreams/sps/triggers.mdx b/website/pages/ko/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/ko/substreams/sps/triggers.mdx +++ b/website/pages/ko/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/ko/substreams/sps/triggers-example.mdx b/website/pages/ko/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/ko/substreams/sps/triggers-example.mdx rename to website/pages/ko/substreams/sps/tutorial.mdx diff --git a/website/pages/mr/substreams/sps/introduction.mdx b/website/pages/mr/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/mr/substreams/sps/introduction.mdx +++ b/website/pages/mr/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/mr/substreams/sps/triggers.mdx b/website/pages/mr/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/mr/substreams/sps/triggers.mdx +++ b/website/pages/mr/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/mr/substreams/sps/triggers-example.mdx b/website/pages/mr/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/mr/substreams/sps/triggers-example.mdx rename to website/pages/mr/substreams/sps/tutorial.mdx diff --git a/website/pages/nl/substreams/sps/introduction.mdx b/website/pages/nl/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/nl/substreams/sps/introduction.mdx +++ b/website/pages/nl/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/nl/substreams/sps/triggers.mdx b/website/pages/nl/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/nl/substreams/sps/triggers.mdx +++ b/website/pages/nl/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/nl/substreams/sps/triggers-example.mdx b/website/pages/nl/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/nl/substreams/sps/triggers-example.mdx rename to website/pages/nl/substreams/sps/tutorial.mdx diff --git a/website/pages/pl/substreams/sps/introduction.mdx b/website/pages/pl/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/pl/substreams/sps/introduction.mdx +++ b/website/pages/pl/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/pl/substreams/sps/triggers.mdx b/website/pages/pl/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/pl/substreams/sps/triggers.mdx +++ b/website/pages/pl/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/pl/substreams/sps/triggers-example.mdx b/website/pages/pl/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/pl/substreams/sps/triggers-example.mdx rename to website/pages/pl/substreams/sps/tutorial.mdx diff --git a/website/pages/pt/substreams/sps/introduction.mdx b/website/pages/pt/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/pt/substreams/sps/introduction.mdx +++ b/website/pages/pt/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/pt/substreams/sps/triggers.mdx b/website/pages/pt/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/pt/substreams/sps/triggers.mdx +++ b/website/pages/pt/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/pt/substreams/sps/triggers-example.mdx b/website/pages/pt/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/pt/substreams/sps/triggers-example.mdx rename to website/pages/pt/substreams/sps/tutorial.mdx diff --git a/website/pages/ro/substreams/sps/introduction.mdx b/website/pages/ro/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/ro/substreams/sps/introduction.mdx +++ b/website/pages/ro/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ro/substreams/sps/triggers.mdx b/website/pages/ro/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/ro/substreams/sps/triggers.mdx +++ b/website/pages/ro/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/ro/substreams/sps/triggers-example.mdx b/website/pages/ro/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/ro/substreams/sps/triggers-example.mdx rename to website/pages/ro/substreams/sps/tutorial.mdx diff --git a/website/pages/ru/substreams/sps/introduction.mdx b/website/pages/ru/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/ru/substreams/sps/introduction.mdx +++ b/website/pages/ru/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ru/substreams/sps/triggers.mdx b/website/pages/ru/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/ru/substreams/sps/triggers.mdx +++ b/website/pages/ru/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/ru/substreams/sps/triggers-example.mdx b/website/pages/ru/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/ru/substreams/sps/triggers-example.mdx rename to website/pages/ru/substreams/sps/tutorial.mdx diff --git a/website/pages/sv/substreams/sps/introduction.mdx b/website/pages/sv/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/sv/substreams/sps/introduction.mdx +++ b/website/pages/sv/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/sv/substreams/sps/triggers.mdx b/website/pages/sv/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/sv/substreams/sps/triggers.mdx +++ b/website/pages/sv/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/sv/substreams/sps/triggers-example.mdx b/website/pages/sv/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/sv/substreams/sps/triggers-example.mdx rename to website/pages/sv/substreams/sps/tutorial.mdx diff --git a/website/pages/sw/substreams/sps/introduction.mdx b/website/pages/sw/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/sw/substreams/sps/introduction.mdx +++ b/website/pages/sw/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/sw/substreams/sps/triggers.mdx b/website/pages/sw/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/sw/substreams/sps/triggers.mdx +++ b/website/pages/sw/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/sw/substreams/sps/triggers-example.mdx b/website/pages/sw/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/sw/substreams/sps/triggers-example.mdx rename to website/pages/sw/substreams/sps/tutorial.mdx diff --git a/website/pages/tr/substreams/sps/introduction.mdx b/website/pages/tr/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/tr/substreams/sps/introduction.mdx +++ b/website/pages/tr/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/tr/substreams/sps/triggers.mdx b/website/pages/tr/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/tr/substreams/sps/triggers.mdx +++ b/website/pages/tr/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/tr/substreams/sps/triggers-example.mdx b/website/pages/tr/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/tr/substreams/sps/triggers-example.mdx rename to website/pages/tr/substreams/sps/tutorial.mdx diff --git a/website/pages/uk/substreams/sps/introduction.mdx b/website/pages/uk/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/uk/substreams/sps/introduction.mdx +++ b/website/pages/uk/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/uk/substreams/sps/triggers.mdx b/website/pages/uk/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/uk/substreams/sps/triggers.mdx +++ b/website/pages/uk/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/uk/substreams/sps/triggers-example.mdx b/website/pages/uk/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/uk/substreams/sps/triggers-example.mdx rename to website/pages/uk/substreams/sps/tutorial.mdx diff --git a/website/pages/ur/substreams/sps/introduction.mdx b/website/pages/ur/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/ur/substreams/sps/introduction.mdx +++ b/website/pages/ur/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ur/substreams/sps/triggers.mdx b/website/pages/ur/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/ur/substreams/sps/triggers.mdx +++ b/website/pages/ur/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/ur/substreams/sps/triggers-example.mdx b/website/pages/ur/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/ur/substreams/sps/triggers-example.mdx rename to website/pages/ur/substreams/sps/tutorial.mdx diff --git a/website/pages/vi/substreams/sps/introduction.mdx b/website/pages/vi/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/vi/substreams/sps/introduction.mdx +++ b/website/pages/vi/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/vi/substreams/sps/triggers.mdx b/website/pages/vi/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/vi/substreams/sps/triggers.mdx +++ b/website/pages/vi/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/vi/substreams/sps/triggers-example.mdx b/website/pages/vi/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/vi/substreams/sps/triggers-example.mdx rename to website/pages/vi/substreams/sps/tutorial.mdx diff --git a/website/pages/zh/substreams/sps/introduction.mdx b/website/pages/zh/substreams/sps/introduction.mdx index 12e3f81c6d53..7c5fcae61777 100644 --- a/website/pages/zh/substreams/sps/introduction.mdx +++ b/website/pages/zh/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/zh/substreams/sps/triggers.mdx b/website/pages/zh/substreams/sps/triggers.mdx index ed19635d4768..8c8f9cf5b83b 100644 --- a/website/pages/zh/substreams/sps/triggers.mdx +++ b/website/pages/zh/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). diff --git a/website/pages/zh/substreams/sps/triggers-example.mdx b/website/pages/zh/substreams/sps/tutorial.mdx similarity index 100% rename from website/pages/zh/substreams/sps/triggers-example.mdx rename to website/pages/zh/substreams/sps/tutorial.mdx diff --git a/website/route-lockfile.txt b/website/route-lockfile.txt index c0990f2b0712..5db5f59504f0 100644 --- a/website/route-lockfile.txt +++ b/website/route-lockfile.txt @@ -30,10 +30,10 @@ /ar/subgraphs/cookbook/enums/ /ar/subgraphs/cookbook/grafting-hotfix/ /ar/subgraphs/cookbook/grafting/ -/ar/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /ar/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /ar/subgraphs/cookbook/near/ /ar/subgraphs/cookbook/pruning/ +/ar/subgraphs/cookbook/secure-api-keys-nextjs/ /ar/subgraphs/cookbook/subgraph-debug-forking/ /ar/subgraphs/cookbook/subgraph-uncrashable/ /ar/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -70,8 +70,8 @@ /ar/substreams/introduction/ /ar/substreams/sps/introduction/ /ar/substreams/sps/sps-faq/ -/ar/substreams/sps/triggers-example/ /ar/substreams/sps/triggers/ +/ar/substreams/sps/tutorial/ /ar/supported-networks/ /cs/ /cs/404/ @@ -104,10 +104,10 @@ /cs/subgraphs/cookbook/enums/ /cs/subgraphs/cookbook/grafting-hotfix/ /cs/subgraphs/cookbook/grafting/ -/cs/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /cs/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /cs/subgraphs/cookbook/near/ /cs/subgraphs/cookbook/pruning/ +/cs/subgraphs/cookbook/secure-api-keys-nextjs/ /cs/subgraphs/cookbook/subgraph-debug-forking/ /cs/subgraphs/cookbook/subgraph-uncrashable/ /cs/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -144,8 +144,8 @@ /cs/substreams/introduction/ /cs/substreams/sps/introduction/ /cs/substreams/sps/sps-faq/ -/cs/substreams/sps/triggers-example/ /cs/substreams/sps/triggers/ +/cs/substreams/sps/tutorial/ /cs/supported-networks/ /de/about/ /de/archived/arbitrum/arbitrum-faq/ @@ -176,10 +176,10 @@ /de/subgraphs/cookbook/enums/ /de/subgraphs/cookbook/grafting-hotfix/ /de/subgraphs/cookbook/grafting/ -/de/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /de/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /de/subgraphs/cookbook/near/ /de/subgraphs/cookbook/pruning/ +/de/subgraphs/cookbook/secure-api-keys-nextjs/ /de/subgraphs/cookbook/subgraph-debug-forking/ /de/subgraphs/cookbook/subgraph-uncrashable/ /de/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -216,8 +216,8 @@ /de/substreams/introduction/ /de/substreams/sps/introduction/ /de/substreams/sps/sps-faq/ -/de/substreams/sps/triggers-example/ /de/substreams/sps/triggers/ +/de/substreams/sps/tutorial/ /de/supported-networks/ /en/ /en/404/ @@ -250,10 +250,10 @@ /en/subgraphs/cookbook/enums/ /en/subgraphs/cookbook/grafting-hotfix/ /en/subgraphs/cookbook/grafting/ -/en/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /en/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /en/subgraphs/cookbook/near/ /en/subgraphs/cookbook/pruning/ +/en/subgraphs/cookbook/secure-api-keys-nextjs/ /en/subgraphs/cookbook/subgraph-debug-forking/ /en/subgraphs/cookbook/subgraph-uncrashable/ /en/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -295,8 +295,8 @@ /en/substreams/introduction/ /en/substreams/sps/introduction/ /en/substreams/sps/sps-faq/ -/en/substreams/sps/triggers-example/ /en/substreams/sps/triggers/ +/en/substreams/sps/tutorial/ /en/supported-networks/ /es/ /es/404/ @@ -329,10 +329,10 @@ /es/subgraphs/cookbook/enums/ /es/subgraphs/cookbook/grafting-hotfix/ /es/subgraphs/cookbook/grafting/ -/es/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /es/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /es/subgraphs/cookbook/near/ /es/subgraphs/cookbook/pruning/ +/es/subgraphs/cookbook/secure-api-keys-nextjs/ /es/subgraphs/cookbook/subgraph-debug-forking/ /es/subgraphs/cookbook/subgraph-uncrashable/ /es/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -369,8 +369,8 @@ /es/substreams/introduction/ /es/substreams/sps/introduction/ /es/substreams/sps/sps-faq/ -/es/substreams/sps/triggers-example/ /es/substreams/sps/triggers/ +/es/substreams/sps/tutorial/ /es/supported-networks/ /fr/ /fr/404/ @@ -403,10 +403,10 @@ /fr/subgraphs/cookbook/enums/ /fr/subgraphs/cookbook/grafting-hotfix/ /fr/subgraphs/cookbook/grafting/ -/fr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /fr/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /fr/subgraphs/cookbook/near/ /fr/subgraphs/cookbook/pruning/ +/fr/subgraphs/cookbook/secure-api-keys-nextjs/ /fr/subgraphs/cookbook/subgraph-debug-forking/ /fr/subgraphs/cookbook/subgraph-uncrashable/ /fr/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -443,8 +443,8 @@ /fr/substreams/introduction/ /fr/substreams/sps/introduction/ /fr/substreams/sps/sps-faq/ -/fr/substreams/sps/triggers-example/ /fr/substreams/sps/triggers/ +/fr/substreams/sps/tutorial/ /fr/supported-networks/ /hi/ /hi/404/ @@ -477,10 +477,10 @@ /hi/subgraphs/cookbook/enums/ /hi/subgraphs/cookbook/grafting-hotfix/ /hi/subgraphs/cookbook/grafting/ -/hi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /hi/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /hi/subgraphs/cookbook/near/ /hi/subgraphs/cookbook/pruning/ +/hi/subgraphs/cookbook/secure-api-keys-nextjs/ /hi/subgraphs/cookbook/subgraph-debug-forking/ /hi/subgraphs/cookbook/subgraph-uncrashable/ /hi/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -517,8 +517,8 @@ /hi/substreams/introduction/ /hi/substreams/sps/introduction/ /hi/substreams/sps/sps-faq/ -/hi/substreams/sps/triggers-example/ /hi/substreams/sps/triggers/ +/hi/substreams/sps/tutorial/ /hi/supported-networks/ /it/ /it/404/ @@ -551,10 +551,10 @@ /it/subgraphs/cookbook/enums/ /it/subgraphs/cookbook/grafting-hotfix/ /it/subgraphs/cookbook/grafting/ -/it/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /it/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /it/subgraphs/cookbook/near/ /it/subgraphs/cookbook/pruning/ +/it/subgraphs/cookbook/secure-api-keys-nextjs/ /it/subgraphs/cookbook/subgraph-debug-forking/ /it/subgraphs/cookbook/subgraph-uncrashable/ /it/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -591,8 +591,8 @@ /it/substreams/introduction/ /it/substreams/sps/introduction/ /it/substreams/sps/sps-faq/ -/it/substreams/sps/triggers-example/ /it/substreams/sps/triggers/ +/it/substreams/sps/tutorial/ /it/supported-networks/ /ja/ /ja/404/ @@ -625,10 +625,10 @@ /ja/subgraphs/cookbook/enums/ /ja/subgraphs/cookbook/grafting-hotfix/ /ja/subgraphs/cookbook/grafting/ -/ja/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /ja/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /ja/subgraphs/cookbook/near/ /ja/subgraphs/cookbook/pruning/ +/ja/subgraphs/cookbook/secure-api-keys-nextjs/ /ja/subgraphs/cookbook/subgraph-debug-forking/ /ja/subgraphs/cookbook/subgraph-uncrashable/ /ja/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -665,8 +665,8 @@ /ja/substreams/introduction/ /ja/substreams/sps/introduction/ /ja/substreams/sps/sps-faq/ -/ja/substreams/sps/triggers-example/ /ja/substreams/sps/triggers/ +/ja/substreams/sps/tutorial/ /ja/supported-networks/ /ko/about/ /ko/archived/arbitrum/arbitrum-faq/ @@ -697,10 +697,10 @@ /ko/subgraphs/cookbook/enums/ /ko/subgraphs/cookbook/grafting-hotfix/ /ko/subgraphs/cookbook/grafting/ -/ko/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /ko/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /ko/subgraphs/cookbook/near/ /ko/subgraphs/cookbook/pruning/ +/ko/subgraphs/cookbook/secure-api-keys-nextjs/ /ko/subgraphs/cookbook/subgraph-debug-forking/ /ko/subgraphs/cookbook/subgraph-uncrashable/ /ko/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -737,8 +737,8 @@ /ko/substreams/introduction/ /ko/substreams/sps/introduction/ /ko/substreams/sps/sps-faq/ -/ko/substreams/sps/triggers-example/ /ko/substreams/sps/triggers/ +/ko/substreams/sps/tutorial/ /ko/supported-networks/ /mr/ /mr/404/ @@ -771,10 +771,10 @@ /mr/subgraphs/cookbook/enums/ /mr/subgraphs/cookbook/grafting-hotfix/ /mr/subgraphs/cookbook/grafting/ -/mr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /mr/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /mr/subgraphs/cookbook/near/ /mr/subgraphs/cookbook/pruning/ +/mr/subgraphs/cookbook/secure-api-keys-nextjs/ /mr/subgraphs/cookbook/subgraph-debug-forking/ /mr/subgraphs/cookbook/subgraph-uncrashable/ /mr/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -811,8 +811,8 @@ /mr/substreams/introduction/ /mr/substreams/sps/introduction/ /mr/substreams/sps/sps-faq/ -/mr/substreams/sps/triggers-example/ /mr/substreams/sps/triggers/ +/mr/substreams/sps/tutorial/ /mr/supported-networks/ /nl/about/ /nl/archived/arbitrum/arbitrum-faq/ @@ -843,10 +843,10 @@ /nl/subgraphs/cookbook/enums/ /nl/subgraphs/cookbook/grafting-hotfix/ /nl/subgraphs/cookbook/grafting/ -/nl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /nl/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /nl/subgraphs/cookbook/near/ /nl/subgraphs/cookbook/pruning/ +/nl/subgraphs/cookbook/secure-api-keys-nextjs/ /nl/subgraphs/cookbook/subgraph-debug-forking/ /nl/subgraphs/cookbook/subgraph-uncrashable/ /nl/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -883,8 +883,8 @@ /nl/substreams/introduction/ /nl/substreams/sps/introduction/ /nl/substreams/sps/sps-faq/ -/nl/substreams/sps/triggers-example/ /nl/substreams/sps/triggers/ +/nl/substreams/sps/tutorial/ /nl/supported-networks/ /pl/about/ /pl/archived/arbitrum/arbitrum-faq/ @@ -915,10 +915,10 @@ /pl/subgraphs/cookbook/enums/ /pl/subgraphs/cookbook/grafting-hotfix/ /pl/subgraphs/cookbook/grafting/ -/pl/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /pl/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /pl/subgraphs/cookbook/near/ /pl/subgraphs/cookbook/pruning/ +/pl/subgraphs/cookbook/secure-api-keys-nextjs/ /pl/subgraphs/cookbook/subgraph-debug-forking/ /pl/subgraphs/cookbook/subgraph-uncrashable/ /pl/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -955,8 +955,8 @@ /pl/substreams/introduction/ /pl/substreams/sps/introduction/ /pl/substreams/sps/sps-faq/ -/pl/substreams/sps/triggers-example/ /pl/substreams/sps/triggers/ +/pl/substreams/sps/tutorial/ /pl/supported-networks/ /pt/ /pt/404/ @@ -989,10 +989,10 @@ /pt/subgraphs/cookbook/enums/ /pt/subgraphs/cookbook/grafting-hotfix/ /pt/subgraphs/cookbook/grafting/ -/pt/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /pt/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /pt/subgraphs/cookbook/near/ /pt/subgraphs/cookbook/pruning/ +/pt/subgraphs/cookbook/secure-api-keys-nextjs/ /pt/subgraphs/cookbook/subgraph-debug-forking/ /pt/subgraphs/cookbook/subgraph-uncrashable/ /pt/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1029,8 +1029,8 @@ /pt/substreams/introduction/ /pt/substreams/sps/introduction/ /pt/substreams/sps/sps-faq/ -/pt/substreams/sps/triggers-example/ /pt/substreams/sps/triggers/ +/pt/substreams/sps/tutorial/ /pt/supported-networks/ /ro/about/ /ro/archived/arbitrum/arbitrum-faq/ @@ -1061,10 +1061,10 @@ /ro/subgraphs/cookbook/enums/ /ro/subgraphs/cookbook/grafting-hotfix/ /ro/subgraphs/cookbook/grafting/ -/ro/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /ro/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /ro/subgraphs/cookbook/near/ /ro/subgraphs/cookbook/pruning/ +/ro/subgraphs/cookbook/secure-api-keys-nextjs/ /ro/subgraphs/cookbook/subgraph-debug-forking/ /ro/subgraphs/cookbook/subgraph-uncrashable/ /ro/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1101,8 +1101,8 @@ /ro/substreams/introduction/ /ro/substreams/sps/introduction/ /ro/substreams/sps/sps-faq/ -/ro/substreams/sps/triggers-example/ /ro/substreams/sps/triggers/ +/ro/substreams/sps/tutorial/ /ro/supported-networks/ /ru/ /ru/404/ @@ -1135,10 +1135,10 @@ /ru/subgraphs/cookbook/enums/ /ru/subgraphs/cookbook/grafting-hotfix/ /ru/subgraphs/cookbook/grafting/ -/ru/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /ru/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /ru/subgraphs/cookbook/near/ /ru/subgraphs/cookbook/pruning/ +/ru/subgraphs/cookbook/secure-api-keys-nextjs/ /ru/subgraphs/cookbook/subgraph-debug-forking/ /ru/subgraphs/cookbook/subgraph-uncrashable/ /ru/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1175,8 +1175,8 @@ /ru/substreams/introduction/ /ru/substreams/sps/introduction/ /ru/substreams/sps/sps-faq/ -/ru/substreams/sps/triggers-example/ /ru/substreams/sps/triggers/ +/ru/substreams/sps/tutorial/ /ru/supported-networks/ /sv/ /sv/404/ @@ -1209,10 +1209,10 @@ /sv/subgraphs/cookbook/enums/ /sv/subgraphs/cookbook/grafting-hotfix/ /sv/subgraphs/cookbook/grafting/ -/sv/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /sv/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /sv/subgraphs/cookbook/near/ /sv/subgraphs/cookbook/pruning/ +/sv/subgraphs/cookbook/secure-api-keys-nextjs/ /sv/subgraphs/cookbook/subgraph-debug-forking/ /sv/subgraphs/cookbook/subgraph-uncrashable/ /sv/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1249,8 +1249,8 @@ /sv/substreams/introduction/ /sv/substreams/sps/introduction/ /sv/substreams/sps/sps-faq/ -/sv/substreams/sps/triggers-example/ /sv/substreams/sps/triggers/ +/sv/substreams/sps/tutorial/ /sv/supported-networks/ /sw/about/ /sw/archived/arbitrum/arbitrum-faq/ @@ -1281,10 +1281,10 @@ /sw/subgraphs/cookbook/enums/ /sw/subgraphs/cookbook/grafting-hotfix/ /sw/subgraphs/cookbook/grafting/ -/sw/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /sw/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /sw/subgraphs/cookbook/near/ /sw/subgraphs/cookbook/pruning/ +/sw/subgraphs/cookbook/secure-api-keys-nextjs/ /sw/subgraphs/cookbook/subgraph-debug-forking/ /sw/subgraphs/cookbook/subgraph-uncrashable/ /sw/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1321,8 +1321,8 @@ /sw/substreams/introduction/ /sw/substreams/sps/introduction/ /sw/substreams/sps/sps-faq/ -/sw/substreams/sps/triggers-example/ /sw/substreams/sps/triggers/ +/sw/substreams/sps/tutorial/ /sw/supported-networks/ /tr/ /tr/404/ @@ -1355,10 +1355,10 @@ /tr/subgraphs/cookbook/enums/ /tr/subgraphs/cookbook/grafting-hotfix/ /tr/subgraphs/cookbook/grafting/ -/tr/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /tr/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /tr/subgraphs/cookbook/near/ /tr/subgraphs/cookbook/pruning/ +/tr/subgraphs/cookbook/secure-api-keys-nextjs/ /tr/subgraphs/cookbook/subgraph-debug-forking/ /tr/subgraphs/cookbook/subgraph-uncrashable/ /tr/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1395,8 +1395,8 @@ /tr/substreams/introduction/ /tr/substreams/sps/introduction/ /tr/substreams/sps/sps-faq/ -/tr/substreams/sps/triggers-example/ /tr/substreams/sps/triggers/ +/tr/substreams/sps/tutorial/ /tr/supported-networks/ /uk/about/ /uk/archived/arbitrum/arbitrum-faq/ @@ -1427,10 +1427,10 @@ /uk/subgraphs/cookbook/enums/ /uk/subgraphs/cookbook/grafting-hotfix/ /uk/subgraphs/cookbook/grafting/ -/uk/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /uk/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /uk/subgraphs/cookbook/near/ /uk/subgraphs/cookbook/pruning/ +/uk/subgraphs/cookbook/secure-api-keys-nextjs/ /uk/subgraphs/cookbook/subgraph-debug-forking/ /uk/subgraphs/cookbook/subgraph-uncrashable/ /uk/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1467,8 +1467,8 @@ /uk/substreams/introduction/ /uk/substreams/sps/introduction/ /uk/substreams/sps/sps-faq/ -/uk/substreams/sps/triggers-example/ /uk/substreams/sps/triggers/ +/uk/substreams/sps/tutorial/ /uk/supported-networks/ /ur/ /ur/404/ @@ -1501,10 +1501,10 @@ /ur/subgraphs/cookbook/enums/ /ur/subgraphs/cookbook/grafting-hotfix/ /ur/subgraphs/cookbook/grafting/ -/ur/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /ur/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /ur/subgraphs/cookbook/near/ /ur/subgraphs/cookbook/pruning/ +/ur/subgraphs/cookbook/secure-api-keys-nextjs/ /ur/subgraphs/cookbook/subgraph-debug-forking/ /ur/subgraphs/cookbook/subgraph-uncrashable/ /ur/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1541,8 +1541,8 @@ /ur/substreams/introduction/ /ur/substreams/sps/introduction/ /ur/substreams/sps/sps-faq/ -/ur/substreams/sps/triggers-example/ /ur/substreams/sps/triggers/ +/ur/substreams/sps/tutorial/ /ur/supported-networks/ /vi/about/ /vi/archived/arbitrum/arbitrum-faq/ @@ -1573,10 +1573,10 @@ /vi/subgraphs/cookbook/enums/ /vi/subgraphs/cookbook/grafting-hotfix/ /vi/subgraphs/cookbook/grafting/ -/vi/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /vi/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /vi/subgraphs/cookbook/near/ /vi/subgraphs/cookbook/pruning/ +/vi/subgraphs/cookbook/secure-api-keys-nextjs/ /vi/subgraphs/cookbook/subgraph-debug-forking/ /vi/subgraphs/cookbook/subgraph-uncrashable/ /vi/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1613,8 +1613,8 @@ /vi/substreams/introduction/ /vi/substreams/sps/introduction/ /vi/substreams/sps/sps-faq/ -/vi/substreams/sps/triggers-example/ /vi/substreams/sps/triggers/ +/vi/substreams/sps/tutorial/ /vi/supported-networks/ /zh/ /zh/404/ @@ -1647,10 +1647,10 @@ /zh/subgraphs/cookbook/enums/ /zh/subgraphs/cookbook/grafting-hotfix/ /zh/subgraphs/cookbook/grafting/ -/zh/subgraphs/cookbook/how-to-secure-api-keys-using-nextjs-server-components/ /zh/subgraphs/cookbook/immutable-entities-bytes-as-ids/ /zh/subgraphs/cookbook/near/ /zh/subgraphs/cookbook/pruning/ +/zh/subgraphs/cookbook/secure-api-keys-nextjs/ /zh/subgraphs/cookbook/subgraph-debug-forking/ /zh/subgraphs/cookbook/subgraph-uncrashable/ /zh/subgraphs/cookbook/substreams-powered-subgraphs/ @@ -1687,6 +1687,6 @@ /zh/substreams/introduction/ /zh/substreams/sps/introduction/ /zh/substreams/sps/sps-faq/ -/zh/substreams/sps/triggers-example/ /zh/substreams/sps/triggers/ +/zh/substreams/sps/tutorial/ /zh/supported-networks/ From 3560e12b544f66b783721af8d16132b38cbb3e69 Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 17:37:22 -0500 Subject: [PATCH 18/22] Ensure links have a trailing slash, since those are the canonical URLs --- website/pages/ar/indexing/chain-integration-overview.mdx | 2 +- website/pages/ar/resources/benefits.mdx | 2 +- website/pages/ar/subgraphs/cookbook/near.mdx | 2 +- .../ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ar/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/ar/subgraphs/querying/introduction.mdx | 2 +- website/pages/ar/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/cs/indexing/chain-integration-overview.mdx | 2 +- website/pages/cs/resources/benefits.mdx | 2 +- website/pages/cs/subgraphs/cookbook/near.mdx | 2 +- .../cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../cs/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/cs/subgraphs/querying/introduction.mdx | 2 +- website/pages/cs/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/de/indexing/chain-integration-overview.mdx | 2 +- website/pages/de/resources/benefits.mdx | 2 +- website/pages/de/subgraphs/cookbook/near.mdx | 2 +- .../de/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../de/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/de/subgraphs/querying/introduction.mdx | 2 +- website/pages/de/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/en/indexing/chain-integration-overview.mdx | 2 +- website/pages/en/resources/benefits.mdx | 2 +- website/pages/en/subgraphs/cookbook/near.mdx | 2 +- .../en/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../en/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/en/subgraphs/querying/introduction.mdx | 2 +- website/pages/en/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/es/indexing/chain-integration-overview.mdx | 2 +- website/pages/es/resources/benefits.mdx | 2 +- website/pages/es/subgraphs/cookbook/near.mdx | 2 +- .../es/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../es/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/es/subgraphs/querying/introduction.mdx | 2 +- website/pages/es/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/fr/indexing/chain-integration-overview.mdx | 2 +- website/pages/fr/resources/benefits.mdx | 2 +- website/pages/fr/subgraphs/cookbook/near.mdx | 2 +- .../fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../fr/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/fr/subgraphs/querying/introduction.mdx | 2 +- website/pages/fr/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/hi/indexing/chain-integration-overview.mdx | 2 +- website/pages/hi/indexing/new-chain-integration.mdx | 2 +- website/pages/hi/resources/benefits.mdx | 2 +- website/pages/hi/subgraphs/cookbook/near.mdx | 2 +- .../hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../hi/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/hi/subgraphs/querying/introduction.mdx | 2 +- website/pages/hi/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/it/indexing/chain-integration-overview.mdx | 2 +- website/pages/it/resources/benefits.mdx | 2 +- website/pages/it/subgraphs/cookbook/near.mdx | 2 +- .../it/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../it/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/it/subgraphs/querying/introduction.mdx | 2 +- website/pages/it/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/ja/indexing/chain-integration-overview.mdx | 2 +- website/pages/ja/resources/benefits.mdx | 2 +- website/pages/ja/subgraphs/cookbook/near.mdx | 2 +- .../ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ja/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/ja/subgraphs/querying/introduction.mdx | 2 +- website/pages/ko/indexing/chain-integration-overview.mdx | 2 +- website/pages/ko/resources/benefits.mdx | 2 +- website/pages/ko/subgraphs/cookbook/near.mdx | 2 +- .../ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ko/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/ko/subgraphs/querying/introduction.mdx | 2 +- website/pages/ko/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/mr/indexing/chain-integration-overview.mdx | 2 +- website/pages/mr/resources/benefits.mdx | 2 +- website/pages/mr/subgraphs/cookbook/near.mdx | 2 +- .../mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../mr/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/mr/subgraphs/querying/introduction.mdx | 2 +- website/pages/mr/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/nl/indexing/chain-integration-overview.mdx | 2 +- website/pages/nl/resources/benefits.mdx | 2 +- website/pages/nl/subgraphs/cookbook/near.mdx | 2 +- .../nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../nl/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/nl/subgraphs/querying/introduction.mdx | 2 +- website/pages/nl/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/pl/indexing/chain-integration-overview.mdx | 2 +- website/pages/pl/resources/benefits.mdx | 2 +- website/pages/pl/subgraphs/cookbook/near.mdx | 2 +- .../pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../pl/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/pl/subgraphs/querying/introduction.mdx | 2 +- website/pages/pl/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/pt/archived/arbitrum/arbitrum-faq.mdx | 2 +- website/pages/pt/indexing/chain-integration-overview.mdx | 2 +- website/pages/pt/resources/benefits.mdx | 2 +- website/pages/pt/subgraphs/cookbook/near.mdx | 2 +- .../pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../pt/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/pt/subgraphs/querying/introduction.mdx | 2 +- website/pages/pt/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/ro/indexing/chain-integration-overview.mdx | 2 +- website/pages/ro/resources/benefits.mdx | 2 +- website/pages/ro/subgraphs/cookbook/near.mdx | 2 +- .../ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ro/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/ro/subgraphs/querying/introduction.mdx | 2 +- website/pages/ro/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/ru/indexing/chain-integration-overview.mdx | 2 +- website/pages/ru/resources/benefits.mdx | 2 +- website/pages/ru/subgraphs/cookbook/near.mdx | 2 +- .../ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ru/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/ru/subgraphs/querying/introduction.mdx | 2 +- website/pages/ru/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/sv/indexing/chain-integration-overview.mdx | 2 +- website/pages/sv/resources/benefits.mdx | 2 +- website/pages/sv/subgraphs/cookbook/near.mdx | 2 +- .../sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../sv/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/sv/subgraphs/querying/introduction.mdx | 2 +- website/pages/sv/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/sw/indexing/chain-integration-overview.mdx | 2 +- website/pages/sw/resources/benefits.mdx | 2 +- website/pages/sw/subgraphs/cookbook/near.mdx | 2 +- .../sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../sw/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/sw/subgraphs/querying/introduction.mdx | 2 +- website/pages/sw/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/tr/indexing/chain-integration-overview.mdx | 2 +- website/pages/tr/resources/benefits.mdx | 2 +- website/pages/tr/subgraphs/cookbook/near.mdx | 2 +- .../tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../tr/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/tr/subgraphs/querying/introduction.mdx | 2 +- website/pages/tr/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/uk/indexing/chain-integration-overview.mdx | 2 +- website/pages/uk/resources/benefits.mdx | 2 +- website/pages/uk/subgraphs/cookbook/near.mdx | 2 +- .../uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../uk/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/uk/subgraphs/querying/introduction.mdx | 2 +- website/pages/uk/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/ur/indexing/chain-integration-overview.mdx | 2 +- website/pages/ur/resources/benefits.mdx | 2 +- website/pages/ur/subgraphs/cookbook/near.mdx | 2 +- .../ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 2 +- .../ur/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/ur/subgraphs/querying/introduction.mdx | 2 +- website/pages/ur/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/vi/indexing/chain-integration-overview.mdx | 2 +- website/pages/vi/resources/benefits.mdx | 2 +- website/pages/vi/subgraphs/cookbook/near.mdx | 2 +- .../vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../vi/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/vi/subgraphs/querying/introduction.mdx | 2 +- website/pages/vi/substreams/sps/sps-faq.mdx | 4 ++-- website/pages/zh/indexing/chain-integration-overview.mdx | 2 +- website/pages/zh/resources/benefits.mdx | 2 +- website/pages/zh/subgraphs/cookbook/near.mdx | 2 +- .../zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../zh/subgraphs/developing/creating/install-the-cli.mdx | 2 +- website/pages/zh/subgraphs/querying/introduction.mdx | 2 +- website/pages/zh/substreams/sps/sps-faq.mdx | 4 ++-- 162 files changed, 206 insertions(+), 206 deletions(-) diff --git a/website/pages/ar/indexing/chain-integration-overview.mdx b/website/pages/ar/indexing/chain-integration-overview.mdx index b8e41513fa9d..458e5a4f54f7 100644 --- a/website/pages/ar/indexing/chain-integration-overview.mdx +++ b/website/pages/ar/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: نظرة عامة حول عملية التكامل مع الشبكة ## المرحلة الأولى: التكامل التقني -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - تستهل الفرق عملية التكامل مع البروتوكول من خلال إنشاء موضوع في المنتدى هنا(https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (الفئة الفرعية "مصادر البيانات الجديدة" تحت قسم "الحوكمة واقتراحات تحسين الغراف"). استخدام قالب المنتدى الافتراضي إلزامي. ## المرحلة الثانية: التحقق من صحة التكامل diff --git a/website/pages/ar/resources/benefits.mdx b/website/pages/ar/resources/benefits.mdx index 3bdd3f1e6e25..e29acaf1ac5f 100644 --- a/website/pages/ar/resources/benefits.mdx +++ b/website/pages/ar/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/ar/subgraphs/cookbook/near.mdx b/website/pages/ar/subgraphs/cookbook/near.mdx index b2f9eaf75feb..8b4f6088b85c 100644 --- a/website/pages/ar/subgraphs/cookbook/near.mdx +++ b/website/pages/ar/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ accounts: ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## المراجع diff --git a/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx index b18e9aa8f7fb..5517fefa4032 100644 --- a/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | الاصدار | ملاحظات الإصدار | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ar/subgraphs/querying/introduction.mdx b/website/pages/ar/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/ar/subgraphs/querying/introduction.mdx +++ b/website/pages/ar/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ar/substreams/sps/sps-faq.mdx b/website/pages/ar/substreams/sps/sps-faq.mdx index d46783a1f7e3..9795fb40f711 100644 --- a/website/pages/ar/substreams/sps/sps-faq.mdx +++ b/website/pages/ar/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -اذهب إلى [وثائق سبستريمز](/substreams) للتعرف على المزيد حول سبستريمز. +اذهب إلى [وثائق سبستريمز](/substreams/) للتعرف على المزيد حول سبستريمز. ## ما هي الغرافات الفرعية المدعومة بسبستريمز؟ @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## أين يمكن للمطورين الوصول إلى مزيد من المعلومات حول الغرافات الفرعية المدعومة بسبستريمز و سبستريمز؟ -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. ستوضح لك [وثائق الغرافات الفرعية المدعومة بواسطة سبستريمز](/cookbook/substreams-powered-subgraphs/) كيفية تجميعها للنشر على الغراف. diff --git a/website/pages/cs/indexing/chain-integration-overview.mdx b/website/pages/cs/indexing/chain-integration-overview.mdx index 673d312e81e1..6252d43dc36a 100644 --- a/website/pages/cs/indexing/chain-integration-overview.mdx +++ b/website/pages/cs/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Pro blockchainové týmy, které usilují o [integraci s protokolem The Graph](h ## Fáze 1. Technická integrace -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Týmy zahájí proces integrace protokolu vytvořením vlákna na fóru [zde](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (podkategorie Nové zdroje dat v části Správa a GIP). Použití výchozí šablony Fóra je povinné. ## Fáze 2. Ověřování integrace diff --git a/website/pages/cs/resources/benefits.mdx b/website/pages/cs/resources/benefits.mdx index 98d8bba2cb04..fdff16533bbb 100644 --- a/website/pages/cs/resources/benefits.mdx +++ b/website/pages/cs/resources/benefits.mdx @@ -89,4 +89,4 @@ Decentralizovaná síť Grafu poskytuje uživatelům přístup ke geografické r Podtrženo a sečteno: Síť Graf je levnější, jednodušší na používání a poskytuje lepší výsledky než lokální provozování `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/cs/subgraphs/cookbook/near.mdx b/website/pages/cs/subgraphs/cookbook/near.mdx index ac95d0149954..75946639fc4d 100644 --- a/website/pages/cs/subgraphs/cookbook/near.mdx +++ b/website/pages/cs/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pro podgrafy NEAR zatím nejsou podporovány čekající funkce. V mezidobí mů ### Moje otázka nebyla zodpovězena, kde mohu získat další pomoc při vytváření podgrafů NEAR? -Pokud se jedná o obecnou otázku týkající se vývoje podgrafů, je zde mnohem více informací ve zbytku [dokumentace pro vývojáře](/quick-start). Jinak se prosím připojte k [The Graph Protocol Discord](https://discord.gg/graphprotocol) a zeptejte se na #near kanálu nebo e-mailem near@thegraph.com. +Pokud se jedná o obecnou otázku týkající se vývoje podgrafů, je zde mnohem více informací ve zbytku [dokumentace pro vývojáře](/quick-start/). Jinak se prosím připojte k [The Graph Protocol Discord](https://discord.gg/graphprotocol) a zeptejte se na #near kanálu nebo e-mailem near@thegraph.com. ## Odkazy: diff --git a/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 667360c3b437..d6d58b3e45f0 100644 --- a/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Podgrafy napájen substreamů --- -[Substreams](/substreams) je nový framework pro zpracování blockchainových dat vyvinutý společností StreamingFast pro The Grafu síť. Moduly Substreams mohou vypisovat změny entit, které jsou kompatibilní s entitami Subgraph. Subgraph může takový modul Substreams používat jako zdroj dat, což vývojářům Subgraphu přináší rychlost indexování a další data Substreams. +[Substreams](/substreams/) je nový framework pro zpracování blockchainových dat vyvinutý společností StreamingFast pro The Grafu síť. Moduly Substreams mohou vypisovat změny entit, které jsou kompatibilní s entitami Subgraph. Subgraph může takový modul Substreams používat jako zdroj dat, což vývojářům Subgraphu přináší rychlost indexování a další data Substreams. ## Požadavky @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Definování balíčku Substreams -Balíček Substreams se skládá z typů (definovaných jako [Protocol Buffers](https://protobuf.dev/)), modulů (napsaných v jazyce Rust) a souboru `substreams.yaml`, který odkazuje na typy a určuje, jak se moduly spouštějí. [Navštivte dokumentaci Substreams, kde se dozvíte více o vývoji Substreams](/substreams), a podívejte se na [awesome-substreams](https://github.com/pinax-network/awesome-substreams) a [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook), kde najdete další příklady. +Balíček Substreams se skládá z typů (definovaných jako [Protocol Buffers](https://protobuf.dev/)), modulů (napsaných v jazyce Rust) a souboru `substreams.yaml`, který odkazuje na typy a určuje, jak se moduly spouštějí. [Navštivte dokumentaci Substreams, kde se dozvíte více o vývoji Substreams](/substreams/), a podívejte se na [awesome-substreams](https://github.com/pinax-network/awesome-substreams) a [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook), kde najdete další příklady. Dotyčný balíček Substreams detekuje nasazení kontraktů na Mainnet Ethereum a sleduje blok vytvoření a časové razítko všech nově nasazených kontraktů. K tomu je v souboru `/proto/example.proto` ([více informací o definování protokolových bufferů](https://protobuf.dev/programming-guides/proto3/#simple)) vyhrazen typ `Contract`: diff --git a/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx index 41abfbdccf16..cbde00522844 100644 --- a/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Soubor(y) ABI se musí shodovat s vaší smlouvou. Soubory ABI lze získat něko | Verze | Poznámky vydání | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/cs/subgraphs/querying/introduction.mdx b/website/pages/cs/subgraphs/querying/introduction.mdx index b6baece6bdaa..9489bcf47b46 100644 --- a/website/pages/cs/subgraphs/querying/introduction.mdx +++ b/website/pages/cs/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/cs/substreams/sps/sps-faq.mdx b/website/pages/cs/substreams/sps/sps-faq.mdx index 330cafa3d2d5..dd0612c56071 100644 --- a/website/pages/cs/substreams/sps/sps-faq.mdx +++ b/website/pages/cs/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Podgrafy napájen substreamů Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Další informace o substreamu naleznete v [Dokumentace k substreamů](/substreams). +Další informace o substreamu naleznete v [Dokumentace k substreamů](/substreams/). ## Co jsou substreamu napájen podgrafy? @@ -62,7 +62,7 @@ Používání Firehose přináší mnoho výhod, včetně: ## Kde mohou vývojáři získat více informací o substreamu, které jsou založeny na podgraf a substreamu? -Dokumentace [Substreams](/substreams) vás naučí, jak vytvářet moduly Substreams. +Dokumentace [Substreams](/substreams/) vás naučí, jak vytvářet moduly Substreams. Dokumentace [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) vám ukáže, jak je zabalit pro nasazení na Grafu. diff --git a/website/pages/de/indexing/chain-integration-overview.mdx b/website/pages/de/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/de/indexing/chain-integration-overview.mdx +++ b/website/pages/de/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/de/resources/benefits.mdx b/website/pages/de/resources/benefits.mdx index f9aec6eee091..7323852385c9 100644 --- a/website/pages/de/resources/benefits.mdx +++ b/website/pages/de/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/de/subgraphs/cookbook/near.mdx b/website/pages/de/subgraphs/cookbook/near.mdx index 6ab983b22272..4d1d5530e04e 100644 --- a/website/pages/de/subgraphs/cookbook/near.mdx +++ b/website/pages/de/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx index 91922e0319e7..246d4892fd52 100644 --- a/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/de/subgraphs/querying/introduction.mdx b/website/pages/de/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/de/subgraphs/querying/introduction.mdx +++ b/website/pages/de/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/de/substreams/sps/sps-faq.mdx b/website/pages/de/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/de/substreams/sps/sps-faq.mdx +++ b/website/pages/de/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/en/indexing/chain-integration-overview.mdx b/website/pages/en/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/en/indexing/chain-integration-overview.mdx +++ b/website/pages/en/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/en/resources/benefits.mdx b/website/pages/en/resources/benefits.mdx index 51f56543d484..faefb37bb683 100644 --- a/website/pages/en/resources/benefits.mdx +++ b/website/pages/en/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/en/subgraphs/cookbook/near.mdx b/website/pages/en/subgraphs/cookbook/near.mdx index f2509e44e84c..8e0be3f5ce4e 100644 --- a/website/pages/en/subgraphs/cookbook/near.mdx +++ b/website/pages/en/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx index 282c68973a8a..86686025b089 100644 --- a/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/en/subgraphs/querying/introduction.mdx b/website/pages/en/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/en/subgraphs/querying/introduction.mdx +++ b/website/pages/en/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/en/substreams/sps/sps-faq.mdx b/website/pages/en/substreams/sps/sps-faq.mdx index 26b2cae1127e..0774edc32dea 100644 --- a/website/pages/en/substreams/sps/sps-faq.mdx +++ b/website/pages/en/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-Powered Subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/es/indexing/chain-integration-overview.mdx b/website/pages/es/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/es/indexing/chain-integration-overview.mdx +++ b/website/pages/es/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/es/resources/benefits.mdx b/website/pages/es/resources/benefits.mdx index 1b8a5510f076..6dc95622629c 100644 --- a/website/pages/es/resources/benefits.mdx +++ b/website/pages/es/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy En conclusión: The Graph Network es menos costoso, más fácil de usar y produce resultados superiores en comparación con ejecutar un `graph-node` localmente. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/es/subgraphs/cookbook/near.mdx b/website/pages/es/subgraphs/cookbook/near.mdx index f915ec580057..1b01dee85059 100644 --- a/website/pages/es/subgraphs/cookbook/near.mdx +++ b/website/pages/es/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ La funcionalidad pendiente aún no es compatible con los subgrafos NEAR. Mientra ### Mi pregunta no ha sido respondida, ¿dónde puedo obtener más ayuda para crear subgrafos NEAR? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## Referencias diff --git a/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx index b70948811960..3f54aeed7a4c 100644 --- a/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Los archivos ABI deben coincidir con tu(s) contrato(s). Hay varias formas de obt | Version | Notas del lanzamiento | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/es/subgraphs/querying/introduction.mdx b/website/pages/es/subgraphs/querying/introduction.mdx index fc87e026d7a1..94fc00ea08b8 100644 --- a/website/pages/es/subgraphs/querying/introduction.mdx +++ b/website/pages/es/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/es/substreams/sps/sps-faq.mdx b/website/pages/es/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/es/substreams/sps/sps-faq.mdx +++ b/website/pages/es/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/fr/indexing/chain-integration-overview.mdx b/website/pages/fr/indexing/chain-integration-overview.mdx index 8e3cc18a00bd..17b6f3567e6d 100644 --- a/website/pages/fr/indexing/chain-integration-overview.mdx +++ b/website/pages/fr/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Un processus d'intégration transparent et basé sur la gouvernance a été con ## Étape 1. Intégration technique -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Les équipes lancent le processus d'intégration du protocole en créant un fil de discussion sur le forum [ici](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (sous-catégorie Nouvelles sources de données sous Gouvernance et GIPs ). L'utilisation du modèle de forum par défaut est obligatoire. ## Étape 2. Validation de l'intégration diff --git a/website/pages/fr/resources/benefits.mdx b/website/pages/fr/resources/benefits.mdx index d290716f01bd..7b1523a93dd9 100644 --- a/website/pages/fr/resources/benefits.mdx +++ b/website/pages/fr/resources/benefits.mdx @@ -90,4 +90,4 @@ Le réseau décentralisé du Graph permet aux utilisateurs d'accéder à une red En résumé : Le réseau de graphs est moins coûteux, plus facile à utiliser et produit des résultats supérieurs à ceux obtenus par l'exécution locale d'un `nœud de graphs`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/fr/subgraphs/cookbook/near.mdx b/website/pages/fr/subgraphs/cookbook/near.mdx index cb3ed047e136..36c04cb55379 100644 --- a/website/pages/fr/subgraphs/cookbook/near.mdx +++ b/website/pages/fr/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ La fonctionnalité "pending" n'est pas encore prise en charge pour les subgraphs ### Ma question n'a pas reçu de réponse, où puis-je obtenir plus d'aide concernant la création de subgraphs NEAR ? -S'il s'agit d'une question générale sur le développement de subgraphs, il y a beaucoup plus d'informations dans le reste de la [Documentation du développeur](/quick-start). Sinon, veuillez rejoindre [The Graph Protocol Discord](https://discord.gg/graphprotocol) et poser votre question sur le canal #near ou par e-mail à near@thegraph.com. +S'il s'agit d'une question générale sur le développement de subgraphs, il y a beaucoup plus d'informations dans le reste de la [Documentation du développeur](/quick-start/). Sinon, veuillez rejoindre [The Graph Protocol Discord](https://discord.gg/graphprotocol) et poser votre question sur le canal #near ou par e-mail à near@thegraph.com. ## Les Références diff --git a/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx index e4272870000c..1a57fffc4121 100644 --- a/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Subgraphs alimentés par Substreams --- -[Substreams](/substreams) est un nouveau framework de traitement des données blockchain, développé par StreamingFast pour The Graph Network. Un module de sous-flux peut générer des modifications d'entité, qui sont compatibles avec les entités Subgraph. Un subgraph peut utiliser un tel module Substreams comme source de données, apportant la vitesse d'indexation et les données supplémentaires des Substreams aux développeurs de subgraphs. +[Substreams](/substreams/) est un nouveau framework de traitement des données blockchain, développé par StreamingFast pour The Graph Network. Un module de sous-flux peut générer des modifications d'entité, qui sont compatibles avec les entités Subgraph. Un subgraph peut utiliser un tel module Substreams comme source de données, apportant la vitesse d'indexation et les données supplémentaires des Substreams aux développeurs de subgraphs. ## Exigences @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Définir un package Substreams -Un paquet Substreams est composé de types (définis comme [Protocol Buffers](https://protobuf.dev/)), de modules (écrits en Rust) et d'un fichier `substreams.yaml` qui référence les types et spécifie comment les modules sont déclenchés. [Visitez la documentation Substreams pour en savoir plus sur le développement de Substreams](/substreams), et consultez [awesome-substreams](https://github.com/pinax-network/awesome-substreams) et le [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) pour plus d'exemples. +Un paquet Substreams est composé de types (définis comme [Protocol Buffers](https://protobuf.dev/)), de modules (écrits en Rust) et d'un fichier `substreams.yaml` qui référence les types et spécifie comment les modules sont déclenchés. [Visitez la documentation Substreams pour en savoir plus sur le développement de Substreams](/substreams/), et consultez [awesome-substreams](https://github.com/pinax-network/awesome-substreams) et le [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) pour plus d'exemples. Le package Substreams en question détecte les déploiements de contrats sur Mainnet Ethereum, en suivant le bloc de création et l'horodatage de tous les contrats nouvellement déployés. Pour ce faire, il existe un type `Contract` dédié dans `/proto/example.proto` ([en savoir plus sur la définition des tampons de protocole](https://protobuf.dev/programming-guides/proto3/#simple)) : diff --git a/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx index d5f137f2260f..d5f4ec246945 100644 --- a/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Le(s) fichier(s) ABI doivent correspondre à votre(vos) contrat(s). Il existe pl | Version | Notes de version | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/fr/subgraphs/querying/introduction.mdx b/website/pages/fr/subgraphs/querying/introduction.mdx index 1b838400c6d3..9e6685937575 100644 --- a/website/pages/fr/subgraphs/querying/introduction.mdx +++ b/website/pages/fr/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/fr/substreams/sps/sps-faq.mdx b/website/pages/fr/substreams/sps/sps-faq.mdx index b5510cf7441c..ca95d4bd375c 100644 --- a/website/pages/fr/substreams/sps/sps-faq.mdx +++ b/website/pages/fr/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: FAQ sur les subgraphs alimentés par les sous-flux Développé par [StreamingFast](https://www.streamingfast.io/), Substreams est un moteur de traitement extrêmement puissant capable de consommer des flux riches de données blockchain. Substreams vous permet de raffiner et de structurer les données blockchain pour une digestion rapide et fluide par les applications des utilisateurs finaux. Plus précisément, Substreams est un moteur agnostique à la blockchain, parallélisé et axé sur le streaming, servant de couche de transformation des données blockchain. Propulsé par [Firehose](https://firehose.streamingfast.io/), il permet aux développeurs d'écrire des modules Rust, de s'appuyer sur des modules communautaires, de fournir une indexation très performante, et de [diriger(sink)](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) leurs données vers n'importe quelle destination. -Rendez-vous sur le site [Substreams Documentation](/substreams) pour en savoir plus sur Substreams. +Rendez-vous sur le site [Substreams Documentation](/substreams/) pour en savoir plus sur Substreams. ## Qu'est-ce qu'un subgraph alimenté par des courants de fond ? @@ -62,7 +62,7 @@ L'utilisation de Firehose présente de nombreux avantages, notamment: ## Où les développeurs peuvent-ils trouver plus d'informations sur les subgraphs alimentés par Substreams et sur Substreams ? -La [documentation Substreams](/substreams) vous apprendra à construire des modules Substreams. +La [documentation Substreams](/substreams/) vous apprendra à construire des modules Substreams. La [documentation sur les subgraphs alimentés par des flux partiels] (/cookbook/substreams-powered-subgraphs/) vous montrera comment les emballer pour les déployer sur The Graph. diff --git a/website/pages/hi/indexing/chain-integration-overview.mdx b/website/pages/hi/indexing/chain-integration-overview.mdx index 575d0b186105..5645f822336d 100644 --- a/website/pages/hi/indexing/chain-integration-overview.mdx +++ b/website/pages/hi/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- कृपया [New Chain Integration](/new-chain-integration) पर जाएं नई chains के लिए `graph-node` समर्थन के बारे में जानकारी के लिए. +- कृपया [New Chain Integration](/new-chain-integration/) पर जाएं नई chains के लिए `graph-node` समर्थन के बारे में जानकारी के लिए. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/hi/indexing/new-chain-integration.mdx b/website/pages/hi/indexing/new-chain-integration.mdx index e2bd36ba8ad3..1ca8eaab721f 100644 --- a/website/pages/hi/indexing/new-chain-integration.mdx +++ b/website/pages/hi/indexing/new-chain-integration.mdx @@ -49,7 +49,7 @@ EVM चेन के लिए, एक गहरे स्तर के डे - सभी `getLogs` कॉल्स और राउंडट्रिप्स को एकल स्ट्रीम द्वारा प्रतिस्थापित किया जाता है, जो सीधे `graph-node` के केंद्र में पहुंचती है; यह एकल ब्लॉक मॉडल सभी सबग्राफ्स के लिए काम करता है जिन्हें यह प्रोसेस करता है। -> **NOTE**: EVM chains के लिए Firehose-based integration के लिए अभी भी Indexers को chain के संग्रह RPC node को subgraph को ठीक से index करने के लिए चलाने की आवश्यकता होगी। यह `eth_call` RPC विधि द्वारा आम तौर पर पहुंच योग्य smart contract स्थिति प्रदान करने में Firehosesकी असमर्थता के कारण है। (It's worth reminding that eth_calls are [not a good practice for developers](/)) +> **NOTE**: EVM chains के लिए Firehose-based integration के लिए अभी भी Indexers को chain के संग्रह RPC node को subgraph को ठीक से index करने के लिए चलाने की आवश्यकता होगी। यह `eth_call` RPC विधि द्वारा आम तौर पर पहुंच योग्य smart contract स्थिति प्रदान करने में Firehosesकी असमर्थता के कारण है। (It's worth reminding that eth_calls are [not a good practice for developers](/)/) ## Graph Node Configuration diff --git a/website/pages/hi/resources/benefits.mdx b/website/pages/hi/resources/benefits.mdx index 72171c86bf9c..2a4bfd334b1a 100644 --- a/website/pages/hi/resources/benefits.mdx +++ b/website/pages/hi/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy निचला रेखा: ग्राफ़ नेटवर्क कम खर्चीला है, उपयोग में आसान है, और `ग्राफ़-नोड` को स्थानीय रूप से चलाने की तुलना में बेहतर परिणाम देता है। -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/hi/subgraphs/cookbook/near.mdx b/website/pages/hi/subgraphs/cookbook/near.mdx index 6ffcaca61696..df507a2c7efb 100644 --- a/website/pages/hi/subgraphs/cookbook/near.mdx +++ b/website/pages/hi/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ NEAR सबग्राफ के लिए पेंडिंग कार् ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## संदर्भ diff --git a/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx index f4ddd954e659..1438848807bd 100644 --- a/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | संस्करण | रिलीज नोट्स | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/hi/subgraphs/querying/introduction.mdx b/website/pages/hi/subgraphs/querying/introduction.mdx index 54d07075671a..5e1b2bb344f4 100644 --- a/website/pages/hi/subgraphs/querying/introduction.mdx +++ b/website/pages/hi/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/hi/substreams/sps/sps-faq.mdx b/website/pages/hi/substreams/sps/sps-faq.mdx index 4ac776772148..d874a6641801 100644 --- a/website/pages/hi/substreams/sps/sps-faq.mdx +++ b/website/pages/hi/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/it/indexing/chain-integration-overview.mdx b/website/pages/it/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/it/indexing/chain-integration-overview.mdx +++ b/website/pages/it/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/it/resources/benefits.mdx b/website/pages/it/resources/benefits.mdx index 19b319509f8a..a3ffbeefeccb 100644 --- a/website/pages/it/resources/benefits.mdx +++ b/website/pages/it/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy In conclusione: The Graph Network è meno costosa, più facile da usare e produce risultati superiori rispetto alla gestione locale di `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/it/subgraphs/cookbook/near.mdx b/website/pages/it/subgraphs/cookbook/near.mdx index 1d2edfe873eb..a15966136fb9 100644 --- a/website/pages/it/subgraphs/cookbook/near.mdx +++ b/website/pages/it/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## Riferimenti diff --git a/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx index bc62da7231bc..ea35b67fb8e3 100644 --- a/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ I file ABI devono corrispondere al vostro contratto. Esistono diversi modi per o | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/it/subgraphs/querying/introduction.mdx b/website/pages/it/subgraphs/querying/introduction.mdx index 2041f36072de..d139dfe55258 100644 --- a/website/pages/it/subgraphs/querying/introduction.mdx +++ b/website/pages/it/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/it/substreams/sps/sps-faq.mdx b/website/pages/it/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/it/substreams/sps/sps-faq.mdx +++ b/website/pages/it/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/ja/indexing/chain-integration-overview.mdx b/website/pages/ja/indexing/chain-integration-overview.mdx index 2a72e99283a4..a1895f77ea6f 100644 --- a/website/pages/ja/indexing/chain-integration-overview.mdx +++ b/website/pages/ja/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: チェーン統合プロセスの概要 ## ステージ 1. 技術的統合 -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - チームは、プロトコルの統合プロセスを開始するために、[here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)のフォーラムスレッドを作成します（Governance & GIPsの下にあるNew Data Sourcesのサブカテゴリ内）。デフォルトのフォーラムテンプレートの使用が必須です。 ## ステージ 2. 統合の検証 diff --git a/website/pages/ja/resources/benefits.mdx b/website/pages/ja/resources/benefits.mdx index da4b2d00900b..48f335f3be72 100644 --- a/website/pages/ja/resources/benefits.mdx +++ b/website/pages/ja/resources/benefits.mdx @@ -89,4 +89,4 @@ Graphの分散型ネットワークは、`graph-node`をセルフホストする 結論: グラフ ネットワークは、ローカルで `graph-node` を実行するよりも安価で使いやすく、優れた結果を生み出します。 -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/ja/subgraphs/cookbook/near.mdx b/website/pages/ja/subgraphs/cookbook/near.mdx index 8c5f1625eaeb..e6913d4d66a5 100644 --- a/website/pages/ja/subgraphs/cookbook/near.mdx +++ b/website/pages/ja/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ accounts: ### 私の質問に対する回答がありません。NEAR サブグラフの作成に関するヘルプはどこで入手できますか? -もし、サブグラフ開発に関する一般的な質問であれば、[開発者ドキュメント](/quick-start)に多くの情報があります。それ以外の場合は、[The Graph Protocol Discord](https://discord.gg/graphprotocol)に参加し、#nearチャンネルで質問するか、near@thegraph.comまでお寄せください。 +もし、サブグラフ開発に関する一般的な質問であれば、[開発者ドキュメント](/quick-start/)に多くの情報があります。それ以外の場合は、[The Graph Protocol Discord](https://discord.gg/graphprotocol)に参加し、#nearチャンネルで質問するか、near@thegraph.comまでお寄せください。 ## 参考文献 diff --git a/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx index d37080612f41..801faa5a0f20 100644 --- a/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams)は、StreamingFastがThe Graph Networkのために開発した、ブロックチェーンのデータを処理するための新しいフレームワークである。サブストリームモジュールは、サブグラフエンティティと互換性のあるエンティティの変更を出力することができます。サブグラフはこのようなサブストリームモジュールをデータソースとして使用することができ、サブストリームのインデックス作成速度と追加データをサブグラフ開発者にもたらします。 +[Substreams](/substreams/)は、StreamingFastがThe Graph Networkのために開発した、ブロックチェーンのデータを処理するための新しいフレームワークである。サブストリームモジュールは、サブグラフエンティティと互換性のあるエンティティの変更を出力することができます。サブグラフはこのようなサブストリームモジュールをデータソースとして使用することができ、サブストリームのインデックス作成速度と追加データをサブグラフ開発者にもたらします。 ## 要件 @@ -22,7 +22,7 @@ npm install -g @graphprotocol/graph-cli ## サブストリームパッケージの定義 -Substreamsパッケージは、型（[プロトコルバッファ](https://protobuf.dev/)として定義される）、モジュール（Rustで記述される）、および型を参照し、モジュールがどのようにトリガーされるかを指定する`substreams.yaml`ファイルで構成されます。[サブストリームの開発についての詳細はサブストリームのドキュメントを参照](/substreams)してください。また、[awesome-substreams](https://github.com/pinax-network/awesome-substreams)や[Substreams cookbook](https://github.com/pinax-network/substreams-cookbook)を参照してください。 +Substreamsパッケージは、型（[プロトコルバッファ](https://protobuf.dev/)として定義される）、モジュール（Rustで記述される）、および型を参照し、モジュールがどのようにトリガーされるかを指定する`substreams.yaml`ファイルで構成されます。[サブストリームの開発についての詳細はサブストリームのドキュメントを参照](/substreams/)してください。また、[awesome-substreams](https://github.com/pinax-network/awesome-substreams)や[Substreams cookbook](https://github.com/pinax-network/substreams-cookbook)を参照してください。 問題の Substreams パッケージは、メインネット イーサリアム上のコントラクトのデプロイメントを検出し、新しくデプロイされたすべてのコントラクトの作成ブロックとタイムスタンプを追跡します。これを行うには、`/proto/example.proto` に専用の `Contract` タイプがあります ([プロトコル バッファーの定義の詳細](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx index 80ecfac7d53c..900aac861511 100644 --- a/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI ファイルは、契約内容と一致している必要があります。A | バージョン | リリースノート | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ja/subgraphs/querying/introduction.mdx b/website/pages/ja/subgraphs/querying/introduction.mdx index 663be78da991..090cbf888524 100644 --- a/website/pages/ja/subgraphs/querying/introduction.mdx +++ b/website/pages/ja/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ko/indexing/chain-integration-overview.mdx b/website/pages/ko/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/ko/indexing/chain-integration-overview.mdx +++ b/website/pages/ko/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/ko/resources/benefits.mdx b/website/pages/ko/resources/benefits.mdx index 80e18ef87c62..8855efeab057 100644 --- a/website/pages/ko/resources/benefits.mdx +++ b/website/pages/ko/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/ko/subgraphs/cookbook/near.mdx b/website/pages/ko/subgraphs/cookbook/near.mdx index f2509e44e84c..8e0be3f5ce4e 100644 --- a/website/pages/ko/subgraphs/cookbook/near.mdx +++ b/website/pages/ko/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx index 282c68973a8a..86686025b089 100644 --- a/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ko/subgraphs/querying/introduction.mdx b/website/pages/ko/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/ko/subgraphs/querying/introduction.mdx +++ b/website/pages/ko/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ko/substreams/sps/sps-faq.mdx b/website/pages/ko/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/ko/substreams/sps/sps-faq.mdx +++ b/website/pages/ko/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/mr/indexing/chain-integration-overview.mdx b/website/pages/mr/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/mr/indexing/chain-integration-overview.mdx +++ b/website/pages/mr/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/mr/resources/benefits.mdx b/website/pages/mr/resources/benefits.mdx index 50102fc70729..0eee99651335 100644 --- a/website/pages/mr/resources/benefits.mdx +++ b/website/pages/mr/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy तळ ओळ: ग्राफ नेटवर्क कमी खर्चिक आहे, वापरण्यास सोपे आहे आणि स्थानिक पातळीवर `ग्राफ-नोड` चालवण्याच्या तुलनेत उत्कृष्ट परिणाम देते. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/mr/subgraphs/cookbook/near.mdx b/website/pages/mr/subgraphs/cookbook/near.mdx index efd00f148a8f..f91dad13e7b0 100644 --- a/website/pages/mr/subgraphs/cookbook/near.mdx +++ b/website/pages/mr/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ NEARサブグラフの「保留中」機能はまだサポートされていま ### माझा प्रश्न उत्तर दिला नाही, NEAR सबग्राफ तयार करण्यासाठी अधिक मदत कुठे मिळेल? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## संदर्भ diff --git a/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx index 7c50a40e48fd..8c243e1ec972 100644 --- a/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | आवृत्ती | रिलीझ नोट्स | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/mr/subgraphs/querying/introduction.mdx b/website/pages/mr/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/mr/subgraphs/querying/introduction.mdx +++ b/website/pages/mr/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/mr/substreams/sps/sps-faq.mdx b/website/pages/mr/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/mr/substreams/sps/sps-faq.mdx +++ b/website/pages/mr/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/nl/indexing/chain-integration-overview.mdx b/website/pages/nl/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/nl/indexing/chain-integration-overview.mdx +++ b/website/pages/nl/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/nl/resources/benefits.mdx b/website/pages/nl/resources/benefits.mdx index 3c8d31ec132f..3e66d7793f22 100644 --- a/website/pages/nl/resources/benefits.mdx +++ b/website/pages/nl/resources/benefits.mdx @@ -89,4 +89,4 @@ Het gedecentraliseerde netwerk van The Graph biedt gebruikers toegang tot geogra Samenvattend: Het Graph Network is goedkoper, gemakkelijker te gebruiken en levert superieure resultaten in vergelijking met het lokaal hosten van een `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/nl/subgraphs/cookbook/near.mdx b/website/pages/nl/subgraphs/cookbook/near.mdx index 46090338ae0d..4bbca2713b73 100644 --- a/website/pages/nl/subgraphs/cookbook/near.mdx +++ b/website/pages/nl/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx index a23e14babbb2..d403f2138eb8 100644 --- a/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/nl/subgraphs/querying/introduction.mdx b/website/pages/nl/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/nl/subgraphs/querying/introduction.mdx +++ b/website/pages/nl/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/nl/substreams/sps/sps-faq.mdx b/website/pages/nl/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/nl/substreams/sps/sps-faq.mdx +++ b/website/pages/nl/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/pl/indexing/chain-integration-overview.mdx b/website/pages/pl/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/pl/indexing/chain-integration-overview.mdx +++ b/website/pages/pl/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/pl/resources/benefits.mdx b/website/pages/pl/resources/benefits.mdx index 7416ff6346fe..8875be34a834 100644 --- a/website/pages/pl/resources/benefits.mdx +++ b/website/pages/pl/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/pl/subgraphs/cookbook/near.mdx b/website/pages/pl/subgraphs/cookbook/near.mdx index f2509e44e84c..8e0be3f5ce4e 100644 --- a/website/pages/pl/subgraphs/cookbook/near.mdx +++ b/website/pages/pl/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx index 37a742e7c78a..2bd046a9e605 100644 --- a/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/pl/subgraphs/querying/introduction.mdx b/website/pages/pl/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/pl/subgraphs/querying/introduction.mdx +++ b/website/pages/pl/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/pl/substreams/sps/sps-faq.mdx b/website/pages/pl/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/pl/substreams/sps/sps-faq.mdx +++ b/website/pages/pl/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx b/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx index 873be7d055ef..02e7092afd1b 100644 --- a/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx @@ -77,4 +77,4 @@ O bridge foi [auditado rigorosamente](https://code4rena.com/contests/2022-10-the A adição de GRT ao seu saldo de cobrança no Arbitrum pode ser feito em apenas um clique no [Subgraph Studio](https://thegraph.com/studio/). Você poderá fazer o bridge do seu GRT ao Arbitrum com facilidade, e preencher as suas chaves de API em uma única transação. -Visite a página de [Cobranças](/) para mais detalhes sobre como depositar, retirar, ou adquirir GRT. +Visite a página de [Cobranças](//) para mais detalhes sobre como depositar, retirar, ou adquirir GRT. diff --git a/website/pages/pt/indexing/chain-integration-overview.mdx b/website/pages/pt/indexing/chain-integration-overview.mdx index 6b239622281f..c03cd35fc70c 100644 --- a/website/pages/pt/indexing/chain-integration-overview.mdx +++ b/website/pages/pt/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Um processo de integração transparente e baseado em governança foi desenhado ## Fase 1. Integração Técnica -- Por favor, visite a página de [Integração de Novas Chains](/new-chain-integration) para informações sobre o apoio do `graph-node` para chains novas. +- Por favor, visite a página de [Integração de Novas Chains](/new-chain-integration/) para informações sobre o apoio do `graph-node` para chains novas. - Equipas iniciam o processo de integração de protocolo com a criação de um tópico de Fórum [aqui](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Nova subcategoria de Fontes de Dados sob Governança e GIPs). O uso do modelo padrão do Fórum é obrigatório. ## Fase 2. Validação de Integração diff --git a/website/pages/pt/resources/benefits.mdx b/website/pages/pt/resources/benefits.mdx index ff04d9e965ce..8bdc4445ed97 100644 --- a/website/pages/pt/resources/benefits.mdx +++ b/website/pages/pt/resources/benefits.mdx @@ -90,4 +90,4 @@ A rede descentralizada do The Graph permite que os utilizadores acessem redundâ Enfim: A Graph Network é mais barata e fácil de usar, e produz resultados superiores comparados à execução local de um `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/pt/subgraphs/cookbook/near.mdx b/website/pages/pt/subgraphs/cookbook/near.mdx index 1b7c1254531f..a08c08d3f056 100644 --- a/website/pages/pt/subgraphs/cookbook/near.mdx +++ b/website/pages/pt/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ No momento, não há apoio à funcionalidade de pendências para subgraphs na NE ### A minha pergunta não foi respondida. Onde posso conseguir mais ajuda sobre construir subgraphs na NEAR? -Se esta for uma pergunta geral sobre desenvolvimento de subgraphs, há mais informações no resto da [documentação para programadores](/quick-start). Caso contrário, entre no [Discord do Graph Protocol](https://discord.gg/graphprotocol) e pergunte no canal #near, ou mande a sua pergunta para near@thegraph.com. +Se esta for uma pergunta geral sobre desenvolvimento de subgraphs, há mais informações no resto da [documentação para programadores](/quick-start/). Caso contrário, entre no [Discord do Graph Protocol](https://discord.gg/graphprotocol) e pergunte no canal #near, ou mande a sua pergunta para near@thegraph.com. ## Referências diff --git a/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx index c32be10aeab8..684af3b191be 100644 --- a/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Subgraphs movidos por substreams --- -[Substreams](/substreams) é uma nova infraestrutura para o processamento de dados na blockchain, desenvolvida pela StreamingFast para a Graph Network. Um módulo de substreams pode gerar mudanças de entidade, que são compatíveis com entidades de Subgraph. Um subgraph pode usar um tal modelo de Substreams como uma fonte de dados, trazendo a velocidade de indexação e dados adicionais do Substreams aos desenvolvedores de subgraph. +[Substreams](/substreams/) é uma nova infraestrutura para o processamento de dados na blockchain, desenvolvida pela StreamingFast para a Graph Network. Um módulo de substreams pode gerar mudanças de entidade, que são compatíveis com entidades de Subgraph. Um subgraph pode usar um tal modelo de Substreams como uma fonte de dados, trazendo a velocidade de indexação e dados adicionais do Substreams aos desenvolvedores de subgraph. ## Requisitos @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Como definir um pacote de Substreams -Um pacote de Substreams é composto de tipos (definidos como [Protocol Buffers](https://protobuf.dev/)), módulos (escritos em Rust), e um arquivo `substreams.yaml` que referencia os tipos, e especifica como os módulos são ativados. [Visite a documentação de Substreams para aprender mais sobre o desenvolvimento de Substreams](/substreams), e confira o [awesome-substreams](https://github.com/pinax-network/awesome-substreams) e o [manual de Substreams](https://github.com/pinax-network/substreams-cookbook) para mais exemplos. +Um pacote de Substreams é composto de tipos (definidos como [Protocol Buffers](https://protobuf.dev/)), módulos (escritos em Rust), e um arquivo `substreams.yaml` que referencia os tipos, e especifica como os módulos são ativados. [Visite a documentação de Substreams para aprender mais sobre o desenvolvimento de Substreams](/substreams/), e confira o [awesome-substreams](https://github.com/pinax-network/awesome-substreams) e o [manual de Substreams](https://github.com/pinax-network/substreams-cookbook) para mais exemplos. O pacote de Substreams em questão deteta publicações de contratos na Mainnet do Ethereum, com rastreio do bloco de criação e horas para todos os contratos recém-lançados. Para fazer isto, há um tipo dedicado de `Contrato` no `/proto/example.proto` ([aprenda mais sobre a definição de Buffers de Protocolo](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx index 5a1bf2c57245..213d9736033c 100644 --- a/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Os arquivos da ABI devem combinar com o(s) seu(s) contrato(s). Há algumas manei | Versão | Notas de atualização | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/pt/subgraphs/querying/introduction.mdx b/website/pages/pt/subgraphs/querying/introduction.mdx index ae925ba0856a..2d0922e65ff6 100644 --- a/website/pages/pt/subgraphs/querying/introduction.mdx +++ b/website/pages/pt/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Aprenda mais sobre queries de um aplicativo [aqui](/querying/querying-from-an-ap Como deve ter percebido, este URL de query deve usar uma chave de API singular. Dá para criar e gerir as suas chaves de API no [Subgraph Studio](https://thegraph.com/studio), na seção "API Keys". Leia mais sobre como usar o Subgraph Studio [aqui](/deploying/subgraph-studio). -Utilizadores do Subgraph Studio começam com um Plano Grátis, que os permite realizar 100 mil queries por mês. Mais queries estão disponíveis no Plano de Crescimento, que oferece preços baseados em uso para queries adicionais; estes podem ser pagos em cartão de crédito ou em GRT no Arbitrum. Aprenda mais sobre cobranças [aqui](/billing). +Utilizadores do Subgraph Studio começam com um Plano Grátis, que os permite realizar 100 mil queries por mês. Mais queries estão disponíveis no Plano de Crescimento, que oferece preços baseados em uso para queries adicionais; estes podem ser pagos em cartão de crédito ou em GRT no Arbitrum. Aprenda mais sobre cobranças [aqui](/billing/). diff --git a/website/pages/pt/substreams/sps/sps-faq.mdx b/website/pages/pt/substreams/sps/sps-faq.mdx index 5fc4b8f0c2f6..ffa5233d7b61 100644 --- a/website/pages/pt/substreams/sps/sps-faq.mdx +++ b/website/pages/pt/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Perguntas frequentes sobre subgraphs movidos por substreams Desenvolvido pela [StreamingFast](https://www.streamingfast.io/), o Substreams é um motor de processamento de poder excepcional, capaz de consumir fluxos ricos de dados em blockchain. O Substreams lhe permite refinar e moldar dados em blockchain para serem digeridos rápida e suavemente por aplicativos de utilizador final. Mais especificamente, o Substreams é um motor paralelizado e agnóstico a blockchains, que põe transmissões em primeiro lugar e serve como uma camada de transformação de dados em blockchain. Movido pelo [Firehose](https://firehose.streamingfast.io/), ele permite que programadores escrevam módulos em Rust, construam sobre módulos da comunidade, providenciem indexações de altíssimo desempenho, e mandar seus dados para qualquer destino com [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink). -Vá à [Documentação do Substreams](/substreams) para aprender mais sobre Substreams. +Vá à [Documentação do Substreams](/substreams/) para aprender mais sobre Substreams. ## O que são subgraphs movidos por substreams? @@ -62,7 +62,7 @@ Há muitos benefícios do uso do Firehose, que incluem: ## Onde programadores podem acessar mais informações sobre Substreams e subgraphs movidos a Substreams? -A [documentação do Substreams](/substreams) lhe ensinará como construir módulos do Substreams. +A [documentação do Substreams](/substreams/) lhe ensinará como construir módulos do Substreams. A [documentação de subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) lhe ensinará como empacotá-los para a publicação no The Graph. diff --git a/website/pages/ro/indexing/chain-integration-overview.mdx b/website/pages/ro/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/ro/indexing/chain-integration-overview.mdx +++ b/website/pages/ro/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/ro/resources/benefits.mdx b/website/pages/ro/resources/benefits.mdx index 47216a1b6219..a26794b2abc1 100644 --- a/website/pages/ro/resources/benefits.mdx +++ b/website/pages/ro/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/ro/subgraphs/cookbook/near.mdx b/website/pages/ro/subgraphs/cookbook/near.mdx index f2509e44e84c..8e0be3f5ce4e 100644 --- a/website/pages/ro/subgraphs/cookbook/near.mdx +++ b/website/pages/ro/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx index 20748328de9e..7770743f9944 100644 --- a/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ro/subgraphs/querying/introduction.mdx b/website/pages/ro/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/ro/subgraphs/querying/introduction.mdx +++ b/website/pages/ro/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ro/substreams/sps/sps-faq.mdx b/website/pages/ro/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/ro/substreams/sps/sps-faq.mdx +++ b/website/pages/ro/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/ru/indexing/chain-integration-overview.mdx b/website/pages/ru/indexing/chain-integration-overview.mdx index 8f95b3db17f2..46dccce2a11a 100644 --- a/website/pages/ru/indexing/chain-integration-overview.mdx +++ b/website/pages/ru/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: Chain Integration Process Overview ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/ru/resources/benefits.mdx b/website/pages/ru/resources/benefits.mdx index 809d32f249df..0def249bbf4e 100644 --- a/website/pages/ru/resources/benefits.mdx +++ b/website/pages/ru/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Итог: Сеть Graph дешевле, проще в использовании и дает превосходные результаты по сравнению с запуском `graph-node` локально. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/ru/subgraphs/cookbook/near.mdx b/website/pages/ru/subgraphs/cookbook/near.mdx index f462d71a036a..5badca17ae9b 100644 --- a/website/pages/ru/subgraphs/cookbook/near.mdx +++ b/website/pages/ru/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ accounts: ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## Ссылки diff --git a/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx index a3a3f9e92200..f81b1674eda3 100644 --- a/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Субграфы, работающие на основе субпотоков (Substreams) --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Требования @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Определение пакета субпотоков -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. Рассматриваемый пакет Substreams обнаруживает развертывания контрактов в основной сети Ethereum, отслеживая блок создания и временную метку для всех вновь развернутых контрактов. Для этого в `/proto/example.proto` есть специальный тип `Contract` ([узнайте больше об определении Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx index 69757f55a845..cf29b952bd77 100644 --- a/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | Версия | Примечания к релизу | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ru/subgraphs/querying/introduction.mdx b/website/pages/ru/subgraphs/querying/introduction.mdx index 230016e09682..58e40dbe8c06 100644 --- a/website/pages/ru/subgraphs/querying/introduction.mdx +++ b/website/pages/ru/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ru/substreams/sps/sps-faq.mdx b/website/pages/ru/substreams/sps/sps-faq.mdx index 4d6d97dd686f..bfe5ac6af46d 100644 --- a/website/pages/ru/substreams/sps/sps-faq.mdx +++ b/website/pages/ru/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Часто задаваемые вопросы о субграфах, р Substreams (Субпотоки), разработанные [StreamingFast](https://www.streamingfast.io/), представляют собой исключительно мощный механизм обработки, способный потреблять обширные потоки блокчейн-данных. Субпотоки позволяют оптимизировать и формировать данные блокчейна для быстрого и бесперебойного использования приложениями конечных пользователей. В частности, Субпотоки - это независимый от блокчейна, распараллеленный и ориентированный на потоковую передачу движок, служащий в качестве уровня преобразования данных блокчейна. Работая на базе [Firehose](https://firehose.streamingfast.io), он позволяет разработчикам писать модули на языке Rust, использовать модули сообщества,обеспечивать крайне высокую производительность индексирования и [отправлять](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) свои данные в любое место. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## Что такое субграфы, работающие на основе Субпотоков? @@ -62,7 +62,7 @@ Firehose, разработанный [StreamingFast](https://www.streamingfast.i ## Где разработчики могут получить доступ к дополнительной информации о субграфах работающих на основе Субпотоков и о Субпотоках? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. В документации [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) показано, как упаковать их для развертывания в The Graph. diff --git a/website/pages/sv/indexing/chain-integration-overview.mdx b/website/pages/sv/indexing/chain-integration-overview.mdx index 5a81ed695be7..61050d78bd3e 100644 --- a/website/pages/sv/indexing/chain-integration-overview.mdx +++ b/website/pages/sv/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ En transparent och styrbaserad integrationsprocess utformades för blockchain-te ## Fas 1. Teknisk Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Team startar protokollintegrationsprocessen genom att skapa en Forumtråd [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Ny Datakällor underkategori under Governance & GIPs). Att använda standardforummallen är obligatoriskt. ## Fas 2. Integrationsvalidering diff --git a/website/pages/sv/resources/benefits.mdx b/website/pages/sv/resources/benefits.mdx index 2ad0e58e1e1b..0e8e42ee4eb8 100644 --- a/website/pages/sv/resources/benefits.mdx +++ b/website/pages/sv/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graphs decentraliserade nätverk ger användare tillgång till geografisk re Sammanfattningsvis är The Graph Nätverk mindre kostsamt, enklare att använda och ger överlägsna resultat jämfört med att köra en `graph-node` lokalt. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/sv/subgraphs/cookbook/near.mdx b/website/pages/sv/subgraphs/cookbook/near.mdx index 78fb45077df5..4c3c34017cb9 100644 --- a/website/pages/sv/subgraphs/cookbook/near.mdx +++ b/website/pages/sv/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Väntande funktionalitet stöds ännu inte för NEAR subgrafer. Under tiden kan ### Min fråga har inte besvarats, var kan jag få mer hjälp med att bygga NEAR subgrafer? -Om det är en generell fråga om subgraffutveckling finns det mycket mer information i resten av [Utvecklardokumentationen](/quick-start). Annars, var vänlig och anslut dig till [The Graph Protocol Discord](https://discord.gg/graphprotocol) och ställ din fråga i kanalen #near eller skicka ett e-postmeddelande till near@thegraph.com. +Om det är en generell fråga om subgraffutveckling finns det mycket mer information i resten av [Utvecklardokumentationen](/quick-start/). Annars, var vänlig och anslut dig till [The Graph Protocol Discord](https://discord.gg/graphprotocol) och ställ din fråga i kanalen #near eller skicka ett e-postmeddelande till near@thegraph.com. ## Referenser diff --git a/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 11e50bc3a8bd..34057468721c 100644 --- a/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-drivna subgrafer --- -[Substreams](/substreams) är en ny ramverk för att behandla blockkedjedata som utvecklats av StreamingFast för The Graph Network. Ett Substreams-modul kan generera ändringar i entiteter som är kompatibla med Subgraph-entiteter. En subgraf kan använda en sådan Substreams-modul som en datakälla och därmed ta del av Substreams indexeringshastighet och ytterligare data för subgrafutvecklare. +[Substreams](/substreams/) är en ny ramverk för att behandla blockkedjedata som utvecklats av StreamingFast för The Graph Network. Ett Substreams-modul kan generera ändringar i entiteter som är kompatibla med Subgraph-entiteter. En subgraf kan använda en sådan Substreams-modul som en datakälla och därmed ta del av Substreams indexeringshastighet och ytterligare data för subgrafutvecklare. ## Krav @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Definiera ett Substreams-paket -En Substreams-paket består av typer (definierade som [Protocol Buffers](https://protobuf.dev/)), moduler (skrivna i Rust) och en `substreams.yaml`-fil som refererar till typerna och specificerar hur modulerna utlöses. [Besök Substreams-dokumentationen för att lära dig mer om Substreams-utveckling](/substreams), och kolla in [awesome-substreams](https://github.com/pinax-network/awesome-substreams) och [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) för fler exempel. +En Substreams-paket består av typer (definierade som [Protocol Buffers](https://protobuf.dev/)), moduler (skrivna i Rust) och en `substreams.yaml`-fil som refererar till typerna och specificerar hur modulerna utlöses. [Besök Substreams-dokumentationen för att lära dig mer om Substreams-utveckling](/substreams/), och kolla in [awesome-substreams](https://github.com/pinax-network/awesome-substreams) och [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) för fler exempel. Substreams-paketet i fråga upptäcker kontraktsdistributioner på Mainnet Ethereum, spårar skapandeblocket och tidsstämpeln för alla nyligen distribuerade kontrakt. För att göra detta finns det en dedikerad "kontrakt"-typ i "/proto/example.proto" ([läs mer om att definiera protokollbuffertar](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx index 8166fa4088c1..59cb02ffa61c 100644 --- a/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI-filerna måste matcha ditt/dina kontrakt. Det finns några olika sätt att f | Version | Versionsanteckningar | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/sv/subgraphs/querying/introduction.mdx b/website/pages/sv/subgraphs/querying/introduction.mdx index 6d6618616eb2..d46760aa79a2 100644 --- a/website/pages/sv/subgraphs/querying/introduction.mdx +++ b/website/pages/sv/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/sv/substreams/sps/sps-faq.mdx b/website/pages/sv/substreams/sps/sps-faq.mdx index 4bca0c8caada..da63b9843a9b 100644 --- a/website/pages/sv/substreams/sps/sps-faq.mdx +++ b/website/pages/sv/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Vanliga frågor om Substreams-drivna subgrafer Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Gå till [Substreams Documentation](/substreams) för att lära dig mer om Substreams. +Gå till [Substreams Documentation](/substreams/) för att lära dig mer om Substreams. ## Vad är Substreams-drivna subgrafer? @@ -62,7 +62,7 @@ Det finns många fördelar med att använda Firehose, inklusive: ## Var kan utvecklare få mer information om Substreams-drivna subgrafer och Substreams? -[Substreams-dokumentationen](/substreams) kommer att lära dig hur du bygger Substreams-moduler. +[Substreams-dokumentationen](/substreams/) kommer att lära dig hur du bygger Substreams-moduler. [Substreams-drivna subgrafer dokumentationen](/cookbook/substreams-powered-subgraphs/) kommer att visa dig hur man paketerar dem för distribution på The Graph. diff --git a/website/pages/sw/indexing/chain-integration-overview.mdx b/website/pages/sw/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/sw/indexing/chain-integration-overview.mdx +++ b/website/pages/sw/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/sw/resources/benefits.mdx b/website/pages/sw/resources/benefits.mdx index 7b50daa789a4..13f1025e91f0 100644 --- a/website/pages/sw/resources/benefits.mdx +++ b/website/pages/sw/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/sw/subgraphs/cookbook/near.mdx b/website/pages/sw/subgraphs/cookbook/near.mdx index f2509e44e84c..8e0be3f5ce4e 100644 --- a/website/pages/sw/subgraphs/cookbook/near.mdx +++ b/website/pages/sw/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx index 282c68973a8a..86686025b089 100644 --- a/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/sw/subgraphs/querying/introduction.mdx b/website/pages/sw/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/sw/subgraphs/querying/introduction.mdx +++ b/website/pages/sw/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/sw/substreams/sps/sps-faq.mdx b/website/pages/sw/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/sw/substreams/sps/sps-faq.mdx +++ b/website/pages/sw/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/tr/indexing/chain-integration-overview.mdx b/website/pages/tr/indexing/chain-integration-overview.mdx index 33a1cdb8a18c..1102a6a76af6 100644 --- a/website/pages/tr/indexing/chain-integration-overview.mdx +++ b/website/pages/tr/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Blok zinciri ekiplerinin [Graph protokolüyle entegrasyon](https://forum.thegrap ## Aşama 1. Teknik Entegrasyon -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Ekipler, protokol entegrasyon sürecini bir Forum başlığı oluşturarak başlatır [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Yönetişim ve GIP'ler altındaki Yeni Veri Kaynakları alt kategorisi). Varsayılan Forum şablonunun kullanılması zorunludur. ## Aşama 2. Entegrasyon Doğrulaması diff --git a/website/pages/tr/resources/benefits.mdx b/website/pages/tr/resources/benefits.mdx index 60bed9f2847a..67a3db14273b 100644 --- a/website/pages/tr/resources/benefits.mdx +++ b/website/pages/tr/resources/benefits.mdx @@ -89,4 +89,4 @@ Graph'ın merkeziyetsiz ağı, kullanıcılara bir `graph node`'unu kendi kendin Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/tr/subgraphs/cookbook/near.mdx b/website/pages/tr/subgraphs/cookbook/near.mdx index e55819a7d0e7..099acc649897 100644 --- a/website/pages/tr/subgraphs/cookbook/near.mdx +++ b/website/pages/tr/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Bekleme fonksiyonelliği henüz NEAR subgraphları için desteklenmemektedir. Bu ### Sorum yanıtlanmadı, NEAR subgraphları oluşturma konusunda nereden daha fazla yardım alabilirim? -Subgraph geliştirme hakkında genel bir soruysa, [Geliştirici dökümantasyonu'nun](/quick-start) geri kalanında çok daha fazla bilgi bulunmaktadır. Aksi durumda lütfen [The Graph Protocol Discord](https://discord.gg/graphprotocol) sunucusuna katılın ve #near kanalında sorunuzu sorun veya near@thegraph.com adresine e-posta gönderin. +Subgraph geliştirme hakkında genel bir soruysa, [Geliştirici dökümantasyonu'nun](/quick-start/) geri kalanında çok daha fazla bilgi bulunmaktadır. Aksi durumda lütfen [The Graph Protocol Discord](https://discord.gg/graphprotocol) sunucusuna katılın ve #near kanalında sorunuzu sorun veya near@thegraph.com adresine e-posta gönderin. ## Referanslar diff --git a/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 17a9a4189fb6..0ce0c9c29e08 100644 --- a/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams destekli subgraphlar --- -[Substreams](/substreams), Graph Ağı için StreamingFast tarafından geliştirilen bir blok zinciri verileri işleme çerçevesidir. Bir substreams modülü, subgraph varlıklarıyla uyumlu olan varlık değişiklikleri çıktısı verebilir. Bir subgraph, böyle bir Substreams modülünü veri kaynağı olarak kullanabilir ve Substreams'in indeksleme hızını ve ek verilerini subgraph geliştiricilere kazandırabilir. +[Substreams](/substreams/), Graph Ağı için StreamingFast tarafından geliştirilen bir blok zinciri verileri işleme çerçevesidir. Bir substreams modülü, subgraph varlıklarıyla uyumlu olan varlık değişiklikleri çıktısı verebilir. Bir subgraph, böyle bir Substreams modülünü veri kaynağı olarak kullanabilir ve Substreams'in indeksleme hızını ve ek verilerini subgraph geliştiricilere kazandırabilir. ## Gereksinimler @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Bir Substreams paketi tanımlama -Bir Substreams paketi tiplerden ([Protocol Buffers](https://protobuf.dev/) olarak tanımlanmış olanlar), modüllerden (Rust dilinde yazılmış), tiplere referans veren ve modüllerin nasıl tetikleneceğini belirten bir `substreams.yaml` dosyasından oluşur. [Substreams geliştirme hakkında daha fazla bilgi edinmek için Substreams dökümantasyonunu ziyaret edin](/substreams) ve daha fazla örnek için [awesome-substreams](https://github.com/pinax-network/awesome-substreams) ve [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) sayfalarına göz atın. +Bir Substreams paketi tiplerden ([Protocol Buffers](https://protobuf.dev/) olarak tanımlanmış olanlar), modüllerden (Rust dilinde yazılmış), tiplere referans veren ve modüllerin nasıl tetikleneceğini belirten bir `substreams.yaml` dosyasından oluşur. [Substreams geliştirme hakkında daha fazla bilgi edinmek için Substreams dökümantasyonunu ziyaret edin](/substreams/) ve daha fazla örnek için [awesome-substreams](https://github.com/pinax-network/awesome-substreams) ve [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) sayfalarına göz atın. Bahsi geçen Substreams paketi, Ethereum Ana Ağı'nda kontrat dağıtımlarını algılar ve yeni oluşturulan kontratlar için oluşturma bloğunu ve zaman damgasını takip eder. Bunun için `/proto/example.proto` içinde buna özel bir `Contract` türü bulunmaktadır ([Protokol Buffers tanımlama hakkında daha fazla bilgi edinin](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx index 6b0ed88435dc..31c275b45dbf 100644 --- a/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI dosya(lar)ı sözleşme(ler) inizle uygun olmalıdır. ABI dosyalarını edi | Sürüm | Sürüm Notları | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/tr/subgraphs/querying/introduction.mdx b/website/pages/tr/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/tr/subgraphs/querying/introduction.mdx +++ b/website/pages/tr/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/tr/substreams/sps/sps-faq.mdx b/website/pages/tr/substreams/sps/sps-faq.mdx index 008fc7ecef4a..8192ebdfa52a 100644 --- a/website/pages/tr/substreams/sps/sps-faq.mdx +++ b/website/pages/tr/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams destekli subgraphlar SSS [StreamingFast](https://www.streamingfast.io/) tarafından geliştirilen Substreams, zengin blokzinciri veri akışlarını işleyebilen son derece güçlü bir işlem motorudur. Substreams, blokzinciri verilerini son kullanıcı uygulamaları tarafından hızlı ve sorunsuz bir şekilde işlenmek üzere rafine etmenizi ve şekillendirmenizi sağlar. Daha spesifik olmak gerekirse, Substreams, farklı blokzincirleriyle uyumlu, paralelleştirilmiş ve akış öncelikli bir motor olup bir blokzinciri veri dönüşüm katmanı olarak işlev görür. [Firehose](https://firehose.streamingfast.io/) tarafından desteklenen Substreams, geliştiricilerin Rust modülleri yazmasına, topluluk modüllerini kullanarak geliştirme yapmasına, son derece yüksek performanslı endeksleme sağlamasına ve verilerini herhangi bir yere yönlendirmesine ([sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink)) olanak tanır. -Substreams hakkında daha fazla bilgi için [SubstreamsDökümantasyonuna](/substreams) gidin. +Substreams hakkında daha fazla bilgi için [SubstreamsDökümantasyonuna](/substreams/) gidin. ## Substreams destekli subgraphlar nelerdir? @@ -62,7 +62,7 @@ Firehose kullanmanın birçok faydası vardır, bunlar şunlardır: ## Geliştiriciler, Substreams destekli subgraphlar ve Substreams hakkında daha fazla bilgiye nereden erişebilir geliştiriciler? -[Substreams dökümantasyonu](/substreams), Substreams modülleri nasıl oluşturulacağını öğretecektir. +[Substreams dökümantasyonu](/substreams/), Substreams modülleri nasıl oluşturulacağını öğretecektir. [Substreams destekli subgrahplar belgeleri](/cookbook/substreams-powered-subgraphs/), onları Graph üzerinde dağıtmak için nasıl paketleyeceğinizi gösterecektir. diff --git a/website/pages/uk/indexing/chain-integration-overview.mdx b/website/pages/uk/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/uk/indexing/chain-integration-overview.mdx +++ b/website/pages/uk/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/uk/resources/benefits.mdx b/website/pages/uk/resources/benefits.mdx index 2ab73dd7d7ba..32703068bd79 100644 --- a/website/pages/uk/resources/benefits.mdx +++ b/website/pages/uk/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/uk/subgraphs/cookbook/near.mdx b/website/pages/uk/subgraphs/cookbook/near.mdx index 3d72ba528304..44d653485491 100644 --- a/website/pages/uk/subgraphs/cookbook/near.mdx +++ b/website/pages/uk/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx index 0100b66c4427..0f6c7b45a843 100644 --- a/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/uk/subgraphs/querying/introduction.mdx b/website/pages/uk/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/uk/subgraphs/querying/introduction.mdx +++ b/website/pages/uk/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/uk/substreams/sps/sps-faq.mdx b/website/pages/uk/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/uk/substreams/sps/sps-faq.mdx +++ b/website/pages/uk/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/ur/indexing/chain-integration-overview.mdx b/website/pages/ur/indexing/chain-integration-overview.mdx index 6230099cd0f5..9e4c618c9e7b 100644 --- a/website/pages/ur/indexing/chain-integration-overview.mdx +++ b/website/pages/ur/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: چین انٹیگریشن کے عمل کا جائزہ ## مرحلہ 1. تکنیکی انٹیگریشن -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - ٹیمیں فورم تھریڈ بنا کر پروٹوکول انٹیگریشن کا عمل شروع کرتی ہیں [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)(گورننس اور GIPs کے تحت نئے ڈیٹا ذرائع ذیلی زمرہ) ۔ پہلے سے طے شدہ فورم ٹیمپلیٹ کا استعمال لازمی ہے. ## مرحلہ 2۔ انٹیگریشن کی توثیق diff --git a/website/pages/ur/resources/benefits.mdx b/website/pages/ur/resources/benefits.mdx index 2597116aef61..0b17f2bb521d 100644 --- a/website/pages/ur/resources/benefits.mdx +++ b/website/pages/ur/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy نیچے کی سطر: گراف نیٹ ورک کم مہنگا ہے، استعمال میں آسان ہے، اور مقامی طور پر `graph-node` کو چلانے کے مقابلے میں بہتر نتائج پیدا کرتا ہے. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/ur/subgraphs/cookbook/near.mdx b/website/pages/ur/subgraphs/cookbook/near.mdx index 2ce706542d8c..52f99378c67c 100644 --- a/website/pages/ur/subgraphs/cookbook/near.mdx +++ b/website/pages/ur/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ accounts: ### میرے سوال کا جواب نہیں دیا گیا ہے، مجھے NEAR سب گراف بنانے میں مزید مدد کہاں سے مل سکتی ہے؟ -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## حوالہ جات diff --git a/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 146c2228f6c6..20a8bfc21fbb 100644 --- a/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## سب سٹریمز پیکیج کی وضاحت کرنا -ایک سب سٹریمز پیکیج اقسام پر مشتمل ہے (جس کی وضاحت [پروٹوکول بفرز](https://protobuf.dev/))، ماڈیولز (Rust میں لکھی گئی ہے)، اور ایک `substreams.yaml` فائل جو اقسام کا حوالہ دیتی ہے، اور یہ بتاتی ہے کہ ماڈیول کیسے ہیں متحرک ہیں. [سب سٹریمز ڈویلپمنٹ کے بارے میں مزید جاننے کے لیے سب سٹریمز کی دستاویزات دیکھیں](/substreams)، اور [wesome-substreams](https://github.com/pinax-network/awesome-substreams) اور [Substreams cookbook](https مزید مثالوں کے لیے://github.com/pinax-network/substreams-cookbook). +ایک سب سٹریمز پیکیج اقسام پر مشتمل ہے (جس کی وضاحت [پروٹوکول بفرز](https://protobuf.dev/))، ماڈیولز (Rust میں لکھی گئی ہے)، اور ایک `substreams.yaml` فائل جو اقسام کا حوالہ دیتی ہے، اور یہ بتاتی ہے کہ ماڈیول کیسے ہیں متحرک ہیں. [سب سٹریمز ڈویلپمنٹ کے بارے میں مزید جاننے کے لیے سب سٹریمز کی دستاویزات دیکھیں](/substreams/)، اور [wesome-substreams](https://github.com/pinax-network/awesome-substreams) اور [Substreams cookbook](https مزید مثالوں کے لیے://github.com/pinax-network/substreams-cookbook). زیر بحث سب اسٹریمز پیکیج مینیٹ ایتھیریم پر کنٹریکٹ کی تعیناتیوں کا پتہ لگاتا ہے، تمام نئے تعینات کردہ کنٹریکٹس کے لیے تخلیق بلاک اور ٹائم اسٹیمپ کا پتہ لگاتا ہے۔ ایسا کرنے کے لیے، `/proto/example.proto` ([پروٹوکول بفرز کی تعریف کرنے کے بارے میں مزید جانیں](https://protobuf.dev/programming-guides/proto3/#simple)) میں ایک مخصوص `Contract` قسم ہے: diff --git a/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx index 118eeea3c5f3..987231f87e72 100644 --- a/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI فائل (فائلیں) آپ کے کنٹریکٹ (کنٹریکٹس) سے م | ورزن | جاری کردہ نوٹس | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ur/subgraphs/querying/introduction.mdx b/website/pages/ur/subgraphs/querying/introduction.mdx index 3228643fd71c..518951ee621b 100644 --- a/website/pages/ur/subgraphs/querying/introduction.mdx +++ b/website/pages/ur/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ur/substreams/sps/sps-faq.mdx b/website/pages/ur/substreams/sps/sps-faq.mdx index d00028321854..5ff4bd0509eb 100644 --- a/website/pages/ur/substreams/sps/sps-faq.mdx +++ b/website/pages/ur/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: سب اسٹریمز سے چلنے والے سب گرافس FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -سب سٹریمز کے بارے میں مزید جاننے کے لیے [سب سٹریمز دستاویزات](/substreams) پر جائیں. +سب سٹریمز کے بارے میں مزید جاننے کے لیے [سب سٹریمز دستاویزات](/substreams/) پر جائیں. ## سب سٹریمز سے چلنے والے سب گرافس کیا ہیں؟ @@ -62,7 +62,7 @@ Firehose استعمال کرنے کے بہت سے فوائد ہیں، بشمول ## ڈویلپرز سب سٹریمز سے چلنے والے سب گرافس اور سب سٹریمز کے بارے میں مزید معلومات کہاں تک رسائی حاصل کرسکتے ہیں؟ -[سب سٹریمز دستاویزات](/substreams) آپ کو سکھائے گا کہ سب سٹریمز کے ماڈیول کیسے بنائے جائیں. +[سب سٹریمز دستاویزات](/substreams/) آپ کو سکھائے گا کہ سب سٹریمز کے ماڈیول کیسے بنائے جائیں. [سب سٹریمز سے چلنے والے سب گرافس کے دستاویزات](/cookbook/substreams-powered-subgraphs/) آپ کو دکھائے گا کہ انہیں گراف پر تعیناتی کے لیے کیسے پیک کیا جائے. diff --git a/website/pages/vi/indexing/chain-integration-overview.mdx b/website/pages/vi/indexing/chain-integration-overview.mdx index a142f3f817f9..280d97bc2aa4 100644 --- a/website/pages/vi/indexing/chain-integration-overview.mdx +++ b/website/pages/vi/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/vi/resources/benefits.mdx b/website/pages/vi/resources/benefits.mdx index 41f8bc870b9a..5636695d5931 100644 --- a/website/pages/vi/resources/benefits.mdx +++ b/website/pages/vi/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/vi/subgraphs/cookbook/near.mdx b/website/pages/vi/subgraphs/cookbook/near.mdx index 9f56cb19e152..bdfa4df2b176 100644 --- a/website/pages/vi/subgraphs/cookbook/near.mdx +++ b/website/pages/vi/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 8a7998c325f8..02bf475bf8ba 100644 --- a/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx index ce25fbcafc6d..20129d442bb4 100644 --- a/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | Phiên bản | Ghi chú phát hành | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/vi/subgraphs/querying/introduction.mdx b/website/pages/vi/subgraphs/querying/introduction.mdx index 1255e0e88a51..b5ea795a934f 100644 --- a/website/pages/vi/subgraphs/querying/introduction.mdx +++ b/website/pages/vi/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/vi/substreams/sps/sps-faq.mdx b/website/pages/vi/substreams/sps/sps-faq.mdx index 92c6a8313a5f..5fd8082aeac1 100644 --- a/website/pages/vi/substreams/sps/sps-faq.mdx +++ b/website/pages/vi/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## What are Substreams-powered subgraphs? @@ -62,7 +62,7 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. diff --git a/website/pages/zh/indexing/chain-integration-overview.mdx b/website/pages/zh/indexing/chain-integration-overview.mdx index e8ee7d47ad02..cffb628a8983 100644 --- a/website/pages/zh/indexing/chain-integration-overview.mdx +++ b/website/pages/zh/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: 链集成过程概述 ## 阶段1：技术集成 -- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. - 团队通过在[here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)（治理与GIPs下的新数据源子类别）创建一个论坛帖子来启动协议集成过程。强制使用默认的论坛模板。 ## 阶段2：集成验证 diff --git a/website/pages/zh/resources/benefits.mdx b/website/pages/zh/resources/benefits.mdx index e9170c43c645..09f7a8fdf07e 100644 --- a/website/pages/zh/resources/benefits.mdx +++ b/website/pages/zh/resources/benefits.mdx @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy 一句话: 与在本地运行一个`graph-node`相比，Graph网络成本更低，更容易使用，并且产生更好的结果。 -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). diff --git a/website/pages/zh/subgraphs/cookbook/near.mdx b/website/pages/zh/subgraphs/cookbook/near.mdx index 25598b11f46d..f166aa66e611 100644 --- a/website/pages/zh/subgraphs/cookbook/near.mdx +++ b/website/pages/zh/subgraphs/cookbook/near.mdx @@ -276,7 +276,7 @@ NEAR 子图尚不支持挂起的功能。 在此期间，您可以将新版本 ### 我的问题尚未得到解答，在哪里可以获得更多构建 NEAR 子图的帮助？ -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## 参考 diff --git a/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx index e59f46d04b23..9a8d3b2b610f 100644 --- a/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: 基于Substreams的子图 --- -[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## 要求 @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## 定义Substreams包 -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. 该Substreams包可以检测以太坊主网上的合约部署，并跟踪所有新部署合约的创建块和时间戳。为此，在/proto/example.proto中有一个专门的Contract类型（了解更多关于定义Protocol Buffers的信息[learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)）： diff --git a/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx index 9db4e62530b6..1258acc91021 100644 --- a/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI 文件必须与您的合约相匹配。 获取 ABI 文件的方法有以下 | 版本 | Release 说明 | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/zh/subgraphs/querying/introduction.mdx b/website/pages/zh/subgraphs/querying/introduction.mdx index de89bd6af491..d6f1f3d35b31 100644 --- a/website/pages/zh/subgraphs/querying/introduction.mdx +++ b/website/pages/zh/subgraphs/querying/introduction.mdx @@ -18,4 +18,4 @@ Learn more about querying from an application [here](/querying/querying-from-an- As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/zh/substreams/sps/sps-faq.mdx b/website/pages/zh/substreams/sps/sps-faq.mdx index 3a9a4b0fe654..e82db5a2ccae 100644 --- a/website/pages/zh/substreams/sps/sps-faq.mdx +++ b/website/pages/zh/substreams/sps/sps-faq.mdx @@ -6,7 +6,7 @@ title: 基于Substreams的子图 Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. ## 什么是基于Substreams的子图？ @@ -62,7 +62,7 @@ Firehose是由[StreamingFast](https://www.streamingfast.io/)开发的区块链 ## 开发人员在哪里可以获得关于Substreams-powered子图和Substreams的更多信息？ -The [Substreams documentation](/substreams) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) 将向您展示如何将它们打包部署在The Graph上。 From 8b2efdb1e7ee69b529604d93cd50cde38148162f Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 17:44:06 -0500 Subject: [PATCH 19/22] `on-chain` => `onchain` --- website/pages/en/indexing/tap.mdx | 2 +- website/pages/en/resources/glossary.mdx | 4 ++-- website/pages/en/resources/roles/curating.mdx | 2 +- website/pages/en/subgraphs/cookbook/cosmos.mdx | 2 +- .../subgraphs/developing/deploying/using-subgraph-studio.mdx | 4 ++-- website/pages/en/subgraphs/developing/subgraphs.mdx | 2 +- website/pages/en/substreams/sps/sps-faq.mdx | 4 ++-- 7 files changed, 10 insertions(+), 10 deletions(-) diff --git a/website/pages/en/indexing/tap.mdx b/website/pages/en/indexing/tap.mdx index 3e8185186982..3d6bbed374a9 100644 --- a/website/pages/en/indexing/tap.mdx +++ b/website/pages/en/indexing/tap.mdx @@ -9,7 +9,7 @@ Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, T [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features: - Efficiently handles micropayments. -- Adds a layer of consolidations to on-chain transactions and costs. +- Adds a layer of consolidations to onchain transactions and costs. - Allows Indexers control of receipts and payments, guaranteeing payment for queries. - It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders. diff --git a/website/pages/en/resources/glossary.mdx b/website/pages/en/resources/glossary.mdx index bdeff7281023..fa813b659730 100644 --- a/website/pages/en/resources/glossary.mdx +++ b/website/pages/en/resources/glossary.mdx @@ -42,7 +42,7 @@ title: Glossary - **Allocation**: An Indexer can allocate their total GRT stake (including Delegators' stake) towards subgraphs that have been published on The Graph's decentralized network. Allocations can have different statuses: - 1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated. + 1. **Active**: An allocation is considered active when it is created onchain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated. 2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data. @@ -64,7 +64,7 @@ title: Glossary - **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer. -- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations. +- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions onchain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations. - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way. diff --git a/website/pages/en/resources/roles/curating.mdx b/website/pages/en/resources/roles/curating.mdx index a5a63f3e2751..f584117580ae 100644 --- a/website/pages/en/resources/roles/curating.mdx +++ b/website/pages/en/resources/roles/curating.mdx @@ -68,7 +68,7 @@ Finding high-quality subgraphs is a complex task, but it can be approached in ma ### 3. What’s the cost of updating a subgraph? -Migrating your curation shares to a new subgraph version incurs a curation tax of 1%. Curators can choose to subscribe to the newest version of a subgraph. When curator shares get auto-migrated to a new version, Curators will also pay half curation tax, ie. 0.5%, because upgrading subgraphs is an on-chain action that costs gas. +Migrating your curation shares to a new subgraph version incurs a curation tax of 1%. Curators can choose to subscribe to the newest version of a subgraph. When curator shares get auto-migrated to a new version, Curators will also pay half curation tax, ie. 0.5%, because upgrading subgraphs is an onchain action that costs gas. ### 4. How often can I update my subgraph? diff --git a/website/pages/en/subgraphs/cookbook/cosmos.mdx b/website/pages/en/subgraphs/cookbook/cosmos.mdx index cd23a3742f86..dfdb377688aa 100644 --- a/website/pages/en/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/en/subgraphs/cookbook/cosmos.mdx @@ -6,7 +6,7 @@ This guide is an introduction on building subgraphs indexing [Cosmos](https://co ## What are Cosmos subgraphs? -The Graph allows developers to process blockchain events and make the resulting data easily available via an open GraphQL API, known as a subgraph. [Graph Node](https://github.com/graphprotocol/graph-node) is now able to process Cosmos events, which means Cosmos developers can now build subgraphs to easily index on-chain events. +The Graph allows developers to process blockchain events and make the resulting data easily available via an open GraphQL API, known as a subgraph. [Graph Node](https://github.com/graphprotocol/graph-node) is now able to process Cosmos events, which means Cosmos developers can now build subgraphs to easily index onchain events. There are four types of handlers supported in Cosmos subgraphs: diff --git a/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx index 3835d29cf548..7ba8e8080254 100644 --- a/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -4,7 +4,7 @@ title: Deploying Using Subgraph Studio Learn how to deploy your subgraph to Subgraph Studio. -> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain. +> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it onchain. ## Subgraph Studio Overview @@ -124,7 +124,7 @@ If you want to update your subgraph, you can do the following: - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer). - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index. -You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. +You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an onchain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). diff --git a/website/pages/en/subgraphs/developing/subgraphs.mdx b/website/pages/en/subgraphs/developing/subgraphs.mdx index 42c1e806f822..1fdd0baf80eb 100644 --- a/website/pages/en/subgraphs/developing/subgraphs.mdx +++ b/website/pages/en/subgraphs/developing/subgraphs.mdx @@ -55,7 +55,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. +- This is an onchain 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-a-subgraph/) by sending the NFT. - Published subgraphs have associated metadata, which provides other network participants with useful context and information. diff --git a/website/pages/en/substreams/sps/sps-faq.mdx b/website/pages/en/substreams/sps/sps-faq.mdx index 0774edc32dea..ab0e8c4c7d2f 100644 --- a/website/pages/en/substreams/sps/sps-faq.mdx +++ b/website/pages/en/substreams/sps/sps-faq.mdx @@ -16,9 +16,9 @@ If you are already familiar with subgraph development, then note that Substreams ## How are Substreams-powered subgraphs different from subgraphs? -Subgraphs are made up of datasources which specify on-chain events, and how those events should be transformed via handlers written in Assemblyscript. These events are processed sequentially, based on the order in which events happen on-chain. +Subgraphs are made up of datasources which specify onchain events, and how those events should be transformed via handlers written in Assemblyscript. These events are processed sequentially, based on the order in which events happen onchain. -By contrast, substreams-powered subgraphs have a single datasource which references a substreams package, which is processed by the Graph Node. Substreams have access to additional granular on-chain data compared to conventional subgraphs, and can also benefit from massively parallelised processing, which can mean much faster processing times. +By contrast, substreams-powered subgraphs have a single datasource which references a substreams package, which is processed by the Graph Node. Substreams have access to additional granular onchain data compared to conventional subgraphs, and can also benefit from massively parallelised processing, which can mean much faster processing times. ## What are the benefits of using Substreams-powered subgraphs? From 743a6c5ea3d81a225a3db02c7ac7d220afec0349 Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 19:38:22 -0500 Subject: [PATCH 20/22] Actually ensure all links have a trailing slash --- website/pages/ar/archived/sunrise.mdx | 2 +- website/pages/ar/contracts.mdx | 2 +- .../pages/ar/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ar/indexing/overview.mdx | 10 +++++----- website/pages/ar/resources/benefits.mdx | 2 +- website/pages/ar/resources/roles/curating.mdx | 4 ++-- website/pages/ar/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/ar/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../ar/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/ar/subgraphs/explorer.mdx | 6 +++--- .../ar/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/ar/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/ar/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/ar/substreams/sps/introduction.mdx | 2 +- website/pages/ar/substreams/sps/triggers.mdx | 4 ++-- website/pages/ar/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/cs/archived/sunrise.mdx | 2 +- website/pages/cs/contracts.mdx | 2 +- .../pages/cs/indexing/new-chain-integration.mdx | 4 ++-- website/pages/cs/indexing/overview.mdx | 10 +++++----- website/pages/cs/resources/benefits.mdx | 2 +- website/pages/cs/resources/roles/curating.mdx | 4 ++-- website/pages/cs/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/cs/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../cs/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/cs/subgraphs/explorer.mdx | 6 +++--- .../cs/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/cs/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/cs/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/cs/substreams/sps/introduction.mdx | 2 +- website/pages/cs/substreams/sps/triggers.mdx | 4 ++-- website/pages/cs/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/de/archived/sunrise.mdx | 2 +- website/pages/de/contracts.mdx | 2 +- .../pages/de/indexing/new-chain-integration.mdx | 4 ++-- website/pages/de/indexing/overview.mdx | 10 +++++----- website/pages/de/resources/benefits.mdx | 2 +- website/pages/de/resources/roles/curating.mdx | 4 ++-- website/pages/de/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/de/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../de/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/de/subgraphs/explorer.mdx | 6 +++--- .../de/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/de/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/de/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/de/substreams/sps/introduction.mdx | 2 +- website/pages/de/substreams/sps/triggers.mdx | 4 ++-- website/pages/de/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/en/archived/sunrise.mdx | 2 +- website/pages/en/contracts.mdx | 2 +- .../pages/en/indexing/new-chain-integration.mdx | 4 ++-- website/pages/en/indexing/overview.mdx | 10 +++++----- website/pages/en/resources/benefits.mdx | 2 +- website/pages/en/resources/roles/curating.mdx | 4 ++-- website/pages/en/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/en/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../en/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/en/subgraphs/explorer.mdx | 6 +++--- .../en/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/en/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/en/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/en/substreams/sps/introduction.mdx | 2 +- website/pages/en/substreams/sps/triggers.mdx | 4 ++-- website/pages/en/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/es/archived/sunrise.mdx | 2 +- website/pages/es/contracts.mdx | 2 +- .../pages/es/indexing/new-chain-integration.mdx | 4 ++-- website/pages/es/indexing/overview.mdx | 10 +++++----- website/pages/es/resources/benefits.mdx | 2 +- website/pages/es/resources/roles/curating.mdx | 4 ++-- website/pages/es/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/es/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../es/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/es/subgraphs/explorer.mdx | 6 +++--- .../es/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/es/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/es/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/es/substreams/sps/introduction.mdx | 2 +- website/pages/es/substreams/sps/triggers.mdx | 4 ++-- website/pages/es/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/fr/archived/sunrise.mdx | 2 +- website/pages/fr/contracts.mdx | 2 +- .../pages/fr/indexing/new-chain-integration.mdx | 4 ++-- website/pages/fr/indexing/overview.mdx | 10 +++++----- website/pages/fr/resources/benefits.mdx | 2 +- website/pages/fr/resources/roles/curating.mdx | 4 ++-- website/pages/fr/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/fr/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 2 +- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../fr/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/fr/subgraphs/explorer.mdx | 6 +++--- .../fr/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/fr/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/fr/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/fr/substreams/sps/introduction.mdx | 2 +- website/pages/fr/substreams/sps/triggers.mdx | 4 ++-- website/pages/fr/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/hi/archived/sunrise.mdx | 2 +- website/pages/hi/contracts.mdx | 2 +- website/pages/hi/indexing/overview.mdx | 10 +++++----- website/pages/hi/resources/benefits.mdx | 2 +- website/pages/hi/resources/roles/curating.mdx | 4 ++-- website/pages/hi/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/hi/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../hi/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/hi/subgraphs/explorer.mdx | 6 +++--- .../hi/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/hi/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/hi/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/hi/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/it/archived/sunrise.mdx | 2 +- website/pages/it/contracts.mdx | 2 +- .../pages/it/indexing/new-chain-integration.mdx | 4 ++-- website/pages/it/indexing/overview.mdx | 10 +++++----- website/pages/it/resources/benefits.mdx | 2 +- website/pages/it/resources/roles/curating.mdx | 4 ++-- website/pages/it/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/it/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../it/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/it/subgraphs/explorer.mdx | 6 +++--- .../it/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/it/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/it/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/it/substreams/sps/introduction.mdx | 2 +- website/pages/it/substreams/sps/triggers.mdx | 4 ++-- website/pages/it/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ja/archived/sunrise.mdx | 2 +- website/pages/ja/contracts.mdx | 2 +- .../pages/ja/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ja/indexing/overview.mdx | 10 +++++----- website/pages/ja/resources/benefits.mdx | 2 +- website/pages/ja/resources/roles/curating.mdx | 4 ++-- website/pages/ja/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/ja/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 2 +- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../ja/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/ja/subgraphs/explorer.mdx | 6 +++--- .../ja/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/ja/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/ja/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/ja/substreams/sps/introduction.mdx | 2 +- website/pages/ja/substreams/sps/triggers.mdx | 4 ++-- website/pages/ja/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ko/archived/sunrise.mdx | 2 +- website/pages/ko/contracts.mdx | 2 +- .../pages/ko/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ko/indexing/overview.mdx | 10 +++++----- website/pages/ko/resources/benefits.mdx | 2 +- website/pages/ko/resources/roles/curating.mdx | 4 ++-- website/pages/ko/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/ko/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../ko/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/ko/subgraphs/explorer.mdx | 6 +++--- .../ko/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/ko/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/ko/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/ko/substreams/sps/introduction.mdx | 2 +- website/pages/ko/substreams/sps/triggers.mdx | 4 ++-- website/pages/ko/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/mr/archived/sunrise.mdx | 2 +- website/pages/mr/contracts.mdx | 2 +- .../pages/mr/indexing/new-chain-integration.mdx | 4 ++-- website/pages/mr/indexing/overview.mdx | 10 +++++----- website/pages/mr/resources/benefits.mdx | 2 +- website/pages/mr/resources/roles/curating.mdx | 4 ++-- website/pages/mr/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/mr/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../mr/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/mr/subgraphs/explorer.mdx | 6 +++--- .../mr/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/mr/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/mr/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/mr/substreams/sps/introduction.mdx | 2 +- website/pages/mr/substreams/sps/triggers.mdx | 4 ++-- website/pages/mr/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/nl/archived/sunrise.mdx | 2 +- website/pages/nl/contracts.mdx | 2 +- .../pages/nl/indexing/new-chain-integration.mdx | 4 ++-- website/pages/nl/indexing/overview.mdx | 10 +++++----- website/pages/nl/resources/benefits.mdx | 2 +- website/pages/nl/resources/roles/curating.mdx | 4 ++-- website/pages/nl/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/nl/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../nl/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/nl/subgraphs/explorer.mdx | 6 +++--- .../nl/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/nl/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/nl/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/nl/substreams/sps/introduction.mdx | 2 +- website/pages/nl/substreams/sps/triggers.mdx | 4 ++-- website/pages/nl/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/pl/archived/sunrise.mdx | 2 +- website/pages/pl/contracts.mdx | 2 +- .../pages/pl/indexing/new-chain-integration.mdx | 4 ++-- website/pages/pl/indexing/overview.mdx | 10 +++++----- website/pages/pl/resources/benefits.mdx | 2 +- website/pages/pl/resources/roles/curating.mdx | 4 ++-- website/pages/pl/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/pl/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../pl/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/pl/subgraphs/explorer.mdx | 6 +++--- .../pl/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/pl/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/pl/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/pl/substreams/sps/introduction.mdx | 2 +- website/pages/pl/substreams/sps/triggers.mdx | 4 ++-- website/pages/pl/supported-networks.mdx | 2 +- .../pages/pt/archived/arbitrum/arbitrum-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/pt/archived/sunrise.mdx | 2 +- website/pages/pt/contracts.mdx | 2 +- .../pages/pt/indexing/new-chain-integration.mdx | 4 ++-- website/pages/pt/indexing/overview.mdx | 10 +++++----- website/pages/pt/resources/benefits.mdx | 2 +- website/pages/pt/resources/roles/curating.mdx | 4 ++-- website/pages/pt/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/pt/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../pt/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/pt/subgraphs/explorer.mdx | 6 +++--- .../pt/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/pt/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/pt/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/pt/substreams/sps/introduction.mdx | 2 +- website/pages/pt/substreams/sps/triggers.mdx | 4 ++-- website/pages/pt/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ro/archived/sunrise.mdx | 2 +- website/pages/ro/contracts.mdx | 2 +- .../pages/ro/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ro/indexing/overview.mdx | 10 +++++----- website/pages/ro/resources/benefits.mdx | 2 +- website/pages/ro/resources/roles/curating.mdx | 4 ++-- website/pages/ro/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/ro/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../ro/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/ro/subgraphs/explorer.mdx | 6 +++--- .../ro/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/ro/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/ro/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/ro/substreams/sps/introduction.mdx | 2 +- website/pages/ro/substreams/sps/triggers.mdx | 4 ++-- website/pages/ro/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ru/archived/sunrise.mdx | 2 +- website/pages/ru/contracts.mdx | 2 +- .../pages/ru/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ru/indexing/overview.mdx | 10 +++++----- website/pages/ru/resources/benefits.mdx | 2 +- website/pages/ru/resources/roles/curating.mdx | 4 ++-- website/pages/ru/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/ru/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../ru/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/ru/subgraphs/explorer.mdx | 6 +++--- .../ru/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/ru/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/ru/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/ru/substreams/sps/introduction.mdx | 2 +- website/pages/ru/substreams/sps/triggers.mdx | 4 ++-- website/pages/ru/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/sv/archived/sunrise.mdx | 2 +- website/pages/sv/contracts.mdx | 2 +- .../pages/sv/indexing/new-chain-integration.mdx | 4 ++-- website/pages/sv/indexing/overview.mdx | 10 +++++----- website/pages/sv/resources/benefits.mdx | 2 +- website/pages/sv/resources/roles/curating.mdx | 4 ++-- website/pages/sv/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/sv/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../sv/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/sv/subgraphs/explorer.mdx | 6 +++--- .../sv/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/sv/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/sv/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/sv/substreams/sps/introduction.mdx | 2 +- website/pages/sv/substreams/sps/triggers.mdx | 4 ++-- website/pages/sv/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/sw/archived/sunrise.mdx | 2 +- website/pages/sw/contracts.mdx | 2 +- .../pages/sw/indexing/new-chain-integration.mdx | 4 ++-- website/pages/sw/indexing/overview.mdx | 10 +++++----- website/pages/sw/resources/benefits.mdx | 2 +- website/pages/sw/resources/roles/curating.mdx | 4 ++-- website/pages/sw/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/sw/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../sw/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/sw/subgraphs/explorer.mdx | 6 +++--- .../sw/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/sw/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/sw/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/sw/substreams/sps/introduction.mdx | 2 +- website/pages/sw/substreams/sps/triggers.mdx | 4 ++-- website/pages/sw/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/tr/archived/sunrise.mdx | 2 +- website/pages/tr/contracts.mdx | 2 +- .../pages/tr/indexing/new-chain-integration.mdx | 4 ++-- website/pages/tr/indexing/overview.mdx | 10 +++++----- website/pages/tr/resources/benefits.mdx | 2 +- website/pages/tr/resources/roles/curating.mdx | 4 ++-- website/pages/tr/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/tr/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../tr/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/tr/subgraphs/explorer.mdx | 6 +++--- .../tr/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/tr/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/tr/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/tr/substreams/sps/introduction.mdx | 2 +- website/pages/tr/substreams/sps/triggers.mdx | 4 ++-- website/pages/tr/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/uk/archived/sunrise.mdx | 2 +- website/pages/uk/contracts.mdx | 2 +- .../pages/uk/indexing/new-chain-integration.mdx | 4 ++-- website/pages/uk/indexing/overview.mdx | 10 +++++----- website/pages/uk/resources/benefits.mdx | 2 +- website/pages/uk/resources/roles/curating.mdx | 4 ++-- website/pages/uk/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/uk/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../uk/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/uk/subgraphs/explorer.mdx | 6 +++--- .../uk/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/uk/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/uk/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/uk/substreams/sps/introduction.mdx | 2 +- website/pages/uk/substreams/sps/triggers.mdx | 4 ++-- website/pages/uk/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ur/archived/sunrise.mdx | 2 +- website/pages/ur/contracts.mdx | 2 +- .../pages/ur/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ur/indexing/overview.mdx | 10 +++++----- website/pages/ur/resources/benefits.mdx | 2 +- .../graphql-validations-migration-guide.mdx | 2 +- website/pages/ur/resources/roles/curating.mdx | 4 ++-- website/pages/ur/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/ur/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 2 +- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../ur/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/ur/subgraphs/explorer.mdx | 6 +++--- .../ur/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/ur/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/ur/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/ur/substreams/sps/introduction.mdx | 2 +- website/pages/ur/substreams/sps/triggers.mdx | 4 ++-- website/pages/ur/supported-networks.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/vi/archived/sunrise.mdx | 2 +- website/pages/vi/contracts.mdx | 2 +- .../pages/vi/indexing/new-chain-integration.mdx | 4 ++-- website/pages/vi/indexing/overview.mdx | 10 +++++----- website/pages/vi/resources/benefits.mdx | 2 +- website/pages/vi/resources/roles/curating.mdx | 4 ++-- website/pages/vi/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/vi/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../vi/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/vi/subgraphs/explorer.mdx | 6 +++--- .../vi/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/vi/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/vi/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/vi/substreams/sps/introduction.mdx | 2 +- website/pages/vi/substreams/sps/triggers.mdx | 4 ++-- website/pages/vi/supported-networks.mdx | 2 +- website/pages/zh/archived/sunrise.mdx | 2 +- website/pages/zh/contracts.mdx | 2 +- .../pages/zh/indexing/new-chain-integration.mdx | 4 ++-- website/pages/zh/indexing/overview.mdx | 10 +++++----- website/pages/zh/resources/benefits.mdx | 2 +- website/pages/zh/resources/roles/curating.mdx | 4 ++-- website/pages/zh/subgraphs/cookbook/grafting.mdx | 2 +- website/pages/zh/subgraphs/cookbook/near.mdx | 16 ++++++++-------- .../developing/creating/graph-ts/api.mdx | 2 +- .../developing/creating/install-the-cli.mdx | 2 +- .../subgraphs/developing/creating/ql-schema.mdx | 2 +- .../developing/deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 2 +- .../zh/subgraphs/developing/developer-faq.mdx | 8 ++++---- .../publishing/publishing-a-subgraph.mdx | 14 +++++++------- website/pages/zh/subgraphs/explorer.mdx | 6 +++--- .../zh/subgraphs/querying/best-practices.mdx | 6 +++--- .../pages/zh/subgraphs/querying/graphql-api.mdx | 2 +- .../pages/zh/subgraphs/querying/introduction.mdx | 6 +++--- website/pages/zh/substreams/sps/introduction.mdx | 2 +- website/pages/zh/substreams/sps/triggers.mdx | 4 ++-- website/pages/zh/supported-networks.mdx | 2 +- 523 files changed, 1208 insertions(+), 1208 deletions(-) diff --git a/website/pages/ar/archived/sunrise.mdx b/website/pages/ar/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/ar/archived/sunrise.mdx +++ b/website/pages/ar/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ar/contracts.mdx b/website/pages/ar/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/ar/contracts.mdx +++ b/website/pages/ar/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ar/indexing/new-chain-integration.mdx b/website/pages/ar/indexing/new-chain-integration.mdx index 75df818160ce..28165d622980 100644 --- a/website/pages/ar/indexing/new-chain-integration.mdx +++ b/website/pages/ar/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Configuring Graph Node is as easy as preparing your local environment. Once your ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ar/indexing/overview.mdx b/website/pages/ar/indexing/overview.mdx index e5cb4d8ea17d..526bb472cee1 100644 --- a/website/pages/ar/indexing/overview.mdx +++ b/website/pages/ar/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### ابدأ -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### من حزم NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### استخدام K8s و Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### الاستخدام @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### اعتماد التوكن tokens diff --git a/website/pages/ar/resources/benefits.mdx b/website/pages/ar/resources/benefits.mdx index e29acaf1ac5f..83a655314638 100644 --- a/website/pages/ar/resources/benefits.mdx +++ b/website/pages/ar/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/ar/resources/roles/curating.mdx b/website/pages/ar/resources/roles/curating.mdx index 970b6fbbc405..a681000aa7e5 100644 --- a/website/pages/ar/resources/roles/curating.mdx +++ b/website/pages/ar/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## كيفية الإشارة -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) يمكن للمنسق الإشارة إلى إصدار معين ل subgraph ، أو يمكنه اختيار أن يتم ترحيل migrate إشاراتهم تلقائيا إلى أحدث إصدار لهذا ال subgraph. كلاهما استراتيجيات سليمة ولها إيجابيات وسلبيات. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. سوق الاستعلام يعتبر حديثا في The Graph وهناك خطر من أن يكون٪ APY الخاص بك أقل مما تتوقع بسبب ديناميكيات السوق الناشئة. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. يمكن أن يفشل ال subgraph بسبب خطأ. ال subgraph الفاشل لا يمكنه إنشاء رسوم استعلام. نتيجة لذلك ، سيتعين عليك الانتظار حتى يصلح المطور الخطأ وينشر إصدارا جديدا. - إذا كنت مشتركا في أحدث إصدار من subgraph ، فسيتم ترحيل migrate أسهمك تلقائيا إلى هذا الإصدار الجديد. هذا سيتحمل ضريبة تنسيق بنسبة 0.5٪. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ar/subgraphs/cookbook/grafting.mdx b/website/pages/ar/subgraphs/cookbook/grafting.mdx index 08c347c50a63..9f965cbf2814 100644 --- a/website/pages/ar/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ar/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [تطعيم(Grafting)](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [تطعيم(Grafting)](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/ar/subgraphs/cookbook/near.mdx b/website/pages/ar/subgraphs/cookbook/near.mdx index 8b4f6088b85c..87505b21adb9 100644 --- a/website/pages/ar/subgraphs/cookbook/near.mdx +++ b/website/pages/ar/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ title: بناء Subgraphs على NEAR **subgraph.yaml:** الـ subgraph manifest ، وتحديد مصادر البيانات ذات الأهمية ، وكيف يجب أن تتم معالجتها.علما أن 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). +**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/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. +**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: @@ -92,13 +92,13 @@ accounts: ### تعريف المخطط -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings تمت كتابة المعالجات(handlers) الخاصة بمعالجة الأحداث بـ[ AssemblyScript ](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx index 5517fefa4032..b18e9aa8f7fb 100644 --- a/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | الاصدار | ملاحظات الإصدار | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx index 20b4acef827a..4a7e49aaa5a6 100644 --- a/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ar/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/ar/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/ar/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/ar/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx index 3e357875b406..d626c7abbb22 100644 --- a/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - يجب ألا تستخدم أيًا من الميزات التالية: - ipfs.cat & ipfs.map - أخطاء غير فادحة diff --git a/website/pages/ar/subgraphs/developing/developer-faq.mdx b/website/pages/ar/subgraphs/developing/developer-faq.mdx index 01aa712bb83c..423e9f9561b7 100644 --- a/website/pages/ar/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ar/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ One possible alternative solution to this is to store raw data in entities and p Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 673160e705f0..7fcaff59788d 100644 --- a/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/ar/subgraphs/explorer.mdx b/website/pages/ar/subgraphs/explorer.mdx index 2024b24bcd1c..d9b262805cca 100644 --- a/website/pages/ar/subgraphs/explorer.mdx +++ b/website/pages/ar/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![نافذة تفاصيل الفهرسة](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![صورة المستكشف 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. المفوضون Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - كمية ال GRT التي يمتلكونها حاليا في البروتوكول - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/ar/subgraphs/querying/best-practices.mdx b/website/pages/ar/subgraphs/querying/best-practices.mdx index 48e8dec63a28..0b34069dbd23 100644 --- a/website/pages/ar/subgraphs/querying/best-practices.mdx +++ b/website/pages/ar/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - يجب استخدام كل `queryName` مرة واحدة فقط لكل عملية. - يجب استخدام كل `field` مرة واحدة فقط في التحديد (لا يمكننا الاستعلام عن `id` مرتين ضمن `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - يجب أن يكون أي متغير تم تعيينه لوسيط متطابقًا مع نوعه. - في قائمة المتغيرات المعطاة ، يجب أن يكون كل واحد منها فريدًا. - يجب استخدام جميع المتغيرات المحددة. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - التعامل مع ال subgraph عبر السلاسل: الاستعلام من عدة subgraphs عبر استعلام واحد - [تتبع الكتلة التلقائي](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/ar/subgraphs/querying/graphql-api.mdx b/website/pages/ar/subgraphs/querying/graphql-api.mdx index 9699c231d93b..3246e4ab97d6 100644 --- a/website/pages/ar/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ar/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/ar/subgraphs/querying/introduction.mdx b/website/pages/ar/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/ar/subgraphs/querying/introduction.mdx +++ b/website/pages/ar/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ar/substreams/sps/introduction.mdx b/website/pages/ar/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/ar/substreams/sps/introduction.mdx +++ b/website/pages/ar/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ar/substreams/sps/triggers.mdx b/website/pages/ar/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/ar/substreams/sps/triggers.mdx +++ b/website/pages/ar/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/ar/supported-networks.mdx b/website/pages/ar/supported-networks.mdx index c2e7677ae4fb..8b90e2232f92 100644 --- a/website/pages/ar/supported-networks.mdx +++ b/website/pages/ar/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx index ef9f654ef9a9..339b86f84237 100644 --- a/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Průvodce nástroji pro přenos L2 Graph usnadnil přechod na úroveň L2 v Arbitrum One. Pro každého účastníka protokolu je k dispozici sada nástrojů pro přechod na L2, které umožňují bezproblémový přechod na L2 pro všechny účastníky sítě. Tyto nástroje vyžadují provedení určitého souboru kroků v závislosti na tom, co přenášíte. -Některé časté otázky týkající se těchto nástrojů jsou zodpovězeny v sekci [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). Často kladené dotazy obsahují podrobné vysvětlení, jak nástroje používat, jak fungují a na co je třeba při jejich používání pamatovat. +Některé časté otázky týkající se těchto nástrojů jsou zodpovězeny v sekci [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). Často kladené dotazy obsahují podrobné vysvětlení, jak nástroje používat, jak fungují a na co je třeba při jejich používání pamatovat. ## Jak přenést podgraf do Arbitrum (L2) diff --git a/website/pages/cs/archived/sunrise.mdx b/website/pages/cs/archived/sunrise.mdx index 75076fb51020..ad98758ce3ff 100644 --- a/website/pages/cs/archived/sunrise.mdx +++ b/website/pages/cs/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/cs/contracts.mdx b/website/pages/cs/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/cs/contracts.mdx +++ b/website/pages/cs/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/cs/indexing/new-chain-integration.mdx b/website/pages/cs/indexing/new-chain-integration.mdx index e9f52eb42a93..6cd08079845c 100644 --- a/website/pages/cs/indexing/new-chain-integration.mdx +++ b/website/pages/cs/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Pokud nedošlo k chybám, měl by uzel Graf synchronizovat nasazený podgraf. De ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/cs/indexing/overview.mdx b/website/pages/cs/indexing/overview.mdx index a3fb06a96484..1c933a2adbb5 100644 --- a/website/pages/cs/indexing/overview.mdx +++ b/website/pages/cs/indexing/overview.mdx @@ -87,7 +87,7 @@ Po uzavření přídělu může indexátor požádat o slevy. Po uplatnění ná ### Co je to snížení poplatku za dotaz a snížení odměny za indexaci? -Hodnoty `queryFeeCut` a `indexingRewardCut` jsou parametry delegování, které může indexátor nastavit spolu s bloky cooldownBlocks a řídit tak rozdělení GRT mezi indexátor a jeho delegáty. Pokyny k nastavení parametrů delegování naleznete v posledních krocích v části [Zadání protokolu](/network/indexing#stake-in-the-protocol). +Hodnoty `queryFeeCut` a `indexingRewardCut` jsou parametry delegování, které může indexátor nastavit spolu s bloky cooldownBlocks a řídit tak rozdělení GRT mezi indexátor a jeho delegáty. Pokyny k nastavení parametrů delegování naleznete v posledních krocích v části [Zadání protokolu](/network/indexing/#stake-in-the-protocol). - **queryFeeCut** - % slev z poplatků za dotaz, které budou rozděleny mezi indexátory. Pokud je tato hodnota nastavena na 95%, obdrží indexátor 95% poplatků za dotaz získaných při uzavření přídělu a zbylých 5% připadne delegátům. @@ -121,7 +121,7 @@ Indexátory se mohou odlišovat použitím pokročilých technik pro rozhodován ### Jaká jsou základní bezpečnostní opatření, která by měl indexátor přijmout? -- **Peněženka operátora** - Nastavení peněženky operátora je důležitým opatřením, protože umožňuje indexátorovi udržovat oddělení mezi klíči, které kontrolují sázky, a klíči, které řídí každodenní operace. Pokyny naleznete v části [Podíl na protokolu](/network/indexing#stake-in-the-protocol). +- **Peněženka operátora** - Nastavení peněženky operátora je důležitým opatřením, protože umožňuje indexátorovi udržovat oddělení mezi klíči, které kontrolují sázky, a klíči, které řídí každodenní operace. Pokyny naleznete v části [Podíl na protokolu](/network/indexing/#stake-in-the-protocol). - **Firewall** - Pouze služba Indexer musí být vystavena veřejně a zvláštní pozornost by měla být věnována uzamčení portů pro správu a přístupu k databázi: koncový bod JSON-RPC uzlu Graf (výchozí port: 8030), koncový bod API pro správu Indexeru (výchozí port: 18000) a koncový bod databáze Postgres (výchozí port: 5432) by neměly být vystaveny. @@ -375,7 +375,7 @@ docker-compose up #### Začínáme -Agent Indexer a služba Indexer by měly být umístěny společně s infrastrukturou graf uzlu. Existuje mnoho způsobů, jak nastavit virtuální prováděcí prostředí pro komponenty Indexer; zde vysvětlíme, jak je spustit na baremetalu pomocí balíčků NPM nebo zdrojových kódů, nebo pomocí kubernetes a docker na Google Cloud Kubernetes Engine. Pokud se tyto příklady nastavení nedají dobře převést na vaši infrastrukturu, bude pravděpodobně existovat komunitní příručka, na kterou se můžete odkázat, přijďte ji pozdravit na [Discord](https://discord.gg/graphprotocol)! Před spuštěním komponent Indexeru nezapomeňte [zakázat protokol](/network/indexing#stake-in-the-protocol)! +Agent Indexer a služba Indexer by měly být umístěny společně s infrastrukturou graf uzlu. Existuje mnoho způsobů, jak nastavit virtuální prováděcí prostředí pro komponenty Indexer; zde vysvětlíme, jak je spustit na baremetalu pomocí balíčků NPM nebo zdrojových kódů, nebo pomocí kubernetes a docker na Google Cloud Kubernetes Engine. Pokud se tyto příklady nastavení nedají dobře převést na vaši infrastrukturu, bude pravděpodobně existovat komunitní příručka, na kterou se můžete odkázat, přijďte ji pozdravit na [Discord](https://discord.gg/graphprotocol)! Před spuštěním komponent Indexeru nezapomeňte [zakázat protokol](/network/indexing/#stake-in-the-protocol)! #### Z balíčků NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Použití K8s a Terraform -Viz část [Nastavení serverové infrastruktury pomocí Terraformu ve službě Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Viz část [Nastavení serverové infrastruktury pomocí Terraformu ve službě Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Použití @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Jakmile indexer zakládá GRT v protokolu, lze spustit komponenty [Indexer](/network/indexing#indexer-components) a zahájit jejich interakci se sítí. +Jakmile indexer zakládá GRT v protokolu, lze spustit komponenty [Indexer](/network/indexing/#indexer-components) a zahájit jejich interakci se sítí. #### Schválení žetonů diff --git a/website/pages/cs/resources/benefits.mdx b/website/pages/cs/resources/benefits.mdx index fdff16533bbb..36124a5b505a 100644 --- a/website/pages/cs/resources/benefits.mdx +++ b/website/pages/cs/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Kurátorování signálu na podgrafu je volitelný jednorázový čistý nulový náklad (např. na podgrafu lze kurátorovat signál v hodnotě $1k a později jej stáhnout - s potenciálem získat v tomto procesu výnosy). diff --git a/website/pages/cs/resources/roles/curating.mdx b/website/pages/cs/resources/roles/curating.mdx index d0230e080bdf..f693ab60980d 100644 --- a/website/pages/cs/resources/roles/curating.mdx +++ b/website/pages/cs/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Jak signalizovat -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) Kurátor si může zvolit, zda bude signalizovat na konkrétní verzi podgrafu, nebo zda se jeho signál automaticky přenese na nejnovější produkční sestavení daného podgrafu. Obě strategie jsou platné a mají své výhody i nevýhody. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Trh s dotazy je v Graf ze své podstaty mladý a existuje riziko, že vaše %APY může být nižší, než očekáváte, v důsledku dynamiky rodícího se trhu. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Podgraf může selhat kvůli chybě. Za neúspěšný podgraf se neúčtují poplatky za dotaz. V důsledku toho budete muset počkat, až vývojář chybu opraví a nasadí novou verzi. - Pokud jste přihlášeni k odběru nejnovější verze podgrafu, vaše sdílené položky se automaticky přemigrují na tuto novou verzi. Při tom bude účtována 0,5% kurátorská daň. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/cs/subgraphs/cookbook/grafting.mdx b/website/pages/cs/subgraphs/cookbook/grafting.mdx index 637a85c5774e..71c477065788 100644 --- a/website/pages/cs/subgraphs/cookbook/grafting.mdx +++ b/website/pages/cs/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ Při roubování se znovu použijí data z existujícího podgrafu a začne se i Další informace naleznete na: -- [Roubování](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Roubování](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/cs/subgraphs/cookbook/near.mdx b/website/pages/cs/subgraphs/cookbook/near.mdx index 75946639fc4d..156610d51579 100644 --- a/website/pages/cs/subgraphs/cookbook/near.mdx +++ b/website/pages/cs/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ Definice podgrafů má tři aspekty: **subgraph.yaml:** manifest podgrafu definující zdroje dat, které vás zajímají, a způsob jejich zpracování. NEAR je nový `druh` zdroje dat. -**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). +**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í AssemblyScript:** [Kód 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. +**Mapování AssemblyScript:** [Kód 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: @@ -92,13 +92,13 @@ Zdroje dat NEAR podporují dva typy zpracovatelů: ### Definice schématu -Definice schématu popisuje strukturu výsledné databáze podgrafů a vztahy mezi entitami. Toto je agnostika původního zdroje dat. Další podrobnosti o definici schématu podgrafu naleznete [zde](/developing/creating-a-subgraph#the-graphql-schema). +Definice schématu popisuje strukturu výsledné databáze podgrafů a vztahy mezi entitami. Toto je agnostika původního zdroje dat. Další podrobnosti o definici schématu podgrafu naleznete [zde](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mapování Obslužné programy pro zpracování událostí jsou napsány v jazyce [AssemblyScript](https://www.assemblyscript.org/). -Indexování NEAR zavádí do [API AssemblyScript](/developing/graph-ts/api) datové typy specifické pro NEAR. +Indexování NEAR zavádí do [API AssemblyScript](/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` -V opačném případě mají vývojáři podgrafů NEAR během provádění mapování k dispozici zbytek [AssemblyScript API](/developing/graph-ts/api). +V opačném případě mají vývojáři podgrafů NEAR během provádění mapování k dispozici zbytek [AssemblyScript API](/developing/graph-ts/api/). -To zahrnuje novou funkci pro parsování JSON - log na NEAR jsou často emitovány jako serializované JSONs. 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 log. +To zahrnuje novou funkci pro parsování JSON - log na NEAR jsou často emitovány jako serializované JSONs. 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 log. ## Nasazení podgrafu NEAR @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ Brzy vám poskytneme další informace o provozu výše uvedených komponent. ## Dotazování podgrafu NEAR -Koncový bod GraphQL pro podgrafy NEAR je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci GraphQL API](/querying/graphql-api). +Koncový bod GraphQL pro podgrafy NEAR je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci GraphQL API](/querying/graphql-api/). ## Příklady podgrafů diff --git a/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx index d8c0004d37ef..fb96e7ac2a7a 100644 --- a/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ Knihovna `@graphprotocol/graph-ts` poskytuje následující API: | 0.0.8 | Přidá ověření existence polí ve schéma při ukládání entity. | | 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum
Přidání pole `receipt` do objektu Ethereum událost | | 0.0.6 | Přidáno pole `nonce` do objektu Ethereum Transaction
Přidáno `baseFeePerGas` do objektu Ethereum bloku | -| 0.0.5 | AssemblyScript povýšen na verzi 0.19.10 (obsahuje rozbíjející změny, viz [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` přejmenováno na `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript povýšen na verzi 0.19.10 (obsahuje rozbíjející změny, viz [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` přejmenováno na `ethereum.transaction.gasLimit` | | 0.0.4 | Přidání pole `functionSignature` do objektu Ethereum SmartContractCall | | 0.0.3 | Do objektu Ethereum Call přidáno pole `from`
`etherem.call.address` přejmenováno na `ethereum.call.to` | | 0.0.2 | Přidání pole `input` do objektu Ethereum Transackce | diff --git a/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx index cbde00522844..41abfbdccf16 100644 --- a/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Soubor(y) ABI se musí shodovat s vaší smlouvou. Soubory ABI lze získat něko | Verze | Poznámky vydání | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx b/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx index befce4a22bf8..135d55457dcf 100644 --- a/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/cs/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/cs/subgraphs/developing/deploying/multiple-networks.mdx index 0c53c9686fb4..77f05e1ad499 100644 --- a/website/pages/cs/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/cs/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Nasazení podgrafu do více sítí diff --git a/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx index 160322951c6f..069ac68eb04a 100644 --- a/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli Aby mohly být podgrafy podporovány indexátory v síti grafů, musí: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Nesmí používat žádnou z následujících funkcí: - ipfs.cat & ipfs.map - Nefatální diff --git a/website/pages/cs/subgraphs/developing/developer-faq.mdx b/website/pages/cs/subgraphs/developing/developer-faq.mdx index 429f18be662c..7c3af8122927 100644 --- a/website/pages/cs/subgraphs/developing/developer-faq.mdx +++ b/website/pages/cs/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ V rámci podgrafu se události zpracovávají vždy v pořadí, v jakém se obje Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Podívejte se do části "Instancování šablony zdroje dat" na: [Šablony datových zdrojů](/developing/creating-a-subgraph#data-source-templates). +Podívejte se do části "Instancování šablony zdroje dat" na: [Šablony datových zdrojů](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -Seznam podporovaných sítí najdete [zde](/developing/supported-networks). +Seznam podporovaných sítí najdete [zde](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 9c05bb6bf272..d09ee76572fc 100644 --- a/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Zveřejnění podgrafu v decentralizované síti --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Aktualizace metadata publikovaného podgrafu @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Přidání signálu do podgrafu, který nemá nárok na odměny, nepřiláká další indexátory. diff --git a/website/pages/cs/subgraphs/explorer.mdx b/website/pages/cs/subgraphs/explorer.mdx index e501104f13e9..17e39181358b 100644 --- a/website/pages/cs/subgraphs/explorer.mdx +++ b/website/pages/cs/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Chcete-li se dozvědět více o tom, jak se stát indexátorem, můžete se podívat do [oficiální dokumentace](/network/indexing) nebo do [průvodců pro indexátory akademie graf.](https://thegraph.academy/delegators/choosing-indexers/) +Chcete-li se dozvědět více o tom, jak se stát indexátorem, můžete se podívat do [oficiální dokumentace](/network/indexing/) nebo do [průvodců pro indexátory akademie graf.](https://thegraph.academy/delegators/choosing-indexers/) ![Podokno s podrobnostmi o indexování](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Obrázek průzkumníka 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegáti @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Celkové množství GRT, které mají v současné době v protokolu - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Síť diff --git a/website/pages/cs/subgraphs/querying/best-practices.mdx b/website/pages/cs/subgraphs/querying/best-practices.mdx index 85f43c8b931d..2c624f1ec87b 100644 --- a/website/pages/cs/subgraphs/querying/best-practices.mdx +++ b/website/pages/cs/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Každý `název dotazu` smí být při jedné operaci použit pouze jednou. - Každé `pole` musí být ve výběru použito pouze jednou (pod `token` se nemůžeme dvakrát dotazovat na `id`) -- Některá `pole` nebo dotazy (jako `tokeny`) vracejí složené typy, které vyžadují výběr podpole. Nezadání výběru, když se očekává (nebo zadání výběru, když se neočekává - například u `id`), vyvolá chybu. Chcete-li znát typ pole, podívejte se na [Graph Explorer](/network/explorer). +- Některá `pole` nebo dotazy (jako `tokeny`) vracejí složené typy, které vyžadují výběr podpole. Nezadání výběru, když se očekává (nebo zadání výběru, když se neočekává - například u `id`), vyvolá chybu. Chcete-li znát typ pole, podívejte se na [Graph Explorer](/network/explorer/). - Každá proměnná přiřazená argumentu musí odpovídat jeho typu. - V daném seznamu proměnných musí být každá z nich jedinečná. - Musí být použity všechny definované proměnné. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Manipulace s podgrafy napříč řetězci: Dotazování z více podgrafů v jednom dotazu - [Automatické sledování](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/cs/subgraphs/querying/graphql-api.mdx b/website/pages/cs/subgraphs/querying/graphql-api.mdx index 194d477a23c1..0e8100c65976 100644 --- a/website/pages/cs/subgraphs/querying/graphql-api.mdx +++ b/website/pages/cs/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ Tento dotaz vrátí entity `Challenge` a s nimi spojené entity `Application` ta ### Fulltextové Vyhledávání dotazy -Pole pro fulltextové vyhledávání poskytují expresivní rozhraní API pro textové vyhledávání, které lze přidat do schématu podgrafů a přizpůsobit je. Viz [Definice polí pro fulltextové vyhledávání](/developing/creating-a-subgraph#defining-fulltext-search-fields) pro přidání fulltextového vyhledávání do podgrafu. +Pole pro fulltextové vyhledávání poskytují expresivní rozhraní API pro textové vyhledávání, které lze přidat do schématu podgrafů a přizpůsobit je. Viz [Definice polí pro fulltextové vyhledávání](/developing/creating-a-subgraph/#defining-fulltext-search-fields) pro přidání fulltextového vyhledávání do podgrafu. Fulltextové vyhledávací dotazy mají jedno povinné pole `text` pro zadání hledaných výrazů. V tomto vyhledávacím poli `text` je k dispozici několik speciálních fulltextových operátorů. diff --git a/website/pages/cs/subgraphs/querying/introduction.mdx b/website/pages/cs/subgraphs/querying/introduction.mdx index 9489bcf47b46..c6ff13f45420 100644 --- a/website/pages/cs/subgraphs/querying/introduction.mdx +++ b/website/pages/cs/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Dotazování na graf When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/cs/substreams/sps/introduction.mdx b/website/pages/cs/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/cs/substreams/sps/introduction.mdx +++ b/website/pages/cs/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/cs/substreams/sps/triggers.mdx b/website/pages/cs/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/cs/substreams/sps/triggers.mdx +++ b/website/pages/cs/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/cs/supported-networks.mdx b/website/pages/cs/supported-networks.mdx index cc2b778d6cad..e9f1d67e1f3a 100644 --- a/website/pages/cs/supported-networks.mdx +++ b/website/pages/cs/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx index 6908af502fee..15f85694f91f 100644 --- a/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph hat den Wechsel zu L2 auf Arbitrum One leicht gemacht. Für jeden Protokollteilnehmer gibt es eine Reihe von L2-Transfer-Tools, um den Transfer zu L2 für alle Netzwerkteilnehmer nahtlos zu gestalten. Je nachdem, was Sie übertragen möchten, müssen Sie eine bestimmte Anzahl von Schritten befolgen. -Einige häufig gestellte Fragen zu diesen Tools werden in den [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq) beantwortet. Die FAQs enthalten ausführliche Erklärungen zur Verwendung der Tools, zu ihrer Funktionsweise und zu den Dingen, die bei ihrer Verwendung zu beachten sind. +Einige häufig gestellte Fragen zu diesen Tools werden in den [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/) beantwortet. Die FAQs enthalten ausführliche Erklärungen zur Verwendung der Tools, zu ihrer Funktionsweise und zu den Dingen, die bei ihrer Verwendung zu beachten sind. ## So übertragen Sie Ihren Untergraphen auf Arbitrum (L2) diff --git a/website/pages/de/archived/sunrise.mdx b/website/pages/de/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/de/archived/sunrise.mdx +++ b/website/pages/de/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/de/contracts.mdx b/website/pages/de/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/de/contracts.mdx +++ b/website/pages/de/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/de/indexing/new-chain-integration.mdx b/website/pages/de/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/de/indexing/new-chain-integration.mdx +++ b/website/pages/de/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/de/indexing/overview.mdx b/website/pages/de/indexing/overview.mdx index c620276a90e7..d255b2b74cea 100644 --- a/website/pages/de/indexing/overview.mdx +++ b/website/pages/de/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens diff --git a/website/pages/de/resources/benefits.mdx b/website/pages/de/resources/benefits.mdx index 7323852385c9..8e03bbb2d177 100644 --- a/website/pages/de/resources/benefits.mdx +++ b/website/pages/de/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/de/resources/roles/curating.mdx b/website/pages/de/resources/roles/curating.mdx index a5a63f3e2751..a3b96ed010fe 100644 --- a/website/pages/de/resources/roles/curating.mdx +++ b/website/pages/de/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/de/subgraphs/cookbook/grafting.mdx b/website/pages/de/subgraphs/cookbook/grafting.mdx index 4e2311f14da2..bf31d0142e73 100644 --- a/website/pages/de/subgraphs/cookbook/grafting.mdx +++ b/website/pages/de/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/de/subgraphs/cookbook/near.mdx b/website/pages/de/subgraphs/cookbook/near.mdx index 4d1d5530e04e..aa495dfea06e 100644 --- a/website/pages/de/subgraphs/cookbook/near.mdx +++ b/website/pages/de/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema-Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript-Mappings 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/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Beispiele von Subgrafen diff --git a/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx index 649dc4d73cd5..a9caaaf51dbb 100644 --- a/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx index 246d4892fd52..91922e0319e7 100644 --- a/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/de/subgraphs/developing/creating/ql-schema.mdx b/website/pages/de/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/de/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/de/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/de/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/de/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/de/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/de/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/de/subgraphs/developing/developer-faq.mdx b/website/pages/de/subgraphs/developing/developer-faq.mdx index 244aae52d0f4..85dccad933b0 100644 --- a/website/pages/de/subgraphs/developing/developer-faq.mdx +++ b/website/pages/de/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 9de36745a95b..4728db3eb245 100644 --- a/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/de/subgraphs/explorer.mdx b/website/pages/de/subgraphs/explorer.mdx index 71f5b687a15d..1e0169b9ae37 100644 --- a/website/pages/de/subgraphs/explorer.mdx +++ b/website/pages/de/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/de/subgraphs/querying/best-practices.mdx b/website/pages/de/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/de/subgraphs/querying/best-practices.mdx +++ b/website/pages/de/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/de/subgraphs/querying/graphql-api.mdx b/website/pages/de/subgraphs/querying/graphql-api.mdx index cd06c27f4d94..6d9706e54717 100644 --- a/website/pages/de/subgraphs/querying/graphql-api.mdx +++ b/website/pages/de/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/de/subgraphs/querying/introduction.mdx b/website/pages/de/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/de/subgraphs/querying/introduction.mdx +++ b/website/pages/de/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/de/substreams/sps/introduction.mdx b/website/pages/de/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/de/substreams/sps/introduction.mdx +++ b/website/pages/de/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/de/substreams/sps/triggers.mdx b/website/pages/de/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/de/substreams/sps/triggers.mdx +++ b/website/pages/de/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/de/supported-networks.mdx b/website/pages/de/supported-networks.mdx index 797202065e99..9e47f25c86e6 100644 --- a/website/pages/de/supported-networks.mdx +++ b/website/pages/de/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx index 5ba89020402c..e516573fd4d9 100644 --- a/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/en/archived/sunrise.mdx b/website/pages/en/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/en/archived/sunrise.mdx +++ b/website/pages/en/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/en/contracts.mdx b/website/pages/en/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/en/contracts.mdx +++ b/website/pages/en/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/en/indexing/new-chain-integration.mdx b/website/pages/en/indexing/new-chain-integration.mdx index a8a3c88c7250..6d5992f72aaf 100644 --- a/website/pages/en/indexing/new-chain-integration.mdx +++ b/website/pages/en/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -76,4 +76,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/en/indexing/overview.mdx b/website/pages/en/indexing/overview.mdx index 8fdbea889d23..4740c6f82ee0 100644 --- a/website/pages/en/indexing/overview.mdx +++ b/website/pages/en/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens diff --git a/website/pages/en/resources/benefits.mdx b/website/pages/en/resources/benefits.mdx index faefb37bb683..7f4de8e5e5cc 100644 --- a/website/pages/en/resources/benefits.mdx +++ b/website/pages/en/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/en/resources/roles/curating.mdx b/website/pages/en/resources/roles/curating.mdx index f584117580ae..ecb879ae6fbe 100644 --- a/website/pages/en/resources/roles/curating.mdx +++ b/website/pages/en/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/en/subgraphs/cookbook/grafting.mdx b/website/pages/en/subgraphs/cookbook/grafting.mdx index 6c3b85419af9..7aa79c7e2755 100644 --- a/website/pages/en/subgraphs/cookbook/grafting.mdx +++ b/website/pages/en/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/en/subgraphs/cookbook/near.mdx b/website/pages/en/subgraphs/cookbook/near.mdx index 3e86322ddbad..e47043981c52 100644 --- a/website/pages/en/subgraphs/cookbook/near.mdx +++ b/website/pages/en/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx index 60703152b49e..6c7247246444 100644 --- a/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx index 86686025b089..282c68973a8a 100644 --- a/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/en/subgraphs/developing/creating/ql-schema.mdx b/website/pages/en/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/en/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/en/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/en/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/en/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/en/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/en/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx index 7ba8e8080254..f528b2ba74f7 100644 --- a/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/en/subgraphs/developing/developer-faq.mdx b/website/pages/en/subgraphs/developing/developer-faq.mdx index b93fddcd90f1..d0bb74ad1633 100644 --- a/website/pages/en/subgraphs/developing/developer-faq.mdx +++ b/website/pages/en/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 9de36745a95b..4728db3eb245 100644 --- a/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/en/subgraphs/explorer.mdx b/website/pages/en/subgraphs/explorer.mdx index 02dca6ed2f9f..d874f80f5140 100644 --- a/website/pages/en/subgraphs/explorer.mdx +++ b/website/pages/en/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/en/subgraphs/querying/best-practices.mdx b/website/pages/en/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/en/subgraphs/querying/best-practices.mdx +++ b/website/pages/en/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/en/subgraphs/querying/graphql-api.mdx b/website/pages/en/subgraphs/querying/graphql-api.mdx index 3dd70fc7b004..917fad3f2406 100644 --- a/website/pages/en/subgraphs/querying/graphql-api.mdx +++ b/website/pages/en/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/en/subgraphs/querying/introduction.mdx b/website/pages/en/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/en/subgraphs/querying/introduction.mdx +++ b/website/pages/en/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/en/substreams/sps/introduction.mdx b/website/pages/en/substreams/sps/introduction.mdx index 27afab0946c2..bacd601bd011 100644 --- a/website/pages/en/substreams/sps/introduction.mdx +++ b/website/pages/en/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/en/substreams/sps/triggers.mdx b/website/pages/en/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/en/substreams/sps/triggers.mdx +++ b/website/pages/en/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/en/supported-networks.mdx b/website/pages/en/supported-networks.mdx index 797202065e99..9e47f25c86e6 100644 --- a/website/pages/en/supported-networks.mdx +++ b/website/pages/en/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx index 91175703a5c7..684fd486b7e1 100644 --- a/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Guía de las Herramientas de Transferencia a L2 The Graph ha facilitado la migración a L2 en Arbitrum One. Para cada participante del protocolo, existen un conjunto de herramientas de transferencia a L2 para que la migración sea fluida para todos los participantes de la red. Estas herramientas requerirán que sigas un conjunto específico de pasos dependiendo de lo que estés transfiriendo. -Algunas preguntas frecuentes sobre estas herramientas se responden en las [Preguntas Frecuentes de las Herramientas de Transferencia a L2](/arbitrum/l2-transfer-tools-faq). Las preguntas frecuentes contienen explicaciones detalladas sobre cómo utilizar las herramientas, cómo funcionan y aspectos a tener en cuenta al usarlas. +Algunas preguntas frecuentes sobre estas herramientas se responden en las [Preguntas Frecuentes de las Herramientas de Transferencia a L2](/arbitrum/l2-transfer-tools-faq/). Las preguntas frecuentes contienen explicaciones detalladas sobre cómo utilizar las herramientas, cómo funcionan y aspectos a tener en cuenta al usarlas. ## Cómo transferir tu subgrafo a Arbitrum (L2) diff --git a/website/pages/es/archived/sunrise.mdx b/website/pages/es/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/es/archived/sunrise.mdx +++ b/website/pages/es/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/es/contracts.mdx b/website/pages/es/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/es/contracts.mdx +++ b/website/pages/es/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/es/indexing/new-chain-integration.mdx b/website/pages/es/indexing/new-chain-integration.mdx index 6e61fadecf0c..5691510d4427 100644 --- a/website/pages/es/indexing/new-chain-integration.mdx +++ b/website/pages/es/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node debería sincronizar el subgrafo implementado si no hay errores. Dale ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/es/indexing/overview.mdx b/website/pages/es/indexing/overview.mdx index e85cc01e0b86..4cbb716f5ca2 100644 --- a/website/pages/es/indexing/overview.mdx +++ b/website/pages/es/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### ¿Qué es el recorte de la tarifa de consulta y el recorte de la recompensa de indexación? -Los valores de los `QueryFeeCut` e `IndexingRewardCut` son parámetros de delegación que el Indexador debe establecer junto con cooldownBlocks para controlar la distribución de GRT entre el Indexador y sus Delegadores. Hecha un vistazo de los últimos pasos de [Staking in the Protocol](/network/indexing#stake-in-the-protocol) para obtener instrucciones sobre la configuración de los parámetros de delegación. +Los valores de los `QueryFeeCut` e `IndexingRewardCut` son parámetros de delegación que el Indexador debe establecer junto con cooldownBlocks para controlar la distribución de GRT entre el Indexador y sus Delegadores. Hecha un vistazo de los últimos pasos de [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) para obtener instrucciones sobre la configuración de los parámetros de delegación. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Los indexadores pueden diferenciarse aplicando técnicas avanzadas para tomar de ### ¿Qué precauciones básicas de seguridad debe tomar un Indexador? -- **Wallet del operador** - Configurar una wallet del operador es una precaución importante porque permite que un Indexador mantenga la separación entre sus claves que controlan el stake y las que controlan las operaciones diarias. Consulta [Stake in Protocol](/network/indexing#stake-in-the-protocol) para obtener instrucciones. +- **Wallet del operador** - Configurar una wallet del operador es una precaución importante porque permite que un Indexador mantenga la separación entre sus claves que controlan el stake y las que controlan las operaciones diarias. Consulta [Stake in Protocol](/network/indexing/#stake-in-the-protocol) para obtener instrucciones. - **Firewall**: Solo el servicio de indexación debe exponerse públicamente y se debe prestar especial atención al bloqueo de los puertos de administración y el acceso a la base de datos: el endpoint JSON-RPC de Graph Node (puerto predeterminado: 8030), el endpoint de la API de administración del Indexador (puerto predeterminado: 18000) y el endpoint de la base de datos de Postgres (puerto predeterminado: 5432) no deben exponerse. @@ -375,7 +375,7 @@ Para participar con éxito en la red se requiere una supervisión e interacción #### Comenzar -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### Paquetes de NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Uso de K8s y Terraform -Consulta la sección [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Consulta la sección [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Uso @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Una vez que un Indexador ha stakeado GRT en el protocolo, los [Indexer components](/network/indexing#indexer-components) pueden iniciarse y comenzar sus interacciones con la red. +Una vez que un Indexador ha stakeado GRT en el protocolo, los [Indexer components](/network/indexing/#indexer-components) pueden iniciarse y comenzar sus interacciones con la red. #### Aprobar tokens diff --git a/website/pages/es/resources/benefits.mdx b/website/pages/es/resources/benefits.mdx index 6dc95622629c..e7ea8d8117b4 100644 --- a/website/pages/es/resources/benefits.mdx +++ b/website/pages/es/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. La señal de curación en un subgrafo es una acción opcional de única vez y no tiene costo neto (por ejemplo, se pueden curar $1k en señales en un subgrafo y luego retirarlas, con el potencial de obtener retornos en el proceso). diff --git a/website/pages/es/resources/roles/curating.mdx b/website/pages/es/resources/roles/curating.mdx index a11299ddd57e..815027929cbb 100644 --- a/website/pages/es/resources/roles/curating.mdx +++ b/website/pages/es/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Cómo señalar -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) Un curador puede optar por señalar una versión especifica de un subgrafo, o puede optar por que su señal migre automáticamente a la versión de producción mas reciente de ese subgrafo. Ambas son estrategias válidas y tienen sus pros y sus contras. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. El mercado de consultas es inherentemente joven en The Graph y existe el riesgo de que su APY (Rentabilidad anualizada) sea más bajo de lo esperado debido a la dinámica del mercado que recién está empezando. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Un subgrafo puede fallar debido a un error. Un subgrafo fallido no acumula tarifas de consulta. Como resultado, tendrás que esperar hasta que el desarrollador corrija el error e implemente una nueva versión. - Si estás suscrito a la versión más reciente de un subgrafo, tus acciones se migrarán automáticamente a esa nueva versión. Esto incurrirá un impuesto de curación del 0.5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/es/subgraphs/cookbook/grafting.mdx b/website/pages/es/subgraphs/cookbook/grafting.mdx index 212250c06428..b5957131aaec 100644 --- a/website/pages/es/subgraphs/cookbook/grafting.mdx +++ b/website/pages/es/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ El subgrafo grafteado puede utilizar un esquema GraphQL que no es idéntico al d Para más información, puedes consultar: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/es/subgraphs/cookbook/near.mdx b/website/pages/es/subgraphs/cookbook/near.mdx index 1b01dee85059..c1e837bfe88a 100644 --- a/website/pages/es/subgraphs/cookbook/near.mdx +++ b/website/pages/es/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ Hay tres aspectos de la definición de subgrafo: **subgraph.yaml:** el manifiesto del subgrafo, que define las fuentes de datos de interés y cómo deben procesarse. NEAR es un nuevo `tipo` de fuente de datos. -**schema.graphql:** un archivo de esquema que define qué datos se almacenan para su subgrafo y cómo consultarlos a través de GraphQL. Los requisitos para los subgrafos NEAR están cubiertos por [la documentación existente](/developing/creating-a-subgraph#the-graphql-schema). +**schema.graphql:** un archivo de esquema que define qué datos se almacenan para su subgrafo y cómo consultarlos a través de GraphQL. Los requisitos para los subgrafos NEAR están cubiertos por [la documentación existente](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**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. Durante el desarrollo del subgrafo hay dos comandos clave: @@ -92,13 +92,13 @@ Las fuentes de datos NEAR admiten dos tipos de handlers: ### Definición de esquema -La definición de esquema describe la estructura de la base de datos de subgrafos resultante y las relaciones entre las entidades. Esto es independiente de la fuente de datos original. Hay más detalles sobre la definición de esquema de subgrafo [aquí](/developing/creating-a-subgraph#the-graphql-schema). +La definición de esquema describe la estructura de la base de datos de subgrafos resultante y las relaciones entre las entidades. Esto es independiente de la fuente de datos original. Hay más detalles sobre la definición de esquema de subgrafo [aquí](/developing/creating-a-subgraph/#the-graphql-schema). ### Asignaciones de AssemblyScript Los handlers para procesar eventos están escritos en [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Estos tipos se pasan a block & handlers de recibos: - Los handlers de bloques recibirán un `Block` - Los handlers de recibos recibirán un `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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. ## Deployando un subgrafo NEAR @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ Pronto proporcionaremos más información sobre cómo ejecutar los componentes a ## Consultando un subgrafo NEAR -El endpoint de GraphQL para los subgrafos NEAR está determinado por la definición del esquema, con la interfaz API existente. Visite la [documentación de la API de GraphQL](/querying/graphql-api) para obtener más información. +El endpoint de GraphQL para los subgrafos NEAR está determinado por la definición del esquema, con la interfaz API existente. Visite la [documentación de la API de GraphQL](/querying/graphql-api/) para obtener más información. ## Subgrafos de ejemplo diff --git a/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx index 5399f3838722..3ae81bb3ba99 100644 --- a/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx index 3f54aeed7a4c..b70948811960 100644 --- a/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Los archivos ABI deben coincidir con tu(s) contrato(s). Hay varias formas de obt | Version | Notas del lanzamiento | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/es/subgraphs/developing/creating/ql-schema.mdx b/website/pages/es/subgraphs/developing/creating/ql-schema.mdx index 4ecbc03b60a8..f1c9b18b2670 100644 --- a/website/pages/es/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/es/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/es/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/es/subgraphs/developing/deploying/multiple-networks.mdx index 276e10f5d0d4..c206beeb8fb3 100644 --- a/website/pages/es/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/es/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Desplegando el subgráfo en múltiples redes diff --git a/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx index 1ea90990a2d9..42e3a9f0b06a 100644 --- a/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - No debe utilizar ninguna de las siguientes funciones: - ipfs.cat & ipfs.map - Errores no fatales diff --git a/website/pages/es/subgraphs/developing/developer-faq.mdx b/website/pages/es/subgraphs/developing/developer-faq.mdx index 3cf0a885e79c..6c241eab68d0 100644 --- a/website/pages/es/subgraphs/developing/developer-faq.mdx +++ b/website/pages/es/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Dentro de un subgrafo, los eventos se procesan siempre en el orden en que aparec Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Consulta la sección "Instantiating a data source template" en: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Consulta la sección "Instantiating a data source template" en: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -Puedes encontrar la lista de redes admitidas [aquí](/developing/supported-networks). +Puedes encontrar la lista de redes admitidas [aquí](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 8665582533ac..7874a463e93a 100644 --- a/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publicación de un subgrafo en la Red Descentralizada --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Actualización de los metadatos de un subgrafo publicado @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/es/subgraphs/explorer.mdx b/website/pages/es/subgraphs/explorer.mdx index 7f8dee22a2e7..cf0be13a6c6a 100644 --- a/website/pages/es/subgraphs/explorer.mdx +++ b/website/pages/es/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Para obtener más información sobre cómo convertirte en un Indexador, puedes consultar la [documentación oficial](/network/indexing) o [The Graph Academy Indexer Guides.](https://thegraph.academy/delegators/ eligiendo-indexadores/) +Para obtener más información sobre cómo convertirte en un Indexador, puedes consultar la [documentación oficial](/network/indexing/) o [The Graph Academy Indexer Guides.](https://thegraph.academy/delegators/ eligiendo-indexadores/) ![Panel de detalles de indexación](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Imagen de Explorer 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegadores @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Cantidad total de GRT que tienen actualmente dentro del protocolo - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Red diff --git a/website/pages/es/subgraphs/querying/best-practices.mdx b/website/pages/es/subgraphs/querying/best-practices.mdx index 8336be7374a7..94161ebe9fbe 100644 --- a/website/pages/es/subgraphs/querying/best-practices.mdx +++ b/website/pages/es/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Cada `queryName` sólo debe utilizarse una vez por operación. - Cada `field` debe utilizarse una sola vez en una selección (no podemos consultar el `id` dos veces bajo `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Cualquier variable asignada a un argumento debe coincidir con su tipo. - En una lista dada de variables, cada una de ellas debe ser única. - Deben utilizarse todas las variables definidas. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Manejo de subgrafos cross-chain: Consulta de varios subgrafos en una sola consulta - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/es/subgraphs/querying/graphql-api.mdx b/website/pages/es/subgraphs/querying/graphql-api.mdx index 0817a89f807e..a85ec5413f85 100644 --- a/website/pages/es/subgraphs/querying/graphql-api.mdx +++ b/website/pages/es/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ Esta consulta devolverá entidades `Challenge` y sus entidades `Application` aso ### Consultas de Búsqueda de Texto Completo -Los campos de consulta de búsqueda de texto completo proporcionan una API de búsqueda de texto expresivo que se puede agregar al esquema del subgrafo y personalizar. Consulta [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) para agregar búsqueda de texto completo a tu subgrafo. +Los campos de consulta de búsqueda de texto completo proporcionan una API de búsqueda de texto expresivo que se puede agregar al esquema del subgrafo y personalizar. Consulta [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) para agregar búsqueda de texto completo a tu subgrafo. Las consultas de búsqueda de texto completo tienen un campo obligatorio, `text`, para proporcionar términos de búsqueda. Hay varios operadores especiales de texto completo disponibles para usar en este campo de búsqueda `text`. diff --git a/website/pages/es/subgraphs/querying/introduction.mdx b/website/pages/es/subgraphs/querying/introduction.mdx index 94fc00ea08b8..270d1803e092 100644 --- a/website/pages/es/subgraphs/querying/introduction.mdx +++ b/website/pages/es/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Consultando The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/es/substreams/sps/introduction.mdx b/website/pages/es/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/es/substreams/sps/introduction.mdx +++ b/website/pages/es/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/es/substreams/sps/triggers.mdx b/website/pages/es/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/es/substreams/sps/triggers.mdx +++ b/website/pages/es/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/es/supported-networks.mdx b/website/pages/es/supported-networks.mdx index 86c379d637f5..0038019281c5 100644 --- a/website/pages/es/supported-networks.mdx +++ b/website/pages/es/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx index a0a6f17b4265..eababee7047d 100644 --- a/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Guide des outils de transfert L2 The Graph a facilité le passage à L2 sur Arbitrum One. Pour chaque participant au protocole, il existe un ensemble d'outils de transfert L2 permettant de rendre le transfert vers L2 transparent pour tous les participants du réseau. Ces outils vous obligeront à suivre un ensemble d’étapes spécifiques en fonction de ce que vous transférez. -Certaines questions fréquentes sur ces outils trouvent leur réponse dans la [FAQ sur les outils de transfert L2](/arbitrum/l2-transfer-tools-faq). Les FAQ contiennent des explications détaillées sur la façon d'utiliser les outils, leur fonctionnement et les éléments à garder à l'esprit lors de leur utilisation. +Certaines questions fréquentes sur ces outils trouvent leur réponse dans la [FAQ sur les outils de transfert L2](/arbitrum/l2-transfer-tools-faq/). Les FAQ contiennent des explications détaillées sur la façon d'utiliser les outils, leur fonctionnement et les éléments à garder à l'esprit lors de leur utilisation. ## Comment transférer votre subgraph vers Arbitrum (L2) diff --git a/website/pages/fr/archived/sunrise.mdx b/website/pages/fr/archived/sunrise.mdx index 20f23e1a01f1..5ca61cbced48 100644 --- a/website/pages/fr/archived/sunrise.mdx +++ b/website/pages/fr/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/fr/contracts.mdx b/website/pages/fr/contracts.mdx index b9b33f2c14d7..b609dceaf476 100644 --- a/website/pages/fr/contracts.mdx +++ b/website/pages/fr/contracts.mdx @@ -14,7 +14,7 @@ Il s'agit du déploiement principal de The Graph Network. ## Réseau principal -Il s'agissait du déploiement initial de The Graph Network. [En savoir plus](/arbitrum/arbitrum-faq) sur la mise à l'échelle de The Graph avec Arbitrum. +Il s'agissait du déploiement initial de The Graph Network. [En savoir plus](/arbitrum/arbitrum-faq/) sur la mise à l'échelle de The Graph avec Arbitrum. diff --git a/website/pages/fr/indexing/new-chain-integration.mdx b/website/pages/fr/indexing/new-chain-integration.mdx index 3f0e6d2612d6..465f1652f340 100644 --- a/website/pages/fr/indexing/new-chain-integration.mdx +++ b/website/pages/fr/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node devrait synchroniser le subgraph déployé s'il n'y a pas d'erreurs. ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/fr/indexing/overview.mdx b/website/pages/fr/indexing/overview.mdx index cb42d6d859be..809e92a8fcb0 100644 --- a/website/pages/fr/indexing/overview.mdx +++ b/website/pages/fr/indexing/overview.mdx @@ -87,7 +87,7 @@ Une fois qu'une allocation a été clôturée, les remises peuvent être réclam ### Qu'est-ce que la réduction des frais de requête et la réduction des récompenses d'indexation ? -Les valeurs `queryFeeCut` et `indexingRewardCut` sont des paramètres de délégation que l'indexeur peut définir avec cooldownBlocks pour contrôler la distribution du GRT entre l'indexeur et ses délégués. Consultez les dernières étapes dans [Jalonnement dans le protocole](/network/indexing#stake-in-the-protocol) pour obtenir des instructions sur la définition des paramètres de délégation. +Les valeurs `queryFeeCut` et `indexingRewardCut` sont des paramètres de délégation que l'indexeur peut définir avec cooldownBlocks pour contrôler la distribution du GRT entre l'indexeur et ses délégués. Consultez les dernières étapes dans [Jalonnement dans le protocole](/network/indexing/#stake-in-the-protocol) pour obtenir des instructions sur la définition des paramètres de délégation. - **queryFeeCut** : % de remise sur les frais de requête qui sera distribuée à l'indexeur. Si ce taux est fixé à 95 %, l'indexeur recevra 95 % des frais de requête gagnés lorsqu'une allocation est clôturée, les 5 % restants étant reversés aux délégateurs. @@ -121,7 +121,7 @@ Les indexeurs peuvent se différencier en appliquant des techniques avancées po ### Quelles sont les précautions de sécurité de base qu’un indexeur doit prendre ? -- **Portefeuille d'opérateur** : la configuration d'un portefeuille d'opérateur est une précaution importante car elle permet à un indexeur de maintenir une séparation entre ses clés qui contrôlent la participation et celles qui contrôlent les opérations quotidiennes. opérations de jour. Voir [Participation dans le protocole](/network/indexing#stake-in-the-protocol) pour les instructions. +- **Portefeuille d'opérateur** : la configuration d'un portefeuille d'opérateur est une précaution importante car elle permet à un indexeur de maintenir une séparation entre ses clés qui contrôlent la participation et celles qui contrôlent les opérations quotidiennes. opérations de jour. Voir [Participation dans le protocole](/network/indexing/#stake-in-the-protocol) pour les instructions. - **Pare-feu** : seul le service Indexer doit être exposé publiquement et une attention particulière doit être accordée au verrouillage des ports d'administration et de l'accès à la base de données : le point de terminaison JSON-RPC de Graph Node (port par défaut : 8030), le point de terminaison de l'API de gestion de l'indexeur (port par défaut : 18000) et le point de terminaison de la base de données Postgres (port par défaut : 5432) ne doivent pas être exposés. @@ -375,7 +375,7 @@ Pour participer avec succès au réseau, il faut une surveillance et une interac #### Commencer -L’agent Indexer et le service Indexer doivent être colocalisés avec votre infrastructure Graph Node. Il existe de nombreuses façons de configurer des environnements d'exécution virtuels pour vos composants Indexer ; nous expliquerons ici comment les exécuter sur baremetal à l'aide des packages ou de la source NPM, ou via kubernetes et docker sur Google Cloud Kubernetes Engine. Si ces exemples de configuration ne s'adaptent pas bien à votre infrastructure, il y aura probablement un guide communautaire à consulter, venez nous dire bonjour sur [Discord](https://discord.gg/graphprotocol) ! N'oubliez pas de [participer au protocole](/network/indexing#stake-in-the-protocol) avant de démarrer vos composants Indexer ! +L’agent Indexer et le service Indexer doivent être colocalisés avec votre infrastructure Graph Node. Il existe de nombreuses façons de configurer des environnements d'exécution virtuels pour vos composants Indexer ; nous expliquerons ici comment les exécuter sur baremetal à l'aide des packages ou de la source NPM, ou via kubernetes et docker sur Google Cloud Kubernetes Engine. Si ces exemples de configuration ne s'adaptent pas bien à votre infrastructure, il y aura probablement un guide communautaire à consulter, venez nous dire bonjour sur [Discord](https://discord.gg/graphprotocol) ! N'oubliez pas de [participer au protocole](/network/indexing/#stake-in-the-protocol) avant de démarrer vos composants Indexer ! #### À partir des packages NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Utilisation de K8s et Terraform -Consultez la section [Configurer l'infrastructure du serveur à l'aide de Terraform sur Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Consultez la section [Configurer l'infrastructure du serveur à l'aide de Terraform sur Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Usage @@ -755,7 +755,7 @@ Les premières étapes pour participer au réseau en tant qu'Indexeur sont d'app > Note : Pour les besoins de ces instructions, Remix sera utilisé pour l'interaction avec le contrat, mais n'hésitez pas à utiliser l'outil de votre choix ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), et [MyCrypto](https://www.mycrypto.com/account) sont quelques autres outils connus). -Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l'indexeur](/network/indexing#indexer-components) peuvent être démarrés et commencer leurs interactions avec le réseau. +Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l'indexeur](/network/indexing/#indexer-components) peuvent être démarrés et commencer leurs interactions avec le réseau. #### Approuver les jetons diff --git a/website/pages/fr/resources/benefits.mdx b/website/pages/fr/resources/benefits.mdx index 7b1523a93dd9..89b0bf8a2d4f 100644 --- a/website/pages/fr/resources/benefits.mdx +++ b/website/pages/fr/resources/benefits.mdx @@ -76,7 +76,7 @@ Les coûts d'interrogation peuvent varier ; le coût indiqué est la moyenne au ‡Reflète le coût pour le consommateur de données. Les frais de requête sont toujours payés aux Indexeurs pour les requêtes du Plan Gratuit. -Les coûts estimés sont uniquement pour les subgraphs Ethereum Mainnet - les coûts sont encore plus élevés lorsqu'on héberge soi-même un `graph-node` sur d'autres réseaux. Certains utilisateurs peuvent avoir besoin de mettre à jour leur subgraph vers une nouvelle version. En raison des frais de gaz Ethereum, une mise à jour coûte ~50 $ au moment de la rédaction. Notez que les frais de gaz sur [Arbitrum](/arbitrum/arbitrum-faq) sont considérablement plus bas que ceux d'Ethereum mainnet. +Les coûts estimés sont uniquement pour les subgraphs Ethereum Mainnet - les coûts sont encore plus élevés lorsqu'on héberge soi-même un `graph-node` sur d'autres réseaux. Certains utilisateurs peuvent avoir besoin de mettre à jour leur subgraph vers une nouvelle version. En raison des frais de gaz Ethereum, une mise à jour coûte ~50 $ au moment de la rédaction. Notez que les frais de gaz sur [Arbitrum](/arbitrum/arbitrum-faq/) sont considérablement plus bas que ceux d'Ethereum mainnet. Émettre un signal sur un subgraph est un cout net, nul optionnel et unique (par exemple, 1 000 $ de signal peuvent être conservés sur un subgraph, puis retirés - avec la possibilité de gagner des revenus au cours du processus). diff --git a/website/pages/fr/resources/roles/curating.mdx b/website/pages/fr/resources/roles/curating.mdx index da503e1d6dea..fb3d73259617 100644 --- a/website/pages/fr/resources/roles/curating.mdx +++ b/website/pages/fr/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Les Indexeurs peuvent trouver des subgraphs à indexer en fonction des signaux d ## Comment signaler -Dans l'onglet Curateur de Graph Explorer, les Curateurs pourront signaler et dé-signaler certains subgraphs en fonction des statistiques du réseau. Pour un aperçu étape par étape de la procédure à suivre dans Graph Explorer, [cliquez ici.](/network/explorer) +Dans l'onglet Curateur de Graph Explorer, les Curateurs pourront signaler et dé-signaler certains subgraphs en fonction des statistiques du réseau. Pour un aperçu étape par étape de la procédure à suivre dans Graph Explorer, [cliquez ici.](/network/explorer/) Un curateur peut choisir de signaler une version spécifique d'un sugraph ou de faire migrer automatiquement son signal vers la version de production la plus récente de ce subgraph. Ces deux stratégies sont valables et comportent leurs propres avantages et inconvénients. @@ -48,7 +48,7 @@ Cependant, il est recommandé que les Curateurs laissent leur GRT signalé en pl 1. Le marché des requêtes est intrinsèquement jeune chez The Graph et il y a un risque que votre %APY soit inférieur à vos attentes en raison de la dynamique naissante du marché. 2. Frais de curation - lorsqu'un Curateur signale des GRT sur un subgraph, il doit s'acquitter d'une taxe de curation de 1%. Cette taxe est brûlée. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Un subgraph peut échouer à cause d'un bug. Un subgraph qui échoue n'accumule pas de frais de requête. Par conséquent, vous devrez attendre que le développeur corrige le bogue et déploie une nouvelle version. - Si vous êtes abonné à la version la plus récente d'un subgraph, vos parts migreront automatiquement vers cette nouvelle version. Cela entraînera une taxe de curation de 0,5 %. - Si vous avez signalé sur une version spécifique d'un subgraph et qu'elle échoue, vous devrez brûler manuellement vos parts de curation. Vous pouvez alors signaler sur la nouvelle version du subgraph, encourant ainsi une taxe de curation de 1%. diff --git a/website/pages/fr/subgraphs/cookbook/grafting.mdx b/website/pages/fr/subgraphs/cookbook/grafting.mdx index b255c571ec8b..b092fd08232e 100644 --- a/website/pages/fr/subgraphs/cookbook/grafting.mdx +++ b/website/pages/fr/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ Le subgraph greffé peut utiliser un schema GraphQL qui n'est pas identique à c Pour plus d’informations, vous pouvez vérifier : -- [Greffage](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Greffage](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/fr/subgraphs/cookbook/near.mdx b/website/pages/fr/subgraphs/cookbook/near.mdx index 36c04cb55379..b3c4cb30bff2 100644 --- a/website/pages/fr/subgraphs/cookbook/near.mdx +++ b/website/pages/fr/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ La définition d'un subgraph comporte trois aspects : **subgraph.yaml** : le manifeste du subgraph, définissant les sources de données d'intérêt et la manière dont elles doivent être traitées. NEAR est un nouveau `type` de source de données. -**schema.graphql** : un fichier de schéma qui définit quelles données sont stockées pour votre subgraph, et comment les interroger via GraphQL. Les exigences pour les subgraphs NEAR sont couvertes par la [documentation existante](/developing/creating-a-subgraph#the-graphql-schema). +**schema.graphql** : un fichier de schéma qui définit quelles données sont stockées pour votre subgraph, et comment les interroger via GraphQL. Les exigences pour les subgraphs NEAR sont couvertes par la [documentation existante](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**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. Lors du développement du subgraph, il y a deux commandes clés : @@ -92,13 +92,13 @@ Les fichiers de données NEAR prennent en charge deux types de gestionnaires : ### La Définition du schema -La définition du schema décrit la structure de la base de données de subgraphs résultante et les relations entre les entités. Ceci est indépendant de la source de données originale. Vous trouverez plus de détails sur la définition du schema des subgraph [ici](/developing/creating-a-subgraph#the-graphql-schema). +La définition du schema décrit la structure de la base de données de subgraphs résultante et les relations entre les entités. Ceci est indépendant de la source de données originale. Vous trouverez plus de détails sur la définition du schema des subgraph [ici](/developing/creating-a-subgraph/#the-graphql-schema). ### Les Cartographies d'AssemblyScript Les gestionnaires de traitement des événements sont écrits dans l'[AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Ces types sont passés au bloc & gestionnaires de reçus : - Les gestionnaires de blocs reçoivent un `Block` - Les gestionnaires de reçus reçoivent un `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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. ## Déploiement d'un subgraph NEAR @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ Nous fournirons bientôt plus d'informations sur l'utilisation des composants ci ## Interrogation d'un subgraph NEAR -Le point de terminaison GraphQL pour les subgraphs NEAR est déterminé par la définition du schéma, avec l'interface API existante. Veuillez consulter la [documentation de l'API GraphQL](/querying/graphql-api) pour plus d'informations. +Le point de terminaison GraphQL pour les subgraphs NEAR est déterminé par la définition du schéma, avec l'interface API existante. Veuillez consulter la [documentation de l'API GraphQL](/querying/graphql-api/) pour plus d'informations. ## Des exemples de subgraphs diff --git a/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx index 3587758f3f64..38125106319c 100644 --- a/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx @@ -35,7 +35,7 @@ La `apiVersion` dans le manifeste du subgraph spécifie la version de l'API de m | 0.0.8 | Ajout de la validation pour l'existence des champs dans le schéma lors de l'enregistrement d'une entité. | | 0.0.7 | Ajout des classes `TransactionReceipt` et `Log`aux types Ethereum
Ajout du champ `receipt` à l'objet Ethereum Event | | 0.0.6 | Ajout du champ `nonce` à l'objet Ethereum Transaction
Ajout de `baseFeePerGas` à l'objet Ethereum Block | -| 0.0.5 | AssemblyScript a été mis à niveau vers la version 0.19.10 (ceci inclut des changements importants, veuillez consulter le [`Guide de Migration`](/release-notes/assemblyscript-migration-guide))
. `ethereum.transaction.gasUsed` est renommé en `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript a été mis à niveau vers la version 0.19.10 (ceci inclut des changements importants, veuillez consulter le [`Guide de Migration`](/release-notes/assemblyscript-migration-guide/))
. `ethereum.transaction.gasUsed` est renommé en `ethereum.transaction.gasLimit` | | 0.0.4 | Ajout du champ `functionSignature` à l'objet Ethereum SmartContractCall | | 0.0.3 | Ajout du champ `from` à l'objet Ethereum Call
`etherem.call.address` est renommé en `ethereum.call.to` | | 0.0.2 | Ajout du champ `input` à l'objet Ethereum Transaction | diff --git a/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx index d5f4ec246945..d5f137f2260f 100644 --- a/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Le(s) fichier(s) ABI doivent correspondre à votre(vos) contrat(s). Il existe pl | Version | Notes de version | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx b/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx index b0c91ff4665f..69dd84eb35e3 100644 --- a/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/fr/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/fr/subgraphs/developing/deploying/multiple-networks.mdx index c4e981a572cc..26e6edf71235 100644 --- a/website/pages/fr/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/fr/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Déploiement d'un subgraph sur plusieurs réseaux --- -Cette page explique comment déployer un subgraph sur plusieurs réseaux. Pour déployer un subgraph, vous devez premièrement installer le [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). Si vous n'avez pas encore créé de subgraph, consultez [Creation d'un subgraph](/developing/creating-a-subgraph). +Cette page explique comment déployer un subgraph sur plusieurs réseaux. Pour déployer un subgraph, vous devez premièrement installer le [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). Si vous n'avez pas encore créé de subgraph, consultez [Creation d'un subgraph](/developing/creating-a-subgraph/). ## Déploiement du subgraph sur plusieurs réseaux diff --git a/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx index 3aeb7730bd33..5650501b53fd 100644 --- a/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli Pour être pris en charge par les Indexeurs sur The Graph Network, les subgraphs doivent : -- Indexer un [réseau pris en charge](/developing/supported-networks) +- Indexer un [réseau pris en charge](/developing/supported-networks/) - Ne doit utiliser aucune des fonctionnalités suivantes : - ipfs.cat & ipfs.map - Erreurs non fatales diff --git a/website/pages/fr/subgraphs/developing/developer-faq.mdx b/website/pages/fr/subgraphs/developing/developer-faq.mdx index 5d05fd278df2..55e93b41e6fb 100644 --- a/website/pages/fr/subgraphs/developing/developer-faq.mdx +++ b/website/pages/fr/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Dans un subgraph, les événements sont toujours traités dans l'ordre dans lequ Les modèles vous permettent de créer rapidement des sources de données , pendant que votre subgraph est en cours d'indexation. Votre contrat peut générer de nouveaux contrats à mesure que les gens interagissent avec lui. Étant donné que vous connaissez la structure de ces contrats (ABI, événements, etc.) à l'avance, vous pouvez définir comment vous souhaitez les indexer dans un modèle. Lorsqu'ils sont générés, votre subgraph créera une source de données dynamique en fournissant l'adresse du contrat. -Consultez la section "Instanciation d'un modèle de source de données" sur : [Modèles de source de données](/developing/creating-a-subgraph#data-source-templates). +Consultez la section "Instanciation d'un modèle de source de données" sur : [Modèles de source de données](/developing/creating-a-subgraph/#data-source-templates). ### 11. Est-il possible de configurer un subgraph en utilisant `graph init` de `graph-cli` avec deux contrats ? Ou devrais-je ajouter manuellement une autre source de données dans `subgraph.yaml` après avoir exécuté `graph init` ? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. Quels réseaux sont supportés par The Graph? -Vous pouvez trouver la liste des réseaux supportés [ici](/developing/supported-networks). +Vous pouvez trouver la liste des réseaux supportés [ici](/developing/supported-networks/). ### 17. Est-il possible de faire la différence entre les réseaux (mainnet, Sepolia, local) dans les gestionnaires d'événements? @@ -107,11 +107,11 @@ Oui. Sepolia prend en charge les gestionnaires de blocs, les gestionnaires d'app ### 19. Est-il possible de spécifier à partir de quel bloc commencer l'indexation? -Oui. `dataSources.source.startBlock` dans le fichier `subgraph.yaml` spécifie le numéro du bloc à partir duquel la Source de donnée commence l'indexation. Dans la plupart des cas, nous suggérons d'utiliser le bloc où le contrat a été créé : [Blocs de départ](/developing/creating-a-subgraph#start-blocks) +Oui. `dataSources.source.startBlock` dans le fichier `subgraph.yaml` spécifie le numéro du bloc à partir duquel la Source de donnée commence l'indexation. Dans la plupart des cas, nous suggérons d'utiliser le bloc où le contrat a été créé : [Blocs de départ](/developing/creating-a-subgraph/#start-blocks) ### 20. Quels sont quelques conseils pour augmenter les performances d'indexation? Mon subgraph prend beaucoup de temps à se synchroniser -Oui, vous devriez consulter la fonctionnalité optionnelle de bloc de départ pour commencer l'indexation à partir du bloc où le contrat a été déployé : [Blocs de départ](/developing/creating-a-subgraph#start-blocks) +Oui, vous devriez consulter la fonctionnalité optionnelle de bloc de départ pour commencer l'indexation à partir du bloc où le contrat a été déployé : [Blocs de départ](/developing/creating-a-subgraph/#start-blocks) ### 21. Existe-t-il un moyen d'interroger directement le subgraph pour déterminer le dernier numéro de bloc qu'il a indexé? diff --git a/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx index fba2c9221675..8e809cf0b720 100644 --- a/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publication d'un subgraph sur le réseau décentralisé --- -Une fois que vous avez [déployé votre subgraph sur Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) et qu'il est prêt à passer en production, vous pouvez le publier sur le réseau décentralisé. +Une fois que vous avez [déployé votre subgraph sur Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) et qu'il est prêt à passer en production, vous pouvez le publier sur le réseau décentralisé. Lorsque vous publiez un subgraph sur le réseau décentralisé, vous le rendez disponible pour : -- [Les Curateurs](/network/curating), qui peuvent commencer à le curer. -- [Les Indexeurs](/network/indexing), qui peuvent commencer à l’indexer. +- [Les Curateurs](/network/curating/), qui peuvent commencer à le curer. +- [Les Indexeurs](/network/indexing/), qui peuvent commencer à l’indexer. -Consultez la liste des [réseaux pris en charge](/developing/supported-networks). +Consultez la liste des [réseaux pris en charge](/developing/supported-networks/). ## Publication à partir de Subgraph Studio @@ -21,9 +21,9 @@ Consultez la liste des [réseaux pris en charge](/developing/supported-networks) Toutes les versions publiées d'un subgraph existant peuvent : -- Être publiées sur Arbitrum One. [En savoir plus sur The Graph Network sur Arbitrum](/arbitrum/arbitrum-faq). +- Être publiées sur Arbitrum One. [En savoir plus sur The Graph Network sur Arbitrum](/arbitrum/arbitrum-faq/). -- Indexer des données sur l'un des [réseaux pris en charge](/developing/supported-networks), quel que soit le réseau sur lequel le subgraph a été publié. +- Indexer des données sur l'un des [réseaux pris en charge](/developing/supported-networks/), quel que soit le réseau sur lequel le subgraph a été publié. ### Mise à jour des métadonnées d'un subgraph publié @@ -69,7 +69,7 @@ Les développeurs peuvent ajouter des signaux GRT à leurs subgraphs pour incite - Vous pouvez vérifier l'éligibilité aux récompenses d'indexation en fonction de l'utilisation des fonctionnalités du subgraph [ici](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Les réseaux spécifiques pris en charge peuvent être vérifiés [ici](/developing/supported-networks). +- Les réseaux spécifiques pris en charge peuvent être vérifiés [ici](/developing/supported-networks/). > Ajouter un signal à un subgraph non éligible aux récompenses n'attirera pas d'Indexeurs supplémentaires. diff --git a/website/pages/fr/subgraphs/explorer.mdx b/website/pages/fr/subgraphs/explorer.mdx index fa9c6046f691..9a34557333fd 100644 --- a/website/pages/fr/subgraphs/explorer.mdx +++ b/website/pages/fr/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Les Indexeurs peuvent gagner à la fois des frais de requête et des récompense - Les paramètres d'indexation peuvent être définis en cliquant sur le côté droit du tableau ou en accédant au profil d'un Indexeur et en cliquant sur le bouton "Delegate ". -Pour en savoir plus sur la façon de devenir un indexeur, vous pouvez consulter la [documentation officielle](/network/indexing) ou les [guides de l'indexeur de la Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) +Pour en savoir plus sur la façon de devenir un indexeur, vous pouvez consulter la [documentation officielle](/network/indexing/) ou les [guides de l'indexeur de la Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) ![Volet Détails de l'indexation](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ Dans le tableau des Curateurs ci-dessous, vous pouvez voir : ![Explorer Image 6](/img/Curation-Overview.png) -Si vous souhaitez en savoir plus sur le rôle de Curateur, vous pouvez le faire en consultant la [documentation officielle.](/network/curating) ou [The Graph Academy](https://thegraph.academy/curators/). +Si vous souhaitez en savoir plus sur le rôle de Curateur, vous pouvez le faire en consultant la [documentation officielle.](/network/curating/) ou [The Graph Academy](https://thegraph.academy/curators/). ### 3. Délégués @@ -113,7 +113,7 @@ Dans le tableau des Délégateurs, vous pouvez voir les Délégateurs actifs dan - Quantité totale de GRT qu'ils ont actuellement dans le protocole - La date de leur dernière délégation -Si vous souhaitez en savoir plus sur comment devenir Délégateur, consultez la [documentation officielle](/network/delegating) ou [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +Si vous souhaitez en savoir plus sur comment devenir Délégateur, consultez la [documentation officielle](/network/delegating/) ou [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Réseau diff --git a/website/pages/fr/subgraphs/querying/best-practices.mdx b/website/pages/fr/subgraphs/querying/best-practices.mdx index fcd071700739..2b39d903630b 100644 --- a/website/pages/fr/subgraphs/querying/best-practices.mdx +++ b/website/pages/fr/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Chaque `queryName` ne doit être utilisé qu'une seule fois par opération. - Chaque `champ` ne doit être utilisé qu'une seule fois dans une sélection (on ne peut pas interroger `id` deux fois sous `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Toute variable affectée à un argument doit correspondre à son type. - Dans une liste de variables donnée, chacune d’elles doit être unique. - Toutes les variables définies doivent être utilisées. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Gestion des subgraphs inter-chaînes : interrogation à partir de plusieurs subgraphs en une seule requête - [Suivi automatique des blocs](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/fr/subgraphs/querying/graphql-api.mdx b/website/pages/fr/subgraphs/querying/graphql-api.mdx index ddc2030bdef5..61f023ffea88 100644 --- a/website/pages/fr/subgraphs/querying/graphql-api.mdx +++ b/website/pages/fr/subgraphs/querying/graphql-api.mdx @@ -331,7 +331,7 @@ Cette requête renverra les entités `Challenge` et leurs entités `Application` ### Requêtes de recherche en texte intégral -Les champs de requête de recherche en texte intégral fournissent une API de recherche textuelle expressive qui peut être ajoutée au schéma du subgraph et personnalisée. Reportez-vous à [Définition des champs de recherche en texte intégral](/developing/creating-a-subgraph#defining-fulltext-search-fields) pour ajouter la recherche en texte intégral à votre subgraph. +Les champs de requête de recherche en texte intégral fournissent une API de recherche textuelle expressive qui peut être ajoutée au schéma du subgraph et personnalisée. Reportez-vous à [Définition des champs de recherche en texte intégral](/developing/creating-a-subgraph/#defining-fulltext-search-fields) pour ajouter la recherche en texte intégral à votre subgraph. Les champs de requête de recherche en texte `intégral`, fournissent une Api de recherche de texte expressive qui peut être ajoutée au schéma de soubgraph et personnalisée. Reportez-vous à `Définition des champs de recherche en texte intégral` pour ajouter une recherche en texte intégral à votre subgraph. diff --git a/website/pages/fr/subgraphs/querying/introduction.mdx b/website/pages/fr/subgraphs/querying/introduction.mdx index 9e6685937575..6af00953fa3f 100644 --- a/website/pages/fr/subgraphs/querying/introduction.mdx +++ b/website/pages/fr/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Interroger The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/fr/substreams/sps/introduction.mdx b/website/pages/fr/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/fr/substreams/sps/introduction.mdx +++ b/website/pages/fr/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/fr/substreams/sps/triggers.mdx b/website/pages/fr/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/fr/substreams/sps/triggers.mdx +++ b/website/pages/fr/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/fr/supported-networks.mdx b/website/pages/fr/supported-networks.mdx index dc5f6841f6e3..ea91c24d942e 100644 --- a/website/pages/fr/supported-networks.mdx +++ b/website/pages/fr/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Support réseau de base fourni par l' [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Intégration avec Graph Node : `evm`, `near`, `cosmos`, `osmosis` et `ar` sont nativement pris en charge dans Graph Node. Les blockchains compatibles avec Firehose et Substreams peuvent tirer parti de l'intégration généralisée des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs) (ceci inclut les réseaux `evm` et `near` ). ⁠† Prend en charge le déploiement des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs). +\*\* Intégration avec Graph Node : `evm`, `near`, `cosmos`, `osmosis` et `ar` sont nativement pris en charge dans Graph Node. Les blockchains compatibles avec Firehose et Substreams peuvent tirer parti de l'intégration généralisée des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs/) (ceci inclut les réseaux `evm` et `near` ). ⁠† Prend en charge le déploiement des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio repose sur la stabilité et la fiabilité des technologies sous-jacentes, comme les endpoints JSON-RPC, Firehose et Substreams. - Les subgraphs indexant Gnosis Chain peuvent désormais être déployés avec l'identifiant de réseau `gnosis`. diff --git a/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx index 38e6c0e64b2f..f8efa2e9c17e 100644 --- a/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## अपने सबग्राफ को आर्बिट्रम (L2) में कैसे स्थानांतरित करें diff --git a/website/pages/hi/archived/sunrise.mdx b/website/pages/hi/archived/sunrise.mdx index 577e562dd9df..8adee9833853 100644 --- a/website/pages/hi/archived/sunrise.mdx +++ b/website/pages/hi/archived/sunrise.mdx @@ -60,7 +60,7 @@ Edge & Node ने ऐतिहासिक रूप से होस्टे ### यह Subgraph डेवलपर्स को कैसे प्रभावित करता है? -सबग्राफ डेवलपर्स अपने सबग्राफ को The Graph Network पर लगभग तुरंत ही अपग्रेड किए जाने के बाद या [Subgraph Studio से प्रकाशित करने](/publishing/publishing-a-subgraph/) के बाद क्वेरी कर सकते हैं, क्योंकि indexing के लिए कोई लीड टाइम की आवश्यकता नहीं थी। कृपया ध्यान दें कि [सबग्राफ बनाना](/developing/creating-a-subgraph) इस अपग्रेड से प्रभावित नहीं हुआ था। +सबग्राफ डेवलपर्स अपने सबग्राफ को The Graph Network पर लगभग तुरंत ही अपग्रेड किए जाने के बाद या [Subgraph Studio से प्रकाशित करने](/publishing/publishing-a-subgraph/) के बाद क्वेरी कर सकते हैं, क्योंकि indexing के लिए कोई लीड टाइम की आवश्यकता नहीं थी। कृपया ध्यान दें कि [सबग्राफ बनाना](/developing/creating-a-subgraph/) इस अपग्रेड से प्रभावित नहीं हुआ था। ### अपग्रेड Indexer डेटा उपभोक्ताओं को कैसे लाभ पहुंचाता है? diff --git a/website/pages/hi/contracts.mdx b/website/pages/hi/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/hi/contracts.mdx +++ b/website/pages/hi/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/hi/indexing/overview.mdx b/website/pages/hi/indexing/overview.mdx index bae7b6240635..354933160704 100644 --- a/website/pages/hi/indexing/overview.mdx +++ b/website/pages/hi/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### क्वेरी फी कट और इंडेक्सिंग रिवॉर्ड कट क्या है? -`queryFeeCut` और `indexingRewardCut` मान डेलिगेशन पैरामीटर हैं जिन्हें इंडेक्सर और उनके डेलीगेटर्स के बीच GRT के वितरण को नियंत्रित करने के लिए इंडेक्सर cooldownBlocks के साथ सेट कर सकता है। प्रतिनिधिमंडल पैरामीटर सेट करने के निर्देशों के लिए [प्रोटोकॉल में स्टेकिंग](/network/indexing#stake-in-the-protocol) में अंतिम चरण देखें। +`queryFeeCut` और `indexingRewardCut` मान डेलिगेशन पैरामीटर हैं जिन्हें इंडेक्सर और उनके डेलीगेटर्स के बीच GRT के वितरण को नियंत्रित करने के लिए इंडेक्सर cooldownBlocks के साथ सेट कर सकता है। प्रतिनिधिमंडल पैरामीटर सेट करने के निर्देशों के लिए [प्रोटोकॉल में स्टेकिंग](/network/indexing/#stake-in-the-protocol) में अंतिम चरण देखें। - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### एक इंडेक्सर को कौन सी बुनियादी सुरक्षा सावधानियां बरतनी चाहिए? -- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करना एक महत्वपूर्ण एहतियात है क्योंकि यह एक इंडेक्सर को उनकी चाबियों के बीच अलगाव बनाए रखने की अनुमति देता है जो हिस्सेदारी को नियंत्रित करती हैं और जो दिन-प्रतिदिन के संचालन को नियंत्रित करती हैं। निर्देशों के लिए [प्रोटोकॉल में हिस्सेदारी](/network/indexing#stake-in-the-protocol) देखें। +- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करना एक महत्वपूर्ण एहतियात है क्योंकि यह एक इंडेक्सर को उनकी चाबियों के बीच अलगाव बनाए रखने की अनुमति देता है जो हिस्सेदारी को नियंत्रित करती हैं और जो दिन-प्रतिदिन के संचालन को नियंत्रित करती हैं। निर्देशों के लिए [प्रोटोकॉल में हिस्सेदारी](/network/indexing/#stake-in-the-protocol) देखें। - **फ़ायरवॉल** - केवल इंडेक्सर सेवा को सार्वजनिक रूप से प्रदर्शित करने की आवश्यकता है और एडमिन पोर्ट और डेटाबेस एक्सेस को लॉक करने पर विशेष ध्यान दिया जाना चाहिए: ग्राफ़ नोड JSON-RPC समापन बिंदु (डिफ़ॉल्ट पोर्ट): 8030), इंडेक्सर मैनेजमेंट एपीआई एंडपॉइंट (डिफ़ॉल्ट पोर्ट: 18000), और पोस्टग्रेज डेटाबेस एंडपॉइंट (डिफ़ॉल्ट पोर्ट: 5432) को उजागर नहीं किया जाना चाहिए। @@ -375,7 +375,7 @@ docker-compose up #### शुरू करना -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s और टेराफॉर्म का उपयोग करना -[Google क्लाउड पर Terraform का उपयोग करके सेटअप सर्वर इन्फ्रास्ट्रक्चर](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) अनुभाग देखें +[Google क्लाउड पर Terraform का उपयोग करके सेटअप सर्वर इन्फ्रास्ट्रक्चर](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) अनुभाग देखें #### प्रयोग @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -एक बार एक इंडेक्सर प्रोटोकॉल में जीआरटी को दांव पर लगा देता है, तो [इंडेक्सर घटक](/network/indexing#indexer-components) को शुरू किया जा सकता है और नेटवर्क के साथ उनकी बातचीत शुरू की जा सकती है। +एक बार एक इंडेक्सर प्रोटोकॉल में जीआरटी को दांव पर लगा देता है, तो [इंडेक्सर घटक](/network/indexing/#indexer-components) को शुरू किया जा सकता है और नेटवर्क के साथ उनकी बातचीत शुरू की जा सकती है। #### टोकन स्वीकृत करें diff --git a/website/pages/hi/resources/benefits.mdx b/website/pages/hi/resources/benefits.mdx index 2a4bfd334b1a..5df5653274dd 100644 --- a/website/pages/hi/resources/benefits.mdx +++ b/website/pages/hi/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. एक सबग्राफ पर क्यूरेटिंग सिग्नल एक वैकल्पिक वन-टाइम, नेट-जीरो कॉस्ट है (उदाहरण के लिए, सिग्नल में $1k को सबग्राफ पर क्यूरेट किया जा सकता है, और बाद में वापस ले लिया जाता है - प्रक्रिया में रिटर्न अर्जित करने की क्षमता के साथ)। diff --git a/website/pages/hi/resources/roles/curating.mdx b/website/pages/hi/resources/roles/curating.mdx index ed5965d0e5cd..9fbaad030f6d 100644 --- a/website/pages/hi/resources/roles/curating.mdx +++ b/website/pages/hi/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## सिग्नल कैसे करें -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) एक क्यूरेटर एक विशिष्ट सबग्राफ संस्करण पर संकेत देना चुन सकता है, या वे अपने सिग्नल को स्वचालित रूप से उस सबग्राफ के नवीनतम उत्पादन निर्माण में माइग्रेट करना चुन सकते हैं। दोनों मान्य रणनीतियाँ हैं और अपने स्वयं के पेशेवरों और विपक्षों के साथ आती हैं। @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. क्वेरी बाजार द ग्राफ में स्वाभाविक रूप से युवा है और इसमें जोखिम है कि नवजात बाजार की गतिशीलता के कारण आपका %APY आपकी अपेक्षा से कम हो सकता है। 2. क्यूरेशन शुल्क - जब कोई क्यूरेटर किसी सबग्राफ़ पर GRT सिग्नल करता है, तो उसे 1% क्यूरेशन टैक्स देना होता है। यह शुल्क जला दिया जाता है। -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. बग के कारण सबग्राफ विफल हो सकता है। एक विफल सबग्राफ क्वेरी शुल्क अर्जित नहीं करता है। नतीजतन, आपको तब तक इंतजार करना होगा जब तक कि डेवलपर बग को ठीक नहीं करता है और एक नया संस्करण तैनात करता है। - यदि आपने सबग्राफ के नवीनतम संस्करण की सदस्यता ली है, तो आपके शेयर उस नए संस्करण में स्वत: माइग्रेट हो जाएंगे। इस पर 0.5% क्यूरेशन टैक्स लगेगा। - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/hi/subgraphs/cookbook/grafting.mdx b/website/pages/hi/subgraphs/cookbook/grafting.mdx index 2225f5cacb01..fde8a5b6d9ac 100644 --- a/website/pages/hi/subgraphs/cookbook/grafting.mdx +++ b/website/pages/hi/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ title: एक कॉन्ट्रैक्ट बदलें और उसक अधिक जानकारी के लिए आप देख सकते हैं: -- [ग्राफ्टिंग](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [ग्राफ्टिंग](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) इस ट्यूटोरियल में, हम एक बुनियादी उपयोग मामले को कवर करेंगे। हम एक मौजूदा कॉन्ट्रैक्ट को एक समान कॉन्ट्रैक्ट (नए पते के साथ, लेकिन वही कोड) से बदलेंगे। फिर, मौजूदा Subgraph को "बेस" Subgraph पर जोड़ेंगे, जो नए कॉन्ट्रैक्ट को ट्रैक करता है। diff --git a/website/pages/hi/subgraphs/cookbook/near.mdx b/website/pages/hi/subgraphs/cookbook/near.mdx index df507a2c7efb..cecf15ff902a 100644 --- a/website/pages/hi/subgraphs/cookbook/near.mdx +++ b/website/pages/hi/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ NEAR सबग्राफ डेवलपमेंट के लिए `graph-c **subgraph.yaml:** सबग्राफ मेनिफेस्ट, रुचि के डेटा स्रोतों को परिभाषित करता है, और उन्हें कैसे संसाधित किया जाना चाहिए। NEAR डेटा स्रोत का `प्रकार` है। -**schema.graphql:** एक स्कीमा फ़ाइल जो परिभाषित करती है कि आपके सबग्राफ के लिए कौन सा डेटा इकट्ठा होगा, और इसे ग्राफ़क्यूएल के माध्यम से कैसे क्वेरी करें। NEAR सबग्राफ की आवश्यकताएं [मौजूदा दस्तावेज़ीकरण](/Developing/creating-a-subgraph#the-graphql-schema) द्वारा कवर की गई हैं। +**schema.graphql:** एक स्कीमा फ़ाइल जो परिभाषित करती है कि आपके सबग्राफ के लिए कौन सा डेटा इकट्ठा होगा, और इसे ग्राफ़क्यूएल के माध्यम से कैसे क्वेरी करें। NEAR सबग्राफ की आवश्यकताएं [मौजूदा दस्तावेज़ीकरण](/Developing/creating-a-subgraph/#the-graphql-schema) द्वारा कवर की गई हैं। -**AssemblyScript मापिंग:** [AssemblyScript कोड](/developing/graph-ts/api) जो घटना डेटा को आपकी स्कीमा में परिभाषित संस्थाओं में अनुवादित करता है। NEAR समर्थन NEAR-विशिष्ट डेटा प्रकार और नई JSON पार्सिंग कार्यक्षमता पेश करता है। +**AssemblyScript मापिंग:** [AssemblyScript कोड](/developing/graph-ts/api/) जो घटना डेटा को आपकी स्कीमा में परिभाषित संस्थाओं में अनुवादित करता है। NEAR समर्थन NEAR-विशिष्ट डेटा प्रकार और नई JSON पार्सिंग कार्यक्षमता पेश करता है। सबग्राफ डेवलपमेंट के दौरान दो प्रमुख कमांड होते हैं: @@ -92,13 +92,13 @@ NEAR डेटा स्रोत दो प्रकार के हैंड ### स्कीमा परिभाषा -स्कीमा परिभाषा परिणामी सबग्राफ डेटाबेस की संरचना और संस्थाओं के बीच संबंधों का वर्णन करती है। यह मूल डेटा स्रोत का अज्ञेयवादी है। सबग्राफ स्कीमा परिभाषा [यहां](/Developing/creating-a-subgraph#the-graphql-schema) पर अधिक विवरण हैं। +स्कीमा परिभाषा परिणामी सबग्राफ डेटाबेस की संरचना और संस्थाओं के बीच संबंधों का वर्णन करती है। यह मूल डेटा स्रोत का अज्ञेयवादी है। सबग्राफ स्कीमा परिभाषा [यहां](/Developing/creating-a-subgraph/#the-graphql-schema) पर अधिक विवरण हैं। ### असेंबलीस्क्रिप्ट मैपिंग्स इवेंट को प्रोसेस करने के लिए हैंडलर [AssemblyScript](https://www.assemblyscript.org/) में लिखे होते हैं। -NEAR indexing 'NEAR' के लिए विशिष्ट डेटा प्रकारों को [AssemblyScript API](/developing/graph-ts/api) में पेश करता है। +NEAR indexing 'NEAR' के लिए विशिष्ट डेटा प्रकारों को [AssemblyScript API](/developing/graph-ts/api/) में पेश करता है। ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - ब्लॉक हैंडलर्स को एक `ब्लॉक` प्राप्त होगा - रसीद संचालकों को `ReceiptWithOutcome` प्राप्त होगा -अन्यथा, [AssemblyScript API](/developing/graph-ts/api) का शेष भाग NEAR subgraph डेवलपर्स के लिए मैपिंग निष्पादन के दौरान उपलब्ध है। +अन्यथा, [AssemblyScript API](/developing/graph-ts/api/) का शेष भाग NEAR subgraph डेवलपर्स के लिए मैपिंग निष्पादन के दौरान उपलब्ध है। -यह एक नई JSON पार्सिंग फ़ंक्शन को शामिल करता है - NEAR पर लॉग अक्सर स्ट्रिंगिफाइड JSONs के रूप में उत्पन्न होते हैं। एक नई `json.fromString(...)` फ़ंक्शन [JSON API](/developing/graph-ts/api#json-api) का हिस्सा के रूप में उपलब्ध है, जिससे डेवलपर्स इन लॉग्स को आसानी से प्रोसेस कर सकते हैं। +यह एक नई JSON पार्सिंग फ़ंक्शन को शामिल करता है - NEAR पर लॉग अक्सर स्ट्रिंगिफाइड JSONs के रूप में उत्पन्न होते हैं। एक नई `json.fromString(...)` फ़ंक्शन [JSON API](/developing/graph-ts/api/#json-api) का हिस्सा के रूप में उपलब्ध है, जिससे डेवलपर्स इन लॉग्स को आसानी से प्रोसेस कर सकते हैं। ## एक NEAR सबग्राफ की तैनाती @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ NEAR को अनुक्रमित करने वाले ग्रा ## NEAR सबग्राफ को क्वेरी करना -NEAR सबग्राफ के लिए ग्राफक्यूएल एंडपॉइंट मौजूदा एपीआई इंटरफेस के साथ स्कीमा परिभाषा द्वारा निर्धारित किया जाता है। अधिक जानकारी के लिए कृपया [GraphQL API दस्तावेज़ीकरण](/querying/graphql-api) पर जाएं। +NEAR सबग्राफ के लिए ग्राफक्यूएल एंडपॉइंट मौजूदा एपीआई इंटरफेस के साथ स्कीमा परिभाषा द्वारा निर्धारित किया जाता है। अधिक जानकारी के लिए कृपया [GraphQL API दस्तावेज़ीकरण](/querying/graphql-api/) पर जाएं। ## उदाहरण सबग्राफ diff --git a/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx index 9d914991e327..bcf85bba922e 100644 --- a/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: असेंबलीस्क्रिप्ट एपीआई --- -> ध्यान दें: यदि आपने `graph-cli`/`graph-ts` version `0.22.0` से पहले एक subgragh बनाया है, तो आप AssemblyScript के पुराना संस्करण का उपयोग कर रहे हैं, हम अनुशंसा करते हैं कि [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> ध्यान दें: यदि आपने `graph-cli`/`graph-ts` version `0.22.0` से पहले एक subgragh बनाया है, तो आप AssemblyScript के पुराना संस्करण का उपयोग कर रहे हैं, हम अनुशंसा करते हैं कि [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). यह पृष्ठ दस्तावेज करता है कि Subgraph मैपिंग लिखते समय किन अंतर्निहित एपीआई का उपयोग किया जा सकता है। बॉक्स से बाहर दो प्रकार के एपीआई उपलब्ध हैं: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx index 1438848807bd..f4ddd954e659 100644 --- a/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | संस्करण | रिलीज नोट्स | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx b/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx index cc56484e1fb3..cf6786579c03 100644 --- a/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/hi/subgraphs/developing/developer-faq.mdx b/website/pages/hi/subgraphs/developing/developer-faq.mdx index b335b8eb8867..a035e4064eb8 100644 --- a/website/pages/hi/subgraphs/developing/developer-faq.mdx +++ b/website/pages/hi/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ AssemblyScript में वर्तमान में मैपिंग् Templates आपको डेटा स्रोतों को तेजी से बनाने की अनुमति देते हैं, जबकि आपका subgraph इंडेक्सिंग कर रहा है। आपका कॉन्ट्रैक्ट नए कॉन्ट्रैक्ट उत्पन्न कर सकता है जब लोग इसके साथ इंटरैक्ट करते हैं। चूंकि आप उन कॉन्ट्रैक्टों का आकार (ABI, इवेंट, आदि) पहले से जानते हैं, आप यह निर्धारित कर सकते हैं कि आप उन्हें एक टेम्पलेट में कैसे इंडेक्स करना चाहते हैं। जब वे उत्पन्न होते हैं, तो आपका subgraph कॉन्ट्रैक्ट पते को प्रदान करके एक डायनामिक डेटा स्रोत बनाएगा। -"डेटा स्रोत टेम्प्लेट को तत्काल बनाना" अनुभाग देखें: [डेटा स्रोत टेम्प्लेट](/developing/creating-a-subgraph#data-source-templates)। +"डेटा स्रोत टेम्प्लेट को तत्काल बनाना" अनुभाग देखें: [डेटा स्रोत टेम्प्लेट](/developing/creating-a-subgraph/#data-source-templates)। ### 11. क्या `graph init` का उपयोग करके `graph-cli` से एक subgraph सेट करना संभव है जिसमें दो कॉन्ट्रैक्ट हैं? या मुझे `graph init` चलाने के बाद `subgraph.yaml` में एक और dataSource मैन्युअल रूप से जोड़ना चाहिए? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. The Graph द्वारा समर्थित नेटवर्क कौन से हैं? -आप समर्थित नेटवर्क की सूची [यहां](/Developing/supported-networks) प्राप्त कर सकते हैं। +आप समर्थित नेटवर्क की सूची [यहां](/Developing/supported-networks/) प्राप्त कर सकते हैं। ### 17. क्या इवेंट हैंडलर्स के भीतर नेटवर्क (mainnet, Sepolia, local) के बीच अंतर करना संभव है? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. क्या यह संभव है कि किस ब्लॉक से इंडेक्सिंग शुरू की जाए? -`dataSources.source.startBlock` `subgraph.yaml` फ़ाइल में उस ब्लॉक का नंबर निर्दिष्ट करता है जिससे dataSource डेटा इंडेक्स करना शुरू करता है। अधिकांश मामलों में, हम अनुशंसा करते हैं कि उस ब्लॉक का उपयोग करें जहाँ अनुबंध बनाया गया था: [Start blocks](/developing/creating-a-subgraph#start-blocks) +`dataSources.source.startBlock` `subgraph.yaml` फ़ाइल में उस ब्लॉक का नंबर निर्दिष्ट करता है जिससे dataSource डेटा इंडेक्स करना शुरू करता है। अधिकांश मामलों में, हम अनुशंसा करते हैं कि उस ब्लॉक का उपयोग करें जहाँ अनुबंध बनाया गया था: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. यहां कुछ सुझाव दिए गए हैं ताकि इंडेक्सिंग का प्रदर्शन बढ़ सके। मेरा subgraph बहुत लंबे समय तक सिंक होने में समय ले रहा है। -आपको वैकल्पिक 'स्टार्ट ब्लॉक' विशेषता पर एक नज़र डालनी चाहिए ताकि आप उस ब्लॉक से अनुक्रमण शुरू कर सकें जहां अनुबंध को तैनात किया गया था: [Start blocks](/developing/creating-a-subgraph#start-blocks) +आपको वैकल्पिक 'स्टार्ट ब्लॉक' विशेषता पर एक नज़र डालनी चाहिए ताकि आप उस ब्लॉक से अनुक्रमण शुरू कर सकें जहां अनुबंध को तैनात किया गया था: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. क्या कोई तरीका है कि 'subgraph' को सीधे क्वेरी करके यह पता लगाया जा सके कि उसने कौन सा लेटेस्ट ब्लॉक नंबर इंडेक्स किया है? diff --git a/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx index dfeec280edfc..2e1bc7f60474 100644 --- a/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: विकेंद्रीकृत नेटवर्क के लिए एक सबग्राफ प्रकाशित करना --- -आपके द्वारा [Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) पर 'subgraph' को तैनात करने के बाद और यह उत्पादन के लिए तैयार हो जाने पर, आप इसे विकेंद्रीकृत नेटवर्क पर प्रकाशित कर सकते हैं। +आपके द्वारा [Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) पर 'subgraph' को तैनात करने के बाद और यह उत्पादन के लिए तैयार हो जाने पर, आप इसे विकेंद्रीकृत नेटवर्क पर प्रकाशित कर सकते हैं। जब आप एक subgraph को विकेंद्रीकृत नेटवर्क पर प्रकाशित करते हैं, तो आप इसे उपलब्ध कराते हैं: -- [Curators](/network/curating) को इसे क्यूरेट करना शुरू करने के लिए। -- [Indexers](/network/indexing) को इसे इंडेक्स करना शुरू करने के लिए। +- [Curators](/network/curating/) को इसे क्यूरेट करना शुरू करने के लिए। +- [Indexers](/network/indexing/) को इसे इंडेक्स करना शुरू करने के लिए। -नीचे दिए गए [supported networks](/developing/supported-networks) की सूची देखें। +नीचे दिए गए [supported networks](/developing/supported-networks/) की सूची देखें। ## Subgraph Studio से प्रकाशित @@ -21,9 +21,9 @@ title: विकेंद्रीकृत नेटवर्क के लि एक मौजूदा subgraph के सभी प्रकाशित संस्करण कर सकते हैं: -- Arbitrum One पर प्रकाशित करें। [Arbitrum पर The Graph Network के बारे में अधिक जानें](/arbitrum/arbitrum-faq)। +- Arbitrum One पर प्रकाशित करें। [Arbitrum पर The Graph Network के बारे में अधिक जानें](/arbitrum/arbitrum-faq/)। -- किसी भी [समर्थित नेटवर्क](/developing/supported-networks) पर डेटा इंडेक्स करें, चाहे वह नेटवर्क हो जिस पर subgraph प्रकाशित किया गया था। +- किसी भी [समर्थित नेटवर्क](/developing/supported-networks/) पर डेटा इंडेक्स करें, चाहे वह नेटवर्क हो जिस पर subgraph प्रकाशित किया गया था। ### प्रकाशित सबग्राफ के लिए मेटाडेटा अपडेट करना @@ -68,7 +68,7 @@ FLAGS - आप उपग्राफ फीचर उपयोग के आधार पर इंडेक्सिंग पुरस्कार पात्रता की जांच [यहाँ](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) कर सकते हैं। -- विशिष्ट समर्थित नेटवर्क की जांच [यहाँ](/developing/supported-networks) की जा सकती है। +- विशिष्ट समर्थित नेटवर्क की जांच [यहाँ](/developing/supported-networks/) की जा सकती है। > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/hi/subgraphs/explorer.mdx b/website/pages/hi/subgraphs/explorer.mdx index 286482ca5268..5179d4b377e2 100644 --- a/website/pages/hi/subgraphs/explorer.mdx +++ b/website/pages/hi/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers दोनों क्वेरी फीस और इंडेक् - इंडेक्सिंग पैरामीटर को टेबल के दाहिने ओर क्लिक करके या किसी इंडेक्सर के प्रोफ़ाइल में जाकर 'Delegate' बटन पर क्लिक करके सेट किया जा सकता है। -इंडेक्सर कैसे बनें, इस बारे में अधिक जानने के लिए, आप [आधिकारिक दस्तावेज़ीकरण](/network/indexing) या [द ग्राफ एकेडमी इंडेक्सर गाइड्स।](https://thegraph.academy/delegators/ पर नज़र डाल सकते हैं चूइंग-इंडेक्सर्स/) +इंडेक्सर कैसे बनें, इस बारे में अधिक जानने के लिए, आप [आधिकारिक दस्तावेज़ीकरण](/network/indexing/) या [द ग्राफ एकेडमी इंडेक्सर गाइड्स।](https://thegraph.academy/delegators/ पर नज़र डाल सकते हैं चूइंग-इंडेक्सर्स/) ![अनुक्रमण विवरण फलक](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ Indexers दोनों क्वेरी फीस और इंडेक् ![एक्सप्लोरर छवि 6](/img/Curation-Overview.png) -अगर आप 'Curator' भूमिका के बारे में अधिक जानना चाहते हैं, तो आप ऐसा कर सकते हैं, यहाँ पर जाएं: [official documentation.](/network/curating) या [The Graph Academy](https://thegraph.academy/curators/). +अगर आप 'Curator' भूमिका के बारे में अधिक जानना चाहते हैं, तो आप ऐसा कर सकते हैं, यहाँ पर जाएं: [official documentation.](/network/curating/) या [The Graph Academy](https://thegraph.academy/curators/). ### 3. प्रतिनिधि @@ -113,7 +113,7 @@ Delegators तालिका में आप समुदाय में स - वर्तमान में उनके पास प्रोटोकॉल में जीआरटी की कुल राशि है - वे आखिरी बार 'delegated' की तारीख -यदि आप Delegator बनने के बारे में अधिक जानना चाहते हैं, तो [आधिकारिक दस्तावेज़](/network/delegating) देखें या [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) पर जाएं। +यदि आप Delegator बनने के बारे में अधिक जानना चाहते हैं, तो [आधिकारिक दस्तावेज़](/network/delegating/) देखें या [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) पर जाएं। ## नेटवर्क diff --git a/website/pages/hi/subgraphs/querying/best-practices.mdx b/website/pages/hi/subgraphs/querying/best-practices.mdx index 8480616c578f..6f0a4716b025 100644 --- a/website/pages/hi/subgraphs/querying/best-practices.mdx +++ b/website/pages/hi/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - प्रत्येक `क्वेरीनाम` का उपयोग प्रति ऑपरेशन केवल एक बार किया जाना चाहिए। - प्रत्येक `फ़ील्ड` का चयन में केवल एक बार उपयोग किया जाना चाहिए (हम `आईडी` को `टोकन` के अंतर्गत दो बार क्वेरी नहीं कर सकते हैं) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - किसी तर्क को असाइन किया गया कोई भी चर उसके प्रकार से मेल खाना चाहिए। - चरों की दी गई सूची में, उनमें से प्रत्येक अद्वितीय होना चाहिए। - सभी परिभाषित चर का उपयोग किया जाना चाहिए। @@ -69,7 +69,7 @@ GraphQL एक भाषा और प्रथाओं का सेट है इसका मतलब है कि आप एक GraphQL API को मानक `fetch` (स्थानीय रूप से या `@whatwg-node/fetch` या `isomorphic-fetch` के माध्यम से) का उपयोग करके क्वेरी कर सकते हैं। -हालांकि, जैसा कि [“Querying from an Application”](/querying/querying-from-an-application) में उल्लेख किया गया है, यह अनुशंसा की जाती है कि आप `graph-client` का उपयोग करें, जो निम्नलिखित अद्वितीय विशेषताओं का समर्थन करता है: +हालांकि, जैसा कि [“Querying from an Application”](/querying/querying-from-an-application/) में उल्लेख किया गया है, यह अनुशंसा की जाती है कि आप `graph-client` का उपयोग करें, जो निम्नलिखित अद्वितीय विशेषताओं का समर्थन करता है: - क्रॉस-चेन सबग्राफ हैंडलिंग: एक ही क्वेरी में कई सबग्राफ से पूछताछ - [स्वचालित ब्लॉक ट्रैकिंग](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -अधिक GraphQL क्लाइंट विकल्पों को [“Querying from an Application”](/querying/querying-from-an-application) में कवर किया गया है। +अधिक GraphQL क्लाइंट विकल्पों को [“Querying from an Application”](/querying/querying-from-an-application/) में कवर किया गया है। --- diff --git a/website/pages/hi/subgraphs/querying/graphql-api.mdx b/website/pages/hi/subgraphs/querying/graphql-api.mdx index 999a29b08e1a..6af99067b807 100644 --- a/website/pages/hi/subgraphs/querying/graphql-api.mdx +++ b/website/pages/hi/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ You can query the state of your entities not just for the latest block, which is ### पूर्ण पाठ खोज प्रश्न -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. शब्दों की आपूर्ति के लिए पूर्ण पाठ्य अन्वेषण में एक आवश्यक क्षेत्र `पाठ` है। इस `पाठ` खोज क्षेत्र में उपयोग करने के लिए कई विशेष पूर्ण-पाठ पत्र उपलब्ध हैं। diff --git a/website/pages/hi/subgraphs/querying/introduction.mdx b/website/pages/hi/subgraphs/querying/introduction.mdx index 5e1b2bb344f4..4ea0563584d3 100644 --- a/website/pages/hi/subgraphs/querying/introduction.mdx +++ b/website/pages/hi/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: ग्राफ़ को क्वेरी करना When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/hi/supported-networks.mdx b/website/pages/hi/supported-networks.mdx index 1f54bddd05cd..fc8166f0653f 100644 --- a/website/pages/hi/supported-networks.mdx +++ b/website/pages/hi/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - सबग्राफ स्टूडियो निर्भर करता है अंतर्निहित प्रौद्योगिकियों की स्थिरता और विश्वसनीयता पर, जैसे JSON-RPC, फायरहोस और सबस्ट्रीम्स एंडपॉइंट्स। - Gnosis Chain पर सबग्राफ इंडेक्सिंग को अब `gnosis` नेटवर्क पहचानकर्ता (network identifier) के साथ डिप्लॉय किया जा सकता है। diff --git a/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx index 5ba89020402c..e516573fd4d9 100644 --- a/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/it/archived/sunrise.mdx b/website/pages/it/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/it/archived/sunrise.mdx +++ b/website/pages/it/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/it/contracts.mdx b/website/pages/it/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/it/contracts.mdx +++ b/website/pages/it/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/it/indexing/new-chain-integration.mdx b/website/pages/it/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/it/indexing/new-chain-integration.mdx +++ b/website/pages/it/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/it/indexing/overview.mdx b/website/pages/it/indexing/overview.mdx index 3b449dc021fa..e7ed427ea8ef 100644 --- a/website/pages/it/indexing/overview.mdx +++ b/website/pages/it/indexing/overview.mdx @@ -87,7 +87,7 @@ Una volta chiusa un'allocation, gli sconti possono essere richiesti dall'Indexer ### Che cos'è la query fee cut e la indexing reward cut? -I valori di `queryFeeCut` e `indexingRewardCut` sono parametri di delega che l'Indexer può impostare insieme ai cooldownBlocks per controllare la distribuzione dei GRT tra l'Indexer i suoi Delegator. Per le istruzioni sull'impostazione dei parametri di delega, si vedano gli ultimi passi di [Staking nel Protocollo](/network/indexing#stake-in-the-protocol). +I valori di `queryFeeCut` e `indexingRewardCut` sono parametri di delega che l'Indexer può impostare insieme ai cooldownBlocks per controllare la distribuzione dei GRT tra l'Indexer i suoi Delegator. Per le istruzioni sull'impostazione dei parametri di delega, si vedano gli ultimi passi di [Staking nel Protocollo](/network/indexing/#stake-in-the-protocol). - **queryFeeCut** - la % delle riduzioni delle tariffe di query che verrà distribuita all'Indexer. Se questa opzione è impostata al 95%, l'Indexer riceverà il 95% delle tariffe di query guadagnate alla chiusura di un'allocazione, mentre il restante 5% andrà ai Delegator. @@ -121,7 +121,7 @@ Gli Indexer possono differenziarsi applicando tecniche avanzate per prendere dec ### Quali sono le precauzioni di base per la sicurezza che un Indexer dovrebbe adottare? -- **Operator wallet** - La creazione di un operator wallet è una precauzione importante perché consente all'Indexer di mantenere una separazione tra le chiavi che controllano il stake e quelle che controllano le operazioni quotidiane. Vedere[ Stake al protocollo](/network/indexing#stake-in-the-protocol) per le istruzioni. +- **Operator wallet** - La creazione di un operator wallet è una precauzione importante perché consente all'Indexer di mantenere una separazione tra le chiavi che controllano il stake e quelle che controllano le operazioni quotidiane. Vedere[ Stake al protocollo](/network/indexing/#stake-in-the-protocol) per le istruzioni. - **Firewall** - Solo l'Indexer service deve essere esposto pubblicamente e occorre prestare particolare attenzione a bloccare le porte di amministrazione e l'accesso al database: l'endpoint JSON-RPC di the Graph Node (porta predefinita: 8030), l'endpoint API di gestione dell'Indexer (porta predefinita: 18000) e l'endpoint del database Postgres (porta predefinita: 5432) non devono essere esposti. @@ -375,7 +375,7 @@ Per partecipare con successo alla rete è necessario un monitoraggio e un'intera #### Per cominciare -L'Indexer Agent ed l'Indexer service devono essere collocati insieme all'infrastruttura di The Graph Node. Ci sono molti modi per impostare ambienti di esecuzione virtuali per i componenti di Indexer; qui spiegheremo come eseguirli su baremetal usando pacchetti NPM o sorgenti, oppure tramite kubernetes e docker su Google Cloud Kubernetes Engine. Se questi esempi di configurazione non si adattano bene alla vostra infrastruttura, è probabile che ci sia una community guide a cui fare riferimento; fate un salto su [Discord](https://discord.gg/graphprotocol)! Ricordatevi di fare [stake nel protocollo](/network/indexing#stake-in-the-protocol) prima di avviare i componenti dell'Indexer! +L'Indexer Agent ed l'Indexer service devono essere collocati insieme all'infrastruttura di The Graph Node. Ci sono molti modi per impostare ambienti di esecuzione virtuali per i componenti di Indexer; qui spiegheremo come eseguirli su baremetal usando pacchetti NPM o sorgenti, oppure tramite kubernetes e docker su Google Cloud Kubernetes Engine. Se questi esempi di configurazione non si adattano bene alla vostra infrastruttura, è probabile che ci sia una community guide a cui fare riferimento; fate un salto su [Discord](https://discord.gg/graphprotocol)! Ricordatevi di fare [stake nel protocollo](/network/indexing/#stake-in-the-protocol) prima di avviare i componenti dell'Indexer! #### Dai pacchetti NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Utilizzo di K8s e Terraform -Vedere la sezione [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Vedere la sezione [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Utilizzo @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Una volta che l'Indexer ha messo in staking i GRT nel protocollo, gli [Indexer components](/network/indexing#indexer-components) possono essere avviati e iniziare le loro interazioni con la rete. +Una volta che l'Indexer ha messo in staking i GRT nel protocollo, gli [Indexer components](/network/indexing/#indexer-components) possono essere avviati e iniziare le loro interazioni con la rete. #### Approvare i token diff --git a/website/pages/it/resources/benefits.mdx b/website/pages/it/resources/benefits.mdx index a3ffbeefeccb..8a3869a26c8c 100644 --- a/website/pages/it/resources/benefits.mdx +++ b/website/pages/it/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. La curation del segnale su un subgraph è opzionale, una tantum, a costo zero (ad esempio, $1.000 in segnale possono essere curati su un subgraph e successivamente ritirati, con un potenziale di guadagno nel processo). diff --git a/website/pages/it/resources/roles/curating.mdx b/website/pages/it/resources/roles/curating.mdx index b7c0039f86b9..7ee7f33834e6 100644 --- a/website/pages/it/resources/roles/curating.mdx +++ b/website/pages/it/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Come segnalare -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) Un curator può scegliere di segnalare su una versione specifica del subgraph, oppure può scegliere di far migrare automaticamente il proprio segnale alla versione di produzione più recente di quel subgraph. Entrambe le strategie sono valide e hanno i loro pro e contro. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Il mercato delle query è intrinsecamente giovane per The Graph e c'è il rischio che la vostra %APY possa essere inferiore a quella prevista a causa delle dinamiche di mercato nascenti. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Un subgraph può fallire a causa di un bug. Un subgraph fallito non matura commissioni della query. Di conseguenza, si dovrà attendere che lo sviluppatore risolva il bug e distribuisca una nuova versione. - Se siete iscritti alla versione più recente di un subgraph, le vostre quote di partecipazione migreranno automaticamente a quella nuova versione. Questo comporta una tassa di curation di 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/it/subgraphs/cookbook/grafting.mdx b/website/pages/it/subgraphs/cookbook/grafting.mdx index d6c443a46538..d5ab9bbbc47a 100644 --- a/website/pages/it/subgraphs/cookbook/grafting.mdx +++ b/website/pages/it/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ Il grafted subgraph può utilizzare uno schema GraphQL non identico a quello del For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/it/subgraphs/cookbook/near.mdx b/website/pages/it/subgraphs/cookbook/near.mdx index a15966136fb9..f1d61e913ca5 100644 --- a/website/pages/it/subgraphs/cookbook/near.mdx +++ b/website/pages/it/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx index 502644810be8..a1bafe444daa 100644 --- a/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: API AssemblyScript --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ La `apiVersion` nel manifest del subgraph specifica la versione dell'API di mapp | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Aggiunte le classi `TransactionReceipt` e `Log` ai tipi di Ethereum
Aggiunto il campo `receipt` all'oggetto Ethereum Event | | 0.0.6 | Aggiunto il campo `nonce` all'oggetto Ethereum Transaction
Aggiunto `baseFeePerGas` all'oggetto Ethereum Block | -| 0.0.5 | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` | | 0.0.4 | Aggiunto il campo `functionSignature` all'oggetto Ethereum SmartContractCall | | 0.0.3 | Aggiunto il campo `from` all'oggetto Ethereum Call
`etherem.call.address` rinominato in `ethereum.call.to` | | 0.0.2 | Aggiunto il campo `input` all'oggetto Ethereum Transaction | diff --git a/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx index ea35b67fb8e3..bc62da7231bc 100644 --- a/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ I file ABI devono corrispondere al vostro contratto. Esistono diversi modi per o | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/it/subgraphs/developing/creating/ql-schema.mdx b/website/pages/it/subgraphs/developing/creating/ql-schema.mdx index 74c9f4274cf2..eac7c291bb70 100644 --- a/website/pages/it/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/it/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/it/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/it/subgraphs/developing/deploying/multiple-networks.mdx index a9385c5e1509..0bcbe1eddc43 100644 --- a/website/pages/it/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/it/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Distribuzione del subgraph su più reti diff --git a/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx index 5d36bc2e669a..d0921b13e966 100644 --- a/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Non deve utilizzare nessuna delle seguenti funzioni: - ipfs.cat & ipfs.map - Errori non fatali diff --git a/website/pages/it/subgraphs/developing/developer-faq.mdx b/website/pages/it/subgraphs/developing/developer-faq.mdx index 244aae52d0f4..85dccad933b0 100644 --- a/website/pages/it/subgraphs/developing/developer-faq.mdx +++ b/website/pages/it/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 558cc552b6e5..485a77da47ea 100644 --- a/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Pubblicare un subgraph nella rete decentralizzata --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Aggiornamento dei metadati per un subgraph pubblicato @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/it/subgraphs/explorer.mdx b/website/pages/it/subgraphs/explorer.mdx index 662aa790d17a..7908d3ee7496 100644 --- a/website/pages/it/subgraphs/explorer.mdx +++ b/website/pages/it/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Per saperne di più su come diventare un Indexer, è possibile consultare la [documentazione ufficiale](/network/indexing) oppure [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +Per saperne di più su come diventare un Indexer, è possibile consultare la [documentazione ufficiale](/network/indexing/) oppure [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Pannello dei dettagli di indicizzazione](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegator @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Quantità totale di GRT che hanno attualmente nel protocollo - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## La rete diff --git a/website/pages/it/subgraphs/querying/best-practices.mdx b/website/pages/it/subgraphs/querying/best-practices.mdx index cdfe37cd6e51..a0eb269cc5fc 100644 --- a/website/pages/it/subgraphs/querying/best-practices.mdx +++ b/website/pages/it/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Ogni `queryName` deve essere usato una sola volta per ogni operazione. - Ogni `field` deve essere utilizzato una sola volta in una selezione (non si può effettuare query di `id` due volte sotto `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Qualsiasi variabile assegnata a un argomento deve corrispondere al suo tipo. - In un determinato elenco di variabili, ciascuna di esse deve essere unica. - Tutte le variabili definite devono essere utilizzate. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Gestione dei subgraph a cross-chain: effettuare query di più subgraph in un'unica query - [Tracciamento automatico dei blocchi](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/it/subgraphs/querying/graphql-api.mdx b/website/pages/it/subgraphs/querying/graphql-api.mdx index 39369363a1d5..ba99bf940a81 100644 --- a/website/pages/it/subgraphs/querying/graphql-api.mdx +++ b/website/pages/it/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ Questa query restituirà le entità `Challenge` e le entità `Application` ad es ### Query di ricerca fulltext -I campi di ricerca fulltext forniscono un'API di ricerca testuale espressiva che può essere aggiunta allo schema del subgraph e personalizzata. Fare riferimento a [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) per aggiungere la ricerca fulltext al subgraph. +I campi di ricerca fulltext forniscono un'API di ricerca testuale espressiva che può essere aggiunta allo schema del subgraph e personalizzata. Fare riferimento a [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) per aggiungere la ricerca fulltext al subgraph. Le query di ricerca fulltext hanno un campo obbligatorio, `text`, per fornire i termini di ricerca. In questo campo di ricerca `text` sono disponibili diversi operatori speciali per il fulltext. diff --git a/website/pages/it/subgraphs/querying/introduction.mdx b/website/pages/it/subgraphs/querying/introduction.mdx index d139dfe55258..a378ce4062ae 100644 --- a/website/pages/it/subgraphs/querying/introduction.mdx +++ b/website/pages/it/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Effettuare query di The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/it/substreams/sps/introduction.mdx b/website/pages/it/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/it/substreams/sps/introduction.mdx +++ b/website/pages/it/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/it/substreams/sps/triggers.mdx b/website/pages/it/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/it/substreams/sps/triggers.mdx +++ b/website/pages/it/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/it/supported-networks.mdx b/website/pages/it/supported-networks.mdx index 797202065e99..9e47f25c86e6 100644 --- a/website/pages/it/supported-networks.mdx +++ b/website/pages/it/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx index 7f9cebc80912..357b116b5639 100644 --- a/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 転送ツールガイド グラフにより、アービトラムワンのL2に簡単に移動できるようになりました。プロトコル参加者ごとに、すべてのネットワーク参加者が L2 への転送をシームレスに行うための L2 転送ツールのセットがあります。これらのツールでは、転送する内容に応じて、特定の一連の手順に従う必要があります。 -これらのツールに関するよくある質問は、[L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq) で回答されています。FAQには、ツールの使用方法、機能、およびツールを使用する際の注意事項に関する詳細な説明が含まれています。 +これらのツールに関するよくある質問は、[L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/) で回答されています。FAQには、ツールの使用方法、機能、およびツールを使用する際の注意事項に関する詳細な説明が含まれています。 ## サブグラフをアービトラムに転送する方法 (L2) diff --git a/website/pages/ja/archived/sunrise.mdx b/website/pages/ja/archived/sunrise.mdx index 5955cec07911..e52305674f86 100644 --- a/website/pages/ja/archived/sunrise.mdx +++ b/website/pages/ja/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ja/contracts.mdx b/website/pages/ja/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/ja/contracts.mdx +++ b/website/pages/ja/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ja/indexing/new-chain-integration.mdx b/website/pages/ja/indexing/new-chain-integration.mdx index ce4d66cccdc7..4c1c6fa51572 100644 --- a/website/pages/ja/indexing/new-chain-integration.mdx +++ b/website/pages/ja/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Nodeはエラーがない場合、デプロイされたサブグラフを ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ja/indexing/overview.mdx b/website/pages/ja/indexing/overview.mdx index 54d5a7c19f23..d05965769e76 100644 --- a/website/pages/ja/indexing/overview.mdx +++ b/website/pages/ja/indexing/overview.mdx @@ -87,7 +87,7 @@ Use Etherscan to call `getRewards()`: ### クエリフィーカットとインデキシングリワードカットとは？ -`クエリフィーカット` と`インデキシングリワードカット` の値は、インデクサーが クールダウンブロックと共に設定できるデリゲーションパラメータで、インデクサーとそのデリゲーター間の GRT の分配を制御するためのものです。 デリゲーションパラメータの設定方法については、[Staking in the Protocol](/network/indexing#stake-in-the-protocol)の最後のステップを参照してください。 +`クエリフィーカット` と`インデキシングリワードカット` の値は、インデクサーが クールダウンブロックと共に設定できるデリゲーションパラメータで、インデクサーとそのデリゲーター間の GRT の分配を制御するためのものです。 デリゲーションパラメータの設定方法については、[Staking in the Protocol](/network/indexing/#stake-in-the-protocol)の最後のステップを参照してください。 - **queryFeeCut** - クエリ料金のリベートの%を示します。これが95%に設定されている場合、インデクサーは割り当てが閉じられた際に獲得するクエリ料金の95%を受け取り、残りの5%は委任者に支払われます。 @@ -121,7 +121,7 @@ Use Etherscan to call `getRewards()`: ### インデクサーが取るべきセキュリティ対策は？ -- **オペレーター ウォレット** - オペレーター ウォレットを設定することは重要な予防措置です。これにより、インデクサーは、ステークを制御するキーと日々の操作を制御するキーとの間の分離を維持できるようになります。 - デイ オペレーション。手順については、[Stake in Protocol](/network/indexing#stake-in-the-protocol) を参照してください。 +- **オペレーター ウォレット** - オペレーター ウォレットを設定することは重要な予防措置です。これにより、インデクサーは、ステークを制御するキーと日々の操作を制御するキーとの間の分離を維持できるようになります。 - デイ オペレーション。手順については、[Stake in Protocol](/network/indexing/#stake-in-the-protocol) を参照してください。 - **ファイアウォール** - インデクサー サービスのみを公開する必要があり、管理ポートとデータベース アクセスのロックダウンに特に注意を払う必要があります: グラフ ノード JSON-RPC エンドポイント (デフォルト ポート: 8030)、インデクサー管理 API エンドポイント (既定のポート: 18000)、および Postgres データベース エンドポイント (既定のポート: 5432) は公開しないでください。 @@ -374,7 +374,7 @@ docker-compose up #### はじめに -インデクサー エージェントとインデクサー サービスは、グラフ ノード インフラストラクチャと同じ場所に配置する必要があります。 インデクサー コンポーネントの仮想実行環境をセットアップするには、さまざまな方法があります。 ここでは、NPM パッケージまたはソースを使用するか、Google Cloud Kubernetes Engine 上の kubernetes と Docker を介してベアメタル上でそれらを実行する方法を説明します。 これらの設定例がご使用のインフラストラクチャにうまく反映されない場合は、参考となるコミュニティ ガイドがある可能性があります。[Discord](https://discord.gg/graphprotocol) にお越しください。 インデクサー コンポーネントを起動する前に、忘れずに [stake in the protocol](/network/indexing#stake-in-the-protocol) してください。 +インデクサー エージェントとインデクサー サービスは、グラフ ノード インフラストラクチャと同じ場所に配置する必要があります。 インデクサー コンポーネントの仮想実行環境をセットアップするには、さまざまな方法があります。 ここでは、NPM パッケージまたはソースを使用するか、Google Cloud Kubernetes Engine 上の kubernetes と Docker を介してベアメタル上でそれらを実行する方法を説明します。 これらの設定例がご使用のインフラストラクチャにうまく反映されない場合は、参考となるコミュニティ ガイドがある可能性があります。[Discord](https://discord.gg/graphprotocol) にお越しください。 インデクサー コンポーネントを起動する前に、忘れずに [stake in the protocol](/network/indexing/#stake-in-the-protocol) してください。 #### NPM パッケージから @@ -454,7 +454,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s と Terraform の使用 -[Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) の項を参照ください。 +[Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) の項を参照ください。 #### 使い方 @@ -753,7 +753,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -インデクサーがプロトコルにGRTをステークすると、[Indexerコンポーネント](/network/indexing#indexer-components)を立ち上げ、ネットワークとのやりとりを開始することができます。 +インデクサーがプロトコルにGRTをステークすると、[Indexerコンポーネント](/network/indexing/#indexer-components)を立ち上げ、ネットワークとのやりとりを開始することができます。 #### トークンの承認 diff --git a/website/pages/ja/resources/benefits.mdx b/website/pages/ja/resources/benefits.mdx index 48f335f3be72..cd9b5fd23705 100644 --- a/website/pages/ja/resources/benefits.mdx +++ b/website/pages/ja/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. サブグラフ上のシグナルのキュレーションは、オプションで1回限り、ネットゼロのコストで可能です（例えば、$1,000のシグナルをサブグラフ上でキュレーションし、後で引き出すことができ、その過程でリターンを得る可能性があります）。 diff --git a/website/pages/ja/resources/roles/curating.mdx b/website/pages/ja/resources/roles/curating.mdx index 1415887e0b70..ece45a6d2a62 100644 --- a/website/pages/ja/resources/roles/curating.mdx +++ b/website/pages/ja/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## シグナルの出し方 -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) キュレーターは、特定のサブグラフのバージョンでシグナルを出すことも、そのサブグラフの最新のプロダクションビルドに自動的にシグナルを移行させることも可能ですます。 どちらも有効な戦略であり、それぞれに長所と短所があります。 @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The Graph では、クエリ市場は本質的に歴史が浅く、初期の市場ダイナミクスのために、あなたの%APY が予想より低くなるリスクがあります。 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. サブグラフはバグで失敗することがあります。 失敗したサブグラフは、クエリフィーが発生しません。 結果的に、開発者がバグを修正して新しいバージョンを展開するまで待たなければならなくなります。 - サブグラフの最新バージョンに加入している場合、シェアはその新バージョンに自動移行します。 これには 0.5％のキュレーション税がかかります。 - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ja/subgraphs/cookbook/grafting.mdx b/website/pages/ja/subgraphs/cookbook/grafting.mdx index 2df8229bce59..41fc94d7fe80 100644 --- a/website/pages/ja/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ja/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ title: グラフティングでコントラクトを取り替え、履歴を残 詳しくは、こちらでご確認ください。 -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/ja/subgraphs/cookbook/near.mdx b/website/pages/ja/subgraphs/cookbook/near.mdx index e6913d4d66a5..aae00c41c789 100644 --- a/website/pages/ja/subgraphs/cookbook/near.mdx +++ b/website/pages/ja/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ NEAR サブグラフの開発には、バージョン`0.23.0`以上の`graph-cli **subgraph.yaml:**: サブグラフのマニフェストで、対象となるデータソースとその処理方法を定義します。NEAR は新しい`種類`のデータソースです。 -**schema.graphql:**: サブグラフのためにどのようなデータが保存されているか、そして GraphQL を介してどのようにクエリを行うかを定義するスキーマファイル。NEAR サブグラフの要件は、[既存のドキュメント](/developing/creating-a-subgraph#the-graphql-schema)でカバーされています。 +**schema.graphql:**: サブグラフのためにどのようなデータが保存されているか、そして GraphQL を介してどのようにクエリを行うかを定義するスキーマファイル。NEAR サブグラフの要件は、[既存のドキュメント](/developing/creating-a-subgraph/#the-graphql-schema)でカバーされています。 -**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. +**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. サブグラフの開発には 2 つの重要なコマンドがあります: @@ -92,13 +92,13 @@ NEAR データソースは 2 種類のハンドラーをサポートしていま ### スキーマ定義 -スキーマの定義は、結果として得られるサブグラフ・データベースの構造と、エンティティ間の関係を記述する。これは、元のデータソースに依存しません。スキーマ定義の詳細は、[ こちら](/developing/creating-a-subgraph#the-graphql-schema)にあります。 +スキーマの定義は、結果として得られるサブグラフ・データベースの構造と、エンティティ間の関係を記述する。これは、元のデータソースに依存しません。スキーマ定義の詳細は、[ こちら](/developing/creating-a-subgraph/#the-graphql-schema)にあります。 ### AssemblyScript マッピング イベントを処理するためのハンドラは[AssemblyScript](https://www.assemblyscript.org/)で書かれています。 -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - ブロックハンドラーは、`Block`を受け取ります - レシートハンドラーは`ReceiptWithOutcome`を受け取ります -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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 サブグラフの展開 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ NEAR のインデックスを作成するグラフノードの運用には、以 ## NEAR サブグラフへのクエリ -NEAR サブグラフの GraphQL エンドポイントは、既存の API インターフェイスを用いて、スキーマ定義によって決定されます。詳細は、[GraphQL API documentation](/querying/graphql-api) をご覧ください。 +NEAR サブグラフの GraphQL エンドポイントは、既存の API インターフェイスを用いて、スキーマ定義によって決定されます。詳細は、[GraphQL API documentation](/querying/graphql-api/) をご覧ください。 ## サブグラフの例 diff --git a/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx index e6f0d323fd82..1bca5f7e5879 100644 --- a/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: diff --git a/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx index 900aac861511..80ecfac7d53c 100644 --- a/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI ファイルは、契約内容と一致している必要があります。A | バージョン | リリースノート | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx index dca410c2b319..2a7137aa4f70 100644 --- a/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ja/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/ja/subgraphs/developing/deploying/multiple-networks.mdx index d4f2935cb302..53c7dcfbd86b 100644 --- a/website/pages/ja/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/ja/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## サブグラフを複数のネットワークにデプロイする diff --git a/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx index 0a867171a0c3..dfcd1aaf915d 100644 --- a/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - 以下の機能のいずれも使用してはいけません: - ipfs.cat & ipfs.map - 致命的でないエラー diff --git a/website/pages/ja/subgraphs/developing/developer-faq.mdx b/website/pages/ja/subgraphs/developing/developer-faq.mdx index c62608db9d9e..64ab9417669d 100644 --- a/website/pages/ja/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ja/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ One possible alternative solution to this is to store raw data in entities and p Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -データソース・テンプレートのインスタンス化」のセクションをご覧ください: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates) +データソース・テンプレートのインスタンス化」のセクションをご覧ください: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -対応ネットワークの一覧は[こちら](/developing/supported-networks)で確認できます。 +対応ネットワークの一覧は[こちら](/developing/supported-networks/)で確認できます。 ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx index da44b21c8e8a..d9b3b54caf9b 100644 --- a/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: 分散型ネットワークへのサブグラフの公開 --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### パブリッシュされたサブグラフのメタデータの更新 @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/ja/subgraphs/explorer.mdx b/website/pages/ja/subgraphs/explorer.mdx index 1fd4f1692eda..401b0b84a0db 100644 --- a/website/pages/ja/subgraphs/explorer.mdx +++ b/website/pages/ja/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -インデクサーになるには、[公式ドキュメント](/network/indexing)や[The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)を見てみてください。 +インデクサーになるには、[公式ドキュメント](/network/indexing/)や[The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)を見てみてください。 ![インデックス作成の詳細](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![エクスプローラーイメージ ６](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. デリゲーター @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - 現在プロトコルに保持している GRT 総量 - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## ネットワーク diff --git a/website/pages/ja/subgraphs/querying/best-practices.mdx b/website/pages/ja/subgraphs/querying/best-practices.mdx index d8b9c04cf7a7..94f2d119d023 100644 --- a/website/pages/ja/subgraphs/querying/best-practices.mdx +++ b/website/pages/ja/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - 各`queryName`は、1回の操作で1回だけ使用しなければなりません。 - 各`フィールド`は、選択の中で一度だけ使用しなければなりません(`トークン`の下に`id`を二度照会することはできません)。 -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - 引数に代入される変数は、その型と一致しなければなりません。 - 与えられた変数のリストにおいて、各変数は一意でなければなりません。 - 定義された変数はすべて使用する必要があります。 @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - クロスチェーンのサブグラフ処理：1回のクエリで複数のサブグラフからクエリを実行可能 - [自動ブロック追跡](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/ja/subgraphs/querying/graphql-api.mdx b/website/pages/ja/subgraphs/querying/graphql-api.mdx index 2c8ec74321ed..403e7f70169d 100644 --- a/website/pages/ja/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ja/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ The result of such a query will not change over time, i.e., querying at a certai ### 全文検索クエリ -フルテキスト検索クエリフィールドは、サブグラフスキーマに追加してカスタマイズできる、表現力豊かなテキスト検索 API を提供します。サブグラフにフルテキスト検索を追加するには、「[Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields)」を参照してください。 +フルテキスト検索クエリフィールドは、サブグラフスキーマに追加してカスタマイズできる、表現力豊かなテキスト検索 API を提供します。サブグラフにフルテキスト検索を追加するには、「[Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields)」を参照してください。 全文検索クエリには、検索語を提供するための必須フィールド `text` が 1 つあります。この `text` 検索フィールドでは、いくつかの特別な全文演算子を使用できます。 diff --git a/website/pages/ja/subgraphs/querying/introduction.mdx b/website/pages/ja/subgraphs/querying/introduction.mdx index 090cbf888524..f221a3f9c80a 100644 --- a/website/pages/ja/subgraphs/querying/introduction.mdx +++ b/website/pages/ja/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: The Graphのクエリ When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ja/substreams/sps/introduction.mdx b/website/pages/ja/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/ja/substreams/sps/introduction.mdx +++ b/website/pages/ja/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ja/substreams/sps/triggers.mdx b/website/pages/ja/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/ja/substreams/sps/triggers.mdx +++ b/website/pages/ja/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/ja/supported-networks.mdx b/website/pages/ja/supported-networks.mdx index 75feee5305b5..44e3b18745cb 100644 --- a/website/pages/ja/supported-networks.mdx +++ b/website/pages/ja/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx index 5ba89020402c..e516573fd4d9 100644 --- a/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/ko/archived/sunrise.mdx b/website/pages/ko/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/ko/archived/sunrise.mdx +++ b/website/pages/ko/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ko/contracts.mdx b/website/pages/ko/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/ko/contracts.mdx +++ b/website/pages/ko/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ko/indexing/new-chain-integration.mdx b/website/pages/ko/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/ko/indexing/new-chain-integration.mdx +++ b/website/pages/ko/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ko/indexing/overview.mdx b/website/pages/ko/indexing/overview.mdx index a6844c2da009..c05c37a275ef 100644 --- a/website/pages/ko/indexing/overview.mdx +++ b/website/pages/ko/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens diff --git a/website/pages/ko/resources/benefits.mdx b/website/pages/ko/resources/benefits.mdx index 8855efeab057..d95723327119 100644 --- a/website/pages/ko/resources/benefits.mdx +++ b/website/pages/ko/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/ko/resources/roles/curating.mdx b/website/pages/ko/resources/roles/curating.mdx index a5a63f3e2751..a3b96ed010fe 100644 --- a/website/pages/ko/resources/roles/curating.mdx +++ b/website/pages/ko/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ko/subgraphs/cookbook/grafting.mdx b/website/pages/ko/subgraphs/cookbook/grafting.mdx index 6c3b85419af9..7aa79c7e2755 100644 --- a/website/pages/ko/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ko/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/ko/subgraphs/cookbook/near.mdx b/website/pages/ko/subgraphs/cookbook/near.mdx index 8e0be3f5ce4e..cc0bf8637bee 100644 --- a/website/pages/ko/subgraphs/cookbook/near.mdx +++ b/website/pages/ko/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx index 6a0c4e208b99..8aa0bf0027bf 100644 --- a/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx index 86686025b089..282c68973a8a 100644 --- a/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ko/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/ko/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/ko/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/ko/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx index a3b2f150a79c..6edd730f2d8b 100644 --- a/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/ko/subgraphs/developing/developer-faq.mdx b/website/pages/ko/subgraphs/developing/developer-faq.mdx index 244aae52d0f4..85dccad933b0 100644 --- a/website/pages/ko/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ko/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 9de36745a95b..4728db3eb245 100644 --- a/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/ko/subgraphs/explorer.mdx b/website/pages/ko/subgraphs/explorer.mdx index 02dca6ed2f9f..d874f80f5140 100644 --- a/website/pages/ko/subgraphs/explorer.mdx +++ b/website/pages/ko/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/ko/subgraphs/querying/best-practices.mdx b/website/pages/ko/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/ko/subgraphs/querying/best-practices.mdx +++ b/website/pages/ko/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/ko/subgraphs/querying/graphql-api.mdx b/website/pages/ko/subgraphs/querying/graphql-api.mdx index 3dd70fc7b004..917fad3f2406 100644 --- a/website/pages/ko/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ko/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/ko/subgraphs/querying/introduction.mdx b/website/pages/ko/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/ko/subgraphs/querying/introduction.mdx +++ b/website/pages/ko/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ko/substreams/sps/introduction.mdx b/website/pages/ko/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/ko/substreams/sps/introduction.mdx +++ b/website/pages/ko/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ko/substreams/sps/triggers.mdx b/website/pages/ko/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/ko/substreams/sps/triggers.mdx +++ b/website/pages/ko/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/ko/supported-networks.mdx b/website/pages/ko/supported-networks.mdx index 797202065e99..9e47f25c86e6 100644 --- a/website/pages/ko/supported-networks.mdx +++ b/website/pages/ko/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx index 7f95f55721c1..d726ba35abb7 100644 --- a/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide ग्राफने Arbitrum One वर L2 वर जाणे सोपे केले आहे. प्रत्येक प्रोटोकॉल सहभागीसाठी, सर्व नेटवर्क सहभागींसाठी L2 मध्ये हस्तांतरण अखंडपणे करण्यासाठी L2 हस्तांतरण साधनांचा संच आहे. तुम्ही काय हस्तांतरित करत आहात त्यानुसार या साधनांसाठी तुम्हाला चरणांच्या विशिष्ट संचाचे अनुसरण करणे आवश्यक आहे. -या साधनांबद्दलच्या काही वारंवार प्रश्नांची उत्तरे [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq) मध्ये दिली आहेत. FAQ मध्ये साधने कशी वापरायची, ते कसे कार्य करतात आणि ते वापरताना लक्षात ठेवण्यासारख्या गोष्टींचे सखोल स्पष्टीकरण असते. +या साधनांबद्दलच्या काही वारंवार प्रश्नांची उत्तरे [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/) मध्ये दिली आहेत. FAQ मध्ये साधने कशी वापरायची, ते कसे कार्य करतात आणि ते वापरताना लक्षात ठेवण्यासारख्या गोष्टींचे सखोल स्पष्टीकरण असते. ## तुमचा सबग्राफ आर्बिट्रम (L2) वर कसा हस्तांतरित करायचा diff --git a/website/pages/mr/archived/sunrise.mdx b/website/pages/mr/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/mr/archived/sunrise.mdx +++ b/website/pages/mr/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/mr/contracts.mdx b/website/pages/mr/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/mr/contracts.mdx +++ b/website/pages/mr/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/mr/indexing/new-chain-integration.mdx b/website/pages/mr/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/mr/indexing/new-chain-integration.mdx +++ b/website/pages/mr/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/mr/indexing/overview.mdx b/website/pages/mr/indexing/overview.mdx index e725d445b914..8965c47f63cb 100644 --- a/website/pages/mr/indexing/overview.mdx +++ b/website/pages/mr/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -`queryFeeCut` आणि `indexingRewardCut` मूल्ये ही डेलिगेशन पॅरामीटर्स आहेत जी इंडेक्सर आणि त्यांच्या प्रतिनिधींमधील GRT चे वितरण नियंत्रित करण्यासाठी CooldownBlocks सोबत सेट करू शकतात. डेलिगेशन पॅरामीटर्स सेट करण्याच्या सूचनांसाठी [प्रोटोकॉलमध्ये स्टॅकिंग](/network/indexing#stake-in-the-protocol) मधील शेवटच्या पायऱ्या पहा. +`queryFeeCut` आणि `indexingRewardCut` मूल्ये ही डेलिगेशन पॅरामीटर्स आहेत जी इंडेक्सर आणि त्यांच्या प्रतिनिधींमधील GRT चे वितरण नियंत्रित करण्यासाठी CooldownBlocks सोबत सेट करू शकतात. डेलिगेशन पॅरामीटर्स सेट करण्याच्या सूचनांसाठी [प्रोटोकॉलमध्ये स्टॅकिंग](/network/indexing/#stake-in-the-protocol) मधील शेवटच्या पायऱ्या पहा. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What are some basic security precautions an Indexer should take? -- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करणे ही एक महत्त्वाची खबरदारी आहे कारण ते इंडेक्सरला त्यांच्या स्टेक नियंत्रित करणार्‍या की आणि दैनंदिन कामकाजावर नियंत्रण ठेवणार्‍या की यांच्यात वेगळेपणा राखण्यास अनुमती देते. सूचनांसाठी [प्रोटोकॉलमध्ये भागीदारी](/network/indexing#stake-in-the-protocol) पहा. +- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करणे ही एक महत्त्वाची खबरदारी आहे कारण ते इंडेक्सरला त्यांच्या स्टेक नियंत्रित करणार्‍या की आणि दैनंदिन कामकाजावर नियंत्रण ठेवणार्‍या की यांच्यात वेगळेपणा राखण्यास अनुमती देते. सूचनांसाठी [प्रोटोकॉलमध्ये भागीदारी](/network/indexing/#stake-in-the-protocol) पहा. - **फायरवॉल** - फक्त इंडेक्सर सेवा सार्वजनिकपणे उघड करणे आवश्यक आहे आणि प्रशासक पोर्ट आणि डेटाबेस प्रवेश लॉक करण्यासाठी विशेष लक्ष दिले पाहिजे: ग्राफ नोड JSON-RPC एंडपॉइंट (डीफॉल्ट पोर्ट: 8030), इंडेक्सर मॅनेजमेंट API एंडपॉइंट (डीफॉल्ट पोर्ट: 18000), आणि पोस्टग्रेस डेटाबेस एंडपॉइंट (डीफॉल्ट पोर्ट: 5432) उघड करू नये. @@ -375,7 +375,7 @@ docker-compose up #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### वापर @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -एकदा इंडेक्सरने प्रोटोकॉलमध्ये GRT स्टेक केल्यानंतर, [इंडेक्सर घटक](/network/indexing#indexer-components) सुरू केले जाऊ शकतात आणि त्यांचे नेटवर्कशी परस्परसंवाद सुरू करू शकतात. +एकदा इंडेक्सरने प्रोटोकॉलमध्ये GRT स्टेक केल्यानंतर, [इंडेक्सर घटक](/network/indexing/#indexer-components) सुरू केले जाऊ शकतात आणि त्यांचे नेटवर्कशी परस्परसंवाद सुरू करू शकतात. #### Approve tokens diff --git a/website/pages/mr/resources/benefits.mdx b/website/pages/mr/resources/benefits.mdx index 0eee99651335..1ddfb18db87b 100644 --- a/website/pages/mr/resources/benefits.mdx +++ b/website/pages/mr/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. सबग्राफवर क्युरेटिंग सिग्नल हा पर्यायी एक-वेळचा, निव्वळ-शून्य खर्च आहे (उदा., $1k सिग्नल सबग्राफवर क्युरेट केला जाऊ शकतो आणि नंतर मागे घेतला जाऊ शकतो—प्रक्रियेत परतावा मिळविण्याच्या संभाव्यतेसह). diff --git a/website/pages/mr/resources/roles/curating.mdx b/website/pages/mr/resources/roles/curating.mdx index 5e9cadc79a04..6d9ac344f246 100644 --- a/website/pages/mr/resources/roles/curating.mdx +++ b/website/pages/mr/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## सिग्नल कसे करावे -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) क्युरेटर विशिष्ट सबग्राफ आवृत्तीवर सिग्नल करणे निवडू शकतो किंवा ते त्यांचे सिग्नल त्या सबग्राफच्या नवीनतम उत्पादन बिल्डमध्ये स्वयंचलितपणे स्थलांतरित करणे निवडू शकतात. दोन्ही वैध धोरणे आहेत आणि त्यांच्या स्वतःच्या साधक आणि बाधकांसह येतात. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. द ग्राफमध्ये क्वेरी मार्केट मूळतः तरुण आहे आणि नवीन मार्केट डायनॅमिक्समुळे तुमचा %APY तुमच्या अपेक्षेपेक्षा कमी असण्याचा धोका आहे. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. बगमुळे सबग्राफ अयशस्वी होऊ शकतो. अयशस्वी सबग्राफ क्वेरी शुल्क जमा करत नाही. परिणामी, विकसक बगचे निराकरण करेपर्यंत आणि नवीन आवृत्ती तैनात करेपर्यंत तुम्हाला प्रतीक्षा करावी लागेल. - तुम्ही सबग्राफच्या नवीनतम आवृत्तीचे सदस्यत्व घेतले असल्यास, तुमचे शेअर्स त्या नवीन आवृत्तीमध्ये स्वयंचलितपणे स्थलांतरित होतील. यावर 0.5% क्युरेशन कर लागेल. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/mr/subgraphs/cookbook/grafting.mdx b/website/pages/mr/subgraphs/cookbook/grafting.mdx index 77d4b0d04899..22f16892c933 100644 --- a/website/pages/mr/subgraphs/cookbook/grafting.mdx +++ b/website/pages/mr/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ title: करार बदला आणि त्याचा इतिहास अधिक माहितीसाठी, तुम्ही तपासू शकता: -- [कलम करणे](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [कलम करणे](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/mr/subgraphs/cookbook/near.mdx b/website/pages/mr/subgraphs/cookbook/near.mdx index f91dad13e7b0..2d4f7f7b6d24 100644 --- a/website/pages/mr/subgraphs/cookbook/near.mdx +++ b/website/pages/mr/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ This guide is an introduction to building subgraphs indexing smart contracts on **subgraph.yaml:** सबग्राफ मॅनिफेस्ट, स्वारस्य असलेल्या डेटा स्रोतांची व्याख्या आणि त्यावर प्रक्रिया कशी करावी. NEAR डेटा स्रोताचा एक नवीन `प्रकार` आहे. -**schema.graphql:** एक स्कीमा फाइल जी तुमच्या सबग्राफसाठी कोणता डेटा संग्रहित केला जातो आणि GraphQL द्वारे त्याची क्वेरी कशी करावी हे परिभाषित करते. जवळच्या सबग्राफसाठी आवश्यकता [विद्यमान दस्तऐवज](/developing/creating-a-subgraph#the-graphql-schema) द्वारे कव्हर केल्या जातात. +**schema.graphql:** एक स्कीमा फाइल जी तुमच्या सबग्राफसाठी कोणता डेटा संग्रहित केला जातो आणि GraphQL द्वारे त्याची क्वेरी कशी करावी हे परिभाषित करते. जवळच्या सबग्राफसाठी आवश्यकता [विद्यमान दस्तऐवज](/developing/creating-a-subgraph/#the-graphql-schema) द्वारे कव्हर केल्या जातात. -**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. +**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. सबग्राफ विकासादरम्यान दोन प्रमुख आज्ञा आहेत: @@ -92,13 +92,13 @@ accounts: ### स्कीमा व्याख्या -स्कीमा व्याख्या परिणामी सबग्राफ डेटाबेसची रचना आणि संस्थांमधील संबंधांचे वर्णन करते. हे मूळ डेटा स्रोताचे अज्ञेय आहे. सबग्राफ स्कीमा व्याख्या [येथे](/developing/creating-a-subgraph#the-graphql-schema) अधिक तपशील आहेत. +स्कीमा व्याख्या परिणामी सबग्राफ डेटाबेसची रचना आणि संस्थांमधील संबंधांचे वर्णन करते. हे मूळ डेटा स्रोताचे अज्ञेय आहे. सबग्राफ स्कीमा व्याख्या [येथे](/developing/creating-a-subgraph/#the-graphql-schema) अधिक तपशील आहेत. ### असेंबलीस्क्रिप्ट मॅपिंग इव्हेंटवर प्रक्रिया करण्यासाठी हँडलर [AssemblyScript](https://www.assemblyscript.org/) मध्ये लिहिलेले आहेत. -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - ब्लॉक हँडलर्सना एक `ब्लॉक` मिळेल - पावती हाताळणाऱ्यांना `ReceiptWithOutcome` मिळेल -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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 सबग्राफ डिप्लॉय करण्यासाठी @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `जवळ-मेननेट` - `जवळ-टेस्टनेट` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ NEAR ची अनुक्रमणिका देणारा आलेख ## NEAR सबग्राफची क्वेरी करणे -NEAR subgraphs साठी GraphQL एंडपॉइंट विद्यमान API इंटरफेससह स्कीमा व्याख्येद्वारे निर्धारित केला जातो. अधिक माहितीसाठी कृपया [GraphQL API दस्तऐवज](/querying/graphql-api) ला भेट द्या. +NEAR subgraphs साठी GraphQL एंडपॉइंट विद्यमान API इंटरफेससह स्कीमा व्याख्येद्वारे निर्धारित केला जातो. अधिक माहितीसाठी कृपया [GraphQL API दस्तऐवज](/querying/graphql-api/) ला भेट द्या. ## उदाहरणे सबग्राफ diff --git a/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx index 1ab6b8e6fad8..d96ebeaee324 100644 --- a/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: असेंबलीस्क्रिप्ट API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx index 8c243e1ec972..7c50a40e48fd 100644 --- a/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | आवृत्ती | रिलीझ नोट्स | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx b/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx index 57d5ceb7ecf7..fbd122685dc7 100644 --- a/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/mr/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/mr/subgraphs/developing/deploying/multiple-networks.mdx index ab644e836b37..8d85033aeb01 100644 --- a/website/pages/mr/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/mr/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## एकाधिक नेटवर्कवर सबग्राफ तैनात करणे diff --git a/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx index 72a5eca3d903..5798560f270d 100644 --- a/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - खालीलपैकी कोणतीही वैशिष्ट्ये वापरू नयेत: - ipfs.cat & ipfs.map - गैर-घातक त्रुटी diff --git a/website/pages/mr/subgraphs/developing/developer-faq.mdx b/website/pages/mr/subgraphs/developing/developer-faq.mdx index 1507d740d45b..76f12ab1d704 100644 --- a/website/pages/mr/subgraphs/developing/developer-faq.mdx +++ b/website/pages/mr/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ One possible alternative solution to this is to store raw data in entities and p Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -[डेटा स्रोत टेम्पलेट्स](/developing/creating-a-subgraph#data-source-templates) यावर "डेटा स्त्रोत टेम्पलेट इन्स्टंटिएटिंग करणे" विभाग पहा. +[डेटा स्रोत टेम्पलेट्स](/developing/creating-a-subgraph/#data-source-templates) यावर "डेटा स्त्रोत टेम्पलेट इन्स्टंटिएटिंग करणे" विभाग पहा. ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -तुम्ही समर्थित नेटवर्कची सूची [येथे](/developing/supported-networks) शोधू शकता. +तुम्ही समर्थित नेटवर्कची सूची [येथे](/developing/supported-networks/) शोधू शकता. ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 742bc24d2c3d..c8bc554999f8 100644 --- a/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: विकेंद्रीकृत नेटवर्कवर सबग्राफ प्रकाशित करणे --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### प्रकाशित सबग्राफसाठी मेटाडेटा अपडेट करत आहे @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/mr/subgraphs/explorer.mdx b/website/pages/mr/subgraphs/explorer.mdx index 1bf46de5f24a..1d967cd1357d 100644 --- a/website/pages/mr/subgraphs/explorer.mdx +++ b/website/pages/mr/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -इंडेक्सर कसे व्हावे याबद्दल अधिक जाणून घेण्यासाठी, तुम्ही [अधिकृत दस्तऐवज](/network/indexing) किंवा [द ग्राफ अकादमी इंडेक्सर मार्गदर्शक](https://thegraph.academy/delegators/ पाहू शकता choosing-indexers/) +इंडेक्सर कसे व्हावे याबद्दल अधिक जाणून घेण्यासाठी, तुम्ही [अधिकृत दस्तऐवज](/network/indexing/) किंवा [द ग्राफ अकादमी इंडेक्सर मार्गदर्शक](https://thegraph.academy/delegators/ पाहू शकता choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/mr/subgraphs/querying/best-practices.mdx b/website/pages/mr/subgraphs/querying/best-practices.mdx index 5112da12c581..1e729d793cf8 100644 --- a/website/pages/mr/subgraphs/querying/best-practices.mdx +++ b/website/pages/mr/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/mr/subgraphs/querying/graphql-api.mdx b/website/pages/mr/subgraphs/querying/graphql-api.mdx index ed5f483cfc2a..67f41194b21d 100644 --- a/website/pages/mr/subgraphs/querying/graphql-api.mdx +++ b/website/pages/mr/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/mr/subgraphs/querying/introduction.mdx b/website/pages/mr/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/mr/subgraphs/querying/introduction.mdx +++ b/website/pages/mr/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/mr/substreams/sps/introduction.mdx b/website/pages/mr/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/mr/substreams/sps/introduction.mdx +++ b/website/pages/mr/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/mr/substreams/sps/triggers.mdx b/website/pages/mr/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/mr/substreams/sps/triggers.mdx +++ b/website/pages/mr/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/mr/supported-networks.mdx b/website/pages/mr/supported-networks.mdx index 797202065e99..9e47f25c86e6 100644 --- a/website/pages/mr/supported-networks.mdx +++ b/website/pages/mr/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx index 08b184bf29bb..191f95ca8a84 100644 --- a/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Gids voor L2 Transfer Tools The Graph heeft het eenvoudig gemaakt om naar L2 op Arbitrum One over te stappen. Voor elke deelnemer aan het protocol is er een set L2 Transfer Tools ontwikkeld om het overzetten van GRT naar L2 makkelijk te maken voor alle netwerkdeelnemers. Deze tools vereisen dat u een specifieke reeks stappen volgt, afhankelijk van wat u overdraagt. -Sommige veelgestelde vragen over deze tools worden beantwoord in de [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). De FAQs bevatten diepgaande uitleg over hoe de tools te gebruiken, hoe ze werken, en punten om rekening mee to houden bij het gebruiken ervan. +Sommige veelgestelde vragen over deze tools worden beantwoord in de [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). De FAQs bevatten diepgaande uitleg over hoe de tools te gebruiken, hoe ze werken, en punten om rekening mee to houden bij het gebruiken ervan. ## Hoe zet je je subgraph over naar Arbitrum (L2) diff --git a/website/pages/nl/archived/sunrise.mdx b/website/pages/nl/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/nl/archived/sunrise.mdx +++ b/website/pages/nl/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/nl/contracts.mdx b/website/pages/nl/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/nl/contracts.mdx +++ b/website/pages/nl/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/nl/indexing/new-chain-integration.mdx b/website/pages/nl/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/nl/indexing/new-chain-integration.mdx +++ b/website/pages/nl/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/nl/indexing/overview.mdx b/website/pages/nl/indexing/overview.mdx index ee65031735f6..e86a0092b1ca 100644 --- a/website/pages/nl/indexing/overview.mdx +++ b/website/pages/nl/indexing/overview.mdx @@ -87,7 +87,7 @@ Zodra een allocatie is gesloten, zijn de rebates beschikbaar om door de Indexeer ### Wat is de Query Fee Cut en de Indexing Reward Cut? -De `queryFeeCut` en `indexingRewardCut` waarden zijn delegatie parameters die de Indexer kan instellen samen met de cooldownBlocks om de verdeling GRT te controleren tussen de Indexer en hun Delegators. Zie de laatste stappen in [Inzetten in het Protocol](/network/indexing#stake-in-the-protocol) voor instructies op delegatie parameters in the stellen. +De `queryFeeCut` en `indexingRewardCut` waarden zijn delegatie parameters die de Indexer kan instellen samen met de cooldownBlocks om de verdeling GRT te controleren tussen de Indexer en hun Delegators. Zie de laatste stappen in [Inzetten in het Protocol](/network/indexing/#stake-in-the-protocol) voor instructies op delegatie parameters in the stellen. - **queryFeeCut** - het % van de query kosten rebates die worden verdeeld aan de Indexeerder. Als dit is ingesteld op 95%, ontvangt de Indexeerder 95% van de query kosten die zijn verdiend wanneer een allocatie wordt gesloten, met de overige 5% gaande naar Delegators. @@ -121,7 +121,7 @@ Indexeerders kunnen zich onderscheiden door geavanceerde technieken toe te passe ### Wat zijn enkele basisveiligheidsmaatregelen die een Indexeerder moet nemen? -- **Operator wallet** - Het opzetten van een operator wallet is een belangrijke voorzorgsmaatregel omdat het een Indexeerder in staat stelt om scheiding te behouden tussen de sleutels die de GRT beheren en degenen die de dagelijkse operaties beheren. Zie [Inzet in het Protocol](/network/indexing#stake-in-the-protocol) voor instructies. +- **Operator wallet** - Het opzetten van een operator wallet is een belangrijke voorzorgsmaatregel omdat het een Indexeerder in staat stelt om scheiding te behouden tussen de sleutels die de GRT beheren en degenen die de dagelijkse operaties beheren. Zie [Inzet in het Protocol](/network/indexing/#stake-in-the-protocol) voor instructies. - **Firewall** - Alleen de Indexer service hoeft openbaar te worden blootgesteld en er moet extra aandacht worden besteed aan het vergrendelen van de admin poorten en database toegang: de Graph Node Jason-RPC endpoint (standaardpoort: 8030), de Indexer management API endpoint (standaardpoort: 18000), en de Postgres database endpoint (standaardpoort: 5432) mogen niet worden blootgesteld. @@ -375,7 +375,7 @@ Om succesvol deel te nemen aan het netwerk is bijna constante monitoring en inte #### Aan de slag -De indexer agent en indexer service moeten zich op de zelfde locatie bevinden als de Graph Node. Er zijn vele manieren om de virtuele uitvoeromgeving voor uw indexer-componenten op te zetten; we zullen uitleggen hoe ze op baremetal uit te voeren zijn met NPM-pakketten of de source code, of via Kubernetes en Docker op de Google Cloud Kubernetes Engine. Als deze voorbeelden niet goed zullen werken op uw infrastructuur, is er waarschijnlijk een community guide om als alternatief te gebruiken. Kom gerust hallo zeggen op [Discord](https://discord.gg/graphprotocol)! Onthoud om [GRT in the zetten](/network/indexing#stake-in-the-protocol) in het protocol voordat u uw indexer-componenten start! +De indexer agent en indexer service moeten zich op de zelfde locatie bevinden als de Graph Node. Er zijn vele manieren om de virtuele uitvoeromgeving voor uw indexer-componenten op te zetten; we zullen uitleggen hoe ze op baremetal uit te voeren zijn met NPM-pakketten of de source code, of via Kubernetes en Docker op de Google Cloud Kubernetes Engine. Als deze voorbeelden niet goed zullen werken op uw infrastructuur, is er waarschijnlijk een community guide om als alternatief te gebruiken. Kom gerust hallo zeggen op [Discord](https://discord.gg/graphprotocol)! Onthoud om [GRT in the zetten](/network/indexing/#stake-in-the-protocol) in het protocol voordat u uw indexer-componenten start! #### Met NPM-pakketten @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Met K8s en Terraform -Zie de sectie [Infrastructuur van de server instellen met behulp van Terraform op Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Zie de sectie [Infrastructuur van de server instellen met behulp van Terraform op Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Gebruik @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens diff --git a/website/pages/nl/resources/benefits.mdx b/website/pages/nl/resources/benefits.mdx index 3e66d7793f22..2bab6ae0a90b 100644 --- a/website/pages/nl/resources/benefits.mdx +++ b/website/pages/nl/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Signaal cureren op een subgraph is een optionele eenmalige, kostenneutrale actie (bijv. $1000 aan signaal kan worden gecureerd op een subgraph en later worden opgenomen - met het potentieel om rendementen te verdienen tijdens het proces). diff --git a/website/pages/nl/resources/roles/curating.mdx b/website/pages/nl/resources/roles/curating.mdx index 3e64881ac6eb..040afc3b2f01 100644 --- a/website/pages/nl/resources/roles/curating.mdx +++ b/website/pages/nl/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Hoe werkt het Signaleren -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) Een curator kan ervoor kiezen om een signaal af te geven voor een specifieke subgraph versie, of ze kunnen ervoor kiezen om hun signaal automatisch te laten migreren naar de nieuwste versie van de subgraph. Beide strategieën hebben voordelen en nadelen. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. De querymarkt is nog jong bij het Graph Netwerk en er bestaat een risico dat je %APY lager kan zijn dan je verwacht door opkomende marktdynamiek. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Een subgraph kan stuk gaan door een bug. Een subgraph die stuk is gegenereerd geen querykosten. Als gevolg hiervan moet je wachten tot de ontwikkelaar de bug repareert en een nieuwe versie implementeert. - Als je bent geabonneerd op de nieuwste versie van een subgraph, worden je curatieaandelen automatisch gemigreerd naar die nieuwe versie. Er is een curatiebelasting van 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/nl/subgraphs/cookbook/grafting.mdx b/website/pages/nl/subgraphs/cookbook/grafting.mdx index 6c3b85419af9..7aa79c7e2755 100644 --- a/website/pages/nl/subgraphs/cookbook/grafting.mdx +++ b/website/pages/nl/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/nl/subgraphs/cookbook/near.mdx b/website/pages/nl/subgraphs/cookbook/near.mdx index 4bbca2713b73..501a04b9455f 100644 --- a/website/pages/nl/subgraphs/cookbook/near.mdx +++ b/website/pages/nl/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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. Tijdens subgraph ontwikkeling zijn er twee belangrijke commando's: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx index 6a0c4e208b99..8aa0bf0027bf 100644 --- a/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx index d403f2138eb8..a23e14babbb2 100644 --- a/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx b/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/nl/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/nl/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/nl/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/nl/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx index 1918c4b13f00..f6b0f1b8d599 100644 --- a/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/nl/subgraphs/developing/developer-faq.mdx b/website/pages/nl/subgraphs/developing/developer-faq.mdx index 6e49c4271720..c68ddb8c7d00 100644 --- a/website/pages/nl/subgraphs/developing/developer-faq.mdx +++ b/website/pages/nl/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 353ff7414cb4..09c20daa62fa 100644 --- a/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/nl/subgraphs/explorer.mdx b/website/pages/nl/subgraphs/explorer.mdx index cb2be6378d2a..e34ca81d144e 100644 --- a/website/pages/nl/subgraphs/explorer.mdx +++ b/website/pages/nl/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Om meer te weten te komen over hoe je een Indexer kunt worden, kun je een kijkje nemen in de [officiële documentatie](/network/indexing) of de Indexeerdersgidsen van [The Graph Academy](https://thegraph.academy/delegators/choosing-indexers/) +Om meer te weten te komen over hoe je een Indexer kunt worden, kun je een kijkje nemen in de [officiële documentatie](/network/indexing/) of de Indexeerdersgidsen van [The Graph Academy](https://thegraph.academy/delegators/choosing-indexers/) ![Indexering details paneel](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Afbeelding 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Het totale bedrag aan GRT dat ze momenteel in het protocol hebben - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Netwerk diff --git a/website/pages/nl/subgraphs/querying/best-practices.mdx b/website/pages/nl/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/nl/subgraphs/querying/best-practices.mdx +++ b/website/pages/nl/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/nl/subgraphs/querying/graphql-api.mdx b/website/pages/nl/subgraphs/querying/graphql-api.mdx index 3dd70fc7b004..917fad3f2406 100644 --- a/website/pages/nl/subgraphs/querying/graphql-api.mdx +++ b/website/pages/nl/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/nl/subgraphs/querying/introduction.mdx b/website/pages/nl/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/nl/subgraphs/querying/introduction.mdx +++ b/website/pages/nl/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/nl/substreams/sps/introduction.mdx b/website/pages/nl/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/nl/substreams/sps/introduction.mdx +++ b/website/pages/nl/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/nl/substreams/sps/triggers.mdx b/website/pages/nl/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/nl/substreams/sps/triggers.mdx +++ b/website/pages/nl/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/nl/supported-networks.mdx b/website/pages/nl/supported-networks.mdx index bd39f933133c..a3fc9b60202a 100644 --- a/website/pages/nl/supported-networks.mdx +++ b/website/pages/nl/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx index 023bc0b8d4c0..014770ff141b 100644 --- a/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Przewodnik po narzędziach przesyłania L2 Graph ułatwił przeniesienie danych do L2 na Arbitrum One. Dla każdego uczestnika protokołu dostępny jest zestaw narzędzi do przesyłania na L2, dzięki którym przeniesienie do L2 jest bezproblemowe dla wszystkich uczestników sieci. Narzędzia te wymagają wykonania określonego zestawu kroków w zależności od przenoszonych danych. -Odpowiedzi na najczęściej zadawane pytania dotyczące tych narzędzi znajdują się w [Narzędzia przesyłania L2 FAQ](/arbitrum/l2-transfer-tools-faq). Odpowiedzi na najczęściej zadawane pytania zawierają szczegółowe wyjaśnienia dotyczące korzystania z narzędzi, ich działania i rzeczy, o których należy pamiętać podczas korzystania z nich. +Odpowiedzi na najczęściej zadawane pytania dotyczące tych narzędzi znajdują się w [Narzędzia przesyłania L2 FAQ](/arbitrum/l2-transfer-tools-faq/). Odpowiedzi na najczęściej zadawane pytania zawierają szczegółowe wyjaśnienia dotyczące korzystania z narzędzi, ich działania i rzeczy, o których należy pamiętać podczas korzystania z nich. ## Jak przenieść swój subgraph do Arbitrum (L2) diff --git a/website/pages/pl/archived/sunrise.mdx b/website/pages/pl/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/pl/archived/sunrise.mdx +++ b/website/pages/pl/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/pl/contracts.mdx b/website/pages/pl/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/pl/contracts.mdx +++ b/website/pages/pl/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/pl/indexing/new-chain-integration.mdx b/website/pages/pl/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/pl/indexing/new-chain-integration.mdx +++ b/website/pages/pl/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/pl/indexing/overview.mdx b/website/pages/pl/indexing/overview.mdx index a6844c2da009..c05c37a275ef 100644 --- a/website/pages/pl/indexing/overview.mdx +++ b/website/pages/pl/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens diff --git a/website/pages/pl/resources/benefits.mdx b/website/pages/pl/resources/benefits.mdx index 8875be34a834..3a3be46c2cf8 100644 --- a/website/pages/pl/resources/benefits.mdx +++ b/website/pages/pl/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/pl/resources/roles/curating.mdx b/website/pages/pl/resources/roles/curating.mdx index a5a63f3e2751..a3b96ed010fe 100644 --- a/website/pages/pl/resources/roles/curating.mdx +++ b/website/pages/pl/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/pl/subgraphs/cookbook/grafting.mdx b/website/pages/pl/subgraphs/cookbook/grafting.mdx index 6c3b85419af9..7aa79c7e2755 100644 --- a/website/pages/pl/subgraphs/cookbook/grafting.mdx +++ b/website/pages/pl/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/pl/subgraphs/cookbook/near.mdx b/website/pages/pl/subgraphs/cookbook/near.mdx index 8e0be3f5ce4e..cc0bf8637bee 100644 --- a/website/pages/pl/subgraphs/cookbook/near.mdx +++ b/website/pages/pl/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx index 6a0c4e208b99..8aa0bf0027bf 100644 --- a/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx index 2bd046a9e605..37a742e7c78a 100644 --- a/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx b/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/pl/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/pl/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/pl/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/pl/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx index 2eb14f2ab083..9adc37bddeb9 100644 --- a/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/pl/subgraphs/developing/developer-faq.mdx b/website/pages/pl/subgraphs/developing/developer-faq.mdx index 97f851a2d0c8..0e8fb2d4f1bf 100644 --- a/website/pages/pl/subgraphs/developing/developer-faq.mdx +++ b/website/pages/pl/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 9de36745a95b..4728db3eb245 100644 --- a/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/pl/subgraphs/explorer.mdx b/website/pages/pl/subgraphs/explorer.mdx index 05b322667e92..593f49b397f9 100644 --- a/website/pages/pl/subgraphs/explorer.mdx +++ b/website/pages/pl/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/pl/subgraphs/querying/best-practices.mdx b/website/pages/pl/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/pl/subgraphs/querying/best-practices.mdx +++ b/website/pages/pl/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/pl/subgraphs/querying/graphql-api.mdx b/website/pages/pl/subgraphs/querying/graphql-api.mdx index 3dd70fc7b004..917fad3f2406 100644 --- a/website/pages/pl/subgraphs/querying/graphql-api.mdx +++ b/website/pages/pl/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/pl/subgraphs/querying/introduction.mdx b/website/pages/pl/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/pl/subgraphs/querying/introduction.mdx +++ b/website/pages/pl/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/pl/substreams/sps/introduction.mdx b/website/pages/pl/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/pl/substreams/sps/introduction.mdx +++ b/website/pages/pl/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/pl/substreams/sps/triggers.mdx b/website/pages/pl/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/pl/substreams/sps/triggers.mdx +++ b/website/pages/pl/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/pl/supported-networks.mdx b/website/pages/pl/supported-networks.mdx index 6a9a3d7332fe..cd2062dcae7c 100644 --- a/website/pages/pl/supported-networks.mdx +++ b/website/pages/pl/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx b/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx index 02e7092afd1b..873be7d055ef 100644 --- a/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx @@ -77,4 +77,4 @@ O bridge foi [auditado rigorosamente](https://code4rena.com/contests/2022-10-the A adição de GRT ao seu saldo de cobrança no Arbitrum pode ser feito em apenas um clique no [Subgraph Studio](https://thegraph.com/studio/). Você poderá fazer o bridge do seu GRT ao Arbitrum com facilidade, e preencher as suas chaves de API em uma única transação. -Visite a página de [Cobranças](//) para mais detalhes sobre como depositar, retirar, ou adquirir GRT. +Visite a página de [Cobranças](/) para mais detalhes sobre como depositar, retirar, ou adquirir GRT. diff --git a/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx index f799681d02ba..6e25493c1292 100644 --- a/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Guia das Ferramentas de Transferência para L2 O The Graph facilitou muito o processo de se mudar para a L2 no Arbitrum One. Para cada participante no protocolo, há um conjunto de Ferramentas de Transferência para L2 que suavizam o processo para todos os participantes na rede. Estas ferramentas exigem que você siga um conjunto específico de passos, dependente no que você transferir. -Algumas perguntas frequentes sobre estas ferramentas são respondidas nas [Perguntas Frequentes das Ferramentas de Transferência para L2](/arbitrum/l2-transfer-tools-faq). As Perguntas Frequentes contém explicações profundas sobre como usar as ferramentas, como elas funcionam, e coisas a lembrar ao usá-las. +Algumas perguntas frequentes sobre estas ferramentas são respondidas nas [Perguntas Frequentes das Ferramentas de Transferência para L2](/arbitrum/l2-transfer-tools-faq/). As Perguntas Frequentes contém explicações profundas sobre como usar as ferramentas, como elas funcionam, e coisas a lembrar ao usá-las. ## Como transferir o seu subgraph ao Arbitrum (L2) diff --git a/website/pages/pt/archived/sunrise.mdx b/website/pages/pt/archived/sunrise.mdx index 7511fb469647..216572c5be6d 100644 --- a/website/pages/pt/archived/sunrise.mdx +++ b/website/pages/pt/archived/sunrise.mdx @@ -60,7 +60,7 @@ Ele opera numa base de "necessidade" e serve como uma reserva até que uma cota ### Como isto afeta os programadores de subgraph? -Progmadores de subgraph poderão enviar queries para os seus subgraphs na Graph Network quase imediatamente após migrar do serviço hospedado ou [publicá-los do Subgraph Studio](/publishing/publishing-a-subgraph/), já que não será necessário tempo de espera para a indexação. Note que a [criação de subgraphs](/developing/creating-a-subgraph) não foi impactada por esta atualização. +Progmadores de subgraph poderão enviar queries para os seus subgraphs na Graph Network quase imediatamente após migrar do serviço hospedado ou [publicá-los do Subgraph Studio](/publishing/publishing-a-subgraph/), já que não será necessário tempo de espera para a indexação. Note que a [criação de subgraphs](/developing/creating-a-subgraph/) não foi impactada por esta atualização. ### Como o Indexador de atualizações beneficia consumidores de dados? diff --git a/website/pages/pt/contracts.mdx b/website/pages/pt/contracts.mdx index c29458e9e0ae..77cc18aa29b4 100644 --- a/website/pages/pt/contracts.mdx +++ b/website/pages/pt/contracts.mdx @@ -14,7 +14,7 @@ Este é o lançamento principal da Graph Network. ## Mainnet -Este foi o lançamento original da Graph Network. [Aprenda mais](/arbitrum/arbitrum-faq) sobre o escalamento do The Graph com Arbitrum. +Este foi o lançamento original da Graph Network. [Aprenda mais](/arbitrum/arbitrum-faq/) sobre o escalamento do The Graph com Arbitrum. diff --git a/website/pages/pt/indexing/new-chain-integration.mdx b/website/pages/pt/indexing/new-chain-integration.mdx index 9c4f0e35d292..27dfb3931e4e 100644 --- a/website/pages/pt/indexing/new-chain-integration.mdx +++ b/website/pages/pt/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ Para chains EVM, há um nível mais profundo de dados que podem ser alcançados ## Considerações de EVM - Diferença entre JSON-RPC e Firehose -Enquanto ambos o JSON-RPC e o Firehose são próprios para subgraphs, um Firehose é sempre necessário para programadores que querem construir com [Substreams](https://substreams.streamingfast.io). Apoiar os Substreams permite que programadores construam [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs) para a nova chain, e tem o potencial de melhorar o desempenho dos seus subgraphs. Além disto, o Firehose — como um substituto pronto para a camada de extração JSON-RPC do `graph-node` — reduz em 90% o número de chamadas RPC exigidas para indexação geral. +Enquanto ambos o JSON-RPC e o Firehose são próprios para subgraphs, um Firehose é sempre necessário para programadores que querem construir com [Substreams](https://substreams.streamingfast.io). Apoiar os Substreams permite que programadores construam [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) para a nova chain, e tem o potencial de melhorar o desempenho dos seus subgraphs. Além disto, o Firehose — como um substituto pronto para a camada de extração JSON-RPC do `graph-node` — reduz em 90% o número de chamadas RPC exigidas para indexação geral. - Todas essas chamadas `getLogs` e roundtrips são substituídas por um único fluxo que chega no coração do `graph-node`, um modelo de bloco único para todos os subgraphs que processa. @@ -77,4 +77,4 @@ O Graph Node deve então sincronizar o subgraph lançado caso não haja erros. D ## Subgraphs movidos por Substreams -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/pt/indexing/overview.mdx b/website/pages/pt/indexing/overview.mdx index 00392d71f392..468fbd0a06c2 100644 --- a/website/pages/pt/indexing/overview.mdx +++ b/website/pages/pt/indexing/overview.mdx @@ -87,7 +87,7 @@ Quando uma alocação é fechada, os rebates podem ser reivindicados pelo Indexa ### O que são porção de taxa de consulta e porção de recompensa de indexação? -Os valores `queryFeeCut` e `indexingRewardCut` são parâmetros de delegação que o Indexador pode configurar junto com o `cooldownBlocks` para controlar a distribuição de GRT entre o Indexador e os seus Delegantes. Veja os últimos passos no [Staking no Protocolo](/network/indexing#stake-in-the-protocol) para instruções sobre como configurar os parâmetros de delegação. +Os valores `queryFeeCut` e `indexingRewardCut` são parâmetros de delegação que o Indexador pode configurar junto com o `cooldownBlocks` para controlar a distribuição de GRT entre o Indexador e os seus Delegantes. Veja os últimos passos no [Staking no Protocolo](/network/indexing/#stake-in-the-protocol) para instruções sobre como configurar os parâmetros de delegação. - **queryFeeCut** - o % de rebates de taxas de query a ser distribuído ao Indexador. Se isto for configurado em 95%, o Indexador receberá 95% das taxas de query ganhas quando uma alocação for fechada, com os outros 5% destinados aos Delegantes. @@ -121,7 +121,7 @@ Os Indexadores podem se diferenciar ao aplicar técnicas avançadas para decidir ### Há alguma precaução básica de segurança que um Indexador deve tomar? -- **Carteira de operador** — Configurar uma carteira de operador é importante, pois permite a um Indexador manter a separação entre as suas chaves que controlam o stake e aquelas no controlo das operações diárias. Mais informações em [Staking no Protocolo](/network/indexing#stake-in-the-protocol). +- **Carteira de operador** — Configurar uma carteira de operador é importante, pois permite a um Indexador manter a separação entre as suas chaves que controlam o stake e aquelas no controlo das operações diárias. Mais informações em [Staking no Protocolo](/network/indexing/#stake-in-the-protocol). - **Firewall** - O serviço de Indexadores é o único que precisa ser exposto publicamente, e o trancamento de portas de admin e acesso ao banco de dados exigem muito mais atenção: o endpoint JSON-RPC do Graph Node (porta padrão: 8030), o endpoint da API de gerenciamento do Indexador (porta padrão: 18000), e o endpoint do banco de dados Postgres (porta padrão: 5432) não devem ser expostos. @@ -375,7 +375,7 @@ Para participar com êxito na rede, são necessários monitorados e interações #### Começando -O agente indexador e o serviço indexador devem ser co-localizados com a sua infraestrutura de Graph Node. Há várias maneiras de preparar ambientes de execução virtual para os seus componentes de Indexador. Aqui, veja como executá-los em um bare-metal (servidor dedicado) com pacotes NPM ou código fonte, ou através do Kubernetes e o docker no Engine Kubernetes do Google Cloud. Se estes exemplos de setup não batem bem com a sua infraestrutura, provavelmente deverá consultar um guia de comunidade no nosso [Discord](https://discord.gg/graphprotocol). Lembre-se de [fazer staking no protocolo](/network/indexing#stake-in-the-protocol) antes de iniciar os seus componentes de Indexador! +O agente indexador e o serviço indexador devem ser co-localizados com a sua infraestrutura de Graph Node. Há várias maneiras de preparar ambientes de execução virtual para os seus componentes de Indexador. Aqui, veja como executá-los em um bare-metal (servidor dedicado) com pacotes NPM ou código fonte, ou através do Kubernetes e o docker no Engine Kubernetes do Google Cloud. Se estes exemplos de setup não batem bem com a sua infraestrutura, provavelmente deverá consultar um guia de comunidade no nosso [Discord](https://discord.gg/graphprotocol). Lembre-se de [fazer staking no protocolo](/network/indexing/#stake-in-the-protocol) antes de iniciar os seus componentes de Indexador! #### De pacotes NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Usando K8s e Terraform -Veja a seção sobre [preparar infraestruturas de servidor usando o Terraform no Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Veja a seção sobre [preparar infraestruturas de servidor usando o Terraform no Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Uso @@ -755,7 +755,7 @@ Os primeiros passos para participar como Indexador consistem em aprovar o protoc > Nota: Para os propósitos destas instruções, o Remix será usado para interação com contratos, mas é possível escolher a sua própria ferramenta ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/) e [MyCrypto](https://www.mycrypto.com/account) são algumas outras ferramentas conhecidas). -Quando um Indexador faz stake de GRT no protocolo, será possível iniciar os seus [componentes](/network/indexing#indexer-components) e começar as suas interações com a rede. +Quando um Indexador faz stake de GRT no protocolo, será possível iniciar os seus [componentes](/network/indexing/#indexer-components) e começar as suas interações com a rede. #### Aprovação de tokens diff --git a/website/pages/pt/resources/benefits.mdx b/website/pages/pt/resources/benefits.mdx index 8bdc4445ed97..934141f16a33 100644 --- a/website/pages/pt/resources/benefits.mdx +++ b/website/pages/pt/resources/benefits.mdx @@ -76,7 +76,7 @@ Os custos de query podem variar; o custo citado é o normal até o fechamento da ‡Reflete o custo ao consumidor de dados. Taxas de query ainda são pagas a Indexadores por queries do Plano Grátis. -Os custos estimados são apenas para subgraphs na Mainnet do Ethereum — os custos são maiores ao auto-hospedar um `graph-node` em outras redes. Alguns utilizadores devem atualizar o seu subgraph a uma versão mais recente. Até o fechamento deste texto, devido às taxas de gas do Ethereum, uma atualização custa cerca de 50 dólares. Note que as taxas de gás no [Arbitrum](/arbitrum/arbitrum-faq) são muito menores que as da mainnet do Ethereum. +Os custos estimados são apenas para subgraphs na Mainnet do Ethereum — os custos são maiores ao auto-hospedar um `graph-node` em outras redes. Alguns utilizadores devem atualizar o seu subgraph a uma versão mais recente. Até o fechamento deste texto, devido às taxas de gas do Ethereum, uma atualização custa cerca de 50 dólares. Note que as taxas de gás no [Arbitrum](/arbitrum/arbitrum-faq/) são muito menores que as da mainnet do Ethereum. Curar um sinal em um subgraph é um custo opcional, único, e zero-líquido (por ex., $1 mil em um subgraph pode ser curado em um subgraph, e depois retirado — com potencial para ganhar retornos no processo). diff --git a/website/pages/pt/resources/roles/curating.mdx b/website/pages/pt/resources/roles/curating.mdx index 89fc295d4c15..6c610c74825a 100644 --- a/website/pages/pt/resources/roles/curating.mdx +++ b/website/pages/pt/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Os indexadores podem achar subgraphs para indexar com base em sinais de curadori ## Como Sinalizar -Dentro da aba Curator (Curador) no Graph Explorer, os curadores poderão sinalizar ou retirar os seus sinais em certos subgraphs com base nas estatísticas da rede. Para uma explicação passo a passo deste processo no Explorer, [clique aqui.](/network/explorer) +Dentro da aba Curator (Curador) no Graph Explorer, os curadores poderão sinalizar ou retirar os seus sinais em certos subgraphs com base nas estatísticas da rede. Para uma explicação passo a passo deste processo no Explorer, [clique aqui.](/network/explorer/) Um curador pode escolher sinalizar uma versão específica de subgraph, ou pode automaticamente migrar o seu sinal à versão mais recente desse subgraph. Ambas estratégias são válidas, e vêm com as suas próprias vantagens e desvantagens. @@ -48,7 +48,7 @@ Porém, é recomendado que curadores deixem o seu GRT no lugar, não apenas para 1. O mercado de consulta é jovem por natureza no The Graph, e há sempre o risco do seu rendimento anual ser menor que o esperado devido às dinâmicas nascentes do mercado. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Um subgraph pode falhar devido a um erro de código. Um subgraph falho não acumula taxas de consulta. Portanto, espere até o programador consertar o erro e lançar uma nova versão. - Caso se inscreva à versão mais recente de um subgraph, suas ações migrarão automaticamente a esta versão nova. Isto incorrerá uma taxa de curadoria de 0.5%. - Se sinalizou em um subgraph específico e ele falhou, deverá queimar as suas ações de curadoria manualmente. Será então possível sinalizar na nova versão do subgraph, o que incorre uma taxa de curadoria de 1%. diff --git a/website/pages/pt/subgraphs/cookbook/grafting.mdx b/website/pages/pt/subgraphs/cookbook/grafting.mdx index 70bffd53aae8..6e4946384443 100644 --- a/website/pages/pt/subgraphs/cookbook/grafting.mdx +++ b/website/pages/pt/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ O subgraph enxertado pode usar um schema GraphQL que não é idêntico ao schema Para mais informações, confira: -- [Enxertos](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Enxertos](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) Neste tutorial, cobriremos um caso de uso básico. Substituiremos um contrato existente com um contrato idêntico (com um novo endereço, mas o mesmo código). Depois, enxertaremos o subgraph existente ao subgraph "base" que rastreará o novo contrato. diff --git a/website/pages/pt/subgraphs/cookbook/near.mdx b/website/pages/pt/subgraphs/cookbook/near.mdx index a08c08d3f056..346056b7887c 100644 --- a/website/pages/pt/subgraphs/cookbook/near.mdx +++ b/website/pages/pt/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ Há três aspectos de definição de subgraph: **subgraph.yaml:** o manifest do subgraph, que define as fontes de dados de interesse e como elas devem ser processadas. A NEAR é uma nova espécie (`kind`) de fonte de dados. -**schema.graphql:** um arquivo schema que define quais dados são armazenados para o seu subgraph, e como consultá-los via GraphQL. Os requerimentos para subgraphs no NEAR são cobertos pela [documentação existente](/developing/creating-a-subgraph#the-graphql-schema). +**schema.graphql:** um arquivo schema que define quais dados são armazenados para o seu subgraph, e como consultá-los via GraphQL. Os requerimentos para subgraphs no NEAR são cobertos pela [documentação existente](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**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. Existem dois comandos importantes durante o desenvolvimento de um subgraph: @@ -92,13 +92,13 @@ As fontes de dados na NEAR apoiam duas categorias de handlers: ### Definição de Schema -A definição do schema descreve a estrutura do banco de dados do subgraph resultante e os relacionamentos entre entidades. Isto é agnóstico da fonte de dados original. Mais detalhes na definição do schema de subgraph [aqui](/developing/creating-a-subgraph#the-graphql-schema). +A definição do schema descreve a estrutura do banco de dados do subgraph resultante e os relacionamentos entre entidades. Isto é agnóstico da fonte de dados original. Mais detalhes na definição do schema de subgraph [aqui](/developing/creating-a-subgraph/#the-graphql-schema). ### Mapeamentos em AssemblyScript Os handlers para o processamento de eventos são escritos em [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Estes tipos são repassados para handlers de blocos e recibos: - Handlers de blocos receberão um `Block` - Handlers de recibos receberão um `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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. ## Lançando um Subgraph na NEAR @@ -178,7 +178,7 @@ O Subgraph Studio e o Indexador de atualização na Graph Network apoiam atualme - `near-mainnet` - `near-testnet` -Saiba mais sobre a criação e lançamento de subgraphs no Subgraph Studio [aqui](/deploying/deploying-a-subgraph-to-studio). +Saiba mais sobre a criação e lançamento de subgraphs no Subgraph Studio [aqui](/deploying/deploying-a-subgraph-to-studio/). Para começo de conversa, o primeiro passo consiste em "criar" o seu subgraph - isto só precisa ser feito uma vez. No Subgraph Studio, isto pode ser feito do [seu Painel](https://thegraph.com/studio/): "Criar um subgraph". @@ -228,7 +228,7 @@ Em breve, falaremos mais sobre como executar os componentes acima. ## Como Consultar um Subgraph na NEAR -O endpoint da GraphQL para subgraphs na NEAR é determinado pela definição do schema, com a interface existente da API. Mais informações na [documentação da API GraphQL](/querying/graphql-api). +O endpoint da GraphQL para subgraphs na NEAR é determinado pela definição do schema, com a interface existente da API. Mais informações na [documentação da API GraphQL](/querying/graphql-api/). ## Exemplos de Subgraphs diff --git a/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx index 0705480c4f03..7a8824c97c1c 100644 --- a/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: API AssemblyScript --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ No manifest do subgraph, `apiVersion` especifica a versão da API de mapeamento, | 0.0.8 | Adiciona validação para existência de campos no schema ao salvar uma entidade. | | 0.0.7 | Classes `TransactionReceipt` e `Log` adicionadas aos tipos do EthereumCampo
Campo `receipt` adicionado ao objeto Ethereum Event | | 0.0.6 | Campo `nonce` adicionado ao objeto Ethereum TransactionCampo
`baseFeePerGas` adicionado ao objeto Ethereum Block | -| 0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` | | 0.0.4 | Campo `functionSignature` adicionado ao objeto Ethereum SmartContractCall | | 0.0.3 | Campo `from` adicionado ao objeto Ethereum
`Calletherem.call.address` renomeado para `ethereum.call.to` | | 0.0.2 | Campo `input` adicionado ao objeto Ethereum Transaction | diff --git a/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx index 213d9736033c..5a1bf2c57245 100644 --- a/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ Os arquivos da ABI devem combinar com o(s) seu(s) contrato(s). Há algumas manei | Versão | Notas de atualização | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx b/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx index a1518a96b957..a0909930982a 100644 --- a/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/pt/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/pt/subgraphs/developing/deploying/multiple-networks.mdx index 91bdd9f3e94a..7164b6d5a83c 100644 --- a/website/pages/pt/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/pt/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Como lançar o subgraph a várias redes diff --git a/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx index f54b8f30084a..b25acabaaee8 100644 --- a/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli Para ter apoio de Indexadores na Graph Network, os subgraphs devem: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Não deve usar quaisquer das seguintes características: - ipfs.cat & ipfs.map - Erros não-fatais diff --git a/website/pages/pt/subgraphs/developing/developer-faq.mdx b/website/pages/pt/subgraphs/developing/developer-faq.mdx index 1c04ef6523c0..39aa8d332e6e 100644 --- a/website/pages/pt/subgraphs/developing/developer-faq.mdx +++ b/website/pages/pt/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Dentro de um subgraph, os eventos são sempre processados na ordem em que aparec Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Confira a seção "como instanciar um modelo de fontes de dados" em: [Modelos de fontes de dados](/developing/creating-a-subgraph#data-source-templates). +Confira a seção "como instanciar um modelo de fontes de dados" em: [Modelos de fontes de dados](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -Veja a lista das redes apoiadas [aqui](/developing/supported-networks). +Veja a lista das redes apoiadas [aqui](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Sim. O Sepolia apoia handlers de blocos, chamadas e eventos. Vale notar que hand ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx index acbf7b78103f..e39eddc376eb 100644 --- a/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Como Editar um Subgraph na Rede Descentralizada --- -Após [lançar o seu subgraph ao Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) e prepará-lo para entrar em produção, será possível editá-lo na rede descentralizada. +Após [lançar o seu subgraph ao Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) e prepará-lo para entrar em produção, será possível editá-lo na rede descentralizada. Ao editar um subgraph à rede descentralizada, ele será disponibilizado para: -- Curadoria por [Curadores](/network/curating). -- Indexação por [Indexadores](/network/indexing). +- Curadoria por [Curadores](/network/curating/). +- Indexação por [Indexadores](/network/indexing/). -Confira a lista de [redes apoiadas](/developing/supported-networks). +Confira a lista de [redes apoiadas](/developing/supported-networks/). ## Edição do Subgraph Studio @@ -21,9 +21,9 @@ Confira a lista de [redes apoiadas](/developing/supported-networks). Todas as versões editadas de um subgraph existente podem: -- Ser editadas ao Arbitrum One. [Aprenda mais sobre a Graph Network no Arbitrum](/arbitrum/arbitrum-faq). +- Ser editadas ao Arbitrum One. [Aprenda mais sobre a Graph Network no Arbitrum](/arbitrum/arbitrum-faq/). -- Indexar dados em quaisquer das [redes apoiadas](/developing/supported-networks), independente da rede na qual o subgraph foi editado. +- Indexar dados em quaisquer das [redes apoiadas](/developing/supported-networks/), independente da rede na qual o subgraph foi editado. ### Como atualizar metadados para um subgraph editado @@ -69,7 +69,7 @@ Programadores podem adicionar sinal de GRT aos seus subgraphs para incentivar In - É possível conferir a elegibilidade a recompensas de indexação com base no uso de ferramentas de subgraph [aqui](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Redes apoiadas específicas podem ser conferidas [aqui](/developing/supported-networks). +- Redes apoiadas específicas podem ser conferidas [aqui](/developing/supported-networks/). > Adicionar sinais a um subgraph que não for elegível não atrairá mais Indexadores. diff --git a/website/pages/pt/subgraphs/explorer.mdx b/website/pages/pt/subgraphs/explorer.mdx index 31d87224dc8c..43409fd827bb 100644 --- a/website/pages/pt/subgraphs/explorer.mdx +++ b/website/pages/pt/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Para aprender mais sobre como tornar-se um Indexador, pode conferir a [documentação oficial](/network/indexing) ou [os guias de Indexador da Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) +Para aprender mais sobre como tornar-se um Indexador, pode conferir a [documentação oficial](/network/indexing/) ou [os guias de Indexador da Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) ![Painel de detalhes de indexação](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Imagem do Explorer 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegantes @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - A quantidade total de GRT que têm no protocolo no momento - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Rede diff --git a/website/pages/pt/subgraphs/querying/best-practices.mdx b/website/pages/pt/subgraphs/querying/best-practices.mdx index 895e871ab11a..eb77bb132e9c 100644 --- a/website/pages/pt/subgraphs/querying/best-practices.mdx +++ b/website/pages/pt/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Cada `queryName` deve ser usado apenas uma vez por operação. - Cada `field` deve ser usado apenas uma vez numa seleção (não podemos consultar a `id` duas vezes sob o `token`) -- Alguns `fields`s ou queries (como `tokens`) retornam tipos complexos que requerem uma seleção de subcampo. Não providenciar uma seleção quando esperado (ou providenciar uma quando não é esperado - por exemplo, no `id`) resultará num erro. Para conhecer um tipo de campo, consulte o [Graph Explorer](/network/explorer). +- Alguns `fields`s ou queries (como `tokens`) retornam tipos complexos que requerem uma seleção de subcampo. Não providenciar uma seleção quando esperado (ou providenciar uma quando não é esperado - por exemplo, no `id`) resultará num erro. Para conhecer um tipo de campo, consulte o [Graph Explorer](/network/explorer/). - Qualquer variável apontada a um argumento deve corresponder ao seu tipo. - Em uma lista dada de variáveis, cada uma delas deve ser única. - Todas as variáveis definidas devem ser usadas. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Gestão de Subgraph Cross-chain: Queries de múltiplos subgraphs numa única consulta - [Rastreamento Automático de Blocos](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/pt/subgraphs/querying/graphql-api.mdx b/website/pages/pt/subgraphs/querying/graphql-api.mdx index 1a7a109cdaaf..274f93e3c81f 100644 --- a/website/pages/pt/subgraphs/querying/graphql-api.mdx +++ b/website/pages/pt/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ Esta consulta retornará entidades `Challenge` e as entidades `Application` asso ### Consultas de Busca Fulltext -Campos de busca fulltext fornecem uma API de busca de texto expressiva, que pode ser adicionada e personalizada ao schema do subgraph. Refira ao [Definindo Campos de Busca Fulltext](/developing/creating-a-subgraph#defining-fulltext-search-fields) para adicionar buscas fulltext ao seu subgraph. +Campos de busca fulltext fornecem uma API de busca de texto expressiva, que pode ser adicionada e personalizada ao schema do subgraph. Refira ao [Definindo Campos de Busca Fulltext](/developing/creating-a-subgraph/#defining-fulltext-search-fields) para adicionar buscas fulltext ao seu subgraph. Buscas fulltext têm um campo obrigatório, `text`, para ofertar termos de busca. Vários operadores especiais de fulltext estão disponíveis para uso neste campo de busca `text`. diff --git a/website/pages/pt/subgraphs/querying/introduction.mdx b/website/pages/pt/subgraphs/querying/introduction.mdx index 2d0922e65ff6..fddfd118b38c 100644 --- a/website/pages/pt/subgraphs/querying/introduction.mdx +++ b/website/pages/pt/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Queries no The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Por favor, confira a [API de Queries](/querying/graphql-api) para uma referência completa em como fazer queries das entidades do subgraph. É possível ler sobre as melhores práticas de querying em GraphQL [aqui](/querying/querying-best-practices) +> Por favor, confira a [API de Queries](/querying/graphql-api/) para uma referência completa em como fazer queries das entidades do subgraph. É possível ler sobre as melhores práticas de querying em GraphQL [aqui](/querying/querying-best-practices/) > Nota: Se encontrar erros 405 com um pedido GET ao URL do Graph Explorer, use um pedido POST. @@ -14,8 +14,8 @@ Cada subgraph publicado à Graph Network tem um URL singular de query no Graph E ![Query Subgraph URL](/img/query-url-screenshot.png) -Aprenda mais sobre queries de um aplicativo [aqui](/querying/querying-from-an-application). +Aprenda mais sobre queries de um aplicativo [aqui](/querying/querying-from-an-application/). -Como deve ter percebido, este URL de query deve usar uma chave de API singular. Dá para criar e gerir as suas chaves de API no [Subgraph Studio](https://thegraph.com/studio), na seção "API Keys". Leia mais sobre como usar o Subgraph Studio [aqui](/deploying/subgraph-studio). +Como deve ter percebido, este URL de query deve usar uma chave de API singular. Dá para criar e gerir as suas chaves de API no [Subgraph Studio](https://thegraph.com/studio), na seção "API Keys". Leia mais sobre como usar o Subgraph Studio [aqui](/deploying/subgraph-studio/). Utilizadores do Subgraph Studio começam com um Plano Grátis, que os permite realizar 100 mil queries por mês. Mais queries estão disponíveis no Plano de Crescimento, que oferece preços baseados em uso para queries adicionais; estes podem ser pagos em cartão de crédito ou em GRT no Arbitrum. Aprenda mais sobre cobranças [aqui](/billing/). diff --git a/website/pages/pt/substreams/sps/introduction.mdx b/website/pages/pt/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/pt/substreams/sps/introduction.mdx +++ b/website/pages/pt/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/pt/substreams/sps/triggers.mdx b/website/pages/pt/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/pt/substreams/sps/triggers.mdx +++ b/website/pages/pt/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/pt/supported-networks.mdx b/website/pages/pt/supported-networks.mdx index 7a1a1d46a772..b47490b02a0c 100644 --- a/website/pages/pt/supported-networks.mdx +++ b/website/pages/pt/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Apoio à rede base providenciado pelo [Indexador de atualização](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integração com o Graph Node: `evm`, `near`, `cosmos`, `osmosis` e `ar` têm apoio nativo a handlers e tipos no Graph Node. Chains compatíveis com Firehose e Substreams podem utilizar a integração generalizada de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs) (isto inclui as redes `evm` e `near`). ⁠† apoia o lançamento de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs). +\*\* Integração com o Graph Node: `evm`, `near`, `cosmos`, `osmosis` e `ar` têm apoio nativo a handlers e tipos no Graph Node. Chains compatíveis com Firehose e Substreams podem utilizar a integração generalizada de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) (isto inclui as redes `evm` e `near`). ⁠† apoia o lançamento de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/). - O Subgraph Studio depende da estabilidade e da confiança das tecnologias subjacentes, por exemplo, JSON-RPC, Firehose e endpoints dos Substreams. - Subgraphs que indexam a Gnosis Chain agora podem ser lançados com a identificadora de rede `gnosis`. diff --git a/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx index 5ba89020402c..e516573fd4d9 100644 --- a/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/ro/archived/sunrise.mdx b/website/pages/ro/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/ro/archived/sunrise.mdx +++ b/website/pages/ro/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ro/contracts.mdx b/website/pages/ro/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/ro/contracts.mdx +++ b/website/pages/ro/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ro/indexing/new-chain-integration.mdx b/website/pages/ro/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/ro/indexing/new-chain-integration.mdx +++ b/website/pages/ro/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ro/indexing/overview.mdx b/website/pages/ro/indexing/overview.mdx index a6844c2da009..c05c37a275ef 100644 --- a/website/pages/ro/indexing/overview.mdx +++ b/website/pages/ro/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens diff --git a/website/pages/ro/resources/benefits.mdx b/website/pages/ro/resources/benefits.mdx index a26794b2abc1..044853e8850b 100644 --- a/website/pages/ro/resources/benefits.mdx +++ b/website/pages/ro/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/ro/resources/roles/curating.mdx b/website/pages/ro/resources/roles/curating.mdx index a5a63f3e2751..a3b96ed010fe 100644 --- a/website/pages/ro/resources/roles/curating.mdx +++ b/website/pages/ro/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ro/subgraphs/cookbook/grafting.mdx b/website/pages/ro/subgraphs/cookbook/grafting.mdx index 6c3b85419af9..7aa79c7e2755 100644 --- a/website/pages/ro/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ro/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/ro/subgraphs/cookbook/near.mdx b/website/pages/ro/subgraphs/cookbook/near.mdx index 8e0be3f5ce4e..cc0bf8637bee 100644 --- a/website/pages/ro/subgraphs/cookbook/near.mdx +++ b/website/pages/ro/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx index 6a0c4e208b99..8aa0bf0027bf 100644 --- a/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx index 7770743f9944..20748328de9e 100644 --- a/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ro/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/ro/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/ro/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/ro/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx index d8bb14e9f3c1..3c6f62194eed 100644 --- a/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/ro/subgraphs/developing/developer-faq.mdx b/website/pages/ro/subgraphs/developing/developer-faq.mdx index e783db4c3d8f..2282091fde23 100644 --- a/website/pages/ro/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ro/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 9de36745a95b..4728db3eb245 100644 --- a/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/ro/subgraphs/explorer.mdx b/website/pages/ro/subgraphs/explorer.mdx index 02dca6ed2f9f..d874f80f5140 100644 --- a/website/pages/ro/subgraphs/explorer.mdx +++ b/website/pages/ro/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/ro/subgraphs/querying/best-practices.mdx b/website/pages/ro/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/ro/subgraphs/querying/best-practices.mdx +++ b/website/pages/ro/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/ro/subgraphs/querying/graphql-api.mdx b/website/pages/ro/subgraphs/querying/graphql-api.mdx index 3dd70fc7b004..917fad3f2406 100644 --- a/website/pages/ro/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ro/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/ro/subgraphs/querying/introduction.mdx b/website/pages/ro/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/ro/subgraphs/querying/introduction.mdx +++ b/website/pages/ro/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ro/substreams/sps/introduction.mdx b/website/pages/ro/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/ro/substreams/sps/introduction.mdx +++ b/website/pages/ro/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ro/substreams/sps/triggers.mdx b/website/pages/ro/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/ro/substreams/sps/triggers.mdx +++ b/website/pages/ro/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/ro/supported-networks.mdx b/website/pages/ro/supported-networks.mdx index b36c202d793d..afeef5f62b9e 100644 --- a/website/pages/ro/supported-networks.mdx +++ b/website/pages/ro/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx index f77c7f686ac9..0ce4b2c48f21 100644 --- a/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Руководство по инструментам переноса L2 The Graph упростил переход на L2 в Arbitrum One. Для каждого участника протокола существует набор инструментов переноса L2, чтобы сделать переход на L2 бесшовным для всех участников сети. Эти инструменты потребуют от Вас выполнения определенного набора шагов в зависимости от того, что Вы передаете. -Ответы на некоторые частые вопросы об этих инструментах можно найти в [Часто задаваемые вопросы по инструментам переноса L2](/arbitrum/l2-transfer-tools-faq). Часто задаваемые вопросы содержат подробные объяснения того, как использовать инструменты, как они работают и что следует учитывать при их использовании. +Ответы на некоторые частые вопросы об этих инструментах можно найти в [Часто задаваемые вопросы по инструментам переноса L2](/arbitrum/l2-transfer-tools-faq/). Часто задаваемые вопросы содержат подробные объяснения того, как использовать инструменты, как они работают и что следует учитывать при их использовании. ## Как перенести свой субграф в Arbitrum (L2) diff --git a/website/pages/ru/archived/sunrise.mdx b/website/pages/ru/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/ru/archived/sunrise.mdx +++ b/website/pages/ru/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ru/contracts.mdx b/website/pages/ru/contracts.mdx index 6030fdf8e4e8..3b049e1bf499 100644 --- a/website/pages/ru/contracts.mdx +++ b/website/pages/ru/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ru/indexing/new-chain-integration.mdx b/website/pages/ru/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/ru/indexing/new-chain-integration.mdx +++ b/website/pages/ru/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ru/indexing/overview.mdx b/website/pages/ru/indexing/overview.mdx index be34140f88fa..445222da6b05 100644 --- a/website/pages/ru/indexing/overview.mdx +++ b/website/pages/ru/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### Что такое query fee cut и indexing reward cut? -Значения `queryFeeCut` и `indexingRewardCut` — это параметры делегирования, которые индексатор может установить вместе с cooldownBlocks для управления распределением GRT между индексатором и его делегаторами. См. последние шаги в разделе [Стейкинг в протоколе](/network/indexing#stake-in-the-protocol), чтобы получить инструкции по настройке параметров делегирования. +Значения `queryFeeCut` и `indexingRewardCut` — это параметры делегирования, которые индексатор может установить вместе с cooldownBlocks для управления распределением GRT между индексатором и его делегаторами. См. последние шаги в разделе [Стейкинг в протоколе](/network/indexing/#stake-in-the-protocol), чтобы получить инструкции по настройке параметров делегирования. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### Какие основные меры безопасности следует предпринять индексатору? -- **Operator wallet**. Настройка кошелька оператора является важной мерой безопасности, поскольку она позволяет индексатору поддерживать разделение между своими ключами, которые контролируют величину стейка, и теми, которые контролируют ежедневные операции. Инструкции см. в разделе [Stake in Protocol](/network/indexing#stake-in-the-protocol). +- **Operator wallet**. Настройка кошелька оператора является важной мерой безопасности, поскольку она позволяет индексатору поддерживать разделение между своими ключами, которые контролируют величину стейка, и теми, которые контролируют ежедневные операции. Инструкции см. в разделе [Stake in Protocol](/network/indexing/#stake-in-the-protocol). - **Firewall**. Только служба индексатора должна быть общедоступной, и особое внимание следует уделить блокировке портов администратора и доступа к базе данных: эндпоинт ноды The Graph JSON-RPC (порт по умолчанию: 8030), API эндпоинт для управления индексатором (порт по умолчанию: 18000) и эндпоинт базы данных Postgres (порт по умолчанию: 5432) не должны быть доступны. @@ -375,7 +375,7 @@ docker-compose up #### Начало работы -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### Из пакетов NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Использование K8s и Terraform -См. раздел [Настройка инфраструктуры сервера с помощью Terraform в Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +См. раздел [Настройка инфраструктуры сервера с помощью Terraform в Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Применение @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -После того как индексатор застейкал GRT в протоколе, можно запустить [Indexer components](/network/indexing#indexer-components) и начать взаимодействие с сетью. +После того как индексатор застейкал GRT в протоколе, можно запустить [Indexer components](/network/indexing/#indexer-components) и начать взаимодействие с сетью. #### Подтверждение токенов diff --git a/website/pages/ru/resources/benefits.mdx b/website/pages/ru/resources/benefits.mdx index 0def249bbf4e..db940b5c9fe6 100644 --- a/website/pages/ru/resources/benefits.mdx +++ b/website/pages/ru/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Курирование сигнала на субграфе - это необязательная единовременная стоимость, равная нулю (например, сигнал стоимостью 1 тыс. долларов может быть курирован на субграфе, а затем отозван - с возможностью получения прибыли в процессе). diff --git a/website/pages/ru/resources/roles/curating.mdx b/website/pages/ru/resources/roles/curating.mdx index 1d05b5c92262..1c6fac307c3a 100644 --- a/website/pages/ru/resources/roles/curating.mdx +++ b/website/pages/ru/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Как подавать Сигнал -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) Куратор может выбрать конкретную версию подграфа для сигнализации, или же он может выбрать автоматическую миграцию своего сигнала на самую новую рабочую сборку этого подграфа. Оба варианта являются допустимыми стратегиями и имеют свои плюсы и минусы. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Рынок запросов в The Graph по своей сути молод, и существует риск того, что ваш %APY может оказаться ниже, чем вы ожидаете, из-за зарождающейся динамики рынка. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Подграф может выйти из строя из-за ошибки. За неудавшийся подграф не начисляется плата за запрос. В результате вам придется ждать, пока разработчик исправит ошибку и выложит новую версию. - Если вы подписаны на новейшую версию подграфа, ваши общие ресурсы автоматически перейдут на эту новую версию. При этом будет взиматься кураторская комиссия в размере 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ru/subgraphs/cookbook/grafting.mdx b/website/pages/ru/subgraphs/cookbook/grafting.mdx index 60ed4fa7211f..61cf032d30ac 100644 --- a/website/pages/ru/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ru/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ title: Замените контракт и сохраните его истор Для получения дополнительной информации Вы можете перейти: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/ru/subgraphs/cookbook/near.mdx b/website/pages/ru/subgraphs/cookbook/near.mdx index 5badca17ae9b..e0ba36ed0191 100644 --- a/website/pages/ru/subgraphs/cookbook/near.mdx +++ b/website/pages/ru/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ The Graph предоставляет разработчикам инструме **subgraph.yaml:** манифест подграфа, определяющий источники данных, представляющие интерес, и как они должны быть обработаны. NEAR - это новый `вид` источника данных. -**schema.graphql:** файл схемы, который определяет, какие данные хранятся для вашего подграфа и как запрашивать их через GraphQL. Требования к подграфам NEAR рассматриваются в [существующей документации](/developing/creating-a-subgraph#the-graphql-schema). +**schema.graphql:** файл схемы, который определяет, какие данные хранятся для вашего подграфа и как запрашивать их через GraphQL. Требования к подграфам NEAR рассматриваются в [существующей документации](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**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. Во время разработки субграфа есть две ключевые команды: @@ -92,13 +92,13 @@ accounts: ### Определение схемы -Определение схемы описывает структуру результирующей базы данных подграфов и взаимосвязи между объектами. Это не зависит от исходного источника данных. Более подробная информация об определении схемы подграфа [ приведена здесь](/developing/creating-a-subgraph#the-graphql-schema). +Определение схемы описывает структуру результирующей базы данных подграфов и взаимосвязи между объектами. Это не зависит от исходного источника данных. Более подробная информация об определении схемы подграфа [ приведена здесь](/developing/creating-a-subgraph/#the-graphql-schema). ### Сопоставления AssemblyScript Обработчики событий написаны на языке [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - Обработчики блоков получат `Block` - Обработчики квитанций получат `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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 субграфа @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 Примечание: Если Вы создали субграф до версии `graph-cli`/`graph-ts` 0.22.0`, значит, Вы используете более старую версию AssemblyScript. Рекомендуется ознакомиться с [`Руководством по миграции\`](/release-notes/assemblyscript-migration-guide). +> Примечание: Если Вы создали субграф до версии `graph-cli`/`graph-ts` 0.22.0`, значит, Вы используете более старую версию AssemblyScript. Рекомендуется ознакомиться с [`Руководством по миграции\`](/release-notes/assemblyscript-migration-guide/). Узнайте, какие встроенные API можно использовать при написании мэппингов субграфов. По умолчанию доступны два типа API: @@ -35,7 +35,7 @@ title: AssemblyScript API | 0.0.8 | Добавлена проверка наличия полей в схеме при сохранении объекта. | | 0.0.7 | К типам Ethereum добавлены классы `TransactionReceipt` и `Log`
К объекту Ethereum Event добавлено поле `receipt` | | 0.0.6 | В объект Ethereum Transaction добавлено поле `nonce`
В объект Ethereum Block добавлено поле `baseFeePerGas` | -| 0.0.5 | AssemblyScript обновлен до версии 0.19.10 (включая критические изменения, см. [`Руководство по миграции`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` переименован в `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript обновлен до версии 0.19.10 (включая критические изменения, см. [`Руководство по миграции`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` переименован в `ethereum.transaction.gasLimit` | | 0.0.4 | В объект Ethereum SmartContractCall добавлено поле `functionSignature` | | 0.0.3 | В объект Ethereum Call добавлено поле `from`
`etherem.call.address` переименован в ethereum.call.to\` | | 0.0.2 | В объект Ethereum Transaction добавлено поле `input` | diff --git a/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx index cf29b952bd77..69757f55a845 100644 --- a/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | Версия | Примечания к релизу | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx index 687ed4af4826..871d523e0077 100644 --- a/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx index b8240d68ce51..5b6294339800 100644 --- a/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Индексировать [поддерживаемую сеть](/developing/supported-networks) +- Индексировать [поддерживаемую сеть](/developing/supported-networks/) - Не должны использовать ни одну из следующих функций: - ipfs.cat & ipfs.map - Неисправимые ошибки diff --git a/website/pages/ru/subgraphs/developing/developer-faq.mdx b/website/pages/ru/subgraphs/developing/developer-faq.mdx index 7ae20c6b3db9..ae17272c3b0b 100644 --- a/website/pages/ru/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ru/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ title: Часто задаваемы вопросы для разработчи Шаблоны позволяют Вам быстро создавать источники данных, пока Ваш субграф индексируется. Ваш контракт может создавать новые контракты по мере того, как люди будут с ним взаимодействовать. Поскольку форма этих контрактов (ABI, события и т. д.) известна заранее, Вы сможете определить, как Вы хотите индексировать их в шаблоне. Когда они будут сгенерированы, Ваш субграф создаст динамический источник данных, предоставив адрес контракта. -Ознакомьтесь с параграфом "Создание экземпляра шаблона источника данных" в разделе: [Шаблоны источников данных](/developing/creating-a-subgraph#data-source-templates). +Ознакомьтесь с параграфом "Создание экземпляра шаблона источника данных" в разделе: [Шаблоны источников данных](/developing/creating-a-subgraph/#data-source-templates). ### 11. Можно ли настроить субграф с помощью `graph init` из `graph-cli` с двумя контрактами? Или мне следует вручную добавить другой источник данных в `subgraph.yaml` после запуска `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. Какие сети поддерживает The Graph? -Вы можете найти список поддерживаемых сетей [здесь](/developing/supported-networks). +Вы можете найти список поддерживаемых сетей [здесь](/developing/supported-networks/). ### 17. Можно ли различать сети (майннет, Sepolia, локальную) внутри обработчиков событий? @@ -107,11 +107,11 @@ dataSource.address() ### 19. Можно ли указать, с какого блока следует начинать индексирование? -Да. `dataSources.source.startBlock` в файле `subgraph.yaml` указывает номер блока, с которого источник данных начинает индексирование. В большинстве случаев мы предлагаем использовать блок, в котором создавался контракт: [Стартовые блоки](/developing/creating-a-subgraph#start-blocks) +Да. `dataSources.source.startBlock` в файле `subgraph.yaml` указывает номер блока, с которого источник данных начинает индексирование. В большинстве случаев мы предлагаем использовать блок, в котором создавался контракт: [Стартовые блоки](/developing/creating-a-subgraph/#start-blocks) ### 20. Есть ли какие-либо советы по увеличению производительности индексирования? Синхронизация моего субграфа занимает очень много времени -Да, Вам следует обратить внимание на дополнительную функцию стартового блока, чтобы начать индексирование с блока, в котором был развернут контракт: [Стартовые блоки](/developing/creating-a-subgraph#start-blocks) +Да, Вам следует обратить внимание на дополнительную функцию стартового блока, чтобы начать индексирование с блока, в котором был развернут контракт: [Стартовые блоки](/developing/creating-a-subgraph/#start-blocks) ### 21. Есть ли способ напрямую запросить субграф, чтобы определить номер последнего проиндексированного блока? diff --git a/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 5538b40f01cf..7f70364c759c 100644 --- a/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Публикация подграфа в децентрализованной сети --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/ru/subgraphs/explorer.mdx b/website/pages/ru/subgraphs/explorer.mdx index c85daa791ead..81af4903f545 100644 --- a/website/pages/ru/subgraphs/explorer.mdx +++ b/website/pages/ru/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Чтобы узнать больше о том, как стать индексатором, ознакомьтесь с [официальной документацией](/network/indexing) или [Руководством для Индексаторов The Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) +Чтобы узнать больше о том, как стать индексатором, ознакомьтесь с [официальной документацией](/network/indexing/) или [Руководством для Индексаторов The Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) ![Панель сведений об индексировании](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Изображение проводника 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Делегаторы @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Общее количество GRT, которое у них имеется в настоящее время в протоколе - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Сеть diff --git a/website/pages/ru/subgraphs/querying/best-practices.mdx b/website/pages/ru/subgraphs/querying/best-practices.mdx index 8363d0264d43..fdaa93a598aa 100644 --- a/website/pages/ru/subgraphs/querying/best-practices.mdx +++ b/website/pages/ru/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/ru/subgraphs/querying/graphql-api.mdx b/website/pages/ru/subgraphs/querying/graphql-api.mdx index f539ff5637c4..2b28aa3ca64c 100644 --- a/website/pages/ru/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ru/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ The result of such a query will not change over time, i.e., querying at a certai ### Полнотекстовые поисковые запросы -Поля запроса полнотекстового поиска предоставляют API-интерфейс содержательного текстового поиска, который можно добавить в схему субграфа и настроить. См. [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields), чтобы добавить полнотекстовый поиск в свой субграф. +Поля запроса полнотекстового поиска предоставляют API-интерфейс содержательного текстового поиска, который можно добавить в схему субграфа и настроить. См. [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields), чтобы добавить полнотекстовый поиск в свой субграф. Запросы полнотекстового поиска имеют одно обязательное поле, `text`, для предоставления поисковых запросов. В этом поле поиска `text` можно использовать несколько специальных операторов полнотекстового поиска. diff --git a/website/pages/ru/subgraphs/querying/introduction.mdx b/website/pages/ru/subgraphs/querying/introduction.mdx index 58e40dbe8c06..d9d77a085ef3 100644 --- a/website/pages/ru/subgraphs/querying/introduction.mdx +++ b/website/pages/ru/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Запрос The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ru/substreams/sps/introduction.mdx b/website/pages/ru/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/ru/substreams/sps/introduction.mdx +++ b/website/pages/ru/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ru/substreams/sps/triggers.mdx b/website/pages/ru/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/ru/substreams/sps/triggers.mdx +++ b/website/pages/ru/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/ru/supported-networks.mdx b/website/pages/ru/supported-networks.mdx index 4efe3873f80f..cc3233aab732 100644 --- a/website/pages/ru/supported-networks.mdx +++ b/website/pages/ru/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Базовая поддержка сети обеспечивается [индексатором обновления](https://thegraph.com/blog/upgrade-indexer/). -\*\* Интеграция с Graph Node: `evm`, `near`, `cosmos`, `osmosis` и `ar` имеют собственный обработчик и поддержку типов в Graph Node. Чейны, совместимые с Firehose и Substreams, могут использовать обобщенную интеграцию [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs) (включая сети `evm` и `near`). ⁠† Поддерживает развертывание [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs). +\*\* Интеграция с Graph Node: `evm`, `near`, `cosmos`, `osmosis` и `ar` имеют собственный обработчик и поддержку типов в Graph Node. Чейны, совместимые с Firehose и Substreams, могут использовать обобщенную интеграцию [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs/) (включая сети `evm` и `near`). ⁠† Поддерживает развертывание [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio полагается на стабильность и надежность базовых технологий, например, таких, как JSON-RPC, Firehose и конечных точек Substreams. - Субграфы, индексирующие Gnosis Chain, теперь могут быть развернуты с помощью сетевого идентификатора `gnosis`. diff --git a/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx index 52a4522b0afc..851c7817e865 100644 --- a/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Guide för överföringsverktyg The Graph har gjort det enkelt att flytta till L2 på Arbitrum One. För varje protokolldeltagare finns det en uppsättning L2 överföringsverktyg som gör överföringen till L2 sömlös för alla nätverksdeltagare. Dessa verktyg kräver att du följer en specifik uppsättning steg beroende på vad du överför. -Några vanliga frågor om dessa verktyg besvaras i [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). De vanliga frågorna innehåller djupgående förklaringar av hur du använder verktygen, hur de fungerar och saker att tänka på när du använder dem. +Några vanliga frågor om dessa verktyg besvaras i [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). De vanliga frågorna innehåller djupgående förklaringar av hur du använder verktygen, hur de fungerar och saker att tänka på när du använder dem. ## Så här överför du din subgraf till Arbitrum (L2) diff --git a/website/pages/sv/archived/sunrise.mdx b/website/pages/sv/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/sv/archived/sunrise.mdx +++ b/website/pages/sv/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/sv/contracts.mdx b/website/pages/sv/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/sv/contracts.mdx +++ b/website/pages/sv/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/sv/indexing/new-chain-integration.mdx b/website/pages/sv/indexing/new-chain-integration.mdx index d3584aea08f5..bda83128ff44 100644 --- a/website/pages/sv/indexing/new-chain-integration.mdx +++ b/website/pages/sv/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graf Node bör synkronisera den distribuerade subgrafen om det inte finns några ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/sv/indexing/overview.mdx b/website/pages/sv/indexing/overview.mdx index c1916a3e9a8e..8249649e259e 100644 --- a/website/pages/sv/indexing/overview.mdx +++ b/website/pages/sv/indexing/overview.mdx @@ -87,7 +87,7 @@ När en tilldelning har avslutats är återbetalningarna tillgängliga för Inde ### Vad är frågeavgiftsminskning och minskning av indexeringsbelöning? -Värdena `queryFeeCut` och `indexingRewardCut` är delegationparametrar som Indexern kan sätta tillsammans med `cooldownBlocks` för att kontrollera distributionen av GRT mellan Indexern och deras Delegatorer. Se de sista stegen i [Staking i protokollet](/network/indexing#stake-in-the-protocol) för anvisningar om att ställa in delegationparametrarna. +Värdena `queryFeeCut` och `indexingRewardCut` är delegationparametrar som Indexern kan sätta tillsammans med `cooldownBlocks` för att kontrollera distributionen av GRT mellan Indexern och deras Delegatorer. Se de sista stegen i [Staking i protokollet](/network/indexing/#stake-in-the-protocol) för anvisningar om att ställa in delegationparametrarna. - **queryFeeCut** - andelen frågeavgiftsåterbetalningar som kommer att distribueras till Indexern. Om detta är inställt på 95% kommer Indexern att få 95% av de frågeavgifter som tjänas när en tilldelning avslutas, medan de andra 5% fördelas till Delegatorerna. @@ -121,7 +121,7 @@ Indexers kan skilja sig åt genom att tillämpa avancerade tekniker för att fat ### Vilka grundläggande säkerhetsåtgärder bör en Indexer vidta? -- **Operatörplånbok** - Att skapa en operatörplånbok är en viktig försiktighetsåtgärd eftersom den möjliggör att en Indexer kan upprätthålla separation mellan sina nycklar som styr insatsen och de som är ansvariga för dagliga operationer. Se [Insats i protokollet](/network/indexing#stake-in-the-protocol) för anvisningar. +- **Operatörplånbok** - Att skapa en operatörplånbok är en viktig försiktighetsåtgärd eftersom den möjliggör att en Indexer kan upprätthålla separation mellan sina nycklar som styr insatsen och de som är ansvariga för dagliga operationer. Se [Insats i protokollet](/network/indexing/#stake-in-the-protocol) för anvisningar. - **Brandvägg** - Endast Indexertjänsten behöver vara offentligt exponerad och särskild uppmärksamhet bör ägnas åt att säkra administrativa portar och databasåtkomst: Graph Node JSON-RPC-gränssnittet (standardport: 8030), Indexerhanterings-API-gränssnittet (standardport: 18000) och PostgreSQL-databasgränssnittet (standardport: 5432) bör inte vara exponerade. @@ -375,7 +375,7 @@ För att framgångsrikt delta i nätverket krävs nästan konstant övervakning #### Komma igång -Indexer-agent och Indexer-service bör placeras tillsammans med din Graph Node-infrastruktur. Det finns många sätt att konfigurera virtuella exekveringsmiljöer för dina Indexer-komponenter; här förklarar vi hur du kör dem på bare-metal med hjälp av NPM-paket eller källkod, eller via Kubernetes och Docker på Google Cloud Kubernetes Engine. Om dessa installations exempel inte passar bra för din infrastruktur kommer det sannolikt att finnas en gemenskapsråd att använda som referens, kom och säg hej på [Discord](https://discord.gg/graphprotocol)! Kom ihåg att [satsa på protokollet](/network/indexing#stake-in-the-protocol) innan du startar dina Indexer-komponenter! +Indexer-agent och Indexer-service bör placeras tillsammans med din Graph Node-infrastruktur. Det finns många sätt att konfigurera virtuella exekveringsmiljöer för dina Indexer-komponenter; här förklarar vi hur du kör dem på bare-metal med hjälp av NPM-paket eller källkod, eller via Kubernetes och Docker på Google Cloud Kubernetes Engine. Om dessa installations exempel inte passar bra för din infrastruktur kommer det sannolikt att finnas en gemenskapsråd att använda som referens, kom och säg hej på [Discord](https://discord.gg/graphprotocol)! Kom ihåg att [satsa på protokollet](/network/indexing/#stake-in-the-protocol) innan du startar dina Indexer-komponenter! #### Från NPM-paket @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Användning av K8s och Terraform -Se avsnittet [Konfigurera serverinfrastruktur med Terraform på Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Se avsnittet [Konfigurera serverinfrastruktur med Terraform på Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Användning @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -När en Indexer har satsat GRT i protokollet kan [Indexer-komponenterna](/network/indexing#indexer-components) startas och börja interagera med nätverket. +När en Indexer har satsat GRT i protokollet kan [Indexer-komponenterna](/network/indexing/#indexer-components) startas och börja interagera med nätverket. #### Godkänn tokens diff --git a/website/pages/sv/resources/benefits.mdx b/website/pages/sv/resources/benefits.mdx index 0e8e42ee4eb8..c83dad663194 100644 --- a/website/pages/sv/resources/benefits.mdx +++ b/website/pages/sv/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Att kurera signal på en subgraf är en valfri engångskostnad med noll nettokostnad (t.ex. $1k i signal kan kurera på en subgraf och senare dras tillbaka - med potential att tjäna avkastning i processen). diff --git a/website/pages/sv/resources/roles/curating.mdx b/website/pages/sv/resources/roles/curating.mdx index 89b3b4d392f3..3e24502b8cf9 100644 --- a/website/pages/sv/resources/roles/curating.mdx +++ b/website/pages/sv/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Hur man Signaliserar -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) En kurator kan välja att signalera på en specifik subgrafversion, eller så kan de välja att ha sin signal automatiskt migrerad till den nyaste produktionsversionen av den subgrafen. Båda är giltiga strategier och har sina egna för- och nackdelar. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Frågemarknaden är i grunden ung på The Graph och det finns en risk att din %APY kan vara lägre än du förväntar dig på grund av tidiga marknadsmekanik. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. En subgraf kan misslyckas på grund av en bugg. En misslyckad subgraf genererar inte frågeavgifter. Som ett resultat måste du vänta tills utvecklaren rättar felet och distribuerar en ny version. - Om du prenumererar på den nyaste versionen av en subgraf kommer dina andelar automatiskt att migreras till den nya versionen. Detta kommer att medföra en kuratoravgift på 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/sv/subgraphs/cookbook/grafting.mdx b/website/pages/sv/subgraphs/cookbook/grafting.mdx index 8ddfa857f8da..96ed588bc5b2 100644 --- a/website/pages/sv/subgraphs/cookbook/grafting.mdx +++ b/website/pages/sv/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ Den ympade subgrafen kan använda ett GraphQL-schema som inte är identiskt med För mer information kan du kontrollera: -- [Ympning](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Ympning](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/sv/subgraphs/cookbook/near.mdx b/website/pages/sv/subgraphs/cookbook/near.mdx index 4c3c34017cb9..88927bb176ef 100644 --- a/website/pages/sv/subgraphs/cookbook/near.mdx +++ b/website/pages/sv/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ Det finns tre aspekter av subgraf definition: **subgraph.yaml:** undergraf manifestet, som definierar datakällorna av intresse och hur de ska behandlas. NEAR är en ny `typ` av datakälla. -**schema.graphql:** en schema fil som definierar vilken data som lagras för din subgraf, och hur man frågar den via GraphQL. Kraven för NEAR undergrafer täcks av [den befintliga dokumentationen](/developing/creating-a-subgraph#the-graphql-schema). +**schema.graphql:** en schema fil som definierar vilken data som lagras för din subgraf, och hur man frågar den via GraphQL. Kraven för NEAR undergrafer täcks av [den befintliga dokumentationen](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**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. Under subgrafutveckling finns det två nyckelkommandon: @@ -92,13 +92,13 @@ NEAR datakällor stöder två typer av hanterare: ### Schema Definition -Schemadefinition beskriver strukturen för den resulterande subgraf databasen och relationerna mellan enheter. Detta är agnostiskt för den ursprungliga datakällan. Det finns mer information om definition av subgraf schema [här](/developing/creating-a-subgraph#the-graphql-schema). +Schemadefinition beskriver strukturen för den resulterande subgraf databasen och relationerna mellan enheter. Detta är agnostiskt för den ursprungliga datakällan. Det finns mer information om definition av subgraf schema [här](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript mappningar Hanterarna för bearbetning av händelser är skrivna i [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Dessa typer skickas till block & kvittohanterare: - Blockhanterare kommer att få ett `Block` - Kvittohanterare kommer att få ett `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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. ## Utplacera en NEAR Subgraf @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ Vi kommer snart att ge mer information om hur du kör ovanstående komponenter. ## Fråga efter en NEAR subgraf -GraphQL slutpunkten för NEAR undergrafer bestäms av schemadefinitionen, med det befintliga API gränssnittet. Besök [GraphQL API-dokumentationen](/querying/graphql-api) för mer information. +GraphQL slutpunkten för NEAR undergrafer bestäms av schemadefinitionen, med det befintliga API gränssnittet. Besök [GraphQL API-dokumentationen](/querying/graphql-api/) för mer information. ## Exempel på subgrafer diff --git a/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx index 9fb6713242bf..f823821216a7 100644 --- a/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: API för AssemblyScript --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx index 59cb02ffa61c..8166fa4088c1 100644 --- a/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI-filerna måste matcha ditt/dina kontrakt. Det finns några olika sätt att f | Version | Versionsanteckningar | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx b/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx index 5428162b401f..541bbae54e19 100644 --- a/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/sv/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/sv/subgraphs/developing/deploying/multiple-networks.mdx index f35ab9327a4c..8be847bc8fab 100644 --- a/website/pages/sv/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/sv/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Distribuera undergrafen till flera nätverk diff --git a/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx index fefe0f330649..03bd77711e98 100644 --- a/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Får inte använda någon av följande egenskaper: - ipfs.cat & ipfs.map - Icke dödliga fel diff --git a/website/pages/sv/subgraphs/developing/developer-faq.mdx b/website/pages/sv/subgraphs/developing/developer-faq.mdx index e79a1bf808e1..fef4bde9658a 100644 --- a/website/pages/sv/subgraphs/developing/developer-faq.mdx +++ b/website/pages/sv/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Inom en subgraf behandlas händelser alltid i den ordning de visas i blocken, oa Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Kolla in avsnittet "Instansiera en mall för datakälla" på: [Mallar för datakällor](/developing/creating-a-subgraph#data-source-templates). +Kolla in avsnittet "Instansiera en mall för datakälla" på: [Mallar för datakällor](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -Du kan hitta listan över de stödda nätverken [här](/developing/supported-networks). +Du kan hitta listan över de stödda nätverken [här](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 6cfad6469b35..eafaa0dd0c1e 100644 --- a/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publicera en Subgraph på Det Decentraliserade Nätverket --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Uppdatera metadata för en publicerad subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/sv/subgraphs/explorer.mdx b/website/pages/sv/subgraphs/explorer.mdx index 1d8facb1b4a8..f3d4efb0d996 100644 --- a/website/pages/sv/subgraphs/explorer.mdx +++ b/website/pages/sv/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -För att lära dig mer om hur du blir indexerare kan du titta på [officiell dokumentation](/Nätverk/indexing) eller [The Graf Academy Indexer-guiden.](https://thegraph.academy/delegators/choosing-indexers/) +För att lära dig mer om hur du blir indexerare kan du titta på [officiell dokumentation](/Nätverk/indexing/) eller [The Graf Academy Indexer-guiden.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexeringsdetaljerpanel](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Utforskaren Bild 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegater @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Totalt belopp av GRT som de för närvarande har i protokollet - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Nätverk diff --git a/website/pages/sv/subgraphs/querying/best-practices.mdx b/website/pages/sv/subgraphs/querying/best-practices.mdx index 4f836b50ab52..8b952e9bcd9d 100644 --- a/website/pages/sv/subgraphs/querying/best-practices.mdx +++ b/website/pages/sv/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Varje `queryName` får endast användas en gång per operation. - Varje `field` får bara användas en gång i ett urval (vi kan inte fråga `id` två gånger under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Varje variabel som tilldelas ett argument måste matcha dess typ. - I en given lista med variabler måste var och en av dem vara unik. - Alla definierade variabler måste användas. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Hantering av subgrafer över olika blockkedjor: Frågehantering från flera subgrafer i en enda fråga - [Automatisk blockspårning](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/sv/subgraphs/querying/graphql-api.mdx b/website/pages/sv/subgraphs/querying/graphql-api.mdx index 06f0568d0e53..3ad4105a1ef2 100644 --- a/website/pages/sv/subgraphs/querying/graphql-api.mdx +++ b/website/pages/sv/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ Denna förfrågan kommer att returnera `Challenge`-entiteter och deras associera ### Fulltextsökförfrågningar -Fält för fulltextsökning ger en uttrycksfull textsöknings-API som kan läggas till i undergrafens schema och anpassas. Hänvisa till [Definiera fält för fulltextsökning](/utveckling/skapa-en-undergraf#definiera-fält-för-fulltextsökning) för att lägga till fulltextsökning i din undergraf. +Fält för fulltextsökning ger en uttrycksfull textsöknings-API som kan läggas till i undergrafens schema och anpassas. Hänvisa till [Definiera fält för fulltextsökning](/utveckling/skapa-en-undergraf/#definiera-fält-för-fulltextsökning) för att lägga till fulltextsökning i din undergraf. Fulltextsökförfrågningar har ett obligatoriskt fält, `text`, för att tillhandahålla söktermer. Flera specialiserade fulltextoperatorer finns tillgängliga att användas i detta `text`-sökfält. diff --git a/website/pages/sv/subgraphs/querying/introduction.mdx b/website/pages/sv/subgraphs/querying/introduction.mdx index d46760aa79a2..be6b16862f2a 100644 --- a/website/pages/sv/subgraphs/querying/introduction.mdx +++ b/website/pages/sv/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Fråga The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/sv/substreams/sps/introduction.mdx b/website/pages/sv/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/sv/substreams/sps/introduction.mdx +++ b/website/pages/sv/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/sv/substreams/sps/triggers.mdx b/website/pages/sv/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/sv/substreams/sps/triggers.mdx +++ b/website/pages/sv/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/sv/supported-networks.mdx b/website/pages/sv/supported-networks.mdx index c8bf3ab7a332..d3113d4759cf 100644 --- a/website/pages/sv/supported-networks.mdx +++ b/website/pages/sv/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx index 5ba89020402c..e516573fd4d9 100644 --- a/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/sw/archived/sunrise.mdx b/website/pages/sw/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/sw/archived/sunrise.mdx +++ b/website/pages/sw/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/sw/contracts.mdx b/website/pages/sw/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/sw/contracts.mdx +++ b/website/pages/sw/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/sw/indexing/new-chain-integration.mdx b/website/pages/sw/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/sw/indexing/new-chain-integration.mdx +++ b/website/pages/sw/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/sw/indexing/overview.mdx b/website/pages/sw/indexing/overview.mdx index a6844c2da009..c05c37a275ef 100644 --- a/website/pages/sw/indexing/overview.mdx +++ b/website/pages/sw/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens diff --git a/website/pages/sw/resources/benefits.mdx b/website/pages/sw/resources/benefits.mdx index 13f1025e91f0..a0f0f5a0b3ed 100644 --- a/website/pages/sw/resources/benefits.mdx +++ b/website/pages/sw/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/sw/resources/roles/curating.mdx b/website/pages/sw/resources/roles/curating.mdx index f584117580ae..ecb879ae6fbe 100644 --- a/website/pages/sw/resources/roles/curating.mdx +++ b/website/pages/sw/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/sw/subgraphs/cookbook/grafting.mdx b/website/pages/sw/subgraphs/cookbook/grafting.mdx index 6c3b85419af9..7aa79c7e2755 100644 --- a/website/pages/sw/subgraphs/cookbook/grafting.mdx +++ b/website/pages/sw/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/sw/subgraphs/cookbook/near.mdx b/website/pages/sw/subgraphs/cookbook/near.mdx index 8e0be3f5ce4e..cc0bf8637bee 100644 --- a/website/pages/sw/subgraphs/cookbook/near.mdx +++ b/website/pages/sw/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx index 6a0c4e208b99..8aa0bf0027bf 100644 --- a/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx index 86686025b089..282c68973a8a 100644 --- a/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx b/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/sw/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/sw/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/sw/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/sw/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx index cb3badff5d1b..4644cd466aa9 100644 --- a/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/sw/subgraphs/developing/developer-faq.mdx b/website/pages/sw/subgraphs/developing/developer-faq.mdx index 244aae52d0f4..85dccad933b0 100644 --- a/website/pages/sw/subgraphs/developing/developer-faq.mdx +++ b/website/pages/sw/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 9de36745a95b..4728db3eb245 100644 --- a/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/sw/subgraphs/explorer.mdx b/website/pages/sw/subgraphs/explorer.mdx index 02dca6ed2f9f..d874f80f5140 100644 --- a/website/pages/sw/subgraphs/explorer.mdx +++ b/website/pages/sw/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/sw/subgraphs/querying/best-practices.mdx b/website/pages/sw/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/sw/subgraphs/querying/best-practices.mdx +++ b/website/pages/sw/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/sw/subgraphs/querying/graphql-api.mdx b/website/pages/sw/subgraphs/querying/graphql-api.mdx index 3dd70fc7b004..917fad3f2406 100644 --- a/website/pages/sw/subgraphs/querying/graphql-api.mdx +++ b/website/pages/sw/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/sw/subgraphs/querying/introduction.mdx b/website/pages/sw/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/sw/subgraphs/querying/introduction.mdx +++ b/website/pages/sw/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/sw/substreams/sps/introduction.mdx b/website/pages/sw/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/sw/substreams/sps/introduction.mdx +++ b/website/pages/sw/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/sw/substreams/sps/triggers.mdx b/website/pages/sw/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/sw/substreams/sps/triggers.mdx +++ b/website/pages/sw/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/sw/supported-networks.mdx b/website/pages/sw/supported-networks.mdx index 797202065e99..9e47f25c86e6 100644 --- a/website/pages/sw/supported-networks.mdx +++ b/website/pages/sw/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx index c2df6e4ed5cb..a5819dd5cc67 100644 --- a/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Katman2 Transfer Araçları Rehberi Graph, Arbitrum One üzerinde Katman2'ye geçişi kolaylaştırmıştır. Her protokol katılımcısı için, tüm ağ katılımcıları adına Katman2'ye transferi sorunsuz hale getirmek için bir dizi Katman2 Transfer Aracı vardır. Bu araçlar, ne transfer ettiğinize bağlı olarak belirli bir dizi adımı izlemenizi gerektirecektir. -Bu araçlarla ilgili sıkça sorulan bazı sorular [Katman2 Transfer Araçları SSS](/arbitrum/l2-transfer-tools-faq) bölümünde yanıtlanmaktadır. SSS, araçların nasıl kullanılacağı, nasıl çalıştıkları ve kullanırken akılda tutulması gerekenler hakkında derinlemesine açıklamalar içermektedir. +Bu araçlarla ilgili sıkça sorulan bazı sorular [Katman2 Transfer Araçları SSS](/arbitrum/l2-transfer-tools-faq/) bölümünde yanıtlanmaktadır. SSS, araçların nasıl kullanılacağı, nasıl çalıştıkları ve kullanırken akılda tutulması gerekenler hakkında derinlemesine açıklamalar içermektedir. ## Subgraph'ınızı Arbitrum'a nasıl transfer edebilirsiniz (Katman2) diff --git a/website/pages/tr/archived/sunrise.mdx b/website/pages/tr/archived/sunrise.mdx index e40c0b6f7914..4a3602426321 100644 --- a/website/pages/tr/archived/sunrise.mdx +++ b/website/pages/tr/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/tr/contracts.mdx b/website/pages/tr/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/tr/contracts.mdx +++ b/website/pages/tr/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/tr/indexing/new-chain-integration.mdx b/website/pages/tr/indexing/new-chain-integration.mdx index f9553b1ba605..bd672058e941 100644 --- a/website/pages/tr/indexing/new-chain-integration.mdx +++ b/website/pages/tr/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Herhangi bir hata olmadığı takdirde Graph Düğü'mü dağıtılan subgraph' ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/tr/indexing/overview.mdx b/website/pages/tr/indexing/overview.mdx index 27984b79fe2a..92fb83529393 100644 --- a/website/pages/tr/indexing/overview.mdx +++ b/website/pages/tr/indexing/overview.mdx @@ -87,7 +87,7 @@ Bir tahsisat kapatıldıktan sonra iadeler İndeksleyici tarafından talep edile ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - İndeksleyiciye dağıtılacak sorgu ücreti iadelerinin %'si. Bu %95 olarak ayarlanırsa, İndeksleyici bir tahsisat kapatıldığında kazanılan sorgu ücretlerinin %95'ini alır ve diğer %5'lik kısım Delegatörlere gider. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### Bir İndeksleyicinin alması gereken bazı temel güvenlik önlemleri nelerdir? -- **Operatör cüzdanı** - Bir operatör cüzdanı oluşturmak önemli bir önlemdir, çünkü bir İndeksleyicinin stake'i kontrol eden anahtarları ile günlük işlemleri kontrol eden anahtarları arasında ayrım yapmasına olanak tanır. Talimatlar için [Protokolde Stake](/network/indexing#stake-in-the-protocol) bölümüne bakın. +- **Operatör cüzdanı** - Bir operatör cüzdanı oluşturmak önemli bir önlemdir, çünkü bir İndeksleyicinin stake'i kontrol eden anahtarları ile günlük işlemleri kontrol eden anahtarları arasında ayrım yapmasına olanak tanır. Talimatlar için [Protokolde Stake](/network/indexing/#stake-in-the-protocol) bölümüne bakın. - **Firewall** - Yalnızca İndeksleyici hizmetinin herkese açık olması gerekir ve yönetici bağlantı noktalarının ve veritabanı erişiminin kilitlenmesine özellikle dikkat edilmelidir: Graph Node JSON-RPC uç noktası (varsayılan bağlantı noktası: 8030), İndeksleyici yönetim API uç noktası (varsayılan bağlantı noktası: 18000) ve Postgres veritabanı uç noktası (varsayılan bağlantı noktası: 5432) herkese açık olmamalıdır. @@ -375,7 +375,7 @@ Ağa başarılı bir şekilde katılmak hemen hemen sürekli izleme ve etkileşi #### Buradan başlayın -İndeksleyici aracısı ve İndeksleyici hizmeti, Graph Düğümü altyapınızla birlikte konumlandırılmalıdır. İndeksleyici bileşenleriniz için sanal yürütme ortamları kurmanın birçok yolu vardır; burada bunları NPM paketleri veya kaynak kullanarak baremetal üzerinde veya Google Cloud Kubernetes Motoru üzerinde kubernetes ve docker aracılığıyla nasıl çalıştıracağınızı açıklayacağız. Bu kurulum örnekleri altyapınıza iyi bir şekilde uyarlanamazsa, muhtemelen başvurabileceğiniz bir topluluk rehberi olacaktır, gelin [Discord](https://discord.gg/graphprotocol)'da merhaba deyin! İndeksleyici bileşenlerinizi başlatmadan önce [protokolde stake etmeyi](/network/indexing#stake-in-the-protocol) unutmayın! +İndeksleyici aracısı ve İndeksleyici hizmeti, Graph Düğümü altyapınızla birlikte konumlandırılmalıdır. İndeksleyici bileşenleriniz için sanal yürütme ortamları kurmanın birçok yolu vardır; burada bunları NPM paketleri veya kaynak kullanarak baremetal üzerinde veya Google Cloud Kubernetes Motoru üzerinde kubernetes ve docker aracılığıyla nasıl çalıştıracağınızı açıklayacağız. Bu kurulum örnekleri altyapınıza iyi bir şekilde uyarlanamazsa, muhtemelen başvurabileceğiniz bir topluluk rehberi olacaktır, gelin [Discord](https://discord.gg/graphprotocol)'da merhaba deyin! İndeksleyici bileşenlerinizi başlatmadan önce [protokolde stake etmeyi](/network/indexing/#stake-in-the-protocol) unutmayın! #### NPM paketlerinden @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s ve Terraform kullanma -[Google Cloud'da Terraform Kullanarak Sunucu Altyapısı Kurma](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) bölümüne bakın +[Google Cloud'da Terraform Kullanarak Sunucu Altyapısı Kurma](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) bölümüne bakın #### Kullanım @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Bir İndeksleyici protokolde GRT'yi stake ettikten sonra, [İndeksleyici kompenetleri ](/network/indexing#indexer-components) başlatılabilir ve ağ ile etkileşimlerine başlayabilir. +Bir İndeksleyici protokolde GRT'yi stake ettikten sonra, [İndeksleyici kompenetleri ](/network/indexing/#indexer-components) başlatılabilir ve ağ ile etkileşimlerine başlayabilir. #### Tokenleri onaylama diff --git a/website/pages/tr/resources/benefits.mdx b/website/pages/tr/resources/benefits.mdx index 67a3db14273b..33a59e1835d7 100644 --- a/website/pages/tr/resources/benefits.mdx +++ b/website/pages/tr/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/tr/resources/roles/curating.mdx b/website/pages/tr/resources/roles/curating.mdx index 17c05c0de615..6553a623c4e6 100644 --- a/website/pages/tr/resources/roles/curating.mdx +++ b/website/pages/tr/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/tr/subgraphs/cookbook/grafting.mdx b/website/pages/tr/subgraphs/cookbook/grafting.mdx index 2857ded9d636..1eec32b7270c 100644 --- a/website/pages/tr/subgraphs/cookbook/grafting.mdx +++ b/website/pages/tr/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ Graftlanan subgraph, temel subgraphla tamamen aynı olmayan, ancak onunla uyumlu Daha fazla bilgi için kontrol edebilirsiniz: -- [Graftlama](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Graftlama](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/tr/subgraphs/cookbook/near.mdx b/website/pages/tr/subgraphs/cookbook/near.mdx index 099acc649897..708782a54425 100644 --- a/website/pages/tr/subgraphs/cookbook/near.mdx +++ b/website/pages/tr/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ Subgraph tanımının üç yönü vardır: **subgraph.yaml:** Veri kaynaklarını ve bunların nasıl işleneceğini tanımlayan subgraph manifestidir. NEAR, yeni bir veri kaynağı türüdür(`kind`). -**schema.graphql:** Subgraph'ınız için hangi verilerin depolandığını ve bunlara GraphQL aracılığıyla nasıl sorgu yapılacağını tanımlayan bir şema dosyası. NEAR subgraph gereksinimleri [mevcut belgelendirmede](/developing/creating-a-subgraph#the-graphql-schema) ele alınmıştır. +**schema.graphql:** Subgraph'ınız için hangi verilerin depolandığını ve bunlara GraphQL aracılığıyla nasıl sorgu yapılacağını tanımlayan bir şema dosyası. NEAR subgraph gereksinimleri [mevcut belgelendirmede](/developing/creating-a-subgraph/#the-graphql-schema) ele alınmıştır. -**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. +**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. Subgraph geliştirme sırasında iki temel komut bulunmaktadır: @@ -92,13 +92,13 @@ NEAR veri kaynakları iki tür işleyiciyi destekler: ### Şema Tanımı -Şema tanımı, ortaya çıkan subgraph veritabanının yapısını ve varlıklar arasındaki ilişkileri tanımlar. Bu, orijinal veri kaynağından bağımsızdır. Subgraph şema tanımı hakkında daha fazla ayrıntı [burada](/developing/creating-a-subgraph#the-graphql-schema) bulunmaktadır. +Şema tanımı, ortaya çıkan subgraph veritabanının yapısını ve varlıklar arasındaki ilişkileri tanımlar. Bu, orijinal veri kaynağından bağımsızdır. Subgraph şema tanımı hakkında daha fazla ayrıntı [burada](/developing/creating-a-subgraph/#the-graphql-schema) bulunmaktadır. ### AssemblyScript Eşleştirmeleri Olayları işlemek için işleyiciler [AssemblyScript](https://www.assemblyscript.org/) içinde yazılmıştır. -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Bu türler blok & makbuz işleyicilerine aktarılır: - Blok işleyicileri bir `Block` alır - Makbuz işleyicileri bir `ReceiptWithOutcome` alır -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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'ını Dağıtma @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ Yukarıdaki bileşenlerin çalıştırılması hakkında yakında daha fazla bil ## NEAR Subgraph'ını Sorgulama -NEAR subgraphları için GraphQL uç noktası, mevcut API arayüzü ile şema tanımı tarafından belirlenir. Daha fazla bilgi için lütfen [GraphQL API dökümantasyonunu](/querying/graphql-api) ziyaret edin. +NEAR subgraphları için GraphQL uç noktası, mevcut API arayüzü ile şema tanımı tarafından belirlenir. Daha fazla bilgi için lütfen [GraphQL API dökümantasyonunu](/querying/graphql-api/) ziyaret edin. ## Örnek Subgraph'ler diff --git a/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx index 9ea83c6096c9..8e20476ad888 100644 --- a/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API'si --- -> Not: Eğer `graph-cli`/`graph-ts` sürüm `0.22.0`'den önce bir subgraph oluşturduysanız, eski bir AssemblyScript sürümünü kullanıyorsunuz demektir. [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide) gözden geçirmeniz önerilir. +> Not: Eğer `graph-cli`/`graph-ts` sürüm `0.22.0`'den önce bir subgraph oluşturduysanız, eski bir AssemblyScript sürümünü kullanıyorsunuz demektir. [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide/) gözden geçirmeniz önerilir. Subgraph eşlemeleri yazarken kullanılabilecek yerleşik API'leri öğrenin. Hazır olarak sunulan iki tür API mevcuttur: @@ -35,7 +35,7 @@ Subgraph manifestosundaki `apiVersion`, bir subgraph için Graph Düğümü tara | 0.0.8 | Bir varlığı kaydederken şemadaki alanların varlığını doğrulama mekanizması ekler. | | 0.0.7 | Ethereum türlerine `TransactionReceipt` ve `Log` sınıfları eklendi
Ethereum Event nesnesine `receipt` alanı eklendi | | 0.0.6 | Ethereum Transaction nesnesine `nonce` alanı eklendi
Ethereum Block nesnesine `baseFeePerGas` eklendi | -| 0.0.5 | AssemblyScript sürümü 0.19.10'a yükseltildi (bu sürümle birlikte uyumluluğu bozabilecek değişiklikler yapılmıştır, lütfen [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide) bölümüne bakın)
`ethereum.transaction.gasUsed`, `ethereum.transaction.gasLimit` olarak yeniden adlandırıldı | +| 0.0.5 | AssemblyScript sürümü 0.19.10'a yükseltildi (bu sürümle birlikte uyumluluğu bozabilecek değişiklikler yapılmıştır, lütfen [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide/) bölümüne bakın)
`ethereum.transaction.gasUsed`, `ethereum.transaction.gasLimit` olarak yeniden adlandırıldı | | 0.0.4 | Ethereum SmartContractCall nesnesine `functionSignature` alanı eklendi | | 0.0.3 | Ethereum Call nesnesine `from` alanı eklendi
`etherem.call.address`, `ethereum.call.to` olarak yeniden adlandırıldı | | 0.0.2 | Ethereum Transaction nesnesine `input` alanı eklendi | diff --git a/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx index 31c275b45dbf..6b0ed88435dc 100644 --- a/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI dosya(lar)ı sözleşme(ler) inizle uygun olmalıdır. ABI dosyalarını edi | Sürüm | Sürüm Notları | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx b/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx index c11d86e38b0e..d82c78526adf 100644 --- a/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/tr/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/tr/subgraphs/developing/deploying/multiple-networks.mdx index 0394197d25f9..34ef341eed20 100644 --- a/website/pages/tr/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/tr/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Bir Subgraph'i Birden Fazla Ağda Dağıtma --- -Bu sayfa, bir subgraph'i birden fazla ağda nasıl dağıtacağınızı açıklar. Bir subgraph'i dağıtmak için öncelikle [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)'yi yüklemeniz gerekir. Henüz bir subgraph oluşturmadıysanız, [Subgraph Oluşturma](/developing/creating-a-subgraph) bölümüne bakın. +Bu sayfa, bir subgraph'i birden fazla ağda nasıl dağıtacağınızı açıklar. Bir subgraph'i dağıtmak için öncelikle [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)'yi yüklemeniz gerekir. Henüz bir subgraph oluşturmadıysanız, [Subgraph Oluşturma](/developing/creating-a-subgraph/) bölümüne bakın. ## Subgraph'i Birden Fazla Ağda Dağıtma diff --git a/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx index eaca0a81f65f..3f4745572daa 100644 --- a/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli Subgraph'lerin Graph Ağı Endeksleyicileri tarafından desteklenebilmesi için şu gereklilikleri karşılaması gerekir: -- [Desteklenen bir ağı](/developing/supported-networks) endeksliyor olmalı +- [Desteklenen bir ağı](/developing/supported-networks/) endeksliyor olmalı - Aşağıdaki özelliklerden hiçbirini kullanmamalı: - ipfs.cat & ipfs.map - Kritik olmayan hatalar diff --git a/website/pages/tr/subgraphs/developing/developer-faq.mdx b/website/pages/tr/subgraphs/developing/developer-faq.mdx index c21248d34942..a288248db0f0 100644 --- a/website/pages/tr/subgraphs/developing/developer-faq.mdx +++ b/website/pages/tr/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Bir subgraph içindeki olaylar, birden fazla sözleşme üzerinde olup olmamaya Şablonlar, subgraph’iniz endeksleme yaparken veri kaynaklarını hızlıca oluşturmanızı sağlar. Sözleşmeniz, kullanıcılar etkileşime girdikçe yeni sözleşmeler yaratabilir. Bu sözleşmelerin yapısını (ABI, olaylar vb.) önceden bildiğinizden, onları nasıl endekslemek istediğinizi bir şablonda tanımlayabilirsiniz. Yeni sözleşmeler oluşturulduğunda, subgraph’iniz sözleşme adresini tespit ederek dinamik bir veri kaynağı oluşturacaktır. -"Bir Veri Kaynağı Şablonunu Başlatma" bölümüne göz atın: [Veri Kaynağı Şablonları](/developing/creating-a-subgraph#data-source-templates). +"Bir Veri Kaynağı Şablonunu Başlatma" bölümüne göz atın: [Veri Kaynağı Şablonları](/developing/creating-a-subgraph/#data-source-templates). ### 11. `graph init` komutunu `graph-cli` ile kullanarak iki sözleşme içeren bir subgraph kurmak mümkün müdür? Yoksa `graph init` komutunu çalıştırdıktan sonra `subgraph.yaml` dosyasına elle bir başka dataSource eklemem mi gerekir? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. The Graph hangi ağları desteklemektedir? -Desteklenen ağların listesini [burada](/developing/supported-networks) bulabilirsiniz. +Desteklenen ağların listesini [burada](/developing/supported-networks/) bulabilirsiniz. ### 17. Olay işleyicileri içerisinde ağlar (mainnet, Sepolia, yerel) arasında ayrım yapmak mümkün müdür? @@ -107,11 +107,11 @@ Evet. Sepolia, blok işleyicileri, çağrı işleyicileri ve olay işleyicilerin ### 19. Endekslemeye hangi bloktan başlanacağını belirtmek mümkün müdür? -Evet. `subgraph.yaml` dosyasındaki `dataSources.source.startBlock`, veri kaynağının endekslemeye başladığı blok numarasını belirtir. Çoğu durumda, sözleşmenin oluşturulduğu bloğun kullanılmasını öneriyoruz. Daha fazla bilgi için: [Başlangıç blokları](/developing/creating-a-subgraph#start-blocks) +Evet. `subgraph.yaml` dosyasındaki `dataSources.source.startBlock`, veri kaynağının endekslemeye başladığı blok numarasını belirtir. Çoğu durumda, sözleşmenin oluşturulduğu bloğun kullanılmasını öneriyoruz. Daha fazla bilgi için: [Başlangıç blokları](/developing/creating-a-subgraph/#start-blocks) ### 20. Endeksleme performansını artırmak için ipuçları var mı? Subgraph'imin senkronize edilmesi çok uzun zaman alıyor -Sözleşmenin dağıtıldığı bloktan itibaren endeksleme yapmak için opsiyonel başlangıç bloğu özelliğine göz atabilirsiniz: [Başlangıç blokları](/developing/creating-a-subgraph#start-blocks) +Sözleşmenin dağıtıldığı bloktan itibaren endeksleme yapmak için opsiyonel başlangıç bloğu özelliğine göz atabilirsiniz: [Başlangıç blokları](/developing/creating-a-subgraph/#start-blocks) ### 21. Subgraph üzerinde doğrudan sorgulama yaparak endekslenmiş en son blok numarasını öğrenmenin bir yolu var mı? diff --git a/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 04e3e499ee22..49fc7ba34e3f 100644 --- a/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Yayınlanan bir subgraph için üst veri güncelleme @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/tr/subgraphs/explorer.mdx b/website/pages/tr/subgraphs/explorer.mdx index cb6d3012f0a6..31878c3af587 100644 --- a/website/pages/tr/subgraphs/explorer.mdx +++ b/website/pages/tr/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Nasıl İndeksleyici olunacağı hakkında daha fazla bilgi edinmek için [resmi dökümantasyona](/network/indexing) veya [Graph Akademi İndeksleyici kılavuzlarına](https://thegraph.academy/delegators/choosing-indexers/) göz atabilirsiniz. +Nasıl İndeksleyici olunacağı hakkında daha fazla bilgi edinmek için [resmi dökümantasyona](/network/indexing/) veya [Graph Akademi İndeksleyici kılavuzlarına](https://thegraph.academy/delegators/choosing-indexers/) göz atabilirsiniz. ![İndeksleme ayrıntıları bölmesi](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Gezgin Gürüntüsü 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegatörler @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Şu anda protokolde bulunan sahip oldukları toplam GRT miktarı - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Ağ diff --git a/website/pages/tr/subgraphs/querying/best-practices.mdx b/website/pages/tr/subgraphs/querying/best-practices.mdx index f5cc0521e5b3..40012c842cad 100644 --- a/website/pages/tr/subgraphs/querying/best-practices.mdx +++ b/website/pages/tr/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/tr/subgraphs/querying/graphql-api.mdx b/website/pages/tr/subgraphs/querying/graphql-api.mdx index c43734c04dd1..adb3764b11fc 100644 --- a/website/pages/tr/subgraphs/querying/graphql-api.mdx +++ b/website/pages/tr/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ Bu sorgu, verilen hash ile bloğun işlenmesinden hemen sonra var olan şekliyle ### Tam Metin Arama Sorguları -Tam metin arama sorgu alanları, subgraph şemasına eklenebilen ve özelleştirilebilen etkileyici bir metin arama API'si sağlar. Subgraph'ınıza tam metin araması eklemek için [Tam Metin Arama Alanlarını Tanımlama](/developing/creating-a-subgraph#defining-fulltext-search-fields) bölümüne göz atın. +Tam metin arama sorgu alanları, subgraph şemasına eklenebilen ve özelleştirilebilen etkileyici bir metin arama API'si sağlar. Subgraph'ınıza tam metin araması eklemek için [Tam Metin Arama Alanlarını Tanımlama](/developing/creating-a-subgraph/#defining-fulltext-search-fields) bölümüne göz atın. Tam metin arama sorgularının kullanması gereken bir zorunlu alanı vardır, bu alan `text` adını taşır ve arama terimlerini sağlamak için kullanılır. Bu `text` arama alanında kullanılmak üzere birkaç özel tam metin operatörü mevcuttur. diff --git a/website/pages/tr/subgraphs/querying/introduction.mdx b/website/pages/tr/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/tr/subgraphs/querying/introduction.mdx +++ b/website/pages/tr/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/tr/substreams/sps/introduction.mdx b/website/pages/tr/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/tr/substreams/sps/introduction.mdx +++ b/website/pages/tr/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/tr/substreams/sps/triggers.mdx b/website/pages/tr/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/tr/substreams/sps/triggers.mdx +++ b/website/pages/tr/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/tr/supported-networks.mdx b/website/pages/tr/supported-networks.mdx index 964822fcca6d..e9cc0167e1b9 100644 --- a/website/pages/tr/supported-networks.mdx +++ b/website/pages/tr/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Temel ağ desteği, [yükseltme Endeksleyicisi](https://thegraph.com/blog/upgrade-indexer/) tarafından sağlanmaktadır. -\*\* Graph Düğümü ile Entegrasyon: `evm`, `near`, `cosmos`, `osmosis` ve `ar`, Graph Düğümü'nde yerel işleyici (handler) ve tür (type) desteğine sahiptir. Firehose ve Substreams uyumlu zincirler, genelleştirilmiş [Substreams destekli subgraph](/cookbook/substreams-powered-subgraphs) entegrasyonundan yararlanabilir (`evm` ve `near` ağları buna dahil). ⁠† [Substreams destekli subgraph’lerin](/cookbook/substreams-powered-subgraphs) dağıtımını destekler. +\*\* Graph Düğümü ile Entegrasyon: `evm`, `near`, `cosmos`, `osmosis` ve `ar`, Graph Düğümü'nde yerel işleyici (handler) ve tür (type) desteğine sahiptir. Firehose ve Substreams uyumlu zincirler, genelleştirilmiş [Substreams destekli subgraph](/cookbook/substreams-powered-subgraphs/) entegrasyonundan yararlanabilir (`evm` ve `near` ağları buna dahil). ⁠† [Substreams destekli subgraph’lerin](/cookbook/substreams-powered-subgraphs/) dağıtımını destekler. - Subgraph Studio, örneğin JSON-RPC, Firehose ve Substreams uç noktaları gibi temel teknolojilerin istikrarlılığına ve güvenilirliğine bel bağlar. - Gnosis Chain’i endeksleyen subgraph'ler artık `gnosis` ağ tanımlayıcısı ile dağıtılabilir. diff --git a/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx index 5ba89020402c..e516573fd4d9 100644 --- a/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/uk/archived/sunrise.mdx b/website/pages/uk/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/uk/archived/sunrise.mdx +++ b/website/pages/uk/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/uk/contracts.mdx b/website/pages/uk/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/uk/contracts.mdx +++ b/website/pages/uk/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/uk/indexing/new-chain-integration.mdx b/website/pages/uk/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/uk/indexing/new-chain-integration.mdx +++ b/website/pages/uk/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/uk/indexing/overview.mdx b/website/pages/uk/indexing/overview.mdx index d9f39f72fe02..d4893efed202 100644 --- a/website/pages/uk/indexing/overview.mdx +++ b/website/pages/uk/indexing/overview.mdx @@ -87,7 +87,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### Що таке query fee cut і indexing reward cut? -Значення `queryFeeCut` і `indexingRewardCut` є параметрами делегування, які Індексатор може встановлювати разом із cooldownBlocks, щоб контролювати розподіл GRT між Індексатором і його Делегатами. Перегляньте останні кроки в розділі [Staking in the Protocol](/network/indexing#stake-in-the-protocol), щоб отримати інструкції щодо встановлення параметрів делегування. +Значення `queryFeeCut` і `indexingRewardCut` є параметрами делегування, які Індексатор може встановлювати разом із cooldownBlocks, щоб контролювати розподіл GRT між Індексатором і його Делегатами. Перегляньте останні кроки в розділі [Staking in the Protocol](/network/indexing/#stake-in-the-protocol), щоб отримати інструкції щодо встановлення параметрів делегування. - **queryFeeCut** - відсоток від комісій за опрацювання запитів, який буде розподілено між Індексатором та Делегатами. Якщо цей параметр встановлено на рівні в 95%, індексатор отримає 95% від комісій за запити, зароблених при закритті розподілу, а решта 5% підуть Делегатам. @@ -121,7 +121,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### Яких основних заходів безпеки повинен дотримуватися індексатор? -- **Operator wallet**. Налаштування гаманця оператора є важливим запобіжним заходом, оскільки він дозволяє Індексатору підтримувати відокремлення між своїми ключами, які контролюють застейкані токени, і тими, які використовуються для щоденних операцій. Інструкції див. у розділі [Stake in Protocol](/network/indexing#stake-in-the-protocol). +- **Operator wallet**. Налаштування гаманця оператора є важливим запобіжним заходом, оскільки він дозволяє Індексатору підтримувати відокремлення між своїми ключами, які контролюють застейкані токени, і тими, які використовуються для щоденних операцій. Інструкції див. у розділі [Stake in Protocol](/network/indexing/#stake-in-the-protocol). - **Firewall** - Публічно доступною має бути лише сервіс-індексатор, і особливу увагу слід приділити блокуванню портів адміністратора і доступу до бази даних: не слід відкривати кінцеву точку JSON-RPC Graph Node (порт за замовчуванням: 8030), кінцеву точку API управління індексатором (порт за замовчуванням: 18000) і кінцеву точку бази даних Postgres (порт за замовчуванням: 5432). @@ -375,7 +375,7 @@ docker-compose up #### Початок роботи -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### З NPM-пакетів @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Використання K8 та Terraform -Див. розділ [Налаштування серверної інфраструктури з використанням Terraform на Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) +Див. розділ [Налаштування серверної інфраструктури з використанням Terraform на Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Використання @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Після того, як індексатор застейкав GRT токени у протоколі, [Indexer components](/network/indexing#indexer-components) можна запустити та почати взаємодію з мережею. +Після того, як індексатор застейкав GRT токени у протоколі, [Indexer components](/network/indexing/#indexer-components) можна запустити та почати взаємодію з мережею. #### Approve токенів diff --git a/website/pages/uk/resources/benefits.mdx b/website/pages/uk/resources/benefits.mdx index 32703068bd79..be12847adfb5 100644 --- a/website/pages/uk/resources/benefits.mdx +++ b/website/pages/uk/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Кураторство сигналу на підграфі є опціональною одноразовою послугою з нульовою вартістю (наприклад, сигнал на суму 1 тис. доларів можна розмістити на підграфі, а потім вивести — з можливістю отримання прибутку в цьому процесі). diff --git a/website/pages/uk/resources/roles/curating.mdx b/website/pages/uk/resources/roles/curating.mdx index 513644bac22c..45ed82d0e24d 100644 --- a/website/pages/uk/resources/roles/curating.mdx +++ b/website/pages/uk/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Як сигналізувати -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) Куратор може обрати подання сигналу на певну версію підграфа, або ж він може обрати автоматичне перенесення сигналу на найновішу версію цього підграфа. Обидва варіанти є прийнятними та мають свої плюси та мінуси. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Ринок запитів за своєю суттю молодий в Graph, і існує ризик того, що ваш %APY може бути нижчим, ніж ви очікуєте, через динаміку ринку, що зароджується. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Підграф може не працювати через різноманітні помилки (баги). Підграф, що не працює не стягує комісію за запити. В результаті вам доведеться почекати, поки розробник виправить усі помилки й випустить нову версію. - Якщо ви підключені до найновішої версії підграфу, ваші частки будуть автоматично перенесені до цієї нової версії. При цьому буде стягуватися податок на в розмірі 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/uk/subgraphs/cookbook/grafting.mdx b/website/pages/uk/subgraphs/cookbook/grafting.mdx index 4e8339df3ee3..9b45598f3810 100644 --- a/website/pages/uk/subgraphs/cookbook/grafting.mdx +++ b/website/pages/uk/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ title: Замініть контракт та збережіть його іст Для отримання додаткової інформації ви можете ознайомитися: -- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Grafting](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/uk/subgraphs/cookbook/near.mdx b/website/pages/uk/subgraphs/cookbook/near.mdx index 44d653485491..1432a082c347 100644 --- a/website/pages/uk/subgraphs/cookbook/near.mdx +++ b/website/pages/uk/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Визначення схеми -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings Обробники для виконання подій написані на мові [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Приклади підграфів diff --git a/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx index 6a0c4e208b99..8aa0bf0027bf 100644 --- a/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx index 0f6c7b45a843..0100b66c4427 100644 --- a/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | Version | Release notes | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx b/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx index 90036d1bfab9..b5b23098f5d1 100644 --- a/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/uk/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/uk/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/uk/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/uk/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx index 8e97e86976fd..f7f27fb18f62 100644 --- a/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/uk/subgraphs/developing/developer-faq.mdx b/website/pages/uk/subgraphs/developing/developer-faq.mdx index 68f141868759..2f4f017871ef 100644 --- a/website/pages/uk/subgraphs/developing/developer-faq.mdx +++ b/website/pages/uk/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Within a subgraph, the events are always processed in the order they appear in t Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx index c137db35754a..594bdd5736bb 100644 --- a/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/uk/subgraphs/explorer.mdx b/website/pages/uk/subgraphs/explorer.mdx index 1246158a97f3..665d497192f3 100644 --- a/website/pages/uk/subgraphs/explorer.mdx +++ b/website/pages/uk/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/uk/subgraphs/querying/best-practices.mdx b/website/pages/uk/subgraphs/querying/best-practices.mdx index ed5a0e2b4af4..0a430c082847 100644 --- a/website/pages/uk/subgraphs/querying/best-practices.mdx +++ b/website/pages/uk/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Кожне `queryName` може бути використане лише один раз за одну операцію. - Кожне `field` може бути використане лише один раз за вибірку (ми не можемо запитувати `id` двічі `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Будь-яка змінна, що присвоюється параметру, повинна відповідати його типу. - У заданому списку змінних кожна з них має бути унікальною. - Всі задані змінні повинні бути використаними. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Робота з кросс-чейн підграфами: Отримання інформації з декількох підграфів за один запит - [Автоматичне відстежування блоків](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/uk/subgraphs/querying/graphql-api.mdx b/website/pages/uk/subgraphs/querying/graphql-api.mdx index 3dd70fc7b004..917fad3f2406 100644 --- a/website/pages/uk/subgraphs/querying/graphql-api.mdx +++ b/website/pages/uk/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/uk/subgraphs/querying/introduction.mdx b/website/pages/uk/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/uk/subgraphs/querying/introduction.mdx +++ b/website/pages/uk/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/uk/substreams/sps/introduction.mdx b/website/pages/uk/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/uk/substreams/sps/introduction.mdx +++ b/website/pages/uk/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/uk/substreams/sps/triggers.mdx b/website/pages/uk/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/uk/substreams/sps/triggers.mdx +++ b/website/pages/uk/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/uk/supported-networks.mdx b/website/pages/uk/supported-networks.mdx index 6a1805deefee..c9e32bb4465b 100644 --- a/website/pages/uk/supported-networks.mdx +++ b/website/pages/uk/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx index 2e50ae4d1a13..651daeaa1c30 100644 --- a/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 ٹرانسفر ٹولز گائڈ گراف نے Arbitrum One پر L2 پر منتقل ہونا آسان کر دیا ہے۔ پروٹوکول کے شریک کے لیے، تمام نیٹ ورک کے شرکاء کے لیے L2 میں منتقلی کو ہموار بنانے کے لیے L2 ٹرانسفر ٹولز کا ایک سیٹ موجود ہے۔ یہ ٹولز آپ سے اس بات پر منحصر ہوں گے کہ آپ کیا منتقل کر رہے ہیں۔ -ان ٹولز کے بارے میں اکثر پوچھے جانے والے سوالات کا جواب [L2 ٹرانسفر ٹولز اکثر پوچھے گئے سوالات](/arbitrum/l2-transfer-tools-faq). اکثر پوچھے جانے والے سوالات میں ٹولز کو استعمال کرنے کے طریقے، وہ کیسے کام کرتے ہیں، اور ان کو استعمال کرتے وقت ذہن میں رکھنے والی چیزوں کی گہرائی سے وضاحت پر مشتمل ہے۔ +ان ٹولز کے بارے میں اکثر پوچھے جانے والے سوالات کا جواب [L2 ٹرانسفر ٹولز اکثر پوچھے گئے سوالات](/arbitrum/l2-transfer-tools-faq/). اکثر پوچھے جانے والے سوالات میں ٹولز کو استعمال کرنے کے طریقے، وہ کیسے کام کرتے ہیں، اور ان کو استعمال کرتے وقت ذہن میں رکھنے والی چیزوں کی گہرائی سے وضاحت پر مشتمل ہے۔ ## اپنے سب گراف کو Arbitrum (L2) میں کیسے منتقل کریں diff --git a/website/pages/ur/archived/sunrise.mdx b/website/pages/ur/archived/sunrise.mdx index 89e51796c01e..a0cc8160fb91 100644 --- a/website/pages/ur/archived/sunrise.mdx +++ b/website/pages/ur/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ur/contracts.mdx b/website/pages/ur/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/ur/contracts.mdx +++ b/website/pages/ur/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ur/indexing/new-chain-integration.mdx b/website/pages/ur/indexing/new-chain-integration.mdx index 6853e523e756..36e0875c1478 100644 --- a/website/pages/ur/indexing/new-chain-integration.mdx +++ b/website/pages/ur/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Configuring Graph Node is as easy as preparing your local environment. Once your ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ur/indexing/overview.mdx b/website/pages/ur/indexing/overview.mdx index a115bb4c34a3..8c35f54af774 100644 --- a/website/pages/ur/indexing/overview.mdx +++ b/website/pages/ur/indexing/overview.mdx @@ -87,7 +87,7 @@ query indexerAllocations { ### کیوری فی کٹ اور انڈیکسنگ ریوارڈ کٹ کیا ہے؟ -`queryFeeCut` اور `indexingRewardCut` قدریں ڈیلی گیشن پیرامیٹر ہیں جنہیں انڈیکسر, انڈیکسر اور ان کے ڈیلیگیٹرز کے درمیان GRT کی تقسیم کو کنٹرول کرنے کے لیے cooldownBlocks کے ساتھ سیٹ کر سکتا ہے. ڈیلیگیشن کے پیرامیٹرز کو ترتیب دینے کے لیے ہدایات کے لیے [پروٹوکول میں حصہ لینا](/network/indexing#stake-in-the-protocol) میں آخری مراحل دیکھیں. +`queryFeeCut` اور `indexingRewardCut` قدریں ڈیلی گیشن پیرامیٹر ہیں جنہیں انڈیکسر, انڈیکسر اور ان کے ڈیلیگیٹرز کے درمیان GRT کی تقسیم کو کنٹرول کرنے کے لیے cooldownBlocks کے ساتھ سیٹ کر سکتا ہے. ڈیلیگیشن کے پیرامیٹرز کو ترتیب دینے کے لیے ہدایات کے لیے [پروٹوکول میں حصہ لینا](/network/indexing/#stake-in-the-protocol) میں آخری مراحل دیکھیں. - **کیوری فیس کٹ** - کیوری فیس کی چھوٹ کا % جو انڈیکسر میں تقسیم کیا جائے گا۔ اگر اسے 95% پر سیٹ کیا جاتا ہے، تو انڈیکسر کو 95% کیوری فیس موصول ہو گی جب ایک مختص بند ہو جائے گا اور باقی 5% ڈیلیگیٹرز کو جائے گا. @@ -121,7 +121,7 @@ query indexerAllocations { ### وہ کون سی چند بنیادی حفاظتی تدابیر ہیں جو ایک انڈیکسر کو اختیار کرنی چاہیے؟ -- **آپریٹر والیٹ** - آپریٹر والیٹ کا سیٹ اپ کرنا ایک اہم احتیاط ہے کیونکہ یہ ایک انڈیکسر کو اپنی کلیدوں کے درمیان علیحدگی برقرار رکھنے کی اجازت دیتا ہے جو سٹیک کو کنٹرول کرتی ہیں اور جو روزمرہ کے کاموں کے کنٹرول میں ہیں. ہدایات کے لیے [پروٹوکول میں حصہ ڈالنا](/network/indexing#stake-in-the-protocol) دیکھیں. +- **آپریٹر والیٹ** - آپریٹر والیٹ کا سیٹ اپ کرنا ایک اہم احتیاط ہے کیونکہ یہ ایک انڈیکسر کو اپنی کلیدوں کے درمیان علیحدگی برقرار رکھنے کی اجازت دیتا ہے جو سٹیک کو کنٹرول کرتی ہیں اور جو روزمرہ کے کاموں کے کنٹرول میں ہیں. ہدایات کے لیے [پروٹوکول میں حصہ ڈالنا](/network/indexing/#stake-in-the-protocol) دیکھیں. - **فائر وال** - صرف انڈیکسر سروس کو عوامی طور پر ظاہر کی ضرورت ہے اور ایڈمن پورٹس اور ڈیٹا بیس تک رسائی کو لاک ڈاؤن کرنے پر خاص توجہ دی جانی چاہیے: گراف نوڈ JSON-RPC اینڈ پوائنٹ (ڈیفالٹ پورٹ: 8030)، انڈیکسر مینجمنٹ API endpoint (ڈیفالٹ پورٹ: 18000)، اور Postgres ڈیٹا بیس اینڈ پوائنٹ (ڈیفالٹ پورٹ: 5432) کو ظاہر نہیں کرنا چاہیے. @@ -375,7 +375,7 @@ docker-compose up #### شروع کرتے ہوئے -انڈیکسر ایجنٹ اور انڈیکسر سروس آپ کے گراف نوڈ انفراسٹرکچر کے ساتھ مل کر واقع ہونی چاہیے۔ آپ کے انڈیکسر اجزاء کے لیے ورچوئل ایگزیکیوشن ماحول قائم کرنے کے بہت سے طریقے ہیں۔ یہاں ہم وضاحت کریں گے کہ انہیں NPM پیکجز یا سورس کا استعمال کرتے ہوئے، یا گوگل کلاؤڈ کبرنیٹس انجن پر کبرنیٹس اور ڈوکر کے ذریعے بیری میٹل پر کیسے چلایا جائے۔ اگر سیٹ اپ کی یہ مثالیں آپ کے بنیادی ڈھانچے میں اچھی طرح سے ترجمہ نہیں کرتی ہیں تو ممکنہ طور پر حوالہ دینے کے لیے کمیونٹی گائیڈ ہو گا، آئیں [ڈسکورڈ](https://discord.gg/graphprotocol) پر ہیلو کہیں! اپنے انڈیکسر اجزاء کو شروع کرنے سے پہلے [پروٹوکول میں حصہ لینا](/network/indexing#stake-in-the-protocol) یاد رکھیں! +انڈیکسر ایجنٹ اور انڈیکسر سروس آپ کے گراف نوڈ انفراسٹرکچر کے ساتھ مل کر واقع ہونی چاہیے۔ آپ کے انڈیکسر اجزاء کے لیے ورچوئل ایگزیکیوشن ماحول قائم کرنے کے بہت سے طریقے ہیں۔ یہاں ہم وضاحت کریں گے کہ انہیں NPM پیکجز یا سورس کا استعمال کرتے ہوئے، یا گوگل کلاؤڈ کبرنیٹس انجن پر کبرنیٹس اور ڈوکر کے ذریعے بیری میٹل پر کیسے چلایا جائے۔ اگر سیٹ اپ کی یہ مثالیں آپ کے بنیادی ڈھانچے میں اچھی طرح سے ترجمہ نہیں کرتی ہیں تو ممکنہ طور پر حوالہ دینے کے لیے کمیونٹی گائیڈ ہو گا، آئیں [ڈسکورڈ](https://discord.gg/graphprotocol) پر ہیلو کہیں! اپنے انڈیکسر اجزاء کو شروع کرنے سے پہلے [پروٹوکول میں حصہ لینا](/network/indexing/#stake-in-the-protocol) یاد رکھیں! #### NPM پیکیجیز سے @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s اور Terraform کو استعمال کرتے ہوئے -[Google Cloud پر Terraform کا استعمال کرتے ہوئے سرور انفراسٹرکچر سیٹ اپ کریں](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) سیکشن دیکھیں +[Google Cloud پر Terraform کا استعمال کرتے ہوئے سرور انفراسٹرکچر سیٹ اپ کریں](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) سیکشن دیکھیں #### استعمال @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -ایک بار جب ایک انڈیکسر نے پروٹوکول میں GRT کو سٹیک کر دیا ہے، تو [انڈیکسر اجزاء](/network/indexing#indexer-components) کو شروع کیا جا سکتا ہے اور نیٹ ورک کے ساتھ اپنے تعاملات شروع کر سکتے ہیں. +ایک بار جب ایک انڈیکسر نے پروٹوکول میں GRT کو سٹیک کر دیا ہے، تو [انڈیکسر اجزاء](/network/indexing/#indexer-components) کو شروع کیا جا سکتا ہے اور نیٹ ورک کے ساتھ اپنے تعاملات شروع کر سکتے ہیں. #### ٹوکنز منظور کریں diff --git a/website/pages/ur/resources/benefits.mdx b/website/pages/ur/resources/benefits.mdx index 0b17f2bb521d..fd51fcdb633d 100644 --- a/website/pages/ur/resources/benefits.mdx +++ b/website/pages/ur/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. سب گراف پر کیوریٹنگ سگنل ایک اختیاری ایک بار، خالص صفر لاگت ہے (مثال کے طور پر، $1k سگنل کو سب گراف پر کیوریٹ کیا جا سکتا ہے، اور بعد میں واپس لیا جا سکتا ہے—اس عمل میں منافع کمانے کی صلاحیت کے ساتھ). diff --git a/website/pages/ur/resources/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ur/resources/release-notes/graphql-validations-migration-guide.mdx index fba78a067915..569f6a35898b 100644 --- a/website/pages/ur/resources/release-notes/graphql-validations-migration-guide.mdx +++ b/website/pages/ur/resources/release-notes/graphql-validations-migration-guide.mdx @@ -20,7 +20,7 @@ GraphQL ویلیڈیشن سپورٹ آنے والی نئی خصوصیات اور آپ اپنے GraphQL آپریشنز میں کسی بھی مسئلے کو تلاش کرنے اور انہیں ٹھیک کرنے کے لیے CLI مائیگریشن ٹول استعمال کر سکتے ہیں۔ متبادل طور پر آپ `https://api-next.thegraph.com/subgraphs/name/$GITHUB_USER/$SUBGRAPH_NAME` اینڈ پوائنٹ استعمال کرنے کے لیے اپنے GraphQL کلائنٹ کے اینڈ پوائنٹ کو اپ ڈیٹ کر سکتے ہیں۔ اس اختتامی نقطہ کے خلاف اپنے کیوریز کی جانچ کرنے سے آپ کو اپنے کیوریز میں مسائل تلاش کرنے میں مدد ملے گی. -> اگر آپ [GraphQL ESlint](https://the-guild.dev/graphql/eslint/docs) یا [ GraphQL کوڈ جنریٹر] (//https://the-guild.dev) استعمال کر رہے ہیں تو تمام سب گراف کو منتقل کرنے کی ضرورت نہیں ہوگی۔ /graphql/codegen، وہ پہلے ہی اس بات کو یقینی بناتے ہیں کہ آپ کے کیوریز درست ہیں. +> اگر آپ [GraphQL ESlint](https://the-guild.dev/graphql/eslint/docs) یا [ GraphQL کوڈ جنریٹر] (/https://the-guild.dev) استعمال کر رہے ہیں تو تمام سب گراف کو منتقل کرنے کی ضرورت نہیں ہوگی۔ /graphql/codegen، وہ پہلے ہی اس بات کو یقینی بناتے ہیں کہ آپ کے کیوریز درست ہیں. ## مائیگریشن CLI ٹول diff --git a/website/pages/ur/resources/roles/curating.mdx b/website/pages/ur/resources/roles/curating.mdx index bd7bb8b3f57f..bd8819becb72 100644 --- a/website/pages/ur/resources/roles/curating.mdx +++ b/website/pages/ur/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## سگنل کرنے کا طریقہ -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) ایک کیوریٹر مخصوص سب گراف ورژن پر سگنل دینے کا انتخاب کر سکتا ہے، یا وہ اپنے سگنل کو خود بخود اس سب گراف کی جدید ترین پروڈکشن بلڈ میں منتقل کرنے کا انتخاب کر سکتا ہے۔ دونوں درست حکمت عملی ہیں اور ان کے اپنے فوائد اور نقصانات کے ساتھ آتے ہیں. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. گراف میں کیوری کی مارکیٹ فطری طور پر جوان ہے اور اس بات کا خطرہ ہے کہ آپ کا %APY مارکیٹ کی نئی حرکیات کی وجہ سے آپ کی توقع سے کم ہو سکتا ہے. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. ایک سب گراف ایک بگ کی وجہ سے ناکام ہو سکتا ہے. ایک ناکام سب گراف کیوری کی فیس جمع نہیں کرتا ہے. اس کے نتیجے میں،آپ کو انتظار کرنا پڑے گاجب تک کہ ڈویلپر اس بگ کو کو ٹھیک نہیں کرتا اور نیا ورژن تعینات کرتا ہے. - اگر آپ نےسب گراف کے نۓ ورژن کو سبسکرائب کیا ہے. آپ کے حصص خود بخود اس نئے ورژن میں منتقل ہو جائیں گے۔ اس پر 0.5% کیوریشن ٹیکس لگے گا. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ur/subgraphs/cookbook/grafting.mdx b/website/pages/ur/subgraphs/cookbook/grafting.mdx index c204eee68424..1f68b682b55e 100644 --- a/website/pages/ur/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ur/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ title: ایک کنٹریکٹ کو تبدیل کریں اور اس کی تاری مزید معلومات کے لۓ، آپ دیکہ سکتے ہیں: -- [گرافٹنگ](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [گرافٹنگ](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/ur/subgraphs/cookbook/near.mdx b/website/pages/ur/subgraphs/cookbook/near.mdx index 52f99378c67c..f2c62e35b654 100644 --- a/website/pages/ur/subgraphs/cookbook/near.mdx +++ b/website/pages/ur/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ NEAR سب گراف ڈیولپمنٹ کے لیے `graph-cli` اوپر والے و **سب گراف.yaml:** سب گراف مینی فیسٹ، دلچسپی کے ڈیٹا کے ذرائع کی وضاحت کرتا ہے، اور ان پر کارروائی کیسے کی جانی چاہیے۔ NEAR ڈیٹا سورس کا ایک نیا `قسم` ہے. -** schema.graphql:** ایک اسکیما فائل جو اس بات کی وضاحت کرتی ہے کہ آپ کے سب گراف کے لیے کون سا ڈیٹا محفوظ کیا جاتا ہے، اور GraphQL کے ذریعے اس سے کیوری کیسے کیا جائے۔ NEAR سب گراف کے تقاضوں کا احاطہ [موجودہ دستاویزات](/developing/creating-a-subgraph#the-graphql-schema) سے ہوتا ہے. +** schema.graphql:** ایک اسکیما فائل جو اس بات کی وضاحت کرتی ہے کہ آپ کے سب گراف کے لیے کون سا ڈیٹا محفوظ کیا جاتا ہے، اور GraphQL کے ذریعے اس سے کیوری کیسے کیا جائے۔ NEAR سب گراف کے تقاضوں کا احاطہ [موجودہ دستاویزات](/developing/creating-a-subgraph/#the-graphql-schema) سے ہوتا ہے. -**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. +**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. سب گراف کی ترقی کے دوران دو اہم کمانڈز ہیں: @@ -92,13 +92,13 @@ accounts: ### اسکیما کی تعریف -سکیما کی تعریف نتیجے میں سب گراف ڈیٹا بیس کی ساخت اور ہستیوں کے درمیان تعلقات کو بیان کرتی ہے۔ یہ اصل ڈیٹا ماخذ کے بارے میں علمی ہے۔ سب گراف اسکیما کی تعریف کے بارے میں مزید تفصیلات [یہاں](/developing/creating-a-subgraph#the-graphql-schema) ہیں. +سکیما کی تعریف نتیجے میں سب گراف ڈیٹا بیس کی ساخت اور ہستیوں کے درمیان تعلقات کو بیان کرتی ہے۔ یہ اصل ڈیٹا ماخذ کے بارے میں علمی ہے۔ سب گراف اسکیما کی تعریف کے بارے میں مزید تفصیلات [یہاں](/developing/creating-a-subgraph/#the-graphql-schema) ہیں. ### اسمبلی اسکرپٹ سب میپنک پروسیسنگ ایونٹس کے ہینڈلرز [اسمبلی اسکرپٹ](https://www.assemblyscript.org/) میں لکھے گئے ہیں. -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - بلاک ہینڈلرز کو ایک `Block` ملے گا - ریسیپٹ ہینڈلرز کو ایک `ReceiptWithOutcome` ملے گا -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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 سب گراف کی تعیناتی @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx index 987231f87e72..118eeea3c5f3 100644 --- a/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI فائل (فائلیں) آپ کے کنٹریکٹ (کنٹریکٹس) سے م | ورزن | جاری کردہ نوٹس | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx index 7b866d878c0b..01dce298e672 100644 --- a/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ur/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/ur/subgraphs/developing/deploying/multiple-networks.mdx index 5e4fddd79b4f..0f23c9bdb044 100644 --- a/website/pages/ur/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/ur/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## سب گراف کو متعدد نیٹ ورکس پر تعینات کرنا diff --git a/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx index 7a0e9d8ce26e..4a97694d7040 100644 --- a/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - درج ذیل خصوصیات میں سے کوئی بھی استعمال نہیں کرنا چاہیے: - ipfs.cat & ipfs.map - Non-fatal errors diff --git a/website/pages/ur/subgraphs/developing/developer-faq.mdx b/website/pages/ur/subgraphs/developing/developer-faq.mdx index 27c0a08a2147..188f94695f68 100644 --- a/website/pages/ur/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ur/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ One possible alternative solution to this is to store raw data in entities and p Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -[ڈیٹا سورس ٹیمپلیٹس](/developing/creating-a-subgraph#data-source-templates) پر "ڈیٹا سورس ٹیمپلیٹ کو تیز کرنا" سیکشن دیکھیں. +[ڈیٹا سورس ٹیمپلیٹس](/developing/creating-a-subgraph/#data-source-templates) پر "ڈیٹا سورس ٹیمپلیٹ کو تیز کرنا" سیکشن دیکھیں. ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -آپ کو تعاون یافتہ نیٹ ورکس کی فہرست [یہاں](/developing/supported-networks) مل سکتی ہے. +آپ کو تعاون یافتہ نیٹ ورکس کی فہرست [یہاں](/developing/supported-networks/) مل سکتی ہے. ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 11eb334e7ce7..29298733cc75 100644 --- a/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: ڈیسینٹرلائزڈ نیٹ ورک پر سب گراف شائع کرنا --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### شائع شدہ سب گراف کے لیے میٹا ڈیٹا کو اپ ڈیٹ کرنا @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/ur/subgraphs/explorer.mdx b/website/pages/ur/subgraphs/explorer.mdx index 15559398fc2e..934c0a8fcdb7 100644 --- a/website/pages/ur/subgraphs/explorer.mdx +++ b/website/pages/ur/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -انڈیکسر بننے کے بارے میں مزید جاننے کے لیے، آپ [آفیشل دستاویزات](/network/indexing) یا [دی گراف اکیڈمی انڈیکسر گائیڈز۔](https://thegraph.academy/delegators/ پر ایک نظر ڈال سکتے ہیں۔ choosing-indexers/) +انڈیکسر بننے کے بارے میں مزید جاننے کے لیے، آپ [آفیشل دستاویزات](/network/indexing/) یا [دی گراف اکیڈمی انڈیکسر گائیڈز۔](https://thegraph.academy/delegators/ پر ایک نظر ڈال سکتے ہیں۔ choosing-indexers/) ![انڈیکسنگ کی تفصیلات کا پین](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![ایکسپلورر امیج 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### ڈیلیگیٹرز @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - پروٹوکول میں ان کے پاس موجود GRT کی کل رقم - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## نیٹ ورک diff --git a/website/pages/ur/subgraphs/querying/best-practices.mdx b/website/pages/ur/subgraphs/querying/best-practices.mdx index 47954840b8fe..bc0328a3fe43 100644 --- a/website/pages/ur/subgraphs/querying/best-practices.mdx +++ b/website/pages/ur/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - ہر ایک `queryName` کو فی آپریشن صرف ایک بار استعمال کیا جانا چاہیے. - ہر ایک `field` کو انتخاب میں صرف ایک بار استعمال کیا جانا چاہیے (ہم `token` کے تحت دو بار `id` سے کیوری نہیں کرسکتے ہیں) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - کسی دلیل کو تفویض کردہ کوئی بھی متغیر اس کی قسم سے مماثل ہونا چاہیے. - متغیرات کی دی گئی فہرست میں، ان میں سے ہر ایک منفرد ہونا چاہیے. - تمام متعین متغیرات کو استعمال کیا جانا چاہیے. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - کراس چین سب گراف ہینڈلنگ: ایک کیوری میں متعدد سب گرافس سے کیوری کرنا - [خودکار بلاک ٹریکنگ](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/ur/subgraphs/querying/graphql-api.mdx b/website/pages/ur/subgraphs/querying/graphql-api.mdx index dca35f1f671a..0f47773b71eb 100644 --- a/website/pages/ur/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ur/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ The result of such a query will not change over time, i.e., querying at a certai ### فل ٹیکسٹ تلاش کے کیوریز -فل ٹیکسٹ تلاش کے کیوری والے فیلڈز ایک تاثراتی ٹیکسٹ سرچ API فراہم کرتے ہیں جسے سب گراف اسکیما میں شامل کیا جا سکتا ہے اور اپنی مرضی کے مطابق بنایا جا سکتا ہے۔ اپنے سب گراف میں مکمل متن کی تلاش کو شامل کرنے کے لیے [فل ٹیکسٹ سرچ فیلڈز کی وضاحت](/developing/creating-a-subgraph#defining-fulltext-search-fields) سے رجوع کریں. +فل ٹیکسٹ تلاش کے کیوری والے فیلڈز ایک تاثراتی ٹیکسٹ سرچ API فراہم کرتے ہیں جسے سب گراف اسکیما میں شامل کیا جا سکتا ہے اور اپنی مرضی کے مطابق بنایا جا سکتا ہے۔ اپنے سب گراف میں مکمل متن کی تلاش کو شامل کرنے کے لیے [فل ٹیکسٹ سرچ فیلڈز کی وضاحت](/developing/creating-a-subgraph/#defining-fulltext-search-fields) سے رجوع کریں. فل ٹیکسٹ کی تلاش کے کیوریز میں ایک مطلوبہ فیلڈ ہے، `text`, تلاش کی اصطلاحات کی فراہمی کے لیے. اس `text` تلاش کے فیلڈ میں استعمال کرنے کے لیے کئی خصوصی فل ٹیکسٹ آپریٹرز دستیاب ہیں. diff --git a/website/pages/ur/subgraphs/querying/introduction.mdx b/website/pages/ur/subgraphs/querying/introduction.mdx index 518951ee621b..32cb24678086 100644 --- a/website/pages/ur/subgraphs/querying/introduction.mdx +++ b/website/pages/ur/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: گراف سے کیوری کرنا When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/ur/substreams/sps/introduction.mdx b/website/pages/ur/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/ur/substreams/sps/introduction.mdx +++ b/website/pages/ur/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/ur/substreams/sps/triggers.mdx b/website/pages/ur/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/ur/substreams/sps/triggers.mdx +++ b/website/pages/ur/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/ur/supported-networks.mdx b/website/pages/ur/supported-networks.mdx index bfa66b78c21b..8dd466430865 100644 --- a/website/pages/ur/supported-networks.mdx +++ b/website/pages/ur/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx index 5893bd88c0b3..67746ef430fb 100644 --- a/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Hướng dẫn sử dụng công cụ chuyển L2 The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Một số câu hỏi thường gặp về những công cụ này được trả lời trong [Câu hỏi thường gặp về Công cụ chuyển L2](/arbitrum/l2-transfer-tools-faq). Câu hỏi thường gặp chứa các giải thích sâu sắc về cách sử dụng các công cụ, cách chúng hoạt động và những điều cần lưu ý khi sử dụng chúng. +Một số câu hỏi thường gặp về những công cụ này được trả lời trong [Câu hỏi thường gặp về Công cụ chuyển L2](/arbitrum/l2-transfer-tools-faq/). Câu hỏi thường gặp chứa các giải thích sâu sắc về cách sử dụng các công cụ, cách chúng hoạt động và những điều cần lưu ý khi sử dụng chúng. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/vi/archived/sunrise.mdx b/website/pages/vi/archived/sunrise.mdx index 14d1444cf8cd..248ebdc3cc49 100644 --- a/website/pages/vi/archived/sunrise.mdx +++ b/website/pages/vi/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/vi/contracts.mdx b/website/pages/vi/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/vi/contracts.mdx +++ b/website/pages/vi/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/vi/indexing/new-chain-integration.mdx b/website/pages/vi/indexing/new-chain-integration.mdx index 3bb6c774f961..8a65bdc55eec 100644 --- a/website/pages/vi/indexing/new-chain-integration.mdx +++ b/website/pages/vi/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/vi/indexing/overview.mdx b/website/pages/vi/indexing/overview.mdx index 8c5ac85fb98e..6c480e8da348 100644 --- a/website/pages/vi/indexing/overview.mdx +++ b/website/pages/vi/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### Cắt giảm phí truy vấn và cắt giảm phần thưởng indexing là gì? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexer có thể tự phân biệt bản thân bằng cách áp dụng các k ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Bắt đầu -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### Từ các gói NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Sử dụng K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Sử dụng @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. #### Phê duyệt các token diff --git a/website/pages/vi/resources/benefits.mdx b/website/pages/vi/resources/benefits.mdx index 5636695d5931..24ed75834e10 100644 --- a/website/pages/vi/resources/benefits.mdx +++ b/website/pages/vi/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). diff --git a/website/pages/vi/resources/roles/curating.mdx b/website/pages/vi/resources/roles/curating.mdx index b10717935904..db8ccf3e50df 100644 --- a/website/pages/vi/resources/roles/curating.mdx +++ b/website/pages/vi/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Làm thế nào để phát tín hiệu -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) Curator có thể chọn phát tín hiệu trên một phiên bản subgraph cụ thể hoặc họ có thể chọn để tín hiệu của họ tự động chuyển sang bản dựng sản xuất mới nhất của subgraph đó. Cả hai đều là những chiến lược hợp lệ và đi kèm với những ưu và nhược điểm của riêng chúng. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. Một subgraph có thể thất bại do một lỗi. Một subgraph thất bại không tích lũy phí truy vấn. Do đó, bạn sẽ phải đợi cho đến khi nhà phát triển sửa lỗi và triển khai phiên bản mới. - Nếu bạn đã đăng ký phiên bản mới nhất của một subgraph, các cổ phần của bạn sẽ tự động chuyển sang phiên bản mới đó. Điều này sẽ phát sinh một khoản thuế curation 0.5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/vi/subgraphs/cookbook/grafting.mdx b/website/pages/vi/subgraphs/cookbook/grafting.mdx index c37ae95c28e0..87631366eb25 100644 --- a/website/pages/vi/subgraphs/cookbook/grafting.mdx +++ b/website/pages/vi/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ The grafted subgraph can use a GraphQL schema that is not identical to the one o For more information, you can check: -- [Ghép](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [Ghép](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/vi/subgraphs/cookbook/near.mdx b/website/pages/vi/subgraphs/cookbook/near.mdx index bdfa4df2b176..53f3448a1532 100644 --- a/website/pages/vi/subgraphs/cookbook/near.mdx +++ b/website/pages/vi/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ There are three aspects of subgraph definition: **subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source. -**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). +**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/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. +**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: @@ -92,13 +92,13 @@ NEAR data sources support two types of handlers: ### Schema Definition -Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema). +Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema). ### AssemblyScript Mappings The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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/graph-ts/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 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-mainnet` - `near-testnet` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx index 9595add2bc4c..d18e42fb902a 100644 --- a/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx index 20129d442bb4..ce25fbcafc6d 100644 --- a/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | Phiên bản | Ghi chú phát hành | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx b/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx index 6f440ca3ca8c..6acca805ef38 100644 --- a/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/vi/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/vi/subgraphs/developing/deploying/multiple-networks.mdx index dc2b8e533430..4f7dcd3864e8 100644 --- a/website/pages/vi/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/vi/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## Deploying the subgraph to multiple networks diff --git a/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx index 8e4333eec207..a31ab87d24dd 100644 --- a/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Lỗi không nghiêm trọng diff --git a/website/pages/vi/subgraphs/developing/developer-faq.mdx b/website/pages/vi/subgraphs/developing/developer-faq.mdx index 202cab4c4ff2..c4e32c8f1d21 100644 --- a/website/pages/vi/subgraphs/developing/developer-faq.mdx +++ b/website/pages/vi/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ Trong một subgraph, các sự kiện luôn được xử lý theo thứ tự c Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates). +Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates). ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks). +You can find the list of the supported networks [here](/developing/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx index a586af0f6d18..7b5baa296e0b 100644 --- a/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: Publishing a Subgraph to the Decentralized Network --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/vi/subgraphs/explorer.mdx b/website/pages/vi/subgraphs/explorer.mdx index 85dded99b651..d3095fb4f3e0 100644 --- a/website/pages/vi/subgraphs/explorer.mdx +++ b/website/pages/vi/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Tổng lượng GRT mà họ hiện có trong giao thức - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Mạng lưới diff --git a/website/pages/vi/subgraphs/querying/best-practices.mdx b/website/pages/vi/subgraphs/querying/best-practices.mdx index 6e085cfe7bf1..9c2db771238c 100644 --- a/website/pages/vi/subgraphs/querying/best-practices.mdx +++ b/website/pages/vi/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/vi/subgraphs/querying/graphql-api.mdx b/website/pages/vi/subgraphs/querying/graphql-api.mdx index 8db543089d78..dd118022aa46 100644 --- a/website/pages/vi/subgraphs/querying/graphql-api.mdx +++ b/website/pages/vi/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ This query will return `Challenge` entities, and their associated `Application` ### Fulltext Search Queries -Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph#defining-fulltext-search-fields) to add fulltext search to your subgraph. +Fulltext search query fields provide an expressive text search API that can be added to the subgraph schema and customized. Refer to [Defining Fulltext Search Fields](/developing/creating-a-subgraph/#defining-fulltext-search-fields) to add fulltext search to your subgraph. Fulltext search queries have one required field, `text`, for supplying search terms. Several special fulltext operators are available to be used in this `text` search field. diff --git a/website/pages/vi/subgraphs/querying/introduction.mdx b/website/pages/vi/subgraphs/querying/introduction.mdx index b5ea795a934f..95f6722f9dc6 100644 --- a/website/pages/vi/subgraphs/querying/introduction.mdx +++ b/website/pages/vi/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/vi/substreams/sps/introduction.mdx b/website/pages/vi/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/vi/substreams/sps/introduction.mdx +++ b/website/pages/vi/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/vi/substreams/sps/triggers.mdx b/website/pages/vi/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/vi/substreams/sps/triggers.mdx +++ b/website/pages/vi/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/vi/supported-networks.mdx b/website/pages/vi/supported-networks.mdx index 2a9585d3213f..70ad6b027d99 100644 --- a/website/pages/vi/supported-networks.mdx +++ b/website/pages/vi/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/zh/archived/sunrise.mdx b/website/pages/zh/archived/sunrise.mdx index a39e1853cc94..9dd332acaaf1 100644 --- a/website/pages/zh/archived/sunrise.mdx +++ b/website/pages/zh/archived/sunrise.mdx @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/zh/contracts.mdx b/website/pages/zh/contracts.mdx index 6abd80577ced..5b3a9ab09e77 100644 --- a/website/pages/zh/contracts.mdx +++ b/website/pages/zh/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/zh/indexing/new-chain-integration.mdx b/website/pages/zh/indexing/new-chain-integration.mdx index d7a098e18184..c1004c12b66c 100644 --- a/website/pages/zh/indexing/new-chain-integration.mdx +++ b/website/pages/zh/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Configuring Graph Node is as easy as preparing your local environment. Once your ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/zh/indexing/overview.mdx b/website/pages/zh/indexing/overview.mdx index 9daffa4ac7d0..df29ff7d60e9 100644 --- a/website/pages/zh/indexing/overview.mdx +++ b/website/pages/zh/indexing/overview.mdx @@ -87,7 +87,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### 什么是查询费减免和索引奖励减免？ -`queryFeeCut` 和 `indexingRewardCut` 值是委托的参数，该索引可以设置连同 cooldownBlocks 控制 GRT 的索引和他们的委托人之间的分配。 有关设置委托参数的说明，请参阅[协议中的质押](/network/indexing#stake-in-the-protocol)的最后步骤。 +`queryFeeCut` 和 `indexingRewardCut` 值是委托的参数，该索引可以设置连同 cooldownBlocks 控制 GRT 的索引和他们的委托人之间的分配。 有关设置委托参数的说明，请参阅[协议中的质押](/network/indexing/#stake-in-the-protocol)的最后步骤。 - **查询费用削减** - 将分配给索引人的子图上累积的查询费用回扣的百分比。 如果将其设置为 95%，则在申请分配时，索引人将获得查询费用回扣池的 95%，另外 5% 将分配给委托人。 @@ -121,7 +121,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### 索引人应该采取哪些基本的安全防范措施？ -- **运营商钱包** - 设置运营商钱包是一项重要的预防措施，因为它允许索引器在控制股权的密钥和控制日常交易的密钥之间保持分离-天操作。有关说明，请参阅[Stake in Protocol](/network/indexing#stake-in-the-protocol)。 +- **运营商钱包** - 设置运营商钱包是一项重要的预防措施，因为它允许索引器在控制股权的密钥和控制日常交易的密钥之间保持分离-天操作。有关说明，请参阅[Stake in Protocol](/network/indexing/#stake-in-the-protocol)。 - **防火墙** - 只有索引人服务需要公开，尤其要注意锁定管理端口和数据库访问：Graph 节点 JSON-RPC 端点（默认端口：8030）、索引人管理 API 端点（默认端口：18000）和 Postgres 数据库端点（默认端口：5432）不应暴露。 @@ -375,7 +375,7 @@ docker-compose up #### 开始 -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! #### 来自 NPM 包 @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### 使用 K8s 和 Terraform -请参阅[在Google Cloud上使用Terraform设置服务器基础结构](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud)一节。 +请参阅[在Google Cloud上使用Terraform设置服务器基础结构](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud)一节。 #### 使用方法 @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -一旦索引人将GRT置于协议中，[索引人组件](/network/indexing#indexer-components)就可以启动并开始与网络交互。 +一旦索引人将GRT置于协议中，[索引人组件](/network/indexing/#indexer-components)就可以启动并开始与网络交互。 #### 批准代币 diff --git a/website/pages/zh/resources/benefits.mdx b/website/pages/zh/resources/benefits.mdx index 09f7a8fdf07e..aef267eff346 100644 --- a/website/pages/zh/resources/benefits.mdx +++ b/website/pages/zh/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. 在一个子图上策划信号是一个可选一次性净零成本(例如，1千美元的信号可以在一个子图上管理，然后撤回ーー在这个过程中有可能获得回报)。 diff --git a/website/pages/zh/resources/roles/curating.mdx b/website/pages/zh/resources/roles/curating.mdx index 1788ca600226..1672eaad69f1 100644 --- a/website/pages/zh/resources/roles/curating.mdx +++ b/website/pages/zh/resources/roles/curating.mdx @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## 如何进行信号处理 -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) 策展人可以选择在特定的子图版本上发出信号，或者他们可以选择让他们的策展份额自动迁移到该子图的最新生产版本。 这两种策略都是有效的，都有各自的优点和缺点。 @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. 在Graph，查询市场本来就很年轻，由于市场动态刚刚开始，你的年收益率可能低于你的预期，这是有风险的。 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). 4. 一个子图可能由于错误而失败。 一个失败的子图不会累积查询费用。 因此，你必须等待，直到开发人员修复错误并部署一个新的版本。 - 如果你订阅了一个子图的最新版本，你的份额将自动迁移到该新版本。 这将产生 0.5%的策展税。 - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/zh/subgraphs/cookbook/grafting.mdx b/website/pages/zh/subgraphs/cookbook/grafting.mdx index c98e74e7d670..2738082e21da 100644 --- a/website/pages/zh/subgraphs/cookbook/grafting.mdx +++ b/website/pages/zh/subgraphs/cookbook/grafting.mdx @@ -20,7 +20,7 @@ title: 用嫁接替换合约并保持合约的历史 有关详情，请参阅: -- [嫁接](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs) +- [嫁接](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract. diff --git a/website/pages/zh/subgraphs/cookbook/near.mdx b/website/pages/zh/subgraphs/cookbook/near.mdx index f166aa66e611..6c986e7775fb 100644 --- a/website/pages/zh/subgraphs/cookbook/near.mdx +++ b/website/pages/zh/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ NEAR 子图开发需要`0.23.0`以上版本的`graph-cli`，以及 `0.23.0`以 **subgraph.yaml:** 子图清单，定义感兴趣的数据源以及如何处理它们。 NEAR 是一种全新`类型`数据源。 -**schema.graphql:** 一个模式文件，定义子图存储的数据以及如何通过 GraphQL 查询数据。NEAR 子图的要求已经在[现有的文档](/developing/creating-a-subgraph#the-graphql-schema)中介绍了。 +**schema.graphql:** 一个模式文件，定义子图存储的数据以及如何通过 GraphQL 查询数据。NEAR 子图的要求已经在[现有的文档](/developing/creating-a-subgraph/#the-graphql-schema)中介绍了。 -**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. +**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. 在子图开发过程中，有两个关键命令： @@ -92,13 +92,13 @@ NEAR 数据源支持两种类型的处理程序： ### 模式定义 -模式定义描述了生成的子图数据库结构以及实体之间的关系。这与原始数据源是不可知的。[这里](/developing/creating-a-subgraph#the-graphql-schema)有更多关于子图模式定义的细节。 +模式定义描述了生成的子图数据库结构以及实体之间的关系。这与原始数据源是不可知的。[这里](/developing/creating-a-subgraph/#the-graphql-schema)有更多关于子图模式定义的细节。 ### AssemblyScript 映射 处理事件的处理程序是用 [AssemblyScript](https://www.assemblyscript.org/) 编写的。 -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - 块处理程序将收到 `Block` - 收据处理程序将收到 `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/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/graph-ts/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 子图 @@ -178,7 +178,7 @@ Subgraph Studio and the upgrade Indexer on The Graph Network currently supports - `near-主网` - `near-测试网` -More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio). +More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio/). As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph". @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: diff --git a/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx index 1258acc91021..9db4e62530b6 100644 --- a/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx @@ -108,7 +108,7 @@ ABI 文件必须与您的合约相匹配。 获取 ABI 文件的方法有以下 | 版本 | Release 说明 | | :-: | --- | -| 1.2.0 | Added support for [Indexed Argument Filtering](//#indexed-argument-filters--topic-filters) & declared `eth_call` | +| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` | | 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. | | 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs | | 0.0.9 | Supports `endBlock` feature | diff --git a/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx b/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx index eb5be4580baf..28101b955e31 100644 --- a/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/zh/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/zh/subgraphs/developing/deploying/multiple-networks.mdx index 77292d1df580..3608f13cb405 100644 --- a/website/pages/zh/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/zh/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Deploying a Subgraph to Multiple Networks --- -This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph). +This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph/). ## 将子图部署到多个网络 diff --git a/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx index d3ee2203f7d3..a0e8ce484342 100644 --- a/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -59,7 +59,7 @@ npm install -g @graphprotocol/graph-cli In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks) +- Index a [supported network](/developing/supported-networks/) - 不得使用以下任何功能： - ipfs.cat & ipfs.map - 非致命错误 diff --git a/website/pages/zh/subgraphs/developing/developer-faq.mdx b/website/pages/zh/subgraphs/developing/developer-faq.mdx index 8b62385e49c4..9299dc71d7e9 100644 --- a/website/pages/zh/subgraphs/developing/developer-faq.mdx +++ b/website/pages/zh/subgraphs/developing/developer-faq.mdx @@ -50,7 +50,7 @@ One possible alternative solution to this is to store raw data in entities and p Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address. -请查看“实例化数据源模板”部分：[数据源模板](/developing/creating-a-subgraph#data-source-templates)。 +请查看“实例化数据源模板”部分：[数据源模板](/developing/creating-a-subgraph/#data-source-templates)。 ### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`? @@ -86,7 +86,7 @@ Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/tra ### 16. What networks are supported by The Graph? -您可以在[这里](/developing/supported-networks)找到支持的网络列表。 +您可以在[这里](/developing/supported-networks/)找到支持的网络列表。 ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? @@ -107,11 +107,11 @@ Yes. Sepolia supports block handlers, call handlers and event handlers. It shoul ### 19. Is it possible to specify what block to start indexing on? -Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync -Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks) +Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph/#start-blocks) ### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed? diff --git a/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx index ea8ef8ec74d2..a40080f30ea0 100644 --- a/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -2,16 +2,16 @@ title: 向去中心化的网络发布子图 --- -Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network. +Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/) and it's ready to go into production, you can publish it to the decentralized network. When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating) to begin curating it. -- [Indexers](/network/indexing) to begin indexing it. +- [Curators](/network/curating/) to begin curating it. +- [Indexers](/network/indexing/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks). +Check out the list of [supported networks](/developing/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. ### 更新已发布的子图的元数据 @@ -69,7 +69,7 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks). +- Specific supported networks can be checked [here](/developing/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. diff --git a/website/pages/zh/subgraphs/explorer.mdx b/website/pages/zh/subgraphs/explorer.mdx index 1c080a696a81..3155efb373fb 100644 --- a/website/pages/zh/subgraphs/explorer.mdx +++ b/website/pages/zh/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -要了解有关如何成为 Indexer 的更多信息，您可以查看[官方文档](/network/indexing) 或 [Graph Academy 索引器指南。](https://thegraph.academy/delegators/选择索引器/) +要了解有关如何成为 Indexer 的更多信息，您可以查看[官方文档](/network/indexing/) 或 [Graph Academy 索引器指南。](https://thegraph.academy/delegators/选择索引器/) ![索引详细信息窗格](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![资源管理器图片 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. 委托人 @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - 目前在协议中的 GRT 总量 - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## 网络 diff --git a/website/pages/zh/subgraphs/querying/best-practices.mdx b/website/pages/zh/subgraphs/querying/best-practices.mdx index 9f09b3c3e636..40fc694b41d1 100644 --- a/website/pages/zh/subgraphs/querying/best-practices.mdx +++ b/website/pages/zh/subgraphs/querying/best-practices.mdx @@ -54,7 +54,7 @@ query [operationName]([variableName]: [variableType]) { - 每个操作只能使用一次 `queryName`。 - 每个`field`在选择中只能使用一次(我们不能在`token`下查询 `id` 两次) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). - 分配给参数的任何变量都必须匹配其类型。 - 在给定的变量列表中，每个变量必须是唯一的。 - 必须使用所有已定义的变量。 @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - 跨链子图处理: 在一个查询中从多个子图进行查询 - [自动区块跟踪](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application). +More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). --- diff --git a/website/pages/zh/subgraphs/querying/graphql-api.mdx b/website/pages/zh/subgraphs/querying/graphql-api.mdx index 7ba254944ed7..086997107f47 100644 --- a/website/pages/zh/subgraphs/querying/graphql-api.mdx +++ b/website/pages/zh/subgraphs/querying/graphql-api.mdx @@ -329,7 +329,7 @@ The result of such a query will not change over time, i.e., querying at a certai ### 全文搜索查询 -全文搜索查询字段提供了一个表达性的文本搜索 API，可以添加到子图模式中并进行自定义。 请参阅[定义全文搜索字段](/developing/creating-a-subgraph#defining-fulltext-search-fields)以将全文搜索添加到您的子图中。 +全文搜索查询字段提供了一个表达性的文本搜索 API，可以添加到子图模式中并进行自定义。 请参阅[定义全文搜索字段](/developing/creating-a-subgraph/#defining-fulltext-search-fields)以将全文搜索添加到您的子图中。 全文搜索查询有一个必填字段 `text`，用于提供搜索词。 在这个 `text` 搜索字段中可以使用几个特殊的全文运算符。 diff --git a/website/pages/zh/subgraphs/querying/introduction.mdx b/website/pages/zh/subgraphs/querying/introduction.mdx index d6f1f3d35b31..a57c2ee304da 100644 --- a/website/pages/zh/subgraphs/querying/introduction.mdx +++ b/website/pages/zh/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: 查询Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices) +> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application). +Learn more about querying from an application [here](/querying/querying-from-an-application/). -As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio). +As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). diff --git a/website/pages/zh/substreams/sps/introduction.mdx b/website/pages/zh/substreams/sps/introduction.mdx index 7c5fcae61777..fd16c10f5c19 100644 --- a/website/pages/zh/substreams/sps/introduction.mdx +++ b/website/pages/zh/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ By using a Substreams package (`.spkg`) as a data source, your subgraph gains ac There are two methods of enabling this technology: -Using Substreams [triggers](/substreams/sps/triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. +Using Substreams [triggers](/substreams/sps/triggers/): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph. Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities. diff --git a/website/pages/zh/substreams/sps/triggers.mdx b/website/pages/zh/substreams/sps/triggers.mdx index 8c8f9cf5b83b..e5e510a6a7ad 100644 --- a/website/pages/zh/substreams/sps/triggers.mdx +++ b/website/pages/zh/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: Substreams Triggers Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework. -> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction) to scaffold your first project in the Development Container. +> Note: If you haven’t already, visit one of the How-To Guides found [here](/substreams/sps/introduction/) to scaffold your first project in the Development Container. The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created. @@ -34,4 +34,4 @@ Here's what you’re seeing in the `mappings.ts` file: 2. Looping over the transactions 3. Create a new subgraph entity for every transaction -To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial). +To go through a detailed example of a trigger-based subgraph, [click here](/substreams/sps/tutorial/). diff --git a/website/pages/zh/supported-networks.mdx b/website/pages/zh/supported-networks.mdx index 487d607586af..6b8f7177d123 100644 --- a/website/pages/zh/supported-networks.mdx +++ b/website/pages/zh/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. From 4784b80622f6db0a66a293bf63963dcdd7eefb02 Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 19:38:30 -0500 Subject: [PATCH 21/22] Add redirects --- nginx.conf | 148 +++++++++++++++++++++++++++++++++++------------------ 1 file changed, 99 insertions(+), 49 deletions(-) diff --git a/nginx.conf b/nginx.conf index 8e170e494aeb..0582c6da2396 100644 --- a/nginx.conf +++ b/nginx.conf @@ -48,56 +48,106 @@ http { 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; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/delegating/$ $scheme://$http_host/docs/$1/network/delegating/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/network-transition-faq/$ $scheme://$http_host/docs/$1/arbitrum/arbitrum-faq/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/assemblyscript-api/$ $scheme://$http_host/docs/$1/developing/assemblyscript-api/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/assemblyscript-migration-guide/$ $scheme://$http_host/docs/$1/release-notes/assemblyscript-migration-guide/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/create-subgraph-hosted/$ $scheme://$http_host/docs/$1/developing/creating-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/define-subgraph-hosted/$ $scheme://$http_host/docs/$1/developing/defining-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/deprecating-a-subgraph/$ $scheme://$http_host/docs/$1/managing/deprecating-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/developer-faq/$ $scheme://$http_host/docs/$1/developing/developer-faqs/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/distributed-systems/$ $scheme://$http_host/docs/$1/querying/distributed-systems/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/graphql-api/$ $scheme://$http_host/docs/$1/querying/graphql-api/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/matchstick/$ $scheme://$http_host/docs/$1/developing/unit-testing-framework/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/publish-subgraph/$ $scheme://$http_host/docs/$1/publishing/publishing-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/query-the-graph/$ $scheme://$http_host/docs/$1/querying/querying-the-graph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/querying-best-practices/$ $scheme://$http_host/docs/$1/querying/querying-best-practices/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/querying-from-your-app/$ $scheme://$http_host/docs/$1/querying/querying-from-an-application/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/quick-start/$ $scheme://$http_host/docs/$1/quick-start/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/subgraph-debug-forking/$ $scheme://$http_host/docs/$1/cookbook/subgraph-debug-forking/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/explorer/$ $scheme://$http_host/docs/$1/network/explorer/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/hosted-service/deploy-subgraph-hosted/$ $scheme://$http_host/docs/$1/deploying/deploying-a-subgraph-to-hosted/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/hosted-service/migrating-subgraph/$ $scheme://$http_host/docs/$1/cookbook/migrating-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/hosted-service/query-hosted-service/$ $scheme://$http_host/docs/$1/querying/querying-the-hosted-service/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/hosted-service/what-is-hosted-service/$ $scheme://$http_host/docs/$1/deploying/hosted-service/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/indexing/$ $scheme://$http_host/docs/$1/network/indexing/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/billing/$ $scheme://$http_host/docs/$1/querying/billing/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/deploy-subgraph-studio/$ $scheme://$http_host/docs/$1/deploying/deploying-a-subgraph-to-studio/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/managing-api-keys/$ $scheme://$http_host/docs/$1/querying/managing-api-keys/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/multisig/$ $scheme://$http_host/docs/$1/cookbook/multisig/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/studio-faq/$ $scheme://$http_host/docs/$1/deploying/subgraph-studio-faqs/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/subgraph-studio/$ $scheme://$http_host/docs/$1/deploying/subgraph-studio/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/transferring-subgraph-ownership/$ $scheme://$http_host/docs/$1/managing/transferring-subgraph-ownership/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-networks/arweave/$ $scheme://$http_host/docs/$1/cookbook/arweave/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-networks/cosmos/$ $scheme://$http_host/docs/$1/cookbook/cosmos/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-networks/near/$ $scheme://$http_host/docs/$1/cookbook/near/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/defining-a-subgraph/$ $scheme://$http_host/docs/$1/developing/creating-a-subgraph/ permanent; - 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/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/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])/deploying/deploying-a-subgraph-to-studio/$ $scheme://$http_host/docs/$1/deploying/deploy-using-subgraph-studio/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/subgraph-studio/$ $scheme://$http_host/docs/$1/deploying/deploy-using-subgraph-studio/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/deprecate-a-subgraph/$ $scheme://$http_host/docs/$1/managing/delete-a-subgraph/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/$ $scheme://$http_host/docs/$1/developing/creating-a-subgraph/starting-your-subgraph/ permanent; + 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])/arbitrum-faq/$ $scheme://$http_host/docs/$1/archived/arbitrum/arbitrum-faq/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/arbitrum/l2-transfer-tools-faq/$ $scheme://$http_host/docs/$1/archived/arbitrum/l2-transfer-tools-faq/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/arbitrum/l2-transfer-tools-guide/$ $scheme://$http_host/docs/$1/archived/arbitrum/l2-transfer-tools-guide/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/billing/$ $scheme://$http_host/docs/$1/subgraphs/billing/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/chain-integration-overview/$ $scheme://$http_host/docs/$1/indexing/chain-integration-overview/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/arweave/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/arweave/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/avoid-eth-calls/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/avoid-eth-calls/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/cosmos/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/cosmos/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/derivedfrom/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/derivedfrom/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/enums/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/enums/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/grafting-hotfix/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/grafting-hotfix/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/grafting/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/grafting/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/immutable-entities-bytes-as-ids/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/immutable-entities-bytes-as-ids/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/near/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/near/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/pruning/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/pruning/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$ $scheme://$http_host/docs/$1/subgraphs/quick-start/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/subgraph-debug-forking/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/subgraph-debug-forking/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/subgraph-uncrashable/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/subgraph-uncrashable/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/substreams-powered-subgraphs/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/substreams-powered-subgraphs/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/timeseries/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/timeseries/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/transfer-to-the-graph/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/transfer-to-the-graph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/curating/$ $scheme://$http_host/docs/$1/resources/roles/curating/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/delegating/$ $scheme://$http_host/docs/$1/resources/roles/delegating/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/deploy-using-subgraph-studio/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/using-subgraph-studio/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/deploying-a-subgraph-to-studio/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/using-subgraph-studio/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/multiple-networks/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/multiple-networks/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/subgraph-studio-faqs/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/subgraph-studio-faq/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/subgraph-studio/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/using-subgraph-studio/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/assemblyscript-api/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/graph-ts/api/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/starting-your-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/starting-your-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/install-the-cli/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/install-the-cli/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/ql-schema/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/ql-schema/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/assemblyscript-mappings/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/assemblyscript-mappings/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/advanced/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/advanced/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/defining-a-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/starting-your-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/developer-faqs/$ $scheme://$http_host/docs/$1/subgraphs/developing/developer-faq/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/graph-ts/api/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/graph-ts/api/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/graph-ts/CHANGELOG/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/graph-ts/CHANGELOG/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/graph-ts/common-issues/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/graph-ts/common-issues/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/graph-ts/README/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/graph-ts/README/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/substreams-powered-subgraphs-faq/$ $scheme://$http_host/docs/$1/substreams/sps/sps-faq/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/supported-networks/$ $scheme://$http_host/docs/$1/supported-networks/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/unit-testing-framework/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/unit-testing-framework/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/explorer/$ $scheme://$http_host/docs/$1/subgraphs/explorer/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/firehose/$ $scheme://$http_host/docs/$1/indexing/tooling/firehose/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/glossary/$ $scheme://$http_host/docs/$1/resources/glossary/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/graphcast/$ $scheme://$http_host/docs/$1/indexing/tooling/graphcast/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/indexing/$ $scheme://$http_host/docs/$1/indexing/overview/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/delete-a-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/managing/deleting-a-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/deprecate-a-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/managing/deleting-a-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/managing/transfer-a-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/managing/transferring-a-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network-transition-faq/$ $scheme://$http_host/docs/$1/archived/arbitrum/arbitrum-faq/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network/benefits/$ $scheme://$http_host/docs/$1/resources/benefits/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network/contracts/$ $scheme://$http_host/docs/$1/contracts/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network/curating/$ $scheme://$http_host/docs/$1/resources/roles/curating/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network/delegating/$ $scheme://$http_host/docs/$1/resources/roles/delegating/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network/developing/$ $scheme://$http_host/docs/$1/subgraphs/developing/introduction/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network/explorer/$ $scheme://$http_host/docs/$1/subgraphs/explorer/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/network/indexing/$ $scheme://$http_host/docs/$1/indexing/overview/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/new-chain-integration/$ $scheme://$http_host/docs/$1/indexing/new-chain-integration/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/operating-graph-node/$ $scheme://$http_host/docs/$1/indexing/tooling/graph-node/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/publishing/publishing-a-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/publishing/publishing-a-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/distributed-systems/$ $scheme://$http_host/docs/$1/subgraphs/querying/distributed-systems/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/graph-client/README/$ $scheme://$http_host/docs/$1/subgraphs/querying/graph-client/README/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/graph-client/architecture/$ $scheme://$http_host/docs/$1/subgraphs/querying/graph-client/architecture/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/graph-client/live/$ $scheme://$http_host/docs/$1/subgraphs/querying/graph-client/live/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/graphql-api/$ $scheme://$http_host/docs/$1/subgraphs/querying/graphql-api/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/managing-api-keys/$ $scheme://$http_host/docs/$1/subgraphs/querying/managing-api-keys/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/querying-best-practices/$ $scheme://$http_host/docs/$1/subgraphs/querying/best-practices/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/querying-by-subgraph-id-vs-deployment-id/$ $scheme://$http_host/docs/$1/subgraphs/querying/subgraph-id-vs-deployment-id/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/querying-from-an-application/$ $scheme://$http_host/docs/$1/subgraphs/querying/from-an-application/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/querying-the-graph/$ $scheme://$http_host/docs/$1/subgraphs/querying/introduction/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/querying/querying-with-python/$ $scheme://$http_host/docs/$1/subgraphs/querying/python/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/quick-start/$ $scheme://$http_host/docs/$1/subgraphs/quick-start/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/release-notes/assemblyscript-migration-guide/$ $scheme://$http_host/docs/$1/resources/release-notes/assemblyscript-migration-guide/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/release-notes/graphql-validations-migration-guide/$ $scheme://$http_host/docs/$1/resources/release-notes/graphql-validations-migration-guide/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/sps/introduction/$ $scheme://$http_host/docs/$1/substreams/sps/introduction/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/sps/triggers-example/$ $scheme://$http_host/docs/$1/substreams/sps/tutorial/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/sps/triggers/$ $scheme://$http_host/docs/$1/substreams/sps/triggers/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/billing/$ $scheme://$http_host/docs/$1/subgraphs/billing/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/deploy-subgraph-studio/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/using-subgraph-studio/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/managing-api-keys/$ $scheme://$http_host/docs/$1/subgraphs/querying/managing-api-keys/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/multisig/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/multisig/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/studio-faq/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/subgraph-studio-faq/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/subgraph-studio/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/using-subgraph-studio/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/studio/transferring-subgraph-ownership/$ $scheme://$http_host/docs/$1/subgraphs/developing/managing/transferring-a-subgraph/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/subgraphs/$ $scheme://$http_host/docs/$1/subgraphs/developing/subgraphs/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/substreams/$ $scheme://$http_host/docs/$1/substreams/introduction/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/sunrise/$ $scheme://$http_host/docs/$1/archived/sunrise/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-network-requirements/$ $scheme://$http_host/docs/$1/indexing/supported-network-requirements/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-networks/arweave/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/arweave/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-networks/cosmos/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/cosmos/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-networks/near/$ $scheme://$http_host/docs/$1/subgraphs/cookbook/near/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/tap/$ $scheme://$http_host/docs/$1/indexing/tap/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/tokenomics/$ $scheme://$http_host/docs/$1/resources/tokenomics/ 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/subgraphs/querying/graph-client/README/ redirect; + rewrite ^/docs/en/developing/graph-ts/$ $scheme://$http_host/docs/en/subgraphs/developing/creating/graph-ts/README/ redirect; location / { try_files $uri $uri.html $uri/index.html =404; From 5fb5d3a93130ce7c18cd3c101350ee697ff89dcf Mon Sep 17 00:00:00 2001 From: benface Date: Wed, 18 Dec 2024 20:45:40 -0500 Subject: [PATCH 22/22] Update links in all pages --- nginx.conf | 1 + website/pages/[locale]/index.mdx | 2 +- website/pages/ar/about.mdx | 2 +- .../ar/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ar/archived/sunrise.mdx | 6 ++--- website/pages/ar/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../ar/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ar/indexing/overview.mdx | 12 +++++----- website/pages/ar/indexing/tap.mdx | 4 ++-- website/pages/ar/resources/benefits.mdx | 4 ++-- website/pages/ar/resources/roles/curating.mdx | 6 ++--- website/pages/ar/resources/tokenomics.mdx | 8 +++---- website/pages/ar/subgraphs/billing.mdx | 8 +++---- .../pages/ar/subgraphs/cookbook/arweave.mdx | 4 ++-- .../ar/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/ar/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../ar/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../ar/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/ar/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/ar/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/ar/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ar/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../ar/subgraphs/developing/developer-faq.mdx | 8 +++---- .../ar/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../ar/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/ar/subgraphs/explorer.mdx | 6 ++--- .../ar/subgraphs/querying/best-practices.mdx | 8 +++---- .../ar/subgraphs/querying/graphql-api.mdx | 2 +- .../ar/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/ar/subgraphs/quick-start.mdx | 12 +++++----- website/pages/ar/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/ar/supported-networks.mdx | 2 +- website/pages/cs/about.mdx | 2 +- .../cs/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/cs/archived/sunrise.mdx | 6 ++--- website/pages/cs/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../cs/indexing/new-chain-integration.mdx | 4 ++-- website/pages/cs/indexing/overview.mdx | 12 +++++----- website/pages/cs/indexing/tap.mdx | 4 ++-- website/pages/cs/resources/benefits.mdx | 4 ++-- website/pages/cs/resources/roles/curating.mdx | 6 ++--- website/pages/cs/resources/tokenomics.mdx | 8 +++---- website/pages/cs/subgraphs/billing.mdx | 8 +++---- .../pages/cs/subgraphs/cookbook/arweave.mdx | 4 ++-- .../cs/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/cs/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../cs/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../cs/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/cs/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/cs/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/cs/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../cs/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../cs/subgraphs/developing/developer-faq.mdx | 8 +++---- .../cs/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../cs/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/cs/subgraphs/explorer.mdx | 6 ++--- .../cs/subgraphs/querying/best-practices.mdx | 8 +++---- .../cs/subgraphs/querying/graphql-api.mdx | 2 +- .../cs/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/cs/subgraphs/quick-start.mdx | 12 +++++----- website/pages/cs/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/cs/supported-networks.mdx | 2 +- website/pages/de/about.mdx | 2 +- .../de/archived/arbitrum/arbitrum-faq.mdx | 4 ++-- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/de/archived/sunrise.mdx | 6 ++--- website/pages/de/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../de/indexing/new-chain-integration.mdx | 4 ++-- website/pages/de/indexing/overview.mdx | 12 +++++----- website/pages/de/indexing/tap.mdx | 4 ++-- website/pages/de/resources/benefits.mdx | 4 ++-- website/pages/de/resources/roles/curating.mdx | 6 ++--- website/pages/de/resources/tokenomics.mdx | 8 +++---- website/pages/de/subgraphs/billing.mdx | 8 +++---- .../pages/de/subgraphs/cookbook/arweave.mdx | 4 ++-- .../de/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/de/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../de/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../de/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/de/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/de/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/de/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../de/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../de/subgraphs/developing/developer-faq.mdx | 8 +++---- .../de/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../de/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/de/subgraphs/explorer.mdx | 6 ++--- .../de/subgraphs/querying/best-practices.mdx | 8 +++---- .../de/subgraphs/querying/graphql-api.mdx | 2 +- .../de/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/de/subgraphs/quick-start.mdx | 12 +++++----- website/pages/de/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/de/supported-networks.mdx | 2 +- website/pages/en/about.mdx | 2 +- .../en/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/en/archived/sunrise.mdx | 6 ++--- website/pages/en/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../en/indexing/new-chain-integration.mdx | 4 ++-- website/pages/en/indexing/overview.mdx | 12 +++++----- website/pages/en/indexing/tap.mdx | 4 ++-- website/pages/en/resources/benefits.mdx | 4 ++-- website/pages/en/resources/roles/curating.mdx | 6 ++--- website/pages/en/resources/tokenomics.mdx | 8 +++---- website/pages/en/subgraphs/billing.mdx | 8 +++---- .../pages/en/subgraphs/cookbook/arweave.mdx | 4 ++-- .../en/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/en/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../en/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../en/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/en/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/en/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/en/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/secure-api-keys-nextjs.mdx | 2 +- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../en/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../creating/graph-ts/[[...slug]].mdx | 2 +- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 14 ++++++------ .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../en/subgraphs/developing/developer-faq.mdx | 8 +++---- .../en/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../en/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/en/subgraphs/explorer.mdx | 6 ++--- .../en/subgraphs/querying/best-practices.mdx | 8 +++---- .../querying/graph-client/[[...slug]].mdx | 2 +- .../en/subgraphs/querying/graphql-api.mdx | 2 +- .../en/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/en/subgraphs/quick-start.mdx | 12 +++++----- website/pages/en/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/en/supported-networks.mdx | 2 +- website/pages/es/about.mdx | 2 +- .../es/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/es/archived/sunrise.mdx | 6 ++--- website/pages/es/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../es/indexing/new-chain-integration.mdx | 4 ++-- website/pages/es/indexing/overview.mdx | 12 +++++----- website/pages/es/indexing/tap.mdx | 4 ++-- website/pages/es/resources/benefits.mdx | 4 ++-- website/pages/es/resources/roles/curating.mdx | 6 ++--- website/pages/es/resources/tokenomics.mdx | 8 +++---- website/pages/es/subgraphs/billing.mdx | 8 +++---- .../pages/es/subgraphs/cookbook/arweave.mdx | 4 ++-- .../es/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/es/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../es/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../es/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/es/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/es/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/es/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../es/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../es/subgraphs/developing/developer-faq.mdx | 8 +++---- .../es/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../es/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/es/subgraphs/explorer.mdx | 6 ++--- .../es/subgraphs/querying/best-practices.mdx | 8 +++---- .../es/subgraphs/querying/graphql-api.mdx | 2 +- .../es/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/es/subgraphs/quick-start.mdx | 12 +++++----- website/pages/es/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/es/supported-networks.mdx | 2 +- website/pages/fr/about.mdx | 2 +- .../fr/archived/arbitrum/arbitrum-faq.mdx | 4 ++-- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/fr/archived/sunrise.mdx | 6 ++--- website/pages/fr/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../fr/indexing/new-chain-integration.mdx | 4 ++-- website/pages/fr/indexing/overview.mdx | 12 +++++----- website/pages/fr/indexing/tap.mdx | 4 ++-- website/pages/fr/resources/benefits.mdx | 4 ++-- website/pages/fr/resources/roles/curating.mdx | 6 ++--- website/pages/fr/resources/tokenomics.mdx | 8 +++---- website/pages/fr/subgraphs/billing.mdx | 8 +++---- .../pages/fr/subgraphs/cookbook/arweave.mdx | 4 ++-- .../fr/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/fr/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../fr/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../fr/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/fr/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/fr/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/fr/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../fr/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../fr/subgraphs/developing/developer-faq.mdx | 8 +++---- .../fr/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../fr/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/fr/subgraphs/explorer.mdx | 6 ++--- .../fr/subgraphs/querying/best-practices.mdx | 8 +++---- .../fr/subgraphs/querying/graphql-api.mdx | 2 +- .../fr/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/fr/subgraphs/quick-start.mdx | 12 +++++----- website/pages/fr/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/fr/supported-networks.mdx | 2 +- website/pages/hi/about.mdx | 2 +- .../hi/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/hi/archived/sunrise.mdx | 6 ++--- website/pages/hi/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../hi/indexing/new-chain-integration.mdx | 2 +- website/pages/hi/indexing/overview.mdx | 12 +++++----- website/pages/hi/indexing/tap.mdx | 4 ++-- website/pages/hi/resources/benefits.mdx | 4 ++-- website/pages/hi/resources/roles/curating.mdx | 6 ++--- website/pages/hi/resources/tokenomics.mdx | 8 +++---- website/pages/hi/subgraphs/billing.mdx | 8 +++---- .../pages/hi/subgraphs/cookbook/arweave.mdx | 4 ++-- .../hi/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/hi/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../hi/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../hi/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/hi/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/hi/subgraphs/cookbook/near.mdx | 16 +++++++------- .../pages/hi/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../hi/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../hi/subgraphs/developing/developer-faq.mdx | 8 +++---- .../hi/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../hi/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/hi/subgraphs/explorer.mdx | 6 ++--- .../hi/subgraphs/querying/best-practices.mdx | 8 +++---- .../hi/subgraphs/querying/graphql-api.mdx | 2 +- .../hi/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/hi/subgraphs/quick-start.mdx | 12 +++++----- .../pages/hi/substreams/sps/introduction.mdx | 2 +- website/pages/hi/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/hi/substreams/sps/triggers.mdx | 4 ++-- website/pages/hi/supported-networks.mdx | 2 +- website/pages/it/about.mdx | 2 +- .../it/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/it/archived/sunrise.mdx | 6 ++--- website/pages/it/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../it/indexing/new-chain-integration.mdx | 4 ++-- website/pages/it/indexing/overview.mdx | 12 +++++----- website/pages/it/indexing/tap.mdx | 4 ++-- website/pages/it/resources/benefits.mdx | 4 ++-- website/pages/it/resources/roles/curating.mdx | 6 ++--- website/pages/it/resources/tokenomics.mdx | 8 +++---- website/pages/it/subgraphs/billing.mdx | 8 +++---- .../pages/it/subgraphs/cookbook/arweave.mdx | 4 ++-- .../it/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/it/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../it/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../it/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/it/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/it/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/it/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../it/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../it/subgraphs/developing/developer-faq.mdx | 8 +++---- .../it/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../it/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/it/subgraphs/explorer.mdx | 6 ++--- .../it/subgraphs/querying/best-practices.mdx | 8 +++---- .../it/subgraphs/querying/graphql-api.mdx | 2 +- .../it/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/it/subgraphs/quick-start.mdx | 12 +++++----- website/pages/it/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/it/supported-networks.mdx | 2 +- website/pages/ja/about.mdx | 2 +- .../ja/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ja/archived/sunrise.mdx | 6 ++--- website/pages/ja/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../ja/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ja/indexing/overview.mdx | 12 +++++----- website/pages/ja/indexing/tap.mdx | 4 ++-- website/pages/ja/resources/benefits.mdx | 4 ++-- website/pages/ja/resources/roles/curating.mdx | 6 ++--- website/pages/ja/resources/tokenomics.mdx | 8 +++---- website/pages/ja/subgraphs/billing.mdx | 8 +++---- .../pages/ja/subgraphs/cookbook/arweave.mdx | 4 ++-- .../ja/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/ja/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../ja/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../ja/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/ja/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/ja/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/ja/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ja/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../ja/subgraphs/developing/developer-faq.mdx | 8 +++---- .../ja/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../ja/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/ja/subgraphs/explorer.mdx | 6 ++--- .../ja/subgraphs/querying/best-practices.mdx | 8 +++---- .../ja/subgraphs/querying/graphql-api.mdx | 2 +- .../ja/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/ja/subgraphs/quick-start.mdx | 12 +++++----- website/pages/ja/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/ja/supported-networks.mdx | 2 +- website/pages/ko/about.mdx | 2 +- .../ko/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ko/archived/sunrise.mdx | 6 ++--- website/pages/ko/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../ko/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ko/indexing/overview.mdx | 12 +++++----- website/pages/ko/indexing/tap.mdx | 4 ++-- website/pages/ko/resources/benefits.mdx | 4 ++-- website/pages/ko/resources/roles/curating.mdx | 6 ++--- website/pages/ko/resources/tokenomics.mdx | 8 +++---- website/pages/ko/subgraphs/billing.mdx | 8 +++---- .../pages/ko/subgraphs/cookbook/arweave.mdx | 4 ++-- .../ko/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/ko/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../ko/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../ko/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/ko/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/ko/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/ko/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ko/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../ko/subgraphs/developing/developer-faq.mdx | 8 +++---- .../ko/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../ko/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/ko/subgraphs/explorer.mdx | 6 ++--- .../ko/subgraphs/querying/best-practices.mdx | 8 +++---- .../ko/subgraphs/querying/graphql-api.mdx | 2 +- .../ko/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/ko/subgraphs/quick-start.mdx | 12 +++++----- website/pages/ko/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/ko/supported-networks.mdx | 2 +- website/pages/mr/about.mdx | 2 +- .../mr/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/mr/archived/sunrise.mdx | 6 ++--- website/pages/mr/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../mr/indexing/new-chain-integration.mdx | 4 ++-- website/pages/mr/indexing/overview.mdx | 12 +++++----- website/pages/mr/indexing/tap.mdx | 4 ++-- website/pages/mr/resources/benefits.mdx | 4 ++-- website/pages/mr/resources/roles/curating.mdx | 6 ++--- website/pages/mr/resources/tokenomics.mdx | 8 +++---- website/pages/mr/subgraphs/billing.mdx | 8 +++---- .../pages/mr/subgraphs/cookbook/arweave.mdx | 4 ++-- .../mr/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/mr/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../mr/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../mr/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/mr/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/mr/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/mr/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../mr/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../mr/subgraphs/developing/developer-faq.mdx | 8 +++---- .../mr/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../mr/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/mr/subgraphs/explorer.mdx | 6 ++--- .../mr/subgraphs/querying/best-practices.mdx | 8 +++---- .../mr/subgraphs/querying/graphql-api.mdx | 2 +- .../mr/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/mr/subgraphs/quick-start.mdx | 12 +++++----- website/pages/mr/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/mr/supported-networks.mdx | 2 +- website/pages/nl/about.mdx | 2 +- .../nl/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/nl/archived/sunrise.mdx | 6 ++--- website/pages/nl/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../nl/indexing/new-chain-integration.mdx | 4 ++-- website/pages/nl/indexing/overview.mdx | 12 +++++----- website/pages/nl/indexing/tap.mdx | 4 ++-- website/pages/nl/resources/benefits.mdx | 4 ++-- website/pages/nl/resources/roles/curating.mdx | 6 ++--- website/pages/nl/resources/tokenomics.mdx | 8 +++---- website/pages/nl/subgraphs/billing.mdx | 8 +++---- .../pages/nl/subgraphs/cookbook/arweave.mdx | 4 ++-- .../nl/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/nl/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../nl/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../nl/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/nl/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/nl/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/nl/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../nl/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../nl/subgraphs/developing/developer-faq.mdx | 8 +++---- .../nl/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../nl/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/nl/subgraphs/explorer.mdx | 6 ++--- .../nl/subgraphs/querying/best-practices.mdx | 8 +++---- .../nl/subgraphs/querying/graphql-api.mdx | 2 +- .../nl/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/nl/subgraphs/quick-start.mdx | 12 +++++----- website/pages/nl/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/nl/supported-networks.mdx | 2 +- website/pages/pl/about.mdx | 2 +- .../pl/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/pl/archived/sunrise.mdx | 6 ++--- website/pages/pl/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../pl/indexing/new-chain-integration.mdx | 4 ++-- website/pages/pl/indexing/overview.mdx | 12 +++++----- website/pages/pl/indexing/tap.mdx | 4 ++-- website/pages/pl/resources/benefits.mdx | 4 ++-- website/pages/pl/resources/roles/curating.mdx | 6 ++--- website/pages/pl/resources/tokenomics.mdx | 8 +++---- website/pages/pl/subgraphs/billing.mdx | 8 +++---- .../pages/pl/subgraphs/cookbook/arweave.mdx | 4 ++-- .../pl/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/pl/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../pl/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../pl/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/pl/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/pl/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/pl/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../pl/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../pl/subgraphs/developing/developer-faq.mdx | 8 +++---- .../pl/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../pl/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/pl/subgraphs/explorer.mdx | 6 ++--- .../pl/subgraphs/querying/best-practices.mdx | 8 +++---- .../pl/subgraphs/querying/graphql-api.mdx | 2 +- .../pl/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/pl/subgraphs/quick-start.mdx | 12 +++++----- website/pages/pl/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/pl/supported-networks.mdx | 2 +- website/pages/pt/about.mdx | 2 +- .../pt/archived/arbitrum/arbitrum-faq.mdx | 4 ++-- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/pt/archived/sunrise.mdx | 6 ++--- website/pages/pt/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../pt/indexing/new-chain-integration.mdx | 4 ++-- website/pages/pt/indexing/overview.mdx | 12 +++++----- website/pages/pt/indexing/tap.mdx | 4 ++-- website/pages/pt/resources/benefits.mdx | 4 ++-- website/pages/pt/resources/roles/curating.mdx | 6 ++--- website/pages/pt/resources/tokenomics.mdx | 8 +++---- website/pages/pt/subgraphs/billing.mdx | 8 +++---- .../pages/pt/subgraphs/cookbook/arweave.mdx | 4 ++-- .../pt/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/pt/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../pt/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../pt/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/pt/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/pt/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/pt/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../pt/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../pt/subgraphs/developing/developer-faq.mdx | 8 +++---- .../pt/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../pt/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/pt/subgraphs/explorer.mdx | 6 ++--- .../pt/subgraphs/querying/best-practices.mdx | 8 +++---- .../pt/subgraphs/querying/graphql-api.mdx | 2 +- .../pt/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/pt/subgraphs/quick-start.mdx | 12 +++++----- website/pages/pt/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/pt/supported-networks.mdx | 2 +- website/pages/ro/about.mdx | 2 +- .../ro/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ro/archived/sunrise.mdx | 6 ++--- website/pages/ro/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../ro/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ro/indexing/overview.mdx | 12 +++++----- website/pages/ro/indexing/tap.mdx | 4 ++-- website/pages/ro/resources/benefits.mdx | 4 ++-- website/pages/ro/resources/roles/curating.mdx | 6 ++--- website/pages/ro/resources/tokenomics.mdx | 8 +++---- website/pages/ro/subgraphs/billing.mdx | 8 +++---- .../pages/ro/subgraphs/cookbook/arweave.mdx | 4 ++-- .../ro/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/ro/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../ro/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../ro/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/ro/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/ro/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/ro/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ro/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../ro/subgraphs/developing/developer-faq.mdx | 8 +++---- .../ro/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../ro/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/ro/subgraphs/explorer.mdx | 6 ++--- .../ro/subgraphs/querying/best-practices.mdx | 8 +++---- .../ro/subgraphs/querying/graphql-api.mdx | 2 +- .../ro/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/ro/subgraphs/quick-start.mdx | 12 +++++----- website/pages/ro/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/ro/supported-networks.mdx | 2 +- website/pages/ru/about.mdx | 2 +- .../ru/archived/arbitrum/arbitrum-faq.mdx | 4 ++-- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ru/archived/sunrise.mdx | 6 ++--- website/pages/ru/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../ru/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ru/indexing/overview.mdx | 12 +++++----- website/pages/ru/indexing/tap.mdx | 4 ++-- website/pages/ru/resources/benefits.mdx | 4 ++-- website/pages/ru/resources/roles/curating.mdx | 6 ++--- website/pages/ru/resources/tokenomics.mdx | 8 +++---- website/pages/ru/subgraphs/billing.mdx | 8 +++---- .../pages/ru/subgraphs/cookbook/arweave.mdx | 4 ++-- .../ru/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/ru/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../ru/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../ru/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/ru/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/ru/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/ru/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../ru/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/multiple-networks.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../ru/subgraphs/developing/developer-faq.mdx | 8 +++---- .../ru/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../ru/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/ru/subgraphs/explorer.mdx | 6 ++--- .../ru/subgraphs/querying/best-practices.mdx | 8 +++---- .../ru/subgraphs/querying/graphql-api.mdx | 2 +- .../ru/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/ru/subgraphs/quick-start.mdx | 12 +++++----- website/pages/ru/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/ru/supported-networks.mdx | 2 +- website/pages/sv/about.mdx | 2 +- .../sv/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/sv/archived/sunrise.mdx | 6 ++--- website/pages/sv/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../sv/indexing/new-chain-integration.mdx | 4 ++-- website/pages/sv/indexing/overview.mdx | 12 +++++----- website/pages/sv/indexing/tap.mdx | 4 ++-- website/pages/sv/resources/benefits.mdx | 4 ++-- website/pages/sv/resources/roles/curating.mdx | 6 ++--- website/pages/sv/resources/tokenomics.mdx | 8 +++---- website/pages/sv/subgraphs/billing.mdx | 8 +++---- .../pages/sv/subgraphs/cookbook/arweave.mdx | 4 ++-- .../sv/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/sv/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../sv/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../sv/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/sv/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/sv/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/sv/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../sv/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../sv/subgraphs/developing/developer-faq.mdx | 8 +++---- .../sv/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../sv/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/sv/subgraphs/explorer.mdx | 4 ++-- .../sv/subgraphs/querying/best-practices.mdx | 8 +++---- .../sv/subgraphs/querying/graphql-api.mdx | 2 +- .../sv/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/sv/subgraphs/quick-start.mdx | 12 +++++----- website/pages/sv/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/sv/supported-networks.mdx | 2 +- website/pages/sw/about.mdx | 2 +- .../sw/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/sw/archived/sunrise.mdx | 6 ++--- website/pages/sw/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../sw/indexing/new-chain-integration.mdx | 4 ++-- website/pages/sw/indexing/overview.mdx | 12 +++++----- website/pages/sw/indexing/tap.mdx | 4 ++-- website/pages/sw/resources/benefits.mdx | 4 ++-- website/pages/sw/resources/roles/curating.mdx | 6 ++--- website/pages/sw/resources/tokenomics.mdx | 8 +++---- website/pages/sw/subgraphs/billing.mdx | 8 +++---- .../pages/sw/subgraphs/cookbook/arweave.mdx | 4 ++-- .../sw/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/sw/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../sw/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../sw/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/sw/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/sw/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/sw/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../sw/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../sw/subgraphs/developing/developer-faq.mdx | 8 +++---- .../sw/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../sw/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/sw/subgraphs/explorer.mdx | 6 ++--- .../sw/subgraphs/querying/best-practices.mdx | 8 +++---- .../sw/subgraphs/querying/graphql-api.mdx | 2 +- .../sw/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/sw/subgraphs/quick-start.mdx | 12 +++++----- website/pages/sw/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/sw/supported-networks.mdx | 2 +- website/pages/tr/about.mdx | 2 +- .../tr/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/tr/archived/sunrise.mdx | 6 ++--- website/pages/tr/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../tr/indexing/new-chain-integration.mdx | 4 ++-- website/pages/tr/indexing/overview.mdx | 12 +++++----- website/pages/tr/indexing/tap.mdx | 4 ++-- website/pages/tr/resources/benefits.mdx | 4 ++-- website/pages/tr/resources/roles/curating.mdx | 6 ++--- website/pages/tr/resources/tokenomics.mdx | 8 +++---- website/pages/tr/subgraphs/billing.mdx | 8 +++---- .../pages/tr/subgraphs/cookbook/arweave.mdx | 4 ++-- .../tr/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/tr/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../tr/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../tr/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/tr/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/tr/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/tr/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../tr/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../tr/subgraphs/developing/developer-faq.mdx | 8 +++---- .../tr/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../tr/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/tr/subgraphs/explorer.mdx | 6 ++--- .../tr/subgraphs/querying/best-practices.mdx | 8 +++---- .../tr/subgraphs/querying/graphql-api.mdx | 2 +- .../tr/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/tr/subgraphs/quick-start.mdx | 12 +++++----- website/pages/tr/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/tr/supported-networks.mdx | 2 +- website/pages/uk/about.mdx | 2 +- .../uk/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/uk/archived/sunrise.mdx | 6 ++--- website/pages/uk/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../uk/indexing/new-chain-integration.mdx | 4 ++-- website/pages/uk/indexing/overview.mdx | 12 +++++----- website/pages/uk/indexing/tap.mdx | 4 ++-- website/pages/uk/resources/benefits.mdx | 4 ++-- website/pages/uk/resources/roles/curating.mdx | 6 ++--- website/pages/uk/resources/tokenomics.mdx | 8 +++---- website/pages/uk/subgraphs/billing.mdx | 8 +++---- .../pages/uk/subgraphs/cookbook/arweave.mdx | 4 ++-- .../uk/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/uk/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../uk/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../uk/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/uk/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/uk/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/uk/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../uk/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../uk/subgraphs/developing/developer-faq.mdx | 8 +++---- .../uk/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../uk/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/uk/subgraphs/explorer.mdx | 6 ++--- .../uk/subgraphs/querying/best-practices.mdx | 8 +++---- .../uk/subgraphs/querying/graphql-api.mdx | 2 +- .../uk/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/uk/subgraphs/quick-start.mdx | 12 +++++----- website/pages/uk/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/uk/supported-networks.mdx | 2 +- website/pages/ur/about.mdx | 2 +- .../ur/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/ur/archived/sunrise.mdx | 6 ++--- website/pages/ur/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../ur/indexing/new-chain-integration.mdx | 4 ++-- website/pages/ur/indexing/overview.mdx | 12 +++++----- website/pages/ur/indexing/tap.mdx | 4 ++-- website/pages/ur/resources/benefits.mdx | 4 ++-- website/pages/ur/resources/roles/curating.mdx | 6 ++--- website/pages/ur/resources/tokenomics.mdx | 8 +++---- website/pages/ur/subgraphs/billing.mdx | 8 +++---- .../pages/ur/subgraphs/cookbook/arweave.mdx | 4 ++-- .../ur/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/ur/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../ur/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../ur/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/ur/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/ur/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/ur/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 2 +- .../ur/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../ur/subgraphs/developing/developer-faq.mdx | 8 +++---- .../ur/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../ur/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/ur/subgraphs/explorer.mdx | 6 ++--- .../ur/subgraphs/querying/best-practices.mdx | 8 +++---- .../ur/subgraphs/querying/graphql-api.mdx | 2 +- .../ur/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/ur/subgraphs/quick-start.mdx | 12 +++++----- website/pages/ur/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/ur/supported-networks.mdx | 2 +- website/pages/vi/about.mdx | 2 +- .../vi/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-faq.mdx | 2 +- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/vi/archived/sunrise.mdx | 6 ++--- website/pages/vi/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../vi/indexing/new-chain-integration.mdx | 4 ++-- website/pages/vi/indexing/overview.mdx | 12 +++++----- website/pages/vi/indexing/tap.mdx | 4 ++-- website/pages/vi/resources/benefits.mdx | 4 ++-- website/pages/vi/resources/roles/curating.mdx | 6 ++--- website/pages/vi/resources/tokenomics.mdx | 8 +++---- website/pages/vi/subgraphs/billing.mdx | 8 +++---- .../pages/vi/subgraphs/cookbook/arweave.mdx | 4 ++-- .../vi/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/vi/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../vi/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../vi/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/vi/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/vi/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/vi/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../vi/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 4 ++-- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../vi/subgraphs/developing/developer-faq.mdx | 8 +++---- .../vi/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../vi/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/vi/subgraphs/explorer.mdx | 6 ++--- .../vi/subgraphs/querying/best-practices.mdx | 8 +++---- .../vi/subgraphs/querying/graphql-api.mdx | 2 +- .../vi/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/vi/subgraphs/quick-start.mdx | 12 +++++----- website/pages/vi/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/vi/supported-networks.mdx | 2 +- website/pages/zh/about.mdx | 2 +- .../zh/archived/arbitrum/arbitrum-faq.mdx | 6 ++--- .../arbitrum/l2-transfer-tools-guide.mdx | 2 +- website/pages/zh/archived/sunrise.mdx | 6 ++--- website/pages/zh/contracts.mdx | 2 +- .../indexing/chain-integration-overview.mdx | 2 +- .../zh/indexing/new-chain-integration.mdx | 4 ++-- website/pages/zh/indexing/overview.mdx | 12 +++++----- website/pages/zh/indexing/tap.mdx | 4 ++-- website/pages/zh/resources/benefits.mdx | 4 ++-- website/pages/zh/resources/roles/curating.mdx | 6 ++--- website/pages/zh/resources/tokenomics.mdx | 8 +++---- website/pages/zh/subgraphs/billing.mdx | 8 +++---- .../pages/zh/subgraphs/cookbook/arweave.mdx | 4 ++-- .../zh/subgraphs/cookbook/avoid-eth-calls.mdx | 12 +++++----- .../pages/zh/subgraphs/cookbook/cosmos.mdx | 4 ++-- .../zh/subgraphs/cookbook/derivedfrom.mdx | 14 ++++++------ .../zh/subgraphs/cookbook/grafting-hotfix.mdx | 16 +++++++------- .../pages/zh/subgraphs/cookbook/grafting.mdx | 4 ++-- .../immutable-entities-bytes-as-ids.mdx | 12 +++++----- website/pages/zh/subgraphs/cookbook/near.mdx | 12 +++++----- .../pages/zh/subgraphs/cookbook/pruning.mdx | 18 +++++++-------- .../cookbook/substreams-powered-subgraphs.mdx | 4 ++-- .../zh/subgraphs/cookbook/timeseries.mdx | 12 +++++----- .../cookbook/transfer-to-the-graph.mdx | 12 +++++----- .../developing/creating/advanced.mdx | 8 +++---- .../developing/creating/graph-ts/api.mdx | 2 +- .../developing/creating/install-the-cli.mdx | 6 ++--- .../developing/creating/ql-schema.mdx | 4 ++-- .../creating/starting-your-subgraph.mdx | 12 +++++----- .../developing/creating/subgraph-manifest.mdx | 6 ++--- .../creating/unit-testing-framework.mdx | 2 +- .../deploying/using-subgraph-studio.mdx | 8 +++---- .../zh/subgraphs/developing/developer-faq.mdx | 8 +++---- .../zh/subgraphs/developing/introduction.mdx | 4 ++-- .../publishing/publishing-a-subgraph.mdx | 16 +++++++------- .../zh/subgraphs/developing/subgraphs.mdx | 18 +++++++-------- website/pages/zh/subgraphs/explorer.mdx | 6 ++--- .../zh/subgraphs/querying/best-practices.mdx | 8 +++---- .../zh/subgraphs/querying/graphql-api.mdx | 2 +- .../zh/subgraphs/querying/introduction.mdx | 6 ++--- website/pages/zh/subgraphs/quick-start.mdx | 12 +++++----- website/pages/zh/substreams/sps/sps-faq.mdx | 10 ++++----- website/pages/zh/supported-networks.mdx | 2 +- website/src/IndexPage.tsx | 22 +++++++++---------- 1044 files changed, 3856 insertions(+), 3855 deletions(-) diff --git a/nginx.conf b/nginx.conf index 0582c6da2396..aa9a39ae2418 100644 --- a/nginx.conf +++ b/nginx.conf @@ -78,6 +78,7 @@ http { rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/subgraph-studio-faqs/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/subgraph-studio-faq/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/deploying/subgraph-studio/$ $scheme://$http_host/docs/$1/subgraphs/developing/deploying/using-subgraph-studio/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/assemblyscript-api/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/graph-ts/api/ permanent; + rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/starting-your-subgraph/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/starting-your-subgraph/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/starting-your-subgraph/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/install-the-cli/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/install-the-cli/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/creating-a-subgraph/ql-schema/$ $scheme://$http_host/docs/$1/subgraphs/developing/creating/ql-schema/ permanent; diff --git a/website/pages/[locale]/index.mdx b/website/pages/[locale]/index.mdx index 03c25f78ccbb..d315a3c874ab 100644 --- a/website/pages/[locale]/index.mdx +++ b/website/pages/[locale]/index.mdx @@ -35,7 +35,7 @@ ${t('index.networkRoles.description')} ## ${t('index.supportedNetworks.title')} ${t('index.supportedNetworks.description')} -${t('index.supportedNetworks.footer').replace('{0}', `[${t('index.supportedNetworks.title')}](/developing/supported-networks/)`)}` +${t('index.supportedNetworks.footer').replace('{0}', `[${t('index.supportedNetworks.title')}](/supported-networks/)`)}` const mdx = await buildDynamicMDX(rawMdx, { codeHighlight: false }) return { props: { diff --git a/website/pages/ar/about.mdx b/website/pages/ar/about.mdx index 7660b0dfd54b..8005f34aef5f 100644 --- a/website/pages/ar/about.mdx +++ b/website/pages/ar/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/ar/archived/arbitrum/arbitrum-faq.mdx b/website/pages/ar/archived/arbitrum/arbitrum-faq.mdx index 2cf8402a7718..ea4e5f0b2872 100644 --- a/website/pages/ar/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/ar/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Once you have GRT on Arbitrum, you can add it to your billing balance. ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx index 250f550bcacd..9c1e9fa8db64 100644 --- a/website/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/ar/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### هل يمكنني استخدام نفس المحفظة التي استخدمها في Ethereum mainnet؟ -إذا كنت تستخدم محفظة [EOA] (https://ethereum.org/en/developers/docs/accounts/#types-of-account) ، فيمكنك استخدام نفس العنوان. إذا كانت محفظة Ethereum mainnet الخاصة بك عبارة عن عقد (مثل multisig) ، فيجب عليك تحديد [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) حيث سيتم إرسال التحويل الخاص بك. يرجى التحقق من العنوان بعناية لأن أي تحويلات إلى عنوان غير صحيح يمكن أن تؤدي إلى خسارة غير قابلة للرجوع. إذا كنت ترغب في استخدام multisig على L2 ، فتأكد من نشر عقد multisig على Arbitrum One. +إذا كنت تستخدم محفظة [EOA] (https://ethereum.org/en/developers/docs/accounts/#types-of-account) ، فيمكنك استخدام نفس العنوان. إذا كانت محفظة Ethereum mainnet الخاصة بك عبارة عن عقد (مثل multisig) ، فيجب عليك تحديد [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) حيث سيتم إرسال التحويل الخاص بك. يرجى التحقق من العنوان بعناية لأن أي تحويلات إلى عنوان غير صحيح يمكن أن تؤدي إلى خسارة غير قابلة للرجوع. إذا كنت ترغب في استخدام multisig على L2 ، فتأكد من نشر عقد multisig على Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx index 33b5b1628783..ed881d8de079 100644 --- a/website/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ar/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide يسهل الغراف الانتقال إلى الطبقة الثانبة على أربترم. لكل مشارك في البروتوكول ، توجد مجموعة من أدوات نقل الطبقة الثانبة لجعل النقل إليها سلسًا لجميع المشاركين في الشبكة. ستطلب منك هذه الأدوات اتباع مجموعة محددة من الخطوات بناءً على ما تقوم بنقله. -بعض الأسئلة المتكررة حول هذه الأدوات تمت الإجابة عليها في [الأسئلة الشائعة حول أدوات نقل الطبقة الثانية] (/arbitrum/l2-transfer-tools-faq). تحتوي الأسئلة الشائعة على تفسيرات متعمقة لكيفية استخدام الأدوات وكيفية عملها والأمور التي يجب وضعها في الاعتبار عند إستخدامها. +بعض الأسئلة المتكررة حول هذه الأدوات تمت الإجابة عليها في [الأسئلة الشائعة حول أدوات نقل الطبقة الثانية] (/archived/arbitrum/l2-transfer-tools-faq/). تحتوي الأسئلة الشائعة على تفسيرات متعمقة لكيفية استخدام الأدوات وكيفية عملها والأمور التي يجب وضعها في الاعتبار عند إستخدامها. ## كيف تنقل الغراف الفرعي الخاص بك إلى شبكة آربترم (الطبقة الثانية) diff --git a/website/pages/ar/archived/sunrise.mdx b/website/pages/ar/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/ar/archived/sunrise.mdx +++ b/website/pages/ar/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ar/contracts.mdx b/website/pages/ar/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/ar/contracts.mdx +++ b/website/pages/ar/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ar/indexing/chain-integration-overview.mdx b/website/pages/ar/indexing/chain-integration-overview.mdx index 458e5a4f54f7..e6b95ec0fc17 100644 --- a/website/pages/ar/indexing/chain-integration-overview.mdx +++ b/website/pages/ar/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: نظرة عامة حول عملية التكامل مع الشبكة ## المرحلة الأولى: التكامل التقني -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - تستهل الفرق عملية التكامل مع البروتوكول من خلال إنشاء موضوع في المنتدى هنا(https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (الفئة الفرعية "مصادر البيانات الجديدة" تحت قسم "الحوكمة واقتراحات تحسين الغراف"). استخدام قالب المنتدى الافتراضي إلزامي. ## المرحلة الثانية: التحقق من صحة التكامل diff --git a/website/pages/ar/indexing/new-chain-integration.mdx b/website/pages/ar/indexing/new-chain-integration.mdx index 28165d622980..90fd989fffce 100644 --- a/website/pages/ar/indexing/new-chain-integration.mdx +++ b/website/pages/ar/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Configuring Graph Node is as easy as preparing your local environment. Once your ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ar/indexing/overview.mdx b/website/pages/ar/indexing/overview.mdx index 526bb472cee1..060c87662a3c 100644 --- a/website/pages/ar/indexing/overview.mdx +++ b/website/pages/ar/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### ابدأ -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### من حزم NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### استخدام K8s و Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### الاستخدام @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### اعتماد التوكن tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/ar/indexing/tap.mdx b/website/pages/ar/indexing/tap.mdx index 0cef5f4209fa..cc523ded6384 100644 --- a/website/pages/ar/indexing/tap.mdx +++ b/website/pages/ar/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/ar/resources/benefits.mdx b/website/pages/ar/resources/benefits.mdx index 83a655314638..d1284dce22f1 100644 --- a/website/pages/ar/resources/benefits.mdx +++ b/website/pages/ar/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/ar/resources/roles/curating.mdx b/website/pages/ar/resources/roles/curating.mdx index a681000aa7e5..70d716d5e5e4 100644 --- a/website/pages/ar/resources/roles/curating.mdx +++ b/website/pages/ar/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## كيفية الإشارة -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) يمكن للمنسق الإشارة إلى إصدار معين ل subgraph ، أو يمكنه اختيار أن يتم ترحيل migrate إشاراتهم تلقائيا إلى أحدث إصدار لهذا ال subgraph. كلاهما استراتيجيات سليمة ولها إيجابيات وسلبيات. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. سوق الاستعلام يعتبر حديثا في The Graph وهناك خطر من أن يكون٪ APY الخاص بك أقل مما تتوقع بسبب ديناميكيات السوق الناشئة. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. يمكن أن يفشل ال subgraph بسبب خطأ. ال subgraph الفاشل لا يمكنه إنشاء رسوم استعلام. نتيجة لذلك ، سيتعين عليك الانتظار حتى يصلح المطور الخطأ وينشر إصدارا جديدا. - إذا كنت مشتركا في أحدث إصدار من subgraph ، فسيتم ترحيل migrate أسهمك تلقائيا إلى هذا الإصدار الجديد. هذا سيتحمل ضريبة تنسيق بنسبة 0.5٪. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ar/resources/tokenomics.mdx b/website/pages/ar/resources/tokenomics.mdx index 049df2b7f086..1afdc3ccf913 100644 --- a/website/pages/ar/resources/tokenomics.mdx +++ b/website/pages/ar/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### الاستعلام عن subgraph موجود -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/ar/subgraphs/billing.mdx b/website/pages/ar/subgraphs/billing.mdx index 42aa104673bb..ec5472fac4f2 100644 --- a/website/pages/ar/subgraphs/billing.mdx +++ b/website/pages/ar/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. انقر على زر "توصيل المحفظة" في الزاوية اليمنى العليا من الصفحة. ستتم إعادة توجيهك إلى صفحة اختيار المحفظة. حدد محفظتك وانقر على "توصيل". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. انقر على زر "توصيل المحفظة" في الزاوية اليمنى العليا من الصفحة. ستتم إعادة توجيهك إلى صفحة اختيار المحفظة. حدد محفظتك وانقر على "توصيل". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### إضافة GRT باستخدام محفظة متعددة التوقيع (multisig wallet) -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/ar/subgraphs/cookbook/arweave.mdx b/website/pages/ar/subgraphs/cookbook/arweave.mdx index 06fe4729bf4b..e2b5d3a37e04 100644 --- a/website/pages/ar/subgraphs/cookbook/arweave.mdx +++ b/website/pages/ar/subgraphs/cookbook/arweave.mdx @@ -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/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## أمثلة على الـ Subgraphs diff --git a/website/pages/ar/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/ar/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/ar/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/ar/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ar/subgraphs/cookbook/cosmos.mdx b/website/pages/ar/subgraphs/cookbook/cosmos.mdx index 15fbf0537bca..64a91ecbc917 100644 --- a/website/pages/ar/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/ar/subgraphs/cookbook/cosmos.mdx @@ -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/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/ar/subgraphs/cookbook/derivedfrom.mdx b/website/pages/ar/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/ar/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/ar/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ar/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/ar/subgraphs/cookbook/grafting-hotfix.mdx index b7699bf2bc85..2bbe296c724a 100644 --- a/website/pages/ar/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/ar/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## مصادر إضافية -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ar/subgraphs/cookbook/grafting.mdx b/website/pages/ar/subgraphs/cookbook/grafting.mdx index 9f965cbf2814..bfbe1c2a19d9 100644 --- a/website/pages/ar/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ar/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/ar/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ar/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/ar/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/ar/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ar/subgraphs/cookbook/near.mdx b/website/pages/ar/subgraphs/cookbook/near.mdx index 87505b21adb9..fe6cbf2223aa 100644 --- a/website/pages/ar/subgraphs/cookbook/near.mdx +++ b/website/pages/ar/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## نشر NEAR Subgraph @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 = 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ar/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ar/subgraphs/cookbook/timeseries.mdx b/website/pages/ar/subgraphs/cookbook/timeseries.mdx index a6402c800725..03ac4f323fa4 100644 --- a/website/pages/ar/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/ar/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ar/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/ar/subgraphs/cookbook/transfer-to-the-graph.mdx index 5c0446fa7fda..375f82097493 100644 --- a/website/pages/ar/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/ar/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### مثال @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### مصادر إضافية -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/ar/subgraphs/developing/creating/advanced.mdx b/website/pages/ar/subgraphs/developing/creating/advanced.mdx index 04984ebb31a6..243ad181d478 100644 --- a/website/pages/ar/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/ar/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting على Subgraphs موجودة -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/ar/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ar/subgraphs/developing/creating/graph-ts/api.mdx index e69137f06cb3..7c6e468b79fc 100644 --- a/website/pages/ar/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ar/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx index b18e9aa8f7fb..76c1d923b417 100644 --- a/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ar/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: قم بتثبيت Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## نظره عامة -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx index 4a7e49aaa5a6..cc8e54d39e64 100644 --- a/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ar/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ar/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/ar/subgraphs/developing/creating/starting-your-subgraph.mdx index f48efba92d85..37c6b4029005 100644 --- a/website/pages/ar/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/ar/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/ar/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/ar/subgraphs/developing/creating/subgraph-manifest.mdx index 8c36c56b624a..16d13269fb85 100644 --- a/website/pages/ar/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/ar/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). الإدخالات الهامة لتحديث manifest هي: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/ar/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/ar/subgraphs/developing/creating/unit-testing-framework.mdx index d123dc0f994b..854e4750cbce 100644 --- a/website/pages/ar/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/ar/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx index d626c7abbb22..835ed254af64 100644 --- a/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ar/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### توافق الـ Subgraph مع شبكة The Graph In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - يجب ألا تستخدم أيًا من الميزات التالية: - ipfs.cat & ipfs.map - أخطاء غير فادحة @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## الأرشفة التلقائية لإصدارات الـ Subgraph diff --git a/website/pages/ar/subgraphs/developing/developer-faq.mdx b/website/pages/ar/subgraphs/developing/developer-faq.mdx index 423e9f9561b7..c740d2680695 100644 --- a/website/pages/ar/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ar/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You can deploy a new version of your subgraph to Subgraph Studio using the CLI. ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ docker pull graphprotocol/graph-node:latest ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/ar/subgraphs/developing/introduction.mdx b/website/pages/ar/subgraphs/developing/introduction.mdx index 6f456be01c17..b4d79001819a 100644 --- a/website/pages/ar/subgraphs/developing/introduction.mdx +++ b/website/pages/ar/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## نظره عامة @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 7fcaff59788d..def875755910 100644 --- a/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ar/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/ar/subgraphs/developing/subgraphs.mdx b/website/pages/ar/subgraphs/developing/subgraphs.mdx index d770a7cb9c57..b17505d7ebad 100644 --- a/website/pages/ar/subgraphs/developing/subgraphs.mdx +++ b/website/pages/ar/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/ar/subgraphs/explorer.mdx b/website/pages/ar/subgraphs/explorer.mdx index d9b262805cca..0f48c1190159 100644 --- a/website/pages/ar/subgraphs/explorer.mdx +++ b/website/pages/ar/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![نافذة تفاصيل الفهرسة](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![صورة المستكشف 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. المفوضون Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - كمية ال GRT التي يمتلكونها حاليا في البروتوكول - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/ar/subgraphs/querying/best-practices.mdx b/website/pages/ar/subgraphs/querying/best-practices.mdx index 0b34069dbd23..7e465d41a7f0 100644 --- a/website/pages/ar/subgraphs/querying/best-practices.mdx +++ b/website/pages/ar/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - يجب استخدام كل `queryName` مرة واحدة فقط لكل عملية. - يجب استخدام كل `field` مرة واحدة فقط في التحديد (لا يمكننا الاستعلام عن `id` مرتين ضمن `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - يجب أن يكون أي متغير تم تعيينه لوسيط متطابقًا مع نوعه. - في قائمة المتغيرات المعطاة ، يجب أن يكون كل واحد منها فريدًا. - يجب استخدام جميع المتغيرات المحددة. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### إرسال استعلام إلى GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - التعامل مع ال subgraph عبر السلاسل: الاستعلام من عدة subgraphs عبر استعلام واحد - [تتبع الكتلة التلقائي](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/ar/subgraphs/querying/graphql-api.mdx b/website/pages/ar/subgraphs/querying/graphql-api.mdx index 3246e4ab97d6..48d139de77fd 100644 --- a/website/pages/ar/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ar/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/ar/subgraphs/querying/introduction.mdx b/website/pages/ar/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/ar/subgraphs/querying/introduction.mdx +++ b/website/pages/ar/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/ar/subgraphs/quick-start.mdx b/website/pages/ar/subgraphs/quick-start.mdx index 8a52663bfc8c..0c5cde32121a 100644 --- a/website/pages/ar/subgraphs/quick-start.mdx +++ b/website/pages/ar/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: بداية سريعة --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## المتطلبات الأساسية - محفظة عملات رقمية -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/ar/substreams/sps/sps-faq.mdx b/website/pages/ar/substreams/sps/sps-faq.mdx index 9795fb40f711..124d364afbc0 100644 --- a/website/pages/ar/substreams/sps/sps-faq.mdx +++ b/website/pages/ar/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -اذهب إلى [وثائق سبستريمز](/substreams/) للتعرف على المزيد حول سبستريمز. +اذهب إلى [وثائق سبستريمز](/substreams/introduction/) للتعرف على المزيد حول سبستريمز. ## ما هي الغرافات الفرعية المدعومة بسبستريمز؟ -[الغرافات الفرعية المدعومة بسبستريمز](/cookbook/substreams-powered-subgraphs/) تجمع بين قوة سبستريمز وقابلية الاستعلام للغرافات الفرعية. عند نشر غراف فرعي مدعوم بواسطة سبستريمز، يمكن أن تنتج البيانات التي تم إنتاجها بواسطة تحويلات سبستريمز، تغييرات في الكيانات (https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs)، والتي تكون متوافقة مع كيانات الغرافات الفرعية. +[الغرافات الفرعية المدعومة بسبستريمز](/subgraphs/cookbook/substreams-powered-subgraphs/) تجمع بين قوة سبستريمز وقابلية الاستعلام للغرافات الفرعية. عند نشر غراف فرعي مدعوم بواسطة سبستريمز، يمكن أن تنتج البيانات التي تم إنتاجها بواسطة تحويلات سبستريمز، تغييرات في الكيانات (https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs)، والتي تكون متوافقة مع كيانات الغرافات الفرعية. إذا كنت على دراية بتطوير الغراف الفرعي، فإن الغرافات الفرعية المدعومة بواسطة سبستريمز يمكن استعلامها بنفس الطريقة كما لو أنها تم إنتاجها بواسطة طبقة تحويل لغة أسيمبلي اسكريبت، بالإضافة إلى جميع فوائد الغراف الفرعي، مثل توفير واجهة برمجة تطبيقات ديناميكية ومرنة للغة استعلام الغراف. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## أين يمكن للمطورين الوصول إلى مزيد من المعلومات حول الغرافات الفرعية المدعومة بسبستريمز و سبستريمز؟ -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -ستوضح لك [وثائق الغرافات الفرعية المدعومة بواسطة سبستريمز](/cookbook/substreams-powered-subgraphs/) كيفية تجميعها للنشر على الغراف. +ستوضح لك [وثائق الغرافات الفرعية المدعومة بواسطة سبستريمز](/subgraphs/cookbook/substreams-powered-subgraphs/) كيفية تجميعها للنشر على الغراف. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ When using Substreams, the composition happens at the transformation layer enabl ## كيف يمكنك إنشاء ونشر غراف فرعي مدعوم بسبستريمز؟ -بعد [تعريف](/cookbook/substreams-powered-subgraphs/) الغراف الفرعي مدعوم بالسبستريمز، يمكنك استخدام واجهة سطر الأوامر للغراف لنشره في [استوديو الغراف الفرعي](https://thegraph.com/studio/). +بعد [تعريف](/subgraphs/cookbook/substreams-powered-subgraphs/) الغراف الفرعي مدعوم بالسبستريمز، يمكنك استخدام واجهة سطر الأوامر للغراف لنشره في [استوديو الغراف الفرعي](https://thegraph.com/studio/). ## أين يمكنني العثور على أمثلة على سبستريمز والغرافات الفرعية المدعومة بسبستريمز؟ diff --git a/website/pages/ar/supported-networks.mdx b/website/pages/ar/supported-networks.mdx index 8b90e2232f92..ef82e9b6f46e 100644 --- a/website/pages/ar/supported-networks.mdx +++ b/website/pages/ar/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/cs/about.mdx b/website/pages/cs/about.mdx index e29bcf5fe650..256519660a73 100644 --- a/website/pages/cs/about.mdx +++ b/website/pages/cs/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/cs/archived/arbitrum/arbitrum-faq.mdx b/website/pages/cs/archived/arbitrum/arbitrum-faq.mdx index 486e371b527d..56c377bdfe10 100644 --- a/website/pages/cs/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/cs/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Pro využití výhod používání a Graf na L2 použijte rozevírací přepína ## Jako vývojář podgrafů, Spotřebitel dat, indexer, kurátor, nebo delegátor, co mám nyní udělat? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Vše bylo důkladně otestováno, a je připraven pohotovostní plán, který za ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ Most byl [podroben důkladnému auditu](https://code4rena.com/contests/2022-10-t Přidání GRT do vašeho zúčtovacího zůstatku Arbitrum lze provést jedním kliknutím v aplikaci [Subgraph Studio](https://thegraph.com/studio/). Budete moci snadno propojit své GRT s Arbitrum a vyplnit své klíče API v rámci jedné transakce. -Podrobnější pokyny k přidávání, odebírání nebo získávání GRT najdete na stránce [Billing page](/billing/). +Podrobnější pokyny k přidávání, odebírání nebo získávání GRT najdete na stránce [Billing page](/subgraphs/billing/). diff --git a/website/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx index bf1ce305641f..4d091bbf91e7 100644 --- a/website/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/cs/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ Tyto nástroje vyžadují, abyste provedli určitý soubor kroků v závislosti ### Mohu používat stejnou peněženku, kterou používám na mainnet Ethereum? -Pokud používáte peněženku [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), můžete použít stejnou adresu. Pokud je vaše peněženka Ethereum mainnet kontraktem (např. multisig), musíte zadat adresu [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2), kam bude váš převod odeslán. Pečlivě zkontrolujte adresu, protože převody na nesprávnou adresu mohou mít za následek trvalou ztrátu. Pokud chcete používat multisig na L2, ujistěte se, že jste nasadili multisig smlouvu na Arbitrum One. +Pokud používáte peněženku [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), můžete použít stejnou adresu. Pokud je vaše peněženka Ethereum mainnet kontraktem (např. multisig), musíte zadat adresu [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2), kam bude váš převod odeslán. Pečlivě zkontrolujte adresu, protože převody na nesprávnou adresu mohou mít za následek trvalou ztrátu. Pokud chcete používat multisig na L2, ujistěte se, že jste nasadili multisig smlouvu na Arbitrum One. Peněženky na blockchainech EVM, jako jsou Ethereum a Arbitrum, představují dvojici klíčů (veřejný a soukromý), které vytvoříte bez nutnosti interakce s blockchainem. Takže jakákoli peněženka vytvořená pro Ethereum bude fungovat i pro Arbitrum, aniž byste museli dělat cokoli jiného. diff --git a/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx index 339b86f84237..ea6a1ef3bf98 100644 --- a/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/cs/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Průvodce nástroji pro přenos L2 Graph usnadnil přechod na úroveň L2 v Arbitrum One. Pro každého účastníka protokolu je k dispozici sada nástrojů pro přechod na L2, které umožňují bezproblémový přechod na L2 pro všechny účastníky sítě. Tyto nástroje vyžadují provedení určitého souboru kroků v závislosti na tom, co přenášíte. -Některé časté otázky týkající se těchto nástrojů jsou zodpovězeny v sekci [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). Často kladené dotazy obsahují podrobné vysvětlení, jak nástroje používat, jak fungují a na co je třeba při jejich používání pamatovat. +Některé časté otázky týkající se těchto nástrojů jsou zodpovězeny v sekci [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). Často kladené dotazy obsahují podrobné vysvětlení, jak nástroje používat, jak fungují a na co je třeba při jejich používání pamatovat. ## Jak přenést podgraf do Arbitrum (L2) diff --git a/website/pages/cs/archived/sunrise.mdx b/website/pages/cs/archived/sunrise.mdx index ad98758ce3ff..c1fd503ed6f4 100644 --- a/website/pages/cs/archived/sunrise.mdx +++ b/website/pages/cs/archived/sunrise.mdx @@ -22,7 +22,7 @@ Ne, na Podgraf Studio neměl Sunrise vliv. Podgrafy byly okamžitě k dispozici ### Proč byly podgrafy zveřejněny na Arbitrum, začalo indexovat jinou síť? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## O Upgrade Indexer @@ -33,7 +33,7 @@ Upgrade Indexer byl implementován za účelem zlepšení zkušeností s upgrade ### Co dělá upgrade Indexer? - Zavádí řetězce, které ještě nezískaly odměnu za indexaci v síti Graf, a zajišťuje, aby byl po zveřejnění podgrafu co nejrychleji k dispozici indexátor pro obsluhu dotazů. -- Podporuje řetězce, které byly dříve dostupné pouze v hostované službě. Úplný seznam podporovaných řetězců najdete [zde](/developing/supported-networks/). +- Podporuje řetězce, které byly dříve dostupné pouze v hostované službě. Úplný seznam podporovaných řetězců najdete [zde](/supported-networks/). - Indexátoři, kteří provozují upgrade indexátoru, tak činí jako veřejnou službu pro podporu nových podgrafů a dalších řetězců, kterým chybí indexační odměny, než je Rada grafů schválí. ### Proč Edge & Node spouští aktualizaci Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/cs/contracts.mdx b/website/pages/cs/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/cs/contracts.mdx +++ b/website/pages/cs/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/cs/indexing/chain-integration-overview.mdx b/website/pages/cs/indexing/chain-integration-overview.mdx index 6252d43dc36a..e048421d7ad9 100644 --- a/website/pages/cs/indexing/chain-integration-overview.mdx +++ b/website/pages/cs/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Pro blockchainové týmy, které usilují o [integraci s protokolem The Graph](h ## Fáze 1. Technická integrace -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Týmy zahájí proces integrace protokolu vytvořením vlákna na fóru [zde](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (podkategorie Nové zdroje dat v části Správa a GIP). Použití výchozí šablony Fóra je povinné. ## Fáze 2. Ověřování integrace diff --git a/website/pages/cs/indexing/new-chain-integration.mdx b/website/pages/cs/indexing/new-chain-integration.mdx index 6cd08079845c..082548e9e502 100644 --- a/website/pages/cs/indexing/new-chain-integration.mdx +++ b/website/pages/cs/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Pokud nedošlo k chybám, měl by uzel Graf synchronizovat nasazený podgraf. De ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/cs/indexing/overview.mdx b/website/pages/cs/indexing/overview.mdx index 1c933a2adbb5..cacdc85fea39 100644 --- a/website/pages/cs/indexing/overview.mdx +++ b/website/pages/cs/indexing/overview.mdx @@ -87,7 +87,7 @@ Po uzavření přídělu může indexátor požádat o slevy. Po uplatnění ná ### Co je to snížení poplatku za dotaz a snížení odměny za indexaci? -Hodnoty `queryFeeCut` a `indexingRewardCut` jsou parametry delegování, které může indexátor nastavit spolu s bloky cooldownBlocks a řídit tak rozdělení GRT mezi indexátor a jeho delegáty. Pokyny k nastavení parametrů delegování naleznete v posledních krocích v části [Zadání protokolu](/network/indexing/#stake-in-the-protocol). +Hodnoty `queryFeeCut` a `indexingRewardCut` jsou parametry delegování, které může indexátor nastavit spolu s bloky cooldownBlocks a řídit tak rozdělení GRT mezi indexátor a jeho delegáty. Pokyny k nastavení parametrů delegování naleznete v posledních krocích v části [Zadání protokolu](/indexing/overview/#stake-in-the-protocol). - **queryFeeCut** - % slev z poplatků za dotaz, které budou rozděleny mezi indexátory. Pokud je tato hodnota nastavena na 95%, obdrží indexátor 95% poplatků za dotaz získaných při uzavření přídělu a zbylých 5% připadne delegátům. @@ -121,7 +121,7 @@ Indexátory se mohou odlišovat použitím pokročilých technik pro rozhodován ### Jaká jsou základní bezpečnostní opatření, která by měl indexátor přijmout? -- **Peněženka operátora** - Nastavení peněženky operátora je důležitým opatřením, protože umožňuje indexátorovi udržovat oddělení mezi klíči, které kontrolují sázky, a klíči, které řídí každodenní operace. Pokyny naleznete v části [Podíl na protokolu](/network/indexing/#stake-in-the-protocol). +- **Peněženka operátora** - Nastavení peněženky operátora je důležitým opatřením, protože umožňuje indexátorovi udržovat oddělení mezi klíči, které kontrolují sázky, a klíči, které řídí každodenní operace. Pokyny naleznete v části [Podíl na protokolu](/indexing/overview/#stake-in-the-protocol). - **Firewall** - Pouze služba Indexer musí být vystavena veřejně a zvláštní pozornost by měla být věnována uzamčení portů pro správu a přístupu k databázi: koncový bod JSON-RPC uzlu Graf (výchozí port: 8030), koncový bod API pro správu Indexeru (výchozí port: 18000) a koncový bod databáze Postgres (výchozí port: 5432) by neměly být vystaveny. @@ -375,7 +375,7 @@ docker-compose up #### Začínáme -Agent Indexer a služba Indexer by měly být umístěny společně s infrastrukturou graf uzlu. Existuje mnoho způsobů, jak nastavit virtuální prováděcí prostředí pro komponenty Indexer; zde vysvětlíme, jak je spustit na baremetalu pomocí balíčků NPM nebo zdrojových kódů, nebo pomocí kubernetes a docker na Google Cloud Kubernetes Engine. Pokud se tyto příklady nastavení nedají dobře převést na vaši infrastrukturu, bude pravděpodobně existovat komunitní příručka, na kterou se můžete odkázat, přijďte ji pozdravit na [Discord](https://discord.gg/graphprotocol)! Před spuštěním komponent Indexeru nezapomeňte [zakázat protokol](/network/indexing/#stake-in-the-protocol)! +Agent Indexer a služba Indexer by měly být umístěny společně s infrastrukturou graf uzlu. Existuje mnoho způsobů, jak nastavit virtuální prováděcí prostředí pro komponenty Indexer; zde vysvětlíme, jak je spustit na baremetalu pomocí balíčků NPM nebo zdrojových kódů, nebo pomocí kubernetes a docker na Google Cloud Kubernetes Engine. Pokud se tyto příklady nastavení nedají dobře převést na vaši infrastrukturu, bude pravděpodobně existovat komunitní příručka, na kterou se můžete odkázat, přijďte ji pozdravit na [Discord](https://discord.gg/graphprotocol)! Před spuštěním komponent Indexeru nezapomeňte [zakázat protokol](/indexing/overview/#stake-in-the-protocol)! #### Z balíčků NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Použití K8s a Terraform -Viz část [Nastavení serverové infrastruktury pomocí Terraformu ve službě Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Viz část [Nastavení serverové infrastruktury pomocí Terraformu ve službě Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Použití @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Jakmile indexer zakládá GRT v protokolu, lze spustit komponenty [Indexer](/network/indexing/#indexer-components) a zahájit jejich interakci se sítí. +Jakmile indexer zakládá GRT v protokolu, lze spustit komponenty [Indexer](/indexing/overview/#indexer-components) a zahájit jejich interakci se sítí. #### Schválení žetonů @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Aktivní** – Jakmile je alokace vytvořena v řetězci ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/ contract/staking/Staking.sol#L316)) je považován za **aktivní**. Část vlastního a/nebo delegovaného podílu indexeru je přidělena na nasazení podgrafu, což jim umožňuje nárokovat si odměny za indexování a obsluhovat dotazy pro toto nasazení podgrafu. Agent indexeru spravuje vytváření alokací na základě pravidel indexeru. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexerům se doporučuje využívat funkce synchronizace mimo řetězec k synchronizaci nasazení subgrafů do hlavy řetězce před vytvořením alokace v řetězci. Tato funkce je užitečná zejména pro subgrafy, jejichž synchronizace může trvat déle než 28 epoch nebo u nichž existuje určitá pravděpodobnost nedeterministického selhání. diff --git a/website/pages/cs/indexing/tap.mdx b/website/pages/cs/indexing/tap.mdx index 6594ce05e1f5..bcf852442f4d 100644 --- a/website/pages/cs/indexing/tap.mdx +++ b/website/pages/cs/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Poznámky: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/cs/resources/benefits.mdx b/website/pages/cs/resources/benefits.mdx index 36124a5b505a..1f8942457a79 100644 --- a/website/pages/cs/resources/benefits.mdx +++ b/website/pages/cs/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Kurátorování signálu na podgrafu je volitelný jednorázový čistý nulový náklad (např. na podgrafu lze kurátorovat signál v hodnotě $1k a později jej stáhnout - s potenciálem získat v tomto procesu výnosy). @@ -89,4 +89,4 @@ Decentralizovaná síť Grafu poskytuje uživatelům přístup ke geografické r Podtrženo a sečteno: Síť Graf je levnější, jednodušší na používání a poskytuje lepší výsledky než lokální provozování `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/cs/resources/roles/curating.mdx b/website/pages/cs/resources/roles/curating.mdx index f693ab60980d..54bcf2497c8d 100644 --- a/website/pages/cs/resources/roles/curating.mdx +++ b/website/pages/cs/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Jak signalizovat -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) Kurátor si může zvolit, zda bude signalizovat na konkrétní verzi podgrafu, nebo zda se jeho signál automaticky přenese na nejnovější produkční sestavení daného podgrafu. Obě strategie jsou platné a mají své výhody i nevýhody. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Trh s dotazy je v Graf ze své podstaty mladý a existuje riziko, že vaše %APY může být nižší, než očekáváte, v důsledku dynamiky rodícího se trhu. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Podgraf může selhat kvůli chybě. Za neúspěšný podgraf se neúčtují poplatky za dotaz. V důsledku toho budete muset počkat, až vývojář chybu opraví a nasadí novou verzi. - Pokud jste přihlášeni k odběru nejnovější verze podgrafu, vaše sdílené položky se automaticky přemigrují na tuto novou verzi. Při tom bude účtována 0,5% kurátorská daň. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/cs/resources/tokenomics.mdx b/website/pages/cs/resources/tokenomics.mdx index 01a258d0fdcd..6937dd409631 100644 --- a/website/pages/cs/resources/tokenomics.mdx +++ b/website/pages/cs/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Dotazování na existující podgraf -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/cs/subgraphs/billing.mdx b/website/pages/cs/subgraphs/billing.mdx index c308319f4286..5bf78c17bb64 100644 --- a/website/pages/cs/subgraphs/billing.mdx +++ b/website/pages/cs/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Klikněte na tlačítko "Připojit peněženku" v pravém horním rohu stránky. Budete přesměrováni na stránku pro výběr peněženky. Vyberte svou peněženku a klikněte na "Připojit". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Klikněte na tlačítko "Připojit peněženku" v pravém horním rohu stránky. Budete přesměrováni na stránku pro výběr peněženky. Vyberte svou peněženku a klikněte na "Připojit". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Přidání GRT pomocí multisig peněženky -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/cs/subgraphs/cookbook/arweave.mdx b/website/pages/cs/subgraphs/cookbook/arweave.mdx index 40c88f99ccca..b9156b1c40a2 100644 --- a/website/pages/cs/subgraphs/cookbook/arweave.mdx +++ b/website/pages/cs/subgraphs/cookbook/arweave.mdx @@ -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/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Dotazování podgrafu Arweave -Koncový bod GraphQL pro podgrafy Arweave je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci rozhraní GraphQL API](/querying/graphql-api/). +Koncový bod GraphQL pro podgrafy Arweave je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci rozhraní GraphQL API](/subgraphs/querying/graphql-api/). ## Příklad podgrafů diff --git a/website/pages/cs/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/cs/subgraphs/cookbook/avoid-eth-calls.mdx index 2a469ec0844e..da01b6cad361 100644 --- a/website/pages/cs/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/cs/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/cs/subgraphs/cookbook/cosmos.mdx b/website/pages/cs/subgraphs/cookbook/cosmos.mdx index b604b8dabda0..5fd2162c63ba 100644 --- a/website/pages/cs/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/cs/subgraphs/cookbook/cosmos.mdx @@ -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/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Dotazování podgrafu Cosmos -Koncový bod GraphQL pro podgrafy Cosmos je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci GraphQL API](/querying/graphql-api/). +Koncový bod GraphQL pro podgrafy Cosmos je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci GraphQL API](/subgraphs/querying/graphql-api/). ## Podporované blockchainy Cosmos diff --git a/website/pages/cs/subgraphs/cookbook/derivedfrom.mdx b/website/pages/cs/subgraphs/cookbook/derivedfrom.mdx index b5662250e154..1e78f786b696 100644 --- a/website/pages/cs/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/cs/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ Tím se nejen zefektivní náš podgraf, ale také se odemknou tři funkce: 2. Můžeme provést zpětné vyhledávání a dotazovat se na jakýkoli `Komentář` a zjistit, ze kterého příspěvku pochází. -3. Pomocí [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) můžeme odemknout možnost přímého přístupu a manipulace s daty z virtuálních vztahů v našich mapováních podgrafů. +3. Pomocí [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) můžeme odemknout možnost přímého přístupu a manipulace s daty z virtuálních vztahů v našich mapováních podgrafů. ## Závěr @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/cs/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/cs/subgraphs/cookbook/grafting-hotfix.mdx index e93c527fa90c..934f1dd419c3 100644 --- a/website/pages/cs/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/cs/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Další zdroje -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/cs/subgraphs/cookbook/grafting.mdx b/website/pages/cs/subgraphs/cookbook/grafting.mdx index 71c477065788..d18fe0be5fe5 100644 --- a/website/pages/cs/subgraphs/cookbook/grafting.mdx +++ b/website/pages/cs/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Dodržováním těchto pokynů minimalizujete rizika a zajistíte hladší průb ## Vytvoření existujícího podgrafu -Vytváření podgrafů je důležitou součástí Grafu, která je podrobněji popsána [zde](/quick-start/). Aby bylo možné sestavit a nasadit existující podgraf použitý v tomto tutoriálu, je k dispozici následující repozitář: +Vytváření podgrafů je důležitou součástí Grafu, která je podrobněji popsána [zde](/subgraphs/quick-start/). Aby bylo možné sestavit a nasadit existující podgraf použitý v tomto tutoriálu, je k dispozici následující repozitář: - [Příklad repo subgrafu](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c Chcete-li se stát ještě větším odborníkem na graf, zvažte možnost seznámit se s dalšími způsoby zpracování změn v podkladových zdrojích dat. Alternativy jako [Šablony zdroje dat](/developing/creating-a-subgraph/#data-source-templates) mohou dosáhnout podobných výsledků -> Poznámka: Mnoho materiálů z tohoto článku bylo převzato z dříve publikovaného [článku Arweave](/cookbook/arweave/) +> Poznámka: Mnoho materiálů z tohoto článku bylo převzato z dříve publikovaného [článku Arweave](/subgraphs/cookbook/arweave/) diff --git a/website/pages/cs/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/cs/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 620906f8cf65..f63f6ba6fb03 100644 --- a/website/pages/cs/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/cs/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Více informací o používání nezměnitelných entit a bytů jako ID najdete ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/cs/subgraphs/cookbook/near.mdx b/website/pages/cs/subgraphs/cookbook/near.mdx index 156610d51579..010aeefc48f9 100644 --- a/website/pages/cs/subgraphs/cookbook/near.mdx +++ b/website/pages/cs/subgraphs/cookbook/near.mdx @@ -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í AssemblyScript:** [Kód 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. +**Mapování AssemblyScript:** [Kód AssemblyScript](/subgraphs/developing/creating/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 [API AssemblyScript](/developing/graph-ts/api/) datové typy specifické pro NEAR. +Indexování NEAR zavádí do [API AssemblyScript](/subgraphs/developing/creating/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` -V opačném případě mají vývojáři podgrafů NEAR během provádění mapování k dispozici zbytek [AssemblyScript API](/developing/graph-ts/api/). +V opačném případě mají vývojáři podgrafů NEAR během provádění mapování k dispozici zbytek [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). -To zahrnuje novou funkci pro parsování JSON - log na NEAR jsou často emitovány jako serializované JSONs. 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 log. +To zahrnuje novou funkci pro parsování JSON - log na NEAR jsou často emitovány jako serializované JSONs. Nová funkce `json.fromString(...)` je k dispozici jako součást [JSON API](/subgraphs/developing/creating/graph-ts/api/#json-api), která umožňuje vývojářům snadno zpracovávat tyto log. ## Nasazení podgrafu NEAR @@ -228,7 +228,7 @@ Brzy vám poskytneme další informace o provozu výše uvedených komponent. ## Dotazování podgrafu NEAR -Koncový bod GraphQL pro podgrafy NEAR je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci GraphQL API](/querying/graphql-api/). +Koncový bod GraphQL pro podgrafy NEAR je určen definicí schématu se stávajícím rozhraním API. Další informace naleznete v [dokumentaci GraphQL API](/subgraphs/querying/graphql-api/). ## Příklady podgrafů @@ -276,7 +276,7 @@ Pro podgrafy NEAR zatím nejsou podporovány čekající funkce. V mezidobí mů ### Moje otázka nebyla zodpovězena, kde mohu získat další pomoc při vytváření podgrafů NEAR? -Pokud se jedná o obecnou otázku týkající se vývoje podgrafů, je zde mnohem více informací ve zbytku [dokumentace pro vývojáře](/quick-start/). Jinak se prosím připojte k [The Graph Protocol Discord](https://discord.gg/graphprotocol) a zeptejte se na #near kanálu nebo e-mailem near@thegraph.com. +Pokud se jedná o obecnou otázku týkající se vývoje podgrafů, je zde mnohem více informací ve zbytku [dokumentace pro vývojáře](/subgraphs/quick-start/). Jinak se prosím připojte k [The Graph Protocol Discord](https://discord.gg/graphprotocol) a zeptejte se na #near kanálu nebo e-mailem near@thegraph.com. ## Odkazy: diff --git a/website/pages/cs/subgraphs/cookbook/pruning.mdx b/website/pages/cs/subgraphs/cookbook/pruning.mdx index 32ffb4e5450a..c818c06f37d5 100644 --- a/website/pages/cs/subgraphs/cookbook/pruning.mdx +++ b/website/pages/cs/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Přidejte do manifestu sekci `indexerHints`. - `prune: auto`: Udržuje minimální potřebnou historii nastavenou indexátorem, čímž optimalizuje výkon dotazu. Toto je obecně doporučené nastavení a je výchozí pro všechny podgrafy vytvořené pomocí `graph-cli` >= 0.66.0. - `prune: `: Nastaví vlastní omezení počtu historických bloků, které se mají zachovat. -- `prune: never`: Je výchozí, pokud není k dispozici sekce `indexerHints`. `prune: never` by mělo být vybráno, pokud jsou požadovány [Dotazy na cestování časem](/querying/graphql-api/#time-travel-queries). +- `prune: never`: Je výchozí, pokud není k dispozici sekce `indexerHints`. `prune: never` by mělo být vybráno, pokud jsou požadovány [Dotazy na cestování časem](/subgraphs/querying/graphql-api/#time-travel-queries). Aktualizací souboru `subgraph.yaml` můžeme do podgrafů přidat `indexerHints`: @@ -32,9 +32,9 @@ dataSources: ## Důležité úvahy -- Pokud jsou kromě ořezávání požadovány i [dotazy na cestování v čase](/querying/graphql-api/#time-travel-queries), musí být ořezávání provedeno přesně, aby byla zachována funkčnost dotazů na cestování v čase. Z tohoto důvodu se obecně nedoporučuje používat `indexerHints: prune: auto` s Time Travel Queries. Místo toho proveďte ořezávání pomocí `indexerHints: prune: ` pro přesné ořezání na výšku bloku, která zachovává historická data požadovaná dotazy Time Travel, nebo použijte `prune: never` pro zachování všech dat. +- Pokud jsou kromě ořezávání požadovány i [dotazy na cestování v čase](/subgraphs/querying/graphql-api/#time-travel-queries), musí být ořezávání provedeno přesně, aby byla zachována funkčnost dotazů na cestování v čase. Z tohoto důvodu se obecně nedoporučuje používat `indexerHints: prune: auto` s Time Travel Queries. Místo toho proveďte ořezávání pomocí `indexerHints: prune: ` pro přesné ořezání na výšku bloku, která zachovává historická data požadovaná dotazy Time Travel, nebo použijte `prune: never` pro zachování všech dat. -- Není možné [roubovat](/cookbook/grafting/) na výšku bloku, který byl prořezán. Pokud se roubování provádí běžně a je požadováno prořezání, doporučuje se použít `indexerHints: prune: ` který přesně zachová stanovený počet bloků (např. dostatečný počet na šest měsíců). +- Není možné [roubovat](/subgraphs/cookbook/grafting/) na výšku bloku, který byl prořezán. Pokud se roubování provádí běžně a je požadováno prořezání, doporučuje se použít `indexerHints: prune: ` který přesně zachová stanovený počet bloků (např. dostatečný počet na šest měsíců). ## Závěr @@ -42,14 +42,14 @@ Ořezávání pomocí `indexerHints` je osvědčeným postupem pro vývoj podgra ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx index d6d58b3e45f0..348ddb6f4065 100644 --- a/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/cs/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Podgrafy napájen substreamů --- -[Substreams](/substreams/) je nový framework pro zpracování blockchainových dat vyvinutý společností StreamingFast pro The Grafu síť. Moduly Substreams mohou vypisovat změny entit, které jsou kompatibilní s entitami Subgraph. Subgraph může takový modul Substreams používat jako zdroj dat, což vývojářům Subgraphu přináší rychlost indexování a další data Substreams. +[Substreams](/substreams/introduction/) je nový framework pro zpracování blockchainových dat vyvinutý společností StreamingFast pro The Grafu síť. Moduly Substreams mohou vypisovat změny entit, které jsou kompatibilní s entitami Subgraph. Subgraph může takový modul Substreams používat jako zdroj dat, což vývojářům Subgraphu přináší rychlost indexování a další data Substreams. ## Požadavky @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Definování balíčku Substreams -Balíček Substreams se skládá z typů (definovaných jako [Protocol Buffers](https://protobuf.dev/)), modulů (napsaných v jazyce Rust) a souboru `substreams.yaml`, který odkazuje na typy a určuje, jak se moduly spouštějí. [Navštivte dokumentaci Substreams, kde se dozvíte více o vývoji Substreams](/substreams/), a podívejte se na [awesome-substreams](https://github.com/pinax-network/awesome-substreams) a [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook), kde najdete další příklady. +Balíček Substreams se skládá z typů (definovaných jako [Protocol Buffers](https://protobuf.dev/)), modulů (napsaných v jazyce Rust) a souboru `substreams.yaml`, který odkazuje na typy a určuje, jak se moduly spouštějí. [Navštivte dokumentaci Substreams, kde se dozvíte více o vývoji Substreams](/substreams/introduction/), a podívejte se na [awesome-substreams](https://github.com/pinax-network/awesome-substreams) a [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook), kde najdete další příklady. Dotyčný balíček Substreams detekuje nasazení kontraktů na Mainnet Ethereum a sleduje blok vytvoření a časové razítko všech nově nasazených kontraktů. K tomu je v souboru `/proto/example.proto` ([více informací o definování protokolových bufferů](https://protobuf.dev/programming-guides/proto3/#simple)) vyhrazen typ `Contract`: diff --git a/website/pages/cs/subgraphs/cookbook/timeseries.mdx b/website/pages/cs/subgraphs/cookbook/timeseries.mdx index 48be01215291..7178891769da 100644 --- a/website/pages/cs/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/cs/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/cs/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/cs/subgraphs/cookbook/transfer-to-the-graph.mdx index e0b9a1fbfe53..261cc3e03b80 100644 --- a/website/pages/cs/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/cs/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Příklad @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Další zdroje -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/cs/subgraphs/developing/creating/advanced.mdx b/website/pages/cs/subgraphs/developing/creating/advanced.mdx index 7d62e06bd1cd..4bd34e17c1c1 100644 --- a/website/pages/cs/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/cs/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Pokud je vztah mezi nadřazenou entitou a entitou výsledného zdroje dat souboru 1:1, je nejjednodušším vzorem propojení nadřazené entity s entitou výsledného souboru pomocí CID IPFS jako vyhledávacího prvku. Pokud máte potíže s modelováním nových entit založených na souborech, ozvěte se na Discord! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Kromě toho není možné vytvářet zdroje dat ze zdroje dat souborů, ať už Pokud propojovat metadata NFT s odpovídajícími tokeny, použijte hash IPFS metadat k odkazu na entita Metadata z entity Token. Uložte entitu Metadata s použitím hashe IPFS jako ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Roubování na existující podgrafy -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx index fb96e7ac2a7a..157f54abcd02 100644 --- a/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/cs/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ Knihovna `@graphprotocol/graph-ts` poskytuje následující API: | 0.0.8 | Přidá ověření existence polí ve schéma při ukládání entity. | | 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum
Přidání pole `receipt` do objektu Ethereum událost | | 0.0.6 | Přidáno pole `nonce` do objektu Ethereum Transaction
Přidáno `baseFeePerGas` do objektu Ethereum bloku | -| 0.0.5 | AssemblyScript povýšen na verzi 0.19.10 (obsahuje rozbíjející změny, viz [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` přejmenováno na `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript povýšen na verzi 0.19.10 (obsahuje rozbíjející změny, viz [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` přejmenováno na `ethereum.transaction.gasLimit` | | 0.0.4 | Přidání pole `functionSignature` do objektu Ethereum SmartContractCall | | 0.0.3 | Do objektu Ethereum Call přidáno pole `from`
`etherem.call.address` přejmenováno na `ethereum.call.to` | | 0.0.2 | Přidání pole `input` do objektu Ethereum Transackce | diff --git a/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx index 41abfbdccf16..913017bb3632 100644 --- a/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/cs/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Instalace Graf CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Přehled -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Začínáme @@ -114,6 +114,6 @@ Soubor(y) ABI se musí shodovat s vaší smlouvou. Soubory ABI lze získat něko | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx b/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx index 135d55457dcf..ae9d13f0f547 100644 --- a/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/cs/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/cs/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/cs/subgraphs/developing/creating/starting-your-subgraph.mdx index 68fba6498608..ebfaefc06b4f 100644 --- a/website/pages/cs/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/cs/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/cs/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/cs/subgraphs/developing/creating/subgraph-manifest.mdx index 84ff104974cf..705df5167126 100644 --- a/website/pages/cs/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/cs/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). Důležité položky, které je třeba v manifestu aktualizovat, jsou: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: Uchování určitého množství historických dat: diff --git a/website/pages/cs/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/cs/subgraphs/developing/creating/unit-testing-framework.mdx index ef2cdd645f76..e20ab984b5ca 100644 --- a/website/pages/cs/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/cs/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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 -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) +This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx index 069ac68eb04a..fabe3c9f0fb1 100644 --- a/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/cs/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### Kompatibilita podgrafů se sítí grafů Aby mohly být podgrafy podporovány indexátory v síti grafů, musí: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - Nesmí používat žádnou z následujících funkcí: - ipfs.cat & ipfs.map - Nefatální @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatická archivace verzí podgrafů diff --git a/website/pages/cs/subgraphs/developing/developer-faq.mdx b/website/pages/cs/subgraphs/developing/developer-faq.mdx index 7c3af8122927..095bef559f01 100644 --- a/website/pages/cs/subgraphs/developing/developer-faq.mdx +++ b/website/pages/cs/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ Podgraf musíte znovu nasadit, ale pokud se ID podgrafu (hash IPFS) nezmění, n ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ Pokud je během události vytvořena pouze jedna entita a pokud není k dispozic ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -Seznam podporovaných sítí najdete [zde](/developing/supported-networks/). +Seznam podporovaných sítí najdete [zde](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/cs/subgraphs/developing/introduction.mdx b/website/pages/cs/subgraphs/developing/introduction.mdx index 106792c6b4ed..dd7c69ed878a 100644 --- a/website/pages/cs/subgraphs/developing/introduction.mdx +++ b/website/pages/cs/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Vývoj --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Přehled @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx index d09ee76572fc..4da92b0e4ffb 100644 --- a/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/cs/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Aktualizace metadata publikovaného podgrafu @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Přidání signálu do podgrafu, který nemá nárok na odměny, nepřiláká další indexátory. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Případně můžete přidat signál GRT do publikovaného podgrafu z Průzkumn ![Signál z Průzkumníka](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/cs/subgraphs/developing/subgraphs.mdx b/website/pages/cs/subgraphs/developing/subgraphs.mdx index 386ea043e174..75af9e178fab 100644 --- a/website/pages/cs/subgraphs/developing/subgraphs.mdx +++ b/website/pages/cs/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/cs/subgraphs/explorer.mdx b/website/pages/cs/subgraphs/explorer.mdx index 17e39181358b..17315c1347dd 100644 --- a/website/pages/cs/subgraphs/explorer.mdx +++ b/website/pages/cs/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Chcete-li se dozvědět více o tom, jak se stát indexátorem, můžete se podívat do [oficiální dokumentace](/network/indexing/) nebo do [průvodců pro indexátory akademie graf.](https://thegraph.academy/delegators/choosing-indexers/) +Chcete-li se dozvědět více o tom, jak se stát indexátorem, můžete se podívat do [oficiální dokumentace](/indexing/overview/) nebo do [průvodců pro indexátory akademie graf.](https://thegraph.academy/delegators/choosing-indexers/) ![Podokno s podrobnostmi o indexování](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Obrázek průzkumníka 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegáti @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Celkové množství GRT, které mají v současné době v protokolu - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Síť diff --git a/website/pages/cs/subgraphs/querying/best-practices.mdx b/website/pages/cs/subgraphs/querying/best-practices.mdx index 2c624f1ec87b..3ec0ff35e4ad 100644 --- a/website/pages/cs/subgraphs/querying/best-practices.mdx +++ b/website/pages/cs/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Každý `název dotazu` smí být při jedné operaci použit pouze jednou. - Každé `pole` musí být ve výběru použito pouze jednou (pod `token` se nemůžeme dvakrát dotazovat na `id`) -- Některá `pole` nebo dotazy (jako `tokeny`) vracejí složené typy, které vyžadují výběr podpole. Nezadání výběru, když se očekává (nebo zadání výběru, když se neočekává - například u `id`), vyvolá chybu. Chcete-li znát typ pole, podívejte se na [Graph Explorer](/network/explorer/). +- Některá `pole` nebo dotazy (jako `tokeny`) vracejí složené typy, které vyžadují výběr podpole. Nezadání výběru, když se očekává (nebo zadání výběru, když se neočekává - například u `id`), vyvolá chybu. Chcete-li znát typ pole, podívejte se na [Graph Explorer](/subgraphs/explorer/). - Každá proměnná přiřazená argumentu musí odpovídat jeho typu. - V daném seznamu proměnných musí být každá z nich jedinečná. - Musí být použity všechny definované proměnné. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Odeslání dotazu na GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Manipulace s podgrafy napříč řetězci: Dotazování z více podgrafů v jednom dotazu - [Automatické sledování](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/cs/subgraphs/querying/graphql-api.mdx b/website/pages/cs/subgraphs/querying/graphql-api.mdx index 0e8100c65976..2ba74416739d 100644 --- a/website/pages/cs/subgraphs/querying/graphql-api.mdx +++ b/website/pages/cs/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/cs/subgraphs/querying/introduction.mdx b/website/pages/cs/subgraphs/querying/introduction.mdx index c6ff13f45420..a7ea241c1087 100644 --- a/website/pages/cs/subgraphs/querying/introduction.mdx +++ b/website/pages/cs/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Dotazování na graf When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/cs/subgraphs/quick-start.mdx b/website/pages/cs/subgraphs/quick-start.mdx index a9a090bca4d6..813aa23768c2 100644 --- a/website/pages/cs/subgraphs/quick-start.mdx +++ b/website/pages/cs/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Rychlé Začít --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Požadavky - Kryptopeněženka -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Přidání signálu do podgrafu @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/cs/substreams/sps/sps-faq.mdx b/website/pages/cs/substreams/sps/sps-faq.mdx index dd0612c56071..d6e28bf3296d 100644 --- a/website/pages/cs/substreams/sps/sps-faq.mdx +++ b/website/pages/cs/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Podgrafy napájen substreamů Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Další informace o substreamu naleznete v [Dokumentace k substreamů](/substreams/). +Další informace o substreamu naleznete v [Dokumentace k substreamů](/substreams/introduction/). ## Co jsou substreamu napájen podgrafy? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) kombinují sílu Substreams s možností dotazování na podgrafy. Při publikování Substreams-powered podgrafu mohou data vytvořená transformacemi Substreams [výstupní změny entit](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), které jsou kompatibilní s entitami podgrafu. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) kombinují sílu Substreams s možností dotazování na podgrafy. Při publikování Substreams-powered podgrafu mohou data vytvořená transformacemi Substreams [výstupní změny entit](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), které jsou kompatibilní s entitami podgrafu. Pokud jste již obeznámeni s vývojem podgrafů, pak vězte, že na podgrafy vytvořené pomocí Substreams se lze dotazovat stejně, jako kdyby byly vytvořeny transformační vrstvou AssemblyScript, se všemi výhodami Subgraphu, jako je poskytování dynamického a flexibilního GraphQL API. @@ -62,9 +62,9 @@ Používání Firehose přináší mnoho výhod, včetně: ## Kde mohou vývojáři získat více informací o substreamu, které jsou založeny na podgraf a substreamu? -Dokumentace [Substreams](/substreams/) vás naučí, jak vytvářet moduly Substreams. +Dokumentace [Substreams](/substreams/introduction/) vás naučí, jak vytvářet moduly Substreams. -Dokumentace [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) vám ukáže, jak je zabalit pro nasazení na Grafu. +Dokumentace [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) vám ukáže, jak je zabalit pro nasazení na Grafu. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ Jako příklad může Alice vytvořit cenový modul DEX, Bob jej může použít ## Jak můžete vytvořit a nasadit Substreams využívající podgraf? -Po [definování](/cookbook/substreams-powered-subgraphs/) podgrafu s podporou substreamů jej můžete pomocí Graph CLI nasadit v [Subgraph Studio](https://thegraph.com/studio/). +Po [definování](/subgraphs/cookbook/substreams-powered-subgraphs/) podgrafu s podporou substreamů jej můžete pomocí Graph CLI nasadit v [Subgraph Studio](https://thegraph.com/studio/). ## Kde najdu příklady podgrafů Substreams a Substreams-powered? diff --git a/website/pages/cs/supported-networks.mdx b/website/pages/cs/supported-networks.mdx index e9f1d67e1f3a..16a1fb4e7b6f 100644 --- a/website/pages/cs/supported-networks.mdx +++ b/website/pages/cs/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/de/about.mdx b/website/pages/de/about.mdx index 8c088d6a53d1..61dbccdd5c84 100644 --- a/website/pages/de/about.mdx +++ b/website/pages/de/about.mdx @@ -24,7 +24,7 @@ Im Fall des oben aufgeführten konkreten Beispiels, Bored Ape Yacht Club, könne Es würde **Stunden oder sogar Tage** dauern, bis eine dezentrale Anwendung (dapp), die in einem Browser läuft, eine Antwort auf diese einfachen Fragen erhält. -Alternativ können Sie einen eigenen Server einrichten, die Transaktionen verarbeiten, sie in einer Datenbank speichern und einen API-Endpunkt zur Abfrage der Daten erstellen. Diese Option ist jedoch [Ressourcen-intensiv](/network/benefits/), muss gewartet werden, stellt einen Single Point of Failure dar und bricht wichtige Sicherheitseigenschaften, die für die Dezentralisierung erforderlich sind. +Alternativ können Sie einen eigenen Server einrichten, die Transaktionen verarbeiten, sie in einer Datenbank speichern und einen API-Endpunkt zur Abfrage der Daten erstellen. Diese Option ist jedoch [Ressourcen-intensiv](/resources/benefits/), muss gewartet werden, stellt einen Single Point of Failure dar und bricht wichtige Sicherheitseigenschaften, die für die Dezentralisierung erforderlich sind. Blockchain-Eigenschaften wie Endgültigkeit, Umstrukturierung der Kette und nicht gesperrte Blöcke erhöhen die Komplexität des Prozesses und machen es zeitaufwändig und konzeptionell schwierig, genaue Abfrageergebnisse aus Blockchain-Daten zu erhalten. diff --git a/website/pages/de/archived/arbitrum/arbitrum-faq.mdx b/website/pages/de/archived/arbitrum/arbitrum-faq.mdx index 7e48874081e2..010ccbb6feb1 100644 --- a/website/pages/de/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/de/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Um die Vorteile von The Graph auf L2 zu nutzen, verwenden Sie diesen Dropdown-Sc ## Was muss ich als Entwickler von Subgraphen, Datenkonsument, Indexer, Kurator oder Delegator jetzt tun? -Die Netzwerkteilnehmer müssen zu Arbitrum wechseln, um weiterhin am The Graph Netzwerk teilzunehmen. Bitte lesen Sie den [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) für zusätzliche Unterstützung. +Die Netzwerkteilnehmer müssen zu Arbitrum wechseln, um weiterhin am The Graph Netzwerk teilzunehmen. Bitte lesen Sie den [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) für zusätzliche Unterstützung. Alle Indexierungsprämien sind jetzt vollständig auf Arbitrum. @@ -53,7 +53,7 @@ Alles wurde gründlich getestet, und es gibt einen Notfallplan, um einen sichere ## Funktionieren die vorhandenen Subgraphen auf Ethereum? -Alle Subgraphen sind jetzt auf Arbitrum. Bitte lesen Sie den [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/), um sicherzustellen, dass Ihre Subgraphen reibungslos funktionieren. +Alle Subgraphen sind jetzt auf Arbitrum. Bitte lesen Sie den [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/), um sicherzustellen, dass Ihre Subgraphen reibungslos funktionieren. ## Verfügt GRT über einen neuen Smart Contract, der auf Arbitrum eingesetzt wird? diff --git a/website/pages/de/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/de/archived/arbitrum/l2-transfer-tools-faq.mdx index 5ff21e03c171..8cb7f384c353 100644 --- a/website/pages/de/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/de/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ Für diese Tools müssen Sie eine Reihe von Schritten befolgen, je nachdem, welc ### Kann ich dieselbe Wallet verwenden, die ich im Ethereum Mainnet benutze? -Wenn Sie eine [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) Wallet verwenden, können Sie dieselbe Adresse verwenden. Wenn Ihr Ethereum Mainnet Wallet ein Kontrakt ist (z.B. ein Multisig), dann müssen Sie eine [Arbitrum Wallet Adresse](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) angeben, an die Ihr Transfer gesendet wird. Bitte überprüfen Sie die Adresse sorgfältig, da Überweisungen an eine falsche Adresse zu einem dauerhaften Verlust führen können. Wenn Sie einen Multisig auf L2 verwenden möchten, stellen Sie sicher, dass Sie einen Multisig-Vertrag auf Arbitrum One einsetzen. +Wenn Sie eine [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) Wallet verwenden, können Sie dieselbe Adresse verwenden. Wenn Ihr Ethereum Mainnet Wallet ein Kontrakt ist (z.B. ein Multisig), dann müssen Sie eine [Arbitrum Wallet Adresse](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) angeben, an die Ihr Transfer gesendet wird. Bitte überprüfen Sie die Adresse sorgfältig, da Überweisungen an eine falsche Adresse zu einem dauerhaften Verlust führen können. Wenn Sie einen Multisig auf L2 verwenden möchten, stellen Sie sicher, dass Sie einen Multisig-Vertrag auf Arbitrum One einsetzen. Wallets auf EVM-Blockchains wie Ethereum und Arbitrum bestehen aus einem Paar von Schlüsseln (öffentlich und privat), die Sie erstellen, ohne mit der Blockchain interagieren zu müssen. Jede Wallet, die für Ethereum erstellt wurde, funktioniert also auch auf Arbitrum, ohne dass Sie etwas anderes tun müssen. diff --git a/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx index 15f85694f91f..edb420b072aa 100644 --- a/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/de/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph hat den Wechsel zu L2 auf Arbitrum One leicht gemacht. Für jeden Protokollteilnehmer gibt es eine Reihe von L2-Transfer-Tools, um den Transfer zu L2 für alle Netzwerkteilnehmer nahtlos zu gestalten. Je nachdem, was Sie übertragen möchten, müssen Sie eine bestimmte Anzahl von Schritten befolgen. -Einige häufig gestellte Fragen zu diesen Tools werden in den [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/) beantwortet. Die FAQs enthalten ausführliche Erklärungen zur Verwendung der Tools, zu ihrer Funktionsweise und zu den Dingen, die bei ihrer Verwendung zu beachten sind. +Einige häufig gestellte Fragen zu diesen Tools werden in den [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/) beantwortet. Die FAQs enthalten ausführliche Erklärungen zur Verwendung der Tools, zu ihrer Funktionsweise und zu den Dingen, die bei ihrer Verwendung zu beachten sind. ## So übertragen Sie Ihren Untergraphen auf Arbitrum (L2) diff --git a/website/pages/de/archived/sunrise.mdx b/website/pages/de/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/de/archived/sunrise.mdx +++ b/website/pages/de/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/de/contracts.mdx b/website/pages/de/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/de/contracts.mdx +++ b/website/pages/de/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/de/indexing/chain-integration-overview.mdx b/website/pages/de/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/de/indexing/chain-integration-overview.mdx +++ b/website/pages/de/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/de/indexing/new-chain-integration.mdx b/website/pages/de/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/de/indexing/new-chain-integration.mdx +++ b/website/pages/de/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/de/indexing/overview.mdx b/website/pages/de/indexing/overview.mdx index d255b2b74cea..af8ed14725b3 100644 --- a/website/pages/de/indexing/overview.mdx +++ b/website/pages/de/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/de/indexing/tap.mdx b/website/pages/de/indexing/tap.mdx index c259f0dbbf32..27f3b85a8c58 100644 --- a/website/pages/de/indexing/tap.mdx +++ b/website/pages/de/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/de/resources/benefits.mdx b/website/pages/de/resources/benefits.mdx index 8e03bbb2d177..8497b5111a6d 100644 --- a/website/pages/de/resources/benefits.mdx +++ b/website/pages/de/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/de/resources/roles/curating.mdx b/website/pages/de/resources/roles/curating.mdx index a3b96ed010fe..6ddf8e91099c 100644 --- a/website/pages/de/resources/roles/curating.mdx +++ b/website/pages/de/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/de/resources/tokenomics.mdx b/website/pages/de/resources/tokenomics.mdx index 135ec1c56fb8..4041e1223131 100644 --- a/website/pages/de/resources/tokenomics.mdx +++ b/website/pages/de/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Abfrage eines vorhandenen Untergraphen -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/de/subgraphs/billing.mdx b/website/pages/de/subgraphs/billing.mdx index 83193509b958..38b09546511e 100644 --- a/website/pages/de/subgraphs/billing.mdx +++ b/website/pages/de/subgraphs/billing.mdx @@ -15,7 +15,7 @@ Es gibt zwei Pläne für die Abfrage von Subgraphen in The Graph Network. ## Abfrage Zahlungen mit Kreditkarte - Um die Abrechnung mit Kredit-/Debitkarten einzurichten, müssen die Benutzer Subgraph Studio (https://thegraph.com/studio/) aufrufen - 1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf. + 1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/subgraphs/billing/) auf. 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Wählen Sie „ Upgrade Plan“, wenn Sie vom Free Plan upgraden oder wählen Sie „Manage Plan“, wenn Sie GRT bereits in der Vergangenheit zu Ihrem Abrechnungssaldo hinzugefügt haben. Als Nächstes können Sie die Anzahl der Abfragen schätzen, um einen Kostenvoranschlag zu erhalten, dieser Schritt ist jedoch nicht erforderlich. 4. Um eine Zahlung per Kreditkarte zu wählen, wählen Sie „Kreditkarte“ als Zahlungsmethode und geben Sie Ihre Kreditkartendaten ein. Diejenigen, die Stripe bereits verwendet haben, können die Funktion „Link“ verwenden, um ihre Daten automatisch auszufüllen. @@ -50,7 +50,7 @@ Sobald Sie GRT überbrücken, können Sie es zu Ihrem Rechnungssaldo hinzufügen ### Hinzufügen von GRT mit einer Wallet -1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf. +1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/subgraphs/billing/) auf. 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Wählen Sie die Schaltfläche „ Manage “ in der oberen rechten Ecke. Erstmalige Nutzer sehen die Option „Upgrade auf den Wachstumsplan“, während wiederkehrende Nutzer auf „Von der Wallet einzahlen“ klicken. 4. Verwenden Sie den Slider, um die Anzahl der Abfragen zu schätzen, die Sie monatlich erwarten. @@ -67,7 +67,7 @@ Sobald Sie GRT überbrücken, können Sie es zu Ihrem Rechnungssaldo hinzufügen ### GRT über eine Wallet abheben -1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf. +1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/subgraphs/billing/) auf. 2. Klicken Sie auf die Schaltfläche „Connect Wallet“ in der oberen rechten Ecke der Seite. Wählen Sie Ihre Wallet aus und klicken Sie auf „Verbinden“. 3. Klicken Sie auf die Schaltfläche „Verwalten“ in der oberen rechten Ecke der Seite. Wählen Sie „GRT abheben“. Ein Seitenfenster wird angezeigt. 4. Geben Sie den Betrag der GRT ein, den Sie abheben möchten. @@ -76,7 +76,7 @@ Sobald Sie GRT überbrücken, können Sie es zu Ihrem Rechnungssaldo hinzufügen ### Adding GRT using a multisig wallet -1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf. +1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/subgraphs/billing/) auf. 2. Klicke auf die Schaltfläche „Wallet verbinden“ in der oberen rechten Ecke der Seite. Wähle deine Wallet aus und klicke auf „Verbinden“. Wenn du die [Gnosis-Safe](https://gnosis-safe.io/) verwendest, kannst du sowohl deine Multisig-Wallet als auch deine Signatur-Wallet verbinden. Anschließend unterschreibe die zugehörige Nachricht. Dies verursacht keine Gasgebühren. 3. Wählen Sie die Schaltfläche „ Manage “ in der oberen rechten Ecke. Erstmalige Nutzer sehen die Option „Upgrade auf den Wachstumsplan“, während wiederkehrende Nutzer auf „Von der Wallet einzahlen“ klicken. 4. Verwenden Sie den Slider, um die Anzahl der Abfragen zu schätzen, die Sie monatlich erwarten. diff --git a/website/pages/de/subgraphs/cookbook/arweave.mdx b/website/pages/de/subgraphs/cookbook/arweave.mdx index 6e68ee97cf34..16a14b7a0a13 100644 --- a/website/pages/de/subgraphs/cookbook/arweave.mdx +++ b/website/pages/de/subgraphs/cookbook/arweave.mdx @@ -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/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Beispiele von Subgrafen diff --git a/website/pages/de/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/de/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/de/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/de/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/de/subgraphs/cookbook/cosmos.mdx b/website/pages/de/subgraphs/cookbook/cosmos.mdx index c37bc95e625e..8c0cd3b67a2c 100644 --- a/website/pages/de/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/de/subgraphs/cookbook/cosmos.mdx @@ -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. -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Unterstützte Cosmos-Blockchains diff --git a/website/pages/de/subgraphs/cookbook/derivedfrom.mdx b/website/pages/de/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/de/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/de/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/de/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/de/subgraphs/cookbook/grafting-hotfix.mdx index 040e3a8209d5..a0bd3f4ab1c2 100644 --- a/website/pages/de/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/de/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/de/subgraphs/cookbook/grafting.mdx b/website/pages/de/subgraphs/cookbook/grafting.mdx index bf31d0142e73..593ab8880977 100644 --- a/website/pages/de/subgraphs/cookbook/grafting.mdx +++ b/website/pages/de/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/de/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/de/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/de/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/de/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/de/subgraphs/cookbook/near.mdx b/website/pages/de/subgraphs/cookbook/near.mdx index aa495dfea06e..3a79be20752f 100644 --- a/website/pages/de/subgraphs/cookbook/near.mdx +++ b/website/pages/de/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Beispiele von Subgrafen @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/de/subgraphs/cookbook/pruning.mdx b/website/pages/de/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/de/subgraphs/cookbook/pruning.mdx +++ b/website/pages/de/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/de/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/de/subgraphs/cookbook/timeseries.mdx b/website/pages/de/subgraphs/cookbook/timeseries.mdx index 2ce0ce266ccf..0168be53d7ed 100644 --- a/website/pages/de/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/de/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/de/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/de/subgraphs/cookbook/transfer-to-the-graph.mdx index 3844b7a94142..d9966a91c24f 100644 --- a/website/pages/de/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/de/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/de/subgraphs/developing/creating/advanced.mdx b/website/pages/de/subgraphs/developing/creating/advanced.mdx index 6a27f4a235a0..da0735e7f7d5 100644 --- a/website/pages/de/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/de/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx index a9caaaf51dbb..522282ec37d7 100644 --- a/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/de/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx index 91922e0319e7..fe4a2a2b0585 100644 --- a/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/de/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/de/subgraphs/developing/creating/ql-schema.mdx b/website/pages/de/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/de/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/de/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/de/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/de/subgraphs/developing/creating/starting-your-subgraph.mdx index 5127f01632aa..f463ca3e9507 100644 --- a/website/pages/de/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/de/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/de/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/de/subgraphs/developing/creating/subgraph-manifest.mdx index 0adbd44216a0..925c81a8b98b 100644 --- a/website/pages/de/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/de/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/de/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/de/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/de/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/de/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx index 6b2f6a058019..973293f70f36 100644 --- a/website/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/de/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> Weitere schriftliche Informationen finden Sie im [Schnellstart](/quick-start/). +> Weitere schriftliche Informationen finden Sie im [Schnellstart](/subgraphs/quick-start/). ### Kompatibilität von Subgraphs mit dem The Graph Network Um von Indexern auf The Graph Network unterstützt zu werden, müssen Subgraphen: -- Ein [unterstütztes Netzwerk] indizieren (/developing/supported-networks) +- Ein [unterstütztes Netzwerk] indizieren (/supported-networks/) - Sie dürfen keine der folgenden Funktionen verwenden: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/de/subgraphs/developing/developer-faq.mdx b/website/pages/de/subgraphs/developing/developer-faq.mdx index 85dccad933b0..8a457a3db5c3 100644 --- a/website/pages/de/subgraphs/developing/developer-faq.mdx +++ b/website/pages/de/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/de/subgraphs/developing/introduction.mdx b/website/pages/de/subgraphs/developing/introduction.mdx index 6ba33f6d916c..45cefaff16ef 100644 --- a/website/pages/de/subgraphs/developing/introduction.mdx +++ b/website/pages/de/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 4728db3eb245..e75e3b13d89e 100644 --- a/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/de/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/de/subgraphs/developing/subgraphs.mdx b/website/pages/de/subgraphs/developing/subgraphs.mdx index 58cf1e9f6498..d650db168962 100644 --- a/website/pages/de/subgraphs/developing/subgraphs.mdx +++ b/website/pages/de/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Hier ist ein allgemeiner Überblick über den Lebenszyklus eines Subgraphs: 1. [Einen Subgraph erstellen](/entwickeln/einen-subgraph-erstellen/) 2. [Einen Subgraph bereitstellen](/deploying/deploying-a-subgraph-to-studio/) 3. [Testen eines Subgraphen](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Einen Subgraph veröffentlichen](/publishing/publishing-a-subgraph/) -5. [Signal auf einem Subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Einen Subgraph veröffentlichen](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal auf einem Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/de/subgraphs/explorer.mdx b/website/pages/de/subgraphs/explorer.mdx index 1e0169b9ae37..3506c8c71691 100644 --- a/website/pages/de/subgraphs/explorer.mdx +++ b/website/pages/de/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/de/subgraphs/querying/best-practices.mdx b/website/pages/de/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/de/subgraphs/querying/best-practices.mdx +++ b/website/pages/de/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/de/subgraphs/querying/graphql-api.mdx b/website/pages/de/subgraphs/querying/graphql-api.mdx index 6d9706e54717..8361dc8d94d9 100644 --- a/website/pages/de/subgraphs/querying/graphql-api.mdx +++ b/website/pages/de/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/de/subgraphs/querying/introduction.mdx b/website/pages/de/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/de/subgraphs/querying/introduction.mdx +++ b/website/pages/de/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/de/subgraphs/quick-start.mdx b/website/pages/de/subgraphs/quick-start.mdx index 10201769e249..b8d77b6a44ea 100644 --- a/website/pages/de/subgraphs/quick-start.mdx +++ b/website/pages/de/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Schnellstart --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - Eine Krypto-Wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Veröffentlichung mit Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -Wie Sie Ihre Bereitstellung anpassen können, erfahren Sie unter [Veröffentlichen eines Subgraphen](/publishing/publishing-a-subgraph/). +Wie Sie Ihre Bereitstellung anpassen können, erfahren Sie unter [Veröffentlichen eines Subgraphen](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ Wie Sie Ihre Bereitstellung anpassen können, erfahren Sie unter [Veröffentlich - Es wird empfohlen, mindestens 3.000 GRT zu kuratieren, um 3 Indexer anzuziehen. Prüfen Sie die Berechtigung zum Reward anhand der Nutzung der Subgraph-Funktionen und der unterstützten Netzwerke. -Um mehr über Kuratierung zu erfahren, lesen Sie [Kuratieren](/network/curating/). +Um mehr über Kuratierung zu erfahren, lesen Sie [Kuratieren](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -Weitere Informationen zur Abfrage von Daten aus Ihrem Subgraphen finden Sie unter [Querying The Graph](/querying/querying-the-graph/). +Weitere Informationen zur Abfrage von Daten aus Ihrem Subgraphen finden Sie unter [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/de/substreams/sps/sps-faq.mdx b/website/pages/de/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/de/substreams/sps/sps-faq.mdx +++ b/website/pages/de/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/de/supported-networks.mdx b/website/pages/de/supported-networks.mdx index 9e47f25c86e6..2f3c40917b37 100644 --- a/website/pages/de/supported-networks.mdx +++ b/website/pages/de/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/en/about.mdx b/website/pages/en/about.mdx index 9c21bf00d08f..02b29895881f 100644 --- a/website/pages/en/about.mdx +++ b/website/pages/en/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/en/archived/arbitrum/arbitrum-faq.mdx b/website/pages/en/archived/arbitrum/arbitrum-faq.mdx index 467c3c12c5e5..4fd8f08572e7 100644 --- a/website/pages/en/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/en/archived/arbitrum/arbitrum-faq.mdx @@ -40,7 +40,7 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -52,7 +52,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -76,4 +76,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx index 28d4b85ccca4..4799e75aa821 100644 --- a/website/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/en/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx index e516573fd4d9..485f34a70c97 100644 --- a/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/en/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/en/archived/sunrise.mdx b/website/pages/en/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/en/archived/sunrise.mdx +++ b/website/pages/en/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/en/contracts.mdx b/website/pages/en/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/en/contracts.mdx +++ b/website/pages/en/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/en/indexing/chain-integration-overview.mdx b/website/pages/en/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/en/indexing/chain-integration-overview.mdx +++ b/website/pages/en/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/en/indexing/new-chain-integration.mdx b/website/pages/en/indexing/new-chain-integration.mdx index 6d5992f72aaf..09b74772eff3 100644 --- a/website/pages/en/indexing/new-chain-integration.mdx +++ b/website/pages/en/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -76,4 +76,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/en/indexing/overview.mdx b/website/pages/en/indexing/overview.mdx index 4740c6f82ee0..ae9f6cd286b7 100644 --- a/website/pages/en/indexing/overview.mdx +++ b/website/pages/en/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created onchain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation onchain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/en/indexing/tap.mdx b/website/pages/en/indexing/tap.mdx index 3d6bbed374a9..59c436571549 100644 --- a/website/pages/en/indexing/tap.mdx +++ b/website/pages/en/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/en/resources/benefits.mdx b/website/pages/en/resources/benefits.mdx index 7f4de8e5e5cc..2e1a0834591c 100644 --- a/website/pages/en/resources/benefits.mdx +++ b/website/pages/en/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/en/resources/roles/curating.mdx b/website/pages/en/resources/roles/curating.mdx index ecb879ae6fbe..8e6416b6d57e 100644 --- a/website/pages/en/resources/roles/curating.mdx +++ b/website/pages/en/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/en/resources/tokenomics.mdx b/website/pages/en/resources/tokenomics.mdx index e2e4c904000d..73a1adda922b 100644 --- a/website/pages/en/resources/tokenomics.mdx +++ b/website/pages/en/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/en/subgraphs/billing.mdx b/website/pages/en/subgraphs/billing.mdx index f3af2fd64994..52f56726971a 100644 --- a/website/pages/en/subgraphs/billing.mdx +++ b/website/pages/en/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/en/subgraphs/cookbook/arweave.mdx b/website/pages/en/subgraphs/cookbook/arweave.mdx index f59b8ac82edb..8924a9f56fa5 100644 --- a/website/pages/en/subgraphs/cookbook/arweave.mdx +++ b/website/pages/en/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/en/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/en/subgraphs/cookbook/avoid-eth-calls.mdx index 25fcb8b0db9d..263c4ab018b0 100644 --- a/website/pages/en/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/en/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/en/subgraphs/cookbook/cosmos.mdx b/website/pages/en/subgraphs/cookbook/cosmos.mdx index dfdb377688aa..31a1d372051a 100644 --- a/website/pages/en/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/en/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/en/subgraphs/cookbook/derivedfrom.mdx b/website/pages/en/subgraphs/cookbook/derivedfrom.mdx index 75827a185a6b..51472df50600 100644 --- a/website/pages/en/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/en/subgraphs/cookbook/derivedfrom.mdx @@ -64,7 +64,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 1. We can query the `Post` and see all of its comments. 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -74,14 +74,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/en/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/en/subgraphs/cookbook/grafting-hotfix.mdx index e1d87dbc6fb1..424087e6ecf8 100644 --- a/website/pages/en/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/en/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/en/subgraphs/cookbook/grafting.mdx b/website/pages/en/subgraphs/cookbook/grafting.mdx index 7aa79c7e2755..57d5169830a7 100644 --- a/website/pages/en/subgraphs/cookbook/grafting.mdx +++ b/website/pages/en/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/en/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/en/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 0541837c652d..8c1ab51e1435 100644 --- a/website/pages/en/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/en/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/en/subgraphs/cookbook/near.mdx b/website/pages/en/subgraphs/cookbook/near.mdx index e47043981c52..6060eb27e761 100644 --- a/website/pages/en/subgraphs/cookbook/near.mdx +++ b/website/pages/en/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/en/subgraphs/cookbook/pruning.mdx b/website/pages/en/subgraphs/cookbook/pruning.mdx index d79d5b8911f9..c36a1c24d8eb 100644 --- a/website/pages/en/subgraphs/cookbook/pruning.mdx +++ b/website/pages/en/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/en/subgraphs/cookbook/secure-api-keys-nextjs.mdx b/website/pages/en/subgraphs/cookbook/secure-api-keys-nextjs.mdx index 5ae8b1b0a8dc..fc7e0ff52eb4 100644 --- a/website/pages/en/subgraphs/cookbook/secure-api-keys-nextjs.mdx +++ b/website/pages/en/subgraphs/cookbook/secure-api-keys-nextjs.mdx @@ -120,4 +120,4 @@ Start our Next.js application using `npm run dev`. Verify that the server compon ### Conclusion -By utilizing Next.js Server Components, we've effectively hidden the API key from the client-side, enhancing the security of our application. This method ensures that sensitive operations are handled server-side, away from potential client-side vulnerabilities. Finally, be sure to explore [other API key security measures](/querying/managing-api-keys/) to increase your API key security even further. +By utilizing Next.js Server Components, we've effectively hidden the API key from the client-side, enhancing the security of our application. This method ensures that sensitive operations are handled server-side, away from potential client-side vulnerabilities. Finally, be sure to explore [other API key security measures](/subgraphs/querying/managing-api-keys/) to increase your API key security even further. diff --git a/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/en/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/en/subgraphs/cookbook/timeseries.mdx b/website/pages/en/subgraphs/cookbook/timeseries.mdx index 88ee70005a6e..cb2f4659863c 100644 --- a/website/pages/en/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/en/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/en/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/en/subgraphs/cookbook/transfer-to-the-graph.mdx index c0be2f6798cc..0c8cd7d869ee 100644 --- a/website/pages/en/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/en/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/en/subgraphs/developing/creating/advanced.mdx b/website/pages/en/subgraphs/developing/creating/advanced.mdx index 7e0ca41c5c18..97437ad1a3f8 100644 --- a/website/pages/en/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/en/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/en/subgraphs/developing/creating/graph-ts/[[...slug]].mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/[[...slug]].mdx index 5caa2942a740..b9432222f628 100644 --- a/website/pages/en/subgraphs/developing/creating/graph-ts/[[...slug]].mdx +++ b/website/pages/en/subgraphs/developing/creating/graph-ts/[[...slug]].mdx @@ -33,7 +33,7 @@ export const getStaticProps = buildGetStaticProps(__filename, async ({ params }) } }) }, - [remarkReplaceLinks, { foundPath, basePath: '/developing/graph-ts/' }], + [remarkReplaceLinks, { foundPath, basePath: '/subgraphs/developing/creating/graph-ts/' }], ], }, codeHighlight: false, diff --git a/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx index 6c7247246444..8158751c35c1 100644 --- a/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/en/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx index 282c68973a8a..a58e6be82324 100644 --- a/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/en/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/en/subgraphs/developing/creating/ql-schema.mdx b/website/pages/en/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/en/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/en/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/en/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/en/subgraphs/developing/creating/starting-your-subgraph.mdx index 4388c412b518..cd4a618392ec 100644 --- a/website/pages/en/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/en/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,10 +14,10 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features -Explore additional [resources for APIs](/developing/creating-a-subgraph/graph-ts/README/) and conduct local testing with [Matchstick](/developing/creating-a-subgraph/unit-testing-framework/). +Explore additional [resources for APIs](/subgraphs/developing/creating/graph-ts/README/) and conduct local testing with [Matchstick](/subgraphs/developing/creating/unit-testing-framework/). diff --git a/website/pages/en/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/en/subgraphs/developing/creating/subgraph-manifest.mdx index c5338321b71f..17778abc7836 100644 --- a/website/pages/en/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/en/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx index a2c60833036c..3b59ee1398b9 100644 --- a/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/en/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx index f528b2ba74f7..5aea3f59986b 100644 --- a/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an onchain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/en/subgraphs/developing/developer-faq.mdx b/website/pages/en/subgraphs/developing/developer-faq.mdx index d0bb74ad1633..2a027a39d2c6 100644 --- a/website/pages/en/subgraphs/developing/developer-faq.mdx +++ b/website/pages/en/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/en/subgraphs/developing/introduction.mdx b/website/pages/en/subgraphs/developing/introduction.mdx index c23d6c0918fd..571c9fbe130e 100644 --- a/website/pages/en/subgraphs/developing/introduction.mdx +++ b/website/pages/en/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Introduction to Subgraph Development --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 4728db3eb245..e75e3b13d89e 100644 --- a/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/en/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/en/subgraphs/developing/subgraphs.mdx b/website/pages/en/subgraphs/developing/subgraphs.mdx index 1fdd0baf80eb..951ec74234d1 100644 --- a/website/pages/en/subgraphs/developing/subgraphs.mdx +++ b/website/pages/en/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph Network. - This is an onchain 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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/en/subgraphs/explorer.mdx b/website/pages/en/subgraphs/explorer.mdx index d874f80f5140..433821560d85 100644 --- a/website/pages/en/subgraphs/explorer.mdx +++ b/website/pages/en/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/en/subgraphs/querying/best-practices.mdx b/website/pages/en/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/en/subgraphs/querying/best-practices.mdx +++ b/website/pages/en/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/en/subgraphs/querying/graph-client/[[...slug]].mdx b/website/pages/en/subgraphs/querying/graph-client/[[...slug]].mdx index bf7d4dd4d9d8..0feaed1d5127 100644 --- a/website/pages/en/subgraphs/querying/graph-client/[[...slug]].mdx +++ b/website/pages/en/subgraphs/querying/graph-client/[[...slug]].mdx @@ -33,7 +33,7 @@ export const getStaticProps = buildGetStaticProps(__filename, async ({ params }) } }) }, - [remarkReplaceLinks, { foundPath, basePath: '/querying/graph-client/' }], + [remarkReplaceLinks, { foundPath, basePath: '/subgraphs/querying/graph-client/' }], ], }, codeHighlight: false, diff --git a/website/pages/en/subgraphs/querying/graphql-api.mdx b/website/pages/en/subgraphs/querying/graphql-api.mdx index 917fad3f2406..8813e2eeb3f3 100644 --- a/website/pages/en/subgraphs/querying/graphql-api.mdx +++ b/website/pages/en/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/en/subgraphs/querying/introduction.mdx b/website/pages/en/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/en/subgraphs/querying/introduction.mdx +++ b/website/pages/en/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/en/subgraphs/quick-start.mdx b/website/pages/en/subgraphs/quick-start.mdx index cd5a60e28a08..7e50fd69be14 100644 --- a/website/pages/en/subgraphs/quick-start.mdx +++ b/website/pages/en/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Quick Start --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -119,7 +119,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -151,7 +151,7 @@ Use the following commands: ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -163,7 +163,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -175,4 +175,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/en/substreams/sps/sps-faq.mdx b/website/pages/en/substreams/sps/sps-faq.mdx index ab0e8c4c7d2f..18248fc069df 100644 --- a/website/pages/en/substreams/sps/sps-faq.mdx +++ b/website/pages/en/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-Powered Subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/en/supported-networks.mdx b/website/pages/en/supported-networks.mdx index 9e47f25c86e6..2f3c40917b37 100644 --- a/website/pages/en/supported-networks.mdx +++ b/website/pages/en/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/es/about.mdx b/website/pages/es/about.mdx index 8b1a092a77b5..22dafa9785ad 100644 --- a/website/pages/es/about.mdx +++ b/website/pages/es/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/es/archived/arbitrum/arbitrum-faq.mdx b/website/pages/es/archived/arbitrum/arbitrum-faq.mdx index b418ae4af15c..85ad70c11ca2 100644 --- a/website/pages/es/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/es/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Para aprovechar el uso de The Graph en L2, usa este conmutador desplegable para ## Como developer de subgrafos, consumidor de datos, Indexador, Curador o Delegador, ¿qué debo hacer ahora? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/es/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/es/archived/arbitrum/l2-transfer-tools-faq.mdx index b13db10c2ca7..8c4f263f418b 100644 --- a/website/pages/es/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/es/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx index 684fd486b7e1..f690539ed5ac 100644 --- a/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/es/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Guía de las Herramientas de Transferencia a L2 The Graph ha facilitado la migración a L2 en Arbitrum One. Para cada participante del protocolo, existen un conjunto de herramientas de transferencia a L2 para que la migración sea fluida para todos los participantes de la red. Estas herramientas requerirán que sigas un conjunto específico de pasos dependiendo de lo que estés transfiriendo. -Algunas preguntas frecuentes sobre estas herramientas se responden en las [Preguntas Frecuentes de las Herramientas de Transferencia a L2](/arbitrum/l2-transfer-tools-faq/). Las preguntas frecuentes contienen explicaciones detalladas sobre cómo utilizar las herramientas, cómo funcionan y aspectos a tener en cuenta al usarlas. +Algunas preguntas frecuentes sobre estas herramientas se responden en las [Preguntas Frecuentes de las Herramientas de Transferencia a L2](/archived/arbitrum/l2-transfer-tools-faq/). Las preguntas frecuentes contienen explicaciones detalladas sobre cómo utilizar las herramientas, cómo funcionan y aspectos a tener en cuenta al usarlas. ## Cómo transferir tu subgrafo a Arbitrum (L2) diff --git a/website/pages/es/archived/sunrise.mdx b/website/pages/es/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/es/archived/sunrise.mdx +++ b/website/pages/es/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/es/contracts.mdx b/website/pages/es/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/es/contracts.mdx +++ b/website/pages/es/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/es/indexing/chain-integration-overview.mdx b/website/pages/es/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/es/indexing/chain-integration-overview.mdx +++ b/website/pages/es/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/es/indexing/new-chain-integration.mdx b/website/pages/es/indexing/new-chain-integration.mdx index 5691510d4427..d8942f2818d3 100644 --- a/website/pages/es/indexing/new-chain-integration.mdx +++ b/website/pages/es/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node debería sincronizar el subgrafo implementado si no hay errores. Dale ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/es/indexing/overview.mdx b/website/pages/es/indexing/overview.mdx index 4cbb716f5ca2..82339b40180e 100644 --- a/website/pages/es/indexing/overview.mdx +++ b/website/pages/es/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### ¿Qué es el recorte de la tarifa de consulta y el recorte de la recompensa de indexación? -Los valores de los `QueryFeeCut` e `IndexingRewardCut` son parámetros de delegación que el Indexador debe establecer junto con cooldownBlocks para controlar la distribución de GRT entre el Indexador y sus Delegadores. Hecha un vistazo de los últimos pasos de [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) para obtener instrucciones sobre la configuración de los parámetros de delegación. +Los valores de los `QueryFeeCut` e `IndexingRewardCut` son parámetros de delegación que el Indexador debe establecer junto con cooldownBlocks para controlar la distribución de GRT entre el Indexador y sus Delegadores. Hecha un vistazo de los últimos pasos de [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) para obtener instrucciones sobre la configuración de los parámetros de delegación. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Los indexadores pueden diferenciarse aplicando técnicas avanzadas para tomar de ### ¿Qué precauciones básicas de seguridad debe tomar un Indexador? -- **Wallet del operador** - Configurar una wallet del operador es una precaución importante porque permite que un Indexador mantenga la separación entre sus claves que controlan el stake y las que controlan las operaciones diarias. Consulta [Stake in Protocol](/network/indexing/#stake-in-the-protocol) para obtener instrucciones. +- **Wallet del operador** - Configurar una wallet del operador es una precaución importante porque permite que un Indexador mantenga la separación entre sus claves que controlan el stake y las que controlan las operaciones diarias. Consulta [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) para obtener instrucciones. - **Firewall**: Solo el servicio de indexación debe exponerse públicamente y se debe prestar especial atención al bloqueo de los puertos de administración y el acceso a la base de datos: el endpoint JSON-RPC de Graph Node (puerto predeterminado: 8030), el endpoint de la API de administración del Indexador (puerto predeterminado: 18000) y el endpoint de la base de datos de Postgres (puerto predeterminado: 5432) no deben exponerse. @@ -375,7 +375,7 @@ Para participar con éxito en la red se requiere una supervisión e interacción #### Comenzar -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### Paquetes de NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Uso de K8s y Terraform -Consulta la sección [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Consulta la sección [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Uso @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Una vez que un Indexador ha stakeado GRT en el protocolo, los [Indexer components](/network/indexing/#indexer-components) pueden iniciarse y comenzar sus interacciones con la red. +Una vez que un Indexador ha stakeado GRT en el protocolo, los [Indexer components](/indexing/overview/#indexer-components) pueden iniciarse y comenzar sus interacciones con la red. #### Aprobar tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Se recomienda a los Indexadores que utilicen la funcionalidad de sincronización fuera de la cadena para sincronizar el deploy de subgrafos con el cabezal de la cadena antes de crear la allocation on-chain. Esta función es especialmente útil para subgrafos que pueden tardar más de 28 épocas en sincronizarse o que tienen algunas posibilidades de fallar de forma indeterminada. diff --git a/website/pages/es/indexing/tap.mdx b/website/pages/es/indexing/tap.mdx index 2f0b75160fa9..5292ca8f6bf6 100644 --- a/website/pages/es/indexing/tap.mdx +++ b/website/pages/es/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notas: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/es/resources/benefits.mdx b/website/pages/es/resources/benefits.mdx index e7ea8d8117b4..6109ec463439 100644 --- a/website/pages/es/resources/benefits.mdx +++ b/website/pages/es/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. La señal de curación en un subgrafo es una acción opcional de única vez y no tiene costo neto (por ejemplo, se pueden curar $1k en señales en un subgrafo y luego retirarlas, con el potencial de obtener retornos en el proceso). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy En conclusión: The Graph Network es menos costoso, más fácil de usar y produce resultados superiores en comparación con ejecutar un `graph-node` localmente. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/es/resources/roles/curating.mdx b/website/pages/es/resources/roles/curating.mdx index 815027929cbb..d4d5a05cf14d 100644 --- a/website/pages/es/resources/roles/curating.mdx +++ b/website/pages/es/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Cómo señalar -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) Un curador puede optar por señalar una versión especifica de un subgrafo, o puede optar por que su señal migre automáticamente a la versión de producción mas reciente de ese subgrafo. Ambas son estrategias válidas y tienen sus pros y sus contras. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. El mercado de consultas es inherentemente joven en The Graph y existe el riesgo de que su APY (Rentabilidad anualizada) sea más bajo de lo esperado debido a la dinámica del mercado que recién está empezando. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Un subgrafo puede fallar debido a un error. Un subgrafo fallido no acumula tarifas de consulta. Como resultado, tendrás que esperar hasta que el desarrollador corrija el error e implemente una nueva versión. - Si estás suscrito a la versión más reciente de un subgrafo, tus acciones se migrarán automáticamente a esa nueva versión. Esto incurrirá un impuesto de curación del 0.5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/es/resources/tokenomics.mdx b/website/pages/es/resources/tokenomics.mdx index d2b3cdd86026..6b03a8e4d03d 100644 --- a/website/pages/es/resources/tokenomics.mdx +++ b/website/pages/es/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Consulta de un subgrafo existente -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/es/subgraphs/billing.mdx b/website/pages/es/subgraphs/billing.mdx index 604244a22148..ae5f92309866 100644 --- a/website/pages/es/subgraphs/billing.mdx +++ b/website/pages/es/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Haz clic en el botón "Conectar wallet" en la esquina superior derecha de la página. Serás redirigido a la página de selección de wallet. Selecciona tu wallet y haz clic en "Conectar". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Haz clic en el botón "Conectar wallet" en la esquina superior derecha de la página. Serás redirigido a la página de selección de wallet. Selecciona tu wallet y haz clic en "Conectar". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Añadir GRT utilizando una wallet multisig -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/es/subgraphs/cookbook/arweave.mdx b/website/pages/es/subgraphs/cookbook/arweave.mdx index 7c07a486f887..645fae5f5783 100644 --- a/website/pages/es/subgraphs/cookbook/arweave.mdx +++ b/website/pages/es/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ La definición de esquema describe la estructura de la base de datos de subgrafo Los handlers para procesar eventos están escritos en [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Consultando un subgrafo de Arweave -El endpoint de GraphQL para los subgrafos de Arweave está determinado por la definición del esquema, con la interfaz API existente. Visita la [documentación de la API de GraphQL](/querying/graphql-api/) para obtener más información. +El endpoint de GraphQL para los subgrafos de Arweave está determinado por la definición del esquema, con la interfaz API existente. Visita la [documentación de la API de GraphQL](/subgraphs/querying/graphql-api/) para obtener más información. ## Ejemplos de subgrafos diff --git a/website/pages/es/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/es/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/es/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/es/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/es/subgraphs/cookbook/cosmos.mdx b/website/pages/es/subgraphs/cookbook/cosmos.mdx index fe36514f6de9..e5f07a8ccce4 100644 --- a/website/pages/es/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/es/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and Los controladores para procesar eventos están escritos en [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Consultar un subgrafo de Cosmos -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Blockchains Cosmos compatibles diff --git a/website/pages/es/subgraphs/cookbook/derivedfrom.mdx b/website/pages/es/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/es/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/es/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/es/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/es/subgraphs/cookbook/grafting-hotfix.mdx index 61da49e08f7b..ddf69bb91735 100644 --- a/website/pages/es/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/es/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Recursos Adicionales -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/es/subgraphs/cookbook/grafting.mdx b/website/pages/es/subgraphs/cookbook/grafting.mdx index b5957131aaec..ddd57394fdab 100644 --- a/website/pages/es/subgraphs/cookbook/grafting.mdx +++ b/website/pages/es/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Construcción de un subgrafo existente -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Repo de ejemplo de subgrafo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Nota: Gran parte del material de este artículo se ha extraído del artículo publicado anteriormente por [Arweave](/cookbook/arweave/) +> Nota: Gran parte del material de este artículo se ha extraído del artículo publicado anteriormente por [Arweave](/subgraphs/cookbook/arweave/) diff --git a/website/pages/es/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/es/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/es/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/es/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/es/subgraphs/cookbook/near.mdx b/website/pages/es/subgraphs/cookbook/near.mdx index c1e837bfe88a..a134eed6b560 100644 --- a/website/pages/es/subgraphs/cookbook/near.mdx +++ b/website/pages/es/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ Hay tres aspectos de la definición de subgrafo: **schema.graphql:** un archivo de esquema que define qué datos se almacenan para su subgrafo y cómo consultarlos a través de GraphQL. Los requisitos para los subgrafos NEAR están cubiertos por [la documentación existente](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. Durante el desarrollo del subgrafo hay dos comandos clave: @@ -98,7 +98,7 @@ La definición de esquema describe la estructura de la base de datos de subgrafo Los handlers para procesar eventos están escritos en [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Estos tipos se pasan a block & handlers de recibos: - Los handlers de bloques recibirán un `Block` - Los handlers de recibos recibirán un `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deployando un subgrafo NEAR @@ -228,7 +228,7 @@ Pronto proporcionaremos más información sobre cómo ejecutar los componentes a ## Consultando un subgrafo NEAR -El endpoint de GraphQL para los subgrafos NEAR está determinado por la definición del esquema, con la interfaz API existente. Visite la [documentación de la API de GraphQL](/querying/graphql-api/) para obtener más información. +El endpoint de GraphQL para los subgrafos NEAR está determinado por la definición del esquema, con la interfaz API existente. Visite la [documentación de la API de GraphQL](/subgraphs/querying/graphql-api/) para obtener más información. ## Subgrafos de ejemplo @@ -276,7 +276,7 @@ La funcionalidad pendiente aún no es compatible con los subgrafos NEAR. Mientra ### Mi pregunta no ha sido respondida, ¿dónde puedo obtener más ayuda para crear subgrafos NEAR? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## Referencias diff --git a/website/pages/es/subgraphs/cookbook/pruning.mdx b/website/pages/es/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/es/subgraphs/cookbook/pruning.mdx +++ b/website/pages/es/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/es/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/es/subgraphs/cookbook/timeseries.mdx b/website/pages/es/subgraphs/cookbook/timeseries.mdx index 8eaed50b0ea3..1dd08ab764d1 100644 --- a/website/pages/es/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/es/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/es/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/es/subgraphs/cookbook/transfer-to-the-graph.mdx index d86f6f31fc62..223800a19102 100644 --- a/website/pages/es/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/es/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Ejemplo @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Recursos Adicionales -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/es/subgraphs/developing/creating/advanced.mdx b/website/pages/es/subgraphs/developing/creating/advanced.mdx index 01332c56e82f..e5c406933622 100644 --- a/website/pages/es/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/es/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Si la relación es 1:1 entre la entidad padre y la entidad fuente de datos de archivo resultante, el patrón más sencillo es vincular la entidad padre a una entidad de archivo resultante utilizando el CID IPFS como búsqueda. Pónte en contacto con nosotros en Discord si tienes dificultades para modelar tus nuevas entidades basadas en archivos! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### Crear un nuevo handler para procesar archivos -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Además, no es posible crear fuentes de datos a partir de una File Data Source, Si estás vinculando metadatos NFT a los tokens correspondientes, utiliza el hash IPFS de los metadatos para hacer referencia a una entidad Metadata desde la entidad Token. Guarda la entidad de metadatos utilizando el hash IPFS como ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting sobre subgrafos existentes -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx index 3ae81bb3ba99..6dafeec664af 100644 --- a/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/es/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx index b70948811960..ef16d813c431 100644 --- a/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/es/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Instalar The Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Descripción -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Empezando @@ -114,6 +114,6 @@ Los archivos ABI deben coincidir con tu(s) contrato(s). Hay varias formas de obt | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/es/subgraphs/developing/creating/ql-schema.mdx b/website/pages/es/subgraphs/developing/creating/ql-schema.mdx index f1c9b18b2670..cb79b75fa584 100644 --- a/website/pages/es/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/es/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/es/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/es/subgraphs/developing/creating/starting-your-subgraph.mdx index 316da18524ef..c0d57cc7fdbe 100644 --- a/website/pages/es/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/es/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/es/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/es/subgraphs/developing/creating/subgraph-manifest.mdx index d8d4f07fd43a..2f8be52bbabf 100644 --- a/website/pages/es/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/es/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). Las entradas importantes a actualizar para el manifiesto son: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/es/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/es/subgraphs/developing/creating/unit-testing-framework.mdx index 63f6babad3d9..750d57c0199f 100644 --- a/website/pages/es/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/es/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,7 @@ La salida del log incluye la duración de la ejecución de la prueba. Aquí hay > 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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx index 42e3a9f0b06a..432d11daa85f 100644 --- a/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/es/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### Compatibilidad de los Subgrafos con The Graph Network In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - No debe utilizar ninguna de las siguientes funciones: - ipfs.cat & ipfs.map - Errores no fatales @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Archivado Automático de Versiones de Subgrafos diff --git a/website/pages/es/subgraphs/developing/developer-faq.mdx b/website/pages/es/subgraphs/developing/developer-faq.mdx index 6c241eab68d0..370adeca6839 100644 --- a/website/pages/es/subgraphs/developing/developer-faq.mdx +++ b/website/pages/es/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ Tienes que volver a realizar el deploy del subgrafo, pero si el ID del subgrafo ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ Si sólo se crea una entidad durante el evento y si no hay nada mejor disponible ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -Puedes encontrar la lista de redes admitidas [aquí](/developing/supported-networks/). +Puedes encontrar la lista de redes admitidas [aquí](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/es/subgraphs/developing/introduction.mdx b/website/pages/es/subgraphs/developing/introduction.mdx index 9f172dd06432..4ee907fc2d63 100644 --- a/website/pages/es/subgraphs/developing/introduction.mdx +++ b/website/pages/es/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Desarrollando --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Descripción @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 7874a463e93a..96dfaf9a5267 100644 --- a/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/es/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Actualización de los metadatos de un subgrafo publicado @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/es/subgraphs/developing/subgraphs.mdx b/website/pages/es/subgraphs/developing/subgraphs.mdx index f41177ea6fbf..d8491793cf27 100644 --- a/website/pages/es/subgraphs/developing/subgraphs.mdx +++ b/website/pages/es/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/es/subgraphs/explorer.mdx b/website/pages/es/subgraphs/explorer.mdx index cf0be13a6c6a..897fbebaa513 100644 --- a/website/pages/es/subgraphs/explorer.mdx +++ b/website/pages/es/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Para obtener más información sobre cómo convertirte en un Indexador, puedes consultar la [documentación oficial](/network/indexing/) o [The Graph Academy Indexer Guides.](https://thegraph.academy/delegators/ eligiendo-indexadores/) +Para obtener más información sobre cómo convertirte en un Indexador, puedes consultar la [documentación oficial](/indexing/overview/) o [The Graph Academy Indexer Guides.](https://thegraph.academy/delegators/ eligiendo-indexadores/) ![Panel de detalles de indexación](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Imagen de Explorer 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegadores @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Cantidad total de GRT que tienen actualmente dentro del protocolo - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Red diff --git a/website/pages/es/subgraphs/querying/best-practices.mdx b/website/pages/es/subgraphs/querying/best-practices.mdx index 94161ebe9fbe..187a081ae419 100644 --- a/website/pages/es/subgraphs/querying/best-practices.mdx +++ b/website/pages/es/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Cada `queryName` sólo debe utilizarse una vez por operación. - Cada `field` debe utilizarse una sola vez en una selección (no podemos consultar el `id` dos veces bajo `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Cualquier variable asignada a un argumento debe coincidir con su tipo. - En una lista dada de variables, cada una de ellas debe ser única. - Deben utilizarse todas las variables definidas. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Envío de una consulta a una API GraphQL @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Manejo de subgrafos cross-chain: Consulta de varios subgrafos en una sola consulta - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/es/subgraphs/querying/graphql-api.mdx b/website/pages/es/subgraphs/querying/graphql-api.mdx index a85ec5413f85..be7916ba2ac8 100644 --- a/website/pages/es/subgraphs/querying/graphql-api.mdx +++ b/website/pages/es/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/es/subgraphs/querying/introduction.mdx b/website/pages/es/subgraphs/querying/introduction.mdx index 270d1803e092..22f8fb7f3a38 100644 --- a/website/pages/es/subgraphs/querying/introduction.mdx +++ b/website/pages/es/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Consultando The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/es/subgraphs/quick-start.mdx b/website/pages/es/subgraphs/quick-start.mdx index f7c62e51c1f0..7baa8638c0b1 100644 --- a/website/pages/es/subgraphs/quick-start.mdx +++ b/website/pages/es/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Comienzo Rapido --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerrequisitos - Una wallet crypto -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/es/substreams/sps/sps-faq.mdx b/website/pages/es/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/es/substreams/sps/sps-faq.mdx +++ b/website/pages/es/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/es/supported-networks.mdx b/website/pages/es/supported-networks.mdx index 0038019281c5..06d85eb4394b 100644 --- a/website/pages/es/supported-networks.mdx +++ b/website/pages/es/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/fr/about.mdx b/website/pages/fr/about.mdx index 36904a652bd4..8557e5d8f522 100644 --- a/website/pages/fr/about.mdx +++ b/website/pages/fr/about.mdx @@ -24,7 +24,7 @@ Dans le cas de l'exemple mentionné ci-dessus, Bored Ape Yacht Club, vous pouvez Il faudrait des **heures, voire des jours,** pour qu'une application décentralisée (dapp) fonctionnant dans un navigateur obtienne une réponse à ces questions simples. -Une alternative serait de configurer votre propre serveur, de traiter les transactions, de les stocker dans une base de données et de créer une API pour interroger les données. Cependant, cette solution est [coûteuse en ressources](/network/benefits/), nécessite une maintenance constante, présente un point de défaillance unique et compromet d'importantes propriétés de securité essentiels à la décentralisation. +Une alternative serait de configurer votre propre serveur, de traiter les transactions, de les stocker dans une base de données et de créer une API pour interroger les données. Cependant, cette solution est [coûteuse en ressources](/resources/benefits/), nécessite une maintenance constante, présente un point de défaillance unique et compromet d'importantes propriétés de securité essentiels à la décentralisation. Les spécificités de la blockchain, comme la finalité des transactions, les réorganisations de chaîne et les blocs oncles (blocs rejetés lorsque deux blocs sont créés simultanément, ce qui entraîne l'omission d'un bloc de la blockchain.), ajoutent de la complexité au processus, rendant longue et conceptuellement difficile la récupération de résultats précis à partir des données de la blockchain. diff --git a/website/pages/fr/archived/arbitrum/arbitrum-faq.mdx b/website/pages/fr/archived/arbitrum/arbitrum-faq.mdx index 23faf8dab29b..4189fe9885c4 100644 --- a/website/pages/fr/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/fr/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Pour tirer parti de l'utilisation de The Graph sur L2, utilisez ce sélecteur d ## En tant que développeur de subgraphs, consommateur de données, indexeur, curateur ou délégateur, que dois-je faire maintenant ? -Les participants du réseau doivent passer à Arbitrum pour continuer à participer à The Graph Network. Veuillez consulter le [Guide de l'outil de transfert L2](/arbitrum/l2-transfer-tools-guide/) pour une assistance supplémentaire. +Les participants du réseau doivent passer à Arbitrum pour continuer à participer à The Graph Network. Veuillez consulter le [Guide de l'outil de transfert L2](/archived/arbitrum/l2-transfer-tools-guide/) pour une assistance supplémentaire. Toutes les récompenses d'indexation sont désormais entièrement sur Arbitrum. @@ -53,7 +53,7 @@ Tout a été testé minutieusement et un plan d’urgence est en place pour assu ## Les subgraphs existants sur Ethereum fonctionnent  t-ils? -Tous les subgraphs sont désormais sur Arbitrum. Veuillez consulter le [Guide de l'outil de transfert L2](/arbitrum/l2-transfer-tools-guide/) pour vous assurer que vos subgraphs fonctionnent sans problème. +Tous les subgraphs sont désormais sur Arbitrum. Veuillez consulter le [Guide de l'outil de transfert L2](/archived/arbitrum/l2-transfer-tools-guide/) pour vous assurer que vos subgraphs fonctionnent sans problème. ## GRT a-t-il un nouveau contrat intelligent déployé sur Arbitrum ? diff --git a/website/pages/fr/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/fr/archived/arbitrum/l2-transfer-tools-faq.mdx index 45ec79e9d4f9..8e5975340a50 100644 --- a/website/pages/fr/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/fr/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ Ces outils vous obligeront à suivre un ensemble d'étapes spécifiques en fonct ### Puis-je utiliser le même portefeuille que celui que j'utilise sur le réseau principal Ethereum ? -Si vous utilisez un portefeuille [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), vous pouvez utiliser la même adresse. Si votre portefeuille du mainnet Ethereum est un contrat (par exemple un multisig), vous devez alors spécifier une [adresse du portefeuille Arbitrum](/arbitrum/arbitrum-faq/#what-do-i-deed-to-do-to-use-the- graph-on-l2) où votre virement sera envoyé. Veuillez vérifier attentivement l'adresse car tout transfert vers une adresse incorrecte peut entraîner une perte permanente. Si vous souhaitez utiliser un multisig sur L2, veillez à déployer un contrat multisig sur Arbitrum One. +Si vous utilisez un portefeuille [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), vous pouvez utiliser la même adresse. Si votre portefeuille du mainnet Ethereum est un contrat (par exemple un multisig), vous devez alors spécifier une [adresse du portefeuille Arbitrum](/archived/arbitrum/arbitrum-faq/#what-do-i-deed-to-do-to-use-the- graph-on-l2) où votre virement sera envoyé. Veuillez vérifier attentivement l'adresse car tout transfert vers une adresse incorrecte peut entraîner une perte permanente. Si vous souhaitez utiliser un multisig sur L2, veillez à déployer un contrat multisig sur Arbitrum One. Les portefeuilles sur les blockchains EVM comme Ethereum et Arbitrum sont une paire de clés (publiques et privées) que vous créez sans avoir besoin d'interagir avec la blockchain. Ainsi, tout portefeuille créé pour Ethereum fonctionnera également sur Arbitrum sans action supplémentaire. diff --git a/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx index eababee7047d..6606735ac390 100644 --- a/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/fr/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Guide des outils de transfert L2 The Graph a facilité le passage à L2 sur Arbitrum One. Pour chaque participant au protocole, il existe un ensemble d'outils de transfert L2 permettant de rendre le transfert vers L2 transparent pour tous les participants du réseau. Ces outils vous obligeront à suivre un ensemble d’étapes spécifiques en fonction de ce que vous transférez. -Certaines questions fréquentes sur ces outils trouvent leur réponse dans la [FAQ sur les outils de transfert L2](/arbitrum/l2-transfer-tools-faq/). Les FAQ contiennent des explications détaillées sur la façon d'utiliser les outils, leur fonctionnement et les éléments à garder à l'esprit lors de leur utilisation. +Certaines questions fréquentes sur ces outils trouvent leur réponse dans la [FAQ sur les outils de transfert L2](/archived/arbitrum/l2-transfer-tools-faq/). Les FAQ contiennent des explications détaillées sur la façon d'utiliser les outils, leur fonctionnement et les éléments à garder à l'esprit lors de leur utilisation. ## Comment transférer votre subgraph vers Arbitrum (L2) diff --git a/website/pages/fr/archived/sunrise.mdx b/website/pages/fr/archived/sunrise.mdx index 5ca61cbced48..69849570e085 100644 --- a/website/pages/fr/archived/sunrise.mdx +++ b/website/pages/fr/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## À propos de l'indexeur de mise à niveau @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Pourquoi Edge & Node exécutent-ils l'indexeur de mise à niveau ? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/fr/contracts.mdx b/website/pages/fr/contracts.mdx index b609dceaf476..127550aad42f 100644 --- a/website/pages/fr/contracts.mdx +++ b/website/pages/fr/contracts.mdx @@ -14,7 +14,7 @@ Il s'agit du déploiement principal de The Graph Network. ## Réseau principal -Il s'agissait du déploiement initial de The Graph Network. [En savoir plus](/arbitrum/arbitrum-faq/) sur la mise à l'échelle de The Graph avec Arbitrum. +Il s'agissait du déploiement initial de The Graph Network. [En savoir plus](/archived/arbitrum/arbitrum-faq/) sur la mise à l'échelle de The Graph avec Arbitrum. diff --git a/website/pages/fr/indexing/chain-integration-overview.mdx b/website/pages/fr/indexing/chain-integration-overview.mdx index 17b6f3567e6d..7f31c5af51aa 100644 --- a/website/pages/fr/indexing/chain-integration-overview.mdx +++ b/website/pages/fr/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Un processus d'intégration transparent et basé sur la gouvernance a été con ## Étape 1. Intégration technique -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Les équipes lancent le processus d'intégration du protocole en créant un fil de discussion sur le forum [ici](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (sous-catégorie Nouvelles sources de données sous Gouvernance et GIPs ). L'utilisation du modèle de forum par défaut est obligatoire. ## Étape 2. Validation de l'intégration diff --git a/website/pages/fr/indexing/new-chain-integration.mdx b/website/pages/fr/indexing/new-chain-integration.mdx index 465f1652f340..be429aaa1369 100644 --- a/website/pages/fr/indexing/new-chain-integration.mdx +++ b/website/pages/fr/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node devrait synchroniser le subgraph déployé s'il n'y a pas d'erreurs. ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/fr/indexing/overview.mdx b/website/pages/fr/indexing/overview.mdx index 809e92a8fcb0..078a6edb839b 100644 --- a/website/pages/fr/indexing/overview.mdx +++ b/website/pages/fr/indexing/overview.mdx @@ -87,7 +87,7 @@ Une fois qu'une allocation a été clôturée, les remises peuvent être réclam ### Qu'est-ce que la réduction des frais de requête et la réduction des récompenses d'indexation ? -Les valeurs `queryFeeCut` et `indexingRewardCut` sont des paramètres de délégation que l'indexeur peut définir avec cooldownBlocks pour contrôler la distribution du GRT entre l'indexeur et ses délégués. Consultez les dernières étapes dans [Jalonnement dans le protocole](/network/indexing/#stake-in-the-protocol) pour obtenir des instructions sur la définition des paramètres de délégation. +Les valeurs `queryFeeCut` et `indexingRewardCut` sont des paramètres de délégation que l'indexeur peut définir avec cooldownBlocks pour contrôler la distribution du GRT entre l'indexeur et ses délégués. Consultez les dernières étapes dans [Jalonnement dans le protocole](/indexing/overview/#stake-in-the-protocol) pour obtenir des instructions sur la définition des paramètres de délégation. - **queryFeeCut** : % de remise sur les frais de requête qui sera distribuée à l'indexeur. Si ce taux est fixé à 95 %, l'indexeur recevra 95 % des frais de requête gagnés lorsqu'une allocation est clôturée, les 5 % restants étant reversés aux délégateurs. @@ -121,7 +121,7 @@ Les indexeurs peuvent se différencier en appliquant des techniques avancées po ### Quelles sont les précautions de sécurité de base qu’un indexeur doit prendre ? -- **Portefeuille d'opérateur** : la configuration d'un portefeuille d'opérateur est une précaution importante car elle permet à un indexeur de maintenir une séparation entre ses clés qui contrôlent la participation et celles qui contrôlent les opérations quotidiennes. opérations de jour. Voir [Participation dans le protocole](/network/indexing/#stake-in-the-protocol) pour les instructions. +- **Portefeuille d'opérateur** : la configuration d'un portefeuille d'opérateur est une précaution importante car elle permet à un indexeur de maintenir une séparation entre ses clés qui contrôlent la participation et celles qui contrôlent les opérations quotidiennes. opérations de jour. Voir [Participation dans le protocole](/indexing/overview/#stake-in-the-protocol) pour les instructions. - **Pare-feu** : seul le service Indexer doit être exposé publiquement et une attention particulière doit être accordée au verrouillage des ports d'administration et de l'accès à la base de données : le point de terminaison JSON-RPC de Graph Node (port par défaut : 8030), le point de terminaison de l'API de gestion de l'indexeur (port par défaut : 18000) et le point de terminaison de la base de données Postgres (port par défaut : 5432) ne doivent pas être exposés. @@ -375,7 +375,7 @@ Pour participer avec succès au réseau, il faut une surveillance et une interac #### Commencer -L’agent Indexer et le service Indexer doivent être colocalisés avec votre infrastructure Graph Node. Il existe de nombreuses façons de configurer des environnements d'exécution virtuels pour vos composants Indexer ; nous expliquerons ici comment les exécuter sur baremetal à l'aide des packages ou de la source NPM, ou via kubernetes et docker sur Google Cloud Kubernetes Engine. Si ces exemples de configuration ne s'adaptent pas bien à votre infrastructure, il y aura probablement un guide communautaire à consulter, venez nous dire bonjour sur [Discord](https://discord.gg/graphprotocol) ! N'oubliez pas de [participer au protocole](/network/indexing/#stake-in-the-protocol) avant de démarrer vos composants Indexer ! +L’agent Indexer et le service Indexer doivent être colocalisés avec votre infrastructure Graph Node. Il existe de nombreuses façons de configurer des environnements d'exécution virtuels pour vos composants Indexer ; nous expliquerons ici comment les exécuter sur baremetal à l'aide des packages ou de la source NPM, ou via kubernetes et docker sur Google Cloud Kubernetes Engine. Si ces exemples de configuration ne s'adaptent pas bien à votre infrastructure, il y aura probablement un guide communautaire à consulter, venez nous dire bonjour sur [Discord](https://discord.gg/graphprotocol) ! N'oubliez pas de [participer au protocole](/indexing/overview/#stake-in-the-protocol) avant de démarrer vos composants Indexer ! #### À partir des packages NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Utilisation de K8s et Terraform -Consultez la section [Configurer l'infrastructure du serveur à l'aide de Terraform sur Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Consultez la section [Configurer l'infrastructure du serveur à l'aide de Terraform sur Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Usage @@ -755,7 +755,7 @@ Les premières étapes pour participer au réseau en tant qu'Indexeur sont d'app > Note : Pour les besoins de ces instructions, Remix sera utilisé pour l'interaction avec le contrat, mais n'hésitez pas à utiliser l'outil de votre choix ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), et [MyCrypto](https://www.mycrypto.com/account) sont quelques autres outils connus). -Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l'indexeur](/network/indexing/#indexer-components) peuvent être démarrés et commencer leurs interactions avec le réseau. +Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l'indexeur](/indexing/overview/#indexer-components) peuvent être démarrés et commencer leurs interactions avec le réseau. #### Approuver les jetons @@ -815,6 +815,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Une fois qu'une allocation est créée on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) elle est considérée comme **active**. Une partie du staking de l'Indexeur et/ou du staking délégué est allouée à un déploiement de subgraph, ce qui leur permet de réclamer des récompenses d'indexation et de servir des requêtes pour ce déploiement de subgraph. L'agent Indexeur gère la création des allocations en fonction des règles de l'Indexeur. -- **Closed** - Un Indexeur est libre de fermer une allocation une fois qu'une époque est passée ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) ou son agent Indexeur fermera automatiquement l'allocation après le **maxAllocationEpochs** (actuellement 28 jours). Lorsqu'une allocation est fermée avec une preuve d'indexation (POI) valide, leurs récompenses d'indexation sont distribuées à l'Indexeur et à ses Délégateurs ([en savoir plus](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - Un Indexeur est libre de fermer une allocation une fois qu'une époque est passée ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) ou son agent Indexeur fermera automatiquement l'allocation après le **maxAllocationEpochs** (actuellement 28 jours). Lorsqu'une allocation est fermée avec une preuve d'indexation (POI) valide, leurs récompenses d'indexation sont distribuées à l'Indexeur et à ses Délégateurs ([en savoir plus](/indexing/overview/#how-are-indexing-rewards-distributed)). Il est recommandé aux indexeurs d'utiliser la fonctionnalité de synchronisation hors chaîne pour synchroniser les déploiements de subgraphs avec Chainhead avant de créer l'allocation en chaîne. Cette fonctionnalité est particulièrement utile pour les sous-graphes dont la synchronisation peut prendre plus de 28 époques ou qui risquent d'échouer de manière indéterministe. diff --git a/website/pages/fr/indexing/tap.mdx b/website/pages/fr/indexing/tap.mdx index 3430199911ab..bf5c6eb3988f 100644 --- a/website/pages/fr/indexing/tap.mdx +++ b/website/pages/fr/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notez : -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/fr/resources/benefits.mdx b/website/pages/fr/resources/benefits.mdx index 89b0bf8a2d4f..280df951b5ff 100644 --- a/website/pages/fr/resources/benefits.mdx +++ b/website/pages/fr/resources/benefits.mdx @@ -76,7 +76,7 @@ Les coûts d'interrogation peuvent varier ; le coût indiqué est la moyenne au ‡Reflète le coût pour le consommateur de données. Les frais de requête sont toujours payés aux Indexeurs pour les requêtes du Plan Gratuit. -Les coûts estimés sont uniquement pour les subgraphs Ethereum Mainnet - les coûts sont encore plus élevés lorsqu'on héberge soi-même un `graph-node` sur d'autres réseaux. Certains utilisateurs peuvent avoir besoin de mettre à jour leur subgraph vers une nouvelle version. En raison des frais de gaz Ethereum, une mise à jour coûte ~50 $ au moment de la rédaction. Notez que les frais de gaz sur [Arbitrum](/arbitrum/arbitrum-faq/) sont considérablement plus bas que ceux d'Ethereum mainnet. +Les coûts estimés sont uniquement pour les subgraphs Ethereum Mainnet - les coûts sont encore plus élevés lorsqu'on héberge soi-même un `graph-node` sur d'autres réseaux. Certains utilisateurs peuvent avoir besoin de mettre à jour leur subgraph vers une nouvelle version. En raison des frais de gaz Ethereum, une mise à jour coûte ~50 $ au moment de la rédaction. Notez que les frais de gaz sur [Arbitrum](/archived/arbitrum/arbitrum-faq/) sont considérablement plus bas que ceux d'Ethereum mainnet. Émettre un signal sur un subgraph est un cout net, nul optionnel et unique (par exemple, 1 000 $ de signal peuvent être conservés sur un subgraph, puis retirés - avec la possibilité de gagner des revenus au cours du processus). @@ -90,4 +90,4 @@ Le réseau décentralisé du Graph permet aux utilisateurs d'accéder à une red En résumé : Le réseau de graphs est moins coûteux, plus facile à utiliser et produit des résultats supérieurs à ceux obtenus par l'exécution locale d'un `nœud de graphs`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/fr/resources/roles/curating.mdx b/website/pages/fr/resources/roles/curating.mdx index fb3d73259617..8d6ca943b109 100644 --- a/website/pages/fr/resources/roles/curating.mdx +++ b/website/pages/fr/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Les signaux des Curateurs sont représentés par des jetons ERC20 appelés Graph Curation Shares (GCS). Ceux qui veulent gagner plus de frais de requête doivent signaler leurs GRT aux subgraphs qui, selon eux, généreront un flux important de frais pour le réseau. Les Curateurs ne peuvent pas être réduits pour mauvais comportement, mais il y a une taxe de dépôt sur les Curateurs pour dissuader les mauvaises décisions pouvant nuire à l'intégrité du réseau. Les Curateurs gagneront également moins de frais de requête s'ils sélectionnent un subgraph de mauvaise qualité car il y aura moins de requêtes à traiter ou moins d'Indexeurs pour les traiter. -Le [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) garantit l'indexation de tous les subgraphs. Signaler du GRT sur un subgraph particulier attirera plus d'indexeurs. Cette incitation d'indexeurs supplémentaires à travers la curation vise à améliorer la qualité du service pour les requêtes en réduisant la latence et en améliorant la disponibilité du réseau. +Le [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) garantit l'indexation de tous les subgraphs. Signaler du GRT sur un subgraph particulier attirera plus d'indexeurs. Cette incitation d'indexeurs supplémentaires à travers la curation vise à améliorer la qualité du service pour les requêtes en réduisant la latence et en améliorant la disponibilité du réseau. Lors du signalement, les Curateurs peuvent décider de signaler une version spécifique du subgraph ou de signaler en utilisant l'auto-migration. S'ils signalent en utilisant l'auto-migration, les parts d'un Curateur seront toujours mises à jour vers la dernière version publiée par le développeur. S'ils décident de signaler une version spécifique, les parts resteront toujours sur cette version spécifique. @@ -24,7 +24,7 @@ Les Indexeurs peuvent trouver des subgraphs à indexer en fonction des signaux d ## Comment signaler -Dans l'onglet Curateur de Graph Explorer, les Curateurs pourront signaler et dé-signaler certains subgraphs en fonction des statistiques du réseau. Pour un aperçu étape par étape de la procédure à suivre dans Graph Explorer, [cliquez ici.](/network/explorer/) +Dans l'onglet Curateur de Graph Explorer, les Curateurs pourront signaler et dé-signaler certains subgraphs en fonction des statistiques du réseau. Pour un aperçu étape par étape de la procédure à suivre dans Graph Explorer, [cliquez ici.](/subgraphs/explorer/) Un curateur peut choisir de signaler une version spécifique d'un sugraph ou de faire migrer automatiquement son signal vers la version de production la plus récente de ce subgraph. Ces deux stratégies sont valables et comportent leurs propres avantages et inconvénients. @@ -48,7 +48,7 @@ Cependant, il est recommandé que les Curateurs laissent leur GRT signalé en pl 1. Le marché des requêtes est intrinsèquement jeune chez The Graph et il y a un risque que votre %APY soit inférieur à vos attentes en raison de la dynamique naissante du marché. 2. Frais de curation - lorsqu'un Curateur signale des GRT sur un subgraph, il doit s'acquitter d'une taxe de curation de 1%. Cette taxe est brûlée. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Un subgraph peut échouer à cause d'un bug. Un subgraph qui échoue n'accumule pas de frais de requête. Par conséquent, vous devrez attendre que le développeur corrige le bogue et déploie une nouvelle version. - Si vous êtes abonné à la version la plus récente d'un subgraph, vos parts migreront automatiquement vers cette nouvelle version. Cela entraînera une taxe de curation de 0,5 %. - Si vous avez signalé sur une version spécifique d'un subgraph et qu'elle échoue, vous devrez brûler manuellement vos parts de curation. Vous pouvez alors signaler sur la nouvelle version du subgraph, encourant ainsi une taxe de curation de 1%. diff --git a/website/pages/fr/resources/tokenomics.mdx b/website/pages/fr/resources/tokenomics.mdx index c7bafa41af3b..96a7cd4d787a 100644 --- a/website/pages/fr/resources/tokenomics.mdx +++ b/website/pages/fr/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Interroger un subgraph existant -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/fr/subgraphs/billing.mdx b/website/pages/fr/subgraphs/billing.mdx index 610c9ff09b00..86a5197e3e6f 100644 --- a/website/pages/fr/subgraphs/billing.mdx +++ b/website/pages/fr/subgraphs/billing.mdx @@ -15,7 +15,7 @@ Il y a deux plans à utiliser lorsqu'on interroge les subgraphs sur le réseau d ## Paiements de Requêtes avec Carte de Crédit⁠ - Pour mettre en place la facturation par carte de crédit/débit, les utilisateurs doivent accéder à Subgraph Studio (https://thegraph.com/studio/) - 1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/billing/). + 1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Cliquez sur le bouton "Connecter le portefeuille" dans le coin supérieur droit de la page. Vous serez redirigé vers la page de sélection des portefeuilles. Sélectionnez votre portefeuille et cliquez sur "Connecter". 3. Choisissez « Mettre à niveau votre abonnement » si vous effectuez une mise à niveau depuis le plan gratuit, ou choisissez « Gérer l'abonnement » si vous avez déjà ajouté des GRT à votre solde de facturation par le passé. Ensuite, vous pouvez estimer le nombre de requêtes pour obtenir une estimation du prix, mais ce n'est pas une étape obligatoire. 4. Pour choisir un paiement par carte de crédit, choisissez “Credit card” comme mode de paiement et remplissez les informations de votre carte de crédit. Ceux qui ont déjà utilisé Stripe peuvent utiliser la fonctionnalité Link pour remplir automatiquement leurs informations. @@ -50,7 +50,7 @@ Une fois que vous avez transféré du GRT, vous pouvez l'ajouter à votre solde ### Ajout de GRT à l'aide d'un portefeuille -1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/billing/). +1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Cliquez sur le bouton "Connecter le portefeuille" dans le coin supérieur droit de la page. Vous serez redirigé vers la page de sélection des portefeuilles. Sélectionnez votre portefeuille et cliquez sur "Connecter". 3. Cliquez sur le bouton « Manage » situé dans le coin supérieur droit. Les nouveaux utilisateurs verront l'option « Upgrade to Growth plan » (Passer au plan de croissance), tandis que les utilisateurs existants devront sélectionner « Deposit from wallet » (Déposer depuis le portefeuille). 4. Utilisez le curseur pour estimer le nombre de requêtes que vous prévoyez d’effectuer sur une base mensuelle. @@ -67,7 +67,7 @@ Une fois que vous avez transféré du GRT, vous pouvez l'ajouter à votre solde ### Retirer des GRT en utilisant un portefeuille -1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/billing/). +1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Cliquez sur le bouton "Connect Wallet" dans le coin supérieur droit de la page. Sélectionnez votre portefeuille et cliquez sur "Connect". 3. Cliquez sur le bouton « Gérer » dans le coin supérieur droit de la page. Sélectionnez « Retirer des GRT ». Un panneau latéral apparaîtra. 4. Entrez le montant de GRT que vous voudriez retirer. @@ -76,7 +76,7 @@ Une fois que vous avez transféré du GRT, vous pouvez l'ajouter à votre solde ### Ajout de GRT à l'aide d'un portefeuille multisig -1. Allez à la page [Facturation de Studio Subgraph](https://thegraph.com/studio/billing/). +1. Allez à la page [Facturation de Studio Subgraph](https://thegraph.com/studio/subgraphs/billing/). 2. Cliquez sur le bouton "Connect Wallet" dans le coin supérieur droit de la page. Sélectionnez votre portefeuille et cliquez sur "Connect". Si vous utilisez [Gnosis-Safe](https://gnosis-safe.io/), vous pourrez connecter votre multisig ainsi que votre portefeuille de signature. Ensuite, signez le message associé. Cela ne coûtera aucun gaz. 3. Cliquez sur le bouton « Manage » situé dans le coin supérieur droit. Les nouveaux utilisateurs verront l'option « Upgrade to Growth plan » (Passer au plan de croissance), tandis que les utilisateurs existants devront sélectionner « Deposit from wallet » (Déposer depuis le portefeuille). 4. Utilisez le curseur pour estimer le nombre de requêtes que vous prévoyez d’effectuer sur une base mensuelle. diff --git a/website/pages/fr/subgraphs/cookbook/arweave.mdx b/website/pages/fr/subgraphs/cookbook/arweave.mdx index b65102acbee9..b399d29205ce 100644 --- a/website/pages/fr/subgraphs/cookbook/arweave.mdx +++ b/website/pages/fr/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ La définition du schéma décrit la structure de la base de données de subgrap Les gestionnaires pour le traitement des événements sont écrits en [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Interroger un subgraph d'Arweave -Le endpoint GraphQL pour les subgraphs d'Arweave est déterminé par la définition du schema, avec l'interface API existante. Veuillez consulter la [documentation de l'API GraphQL](/querying/graphql-api/) pour plus d'informations. +Le endpoint GraphQL pour les subgraphs d'Arweave est déterminé par la définition du schema, avec l'interface API existante. Veuillez consulter la [documentation de l'API GraphQL](/subgraphs/querying/graphql-api/) pour plus d'informations. ## Exemples de subgraphs diff --git a/website/pages/fr/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/fr/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/fr/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/fr/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/fr/subgraphs/cookbook/cosmos.mdx b/website/pages/fr/subgraphs/cookbook/cosmos.mdx index ed318635f292..9c3a34c52a37 100644 --- a/website/pages/fr/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/fr/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and Les gestionnaires pour le traitement des événements sont écrits en [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Interroger un subgraph de Cosmos -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Blockchains Cosmos prises en charge diff --git a/website/pages/fr/subgraphs/cookbook/derivedfrom.mdx b/website/pages/fr/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/fr/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/fr/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/fr/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/fr/subgraphs/cookbook/grafting-hotfix.mdx index fd32ece68e7e..57cd57c1250f 100644 --- a/website/pages/fr/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/fr/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Ressources additionnelles -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/fr/subgraphs/cookbook/grafting.mdx b/website/pages/fr/subgraphs/cookbook/grafting.mdx index b092fd08232e..dd8dd3f5223a 100644 --- a/website/pages/fr/subgraphs/cookbook/grafting.mdx +++ b/website/pages/fr/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ En respectant ces lignes directrices, vous minimisez les risques et vous vous as ## Création d'un subgraph existant -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Exemple de subgraph repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Notez : Une grande partie de cet article a été reprise de l'[article Arweave](/cookbook/arweave/) publié précédemment +> Notez : Une grande partie de cet article a été reprise de l'[article Arweave](/subgraphs/cookbook/arweave/) publié précédemment diff --git a/website/pages/fr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/fr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/fr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/fr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/fr/subgraphs/cookbook/near.mdx b/website/pages/fr/subgraphs/cookbook/near.mdx index b3c4cb30bff2..746a00050407 100644 --- a/website/pages/fr/subgraphs/cookbook/near.mdx +++ b/website/pages/fr/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ La définition d'un subgraph comporte trois aspects : **schema.graphql** : un fichier de schéma qui définit quelles données sont stockées pour votre subgraph, et comment les interroger via GraphQL. Les exigences pour les subgraphs NEAR sont couvertes par la [documentation existante](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. Lors du développement du subgraph, il y a deux commandes clés : @@ -98,7 +98,7 @@ La définition du schema décrit la structure de la base de données de subgraph Les gestionnaires de traitement des événements sont écrits dans l'[AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Ces types sont passés au bloc & gestionnaires de reçus : - Les gestionnaires de blocs reçoivent un `Block` - Les gestionnaires de reçus reçoivent un `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Déploiement d'un subgraph NEAR @@ -228,7 +228,7 @@ Nous fournirons bientôt plus d'informations sur l'utilisation des composants ci ## Interrogation d'un subgraph NEAR -Le point de terminaison GraphQL pour les subgraphs NEAR est déterminé par la définition du schéma, avec l'interface API existante. Veuillez consulter la [documentation de l'API GraphQL](/querying/graphql-api/) pour plus d'informations. +Le point de terminaison GraphQL pour les subgraphs NEAR est déterminé par la définition du schéma, avec l'interface API existante. Veuillez consulter la [documentation de l'API GraphQL](/subgraphs/querying/graphql-api/) pour plus d'informations. ## Des exemples de subgraphs @@ -276,7 +276,7 @@ La fonctionnalité "pending" n'est pas encore prise en charge pour les subgraphs ### Ma question n'a pas reçu de réponse, où puis-je obtenir plus d'aide concernant la création de subgraphs NEAR ? -S'il s'agit d'une question générale sur le développement de subgraphs, il y a beaucoup plus d'informations dans le reste de la [Documentation du développeur](/quick-start/). Sinon, veuillez rejoindre [The Graph Protocol Discord](https://discord.gg/graphprotocol) et poser votre question sur le canal #near ou par e-mail à near@thegraph.com. +S'il s'agit d'une question générale sur le développement de subgraphs, il y a beaucoup plus d'informations dans le reste de la [Documentation du développeur](/subgraphs/quick-start/). Sinon, veuillez rejoindre [The Graph Protocol Discord](https://discord.gg/graphprotocol) et poser votre question sur le canal #near ou par e-mail à near@thegraph.com. ## Les Références diff --git a/website/pages/fr/subgraphs/cookbook/pruning.mdx b/website/pages/fr/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/fr/subgraphs/cookbook/pruning.mdx +++ b/website/pages/fr/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 1a57fffc4121..76186d597c7a 100644 --- a/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/fr/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Subgraphs alimentés par Substreams --- -[Substreams](/substreams/) est un nouveau framework de traitement des données blockchain, développé par StreamingFast pour The Graph Network. Un module de sous-flux peut générer des modifications d'entité, qui sont compatibles avec les entités Subgraph. Un subgraph peut utiliser un tel module Substreams comme source de données, apportant la vitesse d'indexation et les données supplémentaires des Substreams aux développeurs de subgraphs. +[Substreams](/substreams/introduction/) est un nouveau framework de traitement des données blockchain, développé par StreamingFast pour The Graph Network. Un module de sous-flux peut générer des modifications d'entité, qui sont compatibles avec les entités Subgraph. Un subgraph peut utiliser un tel module Substreams comme source de données, apportant la vitesse d'indexation et les données supplémentaires des Substreams aux développeurs de subgraphs. ## Exigences @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Définir un package Substreams -Un paquet Substreams est composé de types (définis comme [Protocol Buffers](https://protobuf.dev/)), de modules (écrits en Rust) et d'un fichier `substreams.yaml` qui référence les types et spécifie comment les modules sont déclenchés. [Visitez la documentation Substreams pour en savoir plus sur le développement de Substreams](/substreams/), et consultez [awesome-substreams](https://github.com/pinax-network/awesome-substreams) et le [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) pour plus d'exemples. +Un paquet Substreams est composé de types (définis comme [Protocol Buffers](https://protobuf.dev/)), de modules (écrits en Rust) et d'un fichier `substreams.yaml` qui référence les types et spécifie comment les modules sont déclenchés. [Visitez la documentation Substreams pour en savoir plus sur le développement de Substreams](/substreams/introduction/), et consultez [awesome-substreams](https://github.com/pinax-network/awesome-substreams) et le [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) pour plus d'exemples. Le package Substreams en question détecte les déploiements de contrats sur Mainnet Ethereum, en suivant le bloc de création et l'horodatage de tous les contrats nouvellement déployés. Pour ce faire, il existe un type `Contract` dédié dans `/proto/example.proto` ([en savoir plus sur la définition des tampons de protocole](https://protobuf.dev/programming-guides/proto3/#simple)) : diff --git a/website/pages/fr/subgraphs/cookbook/timeseries.mdx b/website/pages/fr/subgraphs/cookbook/timeseries.mdx index 44d7eca76ee9..82176f96bdfd 100644 --- a/website/pages/fr/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/fr/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/fr/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/fr/subgraphs/cookbook/transfer-to-the-graph.mdx index 3ffe317f8063..6078975a20a3 100644 --- a/website/pages/fr/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/fr/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Exemple @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Ressources additionnelles -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/fr/subgraphs/developing/creating/advanced.mdx b/website/pages/fr/subgraphs/developing/creating/advanced.mdx index 9788771e2158..68c04eec3ad8 100644 --- a/website/pages/fr/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/fr/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Si la relation est 1:1 entre l'entité parent et l'entité de source de données de fichier résultante, le modèle le plus simple consiste à lier l'entité parent à une entité de fichier résultante en utilisant le CID IPFS comme recherche. Contactez Discord si vous rencontrez des difficultés pour modéliser vos nouvelles entités basées sur des fichiers ! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### Créer un nouveau gestionnaire pour traiter les fichiers -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ En outre, il n'est pas possible de créer des sources de données à partir d'un Si vous liez des métadonnées NFT aux jetons correspondants, utilisez le hachage IPFS des métadonnées pour référencer une entité Metadata à partir de l'entité Token. Enregistrez l'entité Metadata en utilisant le hachage IPFS comme identifiant. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Greffe sur des subgraphs existants -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx index 38125106319c..4ec8c6d6ebb0 100644 --- a/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/fr/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: API AssemblyScript --- -> Remarque : Si vous avez créé un subgraph avant la version `graph-cli`/`graph-ts` `0.22.0`, alors vous utilisez une ancienne version d'AssemblyScript. Il est recommandé de consulter le [`Guide de Migration `] (/release-notes/assemblyscript-migration-guide). +> Remarque : Si vous avez créé un subgraph avant la version `graph-cli`/`graph-ts` `0.22.0`, alors vous utilisez une ancienne version d'AssemblyScript. Il est recommandé de consulter le [`Guide de Migration `] (/resources/release-notes/assemblyscript-migration-guide/). Découvrez quelles APIs intégrées peuvent être utilisées lors de l'écriture des mappages de subgraph. Il existe deux types d'APIs disponibles par défaut : @@ -35,7 +35,7 @@ La `apiVersion` dans le manifeste du subgraph spécifie la version de l'API de m | 0.0.8 | Ajout de la validation pour l'existence des champs dans le schéma lors de l'enregistrement d'une entité. | | 0.0.7 | Ajout des classes `TransactionReceipt` et `Log`aux types Ethereum
Ajout du champ `receipt` à l'objet Ethereum Event | | 0.0.6 | Ajout du champ `nonce` à l'objet Ethereum Transaction
Ajout de `baseFeePerGas` à l'objet Ethereum Block | -| 0.0.5 | AssemblyScript a été mis à niveau vers la version 0.19.10 (ceci inclut des changements importants, veuillez consulter le [`Guide de Migration`](/release-notes/assemblyscript-migration-guide/))
. `ethereum.transaction.gasUsed` est renommé en `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript a été mis à niveau vers la version 0.19.10 (ceci inclut des changements importants, veuillez consulter le [`Guide de Migration`](/resources/release-notes/assemblyscript-migration-guide/))
. `ethereum.transaction.gasUsed` est renommé en `ethereum.transaction.gasLimit` | | 0.0.4 | Ajout du champ `functionSignature` à l'objet Ethereum SmartContractCall | | 0.0.3 | Ajout du champ `from` à l'objet Ethereum Call
`etherem.call.address` est renommé en `ethereum.call.to` | | 0.0.2 | Ajout du champ `input` à l'objet Ethereum Transaction | diff --git a/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx index d5f137f2260f..bf710d6b1844 100644 --- a/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/fr/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Installation du Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Aperçu -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Démarrage @@ -114,6 +114,6 @@ Le(s) fichier(s) ABI doivent correspondre à votre(vos) contrat(s). Il existe pl | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Ajout de la prise en charge des gestionnaires d'événement ayant accès aux reçus de transactions. | | 0.0.4 | Ajout de la prise en charge du management des fonctionnalités de subgraph. | diff --git a/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx b/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx index 69dd84eb35e3..168976049040 100644 --- a/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/fr/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Définition des entités @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/fr/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/fr/subgraphs/developing/creating/starting-your-subgraph.mdx index 423512bd80bc..6a7795812160 100644 --- a/website/pages/fr/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/fr/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/fr/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/fr/subgraphs/developing/creating/subgraph-manifest.mdx index a7c76c52d491..f7f957f5741a 100644 --- a/website/pages/fr/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/fr/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ les sources de données: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). Les entrées importantes à mettre à jour pour le manifeste sont : @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde L'historique à partir d'un bloc donné est requis pour : -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rembobiner le subgraph jusqu'à ce bloc @@ -517,7 +517,7 @@ Si les données historiques à partir du bloc ont été purgées, les capacités > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: Pour conserver une quantité spécifique de données historiques : diff --git a/website/pages/fr/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/fr/subgraphs/developing/creating/unit-testing-framework.mdx index 5fa8e45fb1b2..0a63c492dac1 100644 --- a/website/pages/fr/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/fr/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1364,7 +1364,7 @@ La sortie du journal inclut la durée de l’exécution du test. Voici un exempl > Critique : impossible de créer WasmInstance à partir d'un module valide avec un contexte : importation inconnue : wasi_snapshot_preview1::fd_write n'a pas été défini -Ceci signifie que vous avez utilisé `console.log` dans votre code, ce qui n'est pas pris en charge par AssemblyScript. Veuillez envisager d'utiliser l'[API de journalisation](/developing/graph-ts/api/#logging-api) +Ceci signifie que vous avez utilisé `console.log` dans votre code, ce qui n'est pas pris en charge par AssemblyScript. Veuillez envisager d'utiliser l'[API de journalisation](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERREUR TS2554 : attendu ? arguments, mais j'ai eu ?. > diff --git a/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx index 5650501b53fd..0f876db3e325 100644 --- a/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/fr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> Pour des informations supplémentaires écrites, consultez le [Quick Start](/quick-start/). +> Pour des informations supplémentaires écrites, consultez le [Quick Start](/subgraphs/quick-start/). ### Compatibilité des subgraphs avec le réseau de The Graph Pour être pris en charge par les Indexeurs sur The Graph Network, les subgraphs doivent : -- Indexer un [réseau pris en charge](/developing/supported-networks/) +- Indexer un [réseau pris en charge](/supported-networks/) - Ne doit utiliser aucune des fonctionnalités suivantes : - ipfs.cat & ipfs.map - Erreurs non fatales @@ -114,7 +114,7 @@ Utilisez Subgraph Studio pour vérifier les journaux (logs) sur le tableau de bo ## Publiez votre subgraph -Pour publier votre subgraph avec succès, consultez la page [publier un subgraph](/publishing/publishing-a-subgraph/). +Pour publier votre subgraph avec succès, consultez la page [publier un subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versionning de votre subgraph avec le CLI @@ -126,7 +126,7 @@ Si vous souhaitez mettre à jour votre subgraph, vous pouvez faire ce qui suit : Vous pouvez également mettre à jour les métadonnées de votre subgraph sans publier une nouvelle version. Vous pouvez mettre à jour les détails de votre subgraph dans Studio (sous la photo de profil, le nom, la description, etc.) en cochant une option appelée **Update Details** dans [Graph Explorer](https://thegraph.com/explorer). Si cette option est cochée, une transaction sera générée sur la blockchain (on-chain) pour mettre à jour les détails du subgraph dans Explorer sans avoir à publier une nouvelle version avec un nouveau déploiement. -> Remarque : Il y a des coûts associés à la publication d'une nouvelle version d'un subgraph sur le réseau. En plus des frais de transaction, vous devez également financer une partie de la taxe de curation sur le signal d'auto-migration . Vous ne pouvez pas publier une nouvelle version de votre subgraph si les Curateurs n'ont pas signalé dessus. Pour plus d'informations, veuillez lire plus [ici](/network/curating/). +> Remarque : Il y a des coûts associés à la publication d'une nouvelle version d'un subgraph sur le réseau. En plus des frais de transaction, vous devez également financer une partie de la taxe de curation sur le signal d'auto-migration . Vous ne pouvez pas publier une nouvelle version de votre subgraph si les Curateurs n'ont pas signalé dessus. Pour plus d'informations, veuillez lire plus [ici](/resources/roles/curating/). ## Archivage automatique des versions de subgraphs diff --git a/website/pages/fr/subgraphs/developing/developer-faq.mdx b/website/pages/fr/subgraphs/developing/developer-faq.mdx index 55e93b41e6fb..5052da626232 100644 --- a/website/pages/fr/subgraphs/developing/developer-faq.mdx +++ b/website/pages/fr/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ Un subgraph est une API personnalisée construite sur des données blockchain. L ### 2. Quelle est la première étape pour créer un subgraph ? -Pour créer avec succès un subgraph, vous devrez installer Graph CLI. Consultez le [guide de démarrage rapide](/quick-start/) pour commencer. Pour des informations détaillées, voir [Création d'un subgraph](/developing/creating-a-subgraph/). +Pour créer avec succès un subgraph, vous devrez installer Graph CLI. Consultez le [guide de démarrage rapide](/subgraphs/quick-start/) pour commencer. Pour des informations détaillées, voir [Création d'un subgraph](/developing/creating-a-subgraph/). ### 3. Suis-je toujours en mesure de créer un subgraph si mes smart contracts n'ont pas d'événements ? @@ -34,7 +34,7 @@ Vous devez redéployer le subgraph, mais si l'ID de subgraph (hachage IPFS) ne c ### 7. Comment puis-je appeler une fonction d'un contrat ou accéder à une variable d'état publique depuis mes mappages de subgraph ? -Consultez `Accès à l'état du contrat intelligent` dans la section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Consultez `Accès à l'état du contrat intelligent` dans la section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Puis-je importer `ethers.js` ou d'autres bibliothèques JS dans mes mappages de subgraph ? @@ -80,13 +80,13 @@ Si une seule entité est créée lors de l'événement et s'il n'y a rien de mie ### 15. Puis-je supprimer mon subgraph ? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Relatif au Réseau ### 16. Quels réseaux sont supportés par The Graph? -Vous pouvez trouver la liste des réseaux supportés [ici](/developing/supported-networks/). +Vous pouvez trouver la liste des réseaux supportés [ici](/supported-networks/). ### 17. Est-il possible de faire la différence entre les réseaux (mainnet, Sepolia, local) dans les gestionnaires d'événements? diff --git a/website/pages/fr/subgraphs/developing/introduction.mdx b/website/pages/fr/subgraphs/developing/introduction.mdx index dd4512515ba2..330e2be76d8b 100644 --- a/website/pages/fr/subgraphs/developing/introduction.mdx +++ b/website/pages/fr/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Le Développement --- -Pour commencer à coder immédiatement, rendez-vous sur [Démarrage rapide pour développeurs](/quick-start/). +Pour commencer à coder immédiatement, rendez-vous sur [Démarrage rapide pour développeurs](/subgraphs/quick-start/). ## Aperçu @@ -27,4 +27,4 @@ Sur The Graph, vous pouvez : Un subgraph est une API personnalisée construite sur des données blockchain. Il extrait des données d'une blockchain, les traite et les stocke afin qu'elles puissent être facilement interrogées via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 8e809cf0b720..bbc439508dd1 100644 --- a/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/fr/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Une fois que vous avez [déployé votre subgraph sur Subgraph Studio](/deploying Lorsque vous publiez un subgraph sur le réseau décentralisé, vous le rendez disponible pour : -- [Les Curateurs](/network/curating/), qui peuvent commencer à le curer. -- [Les Indexeurs](/network/indexing/), qui peuvent commencer à l’indexer. +- [Les Curateurs](/resources/roles/curating/), qui peuvent commencer à le curer. +- [Les Indexeurs](/indexing/overview/), qui peuvent commencer à l’indexer. -Consultez la liste des [réseaux pris en charge](/developing/supported-networks/). +Consultez la liste des [réseaux pris en charge](/supported-networks/). ## Publication à partir de Subgraph Studio @@ -21,9 +21,9 @@ Consultez la liste des [réseaux pris en charge](/developing/supported-networks/ Toutes les versions publiées d'un subgraph existant peuvent : -- Être publiées sur Arbitrum One. [En savoir plus sur The Graph Network sur Arbitrum](/arbitrum/arbitrum-faq/). +- Être publiées sur Arbitrum One. [En savoir plus sur The Graph Network sur Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Indexer des données sur l'un des [réseaux pris en charge](/developing/supported-networks/), quel que soit le réseau sur lequel le subgraph a été publié. +- Indexer des données sur l'un des [réseaux pris en charge](/supported-networks/), quel que soit le réseau sur lequel le subgraph a été publié. ### Mise à jour des métadonnées d'un subgraph publié @@ -69,13 +69,13 @@ Les développeurs peuvent ajouter des signaux GRT à leurs subgraphs pour incite - Vous pouvez vérifier l'éligibilité aux récompenses d'indexation en fonction de l'utilisation des fonctionnalités du subgraph [ici](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Les réseaux spécifiques pris en charge peuvent être vérifiés [ici](/developing/supported-networks/). +- Les réseaux spécifiques pris en charge peuvent être vérifiés [ici](/supported-networks/). > Ajouter un signal à un subgraph non éligible aux récompenses n'attirera pas d'Indexeurs supplémentaires. > Si votre subgraph est éligible aux récompenses, il est recommandé de curer votre propre subgraph avec au moins 3 000 GRT afin d'attirer des indexeurs supplémentaires pour indexer votre subgraph. -L'[Indexer Sunrise Upgrade](/sunrise/#what-is-the-upgrade-indexer) garantit l'indexation de tous les subgraphs. Cependant, le signalement de GRT sur un subgraph particulier attirera plus d'indexeurs. Cette incitation supplémentaire des Indexeurs par la curation vise à améliorer la qualité du service pour les requêtes en réduisant la latence et en améliorant la disponibilité du réseau. +L'[Indexer Sunrise Upgrade](/archived/sunrise/#what-is-the-upgrade-indexer) garantit l'indexation de tous les subgraphs. Cependant, le signalement de GRT sur un subgraph particulier attirera plus d'indexeurs. Cette incitation supplémentaire des Indexeurs par la curation vise à améliorer la qualité du service pour les requêtes en réduisant la latence et en améliorant la disponibilité du réseau. Lors du signalement, les Curateurs peuvent décider de signaler une version spécifique du subgraph ou de signaler en utilisant l'auto-migration. S'ils signalent en utilisant l'auto-migration, les parts d'un Curateur seront toujours mises à jour vers la dernière version publiée par le développeur. S'ils décident de signaler une version spécifique, les parts resteront toujours sur cette version spécifique. @@ -91,4 +91,4 @@ Alternativement, vous pouvez ajouter des signaux GRT à un subgraph publié à p ![Signal depuis Explorer](/img/signal-from-explorer.png) -En savoir plus sur la [curation](/network/curating/) sur The Graph Network. +En savoir plus sur la [curation](/resources/roles/curating/) sur The Graph Network. diff --git a/website/pages/fr/subgraphs/developing/subgraphs.mdx b/website/pages/fr/subgraphs/developing/subgraphs.mdx index 2d86a8dea5b8..d4ad5209eb37 100644 --- a/website/pages/fr/subgraphs/developing/subgraphs.mdx +++ b/website/pages/fr/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Voici un aperçu général du cycle de vie d'un subgraph : 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/fr/subgraphs/explorer.mdx b/website/pages/fr/subgraphs/explorer.mdx index 9a34557333fd..8c55523c5f3a 100644 --- a/website/pages/fr/subgraphs/explorer.mdx +++ b/website/pages/fr/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Les Indexeurs peuvent gagner à la fois des frais de requête et des récompense - Les paramètres d'indexation peuvent être définis en cliquant sur le côté droit du tableau ou en accédant au profil d'un Indexeur et en cliquant sur le bouton "Delegate ". -Pour en savoir plus sur la façon de devenir un indexeur, vous pouvez consulter la [documentation officielle](/network/indexing/) ou les [guides de l'indexeur de la Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) +Pour en savoir plus sur la façon de devenir un indexeur, vous pouvez consulter la [documentation officielle](/indexing/overview/) ou les [guides de l'indexeur de la Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) ![Volet Détails de l'indexation](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ Dans le tableau des Curateurs ci-dessous, vous pouvez voir : ![Explorer Image 6](/img/Curation-Overview.png) -Si vous souhaitez en savoir plus sur le rôle de Curateur, vous pouvez le faire en consultant la [documentation officielle.](/network/curating/) ou [The Graph Academy](https://thegraph.academy/curators/). +Si vous souhaitez en savoir plus sur le rôle de Curateur, vous pouvez le faire en consultant la [documentation officielle.](/resources/roles/curating/) ou [The Graph Academy](https://thegraph.academy/curators/). ### 3. Délégués @@ -113,7 +113,7 @@ Dans le tableau des Délégateurs, vous pouvez voir les Délégateurs actifs dan - Quantité totale de GRT qu'ils ont actuellement dans le protocole - La date de leur dernière délégation -Si vous souhaitez en savoir plus sur comment devenir Délégateur, consultez la [documentation officielle](/network/delegating/) ou [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +Si vous souhaitez en savoir plus sur comment devenir Délégateur, consultez la [documentation officielle](/resources/roles/delegating/) ou [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Réseau diff --git a/website/pages/fr/subgraphs/querying/best-practices.mdx b/website/pages/fr/subgraphs/querying/best-practices.mdx index 2b39d903630b..dc66f900eaae 100644 --- a/website/pages/fr/subgraphs/querying/best-practices.mdx +++ b/website/pages/fr/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Chaque `queryName` ne doit être utilisé qu'une seule fois par opération. - Chaque `champ` ne doit être utilisé qu'une seule fois dans une sélection (on ne peut pas interroger `id` deux fois sous `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Toute variable affectée à un argument doit correspondre à son type. - Dans une liste de variables donnée, chacune d’elles doit être unique. - Toutes les variables définies doivent être utilisées. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Envoi d'une requête à une API GraphQL @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Gestion des subgraphs inter-chaînes : interrogation à partir de plusieurs subgraphs en une seule requête - [Suivi automatique des blocs](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/fr/subgraphs/querying/graphql-api.mdx b/website/pages/fr/subgraphs/querying/graphql-api.mdx index 61f023ffea88..5af2e66932ca 100644 --- a/website/pages/fr/subgraphs/querying/graphql-api.mdx +++ b/website/pages/fr/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/fr/subgraphs/querying/introduction.mdx b/website/pages/fr/subgraphs/querying/introduction.mdx index 6af00953fa3f..fdfe9ff034ed 100644 --- a/website/pages/fr/subgraphs/querying/introduction.mdx +++ b/website/pages/fr/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Interroger The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/fr/subgraphs/quick-start.mdx b/website/pages/fr/subgraphs/quick-start.mdx index 5759a2cb0dbb..474fed865a37 100644 --- a/website/pages/fr/subgraphs/quick-start.mdx +++ b/website/pages/fr/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Démarrage Rapide --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Conditions préalables - Un portefeuille crypto -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publier votre subgraph sur The Graph Network⁠ -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publier avec Subgraph Studio⁠ @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -Pour personnaliser votre déploiement, consultez [Publication d'un Subgraph](/publishing/publishing-a-subgraph/). +Pour personnaliser votre déploiement, consultez [Publication d'un Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Ajouter un signal à votre subgraph⁠ @@ -169,7 +169,7 @@ Pour personnaliser votre déploiement, consultez [Publication d'un Subgraph](/pu - Il est recommandé de curer au moins 3 000 GRT pour attirer 3 Indexeurs. Vérifiez l'éligibilité aux récompenses en fonction de l'utilisation des fonctionnalités du subgraph et des réseaux supportés. -Pour en savoir plus sur la curation, lisez [Curation](/network/curating/). +Pour en savoir plus sur la curation, lisez [Curation](/resources/roles/curating/). Pour économiser sur les frais de gas, vous pouvez curer votre subgraph dans la même transaction que celle où vous le publiez en sélectionnant cette option : @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -Pour plus d'informations sur l'interrogation des données de votre subgraph, lisez [Interroger The Graph](/querying/querying-the-graph/). +Pour plus d'informations sur l'interrogation des données de votre subgraph, lisez [Interroger The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/fr/substreams/sps/sps-faq.mdx b/website/pages/fr/substreams/sps/sps-faq.mdx index ca95d4bd375c..5f43a984b67b 100644 --- a/website/pages/fr/substreams/sps/sps-faq.mdx +++ b/website/pages/fr/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: FAQ sur les subgraphs alimentés par les sous-flux Développé par [StreamingFast](https://www.streamingfast.io/), Substreams est un moteur de traitement extrêmement puissant capable de consommer des flux riches de données blockchain. Substreams vous permet de raffiner et de structurer les données blockchain pour une digestion rapide et fluide par les applications des utilisateurs finaux. Plus précisément, Substreams est un moteur agnostique à la blockchain, parallélisé et axé sur le streaming, servant de couche de transformation des données blockchain. Propulsé par [Firehose](https://firehose.streamingfast.io/), il permet aux développeurs d'écrire des modules Rust, de s'appuyer sur des modules communautaires, de fournir une indexation très performante, et de [diriger(sink)](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) leurs données vers n'importe quelle destination. -Rendez-vous sur le site [Substreams Documentation](/substreams/) pour en savoir plus sur Substreams. +Rendez-vous sur le site [Substreams Documentation](/substreams/introduction/) pour en savoir plus sur Substreams. ## Qu'est-ce qu'un subgraph alimenté par des courants de fond ? -Les [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs/) combinent la puissance de Substreams avec la capacité d'interrogation des subgraphs. Lors de la publication d'un subgraph alimenté par Substreams, les données produites par les transformations Substreams peuvent [output entity changes] (https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), qui sont compatibles avec les entités du subgraph. +Les [subgraphs alimentés par Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/) combinent la puissance de Substreams avec la capacité d'interrogation des subgraphs. Lors de la publication d'un subgraph alimenté par Substreams, les données produites par les transformations Substreams peuvent [output entity changes] (https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), qui sont compatibles avec les entités du subgraph. Si vous êtes déjà familiarisé avec le développement de subgraphs, notez que les subgraphs alimentés par Substreams peuvent ensuite être interrogés, comme s'ils avaient été produits par la couche de transformation AssemblyScript, avec tous les avantages de Subgraph, comme la fourniture d'une API GraphQL dynamique et flexible. @@ -62,9 +62,9 @@ L'utilisation de Firehose présente de nombreux avantages, notamment: ## Où les développeurs peuvent-ils trouver plus d'informations sur les subgraphs alimentés par Substreams et sur Substreams ? -La [documentation Substreams](/substreams/) vous apprendra à construire des modules Substreams. +La [documentation Substreams](/substreams/introduction/) vous apprendra à construire des modules Substreams. -La [documentation sur les subgraphs alimentés par des flux partiels] (/cookbook/substreams-powered-subgraphs/) vous montrera comment les emballer pour les déployer sur The Graph. +La [documentation sur les subgraphs alimentés par des flux partiels] (/subgraphs/cookbook/substreams-powered-subgraphs/) vous montrera comment les emballer pour les déployer sur The Graph. Le [dernier outil Substreams Codegen ](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) vous permettra de lancer un projet Substreams sans aucun code. @@ -82,7 +82,7 @@ Par exemple, Alice peut créer un module de prix DEX, Bob peut l'utiliser pour c ## Comment pouvez-vous créer et déployer un Subgraph basé sur Substreams ? -Après avoir [defining](/cookbook/substreams-powered-subgraphs/) un Subgraph alimenté par Substreams, vous pouvez utiliser la CLI Graph pour le déployer dans [Subgraph Studio](https://thegraph.com/studio/). +Après avoir [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) un Subgraph alimenté par Substreams, vous pouvez utiliser la CLI Graph pour le déployer dans [Subgraph Studio](https://thegraph.com/studio/). ## Où puis-je trouver des exemples de subgraphs et de subgraphs alimentés par des substreams ? diff --git a/website/pages/fr/supported-networks.mdx b/website/pages/fr/supported-networks.mdx index ea91c24d942e..f899c29b14ba 100644 --- a/website/pages/fr/supported-networks.mdx +++ b/website/pages/fr/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Support réseau de base fourni par l' [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Intégration avec Graph Node : `evm`, `near`, `cosmos`, `osmosis` et `ar` sont nativement pris en charge dans Graph Node. Les blockchains compatibles avec Firehose et Substreams peuvent tirer parti de l'intégration généralisée des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs/) (ceci inclut les réseaux `evm` et `near` ). ⁠† Prend en charge le déploiement des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs/). +\*\* Intégration avec Graph Node : `evm`, `near`, `cosmos`, `osmosis` et `ar` sont nativement pris en charge dans Graph Node. Les blockchains compatibles avec Firehose et Substreams peuvent tirer parti de l'intégration généralisée des [subgraphs alimentés par Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/) (ceci inclut les réseaux `evm` et `near` ). ⁠† Prend en charge le déploiement des [subgraphs alimentés par Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio repose sur la stabilité et la fiabilité des technologies sous-jacentes, comme les endpoints JSON-RPC, Firehose et Substreams. - Les subgraphs indexant Gnosis Chain peuvent désormais être déployés avec l'identifiant de réseau `gnosis`. diff --git a/website/pages/hi/about.mdx b/website/pages/hi/about.mdx index 182d6d6b068e..4676fe4c295f 100644 --- a/website/pages/hi/about.mdx +++ b/website/pages/hi/about.mdx @@ -24,7 +24,7 @@ The Graph एक शक्तिशाली विकेंद्रीकृ यह सरल सवालों का जवाब पाने में एक ब्राउज़र में चल रही एक विकेन्द्रीकृत एप्लिकेशन (dapp) को **घंटे या यहाँ तक कि दिन** लग सकते हैं। -वैकल्पिक रूप से, आपके पास अपना स्वयं का सर्वर सेट अप करने, लेनदेन को प्रोसेस करने, उन्हें एक डेटाबेस में स्टोर करने, और डेटा को क्वेरी करने के लिए एक API एन्डपॉइंट बनाने का विकल्प है। हालांकि, यह विकल्प [संसाधन-संवेदनशील](/network/benefits/) है, रखरखाव की आवश्यकता होती है, एकल विफलता बिंदु प्रस्तुत करता है, और विकेंद्रीकरण के लिए आवश्यक महत्वपूर्ण सुरक्षा गुणों को तोड़ता है। +वैकल्पिक रूप से, आपके पास अपना स्वयं का सर्वर सेट अप करने, लेनदेन को प्रोसेस करने, उन्हें एक डेटाबेस में स्टोर करने, और डेटा को क्वेरी करने के लिए एक API एन्डपॉइंट बनाने का विकल्प है। हालांकि, यह विकल्प [संसाधन-संवेदनशील](/resources/benefits/) है, रखरखाव की आवश्यकता होती है, एकल विफलता बिंदु प्रस्तुत करता है, और विकेंद्रीकरण के लिए आवश्यक महत्वपूर्ण सुरक्षा गुणों को तोड़ता है। ब्लॉकचेन की विशेषताएँ, जैसे अंतिमता, चेन पुनर्गठन, और अंकल ब्लॉक्स, प्रक्रिया में जटिलता जोड़ती हैं, जिससे ब्लॉकचेन डेटा से सटीक क्वेरी परिणाम प्राप्त करना समय लेने वाला और अवधारणात्मक रूप से चुनौतीपूर्ण हो जाता है। diff --git a/website/pages/hi/archived/arbitrum/arbitrum-faq.mdx b/website/pages/hi/archived/arbitrum/arbitrum-faq.mdx index 885ebdc4f88f..7cd07febfc64 100644 --- a/website/pages/hi/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/hi/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ L2 पर द ग्राफ़ का उपयोग करने का ल ## Subgraph developer, data consumer, Indexer, Curator, or Delegator, के रूप में, मुझे अब क्या करने की आवश्यकता है? -नेटवर्क प्रतिभागियों को The Graph Network में भाग लेना जारी रखने के लिए Arbitrum पर स्थानांतरित होना होगा। अतिरिक्त सहायता के लिए कृपया [L2 ट्रांसफर टूल गाइड](/arbitrum/l2-transfer-tools-guide/) देखें। +नेटवर्क प्रतिभागियों को The Graph Network में भाग लेना जारी रखने के लिए Arbitrum पर स्थानांतरित होना होगा। अतिरिक्त सहायता के लिए कृपया [L2 ट्रांसफर टूल गाइड](/archived/arbitrum/l2-transfer-tools-guide/) देखें। अब सभी इंडेक्सिंग पुरस्कार पूरी तरह से Arbitrum पर हैं। @@ -53,7 +53,7 @@ L2 पर द ग्राफ़ का उपयोग करने का ल ## क्या Ethereum पर मौजूद सबग्राफ़ काम कर रहे हैं? -अब सभी सबग्राफ़ Arbitrum पर हैं। सुनिश्चित करें कि आपके सबग्राफ़ सुचारू रूप से कार्य करते हैं, कृपया [L2 ट्रांसफर टूल गाइड](/arbitrum/l2-transfer-tools-guide/) देखें। +अब सभी सबग्राफ़ Arbitrum पर हैं। सुनिश्चित करें कि आपके सबग्राफ़ सुचारू रूप से कार्य करते हैं, कृपया [L2 ट्रांसफर टूल गाइड](/archived/arbitrum/l2-transfer-tools-guide/) देखें। ## क्या GRT का एक नया स्मार्ट कॉन्ट्रैक्ट Arbitrum पर तैनात किया गया है? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the आपके आर्बिट्रम बिलिंग बैलेंस में जीआरटी जोड़ना [सबग्राफ स्टूडियो] (https://thegraph.com/studio/) में एक-क्लिक अनुभव के साथ किया जा सकता है। आप आसानी से अपने जीआरटी को आर्बिट्रम से जोड़ सकेंगे और एक लेनदेन में अपनी एपीआई कुंजी भर सकेंगे। -कृपया अधिक विस्तृत निर्देशों के लिए [Billing page](/billing/) पर जाएं, जहाँ GRT जोड़ने, निकालने या प्राप्त करने के तरीके बताए गए हैं। +कृपया अधिक विस्तृत निर्देशों के लिए [Billing page](/subgraphs/billing/) पर जाएं, जहाँ GRT जोड़ने, निकालने या प्राप्त करने के तरीके बताए गए हैं। diff --git a/website/pages/hi/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/hi/archived/arbitrum/l2-transfer-tools-faq.mdx index a1c4474d0cba..8a09613e27f6 100644 --- a/website/pages/hi/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/hi/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx index f8efa2e9c17e..21ee64e62ac4 100644 --- a/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/hi/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## अपने सबग्राफ को आर्बिट्रम (L2) में कैसे स्थानांतरित करें diff --git a/website/pages/hi/archived/sunrise.mdx b/website/pages/hi/archived/sunrise.mdx index 8adee9833853..0ac3b30cc40e 100644 --- a/website/pages/hi/archived/sunrise.mdx +++ b/website/pages/hi/archived/sunrise.mdx @@ -22,7 +22,7 @@ title: पोस्ट-सनराइज + The Graph Network में अप ### सबग्राफ्स को Arbitrum पर क्यों प्रकाशित किया गया, क्या इसने एक अलग नेटवर्क को इंडेक्स करना शुरू किया? -The Graph Network को शुरू में Ethereum मेननेट पर तैनात किया गया था, लेकिन बाद में सभी उपयोगकर्ताओं के लिए गैस लागत को कम करने के लिए इसे Arbitrum वन पर स्थानांतरित कर दिया गया। परिणामस्वरूप, सभी नए सबग्राफ़ Arbitrum पर The Graph Network पर प्रकाशित किए जाते हैं ताकि Indexer उनका समर्थन कर सकें। Arbitrum वह नेटवर्क है जिस पर सबग्राफ़ प्रकाशित किए जाते हैं, लेकिन सबग्राफ़ किसी भी [समर्थित नेटवर्क](/developing/supported-networks/) को इंडेक्स कर सकते हैं। +The Graph Network को शुरू में Ethereum मेननेट पर तैनात किया गया था, लेकिन बाद में सभी उपयोगकर्ताओं के लिए गैस लागत को कम करने के लिए इसे Arbitrum वन पर स्थानांतरित कर दिया गया। परिणामस्वरूप, सभी नए सबग्राफ़ Arbitrum पर The Graph Network पर प्रकाशित किए जाते हैं ताकि Indexer उनका समर्थन कर सकें। Arbitrum वह नेटवर्क है जिस पर सबग्राफ़ प्रकाशित किए जाते हैं, लेकिन सबग्राफ़ किसी भी [समर्थित नेटवर्क](/supported-networks/) को इंडेक्स कर सकते हैं। ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The Graph Network को शुरू में Ethereum मेननेट प ### अपग्रेड Indexer क्या करता है? - यह उन चेन को बूटस्ट्रैप करता है जिन्हें अभी तक The Graph Network पर इंडेक्सिंग पुरस्कार नहीं मिले हैं और यह सुनिश्चित करता है कि एक Indexer उपलब्ध हो ताकि एक Subgraph प्रकाशित होने के तुरंत बाद क्वेरी को यथाशीघ्र सेवा दी जा सके। -- यह उन चेन का समर्थन करता है जो पहले केवल Hosted Service पर उपलब्ध थीं। समर्थित चेन की एक व्यापक सूची [यहां](https://thegraph. com/developing/supported-networks/) देखें। +- यह उन चेन का समर्थन करता है जो पहले केवल Hosted Service पर उपलब्ध थीं। समर्थित चेन की एक व्यापक सूची [यहां](https://thegraph. com/supported-networks/) देखें। - जो Indexer अपग्रेड इंडेक्सर का संचालन करते हैं, वे नए सबग्राफ़ और अतिरिक्त चेन का समर्थन करने के लिए एक सार्वजनिक सेवा के रूप में ऐसा करते हैं जो इंडेक्सिंग पुरस्कारों की कमी का सामना कर रहे हैं, जब तक कि The Graph काउंसिल उन्हें मंजूरी नहीं देती। ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ Edge & Node ने ऐतिहासिक रूप से होस्टे ### यह Subgraph डेवलपर्स को कैसे प्रभावित करता है? -सबग्राफ डेवलपर्स अपने सबग्राफ को The Graph Network पर लगभग तुरंत ही अपग्रेड किए जाने के बाद या [Subgraph Studio से प्रकाशित करने](/publishing/publishing-a-subgraph/) के बाद क्वेरी कर सकते हैं, क्योंकि indexing के लिए कोई लीड टाइम की आवश्यकता नहीं थी। कृपया ध्यान दें कि [सबग्राफ बनाना](/developing/creating-a-subgraph/) इस अपग्रेड से प्रभावित नहीं हुआ था। +सबग्राफ डेवलपर्स अपने सबग्राफ को The Graph Network पर लगभग तुरंत ही अपग्रेड किए जाने के बाद या [Subgraph Studio से प्रकाशित करने](/subgraphs/developing/publishing/publishing-a-subgraph/) के बाद क्वेरी कर सकते हैं, क्योंकि indexing के लिए कोई लीड टाइम की आवश्यकता नहीं थी। कृपया ध्यान दें कि [सबग्राफ बनाना](/developing/creating-a-subgraph/) इस अपग्रेड से प्रभावित नहीं हुआ था। ### अपग्रेड Indexer डेटा उपभोक्ताओं को कैसे लाभ पहुंचाता है? diff --git a/website/pages/hi/contracts.mdx b/website/pages/hi/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/hi/contracts.mdx +++ b/website/pages/hi/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/hi/indexing/chain-integration-overview.mdx b/website/pages/hi/indexing/chain-integration-overview.mdx index 5645f822336d..c8bac7343bad 100644 --- a/website/pages/hi/indexing/chain-integration-overview.mdx +++ b/website/pages/hi/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- कृपया [New Chain Integration](/new-chain-integration/) पर जाएं नई chains के लिए `graph-node` समर्थन के बारे में जानकारी के लिए. +- कृपया [New Chain Integration](/indexing/new-chain-integration/) पर जाएं नई chains के लिए `graph-node` समर्थन के बारे में जानकारी के लिए. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/hi/indexing/new-chain-integration.mdx b/website/pages/hi/indexing/new-chain-integration.mdx index 1ca8eaab721f..5e2c9db1a96b 100644 --- a/website/pages/hi/indexing/new-chain-integration.mdx +++ b/website/pages/hi/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ EVM चेन के लिए, एक गहरे स्तर के डे ## EVM विचार - JSON-RPC और Firehose के बीच का अंतर -जबकि JSON-RPC और Firehose दोनों सबग्राफ़ के लिए उपयुक्त हैं, Firehose हमेशा उन डेवलपर्स के लिए आवश्यक है जो [Substreams](https://substreams.streamingfast.io) के साथ निर्माण करना चाहते हैं। Substreams का समर्थन करने से डेवलपर्स को नए चेन के लिए [Substreams-समर्थित सबग्राफ़](https://cookbook/substreams-powered-subgraphs) बनाने की अनुमति मिलती है, और इससे आपके सबग्राफ़ के प्रदर्शन में सुधार करने की क्षमता होती है। इसके अतिरिक्त, Firehose — `graph-node` के JSON-RPC निष्कर्षण स्तर के लिए एक ड्रॉप-इन प्रतिस्थापन के रूप में — सामान्य अनुक्रमण के लिए आवश्यक RPC कॉल की संख्या को 90% तक कम करता है। +जबकि JSON-RPC और Firehose दोनों सबग्राफ़ के लिए उपयुक्त हैं, Firehose हमेशा उन डेवलपर्स के लिए आवश्यक है जो [Substreams](https://substreams.streamingfast.io) के साथ निर्माण करना चाहते हैं। Substreams का समर्थन करने से डेवलपर्स को नए चेन के लिए [Substreams-समर्थित सबग्राफ़](/subgraphs/cookbook/substreams-powered-subgraphs/) बनाने की अनुमति मिलती है, और इससे आपके सबग्राफ़ के प्रदर्शन में सुधार करने की क्षमता होती है। इसके अतिरिक्त, Firehose — `graph-node` के JSON-RPC निष्कर्षण स्तर के लिए एक ड्रॉप-इन प्रतिस्थापन के रूप में — सामान्य अनुक्रमण के लिए आवश्यक RPC कॉल की संख्या को 90% तक कम करता है। - सभी `getLogs` कॉल्स और राउंडट्रिप्स को एकल स्ट्रीम द्वारा प्रतिस्थापित किया जाता है, जो सीधे `graph-node` के केंद्र में पहुंचती है; यह एकल ब्लॉक मॉडल सभी सबग्राफ्स के लिए काम करता है जिन्हें यह प्रोसेस करता है। diff --git a/website/pages/hi/indexing/overview.mdx b/website/pages/hi/indexing/overview.mdx index 354933160704..47f4d7166d29 100644 --- a/website/pages/hi/indexing/overview.mdx +++ b/website/pages/hi/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### क्वेरी फी कट और इंडेक्सिंग रिवॉर्ड कट क्या है? -`queryFeeCut` और `indexingRewardCut` मान डेलिगेशन पैरामीटर हैं जिन्हें इंडेक्सर और उनके डेलीगेटर्स के बीच GRT के वितरण को नियंत्रित करने के लिए इंडेक्सर cooldownBlocks के साथ सेट कर सकता है। प्रतिनिधिमंडल पैरामीटर सेट करने के निर्देशों के लिए [प्रोटोकॉल में स्टेकिंग](/network/indexing/#stake-in-the-protocol) में अंतिम चरण देखें। +`queryFeeCut` और `indexingRewardCut` मान डेलिगेशन पैरामीटर हैं जिन्हें इंडेक्सर और उनके डेलीगेटर्स के बीच GRT के वितरण को नियंत्रित करने के लिए इंडेक्सर cooldownBlocks के साथ सेट कर सकता है। प्रतिनिधिमंडल पैरामीटर सेट करने के निर्देशों के लिए [प्रोटोकॉल में स्टेकिंग](/indexing/overview/#stake-in-the-protocol) में अंतिम चरण देखें। - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### एक इंडेक्सर को कौन सी बुनियादी सुरक्षा सावधानियां बरतनी चाहिए? -- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करना एक महत्वपूर्ण एहतियात है क्योंकि यह एक इंडेक्सर को उनकी चाबियों के बीच अलगाव बनाए रखने की अनुमति देता है जो हिस्सेदारी को नियंत्रित करती हैं और जो दिन-प्रतिदिन के संचालन को नियंत्रित करती हैं। निर्देशों के लिए [प्रोटोकॉल में हिस्सेदारी](/network/indexing/#stake-in-the-protocol) देखें। +- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करना एक महत्वपूर्ण एहतियात है क्योंकि यह एक इंडेक्सर को उनकी चाबियों के बीच अलगाव बनाए रखने की अनुमति देता है जो हिस्सेदारी को नियंत्रित करती हैं और जो दिन-प्रतिदिन के संचालन को नियंत्रित करती हैं। निर्देशों के लिए [प्रोटोकॉल में हिस्सेदारी](/indexing/overview/#stake-in-the-protocol) देखें। - **फ़ायरवॉल** - केवल इंडेक्सर सेवा को सार्वजनिक रूप से प्रदर्शित करने की आवश्यकता है और एडमिन पोर्ट और डेटाबेस एक्सेस को लॉक करने पर विशेष ध्यान दिया जाना चाहिए: ग्राफ़ नोड JSON-RPC समापन बिंदु (डिफ़ॉल्ट पोर्ट): 8030), इंडेक्सर मैनेजमेंट एपीआई एंडपॉइंट (डिफ़ॉल्ट पोर्ट: 18000), और पोस्टग्रेज डेटाबेस एंडपॉइंट (डिफ़ॉल्ट पोर्ट: 5432) को उजागर नहीं किया जाना चाहिए। @@ -375,7 +375,7 @@ docker-compose up #### शुरू करना -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s और टेराफॉर्म का उपयोग करना -[Google क्लाउड पर Terraform का उपयोग करके सेटअप सर्वर इन्फ्रास्ट्रक्चर](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) अनुभाग देखें +[Google क्लाउड पर Terraform का उपयोग करके सेटअप सर्वर इन्फ्रास्ट्रक्चर](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) अनुभाग देखें #### प्रयोग @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -एक बार एक इंडेक्सर प्रोटोकॉल में जीआरटी को दांव पर लगा देता है, तो [इंडेक्सर घटक](/network/indexing/#indexer-components) को शुरू किया जा सकता है और नेटवर्क के साथ उनकी बातचीत शुरू की जा सकती है। +एक बार एक इंडेक्सर प्रोटोकॉल में जीआरटी को दांव पर लगा देता है, तो [इंडेक्सर घटक](/indexing/overview/#indexer-components) को शुरू किया जा सकता है और नेटवर्क के साथ उनकी बातचीत शुरू की जा सकती है। #### टोकन स्वीकृत करें @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). इंडेक्सर्स को ऑन-चेन आवंटन बनाने से पहले चेनहेड में सबग्राफ परिनियोजन को सिंक करने के लिए ऑफ-चेन सिंकिंग कार्यक्षमता का उपयोग करने की सिफारिश की जाती है। यह सुविधा सबग्राफ के लिए विशेष रूप से उपयोगी है जो सिंक करने के लिए 28 से अधिक समय ले सकती है या अनिश्चित रूप से विफल होने की कुछ संभावनाएं हैं। diff --git a/website/pages/hi/indexing/tap.mdx b/website/pages/hi/indexing/tap.mdx index ca4837de335e..dc46d2047b0a 100644 --- a/website/pages/hi/indexing/tap.mdx +++ b/website/pages/hi/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 टिप्पणियाँ: -- tap.sender_aggregator_endpoints के लिए मान gateway section (/tap/#gateway). में पाए जा सकते हैं। -- blockchain.receipts_verifier_address के लिए मानों का उपयोग उचित तरीके से Blockchain addresses section (/tap/#contracts) के अनुसार किया जाना चाहिए, जिसमें उचित चेन आईडी का उपयोग किया गया है। +- tap.sender_aggregator_endpoints के लिए मान gateway section (/indexing/tap/#gateway). में पाए जा सकते हैं। +- blockchain.receipts_verifier_address के लिए मानों का उपयोग उचित तरीके से Blockchain addresses section (/indexing/tap/#contracts) के अनुसार किया जाना चाहिए, जिसमें उचित चेन आईडी का उपयोग किया गया है। **लॉग स्तर** diff --git a/website/pages/hi/resources/benefits.mdx b/website/pages/hi/resources/benefits.mdx index 5df5653274dd..cafb61355a28 100644 --- a/website/pages/hi/resources/benefits.mdx +++ b/website/pages/hi/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. एक सबग्राफ पर क्यूरेटिंग सिग्नल एक वैकल्पिक वन-टाइम, नेट-जीरो कॉस्ट है (उदाहरण के लिए, सिग्नल में $1k को सबग्राफ पर क्यूरेट किया जा सकता है, और बाद में वापस ले लिया जाता है - प्रक्रिया में रिटर्न अर्जित करने की क्षमता के साथ)। @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy निचला रेखा: ग्राफ़ नेटवर्क कम खर्चीला है, उपयोग में आसान है, और `ग्राफ़-नोड` को स्थानीय रूप से चलाने की तुलना में बेहतर परिणाम देता है। -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/hi/resources/roles/curating.mdx b/website/pages/hi/resources/roles/curating.mdx index 9fbaad030f6d..84f401c9681e 100644 --- a/website/pages/hi/resources/roles/curating.mdx +++ b/website/pages/hi/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## सिग्नल कैसे करें -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) एक क्यूरेटर एक विशिष्ट सबग्राफ संस्करण पर संकेत देना चुन सकता है, या वे अपने सिग्नल को स्वचालित रूप से उस सबग्राफ के नवीनतम उत्पादन निर्माण में माइग्रेट करना चुन सकते हैं। दोनों मान्य रणनीतियाँ हैं और अपने स्वयं के पेशेवरों और विपक्षों के साथ आती हैं। @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. क्वेरी बाजार द ग्राफ में स्वाभाविक रूप से युवा है और इसमें जोखिम है कि नवजात बाजार की गतिशीलता के कारण आपका %APY आपकी अपेक्षा से कम हो सकता है। 2. क्यूरेशन शुल्क - जब कोई क्यूरेटर किसी सबग्राफ़ पर GRT सिग्नल करता है, तो उसे 1% क्यूरेशन टैक्स देना होता है। यह शुल्क जला दिया जाता है। -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. बग के कारण सबग्राफ विफल हो सकता है। एक विफल सबग्राफ क्वेरी शुल्क अर्जित नहीं करता है। नतीजतन, आपको तब तक इंतजार करना होगा जब तक कि डेवलपर बग को ठीक नहीं करता है और एक नया संस्करण तैनात करता है। - यदि आपने सबग्राफ के नवीनतम संस्करण की सदस्यता ली है, तो आपके शेयर उस नए संस्करण में स्वत: माइग्रेट हो जाएंगे। इस पर 0.5% क्यूरेशन टैक्स लगेगा। - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/hi/resources/tokenomics.mdx b/website/pages/hi/resources/tokenomics.mdx index b643a3aeaa90..3b059d2c1439 100644 --- a/website/pages/hi/resources/tokenomics.mdx +++ b/website/pages/hi/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### किसी मौजूदा सबग्राफ को क्वेरी करना -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/hi/subgraphs/billing.mdx b/website/pages/hi/subgraphs/billing.mdx index 1462d5d49ea6..a942479485e5 100644 --- a/website/pages/hi/subgraphs/billing.mdx +++ b/website/pages/hi/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - क्रेडिट/डेबिट कार्ड के साथ बिलिंग सेट करने के लिए, उपयोगकर्ताओं को **Subgraph Studio** (https://thegraph.com/studio/) पर जाना चाहिए। - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. पृष्ठ के ऊपरी दाएं कोने पर "कनेक्ट वॉलेट" बटन पर क्लिक करें। आपको बटुआ चयन पृष्ठ पर पुनर्निर्देशित किया जाएगा। अपना बटुआ चुनें और "कनेक्ट" पर क्लिक करें। 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ The Graph का बिलिंग सिस्टम Arbitrum पर GRT क ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. पृष्ठ के ऊपरी दाएं कोने पर "कनेक्ट वॉलेट" बटन पर क्लिक करें। आपको बटुआ चयन पृष्ठ पर पुनर्निर्देशित किया जाएगा। अपना बटुआ चुनें और "कनेक्ट" पर क्लिक करें। 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ The Graph का बिलिंग सिस्टम Arbitrum पर GRT क ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. पृष्ठ के ऊपरी दाएं कोने में "मैनेज" बटन पर क्लिक करें। "GRT निकालें" चुनें। एक साइड पैनल दिखाई देगा। 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ The Graph का बिलिंग सिस्टम Arbitrum पर GRT क ### मल्टीसिग वॉलेट का उपयोग करके जीआरटी जोड़ना -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/hi/subgraphs/cookbook/arweave.mdx b/website/pages/hi/subgraphs/cookbook/arweave.mdx index 21103e5aac2e..12bd2895b137 100644 --- a/website/pages/hi/subgraphs/cookbook/arweave.mdx +++ b/website/pages/hi/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ dataSources: इवेंट्स को प्रोसेस करने के लिए हैंडलर्स [असेंबली स्क्रिप्ट](https://www.assemblyscript.org/) में लिखे गए हैं| -Arweave इंडेक्सिंग '[AssemblyScript API](/developing/graph-ts/api/)' में Arweave-विशिष्ट डेटा प्रकारों को पेश करती है। +Arweave इंडेक्सिंग '[AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/)' में Arweave-विशिष्ट डेटा प्रकारों को पेश करती है। ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## आरवीव सब-ग्राफ क्वेरी करना -आरवीव सब-ग्राफ्स के लिए GraphQL एन्ड पॉइंट्स स्कीमा की परिभाषा के अनुरूप, API इंटरफ़ेस के अनुसार बनाये जाते हैं| अधिक जानकारी के लिए [GraphQL API documentation](/querying/graphql-api/) पर जाएं| +आरवीव सब-ग्राफ्स के लिए GraphQL एन्ड पॉइंट्स स्कीमा की परिभाषा के अनुरूप, API इंटरफ़ेस के अनुसार बनाये जाते हैं| अधिक जानकारी के लिए [GraphQL API documentation](/subgraphs/querying/graphql-api/) पर जाएं| ## सब-ग्राफ के उदाहरण diff --git a/website/pages/hi/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/hi/subgraphs/cookbook/avoid-eth-calls.mdx index 9e56fbef5970..5e86a234262a 100644 --- a/website/pages/hi/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/hi/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/hi/subgraphs/cookbook/cosmos.mdx b/website/pages/hi/subgraphs/cookbook/cosmos.mdx index b64bc7c1cd7b..d62a6ce89a05 100644 --- a/website/pages/hi/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/hi/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and इवेंट्स को प्रोसेस करने के हैंडलर्स [असेंबली स्क्रिप्ट ](https://www.assemblyscript.org/) में लिखे गए हैं| -कॉसमॉस इंडेक्सिंग कॉसमॉस-विशिष्ट डाटा प्रकारो को [असेंबली स्क्रिप्ट ए पी आई](/developing/graph-ts/api/) में ले कर आती है| +कॉसमॉस इंडेक्सिंग कॉसमॉस-विशिष्ट डाटा प्रकारो को [असेंबली स्क्रिप्ट ए पी आई](/subgraphs/developing/creating/graph-ts/api/) में ले कर आती है| ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## कॉसमॉस सब-ग्राफ को क्वेरी करना -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## समर्थित कॉसमॉस ब्लॉकचेन्स diff --git a/website/pages/hi/subgraphs/cookbook/derivedfrom.mdx b/website/pages/hi/subgraphs/cookbook/derivedfrom.mdx index 3c8ffa04332a..8d20dc0e36fe 100644 --- a/website/pages/hi/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/hi/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ type Comment @entity { 2. हम एक रिवर्स लुकअप कर सकते हैं और किसी भी Comment को क्वेरी कर सकते हैं और देख सकते हैं कि यह किस पोस्ट से आया है। -3. हम [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) का उपयोग कर सकते हैं ताकि हमारे Subgraph मैपिंग में वर्चुअल संबंधों से डेटा को सीधे एक्सेस और संपादित करने की क्षमता को अनलॉक किया जा सके। +3. हम [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) का उपयोग कर सकते हैं ताकि हमारे Subgraph मैपिंग में वर्चुअल संबंधों से डेटा को सीधे एक्सेस और संपादित करने की क्षमता को अनलॉक किया जा सके। ## निष्कर्ष @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/hi/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/hi/subgraphs/cookbook/grafting-hotfix.mdx index 1c858096478b..2bf58c320368 100644 --- a/website/pages/hi/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/hi/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## अतिरिक्त संसाधन -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/hi/subgraphs/cookbook/grafting.mdx b/website/pages/hi/subgraphs/cookbook/grafting.mdx index fde8a5b6d9ac..cebcc5f1c533 100644 --- a/website/pages/hi/subgraphs/cookbook/grafting.mdx +++ b/website/pages/hi/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## एक मौजूदा सब-ग्राफ बनाना -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [सब-ग्राफ उदाहरण रेपो](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ Congrats! You have successfully grafted a subgraph onto another subgraph. To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> नोट: इस आर्टिकल में काफी सामग्री पहले से प्रकाशित [आरवीव आर्टिकल](/cookbook/arweave/) से ली गयी है| +> नोट: इस आर्टिकल में काफी सामग्री पहले से प्रकाशित [आरवीव आर्टिकल](/subgraphs/cookbook/arweave/) से ली गयी है| diff --git a/website/pages/hi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/hi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index a58adda01cc3..763e8ec760e6 100644 --- a/website/pages/hi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/hi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Immutable Entities और Bytes को IDs के रूप में उपय ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/hi/subgraphs/cookbook/near.mdx b/website/pages/hi/subgraphs/cookbook/near.mdx index cecf15ff902a..3b098b20ceab 100644 --- a/website/pages/hi/subgraphs/cookbook/near.mdx +++ b/website/pages/hi/subgraphs/cookbook/near.mdx @@ -35,9 +35,9 @@ NEAR सबग्राफ डेवलपमेंट के लिए `graph-c **subgraph.yaml:** सबग्राफ मेनिफेस्ट, रुचि के डेटा स्रोतों को परिभाषित करता है, और उन्हें कैसे संसाधित किया जाना चाहिए। NEAR डेटा स्रोत का `प्रकार` है। -**schema.graphql:** एक स्कीमा फ़ाइल जो परिभाषित करती है कि आपके सबग्राफ के लिए कौन सा डेटा इकट्ठा होगा, और इसे ग्राफ़क्यूएल के माध्यम से कैसे क्वेरी करें। NEAR सबग्राफ की आवश्यकताएं [मौजूदा दस्तावेज़ीकरण](/Developing/creating-a-subgraph/#the-graphql-schema) द्वारा कवर की गई हैं। +**schema.graphql:** एक स्कीमा फ़ाइल जो परिभाषित करती है कि आपके सबग्राफ के लिए कौन सा डेटा इकट्ठा होगा, और इसे ग्राफ़क्यूएल के माध्यम से कैसे क्वेरी करें। NEAR सबग्राफ की आवश्यकताएं [मौजूदा दस्तावेज़ीकरण](/developing/creating-a-subgraph/#the-graphql-schema) द्वारा कवर की गई हैं। -**AssemblyScript मापिंग:** [AssemblyScript कोड](/developing/graph-ts/api/) जो घटना डेटा को आपकी स्कीमा में परिभाषित संस्थाओं में अनुवादित करता है। NEAR समर्थन NEAR-विशिष्ट डेटा प्रकार और नई JSON पार्सिंग कार्यक्षमता पेश करता है। +**AssemblyScript मापिंग:** [AssemblyScript कोड](/subgraphs/developing/creating/graph-ts/api/) जो घटना डेटा को आपकी स्कीमा में परिभाषित संस्थाओं में अनुवादित करता है। NEAR समर्थन NEAR-विशिष्ट डेटा प्रकार और नई JSON पार्सिंग कार्यक्षमता पेश करता है। सबग्राफ डेवलपमेंट के दौरान दो प्रमुख कमांड होते हैं: @@ -92,13 +92,13 @@ NEAR डेटा स्रोत दो प्रकार के हैंड ### स्कीमा परिभाषा -स्कीमा परिभाषा परिणामी सबग्राफ डेटाबेस की संरचना और संस्थाओं के बीच संबंधों का वर्णन करती है। यह मूल डेटा स्रोत का अज्ञेयवादी है। सबग्राफ स्कीमा परिभाषा [यहां](/Developing/creating-a-subgraph/#the-graphql-schema) पर अधिक विवरण हैं। +स्कीमा परिभाषा परिणामी सबग्राफ डेटाबेस की संरचना और संस्थाओं के बीच संबंधों का वर्णन करती है। यह मूल डेटा स्रोत का अज्ञेयवादी है। सबग्राफ स्कीमा परिभाषा [यहां](/developing/creating-a-subgraph/#the-graphql-schema) पर अधिक विवरण हैं। ### असेंबलीस्क्रिप्ट मैपिंग्स इवेंट को प्रोसेस करने के लिए हैंडलर [AssemblyScript](https://www.assemblyscript.org/) में लिखे होते हैं। -NEAR indexing 'NEAR' के लिए विशिष्ट डेटा प्रकारों को [AssemblyScript API](/developing/graph-ts/api/) में पेश करता है। +NEAR indexing 'NEAR' के लिए विशिष्ट डेटा प्रकारों को [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/) में पेश करता है। ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - ब्लॉक हैंडलर्स को एक `ब्लॉक` प्राप्त होगा - रसीद संचालकों को `ReceiptWithOutcome` प्राप्त होगा -अन्यथा, [AssemblyScript API](/developing/graph-ts/api/) का शेष भाग NEAR subgraph डेवलपर्स के लिए मैपिंग निष्पादन के दौरान उपलब्ध है। +अन्यथा, [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/) का शेष भाग NEAR subgraph डेवलपर्स के लिए मैपिंग निष्पादन के दौरान उपलब्ध है। -यह एक नई JSON पार्सिंग फ़ंक्शन को शामिल करता है - NEAR पर लॉग अक्सर स्ट्रिंगिफाइड JSONs के रूप में उत्पन्न होते हैं। एक नई `json.fromString(...)` फ़ंक्शन [JSON API](/developing/graph-ts/api/#json-api) का हिस्सा के रूप में उपलब्ध है, जिससे डेवलपर्स इन लॉग्स को आसानी से प्रोसेस कर सकते हैं। +यह एक नई JSON पार्सिंग फ़ंक्शन को शामिल करता है - NEAR पर लॉग अक्सर स्ट्रिंगिफाइड JSONs के रूप में उत्पन्न होते हैं। एक नई `json.fromString(...)` फ़ंक्शन [JSON API](/subgraphs/developing/creating/graph-ts/api/#json-api) का हिस्सा के रूप में उपलब्ध है, जिससे डेवलपर्स इन लॉग्स को आसानी से प्रोसेस कर सकते हैं। ## एक NEAR सबग्राफ की तैनाती @@ -228,7 +228,7 @@ NEAR को अनुक्रमित करने वाले ग्रा ## NEAR सबग्राफ को क्वेरी करना -NEAR सबग्राफ के लिए ग्राफक्यूएल एंडपॉइंट मौजूदा एपीआई इंटरफेस के साथ स्कीमा परिभाषा द्वारा निर्धारित किया जाता है। अधिक जानकारी के लिए कृपया [GraphQL API दस्तावेज़ीकरण](/querying/graphql-api/) पर जाएं। +NEAR सबग्राफ के लिए ग्राफक्यूएल एंडपॉइंट मौजूदा एपीआई इंटरफेस के साथ स्कीमा परिभाषा द्वारा निर्धारित किया जाता है। अधिक जानकारी के लिए कृपया [GraphQL API दस्तावेज़ीकरण](/subgraphs/querying/graphql-api/) पर जाएं। ## उदाहरण सबग्राफ @@ -276,7 +276,7 @@ NEAR सबग्राफ के लिए पेंडिंग कार् ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## संदर्भ diff --git a/website/pages/hi/subgraphs/cookbook/pruning.mdx b/website/pages/hi/subgraphs/cookbook/pruning.mdx index e583b0c2f373..f2ddfe9da791 100644 --- a/website/pages/hi/subgraphs/cookbook/pruning.mdx +++ b/website/pages/hi/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ indexerHints में तीन prune विकल्प होते हैं - prune: auto: आवश्यक न्यूनतम इतिहास को बनाए रखता है जैसा कि Indexer द्वारा निर्धारित किया गया है, जो क्वेरी प्रदर्शन को अनुकूलित करता है। यह सामान्यतः अनुशंसित सेटिंग है और यह सभी subgraphs के लिए डिफ़ॉल्ट है जो graph-cli >= 0.66.0 द्वारा बनाए गए हैं। - `prune: `: ऐतिहासिक ब्लॉकों को बनाए रखने की संख्या पर एक कस्टम सीमा निर्धारित करता है। -- `prune: never`: ऐतिहासिक डेटा का कोई छंटाई नहीं; पूरी इतिहास को बनाए रखता है और यह डिफ़ॉल्ट है यदि indexerHints अनुभाग नहीं है। `prune: never` को तब चुना जाना चाहिए यदि Time Travel Queries (/querying/graphql-api/#time-travel-queries) की आवश्यकता हो। +- `prune: never`: ऐतिहासिक डेटा का कोई छंटाई नहीं; पूरी इतिहास को बनाए रखता है और यह डिफ़ॉल्ट है यदि indexerHints अनुभाग नहीं है। `prune: never` को तब चुना जाना चाहिए यदि Time Travel Queries (/subgraphs/querying/graphql-api/#time-travel-queries) की आवश्यकता हो। हम अपने 'subgraph' में indexerHints जोड़ सकते हैं हमारे subgraph.yaml को अपडेट करके: @@ -32,9 +32,9 @@ dataSources: ## महत्वपूर्ण विचार -- यदि Time Travel Queries(/querying/graphql-api/#time-travel-queries) की आवश्यकता हो और प्रूनिंग भी की जाए, तो Time Travel Query कार्यक्षमता बनाए रखने के लिए प्रूनिंग को सही ढंग से किया जाना चाहिए। इसलिए, Time Travel Queries के साथ indexerHints: prune: auto का उपयोग करना सामान्यतः अनुशंसित नहीं है। इसके बजाय, उस ब्लॉक ऊंचाई तक सही ढंग से प्रून करने के लिए `indexerHints: prune: ` का उपयोग करें जो Time Travel Queries के लिए आवश्यक ऐतिहासिक डेटा को बनाए रखता है, या prune: never का उपयोग करें ताकि सभी डेटा बनाए रखा जा सके। +- यदि Time Travel Queries(/subgraphs/querying/graphql-api/#time-travel-queries) की आवश्यकता हो और प्रूनिंग भी की जाए, तो Time Travel Query कार्यक्षमता बनाए रखने के लिए प्रूनिंग को सही ढंग से किया जाना चाहिए। इसलिए, Time Travel Queries के साथ indexerHints: prune: auto का उपयोग करना सामान्यतः अनुशंसित नहीं है। इसके बजाय, उस ब्लॉक ऊंचाई तक सही ढंग से प्रून करने के लिए `indexerHints: prune: ` का उपयोग करें जो Time Travel Queries के लिए आवश्यक ऐतिहासिक डेटा को बनाए रखता है, या prune: never का उपयोग करें ताकि सभी डेटा बनाए रखा जा सके। -- यह 'grafting' (/cookbook/grafting/) को उस ब्लॉक ऊँचाई पर करना संभव नहीं है जो छंटनी (pruned) की गई है। यदि 'grafting' नियमित रूप से किया जाता है और छंटनी (pruning) की आवश्यकता है, तो यह अनुशंसा की जाती है कि `indexerHints: prune: ` का उपयोग किया जाए जो सटीक रूप से एक निश्चित संख्या में ब्लॉकों (जैसे, छह महीने के लिए पर्याप्त) को बनाए रखेगा। +- यह 'grafting' (/subgraphs/cookbook/grafting/) को उस ब्लॉक ऊँचाई पर करना संभव नहीं है जो छंटनी (pruned) की गई है। यदि 'grafting' नियमित रूप से किया जाता है और छंटनी (pruning) की आवश्यकता है, तो यह अनुशंसा की जाती है कि `indexerHints: prune: ` का उपयोग किया जाए जो सटीक रूप से एक निश्चित संख्या में ब्लॉकों (जैसे, छह महीने के लिए पर्याप्त) को बनाए रखेगा। ## निष्कर्ष @@ -42,14 +42,14 @@ Pruning का उपयोग indexerHints से करना एक सर् ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/hi/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/hi/subgraphs/cookbook/timeseries.mdx b/website/pages/hi/subgraphs/cookbook/timeseries.mdx index ab4f7619d180..1e4dfb156048 100644 --- a/website/pages/hi/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/hi/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/hi/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/hi/subgraphs/cookbook/transfer-to-the-graph.mdx index caa5f49f29fa..3e99667ab7cc 100644 --- a/website/pages/hi/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/hi/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### उदाहरण @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### अतिरिक्त संसाधन -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/hi/subgraphs/developing/creating/advanced.mdx b/website/pages/hi/subgraphs/developing/creating/advanced.mdx index b92e6528b52f..bfd12afcd2f0 100644 --- a/website/pages/hi/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/hi/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { यदि पैरेंट इकाई और परिणामी फ़ाइल डेटा स्रोत इकाई के बीच संबंध 1:1 है, तो सबसे सरल पैटर्न मूल इकाई को लुकअप के रूप में IPFS CID का उपयोग करके परिणामी फ़ाइल इकाई से लिंक करना है। यदि आपको अपनी नई फ़ाइल-आधारित संस्थाओं को मॉडलिंग करने में कठिनाई हो रही है, तो डिस्कॉर्ड पर संपर्क करें! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### फ़ाइलों को संसाधित करने के लिए एक नया हैंडलर बनाएँ -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0. यदि आप NFT मेटाडेटा को संबंधित टोकन से लिंक कर रहे हैं, तो टोकन इकाई से मेटाडेटा इकाई को संदर्भित करने के लिए मेटाडेटा के IPFS हैश का उपयोग करें। एक आईडी के रूप में IPFS हैश का उपयोग करके मेटाडेटा इकाई को सहेजें। -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### मौजूदा सबग्राफ पर ग्राफ्टिंग -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx index bcf85bba922e..fd52cda96906 100644 --- a/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/hi/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: असेंबलीस्क्रिप्ट एपीआई --- -> ध्यान दें: यदि आपने `graph-cli`/`graph-ts` version `0.22.0` से पहले एक subgragh बनाया है, तो आप AssemblyScript के पुराना संस्करण का उपयोग कर रहे हैं, हम अनुशंसा करते हैं कि [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> ध्यान दें: यदि आपने `graph-cli`/`graph-ts` version `0.22.0` से पहले एक subgragh बनाया है, तो आप AssemblyScript के पुराना संस्करण का उपयोग कर रहे हैं, हम अनुशंसा करते हैं कि [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). यह पृष्ठ दस्तावेज करता है कि Subgraph मैपिंग लिखते समय किन अंतर्निहित एपीआई का उपयोग किया जा सकता है। बॉक्स से बाहर दो प्रकार के एपीआई उपलब्ध हैं: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx index f4ddd954e659..f147a244ebca 100644 --- a/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/hi/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: . ग्राफ़ सीएलआई इनस्टॉल करें --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## अवलोकन -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## शुरू करना @@ -114,6 +114,6 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है। | | 0.0.4 | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है। | diff --git a/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx b/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx index cf6786579c03..df1edc8c2c7c 100644 --- a/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/hi/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### संपत्ति परिभाषित करना @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/hi/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/hi/subgraphs/developing/creating/starting-your-subgraph.mdx index 999393096533..de24bff19b47 100644 --- a/website/pages/hi/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/hi/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/hi/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/hi/subgraphs/developing/creating/subgraph-manifest.mdx index 3afa290667f2..0ed327ae8b8f 100644 --- a/website/pages/hi/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/hi/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). मेनिफेस्ट के लिए अद्यतन करने के लिए महत्वपूर्ण प्रविष्टियां हैं: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde दिए गए ब्लॉक के रूप में इतिहास की आवश्यकता है: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - उस ब्लॉक पर 'subgraph' को वापस लाना @@ -517,7 +517,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: विशिष्ट मात्रा में ऐतिहासिक डेटा बनाए रखने के लिए: diff --git a/website/pages/hi/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/hi/subgraphs/developing/creating/unit-testing-framework.mdx index 30433a184d2b..7d369ebf7700 100644 --- a/website/pages/hi/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/hi/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,7 @@ Global test coverage: 22.2% (2/9 handlers). > गंभीर: संदर्भ के साथ मान्य मॉड्यूल से WasmInstance नहीं बना सका: अज्ञात आयात: wasi_snapshot_preview1::fd_write परिभाषित नहीं किया गया है -इसका मतलब है कि आपने अपने कोड में ``console.log`\` का उपयोग किया है, जिसे AssemblyScript द्वारा सपोर्ट नहीं किया जाता है। कृपया [Logging API](/developing/graph-ts/api/#logging-api) का उपयोग करने पर विचार करें। +इसका मतलब है कि आपने अपने कोड में ``console.log`\` का उपयोग किया है, जिसे AssemblyScript द्वारा सपोर्ट नहीं किया जाता है। कृपया [Logging API](/subgraphs/developing/creating/graph-ts/api/#logging-api) का उपयोग करने पर विचार करें। > त्रुटि TS2554: अपेक्षित? तर्क, लेकिन मिला ?. > diff --git a/website/pages/hi/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/hi/subgraphs/developing/deploying/multiple-networks.mdx index 44447e580313..e4de34cb2268 100644 --- a/website/pages/hi/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/hi/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: मल्टीपल नेटवर्क्स पर एक Subgraph डिप्लॉय करना --- -यह पृष्ठ कई नेटवर्क पर एक subgraph को डिप्लॉय करने के तरीके को समझाता है। एक subgraph को डिप्लॉय करने के लिए, आपको पहले Graph CLI(https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) स्थापित करना होगा। यदि आपने पहले से एक subgraph नहीं बनाया है, तो Creating a subgraph (/developing/creating-a-subgraph). देखें। +यह पृष्ठ कई नेटवर्क पर एक subgraph को डिप्लॉय करने के तरीके को समझाता है। एक subgraph को डिप्लॉय करने के लिए, आपको पहले Graph CLI(https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) स्थापित करना होगा। यदि आपने पहले से एक subgraph नहीं बनाया है, तो Creating a subgraph (/developing/creating-a-subgraph/). देखें। ## सबग्राफ को कई नेटवर्क पर तैनात करना diff --git a/website/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx index b57efc206319..7e7ec4413bad 100644 --- a/website/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/hi/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> अतिरिक्त लिखित विवरण के लिए, Quick Start(/quick-start/) की समीक्षा करें। +> अतिरिक्त लिखित विवरण के लिए, Quick Start(/subgraphs/quick-start/) की समीक्षा करें। ### ग्राफ नेटवर्क के साथ सबग्राफ अनुकूलता In order to be supported by Indexers on The Graph Network, subgraphs must: -- एक supported network(/developing/supported-networks) को अनुक्रमित करें +- एक supported network(/supported-networks/) को अनुक्रमित करें - निम्नलिखित सुविधाओं में से किसी का उपयोग नहीं करना चाहिए: - ipfs.cat & ipfs.map - गैर-घातक त्रुटियाँ @@ -114,7 +114,7 @@ Subgraph Studio का उपयोग करके डैशबोर्ड प ## अपने Subgraph को प्रकाशित करें -अपने subgraph को सफलतापूर्वक प्रकाशित करने के लिए, publishing a subgraph(/publishing/publishing-a-subgraph/). की समीक्षा करें। +अपने subgraph को सफलतापूर्वक प्रकाशित करने के लिए, publishing a subgraph(/subgraphs/developing/publishing/publishing-a-subgraph/). की समीक्षा करें। ## अपने Subgraph को CLI के साथ संस्करण बनाना @@ -126,7 +126,7 @@ Subgraph Studio का उपयोग करके डैशबोर्ड प आप अपने subgraph के मेटाडेटा को बिना नई संस्करण प्रकाशित किए भी अपडेट कर सकते हैं। आप Studio में अपने subgraph विवरण (प्रोफ़ाइल चित्र, नाम, विवरण, आदि के अंतर्गत) को [Graph Explorer](https://thegraph.com/explorer). में Update Details नामक विकल्प को चेक करके अपडेट कर सकते हैं। यदि यह चेक किया गया है, तो एक ऑन-चेन लेनदेन उत्पन्न होगा जो Explorer में subgraph विवरण को अपडेट करेगा, बिना नई तैनाती के साथ नया संस्करण प्रकाशित किए। -> Note: नेटवर्क पर नए संस्करण को प्रकाशित करने से संबंधित लागतें हैं। लेनदेन शुल्क के अलावा, आपको ऑटो-माइग्रेटिंग सिग्नल पर क्यूरेशन टैक्स का एक भाग भी फंड करना होगा। यदि क्यूरेटरों ने इस पर सिग्नल नहीं किया है, तो आप अपने सबग्राफ का नया संस्करण प्रकाशित नहीं कर सकते। अधिक जानकारी के लिए, कृपया और पढ़ें यहाँ(/network/curating/). +> Note: नेटवर्क पर नए संस्करण को प्रकाशित करने से संबंधित लागतें हैं। लेनदेन शुल्क के अलावा, आपको ऑटो-माइग्रेटिंग सिग्नल पर क्यूरेशन टैक्स का एक भाग भी फंड करना होगा। यदि क्यूरेटरों ने इस पर सिग्नल नहीं किया है, तो आप अपने सबग्राफ का नया संस्करण प्रकाशित नहीं कर सकते। अधिक जानकारी के लिए, कृपया और पढ़ें यहाँ(/resources/roles/curating/). ## सबग्राफ संस्करणों का स्वचालित संग्रह diff --git a/website/pages/hi/subgraphs/developing/developer-faq.mdx b/website/pages/hi/subgraphs/developing/developer-faq.mdx index a035e4064eb8..3f99a88b5c9f 100644 --- a/website/pages/hi/subgraphs/developing/developer-faq.mdx +++ b/website/pages/hi/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ title: डेवलपर अक्सर पूछे जाने वाले ### 2. एक Subgraph बनाने का पहला कदम क्या है? -एक सबग्रह को सफलतापूर्वक बनाने के लिए, आपको The Graph CLI स्थापित करने की आवश्यकता होगी। आरंभ करने के लिए [Quick Start](/quick-start/) की समीक्षा करें। विस्तृत जानकारी के लिए, देखें [Creating a Subgraph](/developing/creating-a-subgraph/)। +एक सबग्रह को सफलतापूर्वक बनाने के लिए, आपको The Graph CLI स्थापित करने की आवश्यकता होगी। आरंभ करने के लिए [Quick Start](/subgraphs/quick-start/) की समीक्षा करें। विस्तृत जानकारी के लिए, देखें [Creating a Subgraph](/developing/creating-a-subgraph/)। ### 3. क्या मैं अभी भी एक subgraph बना सकता हूँ यदि मेरी स्मार्ट कॉन्ट्रैक्ट्स में कोई इवेंट्स नहीं हैं? @@ -34,7 +34,7 @@ title: डेवलपर अक्सर पूछे जाने वाले ### 7. आप अपने subgraph mappings से एक contract function को कैसे कॉल करें या एक सार्वजनिक state variable तक कैसे पहुँचें? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. क्या मैं अपने subgraph mappings में `ethers.js` या अन्य JS पुस्तकालय आयात कर सकता हूँ? @@ -80,13 +80,13 @@ docker pull graphprotocol/graph-node:latest ### 15. क्या मैं अपना subgraph हटा सकता हूँ? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## नेटवर्क से संबंधित। ### 16. The Graph द्वारा समर्थित नेटवर्क कौन से हैं? -आप समर्थित नेटवर्क की सूची [यहां](/Developing/supported-networks/) प्राप्त कर सकते हैं। +आप समर्थित नेटवर्क की सूची [यहां](/supported-networks/) प्राप्त कर सकते हैं। ### 17. क्या इवेंट हैंडलर्स के भीतर नेटवर्क (mainnet, Sepolia, local) के बीच अंतर करना संभव है? diff --git a/website/pages/hi/subgraphs/developing/introduction.mdx b/website/pages/hi/subgraphs/developing/introduction.mdx index 6c027c7e2b1c..cf15f2f11e38 100644 --- a/website/pages/hi/subgraphs/developing/introduction.mdx +++ b/website/pages/hi/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: विकसित होना --- -कोडिंग तुरंत शुरू करने के लिए, [डेवलपर क्विक स्टार्ट पर जाएं](/quick-start/)। +कोडिंग तुरंत शुरू करने के लिए, [डेवलपर क्विक स्टार्ट पर जाएं](/subgraphs/quick-start/)। ## अवलोकन @@ -27,4 +27,4 @@ The Graph पर, आप: एक Subgraph एक कस्टम API है जो ब्लॉकचेन डेटा पर आधारित होता है। यह ब्लॉकचेन से डेटा निकालता है, उसे प्रोसेस करता है, और उसे इस तरह से संग्रहित करता है कि उसे GraphQL के माध्यम से आसानी से क्वेरी किया जा सके। -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 2e1bc7f60474..e2688568df1b 100644 --- a/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/hi/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ title: विकेंद्रीकृत नेटवर्क के लि जब आप एक subgraph को विकेंद्रीकृत नेटवर्क पर प्रकाशित करते हैं, तो आप इसे उपलब्ध कराते हैं: -- [Curators](/network/curating/) को इसे क्यूरेट करना शुरू करने के लिए। -- [Indexers](/network/indexing/) को इसे इंडेक्स करना शुरू करने के लिए। +- [Curators](/resources/roles/curating/) को इसे क्यूरेट करना शुरू करने के लिए। +- [Indexers](/indexing/overview/) को इसे इंडेक्स करना शुरू करने के लिए। -नीचे दिए गए [supported networks](/developing/supported-networks/) की सूची देखें। +नीचे दिए गए [supported networks](/supported-networks/) की सूची देखें। ## Subgraph Studio से प्रकाशित @@ -21,9 +21,9 @@ title: विकेंद्रीकृत नेटवर्क के लि एक मौजूदा subgraph के सभी प्रकाशित संस्करण कर सकते हैं: -- Arbitrum One पर प्रकाशित करें। [Arbitrum पर The Graph Network के बारे में अधिक जानें](/arbitrum/arbitrum-faq/)। +- Arbitrum One पर प्रकाशित करें। [Arbitrum पर The Graph Network के बारे में अधिक जानें](/archived/arbitrum/arbitrum-faq/)। -- किसी भी [समर्थित नेटवर्क](/developing/supported-networks/) पर डेटा इंडेक्स करें, चाहे वह नेटवर्क हो जिस पर subgraph प्रकाशित किया गया था। +- किसी भी [समर्थित नेटवर्क](/supported-networks/) पर डेटा इंडेक्स करें, चाहे वह नेटवर्क हो जिस पर subgraph प्रकाशित किया गया था। ### प्रकाशित सबग्राफ के लिए मेटाडेटा अपडेट करना @@ -68,13 +68,13 @@ FLAGS - आप उपग्राफ फीचर उपयोग के आधार पर इंडेक्सिंग पुरस्कार पात्रता की जांच [यहाँ](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) कर सकते हैं। -- विशिष्ट समर्थित नेटवर्क की जांच [यहाँ](/developing/supported-networks/) की जा सकती है। +- विशिष्ट समर्थित नेटवर्क की जांच [यहाँ](/supported-networks/) की जा सकती है। > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > यदि आपका Subgraph पुरस्कारों के लिए पात्र है, तो यह अनुशंसा की जाती है कि आप अपने Subgraph को कम से कम 3,000 GRT के साथ क्यूरेट करें ताकि अधिक Indexer को आपके सबग्राफ़ को इंडेक्स करने के लिए आकर्षित किया जा सके। -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -90,4 +90,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -The Graph नेटवर्क पर [Curating](/network/curating/) के बारे में अधिक जानें। +The Graph नेटवर्क पर [Curating](/resources/roles/curating/) के बारे में अधिक जानें। diff --git a/website/pages/hi/subgraphs/developing/subgraphs.mdx b/website/pages/hi/subgraphs/developing/subgraphs.mdx index 4599a8cc79d9..1000ed87a652 100644 --- a/website/pages/hi/subgraphs/developing/subgraphs.mdx +++ b/website/pages/hi/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ subgraph मैनिफेस्ट, subgraph.yaml, उन स्मार् 1. [एक subgraph बनाएँ](/developing/creating-a-subgraph/) 2. [डिप्लॉय a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [एक 'subgraph' का परीक्षण करें](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [एक subgraph प्रकाशित करें](/publishing/publishing-a-subgraph/) -5. [subgraph पर संकेत](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [एक subgraph प्रकाशित करें](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [subgraph पर संकेत](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/hi/subgraphs/explorer.mdx b/website/pages/hi/subgraphs/explorer.mdx index 5179d4b377e2..f4457a612160 100644 --- a/website/pages/hi/subgraphs/explorer.mdx +++ b/website/pages/hi/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers दोनों क्वेरी फीस और इंडेक् - इंडेक्सिंग पैरामीटर को टेबल के दाहिने ओर क्लिक करके या किसी इंडेक्सर के प्रोफ़ाइल में जाकर 'Delegate' बटन पर क्लिक करके सेट किया जा सकता है। -इंडेक्सर कैसे बनें, इस बारे में अधिक जानने के लिए, आप [आधिकारिक दस्तावेज़ीकरण](/network/indexing/) या [द ग्राफ एकेडमी इंडेक्सर गाइड्स।](https://thegraph.academy/delegators/ पर नज़र डाल सकते हैं चूइंग-इंडेक्सर्स/) +इंडेक्सर कैसे बनें, इस बारे में अधिक जानने के लिए, आप [आधिकारिक दस्तावेज़ीकरण](/indexing/overview/) या [द ग्राफ एकेडमी इंडेक्सर गाइड्स।](https://thegraph.academy/delegators/ पर नज़र डाल सकते हैं चूइंग-इंडेक्सर्स/) ![अनुक्रमण विवरण फलक](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ Indexers दोनों क्वेरी फीस और इंडेक् ![एक्सप्लोरर छवि 6](/img/Curation-Overview.png) -अगर आप 'Curator' भूमिका के बारे में अधिक जानना चाहते हैं, तो आप ऐसा कर सकते हैं, यहाँ पर जाएं: [official documentation.](/network/curating/) या [The Graph Academy](https://thegraph.academy/curators/). +अगर आप 'Curator' भूमिका के बारे में अधिक जानना चाहते हैं, तो आप ऐसा कर सकते हैं, यहाँ पर जाएं: [official documentation.](/resources/roles/curating/) या [The Graph Academy](https://thegraph.academy/curators/). ### 3. प्रतिनिधि @@ -113,7 +113,7 @@ Delegators तालिका में आप समुदाय में स - वर्तमान में उनके पास प्रोटोकॉल में जीआरटी की कुल राशि है - वे आखिरी बार 'delegated' की तारीख -यदि आप Delegator बनने के बारे में अधिक जानना चाहते हैं, तो [आधिकारिक दस्तावेज़](/network/delegating/) देखें या [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) पर जाएं। +यदि आप Delegator बनने के बारे में अधिक जानना चाहते हैं, तो [आधिकारिक दस्तावेज़](/resources/roles/delegating/) देखें या [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) पर जाएं। ## नेटवर्क diff --git a/website/pages/hi/subgraphs/querying/best-practices.mdx b/website/pages/hi/subgraphs/querying/best-practices.mdx index 6f0a4716b025..39a8ec1b5172 100644 --- a/website/pages/hi/subgraphs/querying/best-practices.mdx +++ b/website/pages/hi/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - प्रत्येक `क्वेरीनाम` का उपयोग प्रति ऑपरेशन केवल एक बार किया जाना चाहिए। - प्रत्येक `फ़ील्ड` का चयन में केवल एक बार उपयोग किया जाना चाहिए (हम `आईडी` को `टोकन` के अंतर्गत दो बार क्वेरी नहीं कर सकते हैं) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - किसी तर्क को असाइन किया गया कोई भी चर उसके प्रकार से मेल खाना चाहिए। - चरों की दी गई सूची में, उनमें से प्रत्येक अद्वितीय होना चाहिए। - सभी परिभाषित चर का उपयोग किया जाना चाहिए। > ध्यान दें: इन नियमों का पालन न करने पर The Graph API से त्रुटि होगी। -नियमों की पूरी सूची और कोड उदाहरणों के लिए, [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/) देखें। +नियमों की पूरी सूची और कोड उदाहरणों के लिए, [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/) देखें। ### एक ग्राफ़क्यूएल एपीआई के लिए एक प्रश्न भेजना @@ -69,7 +69,7 @@ GraphQL एक भाषा और प्रथाओं का सेट है इसका मतलब है कि आप एक GraphQL API को मानक `fetch` (स्थानीय रूप से या `@whatwg-node/fetch` या `isomorphic-fetch` के माध्यम से) का उपयोग करके क्वेरी कर सकते हैं। -हालांकि, जैसा कि [“Querying from an Application”](/querying/querying-from-an-application/) में उल्लेख किया गया है, यह अनुशंसा की जाती है कि आप `graph-client` का उपयोग करें, जो निम्नलिखित अद्वितीय विशेषताओं का समर्थन करता है: +हालांकि, जैसा कि [“Querying from an Application”](/subgraphs/querying/from-an-application/) में उल्लेख किया गया है, यह अनुशंसा की जाती है कि आप `graph-client` का उपयोग करें, जो निम्नलिखित अद्वितीय विशेषताओं का समर्थन करता है: - क्रॉस-चेन सबग्राफ हैंडलिंग: एक ही क्वेरी में कई सबग्राफ से पूछताछ - [स्वचालित ब्लॉक ट्रैकिंग](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -अधिक GraphQL क्लाइंट विकल्पों को [“Querying from an Application”](/querying/querying-from-an-application/) में कवर किया गया है। +अधिक GraphQL क्लाइंट विकल्पों को [“Querying from an Application”](/subgraphs/querying/from-an-application/) में कवर किया गया है। --- diff --git a/website/pages/hi/subgraphs/querying/graphql-api.mdx b/website/pages/hi/subgraphs/querying/graphql-api.mdx index 6af99067b807..be1c4356fe10 100644 --- a/website/pages/hi/subgraphs/querying/graphql-api.mdx +++ b/website/pages/hi/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ The Graph में उपयोग किए जाने वाले GraphQL [GraphQL](https://graphql.org/learn/) APIs के लिए एक क्वेरी भाषा और आपके मौजूदा डेटा के साथ उन क्वेरीज़ को पूरा करने के लिए एक रनटाइम। The Graph सबग्राफ को क्वेरी करने के लिए GraphQL का उपयोग करता है। -GraphQL की बड़ी भूमिका को समझने के लिए, [developing](/network/developing/) और [creating a subgraph](/developing/creating-a-subgraph/) की समीक्षा करें। +GraphQL की बड़ी भूमिका को समझने के लिए, [developing](/subgraphs/developing/introduction/) और [creating a subgraph](/developing/creating-a-subgraph/) की समीक्षा करें। ## GraphQL के साथ क्वेरीज़ diff --git a/website/pages/hi/subgraphs/querying/introduction.mdx b/website/pages/hi/subgraphs/querying/introduction.mdx index 4ea0563584d3..d58d26537009 100644 --- a/website/pages/hi/subgraphs/querying/introduction.mdx +++ b/website/pages/hi/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: ग्राफ़ को क्वेरी करना When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/hi/subgraphs/quick-start.mdx b/website/pages/hi/subgraphs/quick-start.mdx index aa55257484bd..a1f3eeea024b 100644 --- a/website/pages/hi/subgraphs/quick-start.mdx +++ b/website/pages/hi/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: जल्दी शुरू --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## आवश्यक शर्तें - एक क्रिप्टो वॉलेट -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. अपने Subgraph को ग्राफ़ के The Graph Network पर प्रकाशित करें -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Subgraph Studio से प्रकाशित @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -अपने डिप्लॉयमेंट को कस्टमाइज़ करने के लिए, देखें [Publishing a Subgraph](/publishing/publishing-a-subgraph/)। +अपने डिप्लॉयमेंट को कस्टमाइज़ करने के लिए, देखें [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/)। #### Adding signal to your subgraph @@ -169,7 +169,7 @@ graph publish - कम से कम 3,000 GRT का चयन करना अनुशंसित है ताकि 3 Indexer को आकर्षित किया जा सके। Subgraph फ़ीचर उपयोग और समर्थित नेटवर्क के आधार पर पुरस्कार पात्रता की जांच करें। -क्यूरेशन के बारे में अधिक जानने के लिए, पढ़ें [Curating](/network/curating/)। +क्यूरेशन के बारे में अधिक जानने के लिए, पढ़ें [Curating](/resources/roles/curating/)। गैस लागत को बचाने के लिए, आप इसे प्रकाशित करते समय अपने Subgraph को उसी लेनदेन में क्यूरेट कर सकते हैं, इस विकल्प का चयन करके: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -अपने subgraph से data query करने के बारे में अधिक जानकारी के लिए, अधिक पढ़ें [Querying The Graph](/querying/querying-the-graph/)। +अपने subgraph से data query करने के बारे में अधिक जानकारी के लिए, अधिक पढ़ें [Querying The Graph](/subgraphs/querying/introduction/)। diff --git a/website/pages/hi/substreams/sps/introduction.mdx b/website/pages/hi/substreams/sps/introduction.mdx index 3e7e817db516..f6ef302e9f53 100644 --- a/website/pages/hi/substreams/sps/introduction.mdx +++ b/website/pages/hi/substreams/sps/introduction.mdx @@ -6,7 +6,7 @@ Substreams पैकेज (.spkg) का उपयोग करके, आप इस तकनीक को सक्षम करने के दो तरीके हैं: -Using Substreams triggers(/substreams/sps/triggers): किसी भी Substreams मॉड्यूल से उपभोग करें, Protobuf मॉडल को एक subgraph हैंडलर के माध्यम से आयात करके और सभी लॉजिक को एक subgraph में स्थानांतरित करें। यह विधि subgraph संस्थाओं को सीधे subgraph में बनाती है। +Using Substreams triggers(/substreams/sps/triggers/): किसी भी Substreams मॉड्यूल से उपभोग करें, Protobuf मॉडल को एक subgraph हैंडलर के माध्यम से आयात करके और सभी लॉजिक को एक subgraph में स्थानांतरित करें। यह विधि subgraph संस्थाओं को सीधे subgraph में बनाती है। Entity Changes (https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out) का उपयोग करके: Substreams में अधिक लॉजिक लिखने से, आप सीधे graph-node में मॉड्यूल का आउटपुट प्राप्त कर सकते हैं। graph-node में, आप Substreams डेटा का उपयोग करके अपने उपग्रह संस्थाएं बना सकते हैं। diff --git a/website/pages/hi/substreams/sps/sps-faq.mdx b/website/pages/hi/substreams/sps/sps-faq.mdx index d874a6641801..ef6023edacc8 100644 --- a/website/pages/hi/substreams/sps/sps-faq.mdx +++ b/website/pages/hi/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. [नवीनतम Substreams Codegen टूल](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) आपको बिना किसी कोड के एक Substreams प्रोजेक्ट शुरू करने की अनुमति देगा। @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/hi/substreams/sps/triggers.mdx b/website/pages/hi/substreams/sps/triggers.mdx index 4de0022baf7c..ca41d30e1f65 100644 --- a/website/pages/hi/substreams/sps/triggers.mdx +++ b/website/pages/hi/substreams/sps/triggers.mdx @@ -4,7 +4,7 @@ title: सबस्ट्रीम्स ट्रिगर्स कस्टम ट्रिगर्स आपको अपने subgraph मैपिंग फ़ाइल और इकाइयों (टेबल और फ़ील्ड के समान) में डेटा सीधे भेजने की अनुमति देते हैं, जो GraphQL परत का पूरा उपयोग करने में सक्षम बनाते हैं। अपने Substreams मॉड्यूल द्वारा उत्पन्न Protobuf परिभाषाओं को आयात करके, आप अपने subgraph के हैंडलर के भीतर इस डेटा को प्राप्त और प्रोसेस कर सकते हैं, जो subgraph ढांचे के भीतर कुशल और सुव्यवस्थित डेटा प्रबंधन सुनिश्चित करता है। -> नोट: यदि आपने पहले से ऐसा नहीं किया है, तो अपने पहले प्रोजेक्ट को Development Container में स्कैफोल्ड करने के लिए यहाँ (/substreams/sps/introduction) पाए जाने वाले How-To Guides में से एक पर जाएं। +> नोट: यदि आपने पहले से ऐसा नहीं किया है, तो अपने पहले प्रोजेक्ट को Development Container में स्कैफोल्ड करने के लिए यहाँ (/substreams/sps/introduction/) पाए जाने वाले How-To Guides में से एक पर जाएं। निम्नलिखित कोड यह दर्शाता है कि कैसे एक handleTransactions फ़ंक्शन को एक subgraph हैंडलर में परिभाषित किया जा सकता है। यह फ़ंक्शन कच्चे Substreams बाइट्स को एक पैरामीटर के रूप में प्राप्त करता है और उन्हें एक Transactions ऑब्जेक्ट में डिकोड करता है। प्रत्येक लेनदेन के लिए, एक नई subgraph एंटिटी बनाई जाती है। @@ -34,4 +34,4 @@ export function handleTransactions(bytes: Uint8Array): void { 2. लेनदेन पर लूप करना 3. प्रत्येक लेनदेन के लिए एक नया subgraph entity बनाएं -ड्रैगर-आधारित एक उपग्राफ के विस्तृत उदाहरण के लिए, यहां क्लिक करें(/substreams/sps/tutorial). +ड्रैगर-आधारित एक उपग्राफ के विस्तृत उदाहरण के लिए, यहां क्लिक करें(/substreams/sps/tutorial/). diff --git a/website/pages/hi/supported-networks.mdx b/website/pages/hi/supported-networks.mdx index fc8166f0653f..f7996d41eec5 100644 --- a/website/pages/hi/supported-networks.mdx +++ b/website/pages/hi/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - सबग्राफ स्टूडियो निर्भर करता है अंतर्निहित प्रौद्योगिकियों की स्थिरता और विश्वसनीयता पर, जैसे JSON-RPC, फायरहोस और सबस्ट्रीम्स एंडपॉइंट्स। - Gnosis Chain पर सबग्राफ इंडेक्सिंग को अब `gnosis` नेटवर्क पहचानकर्ता (network identifier) के साथ डिप्लॉय किया जा सकता है। diff --git a/website/pages/it/about.mdx b/website/pages/it/about.mdx index d1cfbfad3b82..3060784eac83 100644 --- a/website/pages/it/about.mdx +++ b/website/pages/it/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/it/archived/arbitrum/arbitrum-faq.mdx b/website/pages/it/archived/arbitrum/arbitrum-faq.mdx index 220dbe4480c8..4b6ef7df03fc 100644 --- a/website/pages/it/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/it/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Per sfruttare l'utilizzo di The Graph su L2, utilizza il selettore a discesa per ## In quanto sviluppatore di subgraph, consumatore di dati, Indexer, Curator o Delegator, cosa devo fare ora? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Tutto è stato testato accuratamente e un piano di contingenza è in atto per ga ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ Il bridge è stato rigorosamente sottoposto ad [audit](https://code4rena.com/con Aggiungere GRT al tuo saldo di pagamento su Arbitrum può essere fatto con un solo click in [Subgraph Studio](https://thegraph.com/studio/). Sarai in grado di trasferire facilmente i tuoi GRT su Arbitrum e compilare le tue chiavi API in una sola transazione. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx index a5252f121a00..41777b5445e2 100644 --- a/website/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/it/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Posso usare lo stesso wallet utilizzato su Ethereum mainnet? -Se stai usando un wallet [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), puoi utilizzare lo stesso address. Se il tuo wallet su Ethereum mainnet è un contratto (ad esempio un multisig), allora dovrai specificare un [wallet address Arbitrum](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) a cui verrà inviato il trasferimento. Controlla attentamente l'address poiché qualsiasi trasferimento a un indirizzo errato può comportare una perdita permanente. Se desideri utilizzare un multisig su L2, assicurati di deployare un contratto multisig su Arbitrum One. +Se stai usando un wallet [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), puoi utilizzare lo stesso address. Se il tuo wallet su Ethereum mainnet è un contratto (ad esempio un multisig), allora dovrai specificare un [wallet address Arbitrum](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) a cui verrà inviato il trasferimento. Controlla attentamente l'address poiché qualsiasi trasferimento a un indirizzo errato può comportare una perdita permanente. Se desideri utilizzare un multisig su L2, assicurati di deployare un contratto multisig su Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx index e516573fd4d9..485f34a70c97 100644 --- a/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/it/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/it/archived/sunrise.mdx b/website/pages/it/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/it/archived/sunrise.mdx +++ b/website/pages/it/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/it/contracts.mdx b/website/pages/it/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/it/contracts.mdx +++ b/website/pages/it/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/it/indexing/chain-integration-overview.mdx b/website/pages/it/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/it/indexing/chain-integration-overview.mdx +++ b/website/pages/it/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/it/indexing/new-chain-integration.mdx b/website/pages/it/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/it/indexing/new-chain-integration.mdx +++ b/website/pages/it/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/it/indexing/overview.mdx b/website/pages/it/indexing/overview.mdx index e7ed427ea8ef..923ccdf4d87f 100644 --- a/website/pages/it/indexing/overview.mdx +++ b/website/pages/it/indexing/overview.mdx @@ -87,7 +87,7 @@ Una volta chiusa un'allocation, gli sconti possono essere richiesti dall'Indexer ### Che cos'è la query fee cut e la indexing reward cut? -I valori di `queryFeeCut` e `indexingRewardCut` sono parametri di delega che l'Indexer può impostare insieme ai cooldownBlocks per controllare la distribuzione dei GRT tra l'Indexer i suoi Delegator. Per le istruzioni sull'impostazione dei parametri di delega, si vedano gli ultimi passi di [Staking nel Protocollo](/network/indexing/#stake-in-the-protocol). +I valori di `queryFeeCut` e `indexingRewardCut` sono parametri di delega che l'Indexer può impostare insieme ai cooldownBlocks per controllare la distribuzione dei GRT tra l'Indexer i suoi Delegator. Per le istruzioni sull'impostazione dei parametri di delega, si vedano gli ultimi passi di [Staking nel Protocollo](/indexing/overview/#stake-in-the-protocol). - **queryFeeCut** - la % delle riduzioni delle tariffe di query che verrà distribuita all'Indexer. Se questa opzione è impostata al 95%, l'Indexer riceverà il 95% delle tariffe di query guadagnate alla chiusura di un'allocazione, mentre il restante 5% andrà ai Delegator. @@ -121,7 +121,7 @@ Gli Indexer possono differenziarsi applicando tecniche avanzate per prendere dec ### Quali sono le precauzioni di base per la sicurezza che un Indexer dovrebbe adottare? -- **Operator wallet** - La creazione di un operator wallet è una precauzione importante perché consente all'Indexer di mantenere una separazione tra le chiavi che controllano il stake e quelle che controllano le operazioni quotidiane. Vedere[ Stake al protocollo](/network/indexing/#stake-in-the-protocol) per le istruzioni. +- **Operator wallet** - La creazione di un operator wallet è una precauzione importante perché consente all'Indexer di mantenere una separazione tra le chiavi che controllano il stake e quelle che controllano le operazioni quotidiane. Vedere[ Stake al protocollo](/indexing/overview/#stake-in-the-protocol) per le istruzioni. - **Firewall** - Solo l'Indexer service deve essere esposto pubblicamente e occorre prestare particolare attenzione a bloccare le porte di amministrazione e l'accesso al database: l'endpoint JSON-RPC di the Graph Node (porta predefinita: 8030), l'endpoint API di gestione dell'Indexer (porta predefinita: 18000) e l'endpoint del database Postgres (porta predefinita: 5432) non devono essere esposti. @@ -375,7 +375,7 @@ Per partecipare con successo alla rete è necessario un monitoraggio e un'intera #### Per cominciare -L'Indexer Agent ed l'Indexer service devono essere collocati insieme all'infrastruttura di The Graph Node. Ci sono molti modi per impostare ambienti di esecuzione virtuali per i componenti di Indexer; qui spiegheremo come eseguirli su baremetal usando pacchetti NPM o sorgenti, oppure tramite kubernetes e docker su Google Cloud Kubernetes Engine. Se questi esempi di configurazione non si adattano bene alla vostra infrastruttura, è probabile che ci sia una community guide a cui fare riferimento; fate un salto su [Discord](https://discord.gg/graphprotocol)! Ricordatevi di fare [stake nel protocollo](/network/indexing/#stake-in-the-protocol) prima di avviare i componenti dell'Indexer! +L'Indexer Agent ed l'Indexer service devono essere collocati insieme all'infrastruttura di The Graph Node. Ci sono molti modi per impostare ambienti di esecuzione virtuali per i componenti di Indexer; qui spiegheremo come eseguirli su baremetal usando pacchetti NPM o sorgenti, oppure tramite kubernetes e docker su Google Cloud Kubernetes Engine. Se questi esempi di configurazione non si adattano bene alla vostra infrastruttura, è probabile che ci sia una community guide a cui fare riferimento; fate un salto su [Discord](https://discord.gg/graphprotocol)! Ricordatevi di fare [stake nel protocollo](/indexing/overview/#stake-in-the-protocol) prima di avviare i componenti dell'Indexer! #### Dai pacchetti NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Utilizzo di K8s e Terraform -Vedere la sezione [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Vedere la sezione [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Utilizzo @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Una volta che l'Indexer ha messo in staking i GRT nel protocollo, gli [Indexer components](/network/indexing/#indexer-components) possono essere avviati e iniziare le loro interazioni con la rete. +Una volta che l'Indexer ha messo in staking i GRT nel protocollo, gli [Indexer components](/indexing/overview/#indexer-components) possono essere avviati e iniziare le loro interazioni con la rete. #### Approvare i token @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Si raccomanda agli Indexer di utilizzare la funzionalità di sincronizzazione offchain per sincronizzare le distribuzioni dei subgraph con chainhead prima di creare l'allocazione on-chain. Questa funzione è particolarmente utile per i subgraph che possono richiedere più di 28 epoche per la sincronizzazione o che hanno qualche possibilità di fallire in modo indeterminato. diff --git a/website/pages/it/indexing/tap.mdx b/website/pages/it/indexing/tap.mdx index ed40e829a2cb..a07a2f6c98a3 100644 --- a/website/pages/it/indexing/tap.mdx +++ b/website/pages/it/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/it/resources/benefits.mdx b/website/pages/it/resources/benefits.mdx index 8a3869a26c8c..e514868affa4 100644 --- a/website/pages/it/resources/benefits.mdx +++ b/website/pages/it/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. La curation del segnale su un subgraph è opzionale, una tantum, a costo zero (ad esempio, $1.000 in segnale possono essere curati su un subgraph e successivamente ritirati, con un potenziale di guadagno nel processo). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy In conclusione: The Graph Network è meno costosa, più facile da usare e produce risultati superiori rispetto alla gestione locale di `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/it/resources/roles/curating.mdx b/website/pages/it/resources/roles/curating.mdx index 7ee7f33834e6..39d146502580 100644 --- a/website/pages/it/resources/roles/curating.mdx +++ b/website/pages/it/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Come segnalare -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) Un curator può scegliere di segnalare su una versione specifica del subgraph, oppure può scegliere di far migrare automaticamente il proprio segnale alla versione di produzione più recente di quel subgraph. Entrambe le strategie sono valide e hanno i loro pro e contro. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Il mercato delle query è intrinsecamente giovane per The Graph e c'è il rischio che la vostra %APY possa essere inferiore a quella prevista a causa delle dinamiche di mercato nascenti. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Un subgraph può fallire a causa di un bug. Un subgraph fallito non matura commissioni della query. Di conseguenza, si dovrà attendere che lo sviluppatore risolva il bug e distribuisca una nuova versione. - Se siete iscritti alla versione più recente di un subgraph, le vostre quote di partecipazione migreranno automaticamente a quella nuova versione. Questo comporta una tassa di curation di 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/it/resources/tokenomics.mdx b/website/pages/it/resources/tokenomics.mdx index cab957ee77ac..701baf8b4d51 100644 --- a/website/pages/it/resources/tokenomics.mdx +++ b/website/pages/it/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Eseguire query di un subgraph esistente -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/it/subgraphs/billing.mdx b/website/pages/it/subgraphs/billing.mdx index dec5cfdadc12..f3f52bbf35ee 100644 --- a/website/pages/it/subgraphs/billing.mdx +++ b/website/pages/it/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/it/subgraphs/cookbook/arweave.mdx b/website/pages/it/subgraphs/cookbook/arweave.mdx index 4c35f4ee8e2e..2098d5ab5932 100644 --- a/website/pages/it/subgraphs/cookbook/arweave.mdx +++ b/website/pages/it/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/it/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/it/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/it/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/it/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/it/subgraphs/cookbook/cosmos.mdx b/website/pages/it/subgraphs/cookbook/cosmos.mdx index cd23a3742f86..dddfbff521d0 100644 --- a/website/pages/it/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/it/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/it/subgraphs/cookbook/derivedfrom.mdx b/website/pages/it/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/it/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/it/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/it/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/it/subgraphs/cookbook/grafting-hotfix.mdx index 0a0767655660..53c1bae83194 100644 --- a/website/pages/it/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/it/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/it/subgraphs/cookbook/grafting.mdx b/website/pages/it/subgraphs/cookbook/grafting.mdx index d5ab9bbbc47a..8ec621c2ace6 100644 --- a/website/pages/it/subgraphs/cookbook/grafting.mdx +++ b/website/pages/it/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/it/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/it/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/it/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/it/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/it/subgraphs/cookbook/near.mdx b/website/pages/it/subgraphs/cookbook/near.mdx index f1d61e913ca5..97aff10ff8d2 100644 --- a/website/pages/it/subgraphs/cookbook/near.mdx +++ b/website/pages/it/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## Riferimenti diff --git a/website/pages/it/subgraphs/cookbook/pruning.mdx b/website/pages/it/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/it/subgraphs/cookbook/pruning.mdx +++ b/website/pages/it/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/it/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/it/subgraphs/cookbook/timeseries.mdx b/website/pages/it/subgraphs/cookbook/timeseries.mdx index 5c7e78871d22..eeb246a2b3d0 100644 --- a/website/pages/it/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/it/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/it/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/it/subgraphs/cookbook/transfer-to-the-graph.mdx index be40d06f45c0..0acdb716eef6 100644 --- a/website/pages/it/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/it/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Esempio @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/it/subgraphs/developing/creating/advanced.mdx b/website/pages/it/subgraphs/developing/creating/advanced.mdx index 2638c71c7190..b3bf69928664 100644 --- a/website/pages/it/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/it/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Se la relazione è 1:1 tra l'entità genitore e l'entità data source file risultante, il modello più semplice è quello di collegare l'entità genitore a un'entità file risultante utilizzando il CID IPFS come lookup. Contattateci su Discord se avete difficoltà a modellare le vostre nuove entità basate su file! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### Creare un nuovo gestore per elaborare i file -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Inoltre, non è possibile creare data source da una data source file, sia essa u Se si collegano i metadati NFT ai token corrispondenti, utilizzare l'hash IPFS dei metadati per fare riferimento a un'entità Metadata dall'entità Token. Salvare l'entità Metadata usando l'hash IPFS come ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting su subgraph esistenti -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx index a1bafe444daa..3d017c6425f6 100644 --- a/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/it/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: API AssemblyScript --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ La `apiVersion` nel manifest del subgraph specifica la versione dell'API di mapp | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Aggiunte le classi `TransactionReceipt` e `Log` ai tipi di Ethereum
Aggiunto il campo `receipt` all'oggetto Ethereum Event | | 0.0.6 | Aggiunto il campo `nonce` all'oggetto Ethereum Transaction
Aggiunto `baseFeePerGas` all'oggetto Ethereum Block | -| 0.0.5 | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` | | 0.0.4 | Aggiunto il campo `functionSignature` all'oggetto Ethereum SmartContractCall | | 0.0.3 | Aggiunto il campo `from` all'oggetto Ethereum Call
`etherem.call.address` rinominato in `ethereum.call.to` | | 0.0.2 | Aggiunto il campo `input` all'oggetto Ethereum Transaction | diff --git a/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx index bc62da7231bc..da587ecf3f60 100644 --- a/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/it/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Installare the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Panoramica -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ I file ABI devono corrispondere al vostro contratto. Esistono diversi modi per o | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/it/subgraphs/developing/creating/ql-schema.mdx b/website/pages/it/subgraphs/developing/creating/ql-schema.mdx index eac7c291bb70..77d065c06881 100644 --- a/website/pages/it/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/it/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/it/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/it/subgraphs/developing/creating/starting-your-subgraph.mdx index 8a73865b5656..c448c25bf01f 100644 --- a/website/pages/it/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/it/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/it/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/it/subgraphs/developing/creating/subgraph-manifest.mdx index 43e510cf1a7a..559f67852565 100644 --- a/website/pages/it/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/it/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). Le voci importanti da aggiornare per il manifesto sono: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/it/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/it/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/it/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/it/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx index d0921b13e966..112910f93df1 100644 --- a/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/it/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### Compatibilità del subgraph con The Graph Network In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - Non deve utilizzare nessuna delle seguenti funzioni: - ipfs.cat & ipfs.map - Errori non fatali @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Archiviazione automatica delle versioni del subgraph diff --git a/website/pages/it/subgraphs/developing/developer-faq.mdx b/website/pages/it/subgraphs/developing/developer-faq.mdx index 85dccad933b0..8a457a3db5c3 100644 --- a/website/pages/it/subgraphs/developing/developer-faq.mdx +++ b/website/pages/it/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/it/subgraphs/developing/introduction.mdx b/website/pages/it/subgraphs/developing/introduction.mdx index 919c18774f11..f99cd534a1f6 100644 --- a/website/pages/it/subgraphs/developing/introduction.mdx +++ b/website/pages/it/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Sviluppo --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Panoramica @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 485a77da47ea..fa169fb15220 100644 --- a/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/it/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Aggiornamento dei metadati per un subgraph pubblicato @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/it/subgraphs/developing/subgraphs.mdx b/website/pages/it/subgraphs/developing/subgraphs.mdx index ba810051a7c4..9474eea4c0e1 100644 --- a/website/pages/it/subgraphs/developing/subgraphs.mdx +++ b/website/pages/it/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/it/subgraphs/explorer.mdx b/website/pages/it/subgraphs/explorer.mdx index 7908d3ee7496..96fdd3d5d336 100644 --- a/website/pages/it/subgraphs/explorer.mdx +++ b/website/pages/it/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Per saperne di più su come diventare un Indexer, è possibile consultare la [documentazione ufficiale](/network/indexing/) oppure [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +Per saperne di più su come diventare un Indexer, è possibile consultare la [documentazione ufficiale](/indexing/overview/) oppure [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Pannello dei dettagli di indicizzazione](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegator @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Quantità totale di GRT che hanno attualmente nel protocollo - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## La rete diff --git a/website/pages/it/subgraphs/querying/best-practices.mdx b/website/pages/it/subgraphs/querying/best-practices.mdx index a0eb269cc5fc..ecdef4d91dc7 100644 --- a/website/pages/it/subgraphs/querying/best-practices.mdx +++ b/website/pages/it/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Ogni `queryName` deve essere usato una sola volta per ogni operazione. - Ogni `field` deve essere utilizzato una sola volta in una selezione (non si può effettuare query di `id` due volte sotto `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Qualsiasi variabile assegnata a un argomento deve corrispondere al suo tipo. - In un determinato elenco di variabili, ciascuna di esse deve essere unica. - Tutte le variabili definite devono essere utilizzate. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Invio di una query a un API GraphQL @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Gestione dei subgraph a cross-chain: effettuare query di più subgraph in un'unica query - [Tracciamento automatico dei blocchi](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/it/subgraphs/querying/graphql-api.mdx b/website/pages/it/subgraphs/querying/graphql-api.mdx index ba99bf940a81..f0f07d05b7ab 100644 --- a/website/pages/it/subgraphs/querying/graphql-api.mdx +++ b/website/pages/it/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/it/subgraphs/querying/introduction.mdx b/website/pages/it/subgraphs/querying/introduction.mdx index a378ce4062ae..d1ef0dae6bbd 100644 --- a/website/pages/it/subgraphs/querying/introduction.mdx +++ b/website/pages/it/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Effettuare query di The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/it/subgraphs/quick-start.mdx b/website/pages/it/subgraphs/quick-start.mdx index 429d4d51116f..13af8f0deb42 100644 --- a/website/pages/it/subgraphs/quick-start.mdx +++ b/website/pages/it/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Quick Start --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/it/substreams/sps/sps-faq.mdx b/website/pages/it/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/it/substreams/sps/sps-faq.mdx +++ b/website/pages/it/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/it/supported-networks.mdx b/website/pages/it/supported-networks.mdx index 9e47f25c86e6..2f3c40917b37 100644 --- a/website/pages/it/supported-networks.mdx +++ b/website/pages/it/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ja/about.mdx b/website/pages/ja/about.mdx index db8864a69b0f..c867800369a3 100644 --- a/website/pages/ja/about.mdx +++ b/website/pages/ja/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/ja/archived/arbitrum/arbitrum-faq.mdx b/website/pages/ja/archived/arbitrum/arbitrum-faq.mdx index 8b416bd7cfe2..3ab2bdbbf83b 100644 --- a/website/pages/ja/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/ja/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ L2でのThe Graphの活用には、このドロップダウンスイッチャー ## サブグラフ開発者、データ消費者、インデクサー、キュレーター、デリゲーターは何をする必要がありますか？ -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ All smart contracts have been thoroughly [audited](https://github.com/graphproto ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arb Arbitrum 請求残高への GRT の追加は、[Subgraph Studio](https://thegraph.com/studio/) でワンクリックで行うことができます。 GRT を Arbitrum に簡単にブリッジし、1 回のトランザクションで API キーを入力できるようになります。 -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/ja/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ja/archived/arbitrum/l2-transfer-tools-faq.mdx index 9885a24b3c6c..0f2b582f0c08 100644 --- a/website/pages/ja/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/ja/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ The Graphは、プロトコルをArbitrum Oneに展開することで、コン ### イーサリアムメインネットで使用しているのと同じウォレットを使用できますか? -[EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) ウォレットを使用している場合は、同じアドレスを使用できます。 Ethereum メインネット ウォレットがコントラクト (マルチシグなど) の場合、[Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the- graph-on-l2) 転送が送信される場所。 間違ったアドレスへの転送は永久的な損失につながる可能性があるため、アドレスを注意深く確認してください。 L2 でマルチシグを使用したい場合は、必ず Arbitrum One にマルチシグ コントラクトを展開してください。 +[EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) ウォレットを使用している場合は、同じアドレスを使用できます。 Ethereum メインネット ウォレットがコントラクト (マルチシグなど) の場合、[Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the- graph-on-l2) 転送が送信される場所。 間違ったアドレスへの転送は永久的な損失につながる可能性があるため、アドレスを注意深く確認してください。 L2 でマルチシグを使用したい場合は、必ず Arbitrum One にマルチシグ コントラクトを展開してください。 EthereumやArbitrumのようなEVMブロックチェーン上のウォレットは、ブロックチェーンとやり取りすることなく作成できる一対の鍵（公開鍵と秘密鍵）です。そのため、イーサリアム用に作成されたウォレットは、Arbitrum上でも何もすることなく動作します。 diff --git a/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx index 357b116b5639..c2cba6e093b2 100644 --- a/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ja/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 転送ツールガイド グラフにより、アービトラムワンのL2に簡単に移動できるようになりました。プロトコル参加者ごとに、すべてのネットワーク参加者が L2 への転送をシームレスに行うための L2 転送ツールのセットがあります。これらのツールでは、転送する内容に応じて、特定の一連の手順に従う必要があります。 -これらのツールに関するよくある質問は、[L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/) で回答されています。FAQには、ツールの使用方法、機能、およびツールを使用する際の注意事項に関する詳細な説明が含まれています。 +これらのツールに関するよくある質問は、[L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/) で回答されています。FAQには、ツールの使用方法、機能、およびツールを使用する際の注意事項に関する詳細な説明が含まれています。 ## サブグラフをアービトラムに転送する方法 (L2) diff --git a/website/pages/ja/archived/sunrise.mdx b/website/pages/ja/archived/sunrise.mdx index e52305674f86..0ffb746a1721 100644 --- a/website/pages/ja/archived/sunrise.mdx +++ b/website/pages/ja/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### なぜEdge & Nodeはアップグレード・インデクサーを実行しているのか？ @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ja/contracts.mdx b/website/pages/ja/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/ja/contracts.mdx +++ b/website/pages/ja/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ja/indexing/chain-integration-overview.mdx b/website/pages/ja/indexing/chain-integration-overview.mdx index a1895f77ea6f..c9349b7a24e5 100644 --- a/website/pages/ja/indexing/chain-integration-overview.mdx +++ b/website/pages/ja/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: チェーン統合プロセスの概要 ## ステージ 1. 技術的統合 -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - チームは、プロトコルの統合プロセスを開始するために、[here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)のフォーラムスレッドを作成します（Governance & GIPsの下にあるNew Data Sourcesのサブカテゴリ内）。デフォルトのフォーラムテンプレートの使用が必須です。 ## ステージ 2. 統合の検証 diff --git a/website/pages/ja/indexing/new-chain-integration.mdx b/website/pages/ja/indexing/new-chain-integration.mdx index 4c1c6fa51572..94f1424e9113 100644 --- a/website/pages/ja/indexing/new-chain-integration.mdx +++ b/website/pages/ja/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Nodeはエラーがない場合、デプロイされたサブグラフを ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ja/indexing/overview.mdx b/website/pages/ja/indexing/overview.mdx index d05965769e76..7031da608792 100644 --- a/website/pages/ja/indexing/overview.mdx +++ b/website/pages/ja/indexing/overview.mdx @@ -87,7 +87,7 @@ Use Etherscan to call `getRewards()`: ### クエリフィーカットとインデキシングリワードカットとは？ -`クエリフィーカット` と`インデキシングリワードカット` の値は、インデクサーが クールダウンブロックと共に設定できるデリゲーションパラメータで、インデクサーとそのデリゲーター間の GRT の分配を制御するためのものです。 デリゲーションパラメータの設定方法については、[Staking in the Protocol](/network/indexing/#stake-in-the-protocol)の最後のステップを参照してください。 +`クエリフィーカット` と`インデキシングリワードカット` の値は、インデクサーが クールダウンブロックと共に設定できるデリゲーションパラメータで、インデクサーとそのデリゲーター間の GRT の分配を制御するためのものです。 デリゲーションパラメータの設定方法については、[Staking in the Protocol](/indexing/overview/#stake-in-the-protocol)の最後のステップを参照してください。 - **queryFeeCut** - クエリ料金のリベートの%を示します。これが95%に設定されている場合、インデクサーは割り当てが閉じられた際に獲得するクエリ料金の95%を受け取り、残りの5%は委任者に支払われます。 @@ -121,7 +121,7 @@ Use Etherscan to call `getRewards()`: ### インデクサーが取るべきセキュリティ対策は？ -- **オペレーター ウォレット** - オペレーター ウォレットを設定することは重要な予防措置です。これにより、インデクサーは、ステークを制御するキーと日々の操作を制御するキーとの間の分離を維持できるようになります。 - デイ オペレーション。手順については、[Stake in Protocol](/network/indexing/#stake-in-the-protocol) を参照してください。 +- **オペレーター ウォレット** - オペレーター ウォレットを設定することは重要な予防措置です。これにより、インデクサーは、ステークを制御するキーと日々の操作を制御するキーとの間の分離を維持できるようになります。 - デイ オペレーション。手順については、[Stake in Protocol](/indexing/overview/#stake-in-the-protocol) を参照してください。 - **ファイアウォール** - インデクサー サービスのみを公開する必要があり、管理ポートとデータベース アクセスのロックダウンに特に注意を払う必要があります: グラフ ノード JSON-RPC エンドポイント (デフォルト ポート: 8030)、インデクサー管理 API エンドポイント (既定のポート: 18000)、および Postgres データベース エンドポイント (既定のポート: 5432) は公開しないでください。 @@ -374,7 +374,7 @@ docker-compose up #### はじめに -インデクサー エージェントとインデクサー サービスは、グラフ ノード インフラストラクチャと同じ場所に配置する必要があります。 インデクサー コンポーネントの仮想実行環境をセットアップするには、さまざまな方法があります。 ここでは、NPM パッケージまたはソースを使用するか、Google Cloud Kubernetes Engine 上の kubernetes と Docker を介してベアメタル上でそれらを実行する方法を説明します。 これらの設定例がご使用のインフラストラクチャにうまく反映されない場合は、参考となるコミュニティ ガイドがある可能性があります。[Discord](https://discord.gg/graphprotocol) にお越しください。 インデクサー コンポーネントを起動する前に、忘れずに [stake in the protocol](/network/indexing/#stake-in-the-protocol) してください。 +インデクサー エージェントとインデクサー サービスは、グラフ ノード インフラストラクチャと同じ場所に配置する必要があります。 インデクサー コンポーネントの仮想実行環境をセットアップするには、さまざまな方法があります。 ここでは、NPM パッケージまたはソースを使用するか、Google Cloud Kubernetes Engine 上の kubernetes と Docker を介してベアメタル上でそれらを実行する方法を説明します。 これらの設定例がご使用のインフラストラクチャにうまく反映されない場合は、参考となるコミュニティ ガイドがある可能性があります。[Discord](https://discord.gg/graphprotocol) にお越しください。 インデクサー コンポーネントを起動する前に、忘れずに [stake in the protocol](/indexing/overview/#stake-in-the-protocol) してください。 #### NPM パッケージから @@ -454,7 +454,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s と Terraform の使用 -[Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) の項を参照ください。 +[Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) の項を参照ください。 #### 使い方 @@ -753,7 +753,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -インデクサーがプロトコルにGRTをステークすると、[Indexerコンポーネント](/network/indexing/#indexer-components)を立ち上げ、ネットワークとのやりとりを開始することができます。 +インデクサーがプロトコルにGRTをステークすると、[Indexerコンポーネント](/indexing/overview/#indexer-components)を立ち上げ、ネットワークとのやりとりを開始することができます。 #### トークンの承認 @@ -813,6 +813,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). インデクサーは、チェーン上に配置を作成する前に、チェーンヘッドにサブグラフの配置を同期させるために、オフチェーン同期機能を利用することを推奨します。この機能は、同期に28エポック以上かかる可能性があるサブグラフや、不定期に失敗する可能性があるサブグラフに特に有効です。 diff --git a/website/pages/ja/indexing/tap.mdx b/website/pages/ja/indexing/tap.mdx index ab14dd962926..f35c37cf4a46 100644 --- a/website/pages/ja/indexing/tap.mdx +++ b/website/pages/ja/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 注： -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/ja/resources/benefits.mdx b/website/pages/ja/resources/benefits.mdx index cd9b5fd23705..f9312ab51eeb 100644 --- a/website/pages/ja/resources/benefits.mdx +++ b/website/pages/ja/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. サブグラフ上のシグナルのキュレーションは、オプションで1回限り、ネットゼロのコストで可能です（例えば、$1,000のシグナルをサブグラフ上でキュレーションし、後で引き出すことができ、その過程でリターンを得る可能性があります）。 @@ -89,4 +89,4 @@ Graphの分散型ネットワークは、`graph-node`をセルフホストする 結論: グラフ ネットワークは、ローカルで `graph-node` を実行するよりも安価で使いやすく、優れた結果を生み出します。 -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/ja/resources/roles/curating.mdx b/website/pages/ja/resources/roles/curating.mdx index ece45a6d2a62..0cc09f023730 100644 --- a/website/pages/ja/resources/roles/curating.mdx +++ b/website/pages/ja/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## シグナルの出し方 -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) キュレーターは、特定のサブグラフのバージョンでシグナルを出すことも、そのサブグラフの最新のプロダクションビルドに自動的にシグナルを移行させることも可能ですます。 どちらも有効な戦略であり、それぞれに長所と短所があります。 @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The Graph では、クエリ市場は本質的に歴史が浅く、初期の市場ダイナミクスのために、あなたの%APY が予想より低くなるリスクがあります。 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. サブグラフはバグで失敗することがあります。 失敗したサブグラフは、クエリフィーが発生しません。 結果的に、開発者がバグを修正して新しいバージョンを展開するまで待たなければならなくなります。 - サブグラフの最新バージョンに加入している場合、シェアはその新バージョンに自動移行します。 これには 0.5％のキュレーション税がかかります。 - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ja/resources/tokenomics.mdx b/website/pages/ja/resources/tokenomics.mdx index 58a6e5871ca8..6d98f8813d6e 100644 --- a/website/pages/ja/resources/tokenomics.mdx +++ b/website/pages/ja/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### 既存のサブグラフのクエリ -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/ja/subgraphs/billing.mdx b/website/pages/ja/subgraphs/billing.mdx index a8c32eefdd56..e2eba5d225e9 100644 --- a/website/pages/ja/subgraphs/billing.mdx +++ b/website/pages/ja/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. ページ右上の「Connect Wallet」をクリックします。ウォレット選択ページに遷移します。ウォレットを選択し、「Connect」をクリックします。 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. ページ右上の「Connect Wallet」をクリックします。ウォレット選択ページに遷移します。ウォレットを選択し、「Connect」をクリックします。 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### マルチシグウォレットを使ったGRTの追加 -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/ja/subgraphs/cookbook/arweave.mdx b/website/pages/ja/subgraphs/cookbook/arweave.mdx index 5df10d06992e..66a49d865363 100644 --- a/website/pages/ja/subgraphs/cookbook/arweave.mdx +++ b/website/pages/ja/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Arweaveデータソースは 2 種類のハンドラーをサポートしてい イベントを処理するハンドラは、[AssemblyScript](https://www.assemblyscript.org/) で記述されています。 -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Arweaveサブグラフのクエリ -ArweaveサブグラフのGraphQLエンドポイントは、スキーマ定義によって決定され、既存のAPIインタフェースが使用されます。詳細は[GraphQL API documentation](/querying/graphql-api/)を参照してください。 +ArweaveサブグラフのGraphQLエンドポイントは、スキーマ定義によって決定され、既存のAPIインタフェースが使用されます。詳細は[GraphQL API documentation](/subgraphs/querying/graphql-api/)を参照してください。 ## サブグラフの例 diff --git a/website/pages/ja/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/ja/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/ja/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/ja/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ja/subgraphs/cookbook/cosmos.mdx b/website/pages/ja/subgraphs/cookbook/cosmos.mdx index 4ff9a970011d..a2e2be68f0e4 100644 --- a/website/pages/ja/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/ja/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and イベントを処理するためのハンドラは[AssemblyScript](https://www.assemblyscript.org/)で書かれています。 -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Cosmosサブグラフのクエリ -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Cosmosブロックチェーンに対応 diff --git a/website/pages/ja/subgraphs/cookbook/derivedfrom.mdx b/website/pages/ja/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/ja/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/ja/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ja/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/ja/subgraphs/cookbook/grafting-hotfix.mdx index 9c474ebdd73e..ce3e717c103a 100644 --- a/website/pages/ja/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/ja/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## その他のリソース -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ja/subgraphs/cookbook/grafting.mdx b/website/pages/ja/subgraphs/cookbook/grafting.mdx index 41fc94d7fe80..b1c02b9495f5 100644 --- a/website/pages/ja/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ja/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Grafting is a powerful feature that allows you to "graft" one subgraph onto anot ## 既存のサブグラフの構築 -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [サブグラフ例文レポ](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> 注：この記事の多くの資料は、以前公開された[アルウィーブの記事](/cookbook/arweave/)から引用したものです。 +> 注：この記事の多くの資料は、以前公開された[アルウィーブの記事](/subgraphs/cookbook/arweave/)から引用したものです。 diff --git a/website/pages/ja/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ja/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/ja/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/ja/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ja/subgraphs/cookbook/near.mdx b/website/pages/ja/subgraphs/cookbook/near.mdx index aae00c41c789..f20f17ac7ba4 100644 --- a/website/pages/ja/subgraphs/cookbook/near.mdx +++ b/website/pages/ja/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ NEAR サブグラフの開発には、バージョン`0.23.0`以上の`graph-cli **schema.graphql:**: サブグラフのためにどのようなデータが保存されているか、そして GraphQL を介してどのようにクエリを行うかを定義するスキーマファイル。NEAR サブグラフの要件は、[既存のドキュメント](/developing/creating-a-subgraph/#the-graphql-schema)でカバーされています。 -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. サブグラフの開発には 2 つの重要なコマンドがあります: @@ -98,7 +98,7 @@ NEAR データソースは 2 種類のハンドラーをサポートしていま イベントを処理するためのハンドラは[AssemblyScript](https://www.assemblyscript.org/)で書かれています。 -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - ブロックハンドラーは、`Block`を受け取ります - レシートハンドラーは`ReceiptWithOutcome`を受け取ります -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## NEAR サブグラフの展開 @@ -228,7 +228,7 @@ NEAR のインデックスを作成するグラフノードの運用には、以 ## NEAR サブグラフへのクエリ -NEAR サブグラフの GraphQL エンドポイントは、既存の API インターフェイスを用いて、スキーマ定義によって決定されます。詳細は、[GraphQL API documentation](/querying/graphql-api/) をご覧ください。 +NEAR サブグラフの GraphQL エンドポイントは、既存の API インターフェイスを用いて、スキーマ定義によって決定されます。詳細は、[GraphQL API documentation](/subgraphs/querying/graphql-api/) をご覧ください。 ## サブグラフの例 @@ -276,7 +276,7 @@ accounts: ### 私の質問に対する回答がありません。NEAR サブグラフの作成に関するヘルプはどこで入手できますか? -もし、サブグラフ開発に関する一般的な質問であれば、[開発者ドキュメント](/quick-start/)に多くの情報があります。それ以外の場合は、[The Graph Protocol Discord](https://discord.gg/graphprotocol)に参加し、#nearチャンネルで質問するか、near@thegraph.comまでお寄せください。 +もし、サブグラフ開発に関する一般的な質問であれば、[開発者ドキュメント](/subgraphs/quick-start/)に多くの情報があります。それ以外の場合は、[The Graph Protocol Discord](https://discord.gg/graphprotocol)に参加し、#nearチャンネルで質問するか、near@thegraph.comまでお寄せください。 ## 参考文献 diff --git a/website/pages/ja/subgraphs/cookbook/pruning.mdx b/website/pages/ja/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/ja/subgraphs/cookbook/pruning.mdx +++ b/website/pages/ja/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 801faa5a0f20..df3533be5aaf 100644 --- a/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ja/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/)は、StreamingFastがThe Graph Networkのために開発した、ブロックチェーンのデータを処理するための新しいフレームワークである。サブストリームモジュールは、サブグラフエンティティと互換性のあるエンティティの変更を出力することができます。サブグラフはこのようなサブストリームモジュールをデータソースとして使用することができ、サブストリームのインデックス作成速度と追加データをサブグラフ開発者にもたらします。 +[Substreams](/substreams/introduction/)は、StreamingFastがThe Graph Networkのために開発した、ブロックチェーンのデータを処理するための新しいフレームワークである。サブストリームモジュールは、サブグラフエンティティと互換性のあるエンティティの変更を出力することができます。サブグラフはこのようなサブストリームモジュールをデータソースとして使用することができ、サブストリームのインデックス作成速度と追加データをサブグラフ開発者にもたらします。 ## 要件 @@ -22,7 +22,7 @@ npm install -g @graphprotocol/graph-cli ## サブストリームパッケージの定義 -Substreamsパッケージは、型（[プロトコルバッファ](https://protobuf.dev/)として定義される）、モジュール（Rustで記述される）、および型を参照し、モジュールがどのようにトリガーされるかを指定する`substreams.yaml`ファイルで構成されます。[サブストリームの開発についての詳細はサブストリームのドキュメントを参照](/substreams/)してください。また、[awesome-substreams](https://github.com/pinax-network/awesome-substreams)や[Substreams cookbook](https://github.com/pinax-network/substreams-cookbook)を参照してください。 +Substreamsパッケージは、型（[プロトコルバッファ](https://protobuf.dev/)として定義される）、モジュール（Rustで記述される）、および型を参照し、モジュールがどのようにトリガーされるかを指定する`substreams.yaml`ファイルで構成されます。[サブストリームの開発についての詳細はサブストリームのドキュメントを参照](/substreams/introduction/)してください。また、[awesome-substreams](https://github.com/pinax-network/awesome-substreams)や[Substreams cookbook](https://github.com/pinax-network/substreams-cookbook)を参照してください。 問題の Substreams パッケージは、メインネット イーサリアム上のコントラクトのデプロイメントを検出し、新しくデプロイされたすべてのコントラクトの作成ブロックとタイムスタンプを追跡します。これを行うには、`/proto/example.proto` に専用の `Contract` タイプがあります ([プロトコル バッファーの定義の詳細](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ja/subgraphs/cookbook/timeseries.mdx b/website/pages/ja/subgraphs/cookbook/timeseries.mdx index 035975b433d3..6ebf5e48a235 100644 --- a/website/pages/ja/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/ja/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ja/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/ja/subgraphs/cookbook/transfer-to-the-graph.mdx index 3b064acb6cd5..8ba1b5914dd9 100644 --- a/website/pages/ja/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/ja/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### 例 @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### その他のリソース -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/ja/subgraphs/developing/creating/advanced.mdx b/website/pages/ja/subgraphs/developing/creating/advanced.mdx index 6b8fd1fb7db4..cd0d39a6d81e 100644 --- a/website/pages/ja/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/ja/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { 親エンティティと結果のファイルデータソースエンティティの間の関係が1：1である場合、最も単純なパターンは、IPFS CIDをルックアップとして使用して、親エンティティを結果のファイルエンティティにリンクすることです。新しいファイルベースのエンティティのモデリングに問題がある場合は、Discordに連絡してください。 -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### ファイルを処理するハンドラーを新規に作成 -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0. NFT メタデータを対応するトークンにリンクする場合、メタデータの IPFS ハッシュを使用して、トークン エンティティから Metadata エンティティを参照します。IPFSハッシュをIDとして使用してMetadataエンティティを保存します。 -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### 既存のサブグラフへのグラフト -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx index 1bca5f7e5879..2a66b2ead6d6 100644 --- a/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ja/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ Since language mappings are written in AssemblyScript, it is useful to review th | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Ethereum タイプに `TransactionReceipt` と `Log` クラスを追加
Ethereum Event オブジェクトに `receipt` フィールドを追加。 | | 0.0.6 | Ethereum Transactionオブジェクトに`nonce`フィールドを追加
Ethereum Blockオブジェクトに`baseFeePerGas`を追加。 | -| 0.0.5 | AssemblyScriptはバージョン0.19.10にアップグレードされました（このバージョンアップには変更点が含まれていますので Migration Guide) をご覧ください）。
ethereum.transaction.gasUsedの名前がethereum.transaction.gasLimitに変更 | +| 0.0.5 | AssemblyScriptはバージョン0.19.10にアップグレードされました（このバージョンアップには変更点が含まれていますので Migration Guide) をご覧ください）。
ethereum.transaction.gasUsedの名前がethereum.transaction.gasLimitに変更 | | 0.0.4 | Ethereum SmartContractCall オブジェクトにfunctionSignatureフィールドを追加 | | 0.0.3 | イーサリアムコールオブジェクトに`from`フィールドを追加
`etherem.call.address`を`ethereum.call.to`に変更。 | | 0.0.2 | Ethereum Transaction オブジェクトに inputフィールドを追加 | diff --git a/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx index 80ecfac7d53c..593ec6d24b2d 100644 --- a/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ja/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Graph CLI のインストール --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## 概要 -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## はじめに @@ -114,6 +114,6 @@ ABI ファイルは、契約内容と一致している必要があります。A | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx index 2a7137aa4f70..eaa78acfc174 100644 --- a/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ja/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ja/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/ja/subgraphs/developing/creating/starting-your-subgraph.mdx index 15e1d6048cbf..49828585e1e2 100644 --- a/website/pages/ja/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/ja/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/ja/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/ja/subgraphs/developing/creating/subgraph-manifest.mdx index 76206b5791cb..31095cac4850 100644 --- a/website/pages/ja/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/ja/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). マニフェストを更新する重要な項目は以下の通りです: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/ja/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/ja/subgraphs/developing/creating/unit-testing-framework.mdx index 8e20b4fe8312..25c03b18a75f 100644 --- a/website/pages/ja/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/ja/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,7 @@ Global test coverage: 22.2% (2/9 handlers). > Critical: 有効なモジュールから WasmInstance を作成できない。コンテキストが不明 インポート: wasi_snapshot_preview1::fd_write が定義されていない -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) +This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: 期待された引数は? > diff --git a/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx index dfcd1aaf915d..43c7df57e7b0 100644 --- a/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ja/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### Subgraph と The Graph Network の互換性 In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - 以下の機能のいずれも使用してはいけません: - ipfs.cat & ipfs.map - 致命的でないエラー @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## サブグラフのバージョンの自動アーカイブ diff --git a/website/pages/ja/subgraphs/developing/developer-faq.mdx b/website/pages/ja/subgraphs/developing/developer-faq.mdx index 64ab9417669d..d241a0b43748 100644 --- a/website/pages/ja/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ja/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You can deploy a new version of your subgraph to Subgraph Studio using the CLI. ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ docker pull graphprotocol/graph-node:latest ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -対応ネットワークの一覧は[こちら](/developing/supported-networks/)で確認できます。 +対応ネットワークの一覧は[こちら](/supported-networks/)で確認できます。 ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/ja/subgraphs/developing/introduction.mdx b/website/pages/ja/subgraphs/developing/introduction.mdx index 669f37f571f2..e31b269d03e6 100644 --- a/website/pages/ja/subgraphs/developing/introduction.mdx +++ b/website/pages/ja/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: 現像 --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## 概要 @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx index d9b3b54caf9b..ccdbdca54166 100644 --- a/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ja/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### パブリッシュされたサブグラフのメタデータの更新 @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/ja/subgraphs/developing/subgraphs.mdx b/website/pages/ja/subgraphs/developing/subgraphs.mdx index 4801361f96eb..1a838a21c563 100644 --- a/website/pages/ja/subgraphs/developing/subgraphs.mdx +++ b/website/pages/ja/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/ja/subgraphs/explorer.mdx b/website/pages/ja/subgraphs/explorer.mdx index 401b0b84a0db..1adfea2d85b4 100644 --- a/website/pages/ja/subgraphs/explorer.mdx +++ b/website/pages/ja/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -インデクサーになるには、[公式ドキュメント](/network/indexing/)や[The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)を見てみてください。 +インデクサーになるには、[公式ドキュメント](/indexing/overview/)や[The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)を見てみてください。 ![インデックス作成の詳細](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![エクスプローラーイメージ ６](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. デリゲーター @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - 現在プロトコルに保持している GRT 総量 - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## ネットワーク diff --git a/website/pages/ja/subgraphs/querying/best-practices.mdx b/website/pages/ja/subgraphs/querying/best-practices.mdx index 94f2d119d023..672d7aae691f 100644 --- a/website/pages/ja/subgraphs/querying/best-practices.mdx +++ b/website/pages/ja/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - 各`queryName`は、1回の操作で1回だけ使用しなければなりません。 - 各`フィールド`は、選択の中で一度だけ使用しなければなりません(`トークン`の下に`id`を二度照会することはできません)。 -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - 引数に代入される変数は、その型と一致しなければなりません。 - 与えられた変数のリストにおいて、各変数は一意でなければなりません。 - 定義された変数はすべて使用する必要があります。 > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### GraphQL APIへのクエリの送信 @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - クロスチェーンのサブグラフ処理：1回のクエリで複数のサブグラフからクエリを実行可能 - [自動ブロック追跡](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/ja/subgraphs/querying/graphql-api.mdx b/website/pages/ja/subgraphs/querying/graphql-api.mdx index 403e7f70169d..d66def10b5fe 100644 --- a/website/pages/ja/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ja/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/ja/subgraphs/querying/introduction.mdx b/website/pages/ja/subgraphs/querying/introduction.mdx index f221a3f9c80a..1a6649e41a03 100644 --- a/website/pages/ja/subgraphs/querying/introduction.mdx +++ b/website/pages/ja/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: The Graphのクエリ When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/ja/subgraphs/quick-start.mdx b/website/pages/ja/subgraphs/quick-start.mdx index 618252856359..88602845e7ae 100644 --- a/website/pages/ja/subgraphs/quick-start.mdx +++ b/website/pages/ja/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: クイックスタート --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## 前提条件 - クリプトウォレット -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/ja/substreams/sps/sps-faq.mdx b/website/pages/ja/substreams/sps/sps-faq.mdx index b1f97753e12f..642233729257 100644 --- a/website/pages/ja/substreams/sps/sps-faq.mdx +++ b/website/pages/ja/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: サブストリームを利用したサブグラフに関するよくあ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -サブストリームの詳細については、[サブストリームのドキュメント](/substreams/) にアクセスしてください。 +サブストリームの詳細については、[サブストリームのドキュメント](/substreams/introduction/) にアクセスしてください。 ## サブストリームによって動作するサブグラフは何ですか？ -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) は、サブストリームの機能とサブグラフのクエリ可能性を組み合わせています。 サブストリームを利用したサブグラフを公開する場合、サブストリーム変換によって生成されたデータは、[エンティティの変更を出力](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change)できます。 /src/tables.rs)、サブグラフ エンティティと互換性があります。 +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) は、サブストリームの機能とサブグラフのクエリ可能性を組み合わせています。 サブストリームを利用したサブグラフを公開する場合、サブストリーム変換によって生成されたデータは、[エンティティの変更を出力](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change)できます。 /src/tables.rs)、サブグラフ エンティティと互換性があります。 すでにサブグラフ開発に​​精通している場合は、AssemblyScript 変換層によって生成されたかのように、サブストリームを利用したサブグラフをクエリできることに注意してください。動的で柔軟な GraphQL API の提供など、サブグラフのすべての利点が得られます。 @@ -62,9 +62,9 @@ Firehose を使用すると、次のような多くの利点があります。 ## 開発者は、サブストリームを利用したサブグラフとサブストリームに関する詳細情報にどこでアクセスできますか? -[Substreams ドキュメント](/substreams/) では、Substreams モジュールを構築する方法を説明します。 +[Substreams ドキュメント](/substreams/introduction/) では、Substreams モジュールを構築する方法を説明します。 -[Substreams-powered subgraphs ドキュメント](/cookbook/substreams-powered-subgraphs/) では、The Graph にデプロイするためにサブグラフをパッケージ化する方法が示されています。 +[Substreams-powered subgraphs ドキュメント](/subgraphs/cookbook/substreams-powered-subgraphs/) では、The Graph にデプロイするためにサブグラフをパッケージ化する方法が示されています。 The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ See [modules documentation](https://substreams.streamingfast.io/documentation/de ## サブストリームを利用したサブグラフを構築してデプロイするにはどうすればよいでしょうか? -Substreams を利用したサブグラフを [defining](/cookbook/substreams-powered-subgraphs/) した後、Graph CLI を使用してそれを [Subgraph Studio](https://thegraph.com/studio/) にデプロイできます。 +Substreams を利用したサブグラフを [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) した後、Graph CLI を使用してそれを [Subgraph Studio](https://thegraph.com/studio/) にデプロイできます。 ## サブストリームおよびサブストリームを利用したサブグラフの例はどこで見つけることができますか? diff --git a/website/pages/ja/supported-networks.mdx b/website/pages/ja/supported-networks.mdx index 44e3b18745cb..db8c8fc4ad05 100644 --- a/website/pages/ja/supported-networks.mdx +++ b/website/pages/ja/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ko/about.mdx b/website/pages/ko/about.mdx index 9c21bf00d08f..02b29895881f 100644 --- a/website/pages/ko/about.mdx +++ b/website/pages/ko/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/ko/archived/arbitrum/arbitrum-faq.mdx b/website/pages/ko/archived/arbitrum/arbitrum-faq.mdx index 9c12c8816259..562824e64e95 100644 --- a/website/pages/ko/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/ko/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx index de12152a1f00..6254b92ed9c3 100644 --- a/website/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/ko/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### 이더리움 메인넷에서 사용하는 지갑을 그대로 사용할 수 있나요? -당신이 사용하는 경우 [EOA] (https://ethereum.org/ko/개발자/문서/계정/#계정-유형) 만약 당신의 이더리움 메인넷 지갑이 단순한 지갑이라면, 당신은 동일한 주소를 사용할 수 있습니다. 만약 당신의 이더리움 메인넷 지갑이 계약(예: 다중 서명 지갑)인 경우, 당신은 당신의 이체가 전송될 Arbitrum 지갑 주소: /arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2를 지정해야 합니다. 잘못된 주소로의 이체는 영구적인 손실을 초래할 수 있으므로 주소를 주의깊게 확인하십시오. 만약 당신이 L2에서 다중 서명 지갑을 사용하고 싶다면, 반드시 Arbitrum One에 다중 서명 계약을 배포하십시오. +당신이 사용하는 경우 [EOA] (https://ethereum.org/ko/개발자/문서/계정/#계정-유형) 만약 당신의 이더리움 메인넷 지갑이 단순한 지갑이라면, 당신은 동일한 주소를 사용할 수 있습니다. 만약 당신의 이더리움 메인넷 지갑이 계약(예: 다중 서명 지갑)인 경우, 당신은 당신의 이체가 전송될 Arbitrum 지갑 주소: /archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2를 지정해야 합니다. 잘못된 주소로의 이체는 영구적인 손실을 초래할 수 있으므로 주소를 주의깊게 확인하십시오. 만약 당신이 L2에서 다중 서명 지갑을 사용하고 싶다면, 반드시 Arbitrum One에 다중 서명 계약을 배포하십시오. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx index e516573fd4d9..485f34a70c97 100644 --- a/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ko/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/ko/archived/sunrise.mdx b/website/pages/ko/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/ko/archived/sunrise.mdx +++ b/website/pages/ko/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ko/contracts.mdx b/website/pages/ko/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/ko/contracts.mdx +++ b/website/pages/ko/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ko/indexing/chain-integration-overview.mdx b/website/pages/ko/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/ko/indexing/chain-integration-overview.mdx +++ b/website/pages/ko/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/ko/indexing/new-chain-integration.mdx b/website/pages/ko/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/ko/indexing/new-chain-integration.mdx +++ b/website/pages/ko/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ko/indexing/overview.mdx b/website/pages/ko/indexing/overview.mdx index c05c37a275ef..34a60d456cfc 100644 --- a/website/pages/ko/indexing/overview.mdx +++ b/website/pages/ko/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/ko/indexing/tap.mdx b/website/pages/ko/indexing/tap.mdx index 3e8185186982..4132216ca5b6 100644 --- a/website/pages/ko/indexing/tap.mdx +++ b/website/pages/ko/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/ko/resources/benefits.mdx b/website/pages/ko/resources/benefits.mdx index d95723327119..c4539171103b 100644 --- a/website/pages/ko/resources/benefits.mdx +++ b/website/pages/ko/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/ko/resources/roles/curating.mdx b/website/pages/ko/resources/roles/curating.mdx index a3b96ed010fe..6ddf8e91099c 100644 --- a/website/pages/ko/resources/roles/curating.mdx +++ b/website/pages/ko/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ko/resources/tokenomics.mdx b/website/pages/ko/resources/tokenomics.mdx index e2e4c904000d..73a1adda922b 100644 --- a/website/pages/ko/resources/tokenomics.mdx +++ b/website/pages/ko/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/ko/subgraphs/billing.mdx b/website/pages/ko/subgraphs/billing.mdx index dec5cfdadc12..f3f52bbf35ee 100644 --- a/website/pages/ko/subgraphs/billing.mdx +++ b/website/pages/ko/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/ko/subgraphs/cookbook/arweave.mdx b/website/pages/ko/subgraphs/cookbook/arweave.mdx index 4c35f4ee8e2e..2098d5ab5932 100644 --- a/website/pages/ko/subgraphs/cookbook/arweave.mdx +++ b/website/pages/ko/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/ko/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/ko/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/ko/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/ko/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ko/subgraphs/cookbook/cosmos.mdx b/website/pages/ko/subgraphs/cookbook/cosmos.mdx index cd23a3742f86..dddfbff521d0 100644 --- a/website/pages/ko/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/ko/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/ko/subgraphs/cookbook/derivedfrom.mdx b/website/pages/ko/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/ko/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/ko/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ko/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/ko/subgraphs/cookbook/grafting-hotfix.mdx index 040e3a8209d5..a0bd3f4ab1c2 100644 --- a/website/pages/ko/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/ko/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ko/subgraphs/cookbook/grafting.mdx b/website/pages/ko/subgraphs/cookbook/grafting.mdx index 7aa79c7e2755..57d5169830a7 100644 --- a/website/pages/ko/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ko/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/ko/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ko/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/ko/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/ko/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ko/subgraphs/cookbook/near.mdx b/website/pages/ko/subgraphs/cookbook/near.mdx index cc0bf8637bee..23a936406e7b 100644 --- a/website/pages/ko/subgraphs/cookbook/near.mdx +++ b/website/pages/ko/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/ko/subgraphs/cookbook/pruning.mdx b/website/pages/ko/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/ko/subgraphs/cookbook/pruning.mdx +++ b/website/pages/ko/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ko/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ko/subgraphs/cookbook/timeseries.mdx b/website/pages/ko/subgraphs/cookbook/timeseries.mdx index 2ce0ce266ccf..0168be53d7ed 100644 --- a/website/pages/ko/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/ko/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ko/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/ko/subgraphs/cookbook/transfer-to-the-graph.mdx index 6a5d2c2793f3..64c225442860 100644 --- a/website/pages/ko/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/ko/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/ko/subgraphs/developing/creating/advanced.mdx b/website/pages/ko/subgraphs/developing/creating/advanced.mdx index 3a08ddab7066..bc3a9a86efb6 100644 --- a/website/pages/ko/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/ko/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx index 8aa0bf0027bf..4c5ce57993f2 100644 --- a/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ko/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx index 282c68973a8a..a58e6be82324 100644 --- a/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ko/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ko/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ko/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/ko/subgraphs/developing/creating/starting-your-subgraph.mdx index 5127f01632aa..f463ca3e9507 100644 --- a/website/pages/ko/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/ko/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/ko/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/ko/subgraphs/developing/creating/subgraph-manifest.mdx index f282f3946e75..b4c0e467c780 100644 --- a/website/pages/ko/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/ko/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/ko/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/ko/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/ko/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/ko/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx index 6edd730f2d8b..e8483b7fea85 100644 --- a/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ko/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/ko/subgraphs/developing/developer-faq.mdx b/website/pages/ko/subgraphs/developing/developer-faq.mdx index 85dccad933b0..8a457a3db5c3 100644 --- a/website/pages/ko/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ko/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/ko/subgraphs/developing/introduction.mdx b/website/pages/ko/subgraphs/developing/introduction.mdx index 6ba33f6d916c..45cefaff16ef 100644 --- a/website/pages/ko/subgraphs/developing/introduction.mdx +++ b/website/pages/ko/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 4728db3eb245..e75e3b13d89e 100644 --- a/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ko/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/ko/subgraphs/developing/subgraphs.mdx b/website/pages/ko/subgraphs/developing/subgraphs.mdx index 42c1e806f822..e30b77cec1ae 100644 --- a/website/pages/ko/subgraphs/developing/subgraphs.mdx +++ b/website/pages/ko/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/ko/subgraphs/explorer.mdx b/website/pages/ko/subgraphs/explorer.mdx index d874f80f5140..433821560d85 100644 --- a/website/pages/ko/subgraphs/explorer.mdx +++ b/website/pages/ko/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/ko/subgraphs/querying/best-practices.mdx b/website/pages/ko/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/ko/subgraphs/querying/best-practices.mdx +++ b/website/pages/ko/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/ko/subgraphs/querying/graphql-api.mdx b/website/pages/ko/subgraphs/querying/graphql-api.mdx index 917fad3f2406..8813e2eeb3f3 100644 --- a/website/pages/ko/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ko/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/ko/subgraphs/querying/introduction.mdx b/website/pages/ko/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/ko/subgraphs/querying/introduction.mdx +++ b/website/pages/ko/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/ko/subgraphs/quick-start.mdx b/website/pages/ko/subgraphs/quick-start.mdx index 429d4d51116f..13af8f0deb42 100644 --- a/website/pages/ko/subgraphs/quick-start.mdx +++ b/website/pages/ko/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Quick Start --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/ko/substreams/sps/sps-faq.mdx b/website/pages/ko/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/ko/substreams/sps/sps-faq.mdx +++ b/website/pages/ko/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/ko/supported-networks.mdx b/website/pages/ko/supported-networks.mdx index 9e47f25c86e6..2f3c40917b37 100644 --- a/website/pages/ko/supported-networks.mdx +++ b/website/pages/ko/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/mr/about.mdx b/website/pages/mr/about.mdx index d560ebcd179d..6ec630cd8e4e 100644 --- a/website/pages/mr/about.mdx +++ b/website/pages/mr/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/mr/archived/arbitrum/arbitrum-faq.mdx b/website/pages/mr/archived/arbitrum/arbitrum-faq.mdx index 6a6ac6739ee8..689ac37ab7e1 100644 --- a/website/pages/mr/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/mr/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle ## सबग्राफ डेव्हलपर, डेटा कंझ्युमर, इंडेक्सर, क्युरेटर किंवा डेलिगेटर म्हणून, मला आता काय करावे लागेल? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/mr/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/mr/archived/arbitrum/l2-transfer-tools-faq.mdx index 96c2136b1915..b244cebad929 100644 --- a/website/pages/mr/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/mr/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### मी इथरियम मेननेटवर वापरतो तेच वॉलेट मी वापरू शकतो का? -आपल्याला [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) वॉलेट वापरत असल्यास, आपल्याला त्या एका आधीच्या पत्त्याचा वापर करू शकता. आपल्य्या इथे Ethereum मुख्यनेट वॉलेट कंट्रॅक्ट असल्यास (उदा. मल्टीसिग), तर आपल्याला आपल्या स्थानांतरणाच्या लक्ष्यासाठी [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) सूचित करावा लागेल. कृपया पत्त्याची वाचन सावध घ्या कारण कोणत्याही चुकीच्या पत्त्याला स्थायी नुकसान होऊ शकतो. आपल्याला L2 वर मल्टीसिग वापरायचं असल्यास, कृपया सुनिश्चित करा की आपल्याला Arbitrum One वर मल्टीसिग कॉन्ट्रॅक्ट डिप्लॉय करण्याची आवश्यकता आहे. +आपल्याला [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) वॉलेट वापरत असल्यास, आपल्याला त्या एका आधीच्या पत्त्याचा वापर करू शकता. आपल्य्या इथे Ethereum मुख्यनेट वॉलेट कंट्रॅक्ट असल्यास (उदा. मल्टीसिग), तर आपल्याला आपल्या स्थानांतरणाच्या लक्ष्यासाठी [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) सूचित करावा लागेल. कृपया पत्त्याची वाचन सावध घ्या कारण कोणत्याही चुकीच्या पत्त्याला स्थायी नुकसान होऊ शकतो. आपल्याला L2 वर मल्टीसिग वापरायचं असल्यास, कृपया सुनिश्चित करा की आपल्याला Arbitrum One वर मल्टीसिग कॉन्ट्रॅक्ट डिप्लॉय करण्याची आवश्यकता आहे. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx index d726ba35abb7..519d15f34cb4 100644 --- a/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/mr/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide ग्राफने Arbitrum One वर L2 वर जाणे सोपे केले आहे. प्रत्येक प्रोटोकॉल सहभागीसाठी, सर्व नेटवर्क सहभागींसाठी L2 मध्ये हस्तांतरण अखंडपणे करण्यासाठी L2 हस्तांतरण साधनांचा संच आहे. तुम्ही काय हस्तांतरित करत आहात त्यानुसार या साधनांसाठी तुम्हाला चरणांच्या विशिष्ट संचाचे अनुसरण करणे आवश्यक आहे. -या साधनांबद्दलच्या काही वारंवार प्रश्नांची उत्तरे [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/) मध्ये दिली आहेत. FAQ मध्ये साधने कशी वापरायची, ते कसे कार्य करतात आणि ते वापरताना लक्षात ठेवण्यासारख्या गोष्टींचे सखोल स्पष्टीकरण असते. +या साधनांबद्दलच्या काही वारंवार प्रश्नांची उत्तरे [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/) मध्ये दिली आहेत. FAQ मध्ये साधने कशी वापरायची, ते कसे कार्य करतात आणि ते वापरताना लक्षात ठेवण्यासारख्या गोष्टींचे सखोल स्पष्टीकरण असते. ## तुमचा सबग्राफ आर्बिट्रम (L2) वर कसा हस्तांतरित करायचा diff --git a/website/pages/mr/archived/sunrise.mdx b/website/pages/mr/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/mr/archived/sunrise.mdx +++ b/website/pages/mr/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/mr/contracts.mdx b/website/pages/mr/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/mr/contracts.mdx +++ b/website/pages/mr/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/mr/indexing/chain-integration-overview.mdx b/website/pages/mr/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/mr/indexing/chain-integration-overview.mdx +++ b/website/pages/mr/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/mr/indexing/new-chain-integration.mdx b/website/pages/mr/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/mr/indexing/new-chain-integration.mdx +++ b/website/pages/mr/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/mr/indexing/overview.mdx b/website/pages/mr/indexing/overview.mdx index 8965c47f63cb..13b6810e32cc 100644 --- a/website/pages/mr/indexing/overview.mdx +++ b/website/pages/mr/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -`queryFeeCut` आणि `indexingRewardCut` मूल्ये ही डेलिगेशन पॅरामीटर्स आहेत जी इंडेक्सर आणि त्यांच्या प्रतिनिधींमधील GRT चे वितरण नियंत्रित करण्यासाठी CooldownBlocks सोबत सेट करू शकतात. डेलिगेशन पॅरामीटर्स सेट करण्याच्या सूचनांसाठी [प्रोटोकॉलमध्ये स्टॅकिंग](/network/indexing/#stake-in-the-protocol) मधील शेवटच्या पायऱ्या पहा. +`queryFeeCut` आणि `indexingRewardCut` मूल्ये ही डेलिगेशन पॅरामीटर्स आहेत जी इंडेक्सर आणि त्यांच्या प्रतिनिधींमधील GRT चे वितरण नियंत्रित करण्यासाठी CooldownBlocks सोबत सेट करू शकतात. डेलिगेशन पॅरामीटर्स सेट करण्याच्या सूचनांसाठी [प्रोटोकॉलमध्ये स्टॅकिंग](/indexing/overview/#stake-in-the-protocol) मधील शेवटच्या पायऱ्या पहा. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What are some basic security precautions an Indexer should take? -- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करणे ही एक महत्त्वाची खबरदारी आहे कारण ते इंडेक्सरला त्यांच्या स्टेक नियंत्रित करणार्‍या की आणि दैनंदिन कामकाजावर नियंत्रण ठेवणार्‍या की यांच्यात वेगळेपणा राखण्यास अनुमती देते. सूचनांसाठी [प्रोटोकॉलमध्ये भागीदारी](/network/indexing/#stake-in-the-protocol) पहा. +- **ऑपरेटर वॉलेट** - ऑपरेटर वॉलेट सेट करणे ही एक महत्त्वाची खबरदारी आहे कारण ते इंडेक्सरला त्यांच्या स्टेक नियंत्रित करणार्‍या की आणि दैनंदिन कामकाजावर नियंत्रण ठेवणार्‍या की यांच्यात वेगळेपणा राखण्यास अनुमती देते. सूचनांसाठी [प्रोटोकॉलमध्ये भागीदारी](/indexing/overview/#stake-in-the-protocol) पहा. - **फायरवॉल** - फक्त इंडेक्सर सेवा सार्वजनिकपणे उघड करणे आवश्यक आहे आणि प्रशासक पोर्ट आणि डेटाबेस प्रवेश लॉक करण्यासाठी विशेष लक्ष दिले पाहिजे: ग्राफ नोड JSON-RPC एंडपॉइंट (डीफॉल्ट पोर्ट: 8030), इंडेक्सर मॅनेजमेंट API एंडपॉइंट (डीफॉल्ट पोर्ट: 18000), आणि पोस्टग्रेस डेटाबेस एंडपॉइंट (डीफॉल्ट पोर्ट: 5432) उघड करू नये. @@ -375,7 +375,7 @@ docker-compose up #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### वापर @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -एकदा इंडेक्सरने प्रोटोकॉलमध्ये GRT स्टेक केल्यानंतर, [इंडेक्सर घटक](/network/indexing/#indexer-components) सुरू केले जाऊ शकतात आणि त्यांचे नेटवर्कशी परस्परसंवाद सुरू करू शकतात. +एकदा इंडेक्सरने प्रोटोकॉलमध्ये GRT स्टेक केल्यानंतर, [इंडेक्सर घटक](/indexing/overview/#indexer-components) सुरू केले जाऊ शकतात आणि त्यांचे नेटवर्कशी परस्परसंवाद सुरू करू शकतात. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). ऑन-चेन वाटप तयार करण्यापूर्वी चेनहेडमध्ये सबग्राफ उपयोजन समक्रमित करण्यासाठी ऑफचेन सिंकिंग कार्यक्षमता वापरण्याची शिफारस इंडेक्सर्सना केली जाते. हे वैशिष्ट्य विशेषतः उपग्राफसाठी उपयुक्त आहे ज्यांना समक्रमित करण्यासाठी 28 पेक्षा जास्त काळ लागू शकतो किंवा अनिश्चितपणे अयशस्वी होण्याची काही शक्यता असते. diff --git a/website/pages/mr/indexing/tap.mdx b/website/pages/mr/indexing/tap.mdx index 47cb3cbcee00..e1c1886f69a6 100644 --- a/website/pages/mr/indexing/tap.mdx +++ b/website/pages/mr/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 नोट्स: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/mr/resources/benefits.mdx b/website/pages/mr/resources/benefits.mdx index 1ddfb18db87b..33f0a7999983 100644 --- a/website/pages/mr/resources/benefits.mdx +++ b/website/pages/mr/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. सबग्राफवर क्युरेटिंग सिग्नल हा पर्यायी एक-वेळचा, निव्वळ-शून्य खर्च आहे (उदा., $1k सिग्नल सबग्राफवर क्युरेट केला जाऊ शकतो आणि नंतर मागे घेतला जाऊ शकतो—प्रक्रियेत परतावा मिळविण्याच्या संभाव्यतेसह). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy तळ ओळ: ग्राफ नेटवर्क कमी खर्चिक आहे, वापरण्यास सोपे आहे आणि स्थानिक पातळीवर `ग्राफ-नोड` चालवण्याच्या तुलनेत उत्कृष्ट परिणाम देते. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/mr/resources/roles/curating.mdx b/website/pages/mr/resources/roles/curating.mdx index 6d9ac344f246..91b16b2baf4d 100644 --- a/website/pages/mr/resources/roles/curating.mdx +++ b/website/pages/mr/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## सिग्नल कसे करावे -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) क्युरेटर विशिष्ट सबग्राफ आवृत्तीवर सिग्नल करणे निवडू शकतो किंवा ते त्यांचे सिग्नल त्या सबग्राफच्या नवीनतम उत्पादन बिल्डमध्ये स्वयंचलितपणे स्थलांतरित करणे निवडू शकतात. दोन्ही वैध धोरणे आहेत आणि त्यांच्या स्वतःच्या साधक आणि बाधकांसह येतात. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. द ग्राफमध्ये क्वेरी मार्केट मूळतः तरुण आहे आणि नवीन मार्केट डायनॅमिक्समुळे तुमचा %APY तुमच्या अपेक्षेपेक्षा कमी असण्याचा धोका आहे. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. बगमुळे सबग्राफ अयशस्वी होऊ शकतो. अयशस्वी सबग्राफ क्वेरी शुल्क जमा करत नाही. परिणामी, विकसक बगचे निराकरण करेपर्यंत आणि नवीन आवृत्ती तैनात करेपर्यंत तुम्हाला प्रतीक्षा करावी लागेल. - तुम्ही सबग्राफच्या नवीनतम आवृत्तीचे सदस्यत्व घेतले असल्यास, तुमचे शेअर्स त्या नवीन आवृत्तीमध्ये स्वयंचलितपणे स्थलांतरित होतील. यावर 0.5% क्युरेशन कर लागेल. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/mr/resources/tokenomics.mdx b/website/pages/mr/resources/tokenomics.mdx index d31fa89a55a7..4c3add397870 100644 --- a/website/pages/mr/resources/tokenomics.mdx +++ b/website/pages/mr/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### विद्यमान सबग्राफची चौकशी करत आहे -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/mr/subgraphs/billing.mdx b/website/pages/mr/subgraphs/billing.mdx index 63430377cc61..30490b85f3cc 100644 --- a/website/pages/mr/subgraphs/billing.mdx +++ b/website/pages/mr/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. पृष्ठाच्या वरच्या उजव्या कोपर्यात "कनेक्ट वॉलेट" बटणावर क्लिक करा. तुम्हाला वॉलेट निवड पृष्ठावर पुनर्निर्देशित केले जाईल. तुमचे वॉलेट निवडा आणि "कनेक्ट" वर क्लिक करा. 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. पृष्ठाच्या वरच्या उजव्या कोपर्यात "कनेक्ट वॉलेट" बटणावर क्लिक करा. तुम्हाला वॉलेट निवड पृष्ठावर पुनर्निर्देशित केले जाईल. तुमचे वॉलेट निवडा आणि "कनेक्ट" वर क्लिक करा. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/mr/subgraphs/cookbook/arweave.mdx b/website/pages/mr/subgraphs/cookbook/arweave.mdx index a4aebc61808d..1c5300cce813 100644 --- a/website/pages/mr/subgraphs/cookbook/arweave.mdx +++ b/website/pages/mr/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Arweave डेटा स्रोत दोन प्रकारच्या इव्हेंटवर प्रक्रिया करण्यासाठी हँडलर [AssemblyScript](https://www.assemblyscript.org/) मध्ये लिहिलेले आहेत. -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## प्रश्न करत आहे Arweave सबग्राफ -Arweave subgraphs साठी GraphQL एंडपॉइंट विद्यमान API इंटरफेससह स्कीमा व्याख्येद्वारे निर्धारित केला जातो. अधिक माहितीसाठी कृपया [GraphQL API दस्तऐवज](/querying/graphql-api/) ला भेट द्या. +Arweave subgraphs साठी GraphQL एंडपॉइंट विद्यमान API इंटरफेससह स्कीमा व्याख्येद्वारे निर्धारित केला जातो. अधिक माहितीसाठी कृपया [GraphQL API दस्तऐवज](/subgraphs/querying/graphql-api/) ला भेट द्या. ## उदाहरणे सबग्राफ diff --git a/website/pages/mr/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/mr/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/mr/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/mr/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/mr/subgraphs/cookbook/cosmos.mdx b/website/pages/mr/subgraphs/cookbook/cosmos.mdx index 80243dc25ebd..47ff05bda552 100644 --- a/website/pages/mr/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/mr/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and इव्हेंटवर प्रक्रिया करण्यासाठी हँडलर [AssemblyScript](https://www.assemblyscript.org/) मध्ये लिहिलेले आहेत. -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## कॉसमॉस सबग्राफची चौकशी करत आहे -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## समर्थित कॉसमॉस ब्लॉकचेन diff --git a/website/pages/mr/subgraphs/cookbook/derivedfrom.mdx b/website/pages/mr/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/mr/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/mr/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/mr/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/mr/subgraphs/cookbook/grafting-hotfix.mdx index 16ee51f808cd..871f930abd43 100644 --- a/website/pages/mr/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/mr/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/mr/subgraphs/cookbook/grafting.mdx b/website/pages/mr/subgraphs/cookbook/grafting.mdx index 22f16892c933..f1e1538b93dc 100644 --- a/website/pages/mr/subgraphs/cookbook/grafting.mdx +++ b/website/pages/mr/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## विद्यमान सबग्राफ तयार करणे -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [सबग्राफ उदाहरण रेपो](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> टीप: या लेखातील बरीच सामग्री पूर्वी प्रकाशित [Arweave लेख](/cookbook/arweave/) मधून घेतली गेली आहे +> टीप: या लेखातील बरीच सामग्री पूर्वी प्रकाशित [Arweave लेख](/subgraphs/cookbook/arweave/) मधून घेतली गेली आहे diff --git a/website/pages/mr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/mr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/mr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/mr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/mr/subgraphs/cookbook/near.mdx b/website/pages/mr/subgraphs/cookbook/near.mdx index 2d4f7f7b6d24..89b6b4eba868 100644 --- a/website/pages/mr/subgraphs/cookbook/near.mdx +++ b/website/pages/mr/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ This guide is an introduction to building subgraphs indexing smart contracts on **schema.graphql:** एक स्कीमा फाइल जी तुमच्या सबग्राफसाठी कोणता डेटा संग्रहित केला जातो आणि GraphQL द्वारे त्याची क्वेरी कशी करावी हे परिभाषित करते. जवळच्या सबग्राफसाठी आवश्यकता [विद्यमान दस्तऐवज](/developing/creating-a-subgraph/#the-graphql-schema) द्वारे कव्हर केल्या जातात. -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. सबग्राफ विकासादरम्यान दोन प्रमुख आज्ञा आहेत: @@ -98,7 +98,7 @@ accounts: इव्हेंटवर प्रक्रिया करण्यासाठी हँडलर [AssemblyScript](https://www.assemblyscript.org/) मध्ये लिहिलेले आहेत. -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - ब्लॉक हँडलर्सना एक `ब्लॉक` मिळेल - पावती हाताळणाऱ्यांना `ReceiptWithOutcome` मिळेल -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## NEAR सबग्राफ डिप्लॉय करण्यासाठी @@ -228,7 +228,7 @@ NEAR ची अनुक्रमणिका देणारा आलेख ## NEAR सबग्राफची क्वेरी करणे -NEAR subgraphs साठी GraphQL एंडपॉइंट विद्यमान API इंटरफेससह स्कीमा व्याख्येद्वारे निर्धारित केला जातो. अधिक माहितीसाठी कृपया [GraphQL API दस्तऐवज](/querying/graphql-api/) ला भेट द्या. +NEAR subgraphs साठी GraphQL एंडपॉइंट विद्यमान API इंटरफेससह स्कीमा व्याख्येद्वारे निर्धारित केला जातो. अधिक माहितीसाठी कृपया [GraphQL API दस्तऐवज](/subgraphs/querying/graphql-api/) ला भेट द्या. ## उदाहरणे सबग्राफ @@ -276,7 +276,7 @@ NEARサブグラフの「保留中」機能はまだサポートされていま ### माझा प्रश्न उत्तर दिला नाही, NEAR सबग्राफ तयार करण्यासाठी अधिक मदत कुठे मिळेल? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## संदर्भ diff --git a/website/pages/mr/subgraphs/cookbook/pruning.mdx b/website/pages/mr/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/mr/subgraphs/cookbook/pruning.mdx +++ b/website/pages/mr/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/mr/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/mr/subgraphs/cookbook/timeseries.mdx b/website/pages/mr/subgraphs/cookbook/timeseries.mdx index ab5b1b677d64..aef1fe57ac5f 100644 --- a/website/pages/mr/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/mr/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/mr/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/mr/subgraphs/cookbook/transfer-to-the-graph.mdx index 3ab0ac609022..08ea42476c1a 100644 --- a/website/pages/mr/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/mr/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### उदाहरण @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/mr/subgraphs/developing/creating/advanced.mdx b/website/pages/mr/subgraphs/developing/creating/advanced.mdx index 0908f93a2214..40e8b972fba8 100644 --- a/website/pages/mr/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/mr/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { जर मूळ घटक आणि परिणामी फाइल डेटा स्रोत घटक यांच्यातील संबंध 1:1 असेल तर, आयपीएफएस सीआयडी लुकअप म्हणून वापरून मूळ घटकाला परिणामी फाइल घटकाशी जोडणे हा सर्वात सोपा नमुना आहे. तुम्हाला तुमच्या नवीन फाइल-आधारित घटकांचे मॉडेलिंग करण्यात अडचण येत असल्यास Discord वर संपर्क साधा! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### फाइल्सवर प्रक्रिया करण्यासाठी नवीन हँडलर तयार करा -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0. तुम्ही एनएफटी मेटाडेटाला संबंधित टोकनशी लिंक करत असल्यास, टोकन एंटिटीमधील मेटाडेटा घटकाचा संदर्भ देण्यासाठी मेटाडेटाचा IPFS हॅश वापरा. आयडी म्हणून IPFS हॅश वापरून मेटाडेटा घटक जतन करा. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### विद्यमान सबग्राफवर कलम करणे -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx index d96ebeaee324..75baf7701a15 100644 --- a/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/mr/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: असेंबलीस्क्रिप्ट API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx index 7c50a40e48fd..210e247b2270 100644 --- a/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/mr/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## सविश्लेषण -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## प्रारंभ करणे @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx b/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx index fbd122685dc7..1328e880b019 100644 --- a/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/mr/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/mr/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/mr/subgraphs/developing/creating/starting-your-subgraph.mdx index 3920ea48feaf..31806369cd19 100644 --- a/website/pages/mr/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/mr/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/mr/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/mr/subgraphs/developing/creating/subgraph-manifest.mdx index fad2db52e58e..74f2af02b12e 100644 --- a/website/pages/mr/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/mr/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). मॅनिफेस्टसाठी अद्यतनित करण्याच्या महत्त्वाच्या नोंदी आहेत: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/mr/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/mr/subgraphs/developing/creating/unit-testing-framework.mdx index 86ac5cbcd673..8cb83f7735ae 100644 --- a/website/pages/mr/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/mr/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,7 @@ ___ ___ _ _ _ _ _ > गंभीर: संदर्भासह वैध मॉड्यूलमधून WasmInstance तयार करू शकलो नाही: अज्ञात आयात: wasi_snapshot_preview1::fd_write परिभाषित केले गेले नाही -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) +This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx index 5798560f270d..f57e6bd5ce33 100644 --- a/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/mr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### ग्राफ नेटवर्कसह सबग्राफ सुसंगतता In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - खालीलपैकी कोणतीही वैशिष्ट्ये वापरू नयेत: - ipfs.cat & ipfs.map - गैर-घातक त्रुटी @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## सबग्राफ आवृत्त्यांचे स्वयंचलित संग्रहण diff --git a/website/pages/mr/subgraphs/developing/developer-faq.mdx b/website/pages/mr/subgraphs/developing/developer-faq.mdx index 76f12ab1d704..8c4f3ac6578c 100644 --- a/website/pages/mr/subgraphs/developing/developer-faq.mdx +++ b/website/pages/mr/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You can deploy a new version of your subgraph to Subgraph Studio using the CLI. ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ When new dynamic data source are created, the handlers defined for dynamic data ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -तुम्ही समर्थित नेटवर्कची सूची [येथे](/developing/supported-networks/) शोधू शकता. +तुम्ही समर्थित नेटवर्कची सूची [येथे](/supported-networks/) शोधू शकता. ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/mr/subgraphs/developing/introduction.mdx b/website/pages/mr/subgraphs/developing/introduction.mdx index 7ba2e1c2211a..9f9f1251fc88 100644 --- a/website/pages/mr/subgraphs/developing/introduction.mdx +++ b/website/pages/mr/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: विकसनशील --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## सविश्लेषण @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx index c8bc554999f8..101a9cf17585 100644 --- a/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/mr/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### प्रकाशित सबग्राफसाठी मेटाडेटा अपडेट करत आहे @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/mr/subgraphs/developing/subgraphs.mdx b/website/pages/mr/subgraphs/developing/subgraphs.mdx index 1738964b82d2..b16c6c87f7c9 100644 --- a/website/pages/mr/subgraphs/developing/subgraphs.mdx +++ b/website/pages/mr/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/mr/subgraphs/explorer.mdx b/website/pages/mr/subgraphs/explorer.mdx index 1d967cd1357d..f51717dd97fd 100644 --- a/website/pages/mr/subgraphs/explorer.mdx +++ b/website/pages/mr/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -इंडेक्सर कसे व्हावे याबद्दल अधिक जाणून घेण्यासाठी, तुम्ही [अधिकृत दस्तऐवज](/network/indexing/) किंवा [द ग्राफ अकादमी इंडेक्सर मार्गदर्शक](https://thegraph.academy/delegators/ पाहू शकता choosing-indexers/) +इंडेक्सर कसे व्हावे याबद्दल अधिक जाणून घेण्यासाठी, तुम्ही [अधिकृत दस्तऐवज](/indexing/overview/) किंवा [द ग्राफ अकादमी इंडेक्सर मार्गदर्शक](https://thegraph.academy/delegators/ पाहू शकता choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/mr/subgraphs/querying/best-practices.mdx b/website/pages/mr/subgraphs/querying/best-practices.mdx index 1e729d793cf8..f24378edce6b 100644 --- a/website/pages/mr/subgraphs/querying/best-practices.mdx +++ b/website/pages/mr/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/mr/subgraphs/querying/graphql-api.mdx b/website/pages/mr/subgraphs/querying/graphql-api.mdx index 67f41194b21d..51c5da2c1a28 100644 --- a/website/pages/mr/subgraphs/querying/graphql-api.mdx +++ b/website/pages/mr/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/mr/subgraphs/querying/introduction.mdx b/website/pages/mr/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/mr/subgraphs/querying/introduction.mdx +++ b/website/pages/mr/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/mr/subgraphs/quick-start.mdx b/website/pages/mr/subgraphs/quick-start.mdx index af229e33e695..40ecc489c838 100644 --- a/website/pages/mr/subgraphs/quick-start.mdx +++ b/website/pages/mr/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: क्विक स्टार्ट --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## पूर्वतयारी - एक क्रिप्टो वॉलेट -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/mr/substreams/sps/sps-faq.mdx b/website/pages/mr/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/mr/substreams/sps/sps-faq.mdx +++ b/website/pages/mr/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/mr/supported-networks.mdx b/website/pages/mr/supported-networks.mdx index 9e47f25c86e6..2f3c40917b37 100644 --- a/website/pages/mr/supported-networks.mdx +++ b/website/pages/mr/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/nl/about.mdx b/website/pages/nl/about.mdx index 641ff09b8d15..ab5a9033cdac 100644 --- a/website/pages/nl/about.mdx +++ b/website/pages/nl/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/nl/archived/arbitrum/arbitrum-faq.mdx b/website/pages/nl/archived/arbitrum/arbitrum-faq.mdx index 46baaad9d1e0..ee8b300ccb87 100644 --- a/website/pages/nl/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/nl/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Om gebruik te maken van The Graph op L2, gebruik deze keuzeschakelaar om te wiss ## Als een subgraph ontwikkelaar, data consument, Indexer, Curator, of Delegator, wat moet ik nu doen? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Alles is grondig getest, en een eventualiteiten plan is gemaakt en klaargezet vo ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ De brug is [grondig ge-audit](https://code4rena.com/contests/2022-10-the-graph-l Het toevoegen van GRT aan je Arbitrum factuurbalans kan worden gedaan met een èèn klik ervaring in [Subgraph Studio](https://thegraph.com/studio/). Je kunt eenvoudig je GRT naar Arbitrum overzetten en je API-sleutels vullen in één transactie. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/nl/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/nl/archived/arbitrum/l2-transfer-tools-faq.mdx index 70eadd534422..45e6b2ec3dc2 100644 --- a/website/pages/nl/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/nl/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx index 191f95ca8a84..4bd92d074f5e 100644 --- a/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/nl/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Gids voor L2 Transfer Tools The Graph heeft het eenvoudig gemaakt om naar L2 op Arbitrum One over te stappen. Voor elke deelnemer aan het protocol is er een set L2 Transfer Tools ontwikkeld om het overzetten van GRT naar L2 makkelijk te maken voor alle netwerkdeelnemers. Deze tools vereisen dat u een specifieke reeks stappen volgt, afhankelijk van wat u overdraagt. -Sommige veelgestelde vragen over deze tools worden beantwoord in de [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). De FAQs bevatten diepgaande uitleg over hoe de tools te gebruiken, hoe ze werken, en punten om rekening mee to houden bij het gebruiken ervan. +Sommige veelgestelde vragen over deze tools worden beantwoord in de [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). De FAQs bevatten diepgaande uitleg over hoe de tools te gebruiken, hoe ze werken, en punten om rekening mee to houden bij het gebruiken ervan. ## Hoe zet je je subgraph over naar Arbitrum (L2) diff --git a/website/pages/nl/archived/sunrise.mdx b/website/pages/nl/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/nl/archived/sunrise.mdx +++ b/website/pages/nl/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/nl/contracts.mdx b/website/pages/nl/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/nl/contracts.mdx +++ b/website/pages/nl/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/nl/indexing/chain-integration-overview.mdx b/website/pages/nl/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/nl/indexing/chain-integration-overview.mdx +++ b/website/pages/nl/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/nl/indexing/new-chain-integration.mdx b/website/pages/nl/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/nl/indexing/new-chain-integration.mdx +++ b/website/pages/nl/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/nl/indexing/overview.mdx b/website/pages/nl/indexing/overview.mdx index e86a0092b1ca..c625efca9cee 100644 --- a/website/pages/nl/indexing/overview.mdx +++ b/website/pages/nl/indexing/overview.mdx @@ -87,7 +87,7 @@ Zodra een allocatie is gesloten, zijn de rebates beschikbaar om door de Indexeer ### Wat is de Query Fee Cut en de Indexing Reward Cut? -De `queryFeeCut` en `indexingRewardCut` waarden zijn delegatie parameters die de Indexer kan instellen samen met de cooldownBlocks om de verdeling GRT te controleren tussen de Indexer en hun Delegators. Zie de laatste stappen in [Inzetten in het Protocol](/network/indexing/#stake-in-the-protocol) voor instructies op delegatie parameters in the stellen. +De `queryFeeCut` en `indexingRewardCut` waarden zijn delegatie parameters die de Indexer kan instellen samen met de cooldownBlocks om de verdeling GRT te controleren tussen de Indexer en hun Delegators. Zie de laatste stappen in [Inzetten in het Protocol](/indexing/overview/#stake-in-the-protocol) voor instructies op delegatie parameters in the stellen. - **queryFeeCut** - het % van de query kosten rebates die worden verdeeld aan de Indexeerder. Als dit is ingesteld op 95%, ontvangt de Indexeerder 95% van de query kosten die zijn verdiend wanneer een allocatie wordt gesloten, met de overige 5% gaande naar Delegators. @@ -121,7 +121,7 @@ Indexeerders kunnen zich onderscheiden door geavanceerde technieken toe te passe ### Wat zijn enkele basisveiligheidsmaatregelen die een Indexeerder moet nemen? -- **Operator wallet** - Het opzetten van een operator wallet is een belangrijke voorzorgsmaatregel omdat het een Indexeerder in staat stelt om scheiding te behouden tussen de sleutels die de GRT beheren en degenen die de dagelijkse operaties beheren. Zie [Inzet in het Protocol](/network/indexing/#stake-in-the-protocol) voor instructies. +- **Operator wallet** - Het opzetten van een operator wallet is een belangrijke voorzorgsmaatregel omdat het een Indexeerder in staat stelt om scheiding te behouden tussen de sleutels die de GRT beheren en degenen die de dagelijkse operaties beheren. Zie [Inzet in het Protocol](/indexing/overview/#stake-in-the-protocol) voor instructies. - **Firewall** - Alleen de Indexer service hoeft openbaar te worden blootgesteld en er moet extra aandacht worden besteed aan het vergrendelen van de admin poorten en database toegang: de Graph Node Jason-RPC endpoint (standaardpoort: 8030), de Indexer management API endpoint (standaardpoort: 18000), en de Postgres database endpoint (standaardpoort: 5432) mogen niet worden blootgesteld. @@ -375,7 +375,7 @@ Om succesvol deel te nemen aan het netwerk is bijna constante monitoring en inte #### Aan de slag -De indexer agent en indexer service moeten zich op de zelfde locatie bevinden als de Graph Node. Er zijn vele manieren om de virtuele uitvoeromgeving voor uw indexer-componenten op te zetten; we zullen uitleggen hoe ze op baremetal uit te voeren zijn met NPM-pakketten of de source code, of via Kubernetes en Docker op de Google Cloud Kubernetes Engine. Als deze voorbeelden niet goed zullen werken op uw infrastructuur, is er waarschijnlijk een community guide om als alternatief te gebruiken. Kom gerust hallo zeggen op [Discord](https://discord.gg/graphprotocol)! Onthoud om [GRT in the zetten](/network/indexing/#stake-in-the-protocol) in het protocol voordat u uw indexer-componenten start! +De indexer agent en indexer service moeten zich op de zelfde locatie bevinden als de Graph Node. Er zijn vele manieren om de virtuele uitvoeromgeving voor uw indexer-componenten op te zetten; we zullen uitleggen hoe ze op baremetal uit te voeren zijn met NPM-pakketten of de source code, of via Kubernetes en Docker op de Google Cloud Kubernetes Engine. Als deze voorbeelden niet goed zullen werken op uw infrastructuur, is er waarschijnlijk een community guide om als alternatief te gebruiken. Kom gerust hallo zeggen op [Discord](https://discord.gg/graphprotocol)! Onthoud om [GRT in the zetten](/indexing/overview/#stake-in-the-protocol) in het protocol voordat u uw indexer-componenten start! #### Met NPM-pakketten @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Met K8s en Terraform -Zie de sectie [Infrastructuur van de server instellen met behulp van Terraform op Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Zie de sectie [Infrastructuur van de server instellen met behulp van Terraform op Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Gebruik @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/nl/indexing/tap.mdx b/website/pages/nl/indexing/tap.mdx index 3e8185186982..4132216ca5b6 100644 --- a/website/pages/nl/indexing/tap.mdx +++ b/website/pages/nl/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/nl/resources/benefits.mdx b/website/pages/nl/resources/benefits.mdx index 2bab6ae0a90b..6e0dff48b863 100644 --- a/website/pages/nl/resources/benefits.mdx +++ b/website/pages/nl/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Signaal cureren op een subgraph is een optionele eenmalige, kostenneutrale actie (bijv. $1000 aan signaal kan worden gecureerd op een subgraph en later worden opgenomen - met het potentieel om rendementen te verdienen tijdens het proces). @@ -89,4 +89,4 @@ Het gedecentraliseerde netwerk van The Graph biedt gebruikers toegang tot geogra Samenvattend: Het Graph Network is goedkoper, gemakkelijker te gebruiken en levert superieure resultaten in vergelijking met het lokaal hosten van een `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/nl/resources/roles/curating.mdx b/website/pages/nl/resources/roles/curating.mdx index 040afc3b2f01..53182700e48a 100644 --- a/website/pages/nl/resources/roles/curating.mdx +++ b/website/pages/nl/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Hoe werkt het Signaleren -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) Een curator kan ervoor kiezen om een signaal af te geven voor een specifieke subgraph versie, of ze kunnen ervoor kiezen om hun signaal automatisch te laten migreren naar de nieuwste versie van de subgraph. Beide strategieën hebben voordelen en nadelen. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. De querymarkt is nog jong bij het Graph Netwerk en er bestaat een risico dat je %APY lager kan zijn dan je verwacht door opkomende marktdynamiek. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Een subgraph kan stuk gaan door een bug. Een subgraph die stuk is gegenereerd geen querykosten. Als gevolg hiervan moet je wachten tot de ontwikkelaar de bug repareert en een nieuwe versie implementeert. - Als je bent geabonneerd op de nieuwste versie van een subgraph, worden je curatieaandelen automatisch gemigreerd naar die nieuwe versie. Er is een curatiebelasting van 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/nl/resources/tokenomics.mdx b/website/pages/nl/resources/tokenomics.mdx index e2e4c904000d..73a1adda922b 100644 --- a/website/pages/nl/resources/tokenomics.mdx +++ b/website/pages/nl/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/nl/subgraphs/billing.mdx b/website/pages/nl/subgraphs/billing.mdx index dec5cfdadc12..f3f52bbf35ee 100644 --- a/website/pages/nl/subgraphs/billing.mdx +++ b/website/pages/nl/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/nl/subgraphs/cookbook/arweave.mdx b/website/pages/nl/subgraphs/cookbook/arweave.mdx index 056671f1b774..0d8a71a7131c 100644 --- a/website/pages/nl/subgraphs/cookbook/arweave.mdx +++ b/website/pages/nl/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/nl/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/nl/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/nl/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/nl/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/nl/subgraphs/cookbook/cosmos.mdx b/website/pages/nl/subgraphs/cookbook/cosmos.mdx index cd23a3742f86..dddfbff521d0 100644 --- a/website/pages/nl/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/nl/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/nl/subgraphs/cookbook/derivedfrom.mdx b/website/pages/nl/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/nl/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/nl/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/nl/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/nl/subgraphs/cookbook/grafting-hotfix.mdx index 040e3a8209d5..a0bd3f4ab1c2 100644 --- a/website/pages/nl/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/nl/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/nl/subgraphs/cookbook/grafting.mdx b/website/pages/nl/subgraphs/cookbook/grafting.mdx index 7aa79c7e2755..57d5169830a7 100644 --- a/website/pages/nl/subgraphs/cookbook/grafting.mdx +++ b/website/pages/nl/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/nl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/nl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/nl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/nl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/nl/subgraphs/cookbook/near.mdx b/website/pages/nl/subgraphs/cookbook/near.mdx index 501a04b9455f..4a4ac06f2e86 100644 --- a/website/pages/nl/subgraphs/cookbook/near.mdx +++ b/website/pages/nl/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. Tijdens subgraph ontwikkeling zijn er twee belangrijke commando's: @@ -98,7 +98,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/nl/subgraphs/cookbook/pruning.mdx b/website/pages/nl/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/nl/subgraphs/cookbook/pruning.mdx +++ b/website/pages/nl/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/nl/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/nl/subgraphs/cookbook/timeseries.mdx b/website/pages/nl/subgraphs/cookbook/timeseries.mdx index 2ce0ce266ccf..0168be53d7ed 100644 --- a/website/pages/nl/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/nl/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/nl/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/nl/subgraphs/cookbook/transfer-to-the-graph.mdx index 6a5d2c2793f3..64c225442860 100644 --- a/website/pages/nl/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/nl/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/nl/subgraphs/developing/creating/advanced.mdx b/website/pages/nl/subgraphs/developing/creating/advanced.mdx index 3a08ddab7066..bc3a9a86efb6 100644 --- a/website/pages/nl/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/nl/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx index 8aa0bf0027bf..4c5ce57993f2 100644 --- a/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/nl/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx index a23e14babbb2..87c33efe428e 100644 --- a/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/nl/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx b/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/nl/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/nl/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/nl/subgraphs/developing/creating/starting-your-subgraph.mdx index 5127f01632aa..f463ca3e9507 100644 --- a/website/pages/nl/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/nl/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/nl/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/nl/subgraphs/developing/creating/subgraph-manifest.mdx index f282f3946e75..b4c0e467c780 100644 --- a/website/pages/nl/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/nl/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/nl/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/nl/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/nl/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/nl/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx index f6b0f1b8d599..6bbc8a970646 100644 --- a/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/nl/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/nl/subgraphs/developing/developer-faq.mdx b/website/pages/nl/subgraphs/developing/developer-faq.mdx index c68ddb8c7d00..cb3410cc5f5f 100644 --- a/website/pages/nl/subgraphs/developing/developer-faq.mdx +++ b/website/pages/nl/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/nl/subgraphs/developing/introduction.mdx b/website/pages/nl/subgraphs/developing/introduction.mdx index e280e2be1058..6b84b83bf60a 100644 --- a/website/pages/nl/subgraphs/developing/introduction.mdx +++ b/website/pages/nl/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Ontwikkelen --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 09c20daa62fa..1d9dc30a259e 100644 --- a/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/nl/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/nl/subgraphs/developing/subgraphs.mdx b/website/pages/nl/subgraphs/developing/subgraphs.mdx index 42c1e806f822..e30b77cec1ae 100644 --- a/website/pages/nl/subgraphs/developing/subgraphs.mdx +++ b/website/pages/nl/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/nl/subgraphs/explorer.mdx b/website/pages/nl/subgraphs/explorer.mdx index e34ca81d144e..a4a73a43e53d 100644 --- a/website/pages/nl/subgraphs/explorer.mdx +++ b/website/pages/nl/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Om meer te weten te komen over hoe je een Indexer kunt worden, kun je een kijkje nemen in de [officiële documentatie](/network/indexing/) of de Indexeerdersgidsen van [The Graph Academy](https://thegraph.academy/delegators/choosing-indexers/) +Om meer te weten te komen over hoe je een Indexer kunt worden, kun je een kijkje nemen in de [officiële documentatie](/indexing/overview/) of de Indexeerdersgidsen van [The Graph Academy](https://thegraph.academy/delegators/choosing-indexers/) ![Indexering details paneel](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Afbeelding 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Het totale bedrag aan GRT dat ze momenteel in het protocol hebben - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Netwerk diff --git a/website/pages/nl/subgraphs/querying/best-practices.mdx b/website/pages/nl/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/nl/subgraphs/querying/best-practices.mdx +++ b/website/pages/nl/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/nl/subgraphs/querying/graphql-api.mdx b/website/pages/nl/subgraphs/querying/graphql-api.mdx index 917fad3f2406..8813e2eeb3f3 100644 --- a/website/pages/nl/subgraphs/querying/graphql-api.mdx +++ b/website/pages/nl/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/nl/subgraphs/querying/introduction.mdx b/website/pages/nl/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/nl/subgraphs/querying/introduction.mdx +++ b/website/pages/nl/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/nl/subgraphs/quick-start.mdx b/website/pages/nl/subgraphs/quick-start.mdx index 671df69b7c30..d18b354df77c 100644 --- a/website/pages/nl/subgraphs/quick-start.mdx +++ b/website/pages/nl/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Snelle Start --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/nl/substreams/sps/sps-faq.mdx b/website/pages/nl/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/nl/substreams/sps/sps-faq.mdx +++ b/website/pages/nl/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/nl/supported-networks.mdx b/website/pages/nl/supported-networks.mdx index a3fc9b60202a..72d79e26fcc3 100644 --- a/website/pages/nl/supported-networks.mdx +++ b/website/pages/nl/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/pl/about.mdx b/website/pages/pl/about.mdx index f669bb650fd6..199bc6a77400 100644 --- a/website/pages/pl/about.mdx +++ b/website/pages/pl/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/pl/archived/arbitrum/arbitrum-faq.mdx b/website/pages/pl/archived/arbitrum/arbitrum-faq.mdx index 85aa42a5b6f1..8e3f51fe99c9 100644 --- a/website/pages/pl/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/pl/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ By w pełni wykorzystać wszystkie zalety używania protokołu The Graph na L2 w ## Co powinien wiedzieć na ten temat subgraf developer, konsument danych, indekser, kurator lub delegator? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Wszystko zostało dokładnie przetestowane i przygotowano plan awaryjny, aby zap ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ Most został poddany [szczegółowemu audytowi](https://code4rena.com/contests/2 Dodanie GRT do salda rozliczeniowego Arbitrum można wykonać jednym kliknięciem w [Subgraph Studio](https://thegraph.com/studio/). To właśnie tam można łatwo przenieść swoje GRT do Arbitrum i uzupełnić klucze API w jednej transakcji. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/pl/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/pl/archived/arbitrum/l2-transfer-tools-faq.mdx index 7ce69aeab929..67cf4fd948ec 100644 --- a/website/pages/pl/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/pl/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Czy mogę używać tego samego portfela, którego używam w mainnecie Ethereum? -Jeśli korzystasz z portfela [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), możesz użyć tego samego adresu. Jeśli portfel głównej sieci Ethereum jest kontraktem (np. multisig), musisz podać [Adres portfela Arbitrum](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-use-the-graph-on-l2), na który zostanie dokonany przelew. Prosimy o dokładne sprawdzenie adresu, ponieważ wszelkie przelewy na nieprawidłowy adres mogą spowodować ich trwałą utratę. Jeśli chcesz korzystać z multisig na L2, upewnij się, że wdrożyłeś kontrakt multisig na Arbitrum One. +Jeśli korzystasz z portfela [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), możesz użyć tego samego adresu. Jeśli portfel głównej sieci Ethereum jest kontraktem (np. multisig), musisz podać [Adres portfela Arbitrum](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-use-the-graph-on-l2), na który zostanie dokonany przelew. Prosimy o dokładne sprawdzenie adresu, ponieważ wszelkie przelewy na nieprawidłowy adres mogą spowodować ich trwałą utratę. Jeśli chcesz korzystać z multisig na L2, upewnij się, że wdrożyłeś kontrakt multisig na Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx index 014770ff141b..f7391f796a36 100644 --- a/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/pl/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Przewodnik po narzędziach przesyłania L2 Graph ułatwił przeniesienie danych do L2 na Arbitrum One. Dla każdego uczestnika protokołu dostępny jest zestaw narzędzi do przesyłania na L2, dzięki którym przeniesienie do L2 jest bezproblemowe dla wszystkich uczestników sieci. Narzędzia te wymagają wykonania określonego zestawu kroków w zależności od przenoszonych danych. -Odpowiedzi na najczęściej zadawane pytania dotyczące tych narzędzi znajdują się w [Narzędzia przesyłania L2 FAQ](/arbitrum/l2-transfer-tools-faq/). Odpowiedzi na najczęściej zadawane pytania zawierają szczegółowe wyjaśnienia dotyczące korzystania z narzędzi, ich działania i rzeczy, o których należy pamiętać podczas korzystania z nich. +Odpowiedzi na najczęściej zadawane pytania dotyczące tych narzędzi znajdują się w [Narzędzia przesyłania L2 FAQ](/archived/arbitrum/l2-transfer-tools-faq/). Odpowiedzi na najczęściej zadawane pytania zawierają szczegółowe wyjaśnienia dotyczące korzystania z narzędzi, ich działania i rzeczy, o których należy pamiętać podczas korzystania z nich. ## Jak przenieść swój subgraph do Arbitrum (L2) diff --git a/website/pages/pl/archived/sunrise.mdx b/website/pages/pl/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/pl/archived/sunrise.mdx +++ b/website/pages/pl/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/pl/contracts.mdx b/website/pages/pl/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/pl/contracts.mdx +++ b/website/pages/pl/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/pl/indexing/chain-integration-overview.mdx b/website/pages/pl/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/pl/indexing/chain-integration-overview.mdx +++ b/website/pages/pl/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/pl/indexing/new-chain-integration.mdx b/website/pages/pl/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/pl/indexing/new-chain-integration.mdx +++ b/website/pages/pl/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/pl/indexing/overview.mdx b/website/pages/pl/indexing/overview.mdx index c05c37a275ef..34a60d456cfc 100644 --- a/website/pages/pl/indexing/overview.mdx +++ b/website/pages/pl/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/pl/indexing/tap.mdx b/website/pages/pl/indexing/tap.mdx index 3e8185186982..4132216ca5b6 100644 --- a/website/pages/pl/indexing/tap.mdx +++ b/website/pages/pl/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/pl/resources/benefits.mdx b/website/pages/pl/resources/benefits.mdx index 3a3be46c2cf8..da704fd8db8d 100644 --- a/website/pages/pl/resources/benefits.mdx +++ b/website/pages/pl/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/pl/resources/roles/curating.mdx b/website/pages/pl/resources/roles/curating.mdx index a3b96ed010fe..6ddf8e91099c 100644 --- a/website/pages/pl/resources/roles/curating.mdx +++ b/website/pages/pl/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/pl/resources/tokenomics.mdx b/website/pages/pl/resources/tokenomics.mdx index e2e4c904000d..73a1adda922b 100644 --- a/website/pages/pl/resources/tokenomics.mdx +++ b/website/pages/pl/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/pl/subgraphs/billing.mdx b/website/pages/pl/subgraphs/billing.mdx index dec5cfdadc12..f3f52bbf35ee 100644 --- a/website/pages/pl/subgraphs/billing.mdx +++ b/website/pages/pl/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/pl/subgraphs/cookbook/arweave.mdx b/website/pages/pl/subgraphs/cookbook/arweave.mdx index 4c35f4ee8e2e..2098d5ab5932 100644 --- a/website/pages/pl/subgraphs/cookbook/arweave.mdx +++ b/website/pages/pl/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/pl/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/pl/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/pl/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/pl/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pl/subgraphs/cookbook/cosmos.mdx b/website/pages/pl/subgraphs/cookbook/cosmos.mdx index cd23a3742f86..dddfbff521d0 100644 --- a/website/pages/pl/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/pl/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/pl/subgraphs/cookbook/derivedfrom.mdx b/website/pages/pl/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/pl/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/pl/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pl/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/pl/subgraphs/cookbook/grafting-hotfix.mdx index 040e3a8209d5..a0bd3f4ab1c2 100644 --- a/website/pages/pl/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/pl/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pl/subgraphs/cookbook/grafting.mdx b/website/pages/pl/subgraphs/cookbook/grafting.mdx index 7aa79c7e2755..57d5169830a7 100644 --- a/website/pages/pl/subgraphs/cookbook/grafting.mdx +++ b/website/pages/pl/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/pl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/pl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/pl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/pl/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pl/subgraphs/cookbook/near.mdx b/website/pages/pl/subgraphs/cookbook/near.mdx index cc0bf8637bee..23a936406e7b 100644 --- a/website/pages/pl/subgraphs/cookbook/near.mdx +++ b/website/pages/pl/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/pl/subgraphs/cookbook/pruning.mdx b/website/pages/pl/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/pl/subgraphs/cookbook/pruning.mdx +++ b/website/pages/pl/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/pl/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/pl/subgraphs/cookbook/timeseries.mdx b/website/pages/pl/subgraphs/cookbook/timeseries.mdx index 2ce0ce266ccf..0168be53d7ed 100644 --- a/website/pages/pl/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/pl/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pl/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/pl/subgraphs/cookbook/transfer-to-the-graph.mdx index 6a5d2c2793f3..64c225442860 100644 --- a/website/pages/pl/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/pl/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/pl/subgraphs/developing/creating/advanced.mdx b/website/pages/pl/subgraphs/developing/creating/advanced.mdx index 3a08ddab7066..bc3a9a86efb6 100644 --- a/website/pages/pl/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/pl/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx index 8aa0bf0027bf..4c5ce57993f2 100644 --- a/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/pl/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx index 37a742e7c78a..72001c551547 100644 --- a/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/pl/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx b/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/pl/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/pl/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/pl/subgraphs/developing/creating/starting-your-subgraph.mdx index 5127f01632aa..f463ca3e9507 100644 --- a/website/pages/pl/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/pl/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/pl/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/pl/subgraphs/developing/creating/subgraph-manifest.mdx index f282f3946e75..b4c0e467c780 100644 --- a/website/pages/pl/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/pl/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/pl/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/pl/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/pl/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/pl/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx index 9adc37bddeb9..116e87a4912f 100644 --- a/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/pl/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/pl/subgraphs/developing/developer-faq.mdx b/website/pages/pl/subgraphs/developing/developer-faq.mdx index 0e8fb2d4f1bf..7997bcf012d2 100644 --- a/website/pages/pl/subgraphs/developing/developer-faq.mdx +++ b/website/pages/pl/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/pl/subgraphs/developing/introduction.mdx b/website/pages/pl/subgraphs/developing/introduction.mdx index 6ba33f6d916c..45cefaff16ef 100644 --- a/website/pages/pl/subgraphs/developing/introduction.mdx +++ b/website/pages/pl/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 4728db3eb245..e75e3b13d89e 100644 --- a/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/pl/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/pl/subgraphs/developing/subgraphs.mdx b/website/pages/pl/subgraphs/developing/subgraphs.mdx index 614577e46fb0..de2851ac1ad3 100644 --- a/website/pages/pl/subgraphs/developing/subgraphs.mdx +++ b/website/pages/pl/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/pl/subgraphs/explorer.mdx b/website/pages/pl/subgraphs/explorer.mdx index 593f49b397f9..c10068643631 100644 --- a/website/pages/pl/subgraphs/explorer.mdx +++ b/website/pages/pl/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/pl/subgraphs/querying/best-practices.mdx b/website/pages/pl/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/pl/subgraphs/querying/best-practices.mdx +++ b/website/pages/pl/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/pl/subgraphs/querying/graphql-api.mdx b/website/pages/pl/subgraphs/querying/graphql-api.mdx index 917fad3f2406..8813e2eeb3f3 100644 --- a/website/pages/pl/subgraphs/querying/graphql-api.mdx +++ b/website/pages/pl/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/pl/subgraphs/querying/introduction.mdx b/website/pages/pl/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/pl/subgraphs/querying/introduction.mdx +++ b/website/pages/pl/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/pl/subgraphs/quick-start.mdx b/website/pages/pl/subgraphs/quick-start.mdx index 6953408d9420..98f67d0f71a0 100644 --- a/website/pages/pl/subgraphs/quick-start.mdx +++ b/website/pages/pl/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: ' Na start' --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/pl/substreams/sps/sps-faq.mdx b/website/pages/pl/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/pl/substreams/sps/sps-faq.mdx +++ b/website/pages/pl/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/pl/supported-networks.mdx b/website/pages/pl/supported-networks.mdx index cd2062dcae7c..1833ac452dc2 100644 --- a/website/pages/pl/supported-networks.mdx +++ b/website/pages/pl/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/pt/about.mdx b/website/pages/pt/about.mdx index f244df9f2b9d..1648640230f7 100644 --- a/website/pages/pt/about.mdx +++ b/website/pages/pt/about.mdx @@ -24,7 +24,7 @@ No caso do exemplo listado acima, o Bored Ape Yacht Club, é possível realizar Levariam **horas, ou até mesmo dias**, para que um aplicativo descentralizado (dApp) executado em um navegador conseguisse uma resposta a estas questões simples. -Como alternativa, haveria a opção de construir o seu próprio servidor, processar as transações, salvá-las num banco de dados, e construir um endpoint de API sobre tudo isso tudo para poder fazer o query dos dados. Porém, esta opção [consome muitos recursos](/network/benefits/), precisa de manutenção, apresenta um único ponto de falha, e quebra propriedades de segurança importantes obrigatórias para a descentralização. +Como alternativa, haveria a opção de construir o seu próprio servidor, processar as transações, salvá-las num banco de dados, e construir um endpoint de API sobre tudo isso tudo para poder fazer o query dos dados. Porém, esta opção [consome muitos recursos](/resources/benefits/), precisa de manutenção, apresenta um único ponto de falha, e quebra propriedades de segurança importantes obrigatórias para a descentralização. Propriedades de blockchain, como finalidade, reorganizações de chain, ou blocos uncle, complicam ainda mais este processo, e não apenas o tornam longo e cansativo, mas dificultam conceitualmente a retirada de resultados precisos de queries dos dados da blockchain. diff --git a/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx b/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx index 873be7d055ef..3e8f82868222 100644 --- a/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/pt/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Para aproveitar o The Graph na L2, use este switcher de dropdown para alternar e ## Como um programador, consumidor de dados, Indexador, Curador ou Delegante, o que devo fazer agora? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Tudo foi testado exaustivamente, e já está pronto um plano de contingência pa ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? diff --git a/website/pages/pt/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/pt/archived/arbitrum/l2-transfer-tools-faq.mdx index 8b113f4edffa..b761a71d76fa 100644 --- a/website/pages/pt/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/pt/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ Estas ferramentas exigem aderência a um conjunto específico de passos a depend ### Posso usar a mesma carteira que uso na mainnet do Ethereum? -Se usa uma carteira [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), você poderá usar o mesmo endereço. Se a sua carteira na mainnet do Ethereum for um contrato (uma multisig, por ex.), então deve ser especificado um [endereço de carteira no Arbitrum](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) para onde a sua transferência será enviada. Por favor, tenha cuidado ao conferir o endereço, pois transferir a um endereço errado pode causar prejuízos permanentes. Se quiser usar uma multisig na L2, lance um contrato multisig no Arbitrum One. +Se usa uma carteira [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), você poderá usar o mesmo endereço. Se a sua carteira na mainnet do Ethereum for um contrato (uma multisig, por ex.), então deve ser especificado um [endereço de carteira no Arbitrum](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) para onde a sua transferência será enviada. Por favor, tenha cuidado ao conferir o endereço, pois transferir a um endereço errado pode causar prejuízos permanentes. Se quiser usar uma multisig na L2, lance um contrato multisig no Arbitrum One. Carteiras em blockchains EVM como Ethereum e Arbitrum são um par de chaves (pública e privada), que você cria sem precisar interagir com a blockchain. Qualquer carteira criada para o Ethereum também funcionará no Arbitrum sem ter que fazer qualquer outra coisa. diff --git a/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx index 6e25493c1292..c07432ab6097 100644 --- a/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/pt/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Guia das Ferramentas de Transferência para L2 O The Graph facilitou muito o processo de se mudar para a L2 no Arbitrum One. Para cada participante no protocolo, há um conjunto de Ferramentas de Transferência para L2 que suavizam o processo para todos os participantes na rede. Estas ferramentas exigem que você siga um conjunto específico de passos, dependente no que você transferir. -Algumas perguntas frequentes sobre estas ferramentas são respondidas nas [Perguntas Frequentes das Ferramentas de Transferência para L2](/arbitrum/l2-transfer-tools-faq/). As Perguntas Frequentes contém explicações profundas sobre como usar as ferramentas, como elas funcionam, e coisas a lembrar ao usá-las. +Algumas perguntas frequentes sobre estas ferramentas são respondidas nas [Perguntas Frequentes das Ferramentas de Transferência para L2](/archived/arbitrum/l2-transfer-tools-faq/). As Perguntas Frequentes contém explicações profundas sobre como usar as ferramentas, como elas funcionam, e coisas a lembrar ao usá-las. ## Como transferir o seu subgraph ao Arbitrum (L2) diff --git a/website/pages/pt/archived/sunrise.mdx b/website/pages/pt/archived/sunrise.mdx index 216572c5be6d..85a7eefe2397 100644 --- a/website/pages/pt/archived/sunrise.mdx +++ b/website/pages/pt/archived/sunrise.mdx @@ -22,7 +22,7 @@ Não, o Subgraph Studio não foi impactado pelo Nascer do Sol. Os subgraphs esta ### Por que subgraphs eram publicados ao Arbitrum, eles começaram a indexar uma rede diferente? -A Graph Network foi lançada inicialmente à mainnet do Ethereum, mas migrou ao Arbitrum One apra reduzir custos de gas para todos os utilizadores. Assim, todos os subgraphs novos são publicados à Graph Network no Arbitrum para que possam ser apoiados por Indexadores. O Arbitrum é a rede em qual os subgraphs são publicados, mas subgraphs podem indexar quaisquer das [redes apoiadas](/developing/supported-networks/) +A Graph Network foi lançada inicialmente à mainnet do Ethereum, mas migrou ao Arbitrum One apra reduzir custos de gas para todos os utilizadores. Assim, todos os subgraphs novos são publicados à Graph Network no Arbitrum para que possam ser apoiados por Indexadores. O Arbitrum é a rede em qual os subgraphs são publicados, mas subgraphs podem indexar quaisquer das [redes apoiadas](/supported-networks/) ## Sobre o Indexador de Atualização @@ -33,7 +33,7 @@ O Indexador de atualização foi construído para melhorar a experiência de atu ### O que o Indexador de atualização faz? - Ele inicializa chains que ainda não tenham recompensas de indexação na Graph Network, e garante que um Indexador esteja disponível para servir queries o mais rápido possível após a publicação de um subgraph. -- Ele apoia chains que antigamente só estavam disponíveis no serviço hospedado. Veja uma lista compreensiva de chains apoiadas [aqui](/developing/supported-networks/). +- Ele apoia chains que antigamente só estavam disponíveis no serviço hospedado. Veja uma lista compreensiva de chains apoiadas [aqui](/supported-networks/). - Indexadores que operam um Indexador de atualização o fazem como um serviço público, para apoiar novos subgraphs e chains adicionais que não tenham recompensas de indexação antes da aprovação do Graph Council. ### Porque a Edge & Node executa o Indexador de atualização? @@ -60,7 +60,7 @@ Ele opera numa base de "necessidade" e serve como uma reserva até que uma cota ### Como isto afeta os programadores de subgraph? -Progmadores de subgraph poderão enviar queries para os seus subgraphs na Graph Network quase imediatamente após migrar do serviço hospedado ou [publicá-los do Subgraph Studio](/publishing/publishing-a-subgraph/), já que não será necessário tempo de espera para a indexação. Note que a [criação de subgraphs](/developing/creating-a-subgraph/) não foi impactada por esta atualização. +Progmadores de subgraph poderão enviar queries para os seus subgraphs na Graph Network quase imediatamente após migrar do serviço hospedado ou [publicá-los do Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), já que não será necessário tempo de espera para a indexação. Note que a [criação de subgraphs](/developing/creating-a-subgraph/) não foi impactada por esta atualização. ### Como o Indexador de atualizações beneficia consumidores de dados? diff --git a/website/pages/pt/contracts.mdx b/website/pages/pt/contracts.mdx index 77cc18aa29b4..90b309e8c9c4 100644 --- a/website/pages/pt/contracts.mdx +++ b/website/pages/pt/contracts.mdx @@ -14,7 +14,7 @@ Este é o lançamento principal da Graph Network. ## Mainnet -Este foi o lançamento original da Graph Network. [Aprenda mais](/arbitrum/arbitrum-faq/) sobre o escalamento do The Graph com Arbitrum. +Este foi o lançamento original da Graph Network. [Aprenda mais](/archived/arbitrum/arbitrum-faq/) sobre o escalamento do The Graph com Arbitrum. diff --git a/website/pages/pt/indexing/chain-integration-overview.mdx b/website/pages/pt/indexing/chain-integration-overview.mdx index c03cd35fc70c..ba7e92f6032b 100644 --- a/website/pages/pt/indexing/chain-integration-overview.mdx +++ b/website/pages/pt/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Um processo de integração transparente e baseado em governança foi desenhado ## Fase 1. Integração Técnica -- Por favor, visite a página de [Integração de Novas Chains](/new-chain-integration/) para informações sobre o apoio do `graph-node` para chains novas. +- Por favor, visite a página de [Integração de Novas Chains](/indexing/new-chain-integration/) para informações sobre o apoio do `graph-node` para chains novas. - Equipas iniciam o processo de integração de protocolo com a criação de um tópico de Fórum [aqui](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Nova subcategoria de Fontes de Dados sob Governança e GIPs). O uso do modelo padrão do Fórum é obrigatório. ## Fase 2. Validação de Integração diff --git a/website/pages/pt/indexing/new-chain-integration.mdx b/website/pages/pt/indexing/new-chain-integration.mdx index 27dfb3931e4e..8fae626b60e0 100644 --- a/website/pages/pt/indexing/new-chain-integration.mdx +++ b/website/pages/pt/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ Para chains EVM, há um nível mais profundo de dados que podem ser alcançados ## Considerações de EVM - Diferença entre JSON-RPC e Firehose -Enquanto ambos o JSON-RPC e o Firehose são próprios para subgraphs, um Firehose é sempre necessário para programadores que querem construir com [Substreams](https://substreams.streamingfast.io). Apoiar os Substreams permite que programadores construam [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) para a nova chain, e tem o potencial de melhorar o desempenho dos seus subgraphs. Além disto, o Firehose — como um substituto pronto para a camada de extração JSON-RPC do `graph-node` — reduz em 90% o número de chamadas RPC exigidas para indexação geral. +Enquanto ambos o JSON-RPC e o Firehose são próprios para subgraphs, um Firehose é sempre necessário para programadores que querem construir com [Substreams](https://substreams.streamingfast.io). Apoiar os Substreams permite que programadores construam [subgraphs movidos a Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/) para a nova chain, e tem o potencial de melhorar o desempenho dos seus subgraphs. Além disto, o Firehose — como um substituto pronto para a camada de extração JSON-RPC do `graph-node` — reduz em 90% o número de chamadas RPC exigidas para indexação geral. - Todas essas chamadas `getLogs` e roundtrips são substituídas por um único fluxo que chega no coração do `graph-node`, um modelo de bloco único para todos os subgraphs que processa. @@ -77,4 +77,4 @@ O Graph Node deve então sincronizar o subgraph lançado caso não haja erros. D ## Subgraphs movidos por Substreams -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/pt/indexing/overview.mdx b/website/pages/pt/indexing/overview.mdx index 468fbd0a06c2..65b4f4fd7686 100644 --- a/website/pages/pt/indexing/overview.mdx +++ b/website/pages/pt/indexing/overview.mdx @@ -87,7 +87,7 @@ Quando uma alocação é fechada, os rebates podem ser reivindicados pelo Indexa ### O que são porção de taxa de consulta e porção de recompensa de indexação? -Os valores `queryFeeCut` e `indexingRewardCut` são parâmetros de delegação que o Indexador pode configurar junto com o `cooldownBlocks` para controlar a distribuição de GRT entre o Indexador e os seus Delegantes. Veja os últimos passos no [Staking no Protocolo](/network/indexing/#stake-in-the-protocol) para instruções sobre como configurar os parâmetros de delegação. +Os valores `queryFeeCut` e `indexingRewardCut` são parâmetros de delegação que o Indexador pode configurar junto com o `cooldownBlocks` para controlar a distribuição de GRT entre o Indexador e os seus Delegantes. Veja os últimos passos no [Staking no Protocolo](/indexing/overview/#stake-in-the-protocol) para instruções sobre como configurar os parâmetros de delegação. - **queryFeeCut** - o % de rebates de taxas de query a ser distribuído ao Indexador. Se isto for configurado em 95%, o Indexador receberá 95% das taxas de query ganhas quando uma alocação for fechada, com os outros 5% destinados aos Delegantes. @@ -121,7 +121,7 @@ Os Indexadores podem se diferenciar ao aplicar técnicas avançadas para decidir ### Há alguma precaução básica de segurança que um Indexador deve tomar? -- **Carteira de operador** — Configurar uma carteira de operador é importante, pois permite a um Indexador manter a separação entre as suas chaves que controlam o stake e aquelas no controlo das operações diárias. Mais informações em [Staking no Protocolo](/network/indexing/#stake-in-the-protocol). +- **Carteira de operador** — Configurar uma carteira de operador é importante, pois permite a um Indexador manter a separação entre as suas chaves que controlam o stake e aquelas no controlo das operações diárias. Mais informações em [Staking no Protocolo](/indexing/overview/#stake-in-the-protocol). - **Firewall** - O serviço de Indexadores é o único que precisa ser exposto publicamente, e o trancamento de portas de admin e acesso ao banco de dados exigem muito mais atenção: o endpoint JSON-RPC do Graph Node (porta padrão: 8030), o endpoint da API de gerenciamento do Indexador (porta padrão: 18000), e o endpoint do banco de dados Postgres (porta padrão: 5432) não devem ser expostos. @@ -375,7 +375,7 @@ Para participar com êxito na rede, são necessários monitorados e interações #### Começando -O agente indexador e o serviço indexador devem ser co-localizados com a sua infraestrutura de Graph Node. Há várias maneiras de preparar ambientes de execução virtual para os seus componentes de Indexador. Aqui, veja como executá-los em um bare-metal (servidor dedicado) com pacotes NPM ou código fonte, ou através do Kubernetes e o docker no Engine Kubernetes do Google Cloud. Se estes exemplos de setup não batem bem com a sua infraestrutura, provavelmente deverá consultar um guia de comunidade no nosso [Discord](https://discord.gg/graphprotocol). Lembre-se de [fazer staking no protocolo](/network/indexing/#stake-in-the-protocol) antes de iniciar os seus componentes de Indexador! +O agente indexador e o serviço indexador devem ser co-localizados com a sua infraestrutura de Graph Node. Há várias maneiras de preparar ambientes de execução virtual para os seus componentes de Indexador. Aqui, veja como executá-los em um bare-metal (servidor dedicado) com pacotes NPM ou código fonte, ou através do Kubernetes e o docker no Engine Kubernetes do Google Cloud. Se estes exemplos de setup não batem bem com a sua infraestrutura, provavelmente deverá consultar um guia de comunidade no nosso [Discord](https://discord.gg/graphprotocol). Lembre-se de [fazer staking no protocolo](/indexing/overview/#stake-in-the-protocol) antes de iniciar os seus componentes de Indexador! #### De pacotes NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Usando K8s e Terraform -Veja a seção sobre [preparar infraestruturas de servidor usando o Terraform no Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Veja a seção sobre [preparar infraestruturas de servidor usando o Terraform no Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Uso @@ -755,7 +755,7 @@ Os primeiros passos para participar como Indexador consistem em aprovar o protoc > Nota: Para os propósitos destas instruções, o Remix será usado para interação com contratos, mas é possível escolher a sua própria ferramenta ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/) e [MyCrypto](https://www.mycrypto.com/account) são algumas outras ferramentas conhecidas). -Quando um Indexador faz stake de GRT no protocolo, será possível iniciar os seus [componentes](/network/indexing/#indexer-components) e começar as suas interações com a rede. +Quando um Indexador faz stake de GRT no protocolo, será possível iniciar os seus [componentes](/indexing/overview/#indexer-components) e começar as suas interações com a rede. #### Aprovação de tokens @@ -815,6 +815,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Ativa** - Quando uma alocação é criada on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)), ela é considerada **ativa**. Uma porção do stake próprio e/ou delegado do Indexador é alocada a um lançamento de subgraph, que lhe permite resgatar recompensas de indexação e servir queries para aquele lançamento de subgraph. O agente indexador cria alocações baseada nas regras do Indexador. -- **Fechada** - Um Indexador pode fechar uma alocação após a passagem de um epoch ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)), ou o seu agente indexador a fechará automaticamente após o **maxAllocationEpochs** (atualmente, 28 dias). Quando uma alocação é fechada com uma prova de indexação válida (POI), as suas recompensas de indexação são distribuídas ao Indexador e aos seus Delegantes ([aprenda mais](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Fechada** - Um Indexador pode fechar uma alocação após a passagem de um epoch ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)), ou o seu agente indexador a fechará automaticamente após o **maxAllocationEpochs** (atualmente, 28 dias). Quando uma alocação é fechada com uma prova de indexação válida (POI), as suas recompensas de indexação são distribuídas ao Indexador e aos seus Delegantes ([aprenda mais](/indexing/overview/#how-are-indexing-rewards-distributed)). É ideal que os Indexadores utilizem a funcionalidade de sincronização off-chain para sincronizar lançamentos de subgraph à chainhead antes de criar a alocação on-chain. Esta ferramenta é mais útil para subgraphs que demorem mais de 28 epochs para sincronizar, ou que têm chances de falhar não-deterministicamente. diff --git a/website/pages/pt/indexing/tap.mdx b/website/pages/pt/indexing/tap.mdx index c2fefbdd9694..b69d63ceb91e 100644 --- a/website/pages/pt/indexing/tap.mdx +++ b/website/pages/pt/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notas: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/pt/resources/benefits.mdx b/website/pages/pt/resources/benefits.mdx index 934141f16a33..b632c3496de5 100644 --- a/website/pages/pt/resources/benefits.mdx +++ b/website/pages/pt/resources/benefits.mdx @@ -76,7 +76,7 @@ Os custos de query podem variar; o custo citado é o normal até o fechamento da ‡Reflete o custo ao consumidor de dados. Taxas de query ainda são pagas a Indexadores por queries do Plano Grátis. -Os custos estimados são apenas para subgraphs na Mainnet do Ethereum — os custos são maiores ao auto-hospedar um `graph-node` em outras redes. Alguns utilizadores devem atualizar o seu subgraph a uma versão mais recente. Até o fechamento deste texto, devido às taxas de gas do Ethereum, uma atualização custa cerca de 50 dólares. Note que as taxas de gás no [Arbitrum](/arbitrum/arbitrum-faq/) são muito menores que as da mainnet do Ethereum. +Os custos estimados são apenas para subgraphs na Mainnet do Ethereum — os custos são maiores ao auto-hospedar um `graph-node` em outras redes. Alguns utilizadores devem atualizar o seu subgraph a uma versão mais recente. Até o fechamento deste texto, devido às taxas de gas do Ethereum, uma atualização custa cerca de 50 dólares. Note que as taxas de gás no [Arbitrum](/archived/arbitrum/arbitrum-faq/) são muito menores que as da mainnet do Ethereum. Curar um sinal em um subgraph é um custo opcional, único, e zero-líquido (por ex., $1 mil em um subgraph pode ser curado em um subgraph, e depois retirado — com potencial para ganhar retornos no processo). @@ -90,4 +90,4 @@ A rede descentralizada do The Graph permite que os utilizadores acessem redundâ Enfim: A Graph Network é mais barata e fácil de usar, e produz resultados superiores comparados à execução local de um `graph-node`. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/pt/resources/roles/curating.mdx b/website/pages/pt/resources/roles/curating.mdx index 6c610c74825a..2e10ea729d27 100644 --- a/website/pages/pt/resources/roles/curating.mdx +++ b/website/pages/pt/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Sinais de curador são representados como tokens ERC20 chamados de Ações de Curadoria do Graph (GCS). Quem quiser ganhar mais taxas de query devem sinalizar o seu GRT a subgraphs que apostam que gerará um fluxo forte de taxas á rede. Curadores não podem ser cortados por mau comportamento, mas há uma taxa de depósito em Curadores para desincentivar más decisões que possam ferir a integridade da rede. Curadores também ganharão menos taxas de query se curarem um subgraph de baixa qualidade, já que haverão menos queries a processar ou menos Indexadores para processá-las. -O [Indexador de Atualização do Nascer do Sol](/sunrise/#what-is-the-upgrade-indexer) garante a indexação de todos os subgraphs, e que sinalizar GRT em um subgraph em particular atrairá mais Indexadores a ele. Este incentivo de Indexadores adicionais via curadoria visa melhorar a qualidade do serviço de queries ao reduzir a latência e melhorar a disponibilidade da rede. +O [Indexador de Atualização do Nascer do Sol](/archived/sunrise/#what-is-the-upgrade-indexer) garante a indexação de todos os subgraphs, e que sinalizar GRT em um subgraph em particular atrairá mais Indexadores a ele. Este incentivo de Indexadores adicionais via curadoria visa melhorar a qualidade do serviço de queries ao reduzir a latência e melhorar a disponibilidade da rede. Ao sinalizar, Curadores podem decidir entre sinalizar numa versão específica do subgraph ou sinalizar com a automigração. Caso sinalizem com a automigração, as ações de um curador sempre serão atualizadas à versão mais recente publicada pelo programador. Se decidirem sinalizar numa versão específica, as ações sempre permanecerão nesta versão específica. @@ -24,7 +24,7 @@ Os indexadores podem achar subgraphs para indexar com base em sinais de curadori ## Como Sinalizar -Dentro da aba Curator (Curador) no Graph Explorer, os curadores poderão sinalizar ou retirar os seus sinais em certos subgraphs com base nas estatísticas da rede. Para uma explicação passo a passo deste processo no Explorer, [clique aqui.](/network/explorer/) +Dentro da aba Curator (Curador) no Graph Explorer, os curadores poderão sinalizar ou retirar os seus sinais em certos subgraphs com base nas estatísticas da rede. Para uma explicação passo a passo deste processo no Explorer, [clique aqui.](/subgraphs/explorer/) Um curador pode escolher sinalizar uma versão específica de subgraph, ou pode automaticamente migrar o seu sinal à versão mais recente desse subgraph. Ambas estratégias são válidas, e vêm com as suas próprias vantagens e desvantagens. @@ -48,7 +48,7 @@ Porém, é recomendado que curadores deixem o seu GRT no lugar, não apenas para 1. O mercado de consulta é jovem por natureza no The Graph, e há sempre o risco do seu rendimento anual ser menor que o esperado devido às dinâmicas nascentes do mercado. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Um subgraph pode falhar devido a um erro de código. Um subgraph falho não acumula taxas de consulta. Portanto, espere até o programador consertar o erro e lançar uma nova versão. - Caso se inscreva à versão mais recente de um subgraph, suas ações migrarão automaticamente a esta versão nova. Isto incorrerá uma taxa de curadoria de 0.5%. - Se sinalizou em um subgraph específico e ele falhou, deverá queimar as suas ações de curadoria manualmente. Será então possível sinalizar na nova versão do subgraph, o que incorre uma taxa de curadoria de 1%. diff --git a/website/pages/pt/resources/tokenomics.mdx b/website/pages/pt/resources/tokenomics.mdx index 9b7888bda8b9..088dc04cf3a7 100644 --- a/website/pages/pt/resources/tokenomics.mdx +++ b/website/pages/pt/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - Endereço do Token GRT na Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Como fazer queries um Subgraph existente -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/pt/subgraphs/billing.mdx b/website/pages/pt/subgraphs/billing.mdx index a9694e876d05..811f36f892d0 100644 --- a/website/pages/pt/subgraphs/billing.mdx +++ b/website/pages/pt/subgraphs/billing.mdx @@ -15,7 +15,7 @@ Há dois planos disponíveis para queries de subgraphs na Graph Network. ## Pagamentos de Queries com cartão de crédito - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/billing/). + 1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Clique no botão "Connect Wallet" (Conectar Carteira) no canto superior direito da página. Isto levará à página de seleção de carteira; lá, selecione a sua carteira e clique em "Connect". 3. Escolha "atualizar plano" se está a atualizar do Plano Grátis, ou escolha "Gerir plano" se já adicionou GRT ao seu saldo de cobrança no passado. Depois, é possível estimar o número de queries para conseguir uma estimativa de preço, mas isto não é obrigatório. 4. Para escolher um pagamento em cartão de crédito, escolha "Cartão de crédito" como o método de pagamento e preencha os campos. Quem já usou o Stripe antes poderá preencher os seus detalhes automaticamente com o recurso Link. @@ -50,7 +50,7 @@ Quando fizeres bridge do GRT, será possível adicioná-lo ao seu saldo de cobra ### Depósitos de GRT com uma carteira -1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/billing/). +1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Clique no botão "Connect Wallet" (Conectar Carteira) no canto superior direito da página. Isto levará à página de seleção de carteira; lá, selecione a sua carteira e clique em "Connect". 3. Selecione o botão "Manage" (Gerir) perto do canto superior direito. Utilizadores noviços verão uma opção para "Upgrade to Growth Plan" (Atualizar para o Plano de Crescimento), enquanto os frequentes devem clicar em "Deposit from wallet" (Depositar de carteira). 4. Use o slider para estimar o número de queries que espera fazer mensalmente. @@ -67,7 +67,7 @@ Quando fizeres bridge do GRT, será possível adicioná-lo ao seu saldo de cobra ### Saques de GRT com carteira -1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/billing/). +1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Clique no botão "Connect Wallet" (Conectar Carteira) no canto superior direito da página, selecione a sua carteira e clique em "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Insira a quantia de GRT que quer sacar. @@ -76,7 +76,7 @@ Quando fizeres bridge do GRT, será possível adicioná-lo ao seu saldo de cobra ### Depósitos de GRT com uma carteira multisig -1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/billing/). +1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Clique no botão "Connect Wallet" no canto superior direito da página, selecione a sua carteira e clique em "Connect". Se usar o [Gnosis-Safe](https://gnosis-safe.io/), poderá conectar a sua multisig além da sua carteira de assinatura. Depois, assine a mensagem associada — isto não custa gas. 3. Selecione o botão "Manage" (Gerir) perto do canto superior direito. Utilizadores noviços verão uma opção para "Upgrade to Growth Plan" (Atualizar para o Plano de Crescimento), enquanto os frequentes devem clicar em "Deposit from wallet" (Depositar de carteira). 4. Use o slider para estimar o número de queries que espera fazer mensalmente. diff --git a/website/pages/pt/subgraphs/cookbook/arweave.mdx b/website/pages/pt/subgraphs/cookbook/arweave.mdx index 83781cb0165e..8853a7adee4b 100644 --- a/website/pages/pt/subgraphs/cookbook/arweave.mdx +++ b/website/pages/pt/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ A definição de Schema descreve a estrutura do banco de dados resultado do subg Os _handlers_ para eventos de processamento são escritos em [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Consultando um Subgraph no Arweave -O ponto final do GraphQL para subgraphs no Arweave é determinado pela definição do schema, com a interface existente da API. Visite a [documentação da API da GraphQL](/querying/graphql-api/) para mais informações. +O ponto final do GraphQL para subgraphs no Arweave é determinado pela definição do schema, com a interface existente da API. Visite a [documentação da API da GraphQL](/subgraphs/querying/graphql-api/) para mais informações. ## Exemplos de Subgraphs diff --git a/website/pages/pt/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/pt/subgraphs/cookbook/avoid-eth-calls.mdx index 427e3e9e669d..fd40eb79c13c 100644 --- a/website/pages/pt/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/pt/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pt/subgraphs/cookbook/cosmos.mdx b/website/pages/pt/subgraphs/cookbook/cosmos.mdx index d98ffafe1a01..7a38cef0206a 100644 --- a/website/pages/pt/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/pt/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ A definição do schema descreve a estrutura do banco de dados do subgraph resul Os handlers para o processamento de eventos são escritos em [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Consulta a um subgraph no Cosmos -O endpoint do GraphQL para subgraphs no Cosmos é determinado pela definição do schema, com a interface existente da API. Mais informações na [documentação da API GraphQL](/querying/graphql-api/). +O endpoint do GraphQL para subgraphs no Cosmos é determinado pela definição do schema, com a interface existente da API. Mais informações na [documentação da API GraphQL](/subgraphs/querying/graphql-api/). ## Apoio a Blockchains no Cosmos diff --git a/website/pages/pt/subgraphs/cookbook/derivedfrom.mdx b/website/pages/pt/subgraphs/cookbook/derivedfrom.mdx index f6f7a4e51283..21332819995b 100644 --- a/website/pages/pt/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/pt/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ Isto não só aumenta a eficiência do nosso subgraph, mas também desbloqueia t 2. Podemos fazer uma pesquisa reversa e um query sobre qualquer `Comment`, para ver de qual post ele vem. -3. Podemos usar [Carregadores de Campos Derivados](/developing/graph-ts/api/#looking-up-derived-entities) para desbloquear a habilidade de acessar e manipular diretamente dados de relacionamentos virtuais nos nossos mapeamentos de subgraph. +3. Podemos usar [Carregadores de Campos Derivados](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) para desbloquear a habilidade de acessar e manipular diretamente dados de relacionamentos virtuais nos nossos mapeamentos de subgraph. ## Conclusão @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pt/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/pt/subgraphs/cookbook/grafting-hotfix.mdx index ca17181cbf11..b09d54c13373 100644 --- a/website/pages/pt/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/pt/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Outros Recursos -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pt/subgraphs/cookbook/grafting.mdx b/website/pages/pt/subgraphs/cookbook/grafting.mdx index 6e4946384443..2110f465f014 100644 --- a/website/pages/pt/subgraphs/cookbook/grafting.mdx +++ b/website/pages/pt/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Ao aderir a estas diretrizes, dá para minimizar riscos e garantir um processo d ## Como Construir um Subgraph Existente -Construir subgraphs é essencial para o Graph; o processo é descrito em mais detalhes [aqui](/quick-start/). Para poder construir e lançar o subgraph existente usado neste tutorial, há o seguinte repo: +Construir subgraphs é essencial para o Graph; o processo é descrito em mais detalhes [aqui](/subgraphs/quick-start/). Para poder construir e lançar o subgraph existente usado neste tutorial, há o seguinte repo: - [Exemplo de repo de subgraph](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ Caso queira mais experiência com enxertos, veja alguns exemplos de contratos po Para se tornar especialista no The Graph, aprenda sobre outras maneiras de cuidar de mudanças em fontes de dados subjacentes. Alternativas como [Modelos de Fontes de Dados](/developing/creating-a-subgraph/#data-source-templates) podem dar resultados parecidos -> Nota: Grande parte do material deste artigo foi tirado do [artigo sobre o Arweave](/cookbook/arweave/) +> Nota: Grande parte do material deste artigo foi tirado do [artigo sobre o Arweave](/subgraphs/cookbook/arweave/) diff --git a/website/pages/pt/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/pt/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index b00bf3708ef3..49802e0ea200 100644 --- a/website/pages/pt/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/pt/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Leia mais sobre o uso de Entidades Imutáveis e Bytes como IDs nesta publicaçã ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pt/subgraphs/cookbook/near.mdx b/website/pages/pt/subgraphs/cookbook/near.mdx index 346056b7887c..e2fa982b8aac 100644 --- a/website/pages/pt/subgraphs/cookbook/near.mdx +++ b/website/pages/pt/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ Há três aspectos de definição de subgraph: **schema.graphql:** um arquivo schema que define quais dados são armazenados para o seu subgraph, e como consultá-los via GraphQL. Os requerimentos para subgraphs no NEAR são cobertos pela [documentação existente](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. Existem dois comandos importantes durante o desenvolvimento de um subgraph: @@ -98,7 +98,7 @@ A definição do schema descreve a estrutura do banco de dados do subgraph resul Os handlers para o processamento de eventos são escritos em [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Estes tipos são repassados para handlers de blocos e recibos: - Handlers de blocos receberão um `Block` - Handlers de recibos receberão um `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Lançando um Subgraph na NEAR @@ -228,7 +228,7 @@ Em breve, falaremos mais sobre como executar os componentes acima. ## Como Consultar um Subgraph na NEAR -O endpoint da GraphQL para subgraphs na NEAR é determinado pela definição do schema, com a interface existente da API. Mais informações na [documentação da API GraphQL](/querying/graphql-api/). +O endpoint da GraphQL para subgraphs na NEAR é determinado pela definição do schema, com a interface existente da API. Mais informações na [documentação da API GraphQL](/subgraphs/querying/graphql-api/). ## Exemplos de Subgraphs @@ -276,7 +276,7 @@ No momento, não há apoio à funcionalidade de pendências para subgraphs na NE ### A minha pergunta não foi respondida. Onde posso conseguir mais ajuda sobre construir subgraphs na NEAR? -Se esta for uma pergunta geral sobre desenvolvimento de subgraphs, há mais informações no resto da [documentação para programadores](/quick-start/). Caso contrário, entre no [Discord do Graph Protocol](https://discord.gg/graphprotocol) e pergunte no canal #near, ou mande a sua pergunta para near@thegraph.com. +Se esta for uma pergunta geral sobre desenvolvimento de subgraphs, há mais informações no resto da [documentação para programadores](/subgraphs/quick-start/). Caso contrário, entre no [Discord do Graph Protocol](https://discord.gg/graphprotocol) e pergunte no canal #near, ou mande a sua pergunta para near@thegraph.com. ## Referências diff --git a/website/pages/pt/subgraphs/cookbook/pruning.mdx b/website/pages/pt/subgraphs/cookbook/pruning.mdx index 7eb1be85ddf9..5a3d1ac12a50 100644 --- a/website/pages/pt/subgraphs/cookbook/pruning.mdx +++ b/website/pages/pt/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ O `indexerHints` tem três opções de `prune`: - `prune: auto`: Guarda o histórico mínimo necessário, conforme configurado pelo Indexador, para otimizar o desempenho dos queries. Esta é a configuração geralmente recomendada e é padrão para todos os subgraphs criados pela `graph-cli` >= 0.66.0. - `prune: `: Determina um limite personalizado no número de blocos históricos a serem retidos. -- `prune: never`: Nenhum pruning de dados históricos; guarda o histórico completo e é o padrão caso não haja uma secção `indexerHints`. O `prune: never` deve ser selecionado caso queira [Queries de Viagem no Tempo](/querying/graphql-api/#time-travel-queries). +- `prune: never`: Nenhum pruning de dados históricos; guarda o histórico completo e é o padrão caso não haja uma secção `indexerHints`. O `prune: never` deve ser selecionado caso queira [Queries de Viagem no Tempo](/subgraphs/querying/graphql-api/#time-travel-queries). Podemos adicionar `indexerHints` aos nossos subgraphs ao atualizar o nosso `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Considerações Importantes -- Se quiser fazer [Queries de Viagem no Tempo](/querying/graphql-api/#time-travel-queries) junto com pruning, o pruning deve ser realizado com precisão para manter a funcionalidade das Queries de Viagem no Tempo. Portanto, não recomendamos usar `indexerHints: prune: auto` com Queries de Viagem no Tempo. Em vez disto, use `indexerHints: prune: ` para fazer um pruning preciso até uma altura de bloco que preserve os dados históricos requeridos por Queries de Viagem no Tempo, ou use o `prune: never` para manter todos os dados. +- Se quiser fazer [Queries de Viagem no Tempo](/subgraphs/querying/graphql-api/#time-travel-queries) junto com pruning, o pruning deve ser realizado com precisão para manter a funcionalidade das Queries de Viagem no Tempo. Portanto, não recomendamos usar `indexerHints: prune: auto` com Queries de Viagem no Tempo. Em vez disto, use `indexerHints: prune: ` para fazer um pruning preciso até uma altura de bloco que preserve os dados históricos requeridos por Queries de Viagem no Tempo, ou use o `prune: never` para manter todos os dados. -- Não é possível criar [enxertos](/cookbook/grafting/) a uma altura de bloco que já tenha passado por pruning. Se enxertos forem realizados com frequência e o pruning for desejado, recomendamos usar `indexerHints: prune: ` que guardarão com precisão um número determinado de blocos (por ex., o suficiente para seis meses). +- Não é possível criar [enxertos](/subgraphs/cookbook/grafting/) a uma altura de bloco que já tenha passado por pruning. Se enxertos forem realizados com frequência e o pruning for desejado, recomendamos usar `indexerHints: prune: ` que guardarão com precisão um número determinado de blocos (por ex., o suficiente para seis meses). ## Conclusão @@ -42,14 +42,14 @@ O pruning com `indexerHints` é uma boa prática para o desenvolvimento de subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 684af3b191be..47d3866e4ec0 100644 --- a/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/pt/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Subgraphs movidos por substreams --- -[Substreams](/substreams/) é uma nova infraestrutura para o processamento de dados na blockchain, desenvolvida pela StreamingFast para a Graph Network. Um módulo de substreams pode gerar mudanças de entidade, que são compatíveis com entidades de Subgraph. Um subgraph pode usar um tal modelo de Substreams como uma fonte de dados, trazendo a velocidade de indexação e dados adicionais do Substreams aos desenvolvedores de subgraph. +[Substreams](/substreams/introduction/) é uma nova infraestrutura para o processamento de dados na blockchain, desenvolvida pela StreamingFast para a Graph Network. Um módulo de substreams pode gerar mudanças de entidade, que são compatíveis com entidades de Subgraph. Um subgraph pode usar um tal modelo de Substreams como uma fonte de dados, trazendo a velocidade de indexação e dados adicionais do Substreams aos desenvolvedores de subgraph. ## Requisitos @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Como definir um pacote de Substreams -Um pacote de Substreams é composto de tipos (definidos como [Protocol Buffers](https://protobuf.dev/)), módulos (escritos em Rust), e um arquivo `substreams.yaml` que referencia os tipos, e especifica como os módulos são ativados. [Visite a documentação de Substreams para aprender mais sobre o desenvolvimento de Substreams](/substreams/), e confira o [awesome-substreams](https://github.com/pinax-network/awesome-substreams) e o [manual de Substreams](https://github.com/pinax-network/substreams-cookbook) para mais exemplos. +Um pacote de Substreams é composto de tipos (definidos como [Protocol Buffers](https://protobuf.dev/)), módulos (escritos em Rust), e um arquivo `substreams.yaml` que referencia os tipos, e especifica como os módulos são ativados. [Visite a documentação de Substreams para aprender mais sobre o desenvolvimento de Substreams](/substreams/introduction/), e confira o [awesome-substreams](https://github.com/pinax-network/awesome-substreams) e o [manual de Substreams](https://github.com/pinax-network/substreams-cookbook) para mais exemplos. O pacote de Substreams em questão deteta publicações de contratos na Mainnet do Ethereum, com rastreio do bloco de criação e horas para todos os contratos recém-lançados. Para fazer isto, há um tipo dedicado de `Contrato` no `/proto/example.proto` ([aprenda mais sobre a definição de Buffers de Protocolo](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/pt/subgraphs/cookbook/timeseries.mdx b/website/pages/pt/subgraphs/cookbook/timeseries.mdx index d6362da8dda1..9c2a8632c5b6 100644 --- a/website/pages/pt/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/pt/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/pt/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/pt/subgraphs/cookbook/transfer-to-the-graph.mdx index 7d0d8cda34c4..0a0bac2dbc06 100644 --- a/website/pages/pt/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/pt/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Exemplo @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Outros Recursos -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/pt/subgraphs/developing/creating/advanced.mdx b/website/pages/pt/subgraphs/developing/creating/advanced.mdx index a46badf10977..fc407f4281c0 100644 --- a/website/pages/pt/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/pt/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Se o relacionamento for perfeitamente proporcional entre a entidade parente e a entidade de fontes de dados de arquivos resultante, é mais simples ligar a entidade parente a uma entidade de arquivos resultante, com a CID IPFS como o assunto de busca. Se tiver dificuldades em modelar suas novas entidades baseadas em arquivos, pergunte no Discord! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### Criar um novo handler para processar arquivos -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Além disto, não é possível criar fontes de dados de uma fonte de dado de arq Caso ligue metadados de NFTs a tokens correspondentes, use o hash IPFS destes para referenciar uma entidade de Metadados da entidade do Token. Salve a entidade de Metadados a usar o hash IPFS como ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Como Enxertar em Subgraphs Existentes -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx index 7a8824c97c1c..a7521399250e 100644 --- a/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/pt/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: API AssemblyScript --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ No manifest do subgraph, `apiVersion` especifica a versão da API de mapeamento, | 0.0.8 | Adiciona validação para existência de campos no schema ao salvar uma entidade. | | 0.0.7 | Classes `TransactionReceipt` e `Log` adicionadas aos tipos do EthereumCampo
Campo `receipt` adicionado ao objeto Ethereum Event | | 0.0.6 | Campo `nonce` adicionado ao objeto Ethereum TransactionCampo
`baseFeePerGas` adicionado ao objeto Ethereum Block | -| 0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` | | 0.0.4 | Campo `functionSignature` adicionado ao objeto Ethereum SmartContractCall | | 0.0.3 | Campo `from` adicionado ao objeto Ethereum
`Calletherem.call.address` renomeado para `ethereum.call.to` | | 0.0.2 | Campo `input` adicionado ao objeto Ethereum Transaction | diff --git a/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx index 5a1bf2c57245..eda8ead451ae 100644 --- a/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/pt/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Como instalar o Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Visão geral -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Como Começar @@ -114,6 +114,6 @@ Os arquivos da ABI devem combinar com o(s) seu(s) contrato(s). Há algumas manei | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Adicionado apoio a handlers de eventos com acesso a recibos de transação. | | 0.0.4 | Adicionado apoio à gestão de recursos de subgraph. | diff --git a/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx b/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx index a0909930982a..5a2888544ea1 100644 --- a/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/pt/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/pt/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/pt/subgraphs/developing/creating/starting-your-subgraph.mdx index 5d89cfb2fb27..46190164b8a5 100644 --- a/website/pages/pt/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/pt/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/pt/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/pt/subgraphs/developing/creating/subgraph-manifest.mdx index e56c0a59dba8..fdd7f1cba98e 100644 --- a/website/pages/pt/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/pt/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). As entradas importantes para atualizar para o manifest são: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde O histórico, desde um bloco especificado, é necessário para: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rebobinar o subgraph de volta àquele bloco @@ -517,7 +517,7 @@ Se os dados históricos desde aquele bloco tiverem passado por pruning, as capac > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: Para reter uma quantidade específica de dados históricos: diff --git a/website/pages/pt/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/pt/subgraphs/developing/creating/unit-testing-framework.mdx index 68acc7e892b9..2f12939198a4 100644 --- a/website/pages/pt/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/pt/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1378,7 +1378,7 @@ A saída do log inclui a duração do teste. Veja um exemplo: > `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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > `ERROR TS2554: Expected ? arguments, but got ?.` > diff --git a/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx index b25acabaaee8..2ab13dd167ee 100644 --- a/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/pt/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### Compatibilidade de Subgraph com a Graph Network Para ter apoio de Indexadores na Graph Network, os subgraphs devem: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - Não deve usar quaisquer das seguintes características: - ipfs.cat & ipfs.map - Erros não-fatais @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Arquivamento Automático de Versões de Subgraphs diff --git a/website/pages/pt/subgraphs/developing/developer-faq.mdx b/website/pages/pt/subgraphs/developing/developer-faq.mdx index 39aa8d332e6e..36d4325f4fd2 100644 --- a/website/pages/pt/subgraphs/developing/developer-faq.mdx +++ b/website/pages/pt/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ Deve relançar o subgraph, mas se a ID do subgraph (hash IPFS) não mudar, ele n ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Confira o estado `Access to smart contract` dentro da seção [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Confira o estado `Access to smart contract` dentro da seção [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ Se só uma entidade for criada durante o evento e não houver nada melhor dispon ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -Veja a lista das redes apoiadas [aqui](/developing/supported-networks/). +Veja a lista das redes apoiadas [aqui](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/pt/subgraphs/developing/introduction.mdx b/website/pages/pt/subgraphs/developing/introduction.mdx index 815de9d39c85..ddf26f28f05d 100644 --- a/website/pages/pt/subgraphs/developing/introduction.mdx +++ b/website/pages/pt/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Programação --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Visão geral @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx index e39eddc376eb..5e1722875259 100644 --- a/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/pt/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Após [lançar o seu subgraph ao Subgraph Studio](/deploying/deploying-a-subgrap Ao editar um subgraph à rede descentralizada, ele será disponibilizado para: -- Curadoria por [Curadores](/network/curating/). -- Indexação por [Indexadores](/network/indexing/). +- Curadoria por [Curadores](/resources/roles/curating/). +- Indexação por [Indexadores](/indexing/overview/). -Confira a lista de [redes apoiadas](/developing/supported-networks/). +Confira a lista de [redes apoiadas](/supported-networks/). ## Edição do Subgraph Studio @@ -21,9 +21,9 @@ Confira a lista de [redes apoiadas](/developing/supported-networks/). Todas as versões editadas de um subgraph existente podem: -- Ser editadas ao Arbitrum One. [Aprenda mais sobre a Graph Network no Arbitrum](/arbitrum/arbitrum-faq/). +- Ser editadas ao Arbitrum One. [Aprenda mais sobre a Graph Network no Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Indexar dados em quaisquer das [redes apoiadas](/developing/supported-networks/), independente da rede na qual o subgraph foi editado. +- Indexar dados em quaisquer das [redes apoiadas](/supported-networks/), independente da rede na qual o subgraph foi editado. ### Como atualizar metadados para um subgraph editado @@ -69,13 +69,13 @@ Programadores podem adicionar sinal de GRT aos seus subgraphs para incentivar In - É possível conferir a elegibilidade a recompensas de indexação com base no uso de ferramentas de subgraph [aqui](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Redes apoiadas específicas podem ser conferidas [aqui](/developing/supported-networks/). +- Redes apoiadas específicas podem ser conferidas [aqui](/supported-networks/). > Adicionar sinais a um subgraph que não for elegível não atrairá mais Indexadores. > Se o seu subgraph for elegível a recompensas, recomendamos que cure o seu próprio subgraph com, no mínimo, 3000 GRT para atrair mais Indexadores ao seu subgraph. -O [Indexador de Atualização do Nascer do Sol](/sunrise/#what-is-the-upgrade-indexer) garante a indexação de todos os subgraphs. No entanto, sinalizar GRT em um subgraph em particular atrairá mais Indexadores a ele. Este incentivo de Indexadores adicionais via curadoria visa melhorar a qualidade do serviço de queries ao reduzir a latência e melhorar a disponibilidade da rede. +O [Indexador de Atualização do Nascer do Sol](/archived/sunrise/#what-is-the-upgrade-indexer) garante a indexação de todos os subgraphs. No entanto, sinalizar GRT em um subgraph em particular atrairá mais Indexadores a ele. Este incentivo de Indexadores adicionais via curadoria visa melhorar a qualidade do serviço de queries ao reduzir a latência e melhorar a disponibilidade da rede. Ao sinalizar, Curadores podem decidir entre sinalizar numa versão específica do subgraph ou sinalizar com a automigração. Caso sinalizem com a automigração, as ações de um curador sempre serão atualizadas à versão mais recente publicada pelo programador. Se decidirem sinalizar numa versão específica, as ações sempre permanecerão nesta versão específica. @@ -91,4 +91,4 @@ Como alternativa, é possível adicionar sinais em GRT a um subgraph editado a p ![Sinal do Explorer](/img/signal-from-explorer.png) -Saiba mais sobre [Curadoria](/network/curating/) na Graph Network. +Saiba mais sobre [Curadoria](/resources/roles/curating/) na Graph Network. diff --git a/website/pages/pt/subgraphs/developing/subgraphs.mdx b/website/pages/pt/subgraphs/developing/subgraphs.mdx index 5ca8d4007ec4..9adf88b8c22a 100644 --- a/website/pages/pt/subgraphs/developing/subgraphs.mdx +++ b/website/pages/pt/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/pt/subgraphs/explorer.mdx b/website/pages/pt/subgraphs/explorer.mdx index 43409fd827bb..c25a55a59450 100644 --- a/website/pages/pt/subgraphs/explorer.mdx +++ b/website/pages/pt/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Para aprender mais sobre como tornar-se um Indexador, pode conferir a [documentação oficial](/network/indexing/) ou [os guias de Indexador da Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) +Para aprender mais sobre como tornar-se um Indexador, pode conferir a [documentação oficial](/indexing/overview/) ou [os guias de Indexador da Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) ![Painel de detalhes de indexação](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Imagem do Explorer 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegantes @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - A quantidade total de GRT que têm no protocolo no momento - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Rede diff --git a/website/pages/pt/subgraphs/querying/best-practices.mdx b/website/pages/pt/subgraphs/querying/best-practices.mdx index eb77bb132e9c..d6c2e17febbc 100644 --- a/website/pages/pt/subgraphs/querying/best-practices.mdx +++ b/website/pages/pt/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Cada `queryName` deve ser usado apenas uma vez por operação. - Cada `field` deve ser usado apenas uma vez numa seleção (não podemos consultar a `id` duas vezes sob o `token`) -- Alguns `fields`s ou queries (como `tokens`) retornam tipos complexos que requerem uma seleção de subcampo. Não providenciar uma seleção quando esperado (ou providenciar uma quando não é esperado - por exemplo, no `id`) resultará num erro. Para conhecer um tipo de campo, consulte o [Graph Explorer](/network/explorer/). +- Alguns `fields`s ou queries (como `tokens`) retornam tipos complexos que requerem uma seleção de subcampo. Não providenciar uma seleção quando esperado (ou providenciar uma quando não é esperado - por exemplo, no `id`) resultará num erro. Para conhecer um tipo de campo, consulte o [Graph Explorer](/subgraphs/explorer/). - Qualquer variável apontada a um argumento deve corresponder ao seu tipo. - Em uma lista dada de variáveis, cada uma delas deve ser única. - Todas as variáveis definidas devem ser usadas. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Como enviar um query a uma API GraphQL @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Gestão de Subgraph Cross-chain: Queries de múltiplos subgraphs numa única consulta - [Rastreamento Automático de Blocos](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/pt/subgraphs/querying/graphql-api.mdx b/website/pages/pt/subgraphs/querying/graphql-api.mdx index 274f93e3c81f..bdded48af037 100644 --- a/website/pages/pt/subgraphs/querying/graphql-api.mdx +++ b/website/pages/pt/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/pt/subgraphs/querying/introduction.mdx b/website/pages/pt/subgraphs/querying/introduction.mdx index fddfd118b38c..2a043b275e22 100644 --- a/website/pages/pt/subgraphs/querying/introduction.mdx +++ b/website/pages/pt/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Queries no The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Por favor, confira a [API de Queries](/querying/graphql-api/) para uma referência completa em como fazer queries das entidades do subgraph. É possível ler sobre as melhores práticas de querying em GraphQL [aqui](/querying/querying-best-practices/) +> Por favor, confira a [API de Queries](/subgraphs/querying/graphql-api/) para uma referência completa em como fazer queries das entidades do subgraph. É possível ler sobre as melhores práticas de querying em GraphQL [aqui](/subgraphs/querying/best-practices/) > Nota: Se encontrar erros 405 com um pedido GET ao URL do Graph Explorer, use um pedido POST. @@ -14,8 +14,8 @@ Cada subgraph publicado à Graph Network tem um URL singular de query no Graph E ![Query Subgraph URL](/img/query-url-screenshot.png) -Aprenda mais sobre queries de um aplicativo [aqui](/querying/querying-from-an-application/). +Aprenda mais sobre queries de um aplicativo [aqui](/subgraphs/querying/from-an-application/). Como deve ter percebido, este URL de query deve usar uma chave de API singular. Dá para criar e gerir as suas chaves de API no [Subgraph Studio](https://thegraph.com/studio), na seção "API Keys". Leia mais sobre como usar o Subgraph Studio [aqui](/deploying/subgraph-studio/). -Utilizadores do Subgraph Studio começam com um Plano Grátis, que os permite realizar 100 mil queries por mês. Mais queries estão disponíveis no Plano de Crescimento, que oferece preços baseados em uso para queries adicionais; estes podem ser pagos em cartão de crédito ou em GRT no Arbitrum. Aprenda mais sobre cobranças [aqui](/billing/). +Utilizadores do Subgraph Studio começam com um Plano Grátis, que os permite realizar 100 mil queries por mês. Mais queries estão disponíveis no Plano de Crescimento, que oferece preços baseados em uso para queries adicionais; estes podem ser pagos em cartão de crédito ou em GRT no Arbitrum. Aprenda mais sobre cobranças [aqui](/subgraphs/billing/). diff --git a/website/pages/pt/subgraphs/quick-start.mdx b/website/pages/pt/subgraphs/quick-start.mdx index b84ba0083d5f..7a98b37dc814 100644 --- a/website/pages/pt/subgraphs/quick-start.mdx +++ b/website/pages/pt/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Começo Rápido --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Pré-requisitos - Uma carteira de criptomoedas -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Como adicionar sinal ao seu subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/pt/substreams/sps/sps-faq.mdx b/website/pages/pt/substreams/sps/sps-faq.mdx index ffa5233d7b61..cae95563a993 100644 --- a/website/pages/pt/substreams/sps/sps-faq.mdx +++ b/website/pages/pt/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Perguntas frequentes sobre subgraphs movidos por substreams Desenvolvido pela [StreamingFast](https://www.streamingfast.io/), o Substreams é um motor de processamento de poder excepcional, capaz de consumir fluxos ricos de dados em blockchain. O Substreams lhe permite refinar e moldar dados em blockchain para serem digeridos rápida e suavemente por aplicativos de utilizador final. Mais especificamente, o Substreams é um motor paralelizado e agnóstico a blockchains, que põe transmissões em primeiro lugar e serve como uma camada de transformação de dados em blockchain. Movido pelo [Firehose](https://firehose.streamingfast.io/), ele permite que programadores escrevam módulos em Rust, construam sobre módulos da comunidade, providenciem indexações de altíssimo desempenho, e mandar seus dados para qualquer destino com [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink). -Vá à [Documentação do Substreams](/substreams/) para aprender mais sobre Substreams. +Vá à [Documentação do Substreams](/substreams/introduction/) para aprender mais sobre Substreams. ## O que são subgraphs movidos por substreams? -[Subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) combinam o poder do Substreams com a consultabilidade de subgraphs. Ao publicar um subgraph movido a Substreams, os dados produzidos pelas transformações no Substreams podem [resultar em mudanças de entidade](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), que são compatíveis com entidades no subgraph. +[Subgraphs movidos a Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/) combinam o poder do Substreams com a consultabilidade de subgraphs. Ao publicar um subgraph movido a Substreams, os dados produzidos pelas transformações no Substreams podem [resultar em mudanças de entidade](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), que são compatíveis com entidades no subgraph. Se você já for familiar com a programação de subgraphs, então note que subgraphs movidos a Substreams podem ser consultados do mesmo jeito que se tivessem sido produzidos pela camada de transformação em AssemblyScript, com todos os benefícios do Subgraph, como a providência de uma API GraphQL dinâmica e flexível. @@ -62,9 +62,9 @@ Há muitos benefícios do uso do Firehose, que incluem: ## Onde programadores podem acessar mais informações sobre Substreams e subgraphs movidos a Substreams? -A [documentação do Substreams](/substreams/) lhe ensinará como construir módulos do Substreams. +A [documentação do Substreams](/substreams/introduction/) lhe ensinará como construir módulos do Substreams. -A [documentação de subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) lhe ensinará como empacotá-los para a publicação no The Graph. +A [documentação de subgraphs movidos a Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/) lhe ensinará como empacotá-los para a publicação no The Graph. A [ferramenta de Codegen no Substreams mais recente](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) permitirá ao programador inicializar um projeto no Substreams sem a necessidade de código. @@ -82,7 +82,7 @@ Como exemplo, Fulana pode construir um módulo de preço de DEX, Sicrano pode us ## Como construir e publicar um Subgraph movido a Substreams? -(/cookbook/substreams-powered-subgraphs/) um Subgraph movido a Substreams, é possível usar o Graph CLI para publicá lo no [Subgraph Studio](https://thegraph.com/studio/). +(/subgraphs/cookbook/substreams-powered-subgraphs/) um Subgraph movido a Substreams, é possível usar o Graph CLI para publicá lo no [Subgraph Studio](https://thegraph.com/studio/). ## Onde posso encontrar exemplos de Substreams e subgraphs movidos a Substreams? diff --git a/website/pages/pt/supported-networks.mdx b/website/pages/pt/supported-networks.mdx index b47490b02a0c..e023c2befe99 100644 --- a/website/pages/pt/supported-networks.mdx +++ b/website/pages/pt/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Apoio à rede base providenciado pelo [Indexador de atualização](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integração com o Graph Node: `evm`, `near`, `cosmos`, `osmosis` e `ar` têm apoio nativo a handlers e tipos no Graph Node. Chains compatíveis com Firehose e Substreams podem utilizar a integração generalizada de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) (isto inclui as redes `evm` e `near`). ⁠† apoia o lançamento de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/). +\*\* Integração com o Graph Node: `evm`, `near`, `cosmos`, `osmosis` e `ar` têm apoio nativo a handlers e tipos no Graph Node. Chains compatíveis com Firehose e Substreams podem utilizar a integração generalizada de [subgraphs movidos a Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/) (isto inclui as redes `evm` e `near`). ⁠† apoia o lançamento de [subgraphs movidos a Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/). - O Subgraph Studio depende da estabilidade e da confiança das tecnologias subjacentes, por exemplo, JSON-RPC, Firehose e endpoints dos Substreams. - Subgraphs que indexam a Gnosis Chain agora podem ser lançados com a identificadora de rede `gnosis`. diff --git a/website/pages/ro/about.mdx b/website/pages/ro/about.mdx index ad19563a31d2..25c810045af0 100644 --- a/website/pages/ro/about.mdx +++ b/website/pages/ro/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/ro/archived/arbitrum/arbitrum-faq.mdx b/website/pages/ro/archived/arbitrum/arbitrum-faq.mdx index 9c12c8816259..562824e64e95 100644 --- a/website/pages/ro/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/ro/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx index b075b7548fb8..8e6da852a01c 100644 --- a/website/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/ro/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx index e516573fd4d9..485f34a70c97 100644 --- a/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ro/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/ro/archived/sunrise.mdx b/website/pages/ro/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/ro/archived/sunrise.mdx +++ b/website/pages/ro/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ro/contracts.mdx b/website/pages/ro/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/ro/contracts.mdx +++ b/website/pages/ro/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ro/indexing/chain-integration-overview.mdx b/website/pages/ro/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/ro/indexing/chain-integration-overview.mdx +++ b/website/pages/ro/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/ro/indexing/new-chain-integration.mdx b/website/pages/ro/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/ro/indexing/new-chain-integration.mdx +++ b/website/pages/ro/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ro/indexing/overview.mdx b/website/pages/ro/indexing/overview.mdx index c05c37a275ef..34a60d456cfc 100644 --- a/website/pages/ro/indexing/overview.mdx +++ b/website/pages/ro/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/ro/indexing/tap.mdx b/website/pages/ro/indexing/tap.mdx index 3e8185186982..4132216ca5b6 100644 --- a/website/pages/ro/indexing/tap.mdx +++ b/website/pages/ro/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/ro/resources/benefits.mdx b/website/pages/ro/resources/benefits.mdx index 044853e8850b..d0a0e2675280 100644 --- a/website/pages/ro/resources/benefits.mdx +++ b/website/pages/ro/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/ro/resources/roles/curating.mdx b/website/pages/ro/resources/roles/curating.mdx index a3b96ed010fe..6ddf8e91099c 100644 --- a/website/pages/ro/resources/roles/curating.mdx +++ b/website/pages/ro/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ro/resources/tokenomics.mdx b/website/pages/ro/resources/tokenomics.mdx index e2e4c904000d..73a1adda922b 100644 --- a/website/pages/ro/resources/tokenomics.mdx +++ b/website/pages/ro/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/ro/subgraphs/billing.mdx b/website/pages/ro/subgraphs/billing.mdx index dec5cfdadc12..f3f52bbf35ee 100644 --- a/website/pages/ro/subgraphs/billing.mdx +++ b/website/pages/ro/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/ro/subgraphs/cookbook/arweave.mdx b/website/pages/ro/subgraphs/cookbook/arweave.mdx index 4c35f4ee8e2e..2098d5ab5932 100644 --- a/website/pages/ro/subgraphs/cookbook/arweave.mdx +++ b/website/pages/ro/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/ro/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/ro/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/ro/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/ro/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ro/subgraphs/cookbook/cosmos.mdx b/website/pages/ro/subgraphs/cookbook/cosmos.mdx index cd23a3742f86..dddfbff521d0 100644 --- a/website/pages/ro/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/ro/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/ro/subgraphs/cookbook/derivedfrom.mdx b/website/pages/ro/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/ro/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/ro/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ro/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/ro/subgraphs/cookbook/grafting-hotfix.mdx index 040e3a8209d5..a0bd3f4ab1c2 100644 --- a/website/pages/ro/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/ro/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ro/subgraphs/cookbook/grafting.mdx b/website/pages/ro/subgraphs/cookbook/grafting.mdx index 7aa79c7e2755..57d5169830a7 100644 --- a/website/pages/ro/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ro/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/ro/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ro/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/ro/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/ro/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ro/subgraphs/cookbook/near.mdx b/website/pages/ro/subgraphs/cookbook/near.mdx index cc0bf8637bee..23a936406e7b 100644 --- a/website/pages/ro/subgraphs/cookbook/near.mdx +++ b/website/pages/ro/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/ro/subgraphs/cookbook/pruning.mdx b/website/pages/ro/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/ro/subgraphs/cookbook/pruning.mdx +++ b/website/pages/ro/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ro/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ro/subgraphs/cookbook/timeseries.mdx b/website/pages/ro/subgraphs/cookbook/timeseries.mdx index 2ce0ce266ccf..0168be53d7ed 100644 --- a/website/pages/ro/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/ro/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ro/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/ro/subgraphs/cookbook/transfer-to-the-graph.mdx index 6a5d2c2793f3..64c225442860 100644 --- a/website/pages/ro/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/ro/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/ro/subgraphs/developing/creating/advanced.mdx b/website/pages/ro/subgraphs/developing/creating/advanced.mdx index 3a08ddab7066..bc3a9a86efb6 100644 --- a/website/pages/ro/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/ro/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx index 8aa0bf0027bf..4c5ce57993f2 100644 --- a/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ro/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx index 20748328de9e..a60f181e9a50 100644 --- a/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ro/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ro/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ro/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/ro/subgraphs/developing/creating/starting-your-subgraph.mdx index 5127f01632aa..f463ca3e9507 100644 --- a/website/pages/ro/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/ro/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/ro/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/ro/subgraphs/developing/creating/subgraph-manifest.mdx index f282f3946e75..b4c0e467c780 100644 --- a/website/pages/ro/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/ro/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/ro/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/ro/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/ro/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/ro/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx index 3c6f62194eed..740551c03102 100644 --- a/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ro/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/ro/subgraphs/developing/developer-faq.mdx b/website/pages/ro/subgraphs/developing/developer-faq.mdx index 2282091fde23..45b99b086165 100644 --- a/website/pages/ro/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ro/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/ro/subgraphs/developing/introduction.mdx b/website/pages/ro/subgraphs/developing/introduction.mdx index 6ba33f6d916c..45cefaff16ef 100644 --- a/website/pages/ro/subgraphs/developing/introduction.mdx +++ b/website/pages/ro/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 4728db3eb245..e75e3b13d89e 100644 --- a/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ro/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/ro/subgraphs/developing/subgraphs.mdx b/website/pages/ro/subgraphs/developing/subgraphs.mdx index 42c1e806f822..e30b77cec1ae 100644 --- a/website/pages/ro/subgraphs/developing/subgraphs.mdx +++ b/website/pages/ro/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/ro/subgraphs/explorer.mdx b/website/pages/ro/subgraphs/explorer.mdx index d874f80f5140..433821560d85 100644 --- a/website/pages/ro/subgraphs/explorer.mdx +++ b/website/pages/ro/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/ro/subgraphs/querying/best-practices.mdx b/website/pages/ro/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/ro/subgraphs/querying/best-practices.mdx +++ b/website/pages/ro/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/ro/subgraphs/querying/graphql-api.mdx b/website/pages/ro/subgraphs/querying/graphql-api.mdx index 917fad3f2406..8813e2eeb3f3 100644 --- a/website/pages/ro/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ro/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/ro/subgraphs/querying/introduction.mdx b/website/pages/ro/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/ro/subgraphs/querying/introduction.mdx +++ b/website/pages/ro/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/ro/subgraphs/quick-start.mdx b/website/pages/ro/subgraphs/quick-start.mdx index 429d4d51116f..13af8f0deb42 100644 --- a/website/pages/ro/subgraphs/quick-start.mdx +++ b/website/pages/ro/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Quick Start --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/ro/substreams/sps/sps-faq.mdx b/website/pages/ro/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/ro/substreams/sps/sps-faq.mdx +++ b/website/pages/ro/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/ro/supported-networks.mdx b/website/pages/ro/supported-networks.mdx index afeef5f62b9e..3a3c1d44fed6 100644 --- a/website/pages/ro/supported-networks.mdx +++ b/website/pages/ro/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ru/about.mdx b/website/pages/ru/about.mdx index ed071feb2124..6aa90fdbc628 100644 --- a/website/pages/ru/about.mdx +++ b/website/pages/ru/about.mdx @@ -24,7 +24,7 @@ The Graph — это мощный децентрализованный прот Децентрализованному приложению (dapp), запущенному в браузере, потребуются **часы или даже дни**, чтобы получить ответ на эти простые вопросы. -В качестве альтернативы у Вас есть возможность настроить собственный сервер, обрабатывать транзакции, хранить их в базе данных и создать конечную точку API для запроса данных. Однако этот вариант [ресурсоемок](/network/benefits/), требует обслуживания, представляет собой единственную возможную причину сбоя и нарушает важные свойства безопасности, необходимые для децентрализации. +В качестве альтернативы у Вас есть возможность настроить собственный сервер, обрабатывать транзакции, хранить их в базе данных и создать конечную точку API для запроса данных. Однако этот вариант [ресурсоемок](/resources/benefits/), требует обслуживания, представляет собой единственную возможную причину сбоя и нарушает важные свойства безопасности, необходимые для децентрализации. Такие свойства блокчейна, как окончательность, реорганизация чейна и необработанные блоки, усложняют процесс, делая получение точных результатов запроса из данных блокчейна трудоемким и концептуально сложным. diff --git a/website/pages/ru/archived/arbitrum/arbitrum-faq.mdx b/website/pages/ru/archived/arbitrum/arbitrum-faq.mdx index 72bc0949212c..7449536ed55e 100644 --- a/website/pages/ru/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/ru/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ title: Часто задаваемые вопросы об Arbitrum ## Что мне нужно делать сейчас как разработчику субграфа, потребителю данных, индексатору, куратору или делегатору? -Участники сети должны перейти на Arbitrum, чтобы продолжить участие в The Graph Network. Пожалуйста, обратитесь к [Руководству по инструменту переноса на L2](/arbitrum/l2-transfer-tools-guide/) для получения дополнительной помощи. +Участники сети должны перейти на Arbitrum, чтобы продолжить участие в The Graph Network. Пожалуйста, обратитесь к [Руководству по инструменту переноса на L2](/archived/arbitrum/l2-transfer-tools-guide/) для получения дополнительной помощи. Все вознаграждения за индексацию теперь полностью находятся на Arbitrum. @@ -77,4 +77,4 @@ title: Часто задаваемые вопросы об Arbitrum Добавление GRT к Вашему балансу для оплаты на Arbitrum можно выполнить в один клик в [Subgraph Studio](https://thegraph.com/studio/). Вы сможете легко перенести свои GRT на Arbitrum и ввести свои API-ключи в одной транзакции. -Посетите страницу [Billing page](/billing/) для получения более подробных инструкций по добавлению, выводу или приобретению GRT. +Посетите страницу [Billing page](/subgraphs/billing/) для получения более подробных инструкций по добавлению, выводу или приобретению GRT. diff --git a/website/pages/ru/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ru/archived/arbitrum/l2-transfer-tools-faq.mdx index 5438a5afc85a..4d1ce73ed620 100644 --- a/website/pages/ru/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/ru/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ The Graph удешевил участие контрибьюторов в сет ### Могу ли я использовать тот же кошелек, что и в основной сети Ethereum? -Если Вы используете кошелек [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), Вы можете использовать тот же адрес. Если Ваш кошелек основной сети Ethereum является контрактным (например, кошелек с мультиподписью), то Вы должны указать адрес [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2), на который будет отправлен Ваш перевод. Пожалуйста, внимательно проверяйте адрес, так как перевод на неправильный адрес может привести к необратимой потере средств. Если Вы хотите использовать кошелек с мультиподписью на L2, убедитесь, что развернули multisig-контракт на Arbitrum One. +Если Вы используете кошелек [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account), Вы можете использовать тот же адрес. Если Ваш кошелек основной сети Ethereum является контрактным (например, кошелек с мультиподписью), то Вы должны указать адрес [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2), на который будет отправлен Ваш перевод. Пожалуйста, внимательно проверяйте адрес, так как перевод на неправильный адрес может привести к необратимой потере средств. Если Вы хотите использовать кошелек с мультиподписью на L2, убедитесь, что развернули multisig-контракт на Arbitrum One. Кошельки на блокчейнах EVM, таких как Ethereum и Arbitrum, представляют собой пару ключей (публичный и приватный), которые Вы создаете без необходимости взаимодействия с блокчейном. Таким образом, любой кошелек, созданный для Ethereum, также будет работать на Arbitrum без необходимости выполнения дополнительных действий. diff --git a/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx index 0ce4b2c48f21..7733cf60b324 100644 --- a/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ru/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Руководство по инструментам переноса L2 The Graph упростил переход на L2 в Arbitrum One. Для каждого участника протокола существует набор инструментов переноса L2, чтобы сделать переход на L2 бесшовным для всех участников сети. Эти инструменты потребуют от Вас выполнения определенного набора шагов в зависимости от того, что Вы передаете. -Ответы на некоторые частые вопросы об этих инструментах можно найти в [Часто задаваемые вопросы по инструментам переноса L2](/arbitrum/l2-transfer-tools-faq/). Часто задаваемые вопросы содержат подробные объяснения того, как использовать инструменты, как они работают и что следует учитывать при их использовании. +Ответы на некоторые частые вопросы об этих инструментах можно найти в [Часто задаваемые вопросы по инструментам переноса L2](/archived/arbitrum/l2-transfer-tools-faq/). Часто задаваемые вопросы содержат подробные объяснения того, как использовать инструменты, как они работают и что следует учитывать при их использовании. ## Как перенести свой субграф в Arbitrum (L2) diff --git a/website/pages/ru/archived/sunrise.mdx b/website/pages/ru/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/ru/archived/sunrise.mdx +++ b/website/pages/ru/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ru/contracts.mdx b/website/pages/ru/contracts.mdx index 3b049e1bf499..f4baf22afafd 100644 --- a/website/pages/ru/contracts.mdx +++ b/website/pages/ru/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ru/indexing/chain-integration-overview.mdx b/website/pages/ru/indexing/chain-integration-overview.mdx index 46dccce2a11a..cb7944b336ae 100644 --- a/website/pages/ru/indexing/chain-integration-overview.mdx +++ b/website/pages/ru/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: Chain Integration Process Overview ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/ru/indexing/new-chain-integration.mdx b/website/pages/ru/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/ru/indexing/new-chain-integration.mdx +++ b/website/pages/ru/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ru/indexing/overview.mdx b/website/pages/ru/indexing/overview.mdx index 445222da6b05..fe6cdb8e4b7e 100644 --- a/website/pages/ru/indexing/overview.mdx +++ b/website/pages/ru/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### Что такое query fee cut и indexing reward cut? -Значения `queryFeeCut` и `indexingRewardCut` — это параметры делегирования, которые индексатор может установить вместе с cooldownBlocks для управления распределением GRT между индексатором и его делегаторами. См. последние шаги в разделе [Стейкинг в протоколе](/network/indexing/#stake-in-the-protocol), чтобы получить инструкции по настройке параметров делегирования. +Значения `queryFeeCut` и `indexingRewardCut` — это параметры делегирования, которые индексатор может установить вместе с cooldownBlocks для управления распределением GRT между индексатором и его делегаторами. См. последние шаги в разделе [Стейкинг в протоколе](/indexing/overview/#stake-in-the-protocol), чтобы получить инструкции по настройке параметров делегирования. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### Какие основные меры безопасности следует предпринять индексатору? -- **Operator wallet**. Настройка кошелька оператора является важной мерой безопасности, поскольку она позволяет индексатору поддерживать разделение между своими ключами, которые контролируют величину стейка, и теми, которые контролируют ежедневные операции. Инструкции см. в разделе [Stake in Protocol](/network/indexing/#stake-in-the-protocol). +- **Operator wallet**. Настройка кошелька оператора является важной мерой безопасности, поскольку она позволяет индексатору поддерживать разделение между своими ключами, которые контролируют величину стейка, и теми, которые контролируют ежедневные операции. Инструкции см. в разделе [Stake in Protocol](/indexing/overview/#stake-in-the-protocol). - **Firewall**. Только служба индексатора должна быть общедоступной, и особое внимание следует уделить блокировке портов администратора и доступа к базе данных: эндпоинт ноды The Graph JSON-RPC (порт по умолчанию: 8030), API эндпоинт для управления индексатором (порт по умолчанию: 18000) и эндпоинт базы данных Postgres (порт по умолчанию: 5432) не должны быть доступны. @@ -375,7 +375,7 @@ docker-compose up #### Начало работы -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### Из пакетов NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Использование K8s и Terraform -См. раздел [Настройка инфраструктуры сервера с помощью Terraform в Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +См. раздел [Настройка инфраструктуры сервера с помощью Terraform в Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Применение @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -После того как индексатор застейкал GRT в протоколе, можно запустить [Indexer components](/network/indexing/#indexer-components) и начать взаимодействие с сетью. +После того как индексатор застейкал GRT в протоколе, можно запустить [Indexer components](/indexing/overview/#indexer-components) и начать взаимодействие с сетью. #### Подтверждение токенов @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Индексаторам рекомендуется использовать функцию синхронизации вне сети для синхронизации развертывания подграфов в chainhead перед созданием аллокации в сети. Эта функция особенно полезна для подграфов, синхронизация которых может занять более 28 эпох или имеющих некоторую вероятность неопределенного сбоя. diff --git a/website/pages/ru/indexing/tap.mdx b/website/pages/ru/indexing/tap.mdx index 699d25f0f1b5..bcc2ed4535b8 100644 --- a/website/pages/ru/indexing/tap.mdx +++ b/website/pages/ru/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Примечания: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/ru/resources/benefits.mdx b/website/pages/ru/resources/benefits.mdx index db940b5c9fe6..761f08267b6a 100644 --- a/website/pages/ru/resources/benefits.mdx +++ b/website/pages/ru/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Курирование сигнала на субграфе - это необязательная единовременная стоимость, равная нулю (например, сигнал стоимостью 1 тыс. долларов может быть курирован на субграфе, а затем отозван - с возможностью получения прибыли в процессе). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Итог: Сеть Graph дешевле, проще в использовании и дает превосходные результаты по сравнению с запуском `graph-node` локально. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/ru/resources/roles/curating.mdx b/website/pages/ru/resources/roles/curating.mdx index 1c6fac307c3a..06fd883d4673 100644 --- a/website/pages/ru/resources/roles/curating.mdx +++ b/website/pages/ru/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Как подавать Сигнал -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) Куратор может выбрать конкретную версию подграфа для сигнализации, или же он может выбрать автоматическую миграцию своего сигнала на самую новую рабочую сборку этого подграфа. Оба варианта являются допустимыми стратегиями и имеют свои плюсы и минусы. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Рынок запросов в The Graph по своей сути молод, и существует риск того, что ваш %APY может оказаться ниже, чем вы ожидаете, из-за зарождающейся динамики рынка. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Подграф может выйти из строя из-за ошибки. За неудавшийся подграф не начисляется плата за запрос. В результате вам придется ждать, пока разработчик исправит ошибку и выложит новую версию. - Если вы подписаны на новейшую версию подграфа, ваши общие ресурсы автоматически перейдут на эту новую версию. При этом будет взиматься кураторская комиссия в размере 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ru/resources/tokenomics.mdx b/website/pages/ru/resources/tokenomics.mdx index c5c854d49ffe..8340b03ef09d 100644 --- a/website/pages/ru/resources/tokenomics.mdx +++ b/website/pages/ru/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Запрос к существующему субграфу -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/ru/subgraphs/billing.mdx b/website/pages/ru/subgraphs/billing.mdx index b8c58d83de09..ee5a467f80ee 100644 --- a/website/pages/ru/subgraphs/billing.mdx +++ b/website/pages/ru/subgraphs/billing.mdx @@ -15,7 +15,7 @@ title: Выставление счетов ## Оплата запросов с помощью кредитной карты - Чтобы настроить оплату с помощью кредитных/дебетовых карт, пользователи должны зайти в Subgraph Studio (https://thegraph.com/studio/) - 1. Перейдите на[страницу оплаты Subgraph Studio](https://thegraph.com/studio/billing/). + 1. Перейдите на[страницу оплаты Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Нажмите на кнопку «Connect Wallet» в правом верхнем углу страницы. Вы будете перенаправлены на страницу выбора кошелька. Выберите свой кошелек и нажмите «Connect». 3. Выберите «Обновление плана», если Вы переходите с бесплатного плана, или «Управление планом», если Вы уже ранее добавили GRT на свой баланс для оплаты. Далее Вы можете оценить количество запросов, чтобы получить примерную стоимость, но это не обязательный шаг. 4. Чтобы выбрать оплату кредитной картой, выберите «Credit card» как способ оплаты и заполните информацию о своей карте. Те, кто ранее использовал Stripe, могут воспользоваться функцией Link для автоматического заполнения данных. @@ -50,7 +50,7 @@ title: Выставление счетов ### Добавление токенов GRT с помощью кошелька -1. Перейдите на [страницу оплаты в Subgraph Studio](https://thegraph.com/studio/billing/). +1. Перейдите на [страницу оплаты в Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Нажмите на кнопку «Connect Wallet» в правом верхнем углу страницы. Вы будете перенаправлены на страницу выбора кошелька. Выберите свой кошелек и нажмите «Connect». 3. Нажмите кнопку «Управление» в правом верхнем углу. Новые пользователи увидят опцию «Обновить до плана Роста», а те, кто пользовался ранее — «Пополнение с кошелька». 4. Используйте ползунок, чтобы оценить количество запросов, которое Вы планируете выполнять ежемесячно. @@ -67,7 +67,7 @@ title: Выставление счетов ### Вывод токенов GRT с помощью кошелька -1. Перейдите на [страницу для оплаты Subgraph Studio](https://thegraph.com/studio/billing/). +1. Перейдите на [страницу для оплаты Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Нажмите на кнопку «Подключить кошелек» в правом верхнем углу страницы. Выберите свой кошелек и нажмите «Подключить». 3. Нажмите кнопку «Управление» в правом верхнем углу страницы. Выберите «Вывести GRT». Появится боковая панель. 4. Введите сумму GRT, которую хотите вывести. @@ -76,7 +76,7 @@ title: Выставление счетов ### Добавление токенов GRT с помощью кошелька с мультиподписью -1. Перейдите на [страницу оплаты Subgraph Studio](https://thegraph.com/studio/billing/). +1. Перейдите на [страницу оплаты Subgraph Studio](https://thegraph.com/studio/subgraphs/billing/). 2. Кликните «Подключить кошелек» в правом верхнем углу страницы. Выберите свой кошелек и нажмите «Подключить». Если Вы используете [Gnosis-Safe](https://gnosis-safe.io/), Вы сможете подключить как стандартный кошелёк, так и кошелёк с мультиподписью. Затем подпишите соответствующую транзакцию. За это Вам не придётся платить комиссию. 3. Нажмите кнопку «Управление» в правом верхнем углу. Новые пользователи увидят опцию «Обновить до плана Роста», а те, кто пользовался ранее — «Пополнение с кошелька». 4. Используйте ползунок, чтобы оценить количество запросов, которое Вы планируете выполнять ежемесячно. diff --git a/website/pages/ru/subgraphs/cookbook/arweave.mdx b/website/pages/ru/subgraphs/cookbook/arweave.mdx index fa34140e6213..186e6a501f5c 100644 --- a/website/pages/ru/subgraphs/cookbook/arweave.mdx +++ b/website/pages/ru/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ dataSources: Обработчики событий написаны на [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Запрос субграфа Arweave -Конечная точка GraphQL для субграфов Arweave устанавливается определением схемы с помощью существующего интерфейса API. Пожалуйста, посетите [документацию GraphQL API](/querying/graphql-api/) для получения дополнительной информации. +Конечная точка GraphQL для субграфов Arweave устанавливается определением схемы с помощью существующего интерфейса API. Пожалуйста, посетите [документацию GraphQL API](/subgraphs/querying/graphql-api/) для получения дополнительной информации. ## Примеры субграфов diff --git a/website/pages/ru/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/ru/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/ru/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/ru/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ru/subgraphs/cookbook/cosmos.mdx b/website/pages/ru/subgraphs/cookbook/cosmos.mdx index f47e04b61d35..ef567af1ddde 100644 --- a/website/pages/ru/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/ru/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ dataSources: Обработчики событий написаны на языке [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Запрос субграфа на Cosmos -Конечная точка GraphQL для субграфов на Cosmos устанавливается определением схемы с помощью существующего интерфейса API. Дополнительную информацию можно найти в [документации GraphQL API](/querying/graphql-api/). +Конечная точка GraphQL для субграфов на Cosmos устанавливается определением схемы с помощью существующего интерфейса API. Дополнительную информацию можно найти в [документации GraphQL API](/subgraphs/querying/graphql-api/). ## Поддерживаемые блокчейны Cosmos diff --git a/website/pages/ru/subgraphs/cookbook/derivedfrom.mdx b/website/pages/ru/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/ru/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/ru/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ru/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/ru/subgraphs/cookbook/grafting-hotfix.mdx index 5d1b5f30770d..cfa312c965c4 100644 --- a/website/pages/ru/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/ru/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Дополнительные источники -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ru/subgraphs/cookbook/grafting.mdx b/website/pages/ru/subgraphs/cookbook/grafting.mdx index 61cf032d30ac..3b2308c83c0f 100644 --- a/website/pages/ru/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ru/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Grafting is a powerful feature that allows you to "graft" one subgraph onto anot ## Создание существующего субграфа -Создание субграфов — важная часть The Graph, более подробно описанная [здесь](/quick-start/). Чтобы иметь возможность создать и развернуть существующий субграф, используемый в этом руководстве, предоставляется следующий репозиторий: +Создание субграфов — важная часть The Graph, более подробно описанная [здесь](/subgraphs/quick-start/). Чтобы иметь возможность создать и развернуть существующий субграф, используемый в этом руководстве, предоставляется следующий репозиторий: - [Репозиторий субграфа в качестве примера](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c Чтобы стать еще большим экспертом по Graph, рассмотрите возможность узнать о других способах обработки изменений в базовых источниках данных. Такие альтернативы, как [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates), могут дать аналогичные результаты -> Примечание: многие материалы этой статьи были взяты из ранее опубликованной [статьи по Arweave](/cookbook/arweave/) +> Примечание: многие материалы этой статьи были взяты из ранее опубликованной [статьи по Arweave](/subgraphs/cookbook/arweave/) diff --git a/website/pages/ru/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ru/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/ru/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/ru/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ru/subgraphs/cookbook/near.mdx b/website/pages/ru/subgraphs/cookbook/near.mdx index e0ba36ed0191..d815fb9cd7fe 100644 --- a/website/pages/ru/subgraphs/cookbook/near.mdx +++ b/website/pages/ru/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ The Graph предоставляет разработчикам инструме **schema.graphql:** файл схемы, который определяет, какие данные хранятся для вашего подграфа и как запрашивать их через GraphQL. Требования к подграфам NEAR рассматриваются в [существующей документации](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. Во время разработки субграфа есть две ключевые команды: @@ -98,7 +98,7 @@ accounts: Обработчики событий написаны на языке [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - Обработчики блоков получат `Block` - Обработчики квитанций получат `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Развертывание NEAR субграфа @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 = 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx index f81b1674eda3..41a190869890 100644 --- a/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ru/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Субграфы, работающие на основе субпотоков (Substreams) --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Требования @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Определение пакета субпотоков -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. Рассматриваемый пакет Substreams обнаруживает развертывания контрактов в основной сети Ethereum, отслеживая блок создания и временную метку для всех вновь развернутых контрактов. Для этого в `/proto/example.proto` есть специальный тип `Contract` ([узнайте больше об определении Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/ru/subgraphs/cookbook/timeseries.mdx b/website/pages/ru/subgraphs/cookbook/timeseries.mdx index 1e4fbc5cb68f..a1fbbfc6ee87 100644 --- a/website/pages/ru/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/ru/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ru/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/ru/subgraphs/cookbook/transfer-to-the-graph.mdx index d44d0e63c45f..3b434108dbaa 100644 --- a/website/pages/ru/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/ru/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Пример @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Дополнительные источники -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/ru/subgraphs/developing/creating/advanced.mdx b/website/pages/ru/subgraphs/developing/creating/advanced.mdx index 63fdffd404df..568ab172dcc4 100644 --- a/website/pages/ru/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/ru/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Если между родительским объектом и результирующим объектом-источником данных существует связь1:1, то наиболее простым вариантом будет связать родительский объект с результирующим файловым объектом, используя в качестве поиска IPFS CID. Свяжитесь с нами в Discord, если у Вас возникли трудности с моделированием новых объектов на основе файлов! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### Создание нового обработчика для обработки файлов -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0. Если Вы связываете метаданные NFT с соответствующими токенами, используйте хэш IPFS метаданных для ссылки на объект Metadata из объекта Token. Сохраните объект Metadata, используя хэш IPFS в качестве идентификатора. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Графтинг (перенос) на существующие субграфы -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/ru/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ru/subgraphs/developing/creating/graph-ts/api.mdx index 3aaf812f6aa5..5609d9565220 100644 --- a/website/pages/ru/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ru/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Примечание: Если Вы создали субграф до версии `graph-cli`/`graph-ts` 0.22.0`, значит, Вы используете более старую версию AssemblyScript. Рекомендуется ознакомиться с [`Руководством по миграции\`](/release-notes/assemblyscript-migration-guide/). +> Примечание: Если Вы создали субграф до версии `graph-cli`/`graph-ts` 0.22.0`, значит, Вы используете более старую версию AssemblyScript. Рекомендуется ознакомиться с [`Руководством по миграции\`](/resources/release-notes/assemblyscript-migration-guide/). Узнайте, какие встроенные API можно использовать при написании мэппингов субграфов. По умолчанию доступны два типа API: @@ -35,7 +35,7 @@ title: AssemblyScript API | 0.0.8 | Добавлена проверка наличия полей в схеме при сохранении объекта. | | 0.0.7 | К типам Ethereum добавлены классы `TransactionReceipt` и `Log`
К объекту Ethereum Event добавлено поле `receipt` | | 0.0.6 | В объект Ethereum Transaction добавлено поле `nonce`
В объект Ethereum Block добавлено поле `baseFeePerGas` | -| 0.0.5 | AssemblyScript обновлен до версии 0.19.10 (включая критические изменения, см. [`Руководство по миграции`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` переименован в `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript обновлен до версии 0.19.10 (включая критические изменения, см. [`Руководство по миграции`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` переименован в `ethereum.transaction.gasLimit` | | 0.0.4 | В объект Ethereum SmartContractCall добавлено поле `functionSignature` | | 0.0.3 | В объект Ethereum Call добавлено поле `from`
`etherem.call.address` переименован в ethereum.call.to\` | | 0.0.2 | В объект Ethereum Transaction добавлено поле `input` | diff --git a/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx index 69757f55a845..bff4ca3d0b23 100644 --- a/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ru/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Установка Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Обзор -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Начало работы @@ -114,6 +114,6 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Добавлена поддержка обработчиков событий, имеющих доступ к чекам транзакций. | | 0.0.4 | Добавлена ​​поддержка управления функциями субграфа. | diff --git a/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx index 871d523e0077..9c7498da0fbb 100644 --- a/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ru/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Определение Объектов @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ru/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/ru/subgraphs/developing/creating/starting-your-subgraph.mdx index 39005caf1eeb..380c6a5a9314 100644 --- a/website/pages/ru/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/ru/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/ru/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/ru/subgraphs/developing/creating/subgraph-manifest.mdx index 4a8f9c3a7aac..7945d01c1c11 100644 --- a/website/pages/ru/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/ru/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). Важными элементами манифеста, которые необходимо обновить, являются: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde История данного блока необходима для: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Отката субграфа обратно к этому блоку @@ -517,7 +517,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: Чтобы сохранить определенный объем исторических данных: diff --git a/website/pages/ru/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/ru/subgraphs/developing/creating/unit-testing-framework.mdx index e50b9e7f4d2b..404ec4b5d317 100644 --- a/website/pages/ru/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/ru/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1378,7 +1378,7 @@ Global test coverage: 22.2% (2/9 handlers). > Критично: Не удалось создать WasmInstance из допустимого модуля с контекстом: неизвестный импорт: wasi_snapshot_preview1::fd_write не определен -Это означает, что Вы использовали в своем коде `console.log`, который не поддерживается AssemblyScript. Пожалуйста, рассмотрите возможность использования [API логирования](/developing/graph-ts/api/#logging-api) +Это означает, что Вы использовали в своем коде `console.log`, который не поддерживается AssemblyScript. Пожалуйста, рассмотрите возможность использования [API логирования](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/ru/subgraphs/developing/deploying/multiple-networks.mdx b/website/pages/ru/subgraphs/developing/deploying/multiple-networks.mdx index 9c790b17f559..1a4d1b0567db 100644 --- a/website/pages/ru/subgraphs/developing/deploying/multiple-networks.mdx +++ b/website/pages/ru/subgraphs/developing/deploying/multiple-networks.mdx @@ -2,7 +2,7 @@ title: Развертывание субграфа в нескольких сетях --- -На этой странице объясняется, как развернуть субграф в нескольких сетях. Чтобы развернуть субграф, сначала установите [Graph CLI] (https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). Если Вы еще не создали субграф, смотрите раздел [Создание субграфа] (/developing/creating-a-subgraph). +На этой странице объясняется, как развернуть субграф в нескольких сетях. Чтобы развернуть субграф, сначала установите [Graph CLI] (https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). Если Вы еще не создали субграф, смотрите раздел [Создание субграфа] (/developing/creating-a-subgraph/). ## Развертывание подграфа в нескольких сетях diff --git a/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx index 5b6294339800..a5cb2f1241f1 100644 --- a/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ru/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> Для получения дополнительной информации ознакомьтесь с разделом [Быстрый старт](/quick-start/). +> Для получения дополнительной информации ознакомьтесь с разделом [Быстрый старт](/subgraphs/quick-start/). ### Совместимость подграфов с сетью Graph In order to be supported by Indexers on The Graph Network, subgraphs must: -- Индексировать [поддерживаемую сеть](/developing/supported-networks/) +- Индексировать [поддерживаемую сеть](/supported-networks/) - Не должны использовать ни одну из следующих функций: - ipfs.cat & ipfs.map - Неисправимые ошибки @@ -114,7 +114,7 @@ graph deploy ## Публикация Вашего субграфа -Чтобы успешно опубликовать свой субграф, ознакомьтесь с [публикацией субграфа](/publishing/publishing-a-subgraph/). +Чтобы успешно опубликовать свой субграф, ознакомьтесь с [публикацией субграфа](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Управление версиями Вашего субграфа с помощью CLI @@ -126,7 +126,7 @@ graph deploy Вы также можете обновить метаданные субграфа без публикации новой версии. В Studio можно обновить данные субграфа (аватар, название, описание и т.д.), выбрав опцию **Обновить данные** в [Graph Explorer](https://thegraph.com/explorer). Если эта опция выбрана, будет сгенерирована транзакция в сети, которая обновит информацию о субграфе в Explorer без необходимости публиковать новую версию с новым развертыванием. -> Примечание: Публикация новой версии субграфа в сети требует определенных затрат. Помимо комиссий за транзакцию, Вам нужно также оплатить часть кураторского сбора за авто-миграционный сигнал. Вы не сможете опубликовать новую версию субграфа, если на нее не был подан сигнал от Кураторов. Дополнительную информацию можно прочитать [здесь](/network/curating/). +> Примечание: Публикация новой версии субграфа в сети требует определенных затрат. Помимо комиссий за транзакцию, Вам нужно также оплатить часть кураторского сбора за авто-миграционный сигнал. Вы не сможете опубликовать новую версию субграфа, если на нее не был подан сигнал от Кураторов. Дополнительную информацию можно прочитать [здесь](/resources/roles/curating/). ## Автоматическое архивирование версий подграфа diff --git a/website/pages/ru/subgraphs/developing/developer-faq.mdx b/website/pages/ru/subgraphs/developing/developer-faq.mdx index ae17272c3b0b..109268e58b12 100644 --- a/website/pages/ru/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ru/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ title: Часто задаваемы вопросы для разработчи ### 2. Каков первый шаг в создании субграфа? -Для успешного создания субграфа Вам потребуется установить The Graph CLI. Перед началом работы, ознакомьтесь с разделом [Быстрый старт](/quick-start/). Подробную информацию см. в разделе [Создание субграфа](/developing/creating-a-subgraph/). +Для успешного создания субграфа Вам потребуется установить The Graph CLI. Перед началом работы, ознакомьтесь с разделом [Быстрый старт](/subgraphs/quick-start/). Подробную информацию см. в разделе [Создание субграфа](/developing/creating-a-subgraph/). ### 3. Могу ли я создать субграф, если в моих смарт-контрактах нет событий? @@ -34,7 +34,7 @@ title: Часто задаваемы вопросы для разработчи ### 7. Как вызвать контрактную функцию или получить доступ к публичной переменной состояния из моих мэппингов субграфа? -Просмотрите положение `Доступ к смарт-контракту` в разделе [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Просмотрите положение `Доступ к смарт-контракту` в разделе [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Могу ли я импортировать `ethers.js` или другие библиотеки JS в мои мэппинги субграфов? @@ -80,13 +80,13 @@ docker pull graphprotocol/graph-node:latest ### 15. Могу ли я удалить свой субграф? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Вопросы, связанный с сетью ### 16. Какие сети поддерживает The Graph? -Вы можете найти список поддерживаемых сетей [здесь](/developing/supported-networks/). +Вы можете найти список поддерживаемых сетей [здесь](/supported-networks/). ### 17. Можно ли различать сети (майннет, Sepolia, локальную) внутри обработчиков событий? diff --git a/website/pages/ru/subgraphs/developing/introduction.mdx b/website/pages/ru/subgraphs/developing/introduction.mdx index c412422e4035..ac69c283c525 100644 --- a/website/pages/ru/subgraphs/developing/introduction.mdx +++ b/website/pages/ru/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Обзор @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 7f70364c759c..fbba6d2dee4f 100644 --- a/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ru/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/ru/subgraphs/developing/subgraphs.mdx b/website/pages/ru/subgraphs/developing/subgraphs.mdx index a53e52db48ec..6ba23e314bac 100644 --- a/website/pages/ru/subgraphs/developing/subgraphs.mdx +++ b/website/pages/ru/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/ru/subgraphs/explorer.mdx b/website/pages/ru/subgraphs/explorer.mdx index 81af4903f545..9e3c53275104 100644 --- a/website/pages/ru/subgraphs/explorer.mdx +++ b/website/pages/ru/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Чтобы узнать больше о том, как стать индексатором, ознакомьтесь с [официальной документацией](/network/indexing/) или [Руководством для Индексаторов The Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) +Чтобы узнать больше о том, как стать индексатором, ознакомьтесь с [официальной документацией](/indexing/overview/) или [Руководством для Индексаторов The Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/) ![Панель сведений об индексировании](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Изображение проводника 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Делегаторы @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Общее количество GRT, которое у них имеется в настоящее время в протоколе - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Сеть diff --git a/website/pages/ru/subgraphs/querying/best-practices.mdx b/website/pages/ru/subgraphs/querying/best-practices.mdx index fdaa93a598aa..8b9721a393e8 100644 --- a/website/pages/ru/subgraphs/querying/best-practices.mdx +++ b/website/pages/ru/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/ru/subgraphs/querying/graphql-api.mdx b/website/pages/ru/subgraphs/querying/graphql-api.mdx index 2b28aa3ca64c..01fb4690122d 100644 --- a/website/pages/ru/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ru/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/ru/subgraphs/querying/introduction.mdx b/website/pages/ru/subgraphs/querying/introduction.mdx index d9d77a085ef3..653f4a8c2afe 100644 --- a/website/pages/ru/subgraphs/querying/introduction.mdx +++ b/website/pages/ru/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Запрос The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/ru/subgraphs/quick-start.mdx b/website/pages/ru/subgraphs/quick-start.mdx index 1d043dcffac2..81aed3e2ea32 100644 --- a/website/pages/ru/subgraphs/quick-start.mdx +++ b/website/pages/ru/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Быстрый старт --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Предварительные требования - Криптовалютный кошелек -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### Публикация Вашего субграфа в сети The Graph -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Публикация с помощью Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -Для настройки развертывания ознакомьтесь с разделом [Публикация субграфа](/publishing/publishing-a-subgraph/). +Для настройки развертывания ознакомьтесь с разделом [Публикация субграфа](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Добавление сигнала к Вашему субграфу @@ -169,7 +169,7 @@ graph publish - Рекомендуется добавить как минимум 3,000 GRT, чтобы привлечь 3 индексаторов. Проверьте право на вознаграждение на основе использования функций субграфа и поддерживаемых сетей. -Чтобы узнать больше о кураторстве, прочитайте раздел [Curating](/network/curating/). +Чтобы узнать больше о кураторстве, прочитайте раздел [Curating](/resources/roles/curating/). Чтобы сэкономить на расходах на газ, Вы можете курировать свой субграф в той же транзакции, в которой Вы его публикуете, выбрав эту опцию: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -Для получения дополнительной информации о запросах данных из Вашего субграфа прочитайте раздел [Querying The Graph](/querying/querying-the-graph/). +Для получения дополнительной информации о запросах данных из Вашего субграфа прочитайте раздел [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/ru/substreams/sps/sps-faq.mdx b/website/pages/ru/substreams/sps/sps-faq.mdx index bfe5ac6af46d..d9689088d891 100644 --- a/website/pages/ru/substreams/sps/sps-faq.mdx +++ b/website/pages/ru/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Часто задаваемые вопросы о субграфах, р Substreams (Субпотоки), разработанные [StreamingFast](https://www.streamingfast.io/), представляют собой исключительно мощный механизм обработки, способный потреблять обширные потоки блокчейн-данных. Субпотоки позволяют оптимизировать и формировать данные блокчейна для быстрого и бесперебойного использования приложениями конечных пользователей. В частности, Субпотоки - это независимый от блокчейна, распараллеленный и ориентированный на потоковую передачу движок, служащий в качестве уровня преобразования данных блокчейна. Работая на базе [Firehose](https://firehose.streamingfast.io), он позволяет разработчикам писать модули на языке Rust, использовать модули сообщества,обеспечивать крайне высокую производительность индексирования и [отправлять](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) свои данные в любое место. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## Что такое субграфы, работающие на основе Субпотоков? -[Субграфы, работающие на основе Субпотоков](/cookbook/substreams-powered-subgraphs/) сочетают в себе мощь Субпотоков с возможностью запроса субграфов. При публикации Субграфа, работающего на основе Субпотоков, данные, полученные в результате преобразований Субпотоков, могут [выводить изменения объекта](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), совместимые с объектами субграфа. +[Субграфы, работающие на основе Субпотоков](/subgraphs/cookbook/substreams-powered-subgraphs/) сочетают в себе мощь Субпотоков с возможностью запроса субграфов. При публикации Субграфа, работающего на основе Субпотоков, данные, полученные в результате преобразований Субпотоков, могут [выводить изменения объекта](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), совместимые с объектами субграфа. Если Вы уже знакомы с разработкой субграфов, обратите внимание на то, что к тому же можно запрашивать субграфы, работающие на основе Субпотоков, точно так же, как если бы они были созданы на уровне преобразования AssemblyScript, со всеми преимуществами Субграфа, такими как предоставление динамического и гибкого GraphQL API. @@ -62,9 +62,9 @@ Firehose, разработанный [StreamingFast](https://www.streamingfast.i ## Где разработчики могут получить доступ к дополнительной информации о субграфах работающих на основе Субпотоков и о Субпотоках? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -В документации [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) показано, как упаковать их для развертывания в The Graph. +В документации [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) показано, как упаковать их для развертывания в The Graph. [Новейший инструмент Substreams Codegen](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) позволит Вам загрузить проект Substreams без использования какого-либо кода. @@ -82,7 +82,7 @@ The [Substreams documentation](/substreams/) will teach you how to build Substre ## Как Вы можете создать и развернуть субграф, работающий на основе Субпотоков? -После [defining](/cookbook/substreams-powered-subgraphs/) субграфа, работающего на основе Субпотоков, Вы можете использовать the Graph CLI для его развертывания в [Subgraph Studio](https://thegraph.com/studio /). +После [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) субграфа, работающего на основе Субпотоков, Вы можете использовать the Graph CLI для его развертывания в [Subgraph Studio](https://thegraph.com/studio /). ## Где я могу найти примеры Субпотоков и субграфов, работающих на основе Субпотоков? diff --git a/website/pages/ru/supported-networks.mdx b/website/pages/ru/supported-networks.mdx index cc3233aab732..bb4ced6db993 100644 --- a/website/pages/ru/supported-networks.mdx +++ b/website/pages/ru/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Базовая поддержка сети обеспечивается [индексатором обновления](https://thegraph.com/blog/upgrade-indexer/). -\*\* Интеграция с Graph Node: `evm`, `near`, `cosmos`, `osmosis` и `ar` имеют собственный обработчик и поддержку типов в Graph Node. Чейны, совместимые с Firehose и Substreams, могут использовать обобщенную интеграцию [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs/) (включая сети `evm` и `near`). ⁠† Поддерживает развертывание [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs/). +\*\* Интеграция с Graph Node: `evm`, `near`, `cosmos`, `osmosis` и `ar` имеют собственный обработчик и поддержку типов в Graph Node. Чейны, совместимые с Firehose и Substreams, могут использовать обобщенную интеграцию [субграфов на основе Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/) (включая сети `evm` и `near`). ⁠† Поддерживает развертывание [субграфов на основе Substreams](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio полагается на стабильность и надежность базовых технологий, например, таких, как JSON-RPC, Firehose и конечных точек Substreams. - Субграфы, индексирующие Gnosis Chain, теперь могут быть развернуты с помощью сетевого идентификатора `gnosis`. diff --git a/website/pages/sv/about.mdx b/website/pages/sv/about.mdx index a819e0212c3b..90c63c0f036d 100644 --- a/website/pages/sv/about.mdx +++ b/website/pages/sv/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/sv/archived/arbitrum/arbitrum-faq.mdx b/website/pages/sv/archived/arbitrum/arbitrum-faq.mdx index 2afe8b430db2..a3162cf19888 100644 --- a/website/pages/sv/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/sv/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ För att dra fördel av att använda The Graph på L2, använd den här rullgard ## Som subgrafutvecklare, datakonsument, indexerare, curator eller delegator, vad behöver jag göra nu? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Allt har testats noggrant och en beredskapsplan finns på plats för att säkers ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ Bron har blivit [hårt granskad](https://code4rena.com/contests/2022-10-the-grap Att lägga till GRT till ditt Arbitrum faktureringssaldo kan göras med ett klick i [Subgraf Studio](https://thegraph.com/studio/). Du kommer enkelt att kunna koppla din GRT till Arbitrum och fylla dina API nycklar i en transaktion. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/sv/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/sv/archived/arbitrum/l2-transfer-tools-faq.mdx index c0c1a2dedcb6..b47caf143b98 100644 --- a/website/pages/sv/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/sv/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ Dessa verktyg kommer att kräva att du följer en specifik uppsättning steg ber ### Kan jag använda samma plånbok som jag använder på Ethereum huvudnätet? -Om du använder en [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account)-plånbok kan du använda samma adress. Om din Ethereum huvudnät plånbok är en kontrakt (t.ex. en multisig) måste du specificera en [Arbitrum plånboksadress](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) där din överföring kommer att skickas. Kontrollera adressen noggrant eftersom felaktiga överföringar till felaktig adress kan resultera i permanent förlust. Om du vill använda en multisig på L2 måste du se till att du implementerar en multisig-kontrakt på Arbitrum One. +Om du använder en [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account)-plånbok kan du använda samma adress. Om din Ethereum huvudnät plånbok är en kontrakt (t.ex. en multisig) måste du specificera en [Arbitrum plånboksadress](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) där din överföring kommer att skickas. Kontrollera adressen noggrant eftersom felaktiga överföringar till felaktig adress kan resultera i permanent förlust. Om du vill använda en multisig på L2 måste du se till att du implementerar en multisig-kontrakt på Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx index 851c7817e865..6c73e02a271d 100644 --- a/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/sv/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Guide för överföringsverktyg The Graph har gjort det enkelt att flytta till L2 på Arbitrum One. För varje protokolldeltagare finns det en uppsättning L2 överföringsverktyg som gör överföringen till L2 sömlös för alla nätverksdeltagare. Dessa verktyg kräver att du följer en specifik uppsättning steg beroende på vad du överför. -Några vanliga frågor om dessa verktyg besvaras i [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). De vanliga frågorna innehåller djupgående förklaringar av hur du använder verktygen, hur de fungerar och saker att tänka på när du använder dem. +Några vanliga frågor om dessa verktyg besvaras i [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). De vanliga frågorna innehåller djupgående förklaringar av hur du använder verktygen, hur de fungerar och saker att tänka på när du använder dem. ## Så här överför du din subgraf till Arbitrum (L2) diff --git a/website/pages/sv/archived/sunrise.mdx b/website/pages/sv/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/sv/archived/sunrise.mdx +++ b/website/pages/sv/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/sv/contracts.mdx b/website/pages/sv/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/sv/contracts.mdx +++ b/website/pages/sv/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/sv/indexing/chain-integration-overview.mdx b/website/pages/sv/indexing/chain-integration-overview.mdx index 61050d78bd3e..147468f7dc17 100644 --- a/website/pages/sv/indexing/chain-integration-overview.mdx +++ b/website/pages/sv/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ En transparent och styrbaserad integrationsprocess utformades för blockchain-te ## Fas 1. Teknisk Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Team startar protokollintegrationsprocessen genom att skapa en Forumtråd [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Ny Datakällor underkategori under Governance & GIPs). Att använda standardforummallen är obligatoriskt. ## Fas 2. Integrationsvalidering diff --git a/website/pages/sv/indexing/new-chain-integration.mdx b/website/pages/sv/indexing/new-chain-integration.mdx index bda83128ff44..b45f9b924f50 100644 --- a/website/pages/sv/indexing/new-chain-integration.mdx +++ b/website/pages/sv/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graf Node bör synkronisera den distribuerade subgrafen om det inte finns några ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/sv/indexing/overview.mdx b/website/pages/sv/indexing/overview.mdx index 8249649e259e..4889b4e6d0d8 100644 --- a/website/pages/sv/indexing/overview.mdx +++ b/website/pages/sv/indexing/overview.mdx @@ -87,7 +87,7 @@ När en tilldelning har avslutats är återbetalningarna tillgängliga för Inde ### Vad är frågeavgiftsminskning och minskning av indexeringsbelöning? -Värdena `queryFeeCut` och `indexingRewardCut` är delegationparametrar som Indexern kan sätta tillsammans med `cooldownBlocks` för att kontrollera distributionen av GRT mellan Indexern och deras Delegatorer. Se de sista stegen i [Staking i protokollet](/network/indexing/#stake-in-the-protocol) för anvisningar om att ställa in delegationparametrarna. +Värdena `queryFeeCut` och `indexingRewardCut` är delegationparametrar som Indexern kan sätta tillsammans med `cooldownBlocks` för att kontrollera distributionen av GRT mellan Indexern och deras Delegatorer. Se de sista stegen i [Staking i protokollet](/indexing/overview/#stake-in-the-protocol) för anvisningar om att ställa in delegationparametrarna. - **queryFeeCut** - andelen frågeavgiftsåterbetalningar som kommer att distribueras till Indexern. Om detta är inställt på 95% kommer Indexern att få 95% av de frågeavgifter som tjänas när en tilldelning avslutas, medan de andra 5% fördelas till Delegatorerna. @@ -121,7 +121,7 @@ Indexers kan skilja sig åt genom att tillämpa avancerade tekniker för att fat ### Vilka grundläggande säkerhetsåtgärder bör en Indexer vidta? -- **Operatörplånbok** - Att skapa en operatörplånbok är en viktig försiktighetsåtgärd eftersom den möjliggör att en Indexer kan upprätthålla separation mellan sina nycklar som styr insatsen och de som är ansvariga för dagliga operationer. Se [Insats i protokollet](/network/indexing/#stake-in-the-protocol) för anvisningar. +- **Operatörplånbok** - Att skapa en operatörplånbok är en viktig försiktighetsåtgärd eftersom den möjliggör att en Indexer kan upprätthålla separation mellan sina nycklar som styr insatsen och de som är ansvariga för dagliga operationer. Se [Insats i protokollet](/indexing/overview/#stake-in-the-protocol) för anvisningar. - **Brandvägg** - Endast Indexertjänsten behöver vara offentligt exponerad och särskild uppmärksamhet bör ägnas åt att säkra administrativa portar och databasåtkomst: Graph Node JSON-RPC-gränssnittet (standardport: 8030), Indexerhanterings-API-gränssnittet (standardport: 18000) och PostgreSQL-databasgränssnittet (standardport: 5432) bör inte vara exponerade. @@ -375,7 +375,7 @@ För att framgångsrikt delta i nätverket krävs nästan konstant övervakning #### Komma igång -Indexer-agent och Indexer-service bör placeras tillsammans med din Graph Node-infrastruktur. Det finns många sätt att konfigurera virtuella exekveringsmiljöer för dina Indexer-komponenter; här förklarar vi hur du kör dem på bare-metal med hjälp av NPM-paket eller källkod, eller via Kubernetes och Docker på Google Cloud Kubernetes Engine. Om dessa installations exempel inte passar bra för din infrastruktur kommer det sannolikt att finnas en gemenskapsråd att använda som referens, kom och säg hej på [Discord](https://discord.gg/graphprotocol)! Kom ihåg att [satsa på protokollet](/network/indexing/#stake-in-the-protocol) innan du startar dina Indexer-komponenter! +Indexer-agent och Indexer-service bör placeras tillsammans med din Graph Node-infrastruktur. Det finns många sätt att konfigurera virtuella exekveringsmiljöer för dina Indexer-komponenter; här förklarar vi hur du kör dem på bare-metal med hjälp av NPM-paket eller källkod, eller via Kubernetes och Docker på Google Cloud Kubernetes Engine. Om dessa installations exempel inte passar bra för din infrastruktur kommer det sannolikt att finnas en gemenskapsråd att använda som referens, kom och säg hej på [Discord](https://discord.gg/graphprotocol)! Kom ihåg att [satsa på protokollet](/indexing/overview/#stake-in-the-protocol) innan du startar dina Indexer-komponenter! #### Från NPM-paket @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Användning av K8s och Terraform -Se avsnittet [Konfigurera serverinfrastruktur med Terraform på Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Se avsnittet [Konfigurera serverinfrastruktur med Terraform på Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Användning @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -När en Indexer har satsat GRT i protokollet kan [Indexer-komponenterna](/network/indexing/#indexer-components) startas och börja interagera med nätverket. +När en Indexer har satsat GRT i protokollet kan [Indexer-komponenterna](/indexing/overview/#indexer-components) startas och börja interagera med nätverket. #### Godkänn tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Det rekommenderas att Indexers använder funktionen för offchain-synkronisering för att synkronisera subgraph-deploys till kedjehuvudet innan de skapar allokeringen på kedjan. Den här funktionen är särskilt användbar för subgraphs som kan ta längre tid än 28 epoker att synkronisera eller har vissa chanser att misslyckas obestämt. diff --git a/website/pages/sv/indexing/tap.mdx b/website/pages/sv/indexing/tap.mdx index d55093c0862e..bd539c8dfb33 100644 --- a/website/pages/sv/indexing/tap.mdx +++ b/website/pages/sv/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Noteringar: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/sv/resources/benefits.mdx b/website/pages/sv/resources/benefits.mdx index c83dad663194..1fe3ee664fd5 100644 --- a/website/pages/sv/resources/benefits.mdx +++ b/website/pages/sv/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Att kurera signal på en subgraf är en valfri engångskostnad med noll nettokostnad (t.ex. $1k i signal kan kurera på en subgraf och senare dras tillbaka - med potential att tjäna avkastning i processen). @@ -89,4 +89,4 @@ The Graphs decentraliserade nätverk ger användare tillgång till geografisk re Sammanfattningsvis är The Graph Nätverk mindre kostsamt, enklare att använda och ger överlägsna resultat jämfört med att köra en `graph-node` lokalt. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/sv/resources/roles/curating.mdx b/website/pages/sv/resources/roles/curating.mdx index 3e24502b8cf9..7da60d83336f 100644 --- a/website/pages/sv/resources/roles/curating.mdx +++ b/website/pages/sv/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Hur man Signaliserar -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) En kurator kan välja att signalera på en specifik subgrafversion, eller så kan de välja att ha sin signal automatiskt migrerad till den nyaste produktionsversionen av den subgrafen. Båda är giltiga strategier och har sina egna för- och nackdelar. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Frågemarknaden är i grunden ung på The Graph och det finns en risk att din %APY kan vara lägre än du förväntar dig på grund av tidiga marknadsmekanik. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. En subgraf kan misslyckas på grund av en bugg. En misslyckad subgraf genererar inte frågeavgifter. Som ett resultat måste du vänta tills utvecklaren rättar felet och distribuerar en ny version. - Om du prenumererar på den nyaste versionen av en subgraf kommer dina andelar automatiskt att migreras till den nya versionen. Detta kommer att medföra en kuratoravgift på 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/sv/resources/tokenomics.mdx b/website/pages/sv/resources/tokenomics.mdx index b85a99fa6693..113baff87745 100644 --- a/website/pages/sv/resources/tokenomics.mdx +++ b/website/pages/sv/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Fråga en befintlig subgraf -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/sv/subgraphs/billing.mdx b/website/pages/sv/subgraphs/billing.mdx index 5c12aa5cd9c1..a16204c53d73 100644 --- a/website/pages/sv/subgraphs/billing.mdx +++ b/website/pages/sv/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Klicka på knappen "Anslut plånbok" längst upp till höger på sidan. Du kommer att omdirigeras till sidan för plånboksval. Välj din plånbok och klicka på "Anslut". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Klicka på knappen "Anslut plånbok" längst upp till höger på sidan. Du kommer att omdirigeras till sidan för plånboksval. Välj din plånbok och klicka på "Anslut". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Lägga till GRT med en multisig-plånbok -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/sv/subgraphs/cookbook/arweave.mdx b/website/pages/sv/subgraphs/cookbook/arweave.mdx index b354355d683f..019409ea12e6 100644 --- a/website/pages/sv/subgraphs/cookbook/arweave.mdx +++ b/website/pages/sv/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition beskriver strukturen för den resulterande subgraf databasen o Hanterarna för bearbetning av händelser är skrivna i [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Fråga efter en Arweave-subgraf -GraphQL slutpunkten för Arweave subgrafer bestäms av schemadefinitionen, med det befintliga API gränssnittet. Besök [GraphQL API dokumentationen](/querying/graphql-api/) för mer information. +GraphQL slutpunkten för Arweave subgrafer bestäms av schemadefinitionen, med det befintliga API gränssnittet. Besök [GraphQL API dokumentationen](/subgraphs/querying/graphql-api/) för mer information. ## Exempel på subgrafer diff --git a/website/pages/sv/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/sv/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/sv/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/sv/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sv/subgraphs/cookbook/cosmos.mdx b/website/pages/sv/subgraphs/cookbook/cosmos.mdx index f1ae3d262aa3..3c806079a105 100644 --- a/website/pages/sv/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/sv/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and Hanterarna för bearbetning av händelser är skrivna i [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Fråga efter en Cosmos subgraf -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Stöds Cosmos Blockchains diff --git a/website/pages/sv/subgraphs/cookbook/derivedfrom.mdx b/website/pages/sv/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/sv/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/sv/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sv/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/sv/subgraphs/cookbook/grafting-hotfix.mdx index b1e1a022076a..cd68f5b32a38 100644 --- a/website/pages/sv/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/sv/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Ytterligare resurser -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sv/subgraphs/cookbook/grafting.mdx b/website/pages/sv/subgraphs/cookbook/grafting.mdx index 96ed588bc5b2..a25fecf797f0 100644 --- a/website/pages/sv/subgraphs/cookbook/grafting.mdx +++ b/website/pages/sv/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Genom att följa dessa riktlinjer minimerar du riskerna och säkerställer en sm ## Bygga en befintlig subgraf -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraf exempel repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Obs! Mycket material från den här artikeln togs från den tidigare publicerade [Arweave-artikeln](/cookbook/arweave/) +> Obs! Mycket material från den här artikeln togs från den tidigare publicerade [Arweave-artikeln](/subgraphs/cookbook/arweave/) diff --git a/website/pages/sv/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/sv/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/sv/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/sv/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sv/subgraphs/cookbook/near.mdx b/website/pages/sv/subgraphs/cookbook/near.mdx index 88927bb176ef..f2bf41799d74 100644 --- a/website/pages/sv/subgraphs/cookbook/near.mdx +++ b/website/pages/sv/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ Det finns tre aspekter av subgraf definition: **schema.graphql:** en schema fil som definierar vilken data som lagras för din subgraf, och hur man frågar den via GraphQL. Kraven för NEAR undergrafer täcks av [den befintliga dokumentationen](/developing/creating-a-subgraph/#the-graphql-schema). -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. Under subgrafutveckling finns det två nyckelkommandon: @@ -98,7 +98,7 @@ Schemadefinition beskriver strukturen för den resulterande subgraf databasen oc Hanterarna för bearbetning av händelser är skrivna i [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Dessa typer skickas till block & kvittohanterare: - Blockhanterare kommer att få ett `Block` - Kvittohanterare kommer att få ett `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Utplacera en NEAR Subgraf @@ -228,7 +228,7 @@ Vi kommer snart att ge mer information om hur du kör ovanstående komponenter. ## Fråga efter en NEAR subgraf -GraphQL slutpunkten för NEAR undergrafer bestäms av schemadefinitionen, med det befintliga API gränssnittet. Besök [GraphQL API-dokumentationen](/querying/graphql-api/) för mer information. +GraphQL slutpunkten för NEAR undergrafer bestäms av schemadefinitionen, med det befintliga API gränssnittet. Besök [GraphQL API-dokumentationen](/subgraphs/querying/graphql-api/) för mer information. ## Exempel på subgrafer @@ -276,7 +276,7 @@ Väntande funktionalitet stöds ännu inte för NEAR subgrafer. Under tiden kan ### Min fråga har inte besvarats, var kan jag få mer hjälp med att bygga NEAR subgrafer? -Om det är en generell fråga om subgraffutveckling finns det mycket mer information i resten av [Utvecklardokumentationen](/quick-start/). Annars, var vänlig och anslut dig till [The Graph Protocol Discord](https://discord.gg/graphprotocol) och ställ din fråga i kanalen #near eller skicka ett e-postmeddelande till near@thegraph.com. +Om det är en generell fråga om subgraffutveckling finns det mycket mer information i resten av [Utvecklardokumentationen](/subgraphs/quick-start/). Annars, var vänlig och anslut dig till [The Graph Protocol Discord](https://discord.gg/graphprotocol) och ställ din fråga i kanalen #near eller skicka ett e-postmeddelande till near@thegraph.com. ## Referenser diff --git a/website/pages/sv/subgraphs/cookbook/pruning.mdx b/website/pages/sv/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/sv/subgraphs/cookbook/pruning.mdx +++ b/website/pages/sv/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 34057468721c..e7553043450b 100644 --- a/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/sv/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-drivna subgrafer --- -[Substreams](/substreams/) är en ny ramverk för att behandla blockkedjedata som utvecklats av StreamingFast för The Graph Network. Ett Substreams-modul kan generera ändringar i entiteter som är kompatibla med Subgraph-entiteter. En subgraf kan använda en sådan Substreams-modul som en datakälla och därmed ta del av Substreams indexeringshastighet och ytterligare data för subgrafutvecklare. +[Substreams](/substreams/introduction/) är en ny ramverk för att behandla blockkedjedata som utvecklats av StreamingFast för The Graph Network. Ett Substreams-modul kan generera ändringar i entiteter som är kompatibla med Subgraph-entiteter. En subgraf kan använda en sådan Substreams-modul som en datakälla och därmed ta del av Substreams indexeringshastighet och ytterligare data för subgrafutvecklare. ## Krav @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Definiera ett Substreams-paket -En Substreams-paket består av typer (definierade som [Protocol Buffers](https://protobuf.dev/)), moduler (skrivna i Rust) och en `substreams.yaml`-fil som refererar till typerna och specificerar hur modulerna utlöses. [Besök Substreams-dokumentationen för att lära dig mer om Substreams-utveckling](/substreams/), och kolla in [awesome-substreams](https://github.com/pinax-network/awesome-substreams) och [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) för fler exempel. +En Substreams-paket består av typer (definierade som [Protocol Buffers](https://protobuf.dev/)), moduler (skrivna i Rust) och en `substreams.yaml`-fil som refererar till typerna och specificerar hur modulerna utlöses. [Besök Substreams-dokumentationen för att lära dig mer om Substreams-utveckling](/substreams/introduction/), och kolla in [awesome-substreams](https://github.com/pinax-network/awesome-substreams) och [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) för fler exempel. Substreams-paketet i fråga upptäcker kontraktsdistributioner på Mainnet Ethereum, spårar skapandeblocket och tidsstämpeln för alla nyligen distribuerade kontrakt. För att göra detta finns det en dedikerad "kontrakt"-typ i "/proto/example.proto" ([läs mer om att definiera protokollbuffertar](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/sv/subgraphs/cookbook/timeseries.mdx b/website/pages/sv/subgraphs/cookbook/timeseries.mdx index 306ebfa0647a..76678087aca2 100644 --- a/website/pages/sv/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/sv/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sv/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/sv/subgraphs/cookbook/transfer-to-the-graph.mdx index 34d7ef222024..6d9ebccab5c4 100644 --- a/website/pages/sv/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/sv/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Exempel @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Ytterligare resurser -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/sv/subgraphs/developing/creating/advanced.mdx b/website/pages/sv/subgraphs/developing/creating/advanced.mdx index 46220d0a9a0a..9831b7e5436e 100644 --- a/website/pages/sv/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/sv/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Om relationen är 1:1 mellan föräldraentiteten och den resulterande filbaserade datakälla entiteten är det enklaste mönstret att länka föräldraentiteten till en resulterande filbaserad entitet genom att använda IPFS CID som söknyckel. Kontakta oss på Discord om du har svårt att modellera dina nya filbaserade entiteter! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### Skapa en ny hanterare för att bearbeta filer -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Dessutom är det inte möjligt att skapa datakällor från en filbaserad datakä Om du länkar NFT-metadata till motsvarande token, använd metadata IPFS-hash för att referera till en Metadata-entitet från Token-entiteten. Spara Metadata-entiteten med IPFS-hash som ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Ympning på befintliga delgrafer -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx index f823821216a7..78e7403e21f0 100644 --- a/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/sv/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: API för AssemblyScript --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx index 8166fa4088c1..1e917f1a7cc8 100644 --- a/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/sv/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Installera Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Översikt -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Komma igång @@ -114,6 +114,6 @@ ABI-filerna måste matcha ditt/dina kontrakt. Det finns några olika sätt att f | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx b/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx index 541bbae54e19..bdfb8a1357a5 100644 --- a/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/sv/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/sv/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/sv/subgraphs/developing/creating/starting-your-subgraph.mdx index 8e28ff3558ab..04fe67d27470 100644 --- a/website/pages/sv/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/sv/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/sv/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/sv/subgraphs/developing/creating/subgraph-manifest.mdx index fa653c523940..7a8e3a77765f 100644 --- a/website/pages/sv/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/sv/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). De viktiga posterna att uppdatera för manifestet är: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/sv/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/sv/subgraphs/developing/creating/unit-testing-framework.mdx index 1835214d90f8..7f2c0d4330dc 100644 --- a/website/pages/sv/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/sv/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,7 @@ Loggutmatningen innehåller testkörningens varaktighet. Här är ett exempel: > 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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx index 03bd77711e98..7972d60eefbf 100644 --- a/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/sv/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### Kompatibilitet mellan undergrafer och grafnätet In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - Får inte använda någon av följande egenskaper: - ipfs.cat & ipfs.map - Icke dödliga fel @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatisk arkivering av versioner av undergrafer diff --git a/website/pages/sv/subgraphs/developing/developer-faq.mdx b/website/pages/sv/subgraphs/developing/developer-faq.mdx index fef4bde9658a..5ad177f33946 100644 --- a/website/pages/sv/subgraphs/developing/developer-faq.mdx +++ b/website/pages/sv/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ Du måste distribuera om subgrafen, men om subgrafens ID (IPFS-hash) inte ändra ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ Om endast en entitet skapas under händelsen och om inget bättre är tillgängl ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -Du kan hitta listan över de stödda nätverken [här](/developing/supported-networks/). +Du kan hitta listan över de stödda nätverken [här](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/sv/subgraphs/developing/introduction.mdx b/website/pages/sv/subgraphs/developing/introduction.mdx index c726ffb0c5a0..f98e1d38c374 100644 --- a/website/pages/sv/subgraphs/developing/introduction.mdx +++ b/website/pages/sv/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Utveckling --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Översikt @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx index eafaa0dd0c1e..2201dc616c99 100644 --- a/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/sv/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Uppdatera metadata för en publicerad subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/sv/subgraphs/developing/subgraphs.mdx b/website/pages/sv/subgraphs/developing/subgraphs.mdx index ff81ea93c8b9..966263daafca 100644 --- a/website/pages/sv/subgraphs/developing/subgraphs.mdx +++ b/website/pages/sv/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/sv/subgraphs/explorer.mdx b/website/pages/sv/subgraphs/explorer.mdx index f3d4efb0d996..e987ad146153 100644 --- a/website/pages/sv/subgraphs/explorer.mdx +++ b/website/pages/sv/subgraphs/explorer.mdx @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Utforskaren Bild 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegater @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Totalt belopp av GRT som de för närvarande har i protokollet - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Nätverk diff --git a/website/pages/sv/subgraphs/querying/best-practices.mdx b/website/pages/sv/subgraphs/querying/best-practices.mdx index 8b952e9bcd9d..0a0d7524d198 100644 --- a/website/pages/sv/subgraphs/querying/best-practices.mdx +++ b/website/pages/sv/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Varje `queryName` får endast användas en gång per operation. - Varje `field` får bara användas en gång i ett urval (vi kan inte fråga `id` två gånger under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Varje variabel som tilldelas ett argument måste matcha dess typ. - I en given lista med variabler måste var och en av dem vara unik. - Alla definierade variabler måste användas. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Att skicka en fråga till ett GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Hantering av subgrafer över olika blockkedjor: Frågehantering från flera subgrafer i en enda fråga - [Automatisk blockspårning](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/sv/subgraphs/querying/graphql-api.mdx b/website/pages/sv/subgraphs/querying/graphql-api.mdx index 3ad4105a1ef2..ce9280ad090f 100644 --- a/website/pages/sv/subgraphs/querying/graphql-api.mdx +++ b/website/pages/sv/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/sv/subgraphs/querying/introduction.mdx b/website/pages/sv/subgraphs/querying/introduction.mdx index be6b16862f2a..200fec9c4c6c 100644 --- a/website/pages/sv/subgraphs/querying/introduction.mdx +++ b/website/pages/sv/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Fråga The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/sv/subgraphs/quick-start.mdx b/website/pages/sv/subgraphs/quick-start.mdx index d59221b1659c..4cde193daafd 100644 --- a/website/pages/sv/subgraphs/quick-start.mdx +++ b/website/pages/sv/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Snabbstart --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Förutsättningar - En kryptoplånbok -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/sv/substreams/sps/sps-faq.mdx b/website/pages/sv/substreams/sps/sps-faq.mdx index da63b9843a9b..294765705b96 100644 --- a/website/pages/sv/substreams/sps/sps-faq.mdx +++ b/website/pages/sv/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Vanliga frågor om Substreams-drivna subgrafer Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Gå till [Substreams Documentation](/substreams/) för att lära dig mer om Substreams. +Gå till [Substreams Documentation](/substreams/introduction/) för att lära dig mer om Substreams. ## Vad är Substreams-drivna subgrafer? -[Substreams-drivna subgrafer](/cookbook/substreams-powered-subgraphs/) kombinerar kraften hos Substreams med subgrafiernas möjlighet att frågas. När en Substreams-driven subgraf publiceras kan datan som produceras av Substreams omvandlingar [utdata ändringar av enheter](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), vilket är kompatibelt med subgrafiernas enheter. +[Substreams-drivna subgrafer](/subgraphs/cookbook/substreams-powered-subgraphs/) kombinerar kraften hos Substreams med subgrafiernas möjlighet att frågas. När en Substreams-driven subgraf publiceras kan datan som produceras av Substreams omvandlingar [utdata ändringar av enheter](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), vilket är kompatibelt med subgrafiernas enheter. Om du redan är bekant med utveckling av subgrafer kan du notera att Substreams-drivna subgrafer sedan kan frågas på samma sätt som om de hade producerats av AssemblyScript omvandlingslagret, med alla fördelar med subgrafer, som att tillhandahålla en dynamisk och flexibel GraphQL API. @@ -62,9 +62,9 @@ Det finns många fördelar med att använda Firehose, inklusive: ## Var kan utvecklare få mer information om Substreams-drivna subgrafer och Substreams? -[Substreams-dokumentationen](/substreams/) kommer att lära dig hur du bygger Substreams-moduler. +[Substreams-dokumentationen](/substreams/introduction/) kommer att lära dig hur du bygger Substreams-moduler. -[Substreams-drivna subgrafer dokumentationen](/cookbook/substreams-powered-subgraphs/) kommer att visa dig hur man paketerar dem för distribution på The Graph. +[Substreams-drivna subgrafer dokumentationen](/subgraphs/cookbook/substreams-powered-subgraphs/) kommer att visa dig hur man paketerar dem för distribution på The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ Som exempel kan Alice bygga en DEX-prismodul, Bob kan använda den för att bygg ## Hur kan man bygga och distribuera en Substreams-drivna subgraf? -Efter att ha [defining](/cookbook/substreams-powered-subgraphs/) en Substreams-drivna subgraf kan du använda Graph CLI för att distribuera den i [Subgraph Studio](https://thegraph.com/studio/). +Efter att ha [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) en Substreams-drivna subgraf kan du använda Graph CLI för att distribuera den i [Subgraph Studio](https://thegraph.com/studio/). ## Var kan jag hitta exempel på Substreams och Substreams-drivna subgrafer? diff --git a/website/pages/sv/supported-networks.mdx b/website/pages/sv/supported-networks.mdx index d3113d4759cf..ac709b8e1d0d 100644 --- a/website/pages/sv/supported-networks.mdx +++ b/website/pages/sv/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/sw/about.mdx b/website/pages/sw/about.mdx index 9c21bf00d08f..02b29895881f 100644 --- a/website/pages/sw/about.mdx +++ b/website/pages/sw/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/sw/archived/arbitrum/arbitrum-faq.mdx b/website/pages/sw/archived/arbitrum/arbitrum-faq.mdx index 9c12c8816259..562824e64e95 100644 --- a/website/pages/sw/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/sw/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/sw/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/sw/archived/arbitrum/l2-transfer-tools-faq.mdx index b075b7548fb8..8e6da852a01c 100644 --- a/website/pages/sw/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/sw/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx index e516573fd4d9..485f34a70c97 100644 --- a/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/sw/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/sw/archived/sunrise.mdx b/website/pages/sw/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/sw/archived/sunrise.mdx +++ b/website/pages/sw/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/sw/contracts.mdx b/website/pages/sw/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/sw/contracts.mdx +++ b/website/pages/sw/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/sw/indexing/chain-integration-overview.mdx b/website/pages/sw/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/sw/indexing/chain-integration-overview.mdx +++ b/website/pages/sw/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/sw/indexing/new-chain-integration.mdx b/website/pages/sw/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/sw/indexing/new-chain-integration.mdx +++ b/website/pages/sw/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/sw/indexing/overview.mdx b/website/pages/sw/indexing/overview.mdx index c05c37a275ef..34a60d456cfc 100644 --- a/website/pages/sw/indexing/overview.mdx +++ b/website/pages/sw/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Getting started -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### From NPM packages @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Using K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Usage @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Approve tokens @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/sw/indexing/tap.mdx b/website/pages/sw/indexing/tap.mdx index 3d6bbed374a9..59c436571549 100644 --- a/website/pages/sw/indexing/tap.mdx +++ b/website/pages/sw/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/sw/resources/benefits.mdx b/website/pages/sw/resources/benefits.mdx index a0f0f5a0b3ed..249a9e530966 100644 --- a/website/pages/sw/resources/benefits.mdx +++ b/website/pages/sw/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/sw/resources/roles/curating.mdx b/website/pages/sw/resources/roles/curating.mdx index ecb879ae6fbe..8e6416b6d57e 100644 --- a/website/pages/sw/resources/roles/curating.mdx +++ b/website/pages/sw/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/sw/resources/tokenomics.mdx b/website/pages/sw/resources/tokenomics.mdx index e2e4c904000d..73a1adda922b 100644 --- a/website/pages/sw/resources/tokenomics.mdx +++ b/website/pages/sw/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/sw/subgraphs/billing.mdx b/website/pages/sw/subgraphs/billing.mdx index dec5cfdadc12..f3f52bbf35ee 100644 --- a/website/pages/sw/subgraphs/billing.mdx +++ b/website/pages/sw/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/sw/subgraphs/cookbook/arweave.mdx b/website/pages/sw/subgraphs/cookbook/arweave.mdx index 4c35f4ee8e2e..2098d5ab5932 100644 --- a/website/pages/sw/subgraphs/cookbook/arweave.mdx +++ b/website/pages/sw/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/sw/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/sw/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/sw/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/sw/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sw/subgraphs/cookbook/cosmos.mdx b/website/pages/sw/subgraphs/cookbook/cosmos.mdx index dfdb377688aa..31a1d372051a 100644 --- a/website/pages/sw/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/sw/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/sw/subgraphs/cookbook/derivedfrom.mdx b/website/pages/sw/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/sw/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/sw/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sw/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/sw/subgraphs/cookbook/grafting-hotfix.mdx index 040e3a8209d5..a0bd3f4ab1c2 100644 --- a/website/pages/sw/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/sw/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sw/subgraphs/cookbook/grafting.mdx b/website/pages/sw/subgraphs/cookbook/grafting.mdx index 7aa79c7e2755..57d5169830a7 100644 --- a/website/pages/sw/subgraphs/cookbook/grafting.mdx +++ b/website/pages/sw/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/sw/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/sw/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/sw/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/sw/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sw/subgraphs/cookbook/near.mdx b/website/pages/sw/subgraphs/cookbook/near.mdx index cc0bf8637bee..23a936406e7b 100644 --- a/website/pages/sw/subgraphs/cookbook/near.mdx +++ b/website/pages/sw/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/sw/subgraphs/cookbook/pruning.mdx b/website/pages/sw/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/sw/subgraphs/cookbook/pruning.mdx +++ b/website/pages/sw/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/sw/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/sw/subgraphs/cookbook/timeseries.mdx b/website/pages/sw/subgraphs/cookbook/timeseries.mdx index 2ce0ce266ccf..0168be53d7ed 100644 --- a/website/pages/sw/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/sw/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/sw/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/sw/subgraphs/cookbook/transfer-to-the-graph.mdx index 6a5d2c2793f3..64c225442860 100644 --- a/website/pages/sw/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/sw/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/sw/subgraphs/developing/creating/advanced.mdx b/website/pages/sw/subgraphs/developing/creating/advanced.mdx index 3a08ddab7066..bc3a9a86efb6 100644 --- a/website/pages/sw/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/sw/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx index 8aa0bf0027bf..4c5ce57993f2 100644 --- a/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/sw/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx index 282c68973a8a..a58e6be82324 100644 --- a/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/sw/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx b/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/sw/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/sw/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/sw/subgraphs/developing/creating/starting-your-subgraph.mdx index 5127f01632aa..f463ca3e9507 100644 --- a/website/pages/sw/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/sw/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/sw/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/sw/subgraphs/developing/creating/subgraph-manifest.mdx index f282f3946e75..b4c0e467c780 100644 --- a/website/pages/sw/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/sw/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/sw/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/sw/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/sw/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/sw/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx index 4644cd466aa9..00fbd91a2b44 100644 --- a/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/sw/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an onchain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/sw/subgraphs/developing/developer-faq.mdx b/website/pages/sw/subgraphs/developing/developer-faq.mdx index 85dccad933b0..8a457a3db5c3 100644 --- a/website/pages/sw/subgraphs/developing/developer-faq.mdx +++ b/website/pages/sw/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/sw/subgraphs/developing/introduction.mdx b/website/pages/sw/subgraphs/developing/introduction.mdx index 6ba33f6d916c..45cefaff16ef 100644 --- a/website/pages/sw/subgraphs/developing/introduction.mdx +++ b/website/pages/sw/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 4728db3eb245..e75e3b13d89e 100644 --- a/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/sw/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/sw/subgraphs/developing/subgraphs.mdx b/website/pages/sw/subgraphs/developing/subgraphs.mdx index 1fdd0baf80eb..951ec74234d1 100644 --- a/website/pages/sw/subgraphs/developing/subgraphs.mdx +++ b/website/pages/sw/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph Network. - This is an onchain 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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/sw/subgraphs/explorer.mdx b/website/pages/sw/subgraphs/explorer.mdx index d874f80f5140..433821560d85 100644 --- a/website/pages/sw/subgraphs/explorer.mdx +++ b/website/pages/sw/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/sw/subgraphs/querying/best-practices.mdx b/website/pages/sw/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/sw/subgraphs/querying/best-practices.mdx +++ b/website/pages/sw/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/sw/subgraphs/querying/graphql-api.mdx b/website/pages/sw/subgraphs/querying/graphql-api.mdx index 917fad3f2406..8813e2eeb3f3 100644 --- a/website/pages/sw/subgraphs/querying/graphql-api.mdx +++ b/website/pages/sw/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/sw/subgraphs/querying/introduction.mdx b/website/pages/sw/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/sw/subgraphs/querying/introduction.mdx +++ b/website/pages/sw/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/sw/subgraphs/quick-start.mdx b/website/pages/sw/subgraphs/quick-start.mdx index 429d4d51116f..13af8f0deb42 100644 --- a/website/pages/sw/subgraphs/quick-start.mdx +++ b/website/pages/sw/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Quick Start --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/sw/substreams/sps/sps-faq.mdx b/website/pages/sw/substreams/sps/sps-faq.mdx index 204db022ef34..f35d14cedae1 100644 --- a/website/pages/sw/substreams/sps/sps-faq.mdx +++ b/website/pages/sw/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/sw/supported-networks.mdx b/website/pages/sw/supported-networks.mdx index 9e47f25c86e6..2f3c40917b37 100644 --- a/website/pages/sw/supported-networks.mdx +++ b/website/pages/sw/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/tr/about.mdx b/website/pages/tr/about.mdx index eba9046c6f35..9c1841c92789 100644 --- a/website/pages/tr/about.mdx +++ b/website/pages/tr/about.mdx @@ -24,7 +24,7 @@ Yukarıda bahsedilen Bored Ape Yacht Club örneğinde, [sözleşmenin](https://e Bu basit sorulara yanıt almak, tarayıcıda çalışan bir merkeziyetsiz uygulama (dapp) için **saatler, hatta günler ** sürebilir. -Alternatif olarak, kendi sunucunuzu kurup işlemleri işleyebilir, bunları bir veri tabanında depolayabilir ve veriyi sorgulamak için bir API uç noktası oluşturabilirsiniz. Ancak, bu seçenek [kaynak açısından maliyetli](/network/benefits/) olup sürekli bakım gerektirir, tek bir arıza noktası oluşturur ve merkeziyetsizliğin gerektirdiği önemli güvenlik özelliklerini ortadan kaldırır. +Alternatif olarak, kendi sunucunuzu kurup işlemleri işleyebilir, bunları bir veri tabanında depolayabilir ve veriyi sorgulamak için bir API uç noktası oluşturabilirsiniz. Ancak, bu seçenek [kaynak açısından maliyetli](/resources/benefits/) olup sürekli bakım gerektirir, tek bir arıza noktası oluşturur ve merkeziyetsizliğin gerektirdiği önemli güvenlik özelliklerini ortadan kaldırır. Finalite, zincir yeniden organizasyonu ve "uncle" bloklar gibi blokzinciri özellikleri, sürece karmaşıklık katar ve doğru sorgu sonuçlarını blokzinciri verilerinden elde etmeyi zaman alıcı hale getirip kavramsal olarak zorlaştırır. diff --git a/website/pages/tr/archived/arbitrum/arbitrum-faq.mdx b/website/pages/tr/archived/arbitrum/arbitrum-faq.mdx index 65ea8a73cdb7..2d4571f7a6cf 100644 --- a/website/pages/tr/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/tr/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Graph'ı Katman2'de kullanmanın avantajlarından yararlanmak için, zincirler a ## Bir subgraph geliştirici, veri tüketicisi, Endeksleyici, Küratör veya Delegatör olarak şimdi ne yapmalıyım? -Ağ katılımcıları, The Graph Ağı'nda katılım göstermeye devam edebilmek için Arbitrum'a geçmek zorundadır. Ek destek için [L2 Transfer Aracı Kılavuzu](/arbitrum/l2-transfer-tools-guide/) sayfasına bakınız. +Ağ katılımcıları, The Graph Ağı'nda katılım göstermeye devam edebilmek için Arbitrum'a geçmek zorundadır. Ek destek için [L2 Transfer Aracı Kılavuzu](/archived/arbitrum/l2-transfer-tools-guide/) sayfasına bakınız. Tüm endeksleme ödülleri artık tamamen Arbitrum üzerindedir. @@ -53,7 +53,7 @@ Güvenli ve sorunsuz bir geçiş sağlamak için her şey kapsamlı bir şekilde ## Ethereum üzerindeki mevcut subgraph'ler çalışıyor mu? -Tüm subgraph'ler artık Arbitrum üzerindedir. Subgraph'lerinizin sorunsuz bir şekilde çalıştığından emin olmak için [L2 Transfer Aracı Kılavuzu](/arbitrum/l2-transfer-tools-guide/) sayfasını inceleyin. +Tüm subgraph'ler artık Arbitrum üzerindedir. Subgraph'lerinizin sorunsuz bir şekilde çalıştığından emin olmak için [L2 Transfer Aracı Kılavuzu](/archived/arbitrum/l2-transfer-tools-guide/) sayfasını inceleyin. ## GRT'nin Arbitrum'da yeni bir akıllı sözleşmesi mi var? @@ -77,4 +77,4 @@ Köprü, tüm kullanıcılar için emniyet ve güvenliği sağlamak amacıyla [k GRT'yi Arbitrum faturalandırma bakiyenize eklemek [Subgraph Stüdyo'da](https://thegraph.com/studio/) tek bir tık ile yapılabilir. GRT'nizi Arbitrum'a kolayca köprüleyebilecek ve API anahtarlarınızı tek bir işlemle doldurabileceksiniz. -GRT ekleme, çekme veya satın alma hakkında daha ayrıntılı talimatlar için [Faturalandırma sayfasını](/billing/) ziyaret edin. +GRT ekleme, çekme veya satın alma hakkında daha ayrıntılı talimatlar için [Faturalandırma sayfasını](/subgraphs/billing/) ziyaret edin. diff --git a/website/pages/tr/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/tr/archived/arbitrum/l2-transfer-tools-faq.mdx index c960082401d2..07f936ad7943 100644 --- a/website/pages/tr/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/tr/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ Bu araçlar, Graph içindeki rolünüzün ne olduğuna ve Katman2'ye ne transfer ### Ethereum ana ağında kullandığım aynı cüzdanı kullanabilir miyim? -Eğer bir [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) (Harici Olarak Sahip Olunan Hesap) cüzdanı kullanıyorsanız aynı adresi kullanabilirsiniz. Ethereum ana ağ cüzdanınız bir sözleşme ise (örneğin bir çoklu imza), transferinizin gönderileceği bir [Arbitrum cüzdan adresi] (/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) belirtmelisiniz. Yanlış bir adrese yapılan transferler kalıcı kayıplara neden olabileceğinden lütfen adresi dikkatlice kontrol edin. Katman2'de bir çoklu imza cüzdanı kullanmak istiyorsanız, Arbitrum One'da bir çoklu imza sözleşmesi kurduğunuzdan emin olun. +Eğer bir [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) (Harici Olarak Sahip Olunan Hesap) cüzdanı kullanıyorsanız aynı adresi kullanabilirsiniz. Ethereum ana ağ cüzdanınız bir sözleşme ise (örneğin bir çoklu imza), transferinizin gönderileceği bir [Arbitrum cüzdan adresi] (/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) belirtmelisiniz. Yanlış bir adrese yapılan transferler kalıcı kayıplara neden olabileceğinden lütfen adresi dikkatlice kontrol edin. Katman2'de bir çoklu imza cüzdanı kullanmak istiyorsanız, Arbitrum One'da bir çoklu imza sözleşmesi kurduğunuzdan emin olun. Ethereum ve Arbitrum gibi EVM blok zincirlerindeki cüzdanlar, blok zinciri ile etkileşime girmenize gerek kalmadan oluşturduğunuz bir çift anahtardır (genel ve özel). Dolayısıyla, Ethereum için oluşturulan herhangi bir cüzdan, başka bir işlem yapmanıza gerek kalmadan Arbitrum üzerinde de çalışacaktır. diff --git a/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx index a5819dd5cc67..17dda278d6cd 100644 --- a/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/tr/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Katman2 Transfer Araçları Rehberi Graph, Arbitrum One üzerinde Katman2'ye geçişi kolaylaştırmıştır. Her protokol katılımcısı için, tüm ağ katılımcıları adına Katman2'ye transferi sorunsuz hale getirmek için bir dizi Katman2 Transfer Aracı vardır. Bu araçlar, ne transfer ettiğinize bağlı olarak belirli bir dizi adımı izlemenizi gerektirecektir. -Bu araçlarla ilgili sıkça sorulan bazı sorular [Katman2 Transfer Araçları SSS](/arbitrum/l2-transfer-tools-faq/) bölümünde yanıtlanmaktadır. SSS, araçların nasıl kullanılacağı, nasıl çalıştıkları ve kullanırken akılda tutulması gerekenler hakkında derinlemesine açıklamalar içermektedir. +Bu araçlarla ilgili sıkça sorulan bazı sorular [Katman2 Transfer Araçları SSS](/archived/arbitrum/l2-transfer-tools-faq/) bölümünde yanıtlanmaktadır. SSS, araçların nasıl kullanılacağı, nasıl çalıştıkları ve kullanırken akılda tutulması gerekenler hakkında derinlemesine açıklamalar içermektedir. ## Subgraph'ınızı Arbitrum'a nasıl transfer edebilirsiniz (Katman2) diff --git a/website/pages/tr/archived/sunrise.mdx b/website/pages/tr/archived/sunrise.mdx index 4a3602426321..91c6e09fd7c6 100644 --- a/website/pages/tr/archived/sunrise.mdx +++ b/website/pages/tr/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Yükseltme İndeksleyicisini neden Edge & Node çalıştırıyor? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/tr/contracts.mdx b/website/pages/tr/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/tr/contracts.mdx +++ b/website/pages/tr/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/tr/indexing/chain-integration-overview.mdx b/website/pages/tr/indexing/chain-integration-overview.mdx index 1102a6a76af6..db50f7b8e673 100644 --- a/website/pages/tr/indexing/chain-integration-overview.mdx +++ b/website/pages/tr/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ Blok zinciri ekiplerinin [Graph protokolüyle entegrasyon](https://forum.thegrap ## Aşama 1. Teknik Entegrasyon -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Ekipler, protokol entegrasyon sürecini bir Forum başlığı oluşturarak başlatır [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Yönetişim ve GIP'ler altındaki Yeni Veri Kaynakları alt kategorisi). Varsayılan Forum şablonunun kullanılması zorunludur. ## Aşama 2. Entegrasyon Doğrulaması diff --git a/website/pages/tr/indexing/new-chain-integration.mdx b/website/pages/tr/indexing/new-chain-integration.mdx index bd672058e941..3ee656eccc5d 100644 --- a/website/pages/tr/indexing/new-chain-integration.mdx +++ b/website/pages/tr/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Herhangi bir hata olmadığı takdirde Graph Düğü'mü dağıtılan subgraph' ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/tr/indexing/overview.mdx b/website/pages/tr/indexing/overview.mdx index 92fb83529393..82a09216e3af 100644 --- a/website/pages/tr/indexing/overview.mdx +++ b/website/pages/tr/indexing/overview.mdx @@ -87,7 +87,7 @@ Bir tahsisat kapatıldıktan sonra iadeler İndeksleyici tarafından talep edile ### What is query fee cut and indexing reward cut? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - İndeksleyiciye dağıtılacak sorgu ücreti iadelerinin %'si. Bu %95 olarak ayarlanırsa, İndeksleyici bir tahsisat kapatıldığında kazanılan sorgu ücretlerinin %95'ini alır ve diğer %5'lik kısım Delegatörlere gider. @@ -121,7 +121,7 @@ Indexers may differentiate themselves by applying advanced techniques for making ### Bir İndeksleyicinin alması gereken bazı temel güvenlik önlemleri nelerdir? -- **Operatör cüzdanı** - Bir operatör cüzdanı oluşturmak önemli bir önlemdir, çünkü bir İndeksleyicinin stake'i kontrol eden anahtarları ile günlük işlemleri kontrol eden anahtarları arasında ayrım yapmasına olanak tanır. Talimatlar için [Protokolde Stake](/network/indexing/#stake-in-the-protocol) bölümüne bakın. +- **Operatör cüzdanı** - Bir operatör cüzdanı oluşturmak önemli bir önlemdir, çünkü bir İndeksleyicinin stake'i kontrol eden anahtarları ile günlük işlemleri kontrol eden anahtarları arasında ayrım yapmasına olanak tanır. Talimatlar için [Protokolde Stake](/indexing/overview/#stake-in-the-protocol) bölümüne bakın. - **Firewall** - Yalnızca İndeksleyici hizmetinin herkese açık olması gerekir ve yönetici bağlantı noktalarının ve veritabanı erişiminin kilitlenmesine özellikle dikkat edilmelidir: Graph Node JSON-RPC uç noktası (varsayılan bağlantı noktası: 8030), İndeksleyici yönetim API uç noktası (varsayılan bağlantı noktası: 18000) ve Postgres veritabanı uç noktası (varsayılan bağlantı noktası: 5432) herkese açık olmamalıdır. @@ -375,7 +375,7 @@ Ağa başarılı bir şekilde katılmak hemen hemen sürekli izleme ve etkileşi #### Buradan başlayın -İndeksleyici aracısı ve İndeksleyici hizmeti, Graph Düğümü altyapınızla birlikte konumlandırılmalıdır. İndeksleyici bileşenleriniz için sanal yürütme ortamları kurmanın birçok yolu vardır; burada bunları NPM paketleri veya kaynak kullanarak baremetal üzerinde veya Google Cloud Kubernetes Motoru üzerinde kubernetes ve docker aracılığıyla nasıl çalıştıracağınızı açıklayacağız. Bu kurulum örnekleri altyapınıza iyi bir şekilde uyarlanamazsa, muhtemelen başvurabileceğiniz bir topluluk rehberi olacaktır, gelin [Discord](https://discord.gg/graphprotocol)'da merhaba deyin! İndeksleyici bileşenlerinizi başlatmadan önce [protokolde stake etmeyi](/network/indexing/#stake-in-the-protocol) unutmayın! +İndeksleyici aracısı ve İndeksleyici hizmeti, Graph Düğümü altyapınızla birlikte konumlandırılmalıdır. İndeksleyici bileşenleriniz için sanal yürütme ortamları kurmanın birçok yolu vardır; burada bunları NPM paketleri veya kaynak kullanarak baremetal üzerinde veya Google Cloud Kubernetes Motoru üzerinde kubernetes ve docker aracılığıyla nasıl çalıştıracağınızı açıklayacağız. Bu kurulum örnekleri altyapınıza iyi bir şekilde uyarlanamazsa, muhtemelen başvurabileceğiniz bir topluluk rehberi olacaktır, gelin [Discord](https://discord.gg/graphprotocol)'da merhaba deyin! İndeksleyici bileşenlerinizi başlatmadan önce [protokolde stake etmeyi](/indexing/overview/#stake-in-the-protocol) unutmayın! #### NPM paketlerinden @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s ve Terraform kullanma -[Google Cloud'da Terraform Kullanarak Sunucu Altyapısı Kurma](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) bölümüne bakın +[Google Cloud'da Terraform Kullanarak Sunucu Altyapısı Kurma](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) bölümüne bakın #### Kullanım @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Bir İndeksleyici protokolde GRT'yi stake ettikten sonra, [İndeksleyici kompenetleri ](/network/indexing/#indexer-components) başlatılabilir ve ağ ile etkileşimlerine başlayabilir. +Bir İndeksleyici protokolde GRT'yi stake ettikten sonra, [İndeksleyici kompenetleri ](/indexing/overview/#indexer-components) başlatılabilir ve ağ ile etkileşimlerine başlayabilir. #### Tokenleri onaylama @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). İndeksleyicilerin, zincir üstünde tahsis oluşturmadan önce subgraph dağıtımlarını chainhead ile senkronize etmek için zincir dışı senkronizasyon fonksiyonunu kullanmaları önerilir. Bu özellik bilhassa senkronize edilmesi 28 dönemden daha uzun sürebilecek veya belirsiz bir şekilde başarısız olma ihtimali olan subgraphlar için kullanışlıdır. diff --git a/website/pages/tr/indexing/tap.mdx b/website/pages/tr/indexing/tap.mdx index cdee8f3f9111..8fd44a6693de 100644 --- a/website/pages/tr/indexing/tap.mdx +++ b/website/pages/tr/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notlar: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/tr/resources/benefits.mdx b/website/pages/tr/resources/benefits.mdx index 33a59e1835d7..0d2a68affb02 100644 --- a/website/pages/tr/resources/benefits.mdx +++ b/website/pages/tr/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ Graph'ın merkeziyetsiz ağı, kullanıcılara bir `graph node`'unu kendi kendin Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/tr/resources/roles/curating.mdx b/website/pages/tr/resources/roles/curating.mdx index 6553a623c4e6..5ef575f9d8a5 100644 --- a/website/pages/tr/resources/roles/curating.mdx +++ b/website/pages/tr/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## How to Signal -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version. - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/tr/resources/tokenomics.mdx b/website/pages/tr/resources/tokenomics.mdx index 1ac77ce1c85d..a0ecd1efd609 100644 --- a/website/pages/tr/resources/tokenomics.mdx +++ b/website/pages/tr/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Mevcut bir subgraph'ı sorgulama -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/tr/subgraphs/billing.mdx b/website/pages/tr/subgraphs/billing.mdx index 43d51514645f..ce39a25dc54e 100644 --- a/website/pages/tr/subgraphs/billing.mdx +++ b/website/pages/tr/subgraphs/billing.mdx @@ -15,7 +15,7 @@ The Graph Ağı'nda subgraph'leri sorgulamak için kullanabileceğiniz iki plan ## Kredi kartı ile sorgu ödemeleri - Kredi/banka kartları ile faturalandırmayı ayarlamak için, kullanıcıların Subgraph Studio'ya (https://thegraph.com/studio/) erişmeleri gerekir - 1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/billing/). + 1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/subgraphs/billing/). 2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdan seçim sayfasına yönlendirileceksiniz. Cüzdanınızı seçin ve "Bağlan" a tıklayın. 3. Ücretsiz Plan'dan yükseltme yapıyorsanız "Planı Yükselt" seçeneğini, daha önce faturalandırma bakiyenize GRT eklediyseniz "Planı Yönet" seçeneğini seçin. Sonrasında, sorgu sayısını tahmin ederek bir fiyat tahmini alabilirsiniz, ancak bu zorunlu bir adım değildir. 4. Kredi kartı ödemesini seçmek için, ödeme yöntemi olarak "Kredi kartı" seçeneğini seçin ve kredi kartı bilgilerinizi doldurun. Daha önce Stripe kullananlar, bilgilerini otomatik doldurmak için Link özelliğini kullanabilirler. @@ -50,7 +50,7 @@ GRT'yi köprüledikten sonra faturalandırma bakiyenize ekleyebilirsiniz. ### Bir cüzdan kullanarak GRT ekleme -1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/billing/). +1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/subgraphs/billing/). 2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdan seçim sayfasına yönlendirileceksiniz. Cüzdanınızı seçin ve "Bağlan" a tıklayın. 3. Sağ üst köşedeki 'Yönet' düğmesine tıklayın. İlk kez kullanıyorsanız 'Büyüme Planına Yükselt' seçeneğini göreceksiniz. Daha önce işlem yaptıysanız 'Cüzdandan Yatır' seçeneğine tıklayın. 4. Kaydırıcıyı kullanarak aylık olarak yapmayı beklediğiniz sorgu sayısını tahmin edin. @@ -67,7 +67,7 @@ GRT'yi köprüledikten sonra faturalandırma bakiyenize ekleyebilirsiniz. ### Bir cüzdan kullanarak GRT çekme -1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/billing/). +1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/subgraphs/billing/). 2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdanınızı seçin ve "Bağlan" düğmesine tıklayın. 3. Sayfanın sağ üst köşesindeki "Yönet" düğmesine tıklayın. "GRT Çek" seçeneğini seçin. Bir yan panel açılacaktır. 4. Çekmek istediğiniz GRT miktarını girin. @@ -76,7 +76,7 @@ GRT'yi köprüledikten sonra faturalandırma bakiyenize ekleyebilirsiniz. ### Multisig cüzdanı kullanarak GRT ekleme -1. Subgraph Studio Faturalandırma sayfasına gitmek için [buraya tıklayın](https://thegraph.com/studio/billing/). +1. Subgraph Studio Faturalandırma sayfasına gitmek için [buraya tıklayın](https://thegraph.com/studio/subgraphs/billing/). 2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdanınızı seçin ve "Bağlan" düğmesine tıklayın. Eğer [Gnosis-Safe](https://gnosis-safe.io/) kullanıyorsanız, multisig cüzdanınızı ve imza cüzdanınızı da bağlayabileceksiniz. Ardından ilgili mesajı imzalayın. Bu işlem gas ücreti gerektirmeyecektir. 3. Sağ üst köşedeki 'Yönet' düğmesine tıklayın. İlk kez kullanıyorsanız 'Büyüme Planına Yükselt' seçeneğini göreceksiniz. Daha önce işlem yaptıysanız 'Cüzdandan Yatır' seçeneğine tıklayın. 4. Kaydırıcıyı kullanarak aylık olarak yapmayı beklediğiniz sorgu sayısını tahmin edin. diff --git a/website/pages/tr/subgraphs/cookbook/arweave.mdx b/website/pages/tr/subgraphs/cookbook/arweave.mdx index 01e455b7aaf6..bf71b1120b55 100644 --- a/website/pages/tr/subgraphs/cookbook/arweave.mdx +++ b/website/pages/tr/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Arweave veri kaynakları iki tür işleyiciyi destekler: Olayları işlemek için işleyiciler [AssemblyScript](https://www.assemblyscript.org/) içinde yazılmıştır. -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Arweave Subgraph'ını Sorgulama -Arweave subgraphları için GraphQL uç noktası, mevcut API arayüzü ile şema tanımı tarafından belirlenir. Daha fazla bilgi için lütfen [GraphQL API dökümantasyonunu](/querying/graphql-api/) ziyaret edin. +Arweave subgraphları için GraphQL uç noktası, mevcut API arayüzü ile şema tanımı tarafından belirlenir. Daha fazla bilgi için lütfen [GraphQL API dökümantasyonunu](/subgraphs/querying/graphql-api/) ziyaret edin. ## Örnek Subgraph'ler diff --git a/website/pages/tr/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/tr/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/tr/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/tr/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/tr/subgraphs/cookbook/cosmos.mdx b/website/pages/tr/subgraphs/cookbook/cosmos.mdx index e1064c19faf7..3cc5dc639e63 100644 --- a/website/pages/tr/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/tr/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and Olayları işlemek için işleyiciler [AssemblyScript](https://www.assemblyscript.org/) içinde yazılmıştır. -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Bir Cosmos subgraph'ini sorgulama -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Desteklenen Cosmos Blok Zincirleri diff --git a/website/pages/tr/subgraphs/cookbook/derivedfrom.mdx b/website/pages/tr/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/tr/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/tr/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/tr/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/tr/subgraphs/cookbook/grafting-hotfix.mdx index 187d4debd2c3..1169b1e2b4eb 100644 --- a/website/pages/tr/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/tr/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Ek Kaynaklar -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/tr/subgraphs/cookbook/grafting.mdx b/website/pages/tr/subgraphs/cookbook/grafting.mdx index 1eec32b7270c..cf4c592ce0b9 100644 --- a/website/pages/tr/subgraphs/cookbook/grafting.mdx +++ b/website/pages/tr/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Bu yönergelere uyarak riskleri en aza indirebilir ve daha sorunsuz bir taşıma ## Mevcut Bir Subgraph'ı Oluşturma -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph örnek deposu](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Not: Bu makaledeki birçok materyal daha önce yayınlanan [Arweave makalesinden](/cookbook/arweave/) alınmıştır +> Not: Bu makaledeki birçok materyal daha önce yayınlanan [Arweave makalesinden](/subgraphs/cookbook/arweave/) alınmıştır diff --git a/website/pages/tr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/tr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/tr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/tr/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/tr/subgraphs/cookbook/near.mdx b/website/pages/tr/subgraphs/cookbook/near.mdx index 708782a54425..8fe610b7f462 100644 --- a/website/pages/tr/subgraphs/cookbook/near.mdx +++ b/website/pages/tr/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ Subgraph tanımının üç yönü vardır: **schema.graphql:** Subgraph'ınız için hangi verilerin depolandığını ve bunlara GraphQL aracılığıyla nasıl sorgu yapılacağını tanımlayan bir şema dosyası. NEAR subgraph gereksinimleri [mevcut belgelendirmede](/developing/creating-a-subgraph/#the-graphql-schema) ele alınmıştır. -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. Subgraph geliştirme sırasında iki temel komut bulunmaktadır: @@ -98,7 +98,7 @@ NEAR veri kaynakları iki tür işleyiciyi destekler: Olayları işlemek için işleyiciler [AssemblyScript](https://www.assemblyscript.org/) içinde yazılmıştır. -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ Bu türler blok & makbuz işleyicilerine aktarılır: - Blok işleyicileri bir `Block` alır - Makbuz işleyicileri bir `ReceiptWithOutcome` alır -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## NEAR Subgraph'ını Dağıtma @@ -228,7 +228,7 @@ Yukarıdaki bileşenlerin çalıştırılması hakkında yakında daha fazla bil ## NEAR Subgraph'ını Sorgulama -NEAR subgraphları için GraphQL uç noktası, mevcut API arayüzü ile şema tanımı tarafından belirlenir. Daha fazla bilgi için lütfen [GraphQL API dökümantasyonunu](/querying/graphql-api/) ziyaret edin. +NEAR subgraphları için GraphQL uç noktası, mevcut API arayüzü ile şema tanımı tarafından belirlenir. Daha fazla bilgi için lütfen [GraphQL API dökümantasyonunu](/subgraphs/querying/graphql-api/) ziyaret edin. ## Örnek Subgraph'ler @@ -276,7 +276,7 @@ Bekleme fonksiyonelliği henüz NEAR subgraphları için desteklenmemektedir. Bu ### Sorum yanıtlanmadı, NEAR subgraphları oluşturma konusunda nereden daha fazla yardım alabilirim? -Subgraph geliştirme hakkında genel bir soruysa, [Geliştirici dökümantasyonu'nun](/quick-start/) geri kalanında çok daha fazla bilgi bulunmaktadır. Aksi durumda lütfen [The Graph Protocol Discord](https://discord.gg/graphprotocol) sunucusuna katılın ve #near kanalında sorunuzu sorun veya near@thegraph.com adresine e-posta gönderin. +Subgraph geliştirme hakkında genel bir soruysa, [Geliştirici dökümantasyonu'nun](/subgraphs/quick-start/) geri kalanında çok daha fazla bilgi bulunmaktadır. Aksi durumda lütfen [The Graph Protocol Discord](https://discord.gg/graphprotocol) sunucusuna katılın ve #near kanalında sorunuzu sorun veya near@thegraph.com adresine e-posta gönderin. ## Referanslar diff --git a/website/pages/tr/subgraphs/cookbook/pruning.mdx b/website/pages/tr/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/tr/subgraphs/cookbook/pruning.mdx +++ b/website/pages/tr/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 0ce0c9c29e08..fd53fae19940 100644 --- a/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/tr/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams destekli subgraphlar --- -[Substreams](/substreams/), Graph Ağı için StreamingFast tarafından geliştirilen bir blok zinciri verileri işleme çerçevesidir. Bir substreams modülü, subgraph varlıklarıyla uyumlu olan varlık değişiklikleri çıktısı verebilir. Bir subgraph, böyle bir Substreams modülünü veri kaynağı olarak kullanabilir ve Substreams'in indeksleme hızını ve ek verilerini subgraph geliştiricilere kazandırabilir. +[Substreams](/substreams/introduction/), Graph Ağı için StreamingFast tarafından geliştirilen bir blok zinciri verileri işleme çerçevesidir. Bir substreams modülü, subgraph varlıklarıyla uyumlu olan varlık değişiklikleri çıktısı verebilir. Bir subgraph, böyle bir Substreams modülünü veri kaynağı olarak kullanabilir ve Substreams'in indeksleme hızını ve ek verilerini subgraph geliştiricilere kazandırabilir. ## Gereksinimler @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Bir Substreams paketi tanımlama -Bir Substreams paketi tiplerden ([Protocol Buffers](https://protobuf.dev/) olarak tanımlanmış olanlar), modüllerden (Rust dilinde yazılmış), tiplere referans veren ve modüllerin nasıl tetikleneceğini belirten bir `substreams.yaml` dosyasından oluşur. [Substreams geliştirme hakkında daha fazla bilgi edinmek için Substreams dökümantasyonunu ziyaret edin](/substreams/) ve daha fazla örnek için [awesome-substreams](https://github.com/pinax-network/awesome-substreams) ve [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) sayfalarına göz atın. +Bir Substreams paketi tiplerden ([Protocol Buffers](https://protobuf.dev/) olarak tanımlanmış olanlar), modüllerden (Rust dilinde yazılmış), tiplere referans veren ve modüllerin nasıl tetikleneceğini belirten bir `substreams.yaml` dosyasından oluşur. [Substreams geliştirme hakkında daha fazla bilgi edinmek için Substreams dökümantasyonunu ziyaret edin](/substreams/introduction/) ve daha fazla örnek için [awesome-substreams](https://github.com/pinax-network/awesome-substreams) ve [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) sayfalarına göz atın. Bahsi geçen Substreams paketi, Ethereum Ana Ağı'nda kontrat dağıtımlarını algılar ve yeni oluşturulan kontratlar için oluşturma bloğunu ve zaman damgasını takip eder. Bunun için `/proto/example.proto` içinde buna özel bir `Contract` türü bulunmaktadır ([Protokol Buffers tanımlama hakkında daha fazla bilgi edinin](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/tr/subgraphs/cookbook/timeseries.mdx b/website/pages/tr/subgraphs/cookbook/timeseries.mdx index f1135f5c4bcf..e7b242bfa2f3 100644 --- a/website/pages/tr/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/tr/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/tr/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/tr/subgraphs/cookbook/transfer-to-the-graph.mdx index 879b63e66039..1cb8b2d6e9a9 100644 --- a/website/pages/tr/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/tr/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Örnek @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Ek Kaynaklar -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/tr/subgraphs/developing/creating/advanced.mdx b/website/pages/tr/subgraphs/developing/creating/advanced.mdx index f44cb3bcf88d..02697b27d494 100644 --- a/website/pages/tr/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/tr/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { Ana varlık ve sonuç dosya veri kaynak varlığı arasındaki ilişki bire bir ise, en basit kalıp, IPFS CID'yi arama anahtarı olarak kullanarak ana varlığını sonuç dosya varlığına bağlamaktır. Yeni dosya tabanlı varlıklarınızın modellemesiyle ilgili sorun yaşarsanız Discord üzerinden iletişime geçin! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### Dosyaları işlemek için yeni bir işleyici oluşturun -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Ek olarak, zincir üstü bir veri kaynağı veya başka bir dosya veri kaynağı NFT meta verilerini ilgili tokenleri bağlarken, Üst veri varlığına Token varlığından başvurmak için üst verinin IPFS hash değerini kullanın. Üst veri varlığını IPFS hash değerini bir kimlik olarak kullanarak kaydedin. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Mevcut Subgraph'ta Graftlama -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx index 8e20476ad888..2e9ea9e06d56 100644 --- a/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/tr/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API'si --- -> Not: Eğer `graph-cli`/`graph-ts` sürüm `0.22.0`'den önce bir subgraph oluşturduysanız, eski bir AssemblyScript sürümünü kullanıyorsunuz demektir. [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide/) gözden geçirmeniz önerilir. +> Not: Eğer `graph-cli`/`graph-ts` sürüm `0.22.0`'den önce bir subgraph oluşturduysanız, eski bir AssemblyScript sürümünü kullanıyorsunuz demektir. [`Geçiş Kılavuzu`](/resources/release-notes/assemblyscript-migration-guide/) gözden geçirmeniz önerilir. Subgraph eşlemeleri yazarken kullanılabilecek yerleşik API'leri öğrenin. Hazır olarak sunulan iki tür API mevcuttur: @@ -35,7 +35,7 @@ Subgraph manifestosundaki `apiVersion`, bir subgraph için Graph Düğümü tara | 0.0.8 | Bir varlığı kaydederken şemadaki alanların varlığını doğrulama mekanizması ekler. | | 0.0.7 | Ethereum türlerine `TransactionReceipt` ve `Log` sınıfları eklendi
Ethereum Event nesnesine `receipt` alanı eklendi | | 0.0.6 | Ethereum Transaction nesnesine `nonce` alanı eklendi
Ethereum Block nesnesine `baseFeePerGas` eklendi | -| 0.0.5 | AssemblyScript sürümü 0.19.10'a yükseltildi (bu sürümle birlikte uyumluluğu bozabilecek değişiklikler yapılmıştır, lütfen [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide/) bölümüne bakın)
`ethereum.transaction.gasUsed`, `ethereum.transaction.gasLimit` olarak yeniden adlandırıldı | +| 0.0.5 | AssemblyScript sürümü 0.19.10'a yükseltildi (bu sürümle birlikte uyumluluğu bozabilecek değişiklikler yapılmıştır, lütfen [`Geçiş Kılavuzu`](/resources/release-notes/assemblyscript-migration-guide/) bölümüne bakın)
`ethereum.transaction.gasUsed`, `ethereum.transaction.gasLimit` olarak yeniden adlandırıldı | | 0.0.4 | Ethereum SmartContractCall nesnesine `functionSignature` alanı eklendi | | 0.0.3 | Ethereum Call nesnesine `from` alanı eklendi
`etherem.call.address`, `ethereum.call.to` olarak yeniden adlandırıldı | | 0.0.2 | Ethereum Transaction nesnesine `input` alanı eklendi | diff --git a/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx index 6b0ed88435dc..6c69a1d90504 100644 --- a/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/tr/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Graph CLI'ı Yükleyin --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Genel Bakış -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Buradan Başlayın @@ -114,6 +114,6 @@ ABI dosya(lar)ı sözleşme(ler) inizle uygun olmalıdır. ABI dosyalarını edi | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | İşleyicilerin işlem makbuzlarına erişim desteği eklendi. | | 0.0.4 | Subgraph özelliklerini yönetme desteği eklendi. | diff --git a/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx b/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx index d82c78526adf..6016e3cbfe03 100644 --- a/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/tr/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Varlıkları Tanımlama @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/tr/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/tr/subgraphs/developing/creating/starting-your-subgraph.mdx index 9423e8078f24..7367bf775d28 100644 --- a/website/pages/tr/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/tr/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/tr/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/tr/subgraphs/developing/creating/subgraph-manifest.mdx index 702a2183dc23..2853b063257d 100644 --- a/website/pages/tr/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/tr/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). Manifest için güncellenmesi gereken önemli girdiler şunlardır: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde Verilen bir bloktaki geçmiş, şu durumlar için gereklidir: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Subgraph'i verilen bloka geri sarmak @@ -517,7 +517,7 @@ Eğer verilen bloktaki tarihsel veri budanmışsa yukarıdaki özellikler kullan > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: Belirli bir miktarda tarihsel veri saklamak için: diff --git a/website/pages/tr/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/tr/subgraphs/developing/creating/unit-testing-framework.mdx index 379ab4aaa125..4a594d233599 100644 --- a/website/pages/tr/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/tr/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1378,7 +1378,7 @@ Tutulan kayıt çıktısı test çalışma süresini içerir. İşte buna bir ö > Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined -Bu hata kodunuzda `console.log` kullandığınız anlamına gelir. Bu komut AssemblyScript tarafından desteklenmez. Lütfen [Logging API](/developing/graph-ts/api/#logging-api)'yi kullanmayı düşünün. +Bu hata kodunuzda `console.log` kullandığınız anlamına gelir. Bu komut AssemblyScript tarafından desteklenmez. Lütfen [Logging API](/subgraphs/developing/creating/graph-ts/api/#logging-api)'yi kullanmayı düşünün. > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx index 3f4745572daa..07911488981f 100644 --- a/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/tr/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> Daha fazla yazılı detay için [Hızlı Başlangıç](/quick-start/) bölümünü inceleyin. +> Daha fazla yazılı detay için [Hızlı Başlangıç](/subgraphs/quick-start/) bölümünü inceleyin. ### The Graph Ağı ile Subgraph Uyumluluğu Subgraph'lerin Graph Ağı Endeksleyicileri tarafından desteklenebilmesi için şu gereklilikleri karşılaması gerekir: -- [Desteklenen bir ağı](/developing/supported-networks/) endeksliyor olmalı +- [Desteklenen bir ağı](/supported-networks/) endeksliyor olmalı - Aşağıdaki özelliklerden hiçbirini kullanmamalı: - ipfs.cat & ipfs.map - Kritik olmayan hatalar @@ -114,7 +114,7 @@ Subgraph Studio’da günlükleri kontrol ederek subgraph’inizle ilgili hatala ## Subgraph’inizi Yayımlama -Subgraph’inizi başarıyla yayımlamak için [subgraph yayımlama](/publishing/publishing-a-subgraph/) adımlarını gözden geçirin. +Subgraph’inizi başarıyla yayımlamak için [subgraph yayımlama](/subgraphs/developing/publishing/publishing-a-subgraph/) adımlarını gözden geçirin. ## CLI ile Subgraph’inizi Sürümleme @@ -126,7 +126,7 @@ Subgraph’inizi güncellemek isterseniz, aşağıdaki adımları izleyebilirsin Ayrıca, subgraph'inizin meta verilerini yeni bir sürüm yayımlamak zorunda kalmadan güncelleyebilirsiniz. Studio’daki (profil resmi, isim, açıklama gibi) subgraph ayrıntılarını [Graph Gezgini](https://thegraph.com/explorer)'ndeki **Ayrıntıları Güncelle** seçeneğini işaretleyerek güncelleyebilirsiniz. Bu seçenek işaretlendiğinde, yeni bir sürüm yayımlamaya gerek kalmadan, Explorer'da subgraph ayrıntılarını güncelleyen bir blokzincir işlemi oluşturulur. -> Bir subgraph’in yeni bir sürümünü ağda yayımlamanın maliyetleri olduğunu unutmayın. İşlem ücretlerine ek olarak, otomatik olarak taşınan sinyalin kürasyon vergisinin bir kısmını da finanse etmeniz gerekmektedir. Küratörler subgraph'inize sinyal vermemişse subgraph'inizin yeni bir sürümünü yayımlayamazsınız. Daha fazla bilgi için [buraya](/network/curating/) göz atın. +> Bir subgraph’in yeni bir sürümünü ağda yayımlamanın maliyetleri olduğunu unutmayın. İşlem ücretlerine ek olarak, otomatik olarak taşınan sinyalin kürasyon vergisinin bir kısmını da finanse etmeniz gerekmektedir. Küratörler subgraph'inize sinyal vermemişse subgraph'inizin yeni bir sürümünü yayımlayamazsınız. Daha fazla bilgi için [buraya](/resources/roles/curating/) göz atın. ## Subgraph Sürümlerinin Otomatik Arşivlenmesi diff --git a/website/pages/tr/subgraphs/developing/developer-faq.mdx b/website/pages/tr/subgraphs/developing/developer-faq.mdx index a288248db0f0..ea8f513353a1 100644 --- a/website/pages/tr/subgraphs/developing/developer-faq.mdx +++ b/website/pages/tr/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ Bir subgraph, blokzinciri verilerine dayalı olarak oluşturulmuş özel yapım ### 2. Subgraph oluşturmanın ilk adımı nedir? -Başarılı bir şekilde subgraph oluşturmak için The Graph CLI’yi kurmanız gerekir. Başlamak için [Hızlı Başlangıç](/quick-start/) bölümüne göz atın. Ayrıntılı bilgi için [Subgraph Oluşturma](/developing/creating-a-subgraph/) bölümünü inceleyin. +Başarılı bir şekilde subgraph oluşturmak için The Graph CLI’yi kurmanız gerekir. Başlamak için [Hızlı Başlangıç](/subgraphs/quick-start/) bölümüne göz atın. Ayrıntılı bilgi için [Subgraph Oluşturma](/developing/creating-a-subgraph/) bölümünü inceleyin. ### 3. Akıllı sözleşmelerim olay içermiyorsa yine de subgraph oluşturabilir miyim? @@ -34,7 +34,7 @@ Subgraph’i yeniden dağıtmanız gerekir ancak subgraph ID'si (IPFS hash’i) ### 7. Subgraph eşlemelerinden sözleşme fonksiyonunu nasıl çağırabilir veya bir genel durum değişkenine nasıl erişebilirim? -[AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state) bölümündeki `Akıllı sözleşmeye erişim` kısmına göz atın. +[AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state) bölümündeki `Akıllı sözleşmeye erişim` kısmına göz atın. ### 8. Subgraph eşleyicilerinde `ethers.js` veya diğer JS kütüphanelerini kullanabilir miyim? @@ -80,13 +80,13 @@ Eğer olay sırasında yalnızca bir varlık oluşturuluyorsa ve daha iyi bir se ### 15. Subgraph'imi silebilir miyim? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Ağ ile İlgili Sorular ### 16. The Graph hangi ağları desteklemektedir? -Desteklenen ağların listesini [burada](/developing/supported-networks/) bulabilirsiniz. +Desteklenen ağların listesini [burada](/supported-networks/) bulabilirsiniz. ### 17. Olay işleyicileri içerisinde ağlar (mainnet, Sepolia, yerel) arasında ayrım yapmak mümkün müdür? diff --git a/website/pages/tr/subgraphs/developing/introduction.mdx b/website/pages/tr/subgraphs/developing/introduction.mdx index ce6923c88215..cb3033747b5a 100644 --- a/website/pages/tr/subgraphs/developing/introduction.mdx +++ b/website/pages/tr/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Geliştirme --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Genel Bakış @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 49fc7ba34e3f..71e4e5e4618c 100644 --- a/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/tr/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Yayınlanan bir subgraph için üst veri güncelleme @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/tr/subgraphs/developing/subgraphs.mdx b/website/pages/tr/subgraphs/developing/subgraphs.mdx index 4feb5d9d52c3..28e2aa3d9e9f 100644 --- a/website/pages/tr/subgraphs/developing/subgraphs.mdx +++ b/website/pages/tr/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/tr/subgraphs/explorer.mdx b/website/pages/tr/subgraphs/explorer.mdx index 31878c3af587..c75af7bf7fe7 100644 --- a/website/pages/tr/subgraphs/explorer.mdx +++ b/website/pages/tr/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -Nasıl İndeksleyici olunacağı hakkında daha fazla bilgi edinmek için [resmi dökümantasyona](/network/indexing/) veya [Graph Akademi İndeksleyici kılavuzlarına](https://thegraph.academy/delegators/choosing-indexers/) göz atabilirsiniz. +Nasıl İndeksleyici olunacağı hakkında daha fazla bilgi edinmek için [resmi dökümantasyona](/indexing/overview/) veya [Graph Akademi İndeksleyici kılavuzlarına](https://thegraph.academy/delegators/choosing-indexers/) göz atabilirsiniz. ![İndeksleme ayrıntıları bölmesi](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Gezgin Gürüntüsü 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegatörler @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Şu anda protokolde bulunan sahip oldukları toplam GRT miktarı - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Ağ diff --git a/website/pages/tr/subgraphs/querying/best-practices.mdx b/website/pages/tr/subgraphs/querying/best-practices.mdx index 40012c842cad..8f3a056e900e 100644 --- a/website/pages/tr/subgraphs/querying/best-practices.mdx +++ b/website/pages/tr/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/tr/subgraphs/querying/graphql-api.mdx b/website/pages/tr/subgraphs/querying/graphql-api.mdx index adb3764b11fc..b535e5ebe53b 100644 --- a/website/pages/tr/subgraphs/querying/graphql-api.mdx +++ b/website/pages/tr/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/tr/subgraphs/querying/introduction.mdx b/website/pages/tr/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/tr/subgraphs/querying/introduction.mdx +++ b/website/pages/tr/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/tr/subgraphs/quick-start.mdx b/website/pages/tr/subgraphs/quick-start.mdx index 4c4b532e41c0..18eb08c9c713 100644 --- a/website/pages/tr/subgraphs/quick-start.mdx +++ b/website/pages/tr/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Hızlı Başlangıç --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Ön Koşullar - Bir kripto cüzdanı -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Subgraph'inizi The Graph Ağında yayımlayın -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Subgraph Studio ile yayımlama @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -Yayımlamanızı özelleştirmek için, [Subgraph Yayımlama](/publishing/publishing-a-subgraph/) sayfasına göz atın. +Yayımlamanızı özelleştirmek için, [Subgraph Yayımlama](/subgraphs/developing/publishing/publishing-a-subgraph/) sayfasına göz atın. #### Subgraph'inize sinyal ekleme @@ -169,7 +169,7 @@ Yayımlamanızı özelleştirmek için, [Subgraph Yayımlama](/publishing/publis - En az 3 Endeksleyici çekmek için en az 3.000 GRT küratörlük yapmanız önerilir. Subgraph özelliği kullanımı ve desteklenen ağlara bağlı olarak ödül hak kazanımlarının nasıl dağıtıldığını kontrol edin. -Küratörlük hakkında daha fazla bilgi için [Küratörlük](/network/curating/) sayfasını okuyun. +Küratörlük hakkında daha fazla bilgi için [Küratörlük](/resources/roles/curating/) sayfasını okuyun. Gas maliyetlerinden tasarruf etmek için, subgraph'inizi küratörlük işlemini, yayımlama işlemiyle aynı anda yapabilirsiniz. Bunun için şu seçeneği seçin: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -Subgraph'inizden veri sorgulama hakkında daha fazla bilgi için [The Graph'e Sorgu Gönderme](/querying/querying-the-graph/) sayfasına bakın. +Subgraph'inizden veri sorgulama hakkında daha fazla bilgi için [The Graph'e Sorgu Gönderme](/subgraphs/querying/introduction/) sayfasına bakın. diff --git a/website/pages/tr/substreams/sps/sps-faq.mdx b/website/pages/tr/substreams/sps/sps-faq.mdx index 8192ebdfa52a..b6127a7808b8 100644 --- a/website/pages/tr/substreams/sps/sps-faq.mdx +++ b/website/pages/tr/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams destekli subgraphlar SSS [StreamingFast](https://www.streamingfast.io/) tarafından geliştirilen Substreams, zengin blokzinciri veri akışlarını işleyebilen son derece güçlü bir işlem motorudur. Substreams, blokzinciri verilerini son kullanıcı uygulamaları tarafından hızlı ve sorunsuz bir şekilde işlenmek üzere rafine etmenizi ve şekillendirmenizi sağlar. Daha spesifik olmak gerekirse, Substreams, farklı blokzincirleriyle uyumlu, paralelleştirilmiş ve akış öncelikli bir motor olup bir blokzinciri veri dönüşüm katmanı olarak işlev görür. [Firehose](https://firehose.streamingfast.io/) tarafından desteklenen Substreams, geliştiricilerin Rust modülleri yazmasına, topluluk modüllerini kullanarak geliştirme yapmasına, son derece yüksek performanslı endeksleme sağlamasına ve verilerini herhangi bir yere yönlendirmesine ([sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink)) olanak tanır. -Substreams hakkında daha fazla bilgi için [SubstreamsDökümantasyonuna](/substreams/) gidin. +Substreams hakkında daha fazla bilgi için [SubstreamsDökümantasyonuna](/substreams/introduction/) gidin. ## Substreams destekli subgraphlar nelerdir? -[Substreams destekli subgraphlar](/cookbook/substreams-powered-subgraphs/), Substreams'in gücünü subgraphlar'ın sorgulanabilirliği ile birleştirir. Substreams ile desteklenen bir subgraph yayınladığınızda, Substreams dönüşümleri tarafından üretilen veriler, subgraph varlıkları ile uyumlu olan [varlık değişikliklerini çıktı](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs) olarak verebilir. +[Substreams destekli subgraphlar](/subgraphs/cookbook/substreams-powered-subgraphs/), Substreams'in gücünü subgraphlar'ın sorgulanabilirliği ile birleştirir. Substreams ile desteklenen bir subgraph yayınladığınızda, Substreams dönüşümleri tarafından üretilen veriler, subgraph varlıkları ile uyumlu olan [varlık değişikliklerini çıktı](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs) olarak verebilir. Eğer subgraph geliştirme konusun aşina iseniz, aklınızda bulundurun ki, Substreams destekli subgraphlar AssemblyScript dönüştürme katmanı tarafından üretilmiş gibi sorgulanabilir ve dinamik ve esnek bir GraphQL API sağlayarak Subgraph avantajlarından yararlanabilir. @@ -62,9 +62,9 @@ Firehose kullanmanın birçok faydası vardır, bunlar şunlardır: ## Geliştiriciler, Substreams destekli subgraphlar ve Substreams hakkında daha fazla bilgiye nereden erişebilir geliştiriciler? -[Substreams dökümantasyonu](/substreams/), Substreams modülleri nasıl oluşturulacağını öğretecektir. +[Substreams dökümantasyonu](/substreams/introduction/), Substreams modülleri nasıl oluşturulacağını öğretecektir. -[Substreams destekli subgrahplar belgeleri](/cookbook/substreams-powered-subgraphs/), onları Graph üzerinde dağıtmak için nasıl paketleyeceğinizi gösterecektir. +[Substreams destekli subgrahplar belgeleri](/subgraphs/cookbook/substreams-powered-subgraphs/), onları Graph üzerinde dağıtmak için nasıl paketleyeceğinizi gösterecektir. [En son sürüm Substreams Codegen aracı](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6), hiç kod yazmadan bir Substreams projesi başlatmanıza olanak tanır. @@ -82,7 +82,7 @@ Substream kullanırken, kompozisyon dönüşüm katmanında gerçekleşir ve ön ## Bir Substreams destekli Subgraph nasıl oluşturulur ve dağıtılır? -Bir Substreams destekli Subgraph [defining](/cookbook/substreams-powered-subgraphs/) sonra, onu [Subgraph Stüdyo](https://thegraph.com/studio/) üzerinde dağıtmak için Graph CLI'yi kullanabilirsiniz. +Bir Substreams destekli Subgraph [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) sonra, onu [Subgraph Stüdyo](https://thegraph.com/studio/) üzerinde dağıtmak için Graph CLI'yi kullanabilirsiniz. ## Substreams ve Substreams destekli subgraphlar ile ilgili örnekleri nerede bulubilirim? diff --git a/website/pages/tr/supported-networks.mdx b/website/pages/tr/supported-networks.mdx index e9cc0167e1b9..13cfe1582149 100644 --- a/website/pages/tr/supported-networks.mdx +++ b/website/pages/tr/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Temel ağ desteği, [yükseltme Endeksleyicisi](https://thegraph.com/blog/upgrade-indexer/) tarafından sağlanmaktadır. -\*\* Graph Düğümü ile Entegrasyon: `evm`, `near`, `cosmos`, `osmosis` ve `ar`, Graph Düğümü'nde yerel işleyici (handler) ve tür (type) desteğine sahiptir. Firehose ve Substreams uyumlu zincirler, genelleştirilmiş [Substreams destekli subgraph](/cookbook/substreams-powered-subgraphs/) entegrasyonundan yararlanabilir (`evm` ve `near` ağları buna dahil). ⁠† [Substreams destekli subgraph’lerin](/cookbook/substreams-powered-subgraphs/) dağıtımını destekler. +\*\* Graph Düğümü ile Entegrasyon: `evm`, `near`, `cosmos`, `osmosis` ve `ar`, Graph Düğümü'nde yerel işleyici (handler) ve tür (type) desteğine sahiptir. Firehose ve Substreams uyumlu zincirler, genelleştirilmiş [Substreams destekli subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) entegrasyonundan yararlanabilir (`evm` ve `near` ağları buna dahil). ⁠† [Substreams destekli subgraph’lerin](/subgraphs/cookbook/substreams-powered-subgraphs/) dağıtımını destekler. - Subgraph Studio, örneğin JSON-RPC, Firehose ve Substreams uç noktaları gibi temel teknolojilerin istikrarlılığına ve güvenilirliğine bel bağlar. - Gnosis Chain’i endeksleyen subgraph'ler artık `gnosis` ağ tanımlayıcısı ile dağıtılabilir. diff --git a/website/pages/uk/about.mdx b/website/pages/uk/about.mdx index ebc3f6d6f360..7d346fa59854 100644 --- a/website/pages/uk/about.mdx +++ b/website/pages/uk/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/uk/archived/arbitrum/arbitrum-faq.mdx b/website/pages/uk/archived/arbitrum/arbitrum-faq.mdx index 560d2bf46563..28f6a3faeee6 100644 --- a/website/pages/uk/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/uk/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Once you have GRT on Arbitrum, you can add it to your billing balance. ## Якщо я розробник підграфів, споживач даних, Індексатор, Куратор або Делегат, що мені потрібно робити зараз? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx index b075b7548fb8..8e6da852a01c 100644 --- a/website/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/uk/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx index e516573fd4d9..485f34a70c97 100644 --- a/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/uk/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 Transfer Tools Guide The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. +Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/archived/arbitrum/l2-transfer-tools-faq/). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/uk/archived/sunrise.mdx b/website/pages/uk/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/uk/archived/sunrise.mdx +++ b/website/pages/uk/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/uk/contracts.mdx b/website/pages/uk/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/uk/contracts.mdx +++ b/website/pages/uk/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/uk/indexing/chain-integration-overview.mdx b/website/pages/uk/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/uk/indexing/chain-integration-overview.mdx +++ b/website/pages/uk/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/uk/indexing/new-chain-integration.mdx b/website/pages/uk/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/uk/indexing/new-chain-integration.mdx +++ b/website/pages/uk/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/uk/indexing/overview.mdx b/website/pages/uk/indexing/overview.mdx index d4893efed202..c1a06d411cf7 100644 --- a/website/pages/uk/indexing/overview.mdx +++ b/website/pages/uk/indexing/overview.mdx @@ -87,7 +87,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### Що таке query fee cut і indexing reward cut? -Значення `queryFeeCut` і `indexingRewardCut` є параметрами делегування, які Індексатор може встановлювати разом із cooldownBlocks, щоб контролювати розподіл GRT між Індексатором і його Делегатами. Перегляньте останні кроки в розділі [Staking in the Protocol](/network/indexing/#stake-in-the-protocol), щоб отримати інструкції щодо встановлення параметрів делегування. +Значення `queryFeeCut` і `indexingRewardCut` є параметрами делегування, які Індексатор може встановлювати разом із cooldownBlocks, щоб контролювати розподіл GRT між Індексатором і його Делегатами. Перегляньте останні кроки в розділі [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol), щоб отримати інструкції щодо встановлення параметрів делегування. - **queryFeeCut** - відсоток від комісій за опрацювання запитів, який буде розподілено між Індексатором та Делегатами. Якщо цей параметр встановлено на рівні в 95%, індексатор отримає 95% від комісій за запити, зароблених при закритті розподілу, а решта 5% підуть Делегатам. @@ -121,7 +121,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### Яких основних заходів безпеки повинен дотримуватися індексатор? -- **Operator wallet**. Налаштування гаманця оператора є важливим запобіжним заходом, оскільки він дозволяє Індексатору підтримувати відокремлення між своїми ключами, які контролюють застейкані токени, і тими, які використовуються для щоденних операцій. Інструкції див. у розділі [Stake in Protocol](/network/indexing/#stake-in-the-protocol). +- **Operator wallet**. Налаштування гаманця оператора є важливим запобіжним заходом, оскільки він дозволяє Індексатору підтримувати відокремлення між своїми ключами, які контролюють застейкані токени, і тими, які використовуються для щоденних операцій. Інструкції див. у розділі [Stake in Protocol](/indexing/overview/#stake-in-the-protocol). - **Firewall** - Публічно доступною має бути лише сервіс-індексатор, і особливу увагу слід приділити блокуванню портів адміністратора і доступу до бази даних: не слід відкривати кінцеву точку JSON-RPC Graph Node (порт за замовчуванням: 8030), кінцеву точку API управління індексатором (порт за замовчуванням: 18000) і кінцеву точку бази даних Postgres (порт за замовчуванням: 5432). @@ -375,7 +375,7 @@ docker-compose up #### Початок роботи -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### З NPM-пакетів @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Використання K8 та Terraform -Див. розділ [Налаштування серверної інфраструктури з використанням Terraform на Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) +Див. розділ [Налаштування серверної інфраструктури з використанням Terraform на Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) #### Використання @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Після того, як індексатор застейкав GRT токени у протоколі, [Indexer components](/network/indexing/#indexer-components) можна запустити та почати взаємодію з мережею. +Після того, як індексатор застейкав GRT токени у протоколі, [Indexer components](/indexing/overview/#indexer-components) можна запустити та почати взаємодію з мережею. #### Approve токенів @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Індексаторам рекомендується використовувати функцію offchain синхронізації для синхронізації розгортань підграфів з head of chain перед створенням розподілів у мережі. Ця функція особливо корисна для підграфів, синхронізація яких може зайняти понад 28 епох, або для яких існує ймовірність невизначеного збою. diff --git a/website/pages/uk/indexing/tap.mdx b/website/pages/uk/indexing/tap.mdx index 3e8185186982..4132216ca5b6 100644 --- a/website/pages/uk/indexing/tap.mdx +++ b/website/pages/uk/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/uk/resources/benefits.mdx b/website/pages/uk/resources/benefits.mdx index be12847adfb5..39f77a7a7d71 100644 --- a/website/pages/uk/resources/benefits.mdx +++ b/website/pages/uk/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Кураторство сигналу на підграфі є опціональною одноразовою послугою з нульовою вартістю (наприклад, сигнал на суму 1 тис. доларів можна розмістити на підграфі, а потім вивести — з можливістю отримання прибутку в цьому процесі). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/uk/resources/roles/curating.mdx b/website/pages/uk/resources/roles/curating.mdx index 45ed82d0e24d..8514d7a9d473 100644 --- a/website/pages/uk/resources/roles/curating.mdx +++ b/website/pages/uk/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Як сигналізувати -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) Куратор може обрати подання сигналу на певну версію підграфа, або ж він може обрати автоматичне перенесення сигналу на найновішу версію цього підграфа. Обидва варіанти є прийнятними та мають свої плюси та мінуси. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. Ринок запитів за своєю суттю молодий в Graph, і існує ризик того, що ваш %APY може бути нижчим, ніж ви очікуєте, через динаміку ринку, що зароджується. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Підграф може не працювати через різноманітні помилки (баги). Підграф, що не працює не стягує комісію за запити. В результаті вам доведеться почекати, поки розробник виправить усі помилки й випустить нову версію. - Якщо ви підключені до найновішої версії підграфу, ваші частки будуть автоматично перенесені до цієї нової версії. При цьому буде стягуватися податок на в розмірі 0,5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/uk/resources/tokenomics.mdx b/website/pages/uk/resources/tokenomics.mdx index cc8be5788483..1abf2da2618f 100644 --- a/website/pages/uk/resources/tokenomics.mdx +++ b/website/pages/uk/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/uk/subgraphs/billing.mdx b/website/pages/uk/subgraphs/billing.mdx index b6e73127d865..b8118cc737c7 100644 --- a/website/pages/uk/subgraphs/billing.mdx +++ b/website/pages/uk/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Натисніть на кнопку "Connect Wallet" у правому верхньому куті сторінки. Ви будете перенаправлені на сторінку вибору гаманця. Виберіть той, який вам підходить, і натисніть кнопку "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Натисніть на кнопку "Connect Wallet" у правому верхньому куті сторінки. Ви будете перенаправлені на сторінку вибору гаманця. Виберіть той, який вам підходить, і натисніть кнопку "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Поповнення GRT за допомогою гаманця з мультипідписами -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/uk/subgraphs/cookbook/arweave.mdx b/website/pages/uk/subgraphs/cookbook/arweave.mdx index 532af9be1825..dff298483612 100644 --- a/website/pages/uk/subgraphs/cookbook/arweave.mdx +++ b/website/pages/uk/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and Обробники для виконання подій написані на мові [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Приклади підграфів diff --git a/website/pages/uk/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/uk/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/uk/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/uk/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/uk/subgraphs/cookbook/cosmos.mdx b/website/pages/uk/subgraphs/cookbook/cosmos.mdx index 979de8d0a4cc..37e42fc9638b 100644 --- a/website/pages/uk/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/uk/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and Обробники для виконання подій написані на мові [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Запит до Cosmos підграфа -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Блокчейни, що підтримуються Cosmos diff --git a/website/pages/uk/subgraphs/cookbook/derivedfrom.mdx b/website/pages/uk/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/uk/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/uk/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/uk/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/uk/subgraphs/cookbook/grafting-hotfix.mdx index 040e3a8209d5..a0bd3f4ab1c2 100644 --- a/website/pages/uk/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/uk/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/uk/subgraphs/cookbook/grafting.mdx b/website/pages/uk/subgraphs/cookbook/grafting.mdx index 9b45598f3810..ea87f4d73c5e 100644 --- a/website/pages/uk/subgraphs/cookbook/grafting.mdx +++ b/website/pages/uk/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Grafting is a powerful feature that allows you to "graft" one subgraph onto anot ## Побудова наявного підграфа -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Репозиторій з прикладом та відповідним підграфом](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Примітка: Багато матеріалів для цієї статті було взято з раніше опублікованої [ статті від Arweave](/cookbook/arweave/) +> Примітка: Багато матеріалів для цієї статті було взято з раніше опублікованої [ статті від Arweave](/subgraphs/cookbook/arweave/) diff --git a/website/pages/uk/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/uk/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/uk/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/uk/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/uk/subgraphs/cookbook/near.mdx b/website/pages/uk/subgraphs/cookbook/near.mdx index 1432a082c347..1ad5e3c45c00 100644 --- a/website/pages/uk/subgraphs/cookbook/near.mdx +++ b/website/pages/uk/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 Обробники для виконання подій написані на мові [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Приклади підграфів @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/uk/subgraphs/cookbook/pruning.mdx b/website/pages/uk/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/uk/subgraphs/cookbook/pruning.mdx +++ b/website/pages/uk/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/uk/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/uk/subgraphs/cookbook/timeseries.mdx b/website/pages/uk/subgraphs/cookbook/timeseries.mdx index 2ce0ce266ccf..0168be53d7ed 100644 --- a/website/pages/uk/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/uk/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/uk/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/uk/subgraphs/cookbook/transfer-to-the-graph.mdx index 6a5d2c2793f3..64c225442860 100644 --- a/website/pages/uk/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/uk/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Example @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/uk/subgraphs/developing/creating/advanced.mdx b/website/pages/uk/subgraphs/developing/creating/advanced.mdx index 3a08ddab7066..bc3a9a86efb6 100644 --- a/website/pages/uk/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/uk/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Grafting onto Existing Subgraphs -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx index 8aa0bf0027bf..4c5ce57993f2 100644 --- a/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/uk/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx index 0100b66c4427..ea09d89ab610 100644 --- a/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/uk/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Install the Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Overview -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx b/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx index b5b23098f5d1..d148cf2ab1fb 100644 --- a/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/uk/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/uk/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/uk/subgraphs/developing/creating/starting-your-subgraph.mdx index 5127f01632aa..f463ca3e9507 100644 --- a/website/pages/uk/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/uk/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/uk/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/uk/subgraphs/developing/creating/subgraph-manifest.mdx index f282f3946e75..b4c0e467c780 100644 --- a/website/pages/uk/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/uk/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). The important entries to update for the manifest are: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/uk/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/uk/subgraphs/developing/creating/unit-testing-framework.mdx index 553eec2157b3..591b55feda38 100644 --- a/website/pages/uk/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/uk/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx index f7f27fb18f62..f8ec5d2c7f2e 100644 --- a/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/uk/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/uk/subgraphs/developing/developer-faq.mdx b/website/pages/uk/subgraphs/developing/developer-faq.mdx index 2f4f017871ef..ef99407db489 100644 --- a/website/pages/uk/subgraphs/developing/developer-faq.mdx +++ b/website/pages/uk/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't ch ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ If only one entity is created during the event and if there's nothing better ava ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/uk/subgraphs/developing/introduction.mdx b/website/pages/uk/subgraphs/developing/introduction.mdx index 51dd2c70e7e5..da3e509b969d 100644 --- a/website/pages/uk/subgraphs/developing/introduction.mdx +++ b/website/pages/uk/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Розробка --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Overview @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 594bdd5736bb..59fa35629c01 100644 --- a/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/uk/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/uk/subgraphs/developing/subgraphs.mdx b/website/pages/uk/subgraphs/developing/subgraphs.mdx index 1e93ac7c30b8..93dd30ae37c5 100644 --- a/website/pages/uk/subgraphs/developing/subgraphs.mdx +++ b/website/pages/uk/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/uk/subgraphs/explorer.mdx b/website/pages/uk/subgraphs/explorer.mdx index 665d497192f3..e70122cdc018 100644 --- a/website/pages/uk/subgraphs/explorer.mdx +++ b/website/pages/uk/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Total amount of GRT they have currently in the protocol - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Network diff --git a/website/pages/uk/subgraphs/querying/best-practices.mdx b/website/pages/uk/subgraphs/querying/best-practices.mdx index 0a430c082847..cdb126a168fb 100644 --- a/website/pages/uk/subgraphs/querying/best-practices.mdx +++ b/website/pages/uk/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Кожне `queryName` може бути використане лише один раз за одну операцію. - Кожне `field` може бути використане лише один раз за вибірку (ми не можемо запитувати `id` двічі `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Будь-яка змінна, що присвоюється параметру, повинна відповідати його типу. - У заданому списку змінних кожна з них має бути унікальною. - Всі задані змінні повинні бути використаними. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Відправлення запиту до GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Робота з кросс-чейн підграфами: Отримання інформації з декількох підграфів за один запит - [Автоматичне відстежування блоків](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/uk/subgraphs/querying/graphql-api.mdx b/website/pages/uk/subgraphs/querying/graphql-api.mdx index 917fad3f2406..8813e2eeb3f3 100644 --- a/website/pages/uk/subgraphs/querying/graphql-api.mdx +++ b/website/pages/uk/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/uk/subgraphs/querying/introduction.mdx b/website/pages/uk/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/uk/subgraphs/querying/introduction.mdx +++ b/website/pages/uk/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/uk/subgraphs/quick-start.mdx b/website/pages/uk/subgraphs/quick-start.mdx index 28d6bbbe5601..f97d3c023d90 100644 --- a/website/pages/uk/subgraphs/quick-start.mdx +++ b/website/pages/uk/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Швидкий старт --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Prerequisites - Криптогаманець -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/uk/substreams/sps/sps-faq.mdx b/website/pages/uk/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/uk/substreams/sps/sps-faq.mdx +++ b/website/pages/uk/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/uk/supported-networks.mdx b/website/pages/uk/supported-networks.mdx index c9e32bb4465b..3d4240d80b38 100644 --- a/website/pages/uk/supported-networks.mdx +++ b/website/pages/uk/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/ur/about.mdx b/website/pages/ur/about.mdx index 9d53ba42d773..75dd5e34c6e0 100644 --- a/website/pages/ur/about.mdx +++ b/website/pages/ur/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/ur/archived/arbitrum/arbitrum-faq.mdx b/website/pages/ur/archived/arbitrum/arbitrum-faq.mdx index 7e3277e62140..c51d33e4e16c 100644 --- a/website/pages/ur/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/ur/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ L2 پر گراف استعمال کرنے کا فائدہ اٹھانے کے لی ## بطور سب گراف ڈویلپر، ڈیٹا کنزیومر، انڈیکسر، کیوریٹر، یا ڈیلیگیٹر، مجھے اب کیا کرنے کی ضرورت ہے؟ -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ All smart contracts have been thoroughly [audited](https://github.com/graphproto ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arb اپنے Arbitrum بلنگ بیلنس میں GRT شامل کرنا [سب گراف سٹوڈیو](https://thegraph.com/studio/) میں ایک کلک کے تجربے کے ساتھ کیا جا سکتا ہے۔ آپ آسانی سے اپنے GRT کو Arbitrum سے بریج کر سکیں گے اور ایک ٹرانزیکشن میں اپنی API کیز کو بھر سکیں گے۔ -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/ur/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ur/archived/arbitrum/l2-transfer-tools-faq.mdx index 187e52042c74..51bb4ed61437 100644 --- a/website/pages/ur/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/ur/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -15,7 +15,7 @@ These tools will require you to follow a specific set of steps depending on what ### کیا میں وہی والیٹ استعمال کر سکتا ہوں جو میں ایتھیریم مین نیٹ پر استعمال کرتا ہوں؟ -اگر آپ ایک [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) والیٹ استعمال کر رہے ہیں تو آپ وہی ایڈریس استعمال کر سکتے ہیں۔ اگر آپ کا ایتھیریم مین نیٹ والیٹ ایک کنٹریکٹ ہے (مثلاً ایک ملٹی سگ) تو آپ کو [آربٹرم والیٹ ایڈریس](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) کی وضاحت کرنا ہوگی جہاں آپ کی منتقلی بھیجی جائے گی۔ براہ کرم ایڈریس کو احتیاط سے چیک کریں کیونکہ کسی بھی غلط ایڈریس پر منتقلی کے نتیجے میں مستقل نقصان ہو سکتا ہے۔ اگر آپ L2 پر ملٹی سگ استعمال کرنا چاہتے ہیں، تو یقینی بنائیں کہ آپ Arbitrum One پر ملٹی سگ کنٹریکٹ تعینات کرتے ہیں. +اگر آپ ایک [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) والیٹ استعمال کر رہے ہیں تو آپ وہی ایڈریس استعمال کر سکتے ہیں۔ اگر آپ کا ایتھیریم مین نیٹ والیٹ ایک کنٹریکٹ ہے (مثلاً ایک ملٹی سگ) تو آپ کو [آربٹرم والیٹ ایڈریس](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) کی وضاحت کرنا ہوگی جہاں آپ کی منتقلی بھیجی جائے گی۔ براہ کرم ایڈریس کو احتیاط سے چیک کریں کیونکہ کسی بھی غلط ایڈریس پر منتقلی کے نتیجے میں مستقل نقصان ہو سکتا ہے۔ اگر آپ L2 پر ملٹی سگ استعمال کرنا چاہتے ہیں، تو یقینی بنائیں کہ آپ Arbitrum One پر ملٹی سگ کنٹریکٹ تعینات کرتے ہیں. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx index 651daeaa1c30..4be0191c0f28 100644 --- a/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/ur/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2 ٹرانسفر ٹولز گائڈ گراف نے Arbitrum One پر L2 پر منتقل ہونا آسان کر دیا ہے۔ پروٹوکول کے شریک کے لیے، تمام نیٹ ورک کے شرکاء کے لیے L2 میں منتقلی کو ہموار بنانے کے لیے L2 ٹرانسفر ٹولز کا ایک سیٹ موجود ہے۔ یہ ٹولز آپ سے اس بات پر منحصر ہوں گے کہ آپ کیا منتقل کر رہے ہیں۔ -ان ٹولز کے بارے میں اکثر پوچھے جانے والے سوالات کا جواب [L2 ٹرانسفر ٹولز اکثر پوچھے گئے سوالات](/arbitrum/l2-transfer-tools-faq/). اکثر پوچھے جانے والے سوالات میں ٹولز کو استعمال کرنے کے طریقے، وہ کیسے کام کرتے ہیں، اور ان کو استعمال کرتے وقت ذہن میں رکھنے والی چیزوں کی گہرائی سے وضاحت پر مشتمل ہے۔ +ان ٹولز کے بارے میں اکثر پوچھے جانے والے سوالات کا جواب [L2 ٹرانسفر ٹولز اکثر پوچھے گئے سوالات](/archived/arbitrum/l2-transfer-tools-faq/). اکثر پوچھے جانے والے سوالات میں ٹولز کو استعمال کرنے کے طریقے، وہ کیسے کام کرتے ہیں، اور ان کو استعمال کرتے وقت ذہن میں رکھنے والی چیزوں کی گہرائی سے وضاحت پر مشتمل ہے۔ ## اپنے سب گراف کو Arbitrum (L2) میں کیسے منتقل کریں diff --git a/website/pages/ur/archived/sunrise.mdx b/website/pages/ur/archived/sunrise.mdx index a0cc8160fb91..9591fa169909 100644 --- a/website/pages/ur/archived/sunrise.mdx +++ b/website/pages/ur/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### ایج اور نوڈ اپ گریڈ انڈیکسر کیوں چلا رہا ہے؟ @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/ur/contracts.mdx b/website/pages/ur/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/ur/contracts.mdx +++ b/website/pages/ur/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/ur/indexing/chain-integration-overview.mdx b/website/pages/ur/indexing/chain-integration-overview.mdx index 9e4c618c9e7b..e348639e9efa 100644 --- a/website/pages/ur/indexing/chain-integration-overview.mdx +++ b/website/pages/ur/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: چین انٹیگریشن کے عمل کا جائزہ ## مرحلہ 1. تکنیکی انٹیگریشن -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - ٹیمیں فورم تھریڈ بنا کر پروٹوکول انٹیگریشن کا عمل شروع کرتی ہیں [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)(گورننس اور GIPs کے تحت نئے ڈیٹا ذرائع ذیلی زمرہ) ۔ پہلے سے طے شدہ فورم ٹیمپلیٹ کا استعمال لازمی ہے. ## مرحلہ 2۔ انٹیگریشن کی توثیق diff --git a/website/pages/ur/indexing/new-chain-integration.mdx b/website/pages/ur/indexing/new-chain-integration.mdx index 36e0875c1478..53d24d0d1aff 100644 --- a/website/pages/ur/indexing/new-chain-integration.mdx +++ b/website/pages/ur/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Configuring Graph Node is as easy as preparing your local environment. Once your ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/ur/indexing/overview.mdx b/website/pages/ur/indexing/overview.mdx index 8c35f54af774..d46085526ae9 100644 --- a/website/pages/ur/indexing/overview.mdx +++ b/website/pages/ur/indexing/overview.mdx @@ -87,7 +87,7 @@ query indexerAllocations { ### کیوری فی کٹ اور انڈیکسنگ ریوارڈ کٹ کیا ہے؟ -`queryFeeCut` اور `indexingRewardCut` قدریں ڈیلی گیشن پیرامیٹر ہیں جنہیں انڈیکسر, انڈیکسر اور ان کے ڈیلیگیٹرز کے درمیان GRT کی تقسیم کو کنٹرول کرنے کے لیے cooldownBlocks کے ساتھ سیٹ کر سکتا ہے. ڈیلیگیشن کے پیرامیٹرز کو ترتیب دینے کے لیے ہدایات کے لیے [پروٹوکول میں حصہ لینا](/network/indexing/#stake-in-the-protocol) میں آخری مراحل دیکھیں. +`queryFeeCut` اور `indexingRewardCut` قدریں ڈیلی گیشن پیرامیٹر ہیں جنہیں انڈیکسر, انڈیکسر اور ان کے ڈیلیگیٹرز کے درمیان GRT کی تقسیم کو کنٹرول کرنے کے لیے cooldownBlocks کے ساتھ سیٹ کر سکتا ہے. ڈیلیگیشن کے پیرامیٹرز کو ترتیب دینے کے لیے ہدایات کے لیے [پروٹوکول میں حصہ لینا](/indexing/overview/#stake-in-the-protocol) میں آخری مراحل دیکھیں. - **کیوری فیس کٹ** - کیوری فیس کی چھوٹ کا % جو انڈیکسر میں تقسیم کیا جائے گا۔ اگر اسے 95% پر سیٹ کیا جاتا ہے، تو انڈیکسر کو 95% کیوری فیس موصول ہو گی جب ایک مختص بند ہو جائے گا اور باقی 5% ڈیلیگیٹرز کو جائے گا. @@ -121,7 +121,7 @@ query indexerAllocations { ### وہ کون سی چند بنیادی حفاظتی تدابیر ہیں جو ایک انڈیکسر کو اختیار کرنی چاہیے؟ -- **آپریٹر والیٹ** - آپریٹر والیٹ کا سیٹ اپ کرنا ایک اہم احتیاط ہے کیونکہ یہ ایک انڈیکسر کو اپنی کلیدوں کے درمیان علیحدگی برقرار رکھنے کی اجازت دیتا ہے جو سٹیک کو کنٹرول کرتی ہیں اور جو روزمرہ کے کاموں کے کنٹرول میں ہیں. ہدایات کے لیے [پروٹوکول میں حصہ ڈالنا](/network/indexing/#stake-in-the-protocol) دیکھیں. +- **آپریٹر والیٹ** - آپریٹر والیٹ کا سیٹ اپ کرنا ایک اہم احتیاط ہے کیونکہ یہ ایک انڈیکسر کو اپنی کلیدوں کے درمیان علیحدگی برقرار رکھنے کی اجازت دیتا ہے جو سٹیک کو کنٹرول کرتی ہیں اور جو روزمرہ کے کاموں کے کنٹرول میں ہیں. ہدایات کے لیے [پروٹوکول میں حصہ ڈالنا](/indexing/overview/#stake-in-the-protocol) دیکھیں. - **فائر وال** - صرف انڈیکسر سروس کو عوامی طور پر ظاہر کی ضرورت ہے اور ایڈمن پورٹس اور ڈیٹا بیس تک رسائی کو لاک ڈاؤن کرنے پر خاص توجہ دی جانی چاہیے: گراف نوڈ JSON-RPC اینڈ پوائنٹ (ڈیفالٹ پورٹ: 8030)، انڈیکسر مینجمنٹ API endpoint (ڈیفالٹ پورٹ: 18000)، اور Postgres ڈیٹا بیس اینڈ پوائنٹ (ڈیفالٹ پورٹ: 5432) کو ظاہر نہیں کرنا چاہیے. @@ -375,7 +375,7 @@ docker-compose up #### شروع کرتے ہوئے -انڈیکسر ایجنٹ اور انڈیکسر سروس آپ کے گراف نوڈ انفراسٹرکچر کے ساتھ مل کر واقع ہونی چاہیے۔ آپ کے انڈیکسر اجزاء کے لیے ورچوئل ایگزیکیوشن ماحول قائم کرنے کے بہت سے طریقے ہیں۔ یہاں ہم وضاحت کریں گے کہ انہیں NPM پیکجز یا سورس کا استعمال کرتے ہوئے، یا گوگل کلاؤڈ کبرنیٹس انجن پر کبرنیٹس اور ڈوکر کے ذریعے بیری میٹل پر کیسے چلایا جائے۔ اگر سیٹ اپ کی یہ مثالیں آپ کے بنیادی ڈھانچے میں اچھی طرح سے ترجمہ نہیں کرتی ہیں تو ممکنہ طور پر حوالہ دینے کے لیے کمیونٹی گائیڈ ہو گا، آئیں [ڈسکورڈ](https://discord.gg/graphprotocol) پر ہیلو کہیں! اپنے انڈیکسر اجزاء کو شروع کرنے سے پہلے [پروٹوکول میں حصہ لینا](/network/indexing/#stake-in-the-protocol) یاد رکھیں! +انڈیکسر ایجنٹ اور انڈیکسر سروس آپ کے گراف نوڈ انفراسٹرکچر کے ساتھ مل کر واقع ہونی چاہیے۔ آپ کے انڈیکسر اجزاء کے لیے ورچوئل ایگزیکیوشن ماحول قائم کرنے کے بہت سے طریقے ہیں۔ یہاں ہم وضاحت کریں گے کہ انہیں NPM پیکجز یا سورس کا استعمال کرتے ہوئے، یا گوگل کلاؤڈ کبرنیٹس انجن پر کبرنیٹس اور ڈوکر کے ذریعے بیری میٹل پر کیسے چلایا جائے۔ اگر سیٹ اپ کی یہ مثالیں آپ کے بنیادی ڈھانچے میں اچھی طرح سے ترجمہ نہیں کرتی ہیں تو ممکنہ طور پر حوالہ دینے کے لیے کمیونٹی گائیڈ ہو گا، آئیں [ڈسکورڈ](https://discord.gg/graphprotocol) پر ہیلو کہیں! اپنے انڈیکسر اجزاء کو شروع کرنے سے پہلے [پروٹوکول میں حصہ لینا](/indexing/overview/#stake-in-the-protocol) یاد رکھیں! #### NPM پیکیجیز سے @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### K8s اور Terraform کو استعمال کرتے ہوئے -[Google Cloud پر Terraform کا استعمال کرتے ہوئے سرور انفراسٹرکچر سیٹ اپ کریں](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) سیکشن دیکھیں +[Google Cloud پر Terraform کا استعمال کرتے ہوئے سرور انفراسٹرکچر سیٹ اپ کریں](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) سیکشن دیکھیں #### استعمال @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -ایک بار جب ایک انڈیکسر نے پروٹوکول میں GRT کو سٹیک کر دیا ہے، تو [انڈیکسر اجزاء](/network/indexing/#indexer-components) کو شروع کیا جا سکتا ہے اور نیٹ ورک کے ساتھ اپنے تعاملات شروع کر سکتے ہیں. +ایک بار جب ایک انڈیکسر نے پروٹوکول میں GRT کو سٹیک کر دیا ہے، تو [انڈیکسر اجزاء](/indexing/overview/#indexer-components) کو شروع کیا جا سکتا ہے اور نیٹ ورک کے ساتھ اپنے تعاملات شروع کر سکتے ہیں. #### ٹوکنز منظور کریں @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). انڈیکسرز کو تجویز کی جاتی ہے کہ وہ offchain مطابقت پذیری کی فعالیت کو استعمال کریں تاکہ on-chain ایلوکیشن سے پہلے سب گراف کی تعیناتیوں کو chainhead سے ہم آہنگ کیا جا سکے. یہ خصوصیت خاص طور پر ان سب گرافوں کے لیے مفید ہے جن کی مطابقت پذیری میں 28 ایپوک سے زیادہ وقت لگ سکتا ہے یا غیر یقینی طور پر ناکام ہونے کے کچھ امکانات ہوتے ہیں. diff --git a/website/pages/ur/indexing/tap.mdx b/website/pages/ur/indexing/tap.mdx index 44b46f2e5fc7..543e1646070a 100644 --- a/website/pages/ur/indexing/tap.mdx +++ b/website/pages/ur/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 نوٹس: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/ur/resources/benefits.mdx b/website/pages/ur/resources/benefits.mdx index fd51fcdb633d..eb5291212ad0 100644 --- a/website/pages/ur/resources/benefits.mdx +++ b/website/pages/ur/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. سب گراف پر کیوریٹنگ سگنل ایک اختیاری ایک بار، خالص صفر لاگت ہے (مثال کے طور پر، $1k سگنل کو سب گراف پر کیوریٹ کیا جا سکتا ہے، اور بعد میں واپس لیا جا سکتا ہے—اس عمل میں منافع کمانے کی صلاحیت کے ساتھ). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy نیچے کی سطر: گراف نیٹ ورک کم مہنگا ہے، استعمال میں آسان ہے، اور مقامی طور پر `graph-node` کو چلانے کے مقابلے میں بہتر نتائج پیدا کرتا ہے. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/ur/resources/roles/curating.mdx b/website/pages/ur/resources/roles/curating.mdx index bd8819becb72..4f94e6c35db9 100644 --- a/website/pages/ur/resources/roles/curating.mdx +++ b/website/pages/ur/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## سگنل کرنے کا طریقہ -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) ایک کیوریٹر مخصوص سب گراف ورژن پر سگنل دینے کا انتخاب کر سکتا ہے، یا وہ اپنے سگنل کو خود بخود اس سب گراف کی جدید ترین پروڈکشن بلڈ میں منتقل کرنے کا انتخاب کر سکتا ہے۔ دونوں درست حکمت عملی ہیں اور ان کے اپنے فوائد اور نقصانات کے ساتھ آتے ہیں. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. گراف میں کیوری کی مارکیٹ فطری طور پر جوان ہے اور اس بات کا خطرہ ہے کہ آپ کا %APY مارکیٹ کی نئی حرکیات کی وجہ سے آپ کی توقع سے کم ہو سکتا ہے. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. ایک سب گراف ایک بگ کی وجہ سے ناکام ہو سکتا ہے. ایک ناکام سب گراف کیوری کی فیس جمع نہیں کرتا ہے. اس کے نتیجے میں،آپ کو انتظار کرنا پڑے گاجب تک کہ ڈویلپر اس بگ کو کو ٹھیک نہیں کرتا اور نیا ورژن تعینات کرتا ہے. - اگر آپ نےسب گراف کے نۓ ورژن کو سبسکرائب کیا ہے. آپ کے حصص خود بخود اس نئے ورژن میں منتقل ہو جائیں گے۔ اس پر 0.5% کیوریشن ٹیکس لگے گا. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/ur/resources/tokenomics.mdx b/website/pages/ur/resources/tokenomics.mdx index 320a53a47746..bfcb005f6400 100644 --- a/website/pages/ur/resources/tokenomics.mdx +++ b/website/pages/ur/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### موجودہ سب گراف کو کیوری کریں -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/ur/subgraphs/billing.mdx b/website/pages/ur/subgraphs/billing.mdx index 95164e556c2c..60f8ae6e151f 100644 --- a/website/pages/ur/subgraphs/billing.mdx +++ b/website/pages/ur/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. صفحہ کے اوپری دائیں کونے میں "کنیکٹ والیٹ" بٹن پر کلک کریں۔ آپ کو والیٹ کے انتخاب کے صفحہ پر بھیج دیا جائے گا۔ اپنا والیٹ منتخب کریں اور "کنیکٹ" پر کلک کریں. 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. صفحہ کے اوپری دائیں کونے میں "کنیکٹ والیٹ" بٹن پر کلک کریں۔ آپ کو والیٹ کے انتخاب کے صفحہ پر بھیج دیا جائے گا۔ اپنا والیٹ منتخب کریں اور "کنیکٹ" پر کلک کریں. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### ملٹی سگ والیٹ کا استعمال کرتے ہوئے GRT شامل کرنا -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/ur/subgraphs/cookbook/arweave.mdx b/website/pages/ur/subgraphs/cookbook/arweave.mdx index e39ad7d049d2..c54fa9627492 100644 --- a/website/pages/ur/subgraphs/cookbook/arweave.mdx +++ b/website/pages/ur/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ dataSources: پروسیسنگ ایونٹس کے ہینڈلرز [اسمبلی اسکرپٹ](https://www.assemblyscript.org/) میں لکھے گئے ہیں. -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## آرویو سب گراف سے کیوری کرنا -آرویو سب گرافس کے لیے گراف کیو ایل اینڈ پوائنٹ کا تعین موجودہ API انٹرفیس کے ساتھ، اسکیما تعریف سے کیا جاتا ہے۔ مزید معلومات کے لیے براہ کرم [گراف کیو ایل API دستاویزات](/querying/graphql-api/) ملاحظہ کریں. +آرویو سب گرافس کے لیے گراف کیو ایل اینڈ پوائنٹ کا تعین موجودہ API انٹرفیس کے ساتھ، اسکیما تعریف سے کیا جاتا ہے۔ مزید معلومات کے لیے براہ کرم [گراف کیو ایل API دستاویزات](/subgraphs/querying/graphql-api/) ملاحظہ کریں. ## سب گراف کی مثال diff --git a/website/pages/ur/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/ur/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/ur/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/ur/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ur/subgraphs/cookbook/cosmos.mdx b/website/pages/ur/subgraphs/cookbook/cosmos.mdx index 64a25e1cef88..16221134bb54 100644 --- a/website/pages/ur/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/ur/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and پروسیسنگ ایونٹس کے ہینڈلرز [اسمبلی اسکرپٹ](https://www.assemblyscript.org/) میں لکھے گئے ہیں. -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## ایک کوزموس سب گراف کو کیوری کرنا -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## تعاون یافتہ کوزموس بلاکچین diff --git a/website/pages/ur/subgraphs/cookbook/derivedfrom.mdx b/website/pages/ur/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/ur/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/ur/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ur/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/ur/subgraphs/cookbook/grafting-hotfix.mdx index 990a199cbfe0..780d7ad3f827 100644 --- a/website/pages/ur/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/ur/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## اضافی وسائل -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ur/subgraphs/cookbook/grafting.mdx b/website/pages/ur/subgraphs/cookbook/grafting.mdx index 1f68b682b55e..a03c1ee8d4e9 100644 --- a/website/pages/ur/subgraphs/cookbook/grafting.mdx +++ b/website/pages/ur/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ Grafting is a powerful feature that allows you to "graft" one subgraph onto anot ## ایک موجودہ سب گراف بنانا -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [سب گراف مثلی ریپو](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> نوٹ: اس مضمون کا بہت سا مواد پہلے شائع شدہ [آرویو آرٹیکل](/cookbook/arweave/) سے لیا گیا ہے +> نوٹ: اس مضمون کا بہت سا مواد پہلے شائع شدہ [آرویو آرٹیکل](/subgraphs/cookbook/arweave/) سے لیا گیا ہے diff --git a/website/pages/ur/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ur/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/ur/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/ur/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ur/subgraphs/cookbook/near.mdx b/website/pages/ur/subgraphs/cookbook/near.mdx index f2c62e35b654..f719a19bf33e 100644 --- a/website/pages/ur/subgraphs/cookbook/near.mdx +++ b/website/pages/ur/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ NEAR سب گراف ڈیولپمنٹ کے لیے `graph-cli` اوپر والے و ** schema.graphql:** ایک اسکیما فائل جو اس بات کی وضاحت کرتی ہے کہ آپ کے سب گراف کے لیے کون سا ڈیٹا محفوظ کیا جاتا ہے، اور GraphQL کے ذریعے اس سے کیوری کیسے کیا جائے۔ NEAR سب گراف کے تقاضوں کا احاطہ [موجودہ دستاویزات](/developing/creating-a-subgraph/#the-graphql-schema) سے ہوتا ہے. -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. سب گراف کی ترقی کے دوران دو اہم کمانڈز ہیں: @@ -98,7 +98,7 @@ accounts: پروسیسنگ ایونٹس کے ہینڈلرز [اسمبلی اسکرپٹ](https://www.assemblyscript.org/) میں لکھے گئے ہیں. -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - بلاک ہینڈلرز کو ایک `Block` ملے گا - ریسیپٹ ہینڈلرز کو ایک `ReceiptWithOutcome` ملے گا -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## NEAR سب گراف کی تعیناتی @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 = 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 72ee4bd4a320..7c3cdda1b99a 100644 --- a/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/ur/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## سب سٹریمز پیکیج کی وضاحت کرنا -ایک سب سٹریمز پیکیج اقسام پر مشتمل ہے (جس کی وضاحت [پروٹوکول بفرز](https://protobuf.dev/))، ماڈیولز (Rust میں لکھی گئی ہے)، اور ایک `substreams.yaml` فائل جو اقسام کا حوالہ دیتی ہے، اور یہ بتاتی ہے کہ ماڈیول کیسے ہیں متحرک ہیں. [سب سٹریمز ڈویلپمنٹ کے بارے میں مزید جاننے کے لیے سب سٹریمز کی دستاویزات دیکھیں](/substreams/)، اور [wesome-substreams](https://github.com/pinax-network/awesome-substreams) اور [Substreams cookbook](https مزید مثالوں کے لیے://github.com/pinax-network/substreams-cookbook). +ایک سب سٹریمز پیکیج اقسام پر مشتمل ہے (جس کی وضاحت [پروٹوکول بفرز](https://protobuf.dev/))، ماڈیولز (Rust میں لکھی گئی ہے)، اور ایک `substreams.yaml` فائل جو اقسام کا حوالہ دیتی ہے، اور یہ بتاتی ہے کہ ماڈیول کیسے ہیں متحرک ہیں. [سب سٹریمز ڈویلپمنٹ کے بارے میں مزید جاننے کے لیے سب سٹریمز کی دستاویزات دیکھیں](/substreams/introduction/)، اور [wesome-substreams](https://github.com/pinax-network/awesome-substreams) اور [Substreams cookbook](https مزید مثالوں کے لیے://github.com/pinax-network/substreams-cookbook). زیر بحث سب اسٹریمز پیکیج مینیٹ ایتھیریم پر کنٹریکٹ کی تعیناتیوں کا پتہ لگاتا ہے، تمام نئے تعینات کردہ کنٹریکٹس کے لیے تخلیق بلاک اور ٹائم اسٹیمپ کا پتہ لگاتا ہے۔ ایسا کرنے کے لیے، `/proto/example.proto` ([پروٹوکول بفرز کی تعریف کرنے کے بارے میں مزید جانیں](https://protobuf.dev/programming-guides/proto3/#simple)) میں ایک مخصوص `Contract` قسم ہے: diff --git a/website/pages/ur/subgraphs/cookbook/timeseries.mdx b/website/pages/ur/subgraphs/cookbook/timeseries.mdx index 8d3b90fe98c2..5049667a8d5c 100644 --- a/website/pages/ur/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/ur/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/ur/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/ur/subgraphs/cookbook/transfer-to-the-graph.mdx index b5effc7221d4..4930c7916184 100644 --- a/website/pages/ur/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/ur/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### مثال @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### اضافی وسائل -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/ur/subgraphs/developing/creating/advanced.mdx b/website/pages/ur/subgraphs/developing/creating/advanced.mdx index f25870d6bdf7..f5233e0d3ac6 100644 --- a/website/pages/ur/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/ur/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { اگر رشتہ پیرنٹ ادارے اور نتیجے میں آنے والی فائل ڈیٹا سورس ہستی کے درمیان 1:1 ہے، تو سادہ ترین نمونہ IPFS CID کو بطور لوک اپ استعمال کر کے پیرنٹ کی ہستی کو نتیجے میں آنے والی فائل ہستی سے جوڑنا ہے۔ اگر آپ کو اپنی نئی فائل پر مبنی ہستیوں کو ماڈل بنانے میں دشواری ہو رہی ہے تو ڈسکورڈ پر رابطہ کریں! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### فائلوں پر کارروائی کرنے کے لیے ایک نیا ہینڈلر بنائیں -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0. اگر آپ NFT میٹا ڈیٹا کو متعلقہ ٹوکنز سے جوڑ رہے ہیں، تو ٹوکن ہستی سے میٹا ڈیٹا ہستی کا حوالہ دینے کے لیے میٹا ڈیٹا کے IPFS ہیش کا استعمال کریں۔ آئی پی ایف ایس ہیش کو بطور ID استعمال کرتے ہوئے میٹا ڈیٹا ہستی کو محفوظ کریں. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### موجودہ سب گرافس پر گرافٹنگ -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/ur/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/ur/subgraphs/developing/creating/graph-ts/api.mdx index 5355b118c218..89c920dcb52a 100644 --- a/website/pages/ur/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/ur/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: اسمبلی اسکرپٹ API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx index 118eeea3c5f3..70226de74267 100644 --- a/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/ur/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: گراف CLI انسٹال کریں --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## جائزہ -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## شروع ہوا چاہتا ہے @@ -114,6 +114,6 @@ ABI فائل (فائلیں) آپ کے کنٹریکٹ (کنٹریکٹس) سے م | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx b/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx index 01dce298e672..c17ec92f7266 100644 --- a/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/ur/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/ur/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/ur/subgraphs/developing/creating/starting-your-subgraph.mdx index 7f864e823000..455cb2e3a413 100644 --- a/website/pages/ur/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/ur/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/ur/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/ur/subgraphs/developing/creating/subgraph-manifest.mdx index d81254c61923..106d985092ad 100644 --- a/website/pages/ur/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/ur/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). مینی فیسٹ کے لیے اپ ڈیٹ کرنے کے لیے اہم اندراجات یہ ہیں: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/ur/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/ur/subgraphs/developing/creating/unit-testing-framework.mdx index 76d1bd43664a..ecead46a151d 100644 --- a/website/pages/ur/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/ur/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,7 @@ Global test coverage: 22.2% (2/9 handlers). > 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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx index 4a97694d7040..f6823acc0f3c 100644 --- a/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/ur/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### گراف نیٹ ورک کے ساتھ سب گراف مطابقت In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - درج ذیل خصوصیات میں سے کوئی بھی استعمال نہیں کرنا چاہیے: - ipfs.cat & ipfs.map - Non-fatal errors @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## سب گراف ورژن کی خودکار آرکائیونگ diff --git a/website/pages/ur/subgraphs/developing/developer-faq.mdx b/website/pages/ur/subgraphs/developing/developer-faq.mdx index 188f94695f68..03912f36a74f 100644 --- a/website/pages/ur/subgraphs/developing/developer-faq.mdx +++ b/website/pages/ur/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You can deploy a new version of your subgraph to Subgraph Studio using the CLI. ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ docker pull graphprotocol/graph-node:latest ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -آپ کو تعاون یافتہ نیٹ ورکس کی فہرست [یہاں](/developing/supported-networks/) مل سکتی ہے. +آپ کو تعاون یافتہ نیٹ ورکس کی فہرست [یہاں](/supported-networks/) مل سکتی ہے. ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/ur/subgraphs/developing/introduction.mdx b/website/pages/ur/subgraphs/developing/introduction.mdx index 47f6552c33b8..2ab9c83db44f 100644 --- a/website/pages/ur/subgraphs/developing/introduction.mdx +++ b/website/pages/ur/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: ڈویلپنگ --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## جائزہ @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 29298733cc75..6ea0a5822bbb 100644 --- a/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/ur/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### شائع شدہ سب گراف کے لیے میٹا ڈیٹا کو اپ ڈیٹ کرنا @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/ur/subgraphs/developing/subgraphs.mdx b/website/pages/ur/subgraphs/developing/subgraphs.mdx index 5886281f8274..b6c1ffb9c2e3 100644 --- a/website/pages/ur/subgraphs/developing/subgraphs.mdx +++ b/website/pages/ur/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/ur/subgraphs/explorer.mdx b/website/pages/ur/subgraphs/explorer.mdx index 934c0a8fcdb7..544473765e91 100644 --- a/website/pages/ur/subgraphs/explorer.mdx +++ b/website/pages/ur/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -انڈیکسر بننے کے بارے میں مزید جاننے کے لیے، آپ [آفیشل دستاویزات](/network/indexing/) یا [دی گراف اکیڈمی انڈیکسر گائیڈز۔](https://thegraph.academy/delegators/ پر ایک نظر ڈال سکتے ہیں۔ choosing-indexers/) +انڈیکسر بننے کے بارے میں مزید جاننے کے لیے، آپ [آفیشل دستاویزات](/indexing/overview/) یا [دی گراف اکیڈمی انڈیکسر گائیڈز۔](https://thegraph.academy/delegators/ پر ایک نظر ڈال سکتے ہیں۔ choosing-indexers/) ![انڈیکسنگ کی تفصیلات کا پین](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![ایکسپلورر امیج 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### ڈیلیگیٹرز @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - پروٹوکول میں ان کے پاس موجود GRT کی کل رقم - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## نیٹ ورک diff --git a/website/pages/ur/subgraphs/querying/best-practices.mdx b/website/pages/ur/subgraphs/querying/best-practices.mdx index bc0328a3fe43..a8fb4ecbd083 100644 --- a/website/pages/ur/subgraphs/querying/best-practices.mdx +++ b/website/pages/ur/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - ہر ایک `queryName` کو فی آپریشن صرف ایک بار استعمال کیا جانا چاہیے. - ہر ایک `field` کو انتخاب میں صرف ایک بار استعمال کیا جانا چاہیے (ہم `token` کے تحت دو بار `id` سے کیوری نہیں کرسکتے ہیں) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - کسی دلیل کو تفویض کردہ کوئی بھی متغیر اس کی قسم سے مماثل ہونا چاہیے. - متغیرات کی دی گئی فہرست میں، ان میں سے ہر ایک منفرد ہونا چاہیے. - تمام متعین متغیرات کو استعمال کیا جانا چاہیے. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### GraphQL API کو ایک کیوری بھیجنا @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - کراس چین سب گراف ہینڈلنگ: ایک کیوری میں متعدد سب گرافس سے کیوری کرنا - [خودکار بلاک ٹریکنگ](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/ur/subgraphs/querying/graphql-api.mdx b/website/pages/ur/subgraphs/querying/graphql-api.mdx index 0f47773b71eb..32f0c3dc1c71 100644 --- a/website/pages/ur/subgraphs/querying/graphql-api.mdx +++ b/website/pages/ur/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/ur/subgraphs/querying/introduction.mdx b/website/pages/ur/subgraphs/querying/introduction.mdx index 32cb24678086..718526df17ee 100644 --- a/website/pages/ur/subgraphs/querying/introduction.mdx +++ b/website/pages/ur/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: گراف سے کیوری کرنا When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/ur/subgraphs/quick-start.mdx b/website/pages/ur/subgraphs/quick-start.mdx index bc1a9909a23d..5998de2fad57 100644 --- a/website/pages/ur/subgraphs/quick-start.mdx +++ b/website/pages/ur/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: فورا شروع کریں --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## شرطیں - ایک کرپٹو والیٹ -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/ur/substreams/sps/sps-faq.mdx b/website/pages/ur/substreams/sps/sps-faq.mdx index 5ff4bd0509eb..7434516e34b0 100644 --- a/website/pages/ur/substreams/sps/sps-faq.mdx +++ b/website/pages/ur/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: سب اسٹریمز سے چلنے والے سب گرافس FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -سب سٹریمز کے بارے میں مزید جاننے کے لیے [سب سٹریمز دستاویزات](/substreams/) پر جائیں. +سب سٹریمز کے بارے میں مزید جاننے کے لیے [سب سٹریمز دستاویزات](/substreams/introduction/) پر جائیں. ## سب سٹریمز سے چلنے والے سب گرافس کیا ہیں؟ -[سب اسٹریمز سے چلنے والے سب گرافس](/cookbook/substreams-powered-subgraphs/)سب اسٹریمز کی طاقت کو سب گرافس کی کیوری کے ساتھ جوڑتا ہے۔ سب اسٹریمز سے چلنے والے سب گراف کو شائع کرتے وقت، سب سٹریمز کی تبدیلیوں سے تیار کردہ ڈیٹا، [آؤٹ پٹ ہستی میں تبدیلیاں](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs),کر سکتا ہے جو سب گراف اداروں کے ساتھ مطابقت رکھتا ہے. +[سب اسٹریمز سے چلنے والے سب گرافس](/subgraphs/cookbook/substreams-powered-subgraphs/)سب اسٹریمز کی طاقت کو سب گرافس کی کیوری کے ساتھ جوڑتا ہے۔ سب اسٹریمز سے چلنے والے سب گراف کو شائع کرتے وقت، سب سٹریمز کی تبدیلیوں سے تیار کردہ ڈیٹا، [آؤٹ پٹ ہستی میں تبدیلیاں](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs),کر سکتا ہے جو سب گراف اداروں کے ساتھ مطابقت رکھتا ہے. اگر آپ سب گراف ڈیولپمنٹ سے پہلے ہی واقف ہیں، تو نوٹ کریں کہ سب سٹریمز سے چلنے والے سب گرافس کے بارے میں کیوری کیا جا سکتا ہے، بالکل اسی طرح جیسے اسے اسمبلی اسکرپٹ ٹرانسفارمیشن لیئر کے ذریعے تیار کیا گیا ہو، جیسے کہ ایک متحرک اور لچکدار GraphQL API فراہم کرنا. @@ -62,9 +62,9 @@ Firehose استعمال کرنے کے بہت سے فوائد ہیں، بشمول ## ڈویلپرز سب سٹریمز سے چلنے والے سب گرافس اور سب سٹریمز کے بارے میں مزید معلومات کہاں تک رسائی حاصل کرسکتے ہیں؟ -[سب سٹریمز دستاویزات](/substreams/) آپ کو سکھائے گا کہ سب سٹریمز کے ماڈیول کیسے بنائے جائیں. +[سب سٹریمز دستاویزات](/substreams/introduction/) آپ کو سکھائے گا کہ سب سٹریمز کے ماڈیول کیسے بنائے جائیں. -[سب سٹریمز سے چلنے والے سب گرافس کے دستاویزات](/cookbook/substreams-powered-subgraphs/) آپ کو دکھائے گا کہ انہیں گراف پر تعیناتی کے لیے کیسے پیک کیا جائے. +[سب سٹریمز سے چلنے والے سب گرافس کے دستاویزات](/subgraphs/cookbook/substreams-powered-subgraphs/) آپ کو دکھائے گا کہ انہیں گراف پر تعیناتی کے لیے کیسے پیک کیا جائے. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ See [modules documentation](https://substreams.streamingfast.io/documentation/de ## آپ سب سٹریمز سے چلنے والے سب گراف کو کیسے بنا اور تعینات کر سکتے ہیں؟ -سب سٹریمز سے چلنے والے سب گراف کی [defining](/cookbook/substreams-powered-subgraphs/) کے بعد، آپ گراف CLI کو [Subgraph Studio](https://thegraph.com/studio/) میں تعینات کرنے کے لیے استعمال کر سکتے ہیں. +سب سٹریمز سے چلنے والے سب گراف کی [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) کے بعد، آپ گراف CLI کو [Subgraph Studio](https://thegraph.com/studio/) میں تعینات کرنے کے لیے استعمال کر سکتے ہیں. ## مجھے سب سٹریمز اور سب سٹریمز سے چلنے والے سب گرافس کی مثالیں کہاں مل سکتی ہیں؟ diff --git a/website/pages/ur/supported-networks.mdx b/website/pages/ur/supported-networks.mdx index 8dd466430865..856f4765fc8e 100644 --- a/website/pages/ur/supported-networks.mdx +++ b/website/pages/ur/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/vi/about.mdx b/website/pages/vi/about.mdx index b45ddbbc5c39..917e7817b3a7 100644 --- a/website/pages/vi/about.mdx +++ b/website/pages/vi/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/vi/archived/arbitrum/arbitrum-faq.mdx b/website/pages/vi/archived/arbitrum/arbitrum-faq.mdx index 9c12c8816259..562824e64e95 100644 --- a/website/pages/vi/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/vi/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now? -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ Everything has been tested thoroughly, and a contingency plan is in place to ens ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction. -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx index 455a034a056d..ebb2229301d3 100644 --- a/website/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx +++ b/website/pages/vi/archived/arbitrum/l2-transfer-tools-faq.mdx @@ -14,7 +14,7 @@ These tools will require you to follow a specific set of steps depending on what ### Can I use the same wallet I use on Ethereum mainnet? -If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. +If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/archived/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One. Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else. diff --git a/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx index 67746ef430fb..268d22e65a70 100644 --- a/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/vi/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: Hướng dẫn sử dụng công cụ chuyển L2 The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -Một số câu hỏi thường gặp về những công cụ này được trả lời trong [Câu hỏi thường gặp về Công cụ chuyển L2](/arbitrum/l2-transfer-tools-faq/). Câu hỏi thường gặp chứa các giải thích sâu sắc về cách sử dụng các công cụ, cách chúng hoạt động và những điều cần lưu ý khi sử dụng chúng. +Một số câu hỏi thường gặp về những công cụ này được trả lời trong [Câu hỏi thường gặp về Công cụ chuyển L2](/archived/arbitrum/l2-transfer-tools-faq/). Câu hỏi thường gặp chứa các giải thích sâu sắc về cách sử dụng các công cụ, cách chúng hoạt động và những điều cần lưu ý khi sử dụng chúng. ## How to transfer your subgraph to Arbitrum (L2) diff --git a/website/pages/vi/archived/sunrise.mdx b/website/pages/vi/archived/sunrise.mdx index 248ebdc3cc49..f9419c36d642 100644 --- a/website/pages/vi/archived/sunrise.mdx +++ b/website/pages/vi/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### Why is Edge & Node running the upgrade Indexer? @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/vi/contracts.mdx b/website/pages/vi/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/vi/contracts.mdx +++ b/website/pages/vi/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/vi/indexing/chain-integration-overview.mdx b/website/pages/vi/indexing/chain-integration-overview.mdx index 280d97bc2aa4..77141e82b34a 100644 --- a/website/pages/vi/indexing/chain-integration-overview.mdx +++ b/website/pages/vi/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ A transparent and governance-based integration process was designed for blockcha ## Stage 1. Technical Integration -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory. ## Stage 2. Integration Validation diff --git a/website/pages/vi/indexing/new-chain-integration.mdx b/website/pages/vi/indexing/new-chain-integration.mdx index 8a65bdc55eec..f5c5cba520d5 100644 --- a/website/pages/vi/indexing/new-chain-integration.mdx +++ b/website/pages/vi/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Graph Node should be syncing the deployed subgraph if there are no errors. Give ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/vi/indexing/overview.mdx b/website/pages/vi/indexing/overview.mdx index 6c480e8da348..a9a275e13819 100644 --- a/website/pages/vi/indexing/overview.mdx +++ b/website/pages/vi/indexing/overview.mdx @@ -87,7 +87,7 @@ Once an allocation has been closed the rebates are available to be claimed by th ### Cắt giảm phí truy vấn và cắt giảm phần thưởng indexing là gì? -The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing/#stake-in-the-protocol) for instructions on setting the delegation parameters. +The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/indexing/overview/#stake-in-the-protocol) for instructions on setting the delegation parameters. - **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators. @@ -121,7 +121,7 @@ Indexer có thể tự phân biệt bản thân bằng cách áp dụng các k ### What are some basic security precautions an Indexer should take? -- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing/#stake-in-the-protocol) for instructions. +- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/indexing/overview/#stake-in-the-protocol) for instructions. - **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed. @@ -375,7 +375,7 @@ To successfully participate in the network requires almost constant monitoring a #### Bắt đầu -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### Từ các gói NPM @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### Sử dụng K8s and Terraform -See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud) section +See the [Setup Server Infrastructure Using Terraform on Google Cloud](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud) section #### Sử dụng @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing/#indexer-components) can be started up and begin their interactions with the network. +Once an Indexer has staked GRT in the protocol, the [Indexer components](/indexing/overview/#indexer-components) can be started up and begin their interactions with the network. #### Phê duyệt các token @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically. diff --git a/website/pages/vi/indexing/tap.mdx b/website/pages/vi/indexing/tap.mdx index 63b32fa831f6..f4536d331674 100644 --- a/website/pages/vi/indexing/tap.mdx +++ b/website/pages/vi/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 Notes: -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/vi/resources/benefits.mdx b/website/pages/vi/resources/benefits.mdx index 24ed75834e10..fc108e7f6a79 100644 --- a/website/pages/vi/resources/benefits.mdx +++ b/website/pages/vi/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process). @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally. -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/vi/resources/roles/curating.mdx b/website/pages/vi/resources/roles/curating.mdx index db8ccf3e50df..d70b3b9999de 100644 --- a/website/pages/vi/resources/roles/curating.mdx +++ b/website/pages/vi/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## Làm thế nào để phát tín hiệu -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) Curator có thể chọn phát tín hiệu trên một phiên bản subgraph cụ thể hoặc họ có thể chọn để tín hiệu của họ tự động chuyển sang bản dựng sản xuất mới nhất của subgraph đó. Cả hai đều là những chiến lược hợp lệ và đi kèm với những ưu và nhược điểm của riêng chúng. @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics. 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. Một subgraph có thể thất bại do một lỗi. Một subgraph thất bại không tích lũy phí truy vấn. Do đó, bạn sẽ phải đợi cho đến khi nhà phát triển sửa lỗi và triển khai phiên bản mới. - Nếu bạn đã đăng ký phiên bản mới nhất của một subgraph, các cổ phần của bạn sẽ tự động chuyển sang phiên bản mới đó. Điều này sẽ phát sinh một khoản thuế curation 0.5%. - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/vi/resources/tokenomics.mdx b/website/pages/vi/resources/tokenomics.mdx index 7b23de66edfc..af3aad3befc0 100644 --- a/website/pages/vi/resources/tokenomics.mdx +++ b/website/pages/vi/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### Querying an existing subgraph -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/vi/subgraphs/billing.mdx b/website/pages/vi/subgraphs/billing.mdx index dec5cfdadc12..f3f52bbf35ee 100644 --- a/website/pages/vi/subgraphs/billing.mdx +++ b/website/pages/vi/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect". 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a multisig wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/vi/subgraphs/cookbook/arweave.mdx b/website/pages/vi/subgraphs/cookbook/arweave.mdx index 4d925799ee1e..b5f0521e9ca1 100644 --- a/website/pages/vi/subgraphs/cookbook/arweave.mdx +++ b/website/pages/vi/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## Querying an Arweave Subgraph -The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs diff --git a/website/pages/vi/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/vi/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/vi/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/vi/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/vi/subgraphs/cookbook/cosmos.mdx b/website/pages/vi/subgraphs/cookbook/cosmos.mdx index 38b983935e9a..e58bb266b3b5 100644 --- a/website/pages/vi/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/vi/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## Querying a Cosmos subgraph -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Supported Cosmos Blockchains diff --git a/website/pages/vi/subgraphs/cookbook/derivedfrom.mdx b/website/pages/vi/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/vi/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/vi/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/vi/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/vi/subgraphs/cookbook/grafting-hotfix.mdx index 4c5ab7d8929f..ddf32cc35aa6 100644 --- a/website/pages/vi/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/vi/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## Additional Resources -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/vi/subgraphs/cookbook/grafting.mdx b/website/pages/vi/subgraphs/cookbook/grafting.mdx index 87631366eb25..ac324b79cad8 100644 --- a/website/pages/vi/subgraphs/cookbook/grafting.mdx +++ b/website/pages/vi/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## Building an Existing Subgraph -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/) +> Note: A lot of material from this article was taken from the previously published [Arweave article](/subgraphs/cookbook/arweave/) diff --git a/website/pages/vi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/vi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/vi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/vi/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/vi/subgraphs/cookbook/near.mdx b/website/pages/vi/subgraphs/cookbook/near.mdx index 53f3448a1532..324ff08549e1 100644 --- a/website/pages/vi/subgraphs/cookbook/near.mdx +++ b/website/pages/vi/subgraphs/cookbook/near.mdx @@ -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/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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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 The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/). -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## Deploying a NEAR Subgraph @@ -228,7 +228,7 @@ We will provide more information on running the above components soon. ## Querying a NEAR Subgraph -The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## Example Subgraphs @@ -276,7 +276,7 @@ Pending functionality is not yet supported for NEAR subgraphs. In the interim, y ### My question hasn't been answered, where can I get more help building NEAR subgraphs? -If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. +If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/subgraphs/quick-start/). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com. ## References diff --git a/website/pages/vi/subgraphs/cookbook/pruning.mdx b/website/pages/vi/subgraphs/cookbook/pruning.mdx index d86bf50edf42..c6b1217db9a5 100644 --- a/website/pages/vi/subgraphs/cookbook/pruning.mdx +++ b/website/pages/vi/subgraphs/cookbook/pruning.mdx @@ -14,7 +14,7 @@ Add a section called `indexerHints` in the manifest. - `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 02bf475bf8ba..84e1b0adfd3b 100644 --- a/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/vi/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: Substreams-powered subgraphs --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## Requirements @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## Defining a Substreams package -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)): diff --git a/website/pages/vi/subgraphs/cookbook/timeseries.mdx b/website/pages/vi/subgraphs/cookbook/timeseries.mdx index 9f371624ebf0..4a55ac2bcd5a 100644 --- a/website/pages/vi/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/vi/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/vi/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/vi/subgraphs/cookbook/transfer-to-the-graph.mdx index cfd461e80d4d..70e2afcb503c 100644 --- a/website/pages/vi/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/vi/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### Ví dụ @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### Additional Resources -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/vi/subgraphs/developing/creating/advanced.mdx b/website/pages/vi/subgraphs/developing/creating/advanced.mdx index e929137a7147..e02c23f506c5 100644 --- a/website/pages/vi/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/vi/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities! -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ Additionally, it is not possible to create data sources from a file data source, If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID. -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### Ghép vào các Subgraph Hiện có -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx index d18e42fb902a..19b154a479c1 100644 --- a/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/vi/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: @@ -35,7 +35,7 @@ The `apiVersion` in the subgraph manifest specifies the mapping API version whic | 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. | | 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types
Added `receipt` field to the Ethereum Event object | | 0.0.6 | Added `nonce` field to the Ethereum Transaction object
Added `baseFeePerGas` to the Ethereum Block object | -| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | +| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/))
`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` | | 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object | | 0.0.3 | Added `from` field to the Ethereum Call object
`etherem.call.address` renamed to `ethereum.call.to` | | 0.0.2 | Added `input` field to the Ethereum Transaction object | diff --git a/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx index ce25fbcafc6d..d79f714cf51a 100644 --- a/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/vi/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: Cài đặt Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## Tổng quan -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## Getting Started @@ -114,6 +114,6 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx b/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx index 6acca805ef38..a2d88ceca9e5 100644 --- a/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/vi/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/vi/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/vi/subgraphs/developing/creating/starting-your-subgraph.mdx index 4354f4d9b0fd..faa0cc958d66 100644 --- a/website/pages/vi/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/vi/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/vi/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/vi/subgraphs/developing/creating/subgraph-manifest.mdx index 1843837e0506..cd250d296ca8 100644 --- a/website/pages/vi/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/vi/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). Các mục nhập quan trọng cần cập nhật cho tệp kê khai là: @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/vi/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/vi/subgraphs/developing/creating/unit-testing-framework.mdx index 63da75a0cc84..3867eaebfeee 100644 --- a/website/pages/vi/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/vi/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx index a31ab87d24dd..e31e344f60ef 100644 --- a/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/vi/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/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/) +- Index a [supported network](/supported-networks/) - Must not use any of the following features: - ipfs.cat & ipfs.map - Lỗi không nghiêm trọng @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## Automatic Archiving of Subgraph Versions diff --git a/website/pages/vi/subgraphs/developing/developer-faq.mdx b/website/pages/vi/subgraphs/developing/developer-faq.mdx index c4e32c8f1d21..90bc9950e12e 100644 --- a/website/pages/vi/subgraphs/developing/developer-faq.mdx +++ b/website/pages/vi/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ Bạn phải triển khai lại subgraph, nhưng nếu ID subgraph (mã băm IPF ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ Nếu chỉ một thực thể được tạo trong sự kiện và nếu không ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -You can find the list of the supported networks [here](/developing/supported-networks/). +You can find the list of the supported networks [here](/supported-networks/). ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/vi/subgraphs/developing/introduction.mdx b/website/pages/vi/subgraphs/developing/introduction.mdx index 0a4e23fcbf00..c92c181f3af0 100644 --- a/website/pages/vi/subgraphs/developing/introduction.mdx +++ b/website/pages/vi/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: Developing --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## Tổng quan @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx index 7b5baa296e0b..f35a237999bc 100644 --- a/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/vi/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### Updating metadata for a published subgraph @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/vi/subgraphs/developing/subgraphs.mdx b/website/pages/vi/subgraphs/developing/subgraphs.mdx index 42c1e806f822..e30b77cec1ae 100644 --- a/website/pages/vi/subgraphs/developing/subgraphs.mdx +++ b/website/pages/vi/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/vi/subgraphs/explorer.mdx b/website/pages/vi/subgraphs/explorer.mdx index d3095fb4f3e0..51f1856ae915 100644 --- a/website/pages/vi/subgraphs/explorer.mdx +++ b/website/pages/vi/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) +To learn more about how to become an Indexer, you can take a look at the [official documentation](/indexing/overview/) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/) ![Indexing details pane](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![Explorer Image 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. Delegators @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - Tổng lượng GRT mà họ hiện có trong giao thức - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## Mạng lưới diff --git a/website/pages/vi/subgraphs/querying/best-practices.mdx b/website/pages/vi/subgraphs/querying/best-practices.mdx index 9c2db771238c..3736fa32faeb 100644 --- a/website/pages/vi/subgraphs/querying/best-practices.mdx +++ b/website/pages/vi/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - Each `queryName` must only be used once per operation. - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - Any variable assigned to an argument must match its type. - In a given list of variables, each of them must be unique. - All defined variables must be used. > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### Sending a query to a GraphQL API @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/vi/subgraphs/querying/graphql-api.mdx b/website/pages/vi/subgraphs/querying/graphql-api.mdx index dd118022aa46..f6351619bd7c 100644 --- a/website/pages/vi/subgraphs/querying/graphql-api.mdx +++ b/website/pages/vi/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/vi/subgraphs/querying/introduction.mdx b/website/pages/vi/subgraphs/querying/introduction.mdx index 95f6722f9dc6..e19e027659ca 100644 --- a/website/pages/vi/subgraphs/querying/introduction.mdx +++ b/website/pages/vi/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: Querying The Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/vi/subgraphs/quick-start.mdx b/website/pages/vi/subgraphs/quick-start.mdx index 366aa6ebe8a4..e41c12dfdc4c 100644 --- a/website/pages/vi/subgraphs/quick-start.mdx +++ b/website/pages/vi/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: Bắt đầu nhanh --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## Điều kiện tiên quyết - A crypto wallet -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/vi/substreams/sps/sps-faq.mdx b/website/pages/vi/substreams/sps/sps-faq.mdx index 5fd8082aeac1..ec24f97300ae 100644 --- a/website/pages/vi/substreams/sps/sps-faq.mdx +++ b/website/pages/vi/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: Substreams-powered subgraphs FAQ Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## What are Substreams-powered subgraphs? -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities. If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API. @@ -62,9 +62,9 @@ There are many benefits to using Firehose, including: ## Where can developers access more information about Substreams-powered subgraphs and Substreams? -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. +The [Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph. The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ As an example, Alice can build a DEX price module, Bob can use it to build a vol ## How can you build and deploy a Substreams-powered Subgraph? -After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). +After [defining](/subgraphs/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/). ## Where can I find examples of Substreams and Substreams-powered subgraphs? diff --git a/website/pages/vi/supported-networks.mdx b/website/pages/vi/supported-networks.mdx index 70ad6b027d99..9972685d5c15 100644 --- a/website/pages/vi/supported-networks.mdx +++ b/website/pages/vi/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/pages/zh/about.mdx b/website/pages/zh/about.mdx index d057befe67cf..81c40b3d9f61 100644 --- a/website/pages/zh/about.mdx +++ b/website/pages/zh/about.mdx @@ -24,7 +24,7 @@ In the case of the example listed above, Bored Ape Yacht Club, you can perform b It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions. -Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. +Alternatively, you have the option to set up your own server, process the transactions, store them in a database, and create an API endpoint to query the data. However, this option is [resource intensive](/resources/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization. Blockchain properties, such as finality, chain reorganizations, and uncled blocks, add complexity to the process, making it time-consuming and conceptually challenging to retrieve accurate query results from blockchain data. diff --git a/website/pages/zh/archived/arbitrum/arbitrum-faq.mdx b/website/pages/zh/archived/arbitrum/arbitrum-faq.mdx index 6ae6a6ccd818..1696ca24d7fe 100644 --- a/website/pages/zh/archived/arbitrum/arbitrum-faq.mdx +++ b/website/pages/zh/archived/arbitrum/arbitrum-faq.mdx @@ -41,7 +41,7 @@ Once you have GRT on Arbitrum, you can add it to your billing balance. ## 作为子图开发人员、数据消费者、索引人、策展人或授权者，我现在需要做什么？ -Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support. +Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) for additional support. All indexing rewards are now entirely on Arbitrum. @@ -53,7 +53,7 @@ All smart contracts have been thoroughly [audited](https://github.com/graphproto ## Are existing subgraphs on Ethereum working? -All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. +All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/archived/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly. ## Does GRT have a new smart contract deployed on Arbitrum? @@ -77,4 +77,4 @@ All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arb 您可以通过在[Subgraph Studio](https://thegraph.com/studio/)中进行一键体验，将GRT添加到您的Arbitrum计费余额中。您将能够通过一笔交易轻松将您的GRT桥接到Arbitrum并填写您的API密钥。 -Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. +Visit the [Billing page](/subgraphs/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT. diff --git a/website/pages/zh/archived/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/zh/archived/arbitrum/l2-transfer-tools-guide.mdx index 71601a39c69d..61c7aaa77b39 100644 --- a/website/pages/zh/archived/arbitrum/l2-transfer-tools-guide.mdx +++ b/website/pages/zh/archived/arbitrum/l2-transfer-tools-guide.mdx @@ -4,7 +4,7 @@ title: L2转移工具指南 The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring. -关于这些工具的一些常见问题在 L2 Transfer Tools FAQ(/arbitrum/l2-transfer-tools-faq) 中有详细解答。FAQ 中深入解释了如何使用这些工具、它们的工作原理以及在使用过程中需要注意的事项。 +关于这些工具的一些常见问题在 L2 Transfer Tools FAQ(/archived/arbitrum/l2-transfer-tools-faq/) 中有详细解答。FAQ 中深入解释了如何使用这些工具、它们的工作原理以及在使用过程中需要注意的事项。 ## 如何将你的子图转移到 Arbitrum（L2） diff --git a/website/pages/zh/archived/sunrise.mdx b/website/pages/zh/archived/sunrise.mdx index 9dd332acaaf1..0e7fafa344d0 100644 --- a/website/pages/zh/archived/sunrise.mdx +++ b/website/pages/zh/archived/sunrise.mdx @@ -22,7 +22,7 @@ No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately avai ### Why were subgraphs published to Arbitrum, did it start indexing a different network? -The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/) +The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/supported-networks/) ## About the Upgrade Indexer @@ -33,7 +33,7 @@ The upgrade Indexer was implemented to improve the experience of upgrading subgr ### What does the upgrade Indexer do? - It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published. -- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/). +- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/supported-networks/). - Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them. ### 为什么 Edge & Node 运行升级索引人？ @@ -60,7 +60,7 @@ It operates on an “as needed” basis, serving as a fallback until sufficient ### How does this affect subgraph developers? -Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. +Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/subgraphs/developing/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph/) was not impacted by this upgrade. ### How does the upgrade Indexer benefit data consumers? diff --git a/website/pages/zh/contracts.mdx b/website/pages/zh/contracts.mdx index 5b3a9ab09e77..d2255f3af336 100644 --- a/website/pages/zh/contracts.mdx +++ b/website/pages/zh/contracts.mdx @@ -14,7 +14,7 @@ This is the principal deployment of The Graph Network. ## Mainnet -This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. +This was the original deployment of The Graph Network. [Learn more](/archived/arbitrum/arbitrum-faq/) about The Graph's scaling with Arbitrum. diff --git a/website/pages/zh/indexing/chain-integration-overview.mdx b/website/pages/zh/indexing/chain-integration-overview.mdx index cffb628a8983..3caa15d11f90 100644 --- a/website/pages/zh/indexing/chain-integration-overview.mdx +++ b/website/pages/zh/indexing/chain-integration-overview.mdx @@ -6,7 +6,7 @@ title: 链集成过程概述 ## 阶段1：技术集成 -- Please visit [New Chain Integration](/new-chain-integration/) for information on `graph-node` support for new chains. +- Please visit [New Chain Integration](/indexing/new-chain-integration/) for information on `graph-node` support for new chains. - 团队通过在[here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)（治理与GIPs下的新数据源子类别）创建一个论坛帖子来启动协议集成过程。强制使用默认的论坛模板。 ## 阶段2：集成验证 diff --git a/website/pages/zh/indexing/new-chain-integration.mdx b/website/pages/zh/indexing/new-chain-integration.mdx index c1004c12b66c..4975c18f4e62 100644 --- a/website/pages/zh/indexing/new-chain-integration.mdx +++ b/website/pages/zh/indexing/new-chain-integration.mdx @@ -45,7 +45,7 @@ For EVM chains, there exists a deeper level of data that can be achieved through ## EVM considerations - Difference between JSON-RPC & Firehose -While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. +While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing. - All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes. @@ -77,4 +77,4 @@ Configuring Graph Node is as easy as preparing your local environment. Once your ## Substreams-powered Subgraphs -For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. +For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/substreams/sps/introduction/). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself. diff --git a/website/pages/zh/indexing/overview.mdx b/website/pages/zh/indexing/overview.mdx index df29ff7d60e9..5df18460e46c 100644 --- a/website/pages/zh/indexing/overview.mdx +++ b/website/pages/zh/indexing/overview.mdx @@ -87,7 +87,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### 什么是查询费减免和索引奖励减免？ -`queryFeeCut` 和 `indexingRewardCut` 值是委托的参数，该索引可以设置连同 cooldownBlocks 控制 GRT 的索引和他们的委托人之间的分配。 有关设置委托参数的说明，请参阅[协议中的质押](/network/indexing/#stake-in-the-protocol)的最后步骤。 +`queryFeeCut` 和 `indexingRewardCut` 值是委托的参数，该索引可以设置连同 cooldownBlocks 控制 GRT 的索引和他们的委托人之间的分配。 有关设置委托参数的说明，请参阅[协议中的质押](/indexing/overview/#stake-in-the-protocol)的最后步骤。 - **查询费用削减** - 将分配给索引人的子图上累积的查询费用回扣的百分比。 如果将其设置为 95%，则在申请分配时，索引人将获得查询费用回扣池的 95%，另外 5% 将分配给委托人。 @@ -121,7 +121,7 @@ Query fees are collected by the gateway and distributed to indexers according to ### 索引人应该采取哪些基本的安全防范措施？ -- **运营商钱包** - 设置运营商钱包是一项重要的预防措施，因为它允许索引器在控制股权的密钥和控制日常交易的密钥之间保持分离-天操作。有关说明，请参阅[Stake in Protocol](/network/indexing/#stake-in-the-protocol)。 +- **运营商钱包** - 设置运营商钱包是一项重要的预防措施，因为它允许索引器在控制股权的密钥和控制日常交易的密钥之间保持分离-天操作。有关说明，请参阅[Stake in Protocol](/indexing/overview/#stake-in-the-protocol)。 - **防火墙** - 只有索引人服务需要公开，尤其要注意锁定管理端口和数据库访问：Graph 节点 JSON-RPC 端点（默认端口：8030）、索引人管理 API 端点（默认端口：18000）和 Postgres 数据库端点（默认端口：5432）不应暴露。 @@ -375,7 +375,7 @@ docker-compose up #### 开始 -The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing/#stake-in-the-protocol) before starting up your Indexer components! +The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/indexing/overview/#stake-in-the-protocol) before starting up your Indexer components! #### 来自 NPM 包 @@ -455,7 +455,7 @@ docker run -p 18000:8000 -it indexer-agent:latest ... #### 使用 K8s 和 Terraform -请参阅[在Google Cloud上使用Terraform设置服务器基础结构](/network/indexing/#setup-server-infrastructure-using-terraform-on-google-cloud)一节。 +请参阅[在Google Cloud上使用Terraform设置服务器基础结构](/indexing/overview/#setup-server-infrastructure-using-terraform-on-google-cloud)一节。 #### 使用方法 @@ -754,7 +754,7 @@ The first steps to participating in the network as an Indexer are to approve the > Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools). -一旦索引人将GRT置于协议中，[索引人组件](/network/indexing/#indexer-components)就可以启动并开始与网络交互。 +一旦索引人将GRT置于协议中，[索引人组件](/indexing/overview/#indexer-components)就可以启动并开始与网络交互。 #### 批准代币 @@ -814,6 +814,6 @@ After being created by an Indexer a healthy allocation goes through two states. - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules. -- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)). +- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/indexing/overview/#how-are-indexing-rewards-distributed)). 建议索引人在链上创建分配之前，利用链外同步功能将子图部署同步到链头。对于可能需要超过28个时期才能同步或有一些无法确定失败的机会的子图，此功能特别有用。 diff --git a/website/pages/zh/indexing/tap.mdx b/website/pages/zh/indexing/tap.mdx index a91191795f03..a93fe0ae6937 100644 --- a/website/pages/zh/indexing/tap.mdx +++ b/website/pages/zh/indexing/tap.mdx @@ -170,8 +170,8 @@ max_amount_willing_to_lose_grt = 20 注意： -- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway). -- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id. +- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/indexing/tap/#gateway). +- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/indexing/tap/#contracts) using the appropriate chain id. **Log Level** diff --git a/website/pages/zh/resources/benefits.mdx b/website/pages/zh/resources/benefits.mdx index aef267eff346..484b2c2c410a 100644 --- a/website/pages/zh/resources/benefits.mdx +++ b/website/pages/zh/resources/benefits.mdx @@ -75,7 +75,7 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar ‡Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries. -Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. +Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/archived/arbitrum/arbitrum-faq/) are substantially lower than Ethereum mainnet. 在一个子图上策划信号是一个可选一次性净零成本(例如，1千美元的信号可以在一个子图上管理，然后撤回ーー在这个过程中有可能获得回报)。 @@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy 一句话: 与在本地运行一个`graph-node`相比，Graph网络成本更低，更容易使用，并且产生更好的结果。 -Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start/). +Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/subgraphs/quick-start/). diff --git a/website/pages/zh/resources/roles/curating.mdx b/website/pages/zh/resources/roles/curating.mdx index 1672eaad69f1..cfb16d3942c8 100644 --- a/website/pages/zh/resources/roles/curating.mdx +++ b/website/pages/zh/resources/roles/curating.mdx @@ -12,7 +12,7 @@ Curators make The Graph network efficient and [signaling](#how-to-signal) is the Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -24,7 +24,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph ## 如何进行信号处理 -Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer/) +Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/subgraphs/explorer/) 策展人可以选择在特定的子图版本上发出信号，或者他们可以选择让他们的策展份额自动迁移到该子图的最新生产版本。 这两种策略都是有效的，都有各自的优点和缺点。 @@ -48,7 +48,7 @@ However, it is recommended that curators leave their signaled GRT in place not o 1. 在Graph，查询市场本来就很年轻，由于市场动态刚刚开始，你的年收益率可能低于你的预期，这是有风险的。 2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned. -3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating/). +3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/resources/roles/delegating/). 4. 一个子图可能由于错误而失败。 一个失败的子图不会累积查询费用。 因此，你必须等待，直到开发人员修复错误并部署一个新的版本。 - 如果你订阅了一个子图的最新版本，你的份额将自动迁移到该新版本。 这将产生 0.5%的策展税。 - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax. diff --git a/website/pages/zh/resources/tokenomics.mdx b/website/pages/zh/resources/tokenomics.mdx index d3ef5296a6b9..cd2c84562e70 100644 --- a/website/pages/zh/resources/tokenomics.mdx +++ b/website/pages/zh/resources/tokenomics.mdx @@ -11,7 +11,7 @@ The Graph is a decentralized protocol that enables easy access to blockchain dat The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network. -The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/). +The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/subgraphs/billing/). - GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) @@ -59,13 +59,13 @@ Developers build and query subgraphs to retrieve blockchain data. Since subgraph Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers. -Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network. +Once developers have built and tested their subgraph, they can [publish their subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) on The Graph's decentralized network. ### 查询现存子图 -Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. +Once a subgraph is [published](/subgraphs/developing/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph. -Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. +Subgraphs are [queried using GraphQL](/subgraphs/querying/introduction/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol. 1% of the query fees paid to the network are burned. diff --git a/website/pages/zh/subgraphs/billing.mdx b/website/pages/zh/subgraphs/billing.mdx index 8d63ddec5ba1..aea848cf6722 100644 --- a/website/pages/zh/subgraphs/billing.mdx +++ b/website/pages/zh/subgraphs/billing.mdx @@ -15,7 +15,7 @@ There are two plans to use when querying subgraphs on The Graph Network. ## Query Payments with credit card - To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/) - 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). + 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. 单击页面右上角的“Connect Wallet”（连接钱包）按钮。您将被重定向到钱包选择页面。选择您的钱包，然后单击“Connect”（连接）。 3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step. 4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details. @@ -50,7 +50,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Adding GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. 单击页面右上角的“Connect Wallet”（连接钱包）按钮。您将被重定向到钱包选择页面。选择您的钱包，然后单击“Connect”（连接）。 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. @@ -67,7 +67,7 @@ Once you bridge GRT, you can add it to your billing balance. ### Withdrawing GRT using a wallet -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". 3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear. 4. Enter the amount of GRT you would like to withdraw. @@ -76,7 +76,7 @@ Once you bridge GRT, you can add it to your billing balance. ### 使用多签钱包添加GRT -1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/). +1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/subgraphs/billing/). 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas. 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet". 4. Use the slider to estimate the number of queries you expect to make on a monthly basis. diff --git a/website/pages/zh/subgraphs/cookbook/arweave.mdx b/website/pages/zh/subgraphs/cookbook/arweave.mdx index a3ecd2f1c70b..ae6a399817d8 100644 --- a/website/pages/zh/subgraphs/cookbook/arweave.mdx +++ b/website/pages/zh/subgraphs/cookbook/arweave.mdx @@ -105,7 +105,7 @@ Arweave 数据源支持两种类型的处理程序: 处理事件的处理程序是用 [AssemblyScript](https://www.assemblyscript.org/) 编写的。 -Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -160,7 +160,7 @@ graph deploy --access-token ## 查询 Arweave 子图 -Arweave 子图的 GraphQL 端点由模式定义和现有的 API 接口决定。有关更多信息，请访问 [GraphQLAPI 文档](/querying/graphql-api/)。 +Arweave 子图的 GraphQL 端点由模式定义和现有的 API 接口决定。有关更多信息，请访问 [GraphQLAPI 文档](/subgraphs/querying/graphql-api/)。 ## 示例子图 diff --git a/website/pages/zh/subgraphs/cookbook/avoid-eth-calls.mdx b/website/pages/zh/subgraphs/cookbook/avoid-eth-calls.mdx index 8897ecdbfdc7..a0613bf2b69f 100644 --- a/website/pages/zh/subgraphs/cookbook/avoid-eth-calls.mdx +++ b/website/pages/zh/subgraphs/cookbook/avoid-eth-calls.mdx @@ -103,14 +103,14 @@ You can significantly improve indexing performance by minimizing or eliminating ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/zh/subgraphs/cookbook/cosmos.mdx b/website/pages/zh/subgraphs/cookbook/cosmos.mdx index c5ea0c2b44e6..475d0cb1108a 100644 --- a/website/pages/zh/subgraphs/cookbook/cosmos.mdx +++ b/website/pages/zh/subgraphs/cookbook/cosmos.mdx @@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and 处理事件的处理程序是用 [AssemblyScript](https://www.assemblyscript.org/) 编写的。 -Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```tsx class Block { @@ -218,7 +218,7 @@ graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost ## 查询 Cosmos 子图 -The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information. +The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/subgraphs/querying/graphql-api/) for more information. ## 受支持的Cosmos区块链 diff --git a/website/pages/zh/subgraphs/cookbook/derivedfrom.mdx b/website/pages/zh/subgraphs/cookbook/derivedfrom.mdx index 09ba62abde3f..22845a8d7dd2 100644 --- a/website/pages/zh/subgraphs/cookbook/derivedfrom.mdx +++ b/website/pages/zh/subgraphs/cookbook/derivedfrom.mdx @@ -65,7 +65,7 @@ This will not only make our subgraph more efficient, but it will also unlock thr 2. We can do a reverse lookup and query any `Comment` and see which post it comes from. -3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. +3. We can use [Derived Field Loaders](/subgraphs/developing/creating/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings. ## Conclusion @@ -75,14 +75,14 @@ For a more detailed explanation of strategies to avoid large arrays, check out K ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/zh/subgraphs/cookbook/grafting-hotfix.mdx b/website/pages/zh/subgraphs/cookbook/grafting-hotfix.mdx index 1a9736aa17a2..8153e7143816 100644 --- a/website/pages/zh/subgraphs/cookbook/grafting-hotfix.mdx +++ b/website/pages/zh/subgraphs/cookbook/grafting-hotfix.mdx @@ -166,21 +166,21 @@ However, it’s important to use grafting judiciously and follow best practices ## 其他资源 -- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting -- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. +- **[Grafting Documentation](/subgraphs/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting +- **[Understanding Deployment IDs](/subgraphs/querying/subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID. By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable. ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/zh/subgraphs/cookbook/grafting.mdx b/website/pages/zh/subgraphs/cookbook/grafting.mdx index 2738082e21da..c741d57e8787 100644 --- a/website/pages/zh/subgraphs/cookbook/grafting.mdx +++ b/website/pages/zh/subgraphs/cookbook/grafting.mdx @@ -42,7 +42,7 @@ By adhering to these guidelines, you minimize risks and ensure a smoother migrat ## 构建现有子图 -Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: +Building subgraphs is an essential part of The Graph, described more in depth [here](/subgraphs/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided: - [子图示例存储库](https://github.com/Shiyasmohd/grafting-tutorial) @@ -199,4 +199,4 @@ If you want more experience with grafting, here are a few examples for popular c To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results -> 注意：这篇文章中的很多内容都来自之前发表的[Arweave文章](/cookbook/arweave/)。 +> 注意：这篇文章中的很多内容都来自之前发表的[Arweave文章](/subgraphs/cookbook/arweave/)。 diff --git a/website/pages/zh/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/zh/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx index 541212617f9f..ed3d902cfad3 100644 --- a/website/pages/zh/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx +++ b/website/pages/zh/subgraphs/cookbook/immutable-entities-bytes-as-ids.mdx @@ -177,14 +177,14 @@ Read more about using Immutable Entities and Bytes as IDs in this blog post by D ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/zh/subgraphs/cookbook/near.mdx b/website/pages/zh/subgraphs/cookbook/near.mdx index 6c986e7775fb..b2544c076d8a 100644 --- a/website/pages/zh/subgraphs/cookbook/near.mdx +++ b/website/pages/zh/subgraphs/cookbook/near.mdx @@ -37,7 +37,7 @@ NEAR 子图开发需要`0.23.0`以上版本的`graph-cli`，以及 `0.23.0`以 **schema.graphql:** 一个模式文件，定义子图存储的数据以及如何通过 GraphQL 查询数据。NEAR 子图的要求已经在[现有的文档](/developing/creating-a-subgraph/#the-graphql-schema)中介绍了。 -**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. +**AssemblyScript Mappings:** [AssemblyScript code](/subgraphs/developing/creating/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. 在子图开发过程中，有两个关键命令： @@ -98,7 +98,7 @@ NEAR 数据源支持两种类型的处理程序： 处理事件的处理程序是用 [AssemblyScript](https://www.assemblyscript.org/) 编写的。 -NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api/). +NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/). ```typescript @@ -165,9 +165,9 @@ class ReceiptWithOutcome { - 块处理程序将收到 `Block` - 收据处理程序将收到 `ReceiptWithOutcome` -Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api/) is available to NEAR subgraph developers during mapping execution. +Otherwise, the rest of the [AssemblyScript API](/subgraphs/developing/creating/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/graph-ts/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](/subgraphs/developing/creating/graph-ts/api/#json-api) to allow developers to easily process these logs. ## 部署 NEAR 子图 @@ -228,7 +228,7 @@ graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 = 0.66.0. - `prune: `: Sets a custom limit on the number of historical blocks to retain. -- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired. +- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired. We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`: @@ -32,9 +32,9 @@ dataSources: ## Important Considerations -- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. +- If [Time Travel Queries](/subgraphs/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: ` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data. -- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). +- It is not possible to [graft](/subgraphs/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: ` that will accurately retain a set number of blocks (e.g., enough for six months). ## Conclusion @@ -42,14 +42,14 @@ Pruning using `indexerHints` is a best practice for subgraph development, offeri ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx b/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx index 9a8d3b2b610f..35b5d34c9bb2 100644 --- a/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx +++ b/website/pages/zh/subgraphs/cookbook/substreams-powered-subgraphs.mdx @@ -2,7 +2,7 @@ title: 基于Substreams的子图 --- -[Substreams](/substreams/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. +[Substreams](/substreams/introduction/) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers. ## 要求 @@ -22,7 +22,7 @@ graph init --from-example substreams-powered-subgraph ## 定义Substreams包 -A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. +A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams/introduction/), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples. 该Substreams包可以检测以太坊主网上的合约部署，并跟踪所有新部署合约的创建块和时间戳。为此，在/proto/example.proto中有一个专门的Contract类型（了解更多关于定义Protocol Buffers的信息[learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)）： diff --git a/website/pages/zh/subgraphs/cookbook/timeseries.mdx b/website/pages/zh/subgraphs/cookbook/timeseries.mdx index b3072b4d102b..7ac1de481272 100644 --- a/website/pages/zh/subgraphs/cookbook/timeseries.mdx +++ b/website/pages/zh/subgraphs/cookbook/timeseries.mdx @@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr ## Subgraph Best Practices 1-6 -1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/) +1. [Improve Query Speed with Subgraph Pruning](/subgraphs/cookbook/pruning/) -2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/) +2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/subgraphs/cookbook/derivedfrom/) -3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/) +3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/subgraphs/cookbook/immutable-entities-bytes-as-ids/) -4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/) +4. [Improve Indexing Speed by Avoiding `eth_calls`](/subgraphs/cookbook/avoid-eth-calls/) -5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/) +5. [Simplify and Optimize with Timeseries and Aggregations](/subgraphs/cookbook/timeseries/) -6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/) +6. [Use Grafting for Quick Hotfix Deployment](/subgraphs/cookbook/grafting-hotfix/) diff --git a/website/pages/zh/subgraphs/cookbook/transfer-to-the-graph.mdx b/website/pages/zh/subgraphs/cookbook/transfer-to-the-graph.mdx index 5186b6088071..f5b0745282c9 100644 --- a/website/pages/zh/subgraphs/cookbook/transfer-to-the-graph.mdx +++ b/website/pages/zh/subgraphs/cookbook/transfer-to-the-graph.mdx @@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n ## Upgrade Your Subgraph to The Graph in 3 Easy Steps -1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) -2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) -3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) +1. [Set Up Your Studio Environment](/subgraphs/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment) +2. [Deploy Your Subgraph to Studio](/subgraphs/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio) +3. [Publish to The Graph Network](/subgraphs/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network) ## 1. Set Up Your Studio Environment @@ -70,9 +70,9 @@ graph deploy --ipfs-hash ### Query Your Subgraph -> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph. +> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/resources/roles/curating/) on The Graph. -You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. +You can start [querying](/subgraphs/querying/introduction/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio. #### 示例 @@ -100,5 +100,5 @@ Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio]( ### 其他资源 -- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/). +- To quickly create and publish a new subgraph, check out the [Quick Start](/subgraphs/quick-start/). - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/). diff --git a/website/pages/zh/subgraphs/developing/creating/advanced.mdx b/website/pages/zh/subgraphs/developing/creating/advanced.mdx index 7ecc521091c6..aaef1e7aa989 100644 --- a/website/pages/zh/subgraphs/developing/creating/advanced.mdx +++ b/website/pages/zh/subgraphs/developing/creating/advanced.mdx @@ -202,7 +202,7 @@ type TokenMetadata @entity { 如果母实体与生成的文件数据源实体之间的关系为1:1，则最简单的模式是通过使用IPFS CID作为查找将母实体链接到生成的文件实体。如果您在建模新的基于文件的实体时遇到困难，请联系Discord！ -> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities. +> You can use [nested filters](/subgraphs/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` or `kind: file/arweave` @@ -230,7 +230,7 @@ The file data source must specifically mention all the entity types which it wil #### 创建新处理程序以处理文件 -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)). +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](/subgraphs/developing/creating/graph-ts/api/#json-api)). The CID of the file as a readable string can be accessed via the `dataSource` as follows: @@ -333,7 +333,7 @@ You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0. 如果要将 NFT 元数据链接到相应的代币，请使用元数据的 IPFS hash从代币实体引用元数据实体。使用 IPFS hash作为 ID 保存元数据实体。 -You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. +You can use [DataSource context](/subgraphs/developing/creating/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler. If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity. @@ -525,7 +525,7 @@ calls: ### 嫁接到现有子图 -> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). +> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/subgraphs/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network). When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. diff --git a/website/pages/zh/subgraphs/developing/creating/graph-ts/api.mdx b/website/pages/zh/subgraphs/developing/creating/graph-ts/api.mdx index 3f374fbbbc12..708704b73b07 100644 --- a/website/pages/zh/subgraphs/developing/creating/graph-ts/api.mdx +++ b/website/pages/zh/subgraphs/developing/creating/graph-ts/api.mdx @@ -2,7 +2,7 @@ title: AssemblyScript API --- -> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide/). +> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/resources/release-notes/assemblyscript-migration-guide/). Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box: diff --git a/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx b/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx index 9db4e62530b6..62bb898478c0 100644 --- a/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx +++ b/website/pages/zh/subgraphs/developing/creating/install-the-cli.mdx @@ -2,11 +2,11 @@ title: 安装 Graph CLI --- -> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/). +> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/subgraphs/developing/deploying/subgraph-studio-faq/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/resources/roles/curating/). ## 概述 -The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. +The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/subgraphs/developing/creating/subgraph-manifest/) and compiles the [mappings](/subgraphs/developing/creating/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network. ## 开始 @@ -114,6 +114,6 @@ ABI 文件必须与您的合约相匹配。 获取 ABI 文件的方法有以下 | 0.0.9 | Supports `endBlock` feature | | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). | | 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). | -| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. | +| 0.0.6 | Supports fast [Proof of Indexing](/indexing/overview/#what-is-a-proof-of-indexing-poi) calculation variant. | | 0.0.5 | Added support for event handlers having access to transaction receipts. | | 0.0.4 | Added support for managing subgraph features. | diff --git a/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx b/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx index 28101b955e31..224a3fb0aa34 100644 --- a/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx +++ b/website/pages/zh/subgraphs/developing/creating/ql-schema.mdx @@ -6,7 +6,7 @@ title: The Graph QL Schema The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language. -> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section. +> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/subgraphs/querying/graphql-api/) section. ### Defining Entities @@ -262,7 +262,7 @@ type Band @entity { } ``` -The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. +The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/subgraphs/querying/graphql-api/#queries) for a description of the fulltext search API and more example usage. ```graphql query { diff --git a/website/pages/zh/subgraphs/developing/creating/starting-your-subgraph.mdx b/website/pages/zh/subgraphs/developing/creating/starting-your-subgraph.mdx index f99d56a6aa44..fdef40db3f8a 100644 --- a/website/pages/zh/subgraphs/developing/creating/starting-your-subgraph.mdx +++ b/website/pages/zh/subgraphs/developing/creating/starting-your-subgraph.mdx @@ -6,7 +6,7 @@ title: Starting Your Subgraph The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs. -When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. +When you create a [subgraph](/subgraphs/developing/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL. Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs. @@ -14,8 +14,8 @@ Subgraph development ranges from simple scaffold subgraphs to advanced, specific Start the process and build a subgraph that matches your needs: -1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure -2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component -3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema -4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings -5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features +1. [Install the CLI](/subgraphs/developing/creating/install-the-cli/) - Set up your infrastructure +2. [Subgraph Manifest](/subgraphs/developing/creating/subgraph-manifest/) - Understand a subgraph's key component +3. [The Graph Ql Schema](/subgraphs/developing/creating/ql-schema/) - Write your schema +4. [Writing AssemblyScript Mappings](/subgraphs/developing/creating/assemblyscript-mappings/) - Write your mappings +5. [Advanced Features](/subgraphs/developing/creating/advanced/) - Customize your subgraph with advanced features diff --git a/website/pages/zh/subgraphs/developing/creating/subgraph-manifest.mdx b/website/pages/zh/subgraphs/developing/creating/subgraph-manifest.mdx index 58f782bc4bb7..9e2913c97e75 100644 --- a/website/pages/zh/subgraphs/developing/creating/subgraph-manifest.mdx +++ b/website/pages/zh/subgraphs/developing/creating/subgraph-manifest.mdx @@ -79,7 +79,7 @@ dataSources: ## Subgraph Entries -> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/). +> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/subgraphs/developing/creating/ql-schema/). 清单中要更新的重要条目是： @@ -509,7 +509,7 @@ The `indexerHints` setting in a subgraph's manifest provides directives for inde History as of a given block is required for: -- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history +- [Time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history - Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block - Rewinding the subgraph back to that block @@ -517,7 +517,7 @@ If historical data as of the block has been pruned, the above capabilities will > Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data. -For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: +For subgraphs leveraging [time travel queries](/subgraphs/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings: To retain a specific amount of historical data: diff --git a/website/pages/zh/subgraphs/developing/creating/unit-testing-framework.mdx b/website/pages/zh/subgraphs/developing/creating/unit-testing-framework.mdx index 6a6c46fd3d9b..b077795de1d4 100644 --- a/website/pages/zh/subgraphs/developing/creating/unit-testing-framework.mdx +++ b/website/pages/zh/subgraphs/developing/creating/unit-testing-framework.mdx @@ -1377,7 +1377,7 @@ Global test coverage: 22.2% (2/9 handlers). > 关键：无法从具有背景的有效模块创建WasmInstance：未知导入：wasi_snapshot_preview1:：尚未定义fd_write -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) +This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/subgraphs/developing/creating/graph-ts/api/#logging-api) > ERROR TS2554: Expected ? arguments, but got ?. > diff --git a/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx index a0e8ce484342..24724980581a 100644 --- a/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx +++ b/website/pages/zh/subgraphs/developing/deploying/using-subgraph-studio.mdx @@ -53,13 +53,13 @@ npm install -g @graphprotocol/graph-cli -> For additional written detail, review the [Quick Start](/quick-start/). +> For additional written detail, review the [Quick Start](/subgraphs/quick-start/). ### 子图与图形网络的兼容性 In order to be supported by Indexers on The Graph Network, subgraphs must: -- Index a [supported network](/developing/supported-networks/) +- Index a [supported network](/supported-networks/) - 不得使用以下任何功能： - ipfs.cat & ipfs.map - 非致命错误 @@ -114,7 +114,7 @@ Use Subgraph Studio to check the logs on the dashboard and look for any errors w ## Publish Your Subgraph -In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/). +In order to publish your subgraph successfully, review [publishing a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). ## Versioning Your Subgraph with the CLI @@ -126,7 +126,7 @@ If you want to update your subgraph, you can do the following: You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment. -> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/). +> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/resources/roles/curating/). ## 子图版本的自动归档 diff --git a/website/pages/zh/subgraphs/developing/developer-faq.mdx b/website/pages/zh/subgraphs/developing/developer-faq.mdx index 9299dc71d7e9..36cb36c8a674 100644 --- a/website/pages/zh/subgraphs/developing/developer-faq.mdx +++ b/website/pages/zh/subgraphs/developing/developer-faq.mdx @@ -12,7 +12,7 @@ A subgraph is a custom API built on blockchain data. Subgraphs are queried using ### 2. What is the first step to create a subgraph? -To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). +To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/subgraphs/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/). ### 3. Can I still create a subgraph if my smart contracts don't have events? @@ -34,7 +34,7 @@ You can deploy a new version of your subgraph to Subgraph Studio using the CLI. ### 7. How do I call a contract function or access a public state variable from my subgraph mappings? -Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state). +Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/subgraphs/developing/creating/graph-ts/api/#access-to-smart-contract-state). ### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings? @@ -80,13 +80,13 @@ docker pull graphprotocol/graph-node:latest ### 15. Can I delete my subgraph? -Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph. +Yes, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) and [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) your subgraph. ## Network Related ### 16. What networks are supported by The Graph? -您可以在[这里](/developing/supported-networks/)找到支持的网络列表。 +您可以在[这里](/supported-networks/)找到支持的网络列表。 ### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers? diff --git a/website/pages/zh/subgraphs/developing/introduction.mdx b/website/pages/zh/subgraphs/developing/introduction.mdx index c69562f7cb5f..b7ea25dc49cd 100644 --- a/website/pages/zh/subgraphs/developing/introduction.mdx +++ b/website/pages/zh/subgraphs/developing/introduction.mdx @@ -2,7 +2,7 @@ title: 开发 --- -To start coding right away, go to [Developer Quick Start](/quick-start/). +To start coding right away, go to [Developer Quick Start](/subgraphs/quick-start/). ## 概述 @@ -27,4 +27,4 @@ On The Graph, you can: A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. -Check out the documentation on [subgraphs](/subgraphs/) to learn specifics. +Check out the documentation on [subgraphs](/subgraphs/developing/subgraphs/) to learn specifics. diff --git a/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx b/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx index a40080f30ea0..04649d60c564 100644 --- a/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx +++ b/website/pages/zh/subgraphs/developing/publishing/publishing-a-subgraph.mdx @@ -6,12 +6,12 @@ Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a When you publish a subgraph to the decentralized network, you make it available for: -- [Curators](/network/curating/) to begin curating it. -- [Indexers](/network/indexing/) to begin indexing it. +- [Curators](/resources/roles/curating/) to begin curating it. +- [Indexers](/indexing/overview/) to begin indexing it. -Check out the list of [supported networks](/developing/supported-networks/). +Check out the list of [supported networks](/supported-networks/). ## Publishing from Subgraph Studio @@ -21,9 +21,9 @@ Check out the list of [supported networks](/developing/supported-networks/). All published versions of an existing subgraph can: -- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq/). +- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/archived/arbitrum/arbitrum-faq/). -- Index data on any of the [supported networks](/developing/supported-networks/), regardless of the network on which the subgraph was published. +- Index data on any of the [supported networks](/supported-networks/), regardless of the network on which the subgraph was published. ### 更新已发布的子图的元数据 @@ -69,13 +69,13 @@ Developers can add GRT signal to their subgraphs to incentivize Indexers to quer - You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md). -- Specific supported networks can be checked [here](/developing/supported-networks/). +- Specific supported networks can be checked [here](/supported-networks/). > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers. > If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph. -The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. +The [Sunrise Upgrade Indexer](/archived/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability. When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version. @@ -91,4 +91,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore ![Signal from Explorer](/img/signal-from-explorer.png) -Learn more about [Curating](/network/curating/) on The Graph Network. +Learn more about [Curating](/resources/roles/curating/) on The Graph Network. diff --git a/website/pages/zh/subgraphs/developing/subgraphs.mdx b/website/pages/zh/subgraphs/developing/subgraphs.mdx index bf8d590fe7e9..0ddf77fea7cc 100644 --- a/website/pages/zh/subgraphs/developing/subgraphs.mdx +++ b/website/pages/zh/subgraphs/developing/subgraphs.mdx @@ -37,12 +37,12 @@ Here is a general overview of a subgraph’s lifecycle: 1. [Create a subgraph](/developing/creating-a-subgraph/) 2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/) 3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio) -4. [Publish a subgraph](/publishing/publishing-a-subgraph/) -5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) +4. [Publish a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/) +5. [Signal on a subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph) ### Build locally -Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs. +Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/subgraphs/developing/creating/graph-ts/README/) and [Matchstick](/subgraphs/developing/creating/unit-testing-framework/) to create robust subgraphs. ### Deploy to Subgraph Studio @@ -53,15 +53,15 @@ Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deployi ### Publish to the Network -When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network. +When you're happy with your subgraph, you can [publish it](/subgraphs/developing/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-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](/subgraphs/developing/managing/transferring-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 -Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph. +Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/resources/roles/curating/) on The Graph. #### What is signal? @@ -70,9 +70,9 @@ Published subgraphs are unlikely to be picked up by Indexers without curation si ### Querying & Application Development -Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/). +Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/subgraphs/billing/). -Learn more about [querying subgraphs](/querying/querying-the-graph/). +Learn more about [querying subgraphs](/subgraphs/querying/introduction/). ### Updating Subgraphs @@ -83,4 +83,4 @@ To update your subgraph with bug fixes or new functionalities, initiate a transa ### Deleting & Transferring Subgraphs -If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/). +If you no longer need a published subgraph, you can [delete](/subgraphs/developing/managing/deleting-a-subgraph/) or [transfer](/subgraphs/developing/managing/transferring-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/resources/roles/curating/). diff --git a/website/pages/zh/subgraphs/explorer.mdx b/website/pages/zh/subgraphs/explorer.mdx index 3155efb373fb..a7ac3587700e 100644 --- a/website/pages/zh/subgraphs/explorer.mdx +++ b/website/pages/zh/subgraphs/explorer.mdx @@ -72,7 +72,7 @@ Indexers can earn both query fees and indexing rewards. Functionally, this happe - Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button. -要了解有关如何成为 Indexer 的更多信息，您可以查看[官方文档](/network/indexing/) 或 [Graph Academy 索引器指南。](https://thegraph.academy/delegators/选择索引器/) +要了解有关如何成为 Indexer 的更多信息，您可以查看[官方文档](/indexing/overview/) 或 [Graph Academy 索引器指南。](https://thegraph.academy/delegators/选择索引器/) ![索引详细信息窗格](/img/Indexing-Details-Pane.png) @@ -92,7 +92,7 @@ In the The Curator table listed below you can see: ![资源管理器图片 6](/img/Curation-Overview.png) -If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating/) or [The Graph Academy](https://thegraph.academy/curators/). +If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/resources/roles/curating/) or [The Graph Academy](https://thegraph.academy/curators/). ### 3. 委托人 @@ -113,7 +113,7 @@ In the Delegators table you can see the active Delegators in the community and i - 目前在协议中的 GRT 总量 - The date they last delegated -If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). +If you want to learn more about how to become a Delegator, check out the [official documentation](/resources/roles/delegating/) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers). ## 网络 diff --git a/website/pages/zh/subgraphs/querying/best-practices.mdx b/website/pages/zh/subgraphs/querying/best-practices.mdx index 40fc694b41d1..7e0669a325b9 100644 --- a/website/pages/zh/subgraphs/querying/best-practices.mdx +++ b/website/pages/zh/subgraphs/querying/best-practices.mdx @@ -54,14 +54,14 @@ query [operationName]([variableName]: [variableType]) { - 每个操作只能使用一次 `queryName`。 - 每个`field`在选择中只能使用一次(我们不能在`token`下查询 `id` 两次) -- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer/). +- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/subgraphs/explorer/). - 分配给参数的任何变量都必须匹配其类型。 - 在给定的变量列表中，每个变量必须是唯一的。 - 必须使用所有已定义的变量。 > Note: Failing to follow these rules will result in an error from The Graph API. -For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/). +For a complete list of rules with code examples, check out [GraphQL Validations guide](/resources/release-notes/graphql-validations-migration-guide/). ### 向 GraphQL API 发送查询 @@ -69,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP. It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`). -However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: +However, as mentioned in ["Querying from an Application"](/subgraphs/querying/from-an-application/), it's recommended to use `graph-client`, which supports the following unique features: - 跨链子图处理: 在一个查询中从多个子图进行查询 - [自动区块跟踪](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md) @@ -100,7 +100,7 @@ async function main() { main() ``` -More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application/). +More GraphQL client alternatives are covered in ["Querying from an Application"](/subgraphs/querying/from-an-application/). --- diff --git a/website/pages/zh/subgraphs/querying/graphql-api.mdx b/website/pages/zh/subgraphs/querying/graphql-api.mdx index 086997107f47..410d181ca42f 100644 --- a/website/pages/zh/subgraphs/querying/graphql-api.mdx +++ b/website/pages/zh/subgraphs/querying/graphql-api.mdx @@ -8,7 +8,7 @@ Learn about the GraphQL Query API used in The Graph. [GraphQL](https://graphql.org/learn/) is a query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs. -To understand the larger role that GraphQL plays, review [developing](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/). +To understand the larger role that GraphQL plays, review [developing](/subgraphs/developing/introduction/) and [creating a subgraph](/developing/creating-a-subgraph/). ## Queries with GraphQL diff --git a/website/pages/zh/subgraphs/querying/introduction.mdx b/website/pages/zh/subgraphs/querying/introduction.mdx index a57c2ee304da..baae90fd7b6b 100644 --- a/website/pages/zh/subgraphs/querying/introduction.mdx +++ b/website/pages/zh/subgraphs/querying/introduction.mdx @@ -4,7 +4,7 @@ title: 查询Graph When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema. -> Please see the [Query API](/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices/) +> Please see the [Query API](/subgraphs/querying/graphql-api/) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/subgraphs/querying/best-practices/) > Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead. @@ -14,8 +14,8 @@ Each subgraph published to The Graph Network has a unique query URL in Graph Exp ![Query Subgraph URL](/img/query-url-screenshot.png) -Learn more about querying from an application [here](/querying/querying-from-an-application/). +Learn more about querying from an application [here](/subgraphs/querying/from-an-application/). As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio/). -Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing/). +Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/subgraphs/billing/). diff --git a/website/pages/zh/subgraphs/quick-start.mdx b/website/pages/zh/subgraphs/quick-start.mdx index b68efb3aa361..90b4a43d6fef 100644 --- a/website/pages/zh/subgraphs/quick-start.mdx +++ b/website/pages/zh/subgraphs/quick-start.mdx @@ -2,12 +2,12 @@ title: 快速开始 --- -Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph. +Learn how to easily build, publish and query a [subgraph](/subgraphs/developing/developer-faq/#1-what-is-a-subgraph) on The Graph. ## 先决条件 - 一个加密钱包 -- A smart contract address on a [supported network](/developing/supported-networks/) +- A smart contract address on a [supported network](/supported-networks/) - [Node.js](https://nodejs.org/) installed - A package manager of your choice (`npm`, `yarn` or `pnpm`) @@ -123,7 +123,7 @@ If you’d like to test your subgraph before publishing it, you can use [Subgrap ### 7. Publish your subgraph to The Graph Network -Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it. +Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/resources/roles/curating/) to curate it and [Indexers](/indexing/overview/) to index it. #### Publishing with Subgraph Studio @@ -157,7 +157,7 @@ graph publish ![cli-ui](/img/cli-ui.png) -To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/). +To customize your deployment, see [Publishing a Subgraph](/subgraphs/developing/publishing/publishing-a-subgraph/). #### Adding signal to your subgraph @@ -169,7 +169,7 @@ To customize your deployment, see [Publishing a Subgraph](/publishing/publishing - It’s recommended to curate at least 3,000 GRT to attract 3 Indexers. Check reward eligibility based on subgraph feature usage and supported networks. -To learn more about curation, read [Curating](/network/curating/). +To learn more about curation, read [Curating](/resources/roles/curating/). To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option: @@ -181,4 +181,4 @@ You now have access to 100,000 free queries per month with your subgraph on The You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button. -For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/). +For more information about querying data from your subgraph, read [Querying The Graph](/subgraphs/querying/introduction/). diff --git a/website/pages/zh/substreams/sps/sps-faq.mdx b/website/pages/zh/substreams/sps/sps-faq.mdx index e82db5a2ccae..69c3d0631722 100644 --- a/website/pages/zh/substreams/sps/sps-faq.mdx +++ b/website/pages/zh/substreams/sps/sps-faq.mdx @@ -6,11 +6,11 @@ title: 基于Substreams的子图 Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere. -Go to the [Substreams Documentation](/substreams/) to learn more about Substreams. +Go to the [Substreams Documentation](/substreams/introduction/) to learn more about Substreams. ## 什么是基于Substreams的子图？ -[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/)将Substreams的强大功能与子图(subgraphs)的可查询性相结合。在发布一个由Substreams驱动的子图时，Substreams的转换过程产生的数据可以[输出实体变更](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs)，这些实体变更与子图的实体是兼容的。 +[Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/)将Substreams的强大功能与子图(subgraphs)的可查询性相结合。在发布一个由Substreams驱动的子图时，Substreams的转换过程产生的数据可以[输出实体变更](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs)，这些实体变更与子图的实体是兼容的。 如果您已经熟悉子图（Subgraph）开发，那么请注意，基于Substreams的子图可以被查询，就像它是由AssemblyScript转换层生成的一样，具有所有子图的优势，比如提供动态和灵活的GraphQL API。 @@ -62,9 +62,9 @@ Firehose是由[StreamingFast](https://www.streamingfast.io/)开发的区块链 ## 开发人员在哪里可以获得关于Substreams-powered子图和Substreams的更多信息？ -The [Substreams documentation](/substreams/) will teach you how to build Substreams modules. +The [Substreams documentation](/substreams/introduction/) will teach you how to build Substreams modules. -[Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) 将向您展示如何将它们打包部署在The Graph上。 +[Substreams-powered subgraphs documentation](/subgraphs/cookbook/substreams-powered-subgraphs/) 将向您展示如何将它们打包部署在The Graph上。 The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code. @@ -82,7 +82,7 @@ See [modules documentation](https://substreams.streamingfast.io/documentation/de ## 如何构建和部署Substreams-powered子图？ -在[defining](/cookbook/substreams-powered-subgraphs/)Substreams-powered子图之后，您可以使用Graph CLI在[Subgraph Studio](https://thegraph.com/studio/)上部署它。 +在[defining](/subgraphs/cookbook/substreams-powered-subgraphs/)Substreams-powered子图之后，您可以使用Graph CLI在[Subgraph Studio](https://thegraph.com/studio/)上部署它。 ## 在哪里可以找到Substreams和Substreams-powered子图的示例？ diff --git a/website/pages/zh/supported-networks.mdx b/website/pages/zh/supported-networks.mdx index 6b8f7177d123..416453068b29 100644 --- a/website/pages/zh/supported-networks.mdx +++ b/website/pages/zh/supported-networks.mdx @@ -10,7 +10,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename) \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/). -\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/). +\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/subgraphs/cookbook/substreams-powered-subgraphs/) integration (this includes `evm` and `near` networks). ⁠† Supports deployment of [Substreams-powered subgraphs](/subgraphs/cookbook/substreams-powered-subgraphs/). - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints. - Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. diff --git a/website/src/IndexPage.tsx b/website/src/IndexPage.tsx index 533fccaf9a65..ba64423b2666 100644 --- a/website/src/IndexPage.tsx +++ b/website/src/IndexPage.tsx @@ -26,27 +26,27 @@ export function Intro() { { title: t('index.shortcuts.aboutTheGraph.title'), description: t('index.shortcuts.aboutTheGraph.description'), - href: '/about', + href: '/about/', }, { title: t('index.shortcuts.quickStart.title'), description: t('index.shortcuts.quickStart.description'), - href: '/quick-start', + href: '/subgraphs/quick-start/', }, { title: t('index.shortcuts.developerFaqs.title'), description: t('index.shortcuts.developerFaqs.description'), - href: '/developing/developer-faqs', + href: '/subgraphs/developing/developer-faq/', }, { title: t('index.shortcuts.queryFromAnApplication.title'), description: t('index.shortcuts.queryFromAnApplication.description'), - href: '/querying/querying-from-an-application', + href: '/subgraphs/querying/from-an-application/', }, { title: t('index.shortcuts.createASubgraph.title'), description: t('index.shortcuts.createASubgraph.description'), - href: '/developing/creating-a-subgraph', + href: '/subgraphs/developing/creating/starting-your-subgraph/', }, ].map((card) => (
  • @@ -102,25 +102,25 @@ export function NetworkRoles() { title: t('index.networkRoles.roles.developer.title'), description: t('index.networkRoles.roles.developer.description'), image: '/img/roles/developer.png', - href: '/developing/defining-a-subgraph', + href: '/subgraphs/developing/creating/starting-your-subgraph/', }, { title: t('index.networkRoles.roles.indexer.title'), description: t('index.networkRoles.roles.indexer.description'), image: '/img/roles/indexer.png', - href: '/network/indexing', + href: '/indexing/overview/', }, { title: t('index.networkRoles.roles.curator.title'), description: t('index.networkRoles.roles.curator.description'), image: '/img/roles/curator.png', - href: '/network/curating', + href: '/resources/roles/curating/', }, { title: t('index.networkRoles.roles.delegator.title'), description: t('index.networkRoles.roles.delegator.description'), image: '/img/roles/delegator.png', - href: '/network/delegating', + href: '/resources/roles/delegating/', }, ].map((role, index) => ( @@ -159,12 +159,12 @@ export function Products() { { title: t('index.products.products.subgraphStudio.title'), description: t('index.products.products.subgraphStudio.description'), - href: '/deploying/subgraph-studio', + href: '/subgraphs/developing/deploying/using-subgraph-studio/', }, { title: t('index.products.products.graphExplorer.title'), description: t('index.products.products.graphExplorer.description'), - href: '/network/explorer', + href: '/subgraphs/explorer/', }, ].map((product) => (