Reorganize data landing page (#1382)

* Reorganize data landing page

* remove overview from build your own

* fix typos

* Add chart for rpc vs horizon

* Update docs/data/README.mdx

Co-authored-by: Molly Karcher <[email protected]>

* Update docs/data/indexing/README.mdx

Co-authored-by: Molly Karcher <[email protected]>

* address comments

* Add tutorials

* address comments

* Update hubble description

* expand dropdown

* Merge fixes

* remove duplicate indexers

* update redirects

* Fix rpc link

* Update docs/build/apps/moneygram-access-integration-guide.mdx

Co-authored-by: Elliot Voris <[email protected]>

* remove double slash

* No uppercase all for data dropdown

* fix links from merge

* fix dropdown spacing

* fix merge links

* drop the s from apis in the dropdown

---------

Co-authored-by: Molly Karcher <[email protected]>
Co-authored-by: Elliot Voris <[email protected]>

Author: 3 people

config/sidebars.ts

@@ -21,12 +21,44 @@ const sidebars: SidebarsConfig = {
   ],
   data_overview: [
     'data/README',
-    { type: 'ref', id: 'data/rpc/README', label: 'Stellar RPC'},
-    { type: 'ref', id: 'data/hubble/README', label: 'Hubble'},
-    { type: 'ref', id: 'data/horizon/README', label: 'Horizon'},
-    { type: 'ref', id: 'data/galexie/README', label: 'Galexie'},
-    { type: 'ref', id: 'data/data-indexers/README', label: 'Data Indexers'},
-    { type: 'ref', id: 'data/oracles/README', label: 'Oracles'},
+    {
+      type: 'category',
+      label: 'Analytics',
+      link: { type: 'doc', id: 'data/analytics/README' },
+      items: [
+        { type: 'ref', id: 'data/analytics/hubble/README', label: 'Hubble' },
+        { type: 'ref', id: 'data/analytics/analytics-providers/analytics-providers', label: 'Data Analytics Providers' },
+      ]
+    },
+    {
+      type: 'category',
+      label: 'APIs',
+      link: { type: 'doc', id: 'data/apis/README' },
+      items: [
+        { type: 'ref', id: 'data/apis/rpc/README', label: 'RPC' },
+        { type: 'ref', id: 'data/apis/horizon/README', label: 'Horizon' },
+        { type: 'ref', id: 'data/apis/migrate-from-horizon-to-rpc/migrate-from-horizon-to-rpc', label: 'Migrate Horizon to RPC' },
+        { type: 'ref', id: 'data/apis/rpc/rpc-providers', label: 'RPC Providers' },
+        { type: 'ref', id: 'data/apis/horizon/horizon-providers', label: 'Horizon Providers' },
+      ]
+    },
+    {
+      type: 'category',
+      label: 'Indexers',
+      link: { type: 'doc', id: 'data/indexers/README' },
+      items: [
+        { type: 'ref', id: 'data/indexers/build-your-own/README', label: 'Build Your Own Indexer' },
+        { type: 'ref', id: 'data/indexers/indexer-providers/indexer-providers', label: 'Indexer Providers' },
+      ]
+    },
+    {
+      type: 'category',
+      label: 'Oracles',
+      link: { type: 'doc', id: 'data/oracles/README' },
+      items: [
+        { type: 'ref', id: 'data/oracles/oracle-providers', label: 'Oracle Providers' },
+      ]
+    },
   ],
   tools: [
     {
@@ -56,7 +88,7 @@ const sidebars: SidebarsConfig = {
       items: [
         {
           type: "autogenerated",
-          dirName: "data/horizon",
+          dirName: "data/apis/horizon",
         },
       ],
       collapsible: false,
@@ -69,7 +101,7 @@ const sidebars: SidebarsConfig = {
       items: [
         {
           type: "autogenerated",
-          dirName: "data/hubble",
+          dirName: "data/analytics/hubble",
         },
       ],
       collapsible: false,
@@ -82,7 +114,7 @@ const sidebars: SidebarsConfig = {
       items: [
         {
           type: "autogenerated",
-          dirName: "data/galexie",
+          dirName: "data/indexers/build-your-own/galexie",
         },
       ],
       collapsible: false,
@@ -95,20 +127,46 @@ const sidebars: SidebarsConfig = {
       items: [
         {
           type: 'autogenerated',
-          dirName: 'data/rpc',
+          dirName: 'data/apis/rpc',
+        },
+      ],
+      collapsible: false,
+    },
+  ],
+  analytics: [
+    {
+      type: 'category',
+      label: 'Analytics',
+      items: [
+        {
+          type: "autogenerated",
+          dirName: "data/analytics",
+        },
+      ],
+      collapsible: false,
+    },
+  ],
+  apis: [
+    {
+      type: 'category',
+      label: 'APIs',
+      items: [
+        {
+          type: "autogenerated",
+          dirName: "data/apis",
         },
       ],
       collapsible: false,
     },
   ],
-  data_indexers: [
+  indexers: [
     {
       type: 'category',
-      label: 'Data Indexers',
+      label: 'Indexers',
       items: [
         {
           type: "autogenerated",
-          dirName: "data/data-indexers",
+          dirName: "data/indexers",
         },
       ],
       collapsible: false,

docs/build/apps/moneygram-access-integration-guide.mdx

@@ -542,7 +542,7 @@ onMessage: (transaction) => {
         https://developers.stellar.org/docs/learn/encyclopedia/errors-and-debugging/error-handling
 
         And status/result codes:
-        https://developers.stellar.org/docs/data/horizon/api-reference/errors
+        https://developers.stellar.org/docs/data/apis/horizon/api-reference/errors
       */
 
       // Let's illustrate here how we could handle an 'invalid sequence number' error.
@@ -561,7 +561,7 @@ onMessage: (transaction) => {
           detail: 'The transaction failed when submitted to the stellar network.
             The `extras.result_codes` field on this response contains further details.
             Descriptions of each code can be found at:
-            https://developers.stellar.org/docs/data/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed',
+            https://developers.stellar.org/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed',
           extras: {
             envelope_xdr: 'AAAAAgAAAADBjF7n9gfByOwlnyaJH...k4BRagf/////////8AAAAAAAAAAA==',
             result_codes: { transaction: 'tx_bad_seq' },
@@ -783,12 +783,12 @@ print(
 [stellar lab]: https://lab.stellar.org/
 [anchor directory]: https://resources.stellar.org/anchors?
 [lobstr]: https://lobstr.co/
-[trustline]: ../../data/horizon/api-reference/resources/operations/object/change-trust.mdx
-[sell offer]: ../../data/horizon/api-reference/resources/operations/object/sell-offer.mdx
+[trustline]: ../../data/apis/horizon/api-reference/resources/operations/object/change-trust.mdx
+[sell offer]: ../../data/apis/horizon/api-reference/resources/operations/object/sell-offer.mdx
 [postmessage]: https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage
-[submitting transactions and handling errors gracefully]: /data/horizon/api-reference/errors/error-handling.mdx
-[path payments]: ../../data/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
-[claimable balances]: ../../data/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
+[submitting transactions and handling errors gracefully]: ../../data/apis/horizon/api-reference/errors/error-handling.mdx
+[path payments]: ../../data/apis/horizon/api-reference/resources/operations/object/path-payment-strict-receive.mdx
+[claimable balances]: ../../data/apis/horizon/api-reference/resources/operations/object/create-claimable-balance.mdx
 [moneygram screening questionnaire]: https://stellarquestionnaire.typeform.com/to/RD1a71wQ
 [gcdnjubqsx7ajwljacmj7i4bc3z47bqutmheiczle6mu4kqbryg5jy6b]: https://stellar.expert/explorer/testnet/asset/SRT-GCDNJUBQSX7AJWLJACMJ7I4BC3Z47BQUTMHEICZLE6MU4KQBRYG5JY6B-1
 [gbbd47if6lwk7p7mdevscwr7dpuwv3ny3dtqevfl4nat4aqh3zllfla5]: https://stellar.expert/explorer/testnet/asset/USDC-GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5-1

docs/build/apps/wallet/sep24.mdx

@@ -789,4 +789,4 @@ watcher.controller.stream.listen(
 [sep-10]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md
 [sep-24]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md
 [stellar authentication]: ./sep10.mdx
-[submitting transactions and handling errors gracefully]: /data/horizon/api-reference/errors/error-handling.mdx
+[submitting transactions and handling errors gracefully]: ../../../data/apis/horizon/api-reference/errors/error-handling.mdx

docs/build/guides/basics/classic-transition.mdx

@@ -10,17 +10,17 @@ Stellar recently [upgraded its protocol](https://stellar.org/blog/developers/pro
 
 ### Transitioning from Horizon to RPC
 
-To properly support Stellar's smart contracts, you must use [Stellar RPC](../../../data/rpc). More specifically, you need RPC to simulate transactions that execute smart contracts, as described in the "Simulating Transactions" section, and it provides a convenient [API](../../../data/rpc/api-reference) for consuming contract events. Both of these features are not available in Horizon.
+To properly support Stellar's smart contracts, you must use [Stellar RPC](../../../data/apis/rpc). More specifically, you need RPC to simulate transactions that execute smart contracts, as described in the "Simulating Transactions" section, and it provides a convenient [API](../../../data/apis/rpc/api-reference) for consuming contract events. Both of these features are not available in Horizon.
 
 ### Running Your Own RPC vs. Leveraging Third-Party Providers
 
-You can set up an RPC environment by hosting your own node or using a third-party provider. For guidance on hosting your own instance, including a Docker-based setup, refer to the [Admin Guide](../../../data/rpc/admin-guide). Alternatively, a list of trusted providers is available in the [ecosystem RPC providers documentation](../../../data/rpc/rpc-providers).
+You can set up an RPC environment by hosting your own node or using a third-party provider. For guidance on hosting your own instance, including a Docker-based setup, refer to the [Admin Guide](../../../data/apis/rpc/admin-guide). Alternatively, a list of trusted providers is available in the [ecosystem RPC providers documentation](../../../data/apis/rpc/rpc-providers).
 
 ## 2. Data Ingestion
 
 ### Ingesting Smart Contract Events
 
-Horizon offers an effects endpoint that describes state changes executed by classic operations. Similarly, contracts emit [events](../../../learn/encyclopedia/contract-development/events.mdx) that describe changes to their state, which can be fetched via RPC's API. Off-chain solutions can [monitor and ingest these events](../../../build/guides/events/ingest.mdx) (for token transfers or protocol updates) and remain in sync with on-chain data. Each event is defined by the contract and is subject to standards applied to the implementation. Depending on the requirements for retention, a solution might have to handle ingestion directly or use a [third-party service](../../../data/data-indexers/indexer-providers) for a longer-term history.
+Horizon offers an effects endpoint that describes state changes executed by classic operations. Similarly, contracts emit [events](../../../learn/encyclopedia/contract-development/events.mdx) that describe changes to their state, which can be fetched via RPC's API. Off-chain solutions can [monitor and ingest these events](../../../build/guides/events/ingest.mdx) (for token transfers or protocol updates) and remain in sync with on-chain data. Each event is defined by the contract and is subject to standards applied to the implementation. Depending on the requirements for retention, a solution might have to handle ingestion directly or use a [third-party service](../../../data/indexers/indexer-providers/indexer-providers.mdx) for a longer-term history.
 
 ### Simulating Transaction
 
@@ -44,4 +44,4 @@ Smart contracts can define their own [custom authorization logic](../../../learn
 
 ### Asynchronous Transaction Submission
 
-Unlike Horizon, [RPC only queues transactions for inclusion rather than waiting for final confirmation](../../../data/rpc/api-reference/methods/sendTransaction). Therefore, it is necessary to [poll the transaction’s status](../../../data/rpc/api-reference/methods/getTransaction) to determine if a transaction eventually succeeds or fails. This asynchronous model, as well as other common challenges, can be seen at the [Documentation for Dapp Development - Common Pitfalls](../../../build/guides/dapps/frontend-guide.mdx#7-common-pitfalls).
+Unlike Horizon, [RPC only queues transactions for inclusion rather than waiting for final confirmation](../../../data/apis/rpc/api-reference/methods/sendTransaction). Therefore, it is necessary to [poll the transaction’s status](../../../data/apis/rpc/api-reference/methods/getTransaction) to determine if a transaction eventually succeeds or fails. This asynchronous model, as well as other common challenges, can be seen at the [Documentation for Dapp Development - Common Pitfalls](../../../build/guides/dapps/frontend-guide.mdx#7-common-pitfalls).

docs/build/guides/basics/create-account.mdx

@@ -292,6 +292,6 @@ Now that you’ve got an account, you can [start sending and receiving payments]
 
 <Alert>
 
-In the above code samples, proper error checking is omitted for brevity. However, you should _always_ validate your results, as there are many ways that requests can fail. You should refer to the guide on [Error Handling](/data/horizon/api-reference/errors/error-handling.mdx) for tips on error management strategies.
+In the above code samples, proper error checking is omitted for brevity. However, you should _always_ validate your results, as there are many ways that requests can fail. You should refer to the guide on [Error Handling](../../../data/apis/horizon/api-reference/errors/error-handling.mdx) for tips on error management strategies.
 
 </Alert>

docs/build/guides/basics/follow-received-payments.mdx

@@ -112,7 +112,7 @@ After a few seconds, the Stellar network will perform consensus, close the ledge
 
 ## Following payments using `curl`
 
-To follow new payments connected to your account you simply need to send the `Accept: text/event-stream` header to the [/payments](../../../data/horizon/api-reference/resources/operations/README.mdx) endpoint.
+To follow new payments connected to your account you simply need to send the `Accept: text/event-stream` header to the [/payments](../../../data/apis/horizon/api-reference/resources/operations/README.mdx) endpoint.
 
 <CodeExample>
 
@@ -148,7 +148,7 @@ data: {"_links":{"effects":{"href":"/operations/713226564145153/effects/{?cursor
 
 </CodeExample>
 
-Every time you receive a new payment you will get a new row of data. Payments is not the only endpoint that supports streaming. You can also stream transactions [/transactions](../../../data/horizon/api-reference/resources/transactions/README.mdx) and operations [/operations](../../../data/horizon/api-reference/resources/operations/README.mdx).
+Every time you receive a new payment you will get a new row of data. Payments is not the only endpoint that supports streaming. You can also stream transactions [/transactions](../../../data/apis/horizon/api-reference/resources/transactions/README.mdx) and operations [/operations](../../../data/apis/horizon/api-reference/resources/operations/README.mdx).
 
 ## Following payments using `EventStream`
 

docs/build/guides/basics/send-and-receive-payments.mdx

@@ -19,13 +19,13 @@ Every transaction also incurs a small fee. Like the minimum balance on accounts,
 
 <Alert>
 
-In the following code samples, proper error checking is omitted for brevity. However, you should _always_ validate your results, as there are many ways that requests can fail. You should refer to the guide on [Error Handling](/data/horizon/api-reference/errors/error-handling.mdx) for tips on error management strategies.
+In the following code samples, proper error checking is omitted for brevity. However, you should _always_ validate your results, as there are many ways that requests can fail. You should refer to the guide on [Error Handling](../../../data/apis/horizon/api-reference/errors/error-handling.mdx) for tips on error management strategies.
 
 </Alert>
 
 ## Send a Payment
 
-Stellar stores and communicates transaction data in a binary format called [XDR](../../../learn/encyclopedia/data-format/xdr.mdx), which is optimized for network performance but unreadable to the human eye. Luckily, [Horizon](../../../data/horizon/README.mdx), the Stellar API, and the [Stellar SDKs](../../../tools/sdks/README.mdx) convert XDRs into friendlier formats. Here’s how you might send 10 lumens to an account:
+Stellar stores and communicates transaction data in a binary format called [XDR](../../../learn/encyclopedia/data-format/xdr.mdx), which is optimized for network performance but unreadable to the human eye. Luckily, [Horizon](../../../data/apis/horizon/README.mdx), the Stellar API, and the [Stellar SDKs](../../../tools/sdks/README.mdx) convert XDRs into friendlier formats. Here’s how you might send 10 lumens to an account:
 
 <CodeExample>
 

docs/build/guides/conventions/extending-wasm-ttl.mdx

@@ -25,7 +25,7 @@ Before we demonstrate the TTL extension methods, you should note that in Soroban
 ## Prerequisites
 
 - Stellar SDK: `npm install @stellar/stellar-sdk` for Javascript
-- A [Stellar RPC](../../../data/rpc/README.mdx) endpoint (e.g., `https://soroban-testnet.stellar.org`)
+- A [Stellar RPC](../../../data/apis/rpc/README.mdx) endpoint (e.g., `https://soroban-testnet.stellar.org`)
 - Basic knowledge of the SDK in use
 
 ## Methods for Extending TTL

docs/build/guides/dapps/frontend-guide.mdx

@@ -743,7 +743,7 @@ This is made possible by using the `server.getEvents` method which allows you to
 
 We will be editing the `CounterPage` component to read events from the counter smart contract immediately the page loads to get the initial counter value and update instead of using "Unknown". Before we continue, please take a look at the [contract code](https://github.com/stellar/soroban-examples/blob/main/events/src/lib.rs). In the contract code, an event named `increment` is emitted whenever the `increment` function is called. It is published over 2 topics, `increment` and `COUNTER` and we need to listen to these topics to get the events.
 
-The topics are stored in a data type called `symbol` and we will need to convert both `increment` and `COUNTER` to `symbol` before we can use them in the [`server.getEvents`](https://developers.stellar.org/docs/data/rpc/api-reference/methods/getEvents) method. At maximum, stellar RPCs keep track of events for 7 days and you can query events that happened within the last 7 days, so if you need to store events for longer, you may need to make use of an [indexer](../../../data/data-indexers/README.mdx).
+The topics are stored in a data type called `symbol` and we will need to convert both `increment` and `COUNTER` to `symbol` before we can use them in the [`server.getEvents`](../../../data/apis/rpc/api-reference/methods/getEvents) method. At maximum, stellar RPCs keep track of events for 7 days and you can query events that happened within the last 7 days, so if you need to store events for longer, you may need to make use of an [indexer](../../../data/indexers/indexer-providers).
 
 To use events,we edit our counter page and add the following code:
 

docs/build/guides/dapps/state-archival.mdx

@@ -258,7 +258,7 @@ async function performContractAction(contractId, method, ...args) {
 
 For restoring an entire contract instance, you might need a separate function:
 
-Here we will be using the [`getLedgerEntries` method](/docs/data/rpc/api-reference/methods/getLedgerEntries#requesting-a-contracts-wasm-code) to get the WASM code of the contract and also the [`restoreFootprint` operation](/docs/learn/fundamentals/transactions/list-of-operations#restore-footprint) to restore the contract instance.
+Here we will be using the [`getLedgerEntries` method](/docs/data/apis/rpc/api-reference/methods/getLedgerEntries#requesting-a-contracts-wasm-code) to get the WASM code of the contract and also the [`restoreFootprint` operation](/docs/learn/fundamentals/transactions/list-of-operations#restore-footprint) to restore the contract instance.
 
 ```javascript
 async function restoreContractInstance(contractId) {