refactor(docs): updated running a node documentation (#679)

Author: dineshpinto

docs/1-intro.mdx

@@ -176,9 +176,9 @@ Its native data protocols - [Flare Time Series Oracle](/ftso/overview) and [Flar
     <DocCard
       item={{
         type: "link",
-        label: "Run a Validator Node",
-        href: "/run-node/validator-node",
-        description: "Earn rewards by helping secure Flare.",
+        label: "Run an RPC Node",
+        href: "/run-node#rpc-node",
+        description: "Service application requests locally or publicly.",
         docId: undefined,
       }}
     />
@@ -187,10 +187,9 @@ Its native data protocols - [Flare Time Series Oracle](/ftso/overview) and [Flar
     <DocCard
       item={{
         type: "link",
-        label: "Run a Flare Entity",
-        href: "/run-node/flare-entity",
-        description:
-          "Validate blocks and provide data for Flare's enshrined oracles.",
+        label: "Run a Validator Node",
+        href: "/run-node#validator-node",
+        description: "Earn rewards by helping secure Flare.",
         docId: undefined,
       }}
     />
@@ -199,9 +198,10 @@ Its native data protocols - [Flare Time Series Oracle](/ftso/overview) and [Flar
     <DocCard
       item={{
         type: "link",
-        label: "Run an RPC Node",
-        href: "/run-node/rpc-node",
-        description: "Service application requests locally or publicly.",
+        label: "Run a Flare Entity",
+        href: "/run-node#flare-entity",
+        description:
+          "Validate blocks and provide data for Flare's enshrined oracles.",
         docId: undefined,
       }}
     />

docs/2-run-node.mdx

@@ -0,0 +1,82 @@
+---
+title: Run a Node
+description: Run a node on Flare.
+keywords: [rpc, validator, nodes, flare-network, flare-entity]
+---
+
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
+import DocCardList from "@theme/DocCardList";
+
+Running your own node is the most direct way to connect to and interact with the Flare network.
+Whether you need to query blockchain data for your application, want to help secure the network by validating transactions, or aim to participate fully in Flare's data protocols, setting up a node is the first step.
+
+This guide covers the different types of nodes you can run - RPC, Validator, and Flare Entity - and provides links to detailed setup instructions for each.
+
+## RPC Node
+
+Allows applications to read blockchain data and submit transactions.
+Does not participate in consensus.
+
+<DocCardList
+  items={[
+    {
+      type: "link",
+      label: "Check System requirements",
+      href: "run-node/system-requirements",
+      description: "Minimum hardware requirements for running a node.",
+    },
+    {
+      type: "link",
+      label: "Run Node from source",
+      href: "run-node/from-source",
+      description: "Run a Flare node from go-flare source code.",
+    },
+    {
+      type: "link",
+      label: "Run Node using Docker",
+      href: "run-node/using-docker",
+      description: "Run a Flare node using Docker.",
+    },
+  ]}
+/>
+
+## Validator Node
+
+Secures the network by validating transactions and participating in consensus.
+Setting up a validator starts with installing a standard node (see [RPC Node](#rpc-node)).
+Once your node is running, proceed with the registration:
+
+<DocCardList
+  items={[
+    {
+      type: "link",
+      label: "Register as Validator",
+      href: "run-node/register-validator",
+      description: "Register your node as a validator.",
+    },
+  ]}
+/>
+
+## Flare Entity
+
+Runs alongside a Validator to provide crucial data for Flare's FTSO and FDC protocols.
+Required for full reward eligibility.
+Requires a running [Validator Node](#validator-node). To set up a Flare Entity:
+
+<DocCardList
+  items={[
+    {
+      type: "link",
+      label: "Set Up Flare Entity",
+      href: "run-node/flare-entity",
+      description: "Provide data for Flare's enshrined FTSO and FDC protocols.",
+    },
+  ]}
+/>
+
+:::tip[Systems Explorer]
+
+All registered Flare Entities, alongside voting and reward epoch, and finalization data can be viewed on the [Flare Systems Explorer](https://flare-systems-explorer.flare.network/providers).
+
+:::

docs/fassets/guides/8-infrastructure.mdx

@@ -15,9 +15,8 @@ This guide explains how to configure it to utilize your own infrastructure for e
 
 ## Prerequisites
 
-- [Running an RPC node](/run-node/rpc-node)
-- [Configure FTSO data provider](/run-node/ftso-data-provider)
-- [Configuring FDC attestation provider](/run-node/fdc-attestation-provider)
+- [Running an RPC node](/run-node#rpc-node)
+- [Configure a Flare Entity](/run-node#flare-entity)
 - [Setting up DAL](https://github.com/flare-foundation/data-availability)
 
 ## Setting Up

docs/fdc/1-overview.mdx

@@ -47,7 +47,7 @@ For a detailed explanation of the FDC mechanism, read the [FDC whitepaper](/pdf/
 The Data Availability Layer (DA Layer) provides API endpoints for querying offchain attestation data.
 Accessing this data is trustless, as users can independently compute and compare Merkle roots against the onchain version.
 
-Operating a DA Layer is permissionless—anyone can run a DA Layer service by sourcing data from an [FTSOv2 data provider](/run-node/ftso-data-provider) and [FDC attestation provider](/run-node/fdc-attestation-provider).
+Operating a DA Layer is permissionless—anyone can run a DA Layer service by sourcing data from an [Flare Entity](/run-node/flare-entity).
 
 <ThemedImage
   alt="DA Layer Diagram"

docs/ftso/guides/make-volatility-incentive.mdx

@@ -34,7 +34,7 @@ Before reading this guide, make sure you understand [FTSOv2's Volatility Incenti
 
 This guide provides code examples demonstrating how to make an FTSOv2 volatility incentive offer using various programming languages. To make a volatility incentive offer, you need three key pieces of information:
 
-1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can use a node provider service or point to your [own RPC node](/run-node/rpc-node). A comprehensive list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
+1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can use a node provider service or point to your [own RPC node](/run-node#rpc-node). A comprehensive list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
 
 2. **Contract Address:** The address for the `FastUpdateIncentiveManager` contract varies by network. You can obtain this address in two ways:
 

docs/ftso/guides/query-feed-configuration.mdx

@@ -28,7 +28,7 @@ import FtsoConfigGo from "!!raw-loader!/examples/developer-hub-go/ftsov2_config_
 
 This guide provides code examples demonstrating how to read FTSOv2 feed configurations offchain using various programming languages. To achieve this, you need two key pieces of information:
 
-1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can either use a node provider service or point to your [own RPC node](/run-node/rpc-node). A list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
+1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can either use a node provider service or point to your [own RPC node](/run-node#rpc-node). A list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
 
 2. **Contract Address:** The address for the `FastUpdatesConfiguration` contract varies by network. You can obtain this address in two ways:
 

docs/ftso/guides/read-feeds-offchain.mdx

@@ -28,7 +28,7 @@ import ReadOffhainGo from "!!raw-loader!/examples/developer-hub-go/ftsov2_consum
 
 This guide provides code examples demonstrating how to read FTSOv2 feeds offchain using various programming languages. To read a block-latency feed offchain, you need three key pieces of information:
 
-1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can use a node provider service or point to your [own RPC node](/run-node/rpc-node). A comprehensive list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
+1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can use a node provider service or point to your [own RPC node](/run-node#rpc-node). A comprehensive list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
 
 2. **Contract Address:** Feeds are served on the `FtsoV2` contract, whose address varies by network. You can obtain this address in two ways:
 

docs/network/0-overview.mdx

@@ -325,7 +325,7 @@ Discover suitable options for your needs on the [Flare Wallets](https://flare.ne
 :::note[Adding Flare (FLR) to your exchange]
 
 Integrating Flare is similar to integrating Ethereum or other EVM chains.
-To add it to your exchange set up an [RPC node](/run-node/rpc-node) and use the appropriate [network configuration](#configuration) for Flare Mainnet.
+To add it to your exchange set up an [RPC node](/run-node#rpc-node) and use the appropriate [network configuration](#configuration) for Flare Mainnet.
 
 Additional resources: [Flare Brand assets](https://flare.network/media/), [go-flare Source Code](https://github.com/flare-foundation/go-flare)
 

docs/network/guides/secure-random-numbers.mdx

@@ -153,7 +153,7 @@ Participants can enter the lottery, and the winner is drawn using the secure ran
 
 To obtain a secure random number offchain, you need two key pieces of information:
 
-1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can use a node provider service or point to your [own RPC node](/run-node/rpc-node). A comprehensive list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
+1. **RPC Endpoint URL:** The RPC Endpoint URL determines which network your code will interact with. You can use a node provider service or point to your [own RPC node](/run-node#rpc-node). A comprehensive list of public and private RPC endpoints for all Flare networks is available on the [Network Configuration](/network/overview#configuration) page.
 
 2. **Contract Address:** The address for the `RandomNumberV2` contract varies by network. You can obtain this address in two ways: