More nav changes (proposal)

packages/nextra-theme/package.json

@@ -35,16 +35,16 @@
     "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",
     "react-intersection-observer": "^9.14.0",
     "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",

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(' > ')}
                 </div>
               ) : null}
-              {frontMatter.title ? <Heading.H1>{frontMatter.title}</Heading.H1> : null}
+              {frontMatter.title || args.activeIndex === 0 ? (
+                <Heading.H1>{args.activeIndex === 0 ? 'The Graph Docs' : frontMatter.title}</Heading.H1>
+              ) : null}
               {lastUpdated || readingTime ? (
                 <Paragraph size="14px">
                   {lastUpdated ? (

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"
   }
 }

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"
   }

website/pages/[locale]/index.mdx

@@ -35,7 +35,7 @@ ${t('index.networkRoles.description')}
 ## ${t('index.supportedNetworks.title')}
 ${t('index.supportedNetworks.description')}
 <SupportedNetworks />
-${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: {

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.
 

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.

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.
 

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/). تحتوي الأسئلة الشائعة على تفسيرات متعمقة لكيفية استخدام الأدوات وكيفية عملها والأمور التي يجب وضعها في الاعتبار عند إستخدامها.
 
 ## كيف تنقل الغراف الفرعي الخاص بك إلى شبكة آربترم (الطبقة الثانية)
 

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?