Add "Technology" section

docs/api/reference/eth-sendrawtransaction.mdx

@@ -31,7 +31,7 @@ On Linea, each transaction is represented by a sequence of lines representing th
 happening at the EVM level. These lines are grouped by modules and are used as inputs to the prover. 
 In order to limit the resources required to generate proofs, limits are enforced on the maximum 
 number of lines each module can have. Hence, when a transaction is considered for inclusion in a 
-block, a [line count check is performed to ensure it conforms to the requirements](../../get-started/concepts/prover/prover-limits.mdx).
+block, a [line count check is performed to ensure it conforms to the requirements](../../technology/prover/prover-limits.mdx).
 
 ## Parameters
 

docs/get-started/build/quickstart/deploy.mdx

@@ -7,8 +7,12 @@ pagination_prev: null
 image: /img/socialCards/deploy-your-contract.jpg
 ---
 
-Building apps on Linea needn't be complicated. In this guide, we'll walk you through using
-[Foundry](https://book.getfoundry.sh/) to create a new project from scratch. 
+Building apps on Linea needn't be complicated. Linea is Ethereum Virtual Machine (EVM)-equivalent,
+providing a developemnt experience identical to Ethereum, and allowing you to leverage the many 
+smart contracts, tools, and libraries created for EVM chains. 
+
+In this guide, we'll walk you through using [Foundry](https://book.getfoundry.sh/) to create a new 
+project from scratch. 
 
 This involves:
 1. [Creating a project](#create-your-project)

docs/get-started/how-to/bridge/index.mdx

@@ -17,7 +17,7 @@ implementation or building a dedicated token bridge.
 :::note
 We recommend that tech operators that want to provide liquidity use the
 [**Native Bridge for Tech Operators**](https://bridge.linea.build/) which provides the interface to
-the [canonical token bridge](../../concepts/canonical-token-bridge.mdx).
+the [canonical token bridge](../../../technology/canonical-token-bridge.mdx).
 :::
 
 Select one of the following cards for instructions to bridge using the default canonical token bridge.

docs/get-started/how-to/gas-fees.mdx

@@ -31,7 +31,7 @@ components:
 These two resource costs are abstracted by the rollup and covered by the recommended L2 gas price
 and gas used.
 
-> Learn more about gas on Linea on our [support page](https://support.linea.build/getting-started/what-does-gas-pay-for/) 
+> Learn more about gas on Linea on our [support page](https://support.linea.build/getting-started/what-does-gas-pay-for) 
 and release notes for [Alpha v2](../../release-notes.mdx#alpha-v2) and [Alpha v3](../../release-notes.mdx#alpha-v3).
 
 `linea_estimateGas` is the recommended method for estimating gas on Linea. See our 
@@ -126,7 +126,7 @@ takes precedence.
 `baseFeePerGas`, and `priorityFeePerGas`, and therefore provides a more precise gas estimate than 
 the alternatives.
 
-It can also help prevent transactions from being rejected due to exceeding [module limits](../concepts/prover/prover-limits.mdx).
+It can also help prevent transactions from being rejected due to exceeding [module limits](../../technology/prover/prover-limits.mdx).
 
 ### Example
 

docs/get-started/index.mdx

@@ -12,7 +12,7 @@ Linea has been incubated within Consensys and will decentralize in Q1 2025.
 Our mission is to empower developers to build the next generation of decentralized applications and 
 onboard the next billion users to web3. 
 
-## Low-cost security
+## Security for all
 
 Built as a layer above Ethereum, Linea inherits the robust security and decentralization of the 
 Ethereum network while significantly increasing throughput and reducing transaction fees to 

docs/get-started/tooling/cross-chain/ccip-read.mdx

@@ -22,7 +22,7 @@ Linea ENS repository therefore adds support for CCIP Read to Linea.
 
 :::info 
 
-Read more about sparse Merkle trees in our [architecture documentation](../../concepts/state-manager.mdx).
+Read more about sparse Merkle trees in our [architecture documentation](../../../technology/state-manager.mdx).
 
 :::
 

docs/release-notes.mdx

@@ -830,7 +830,7 @@ Contracts audit is in progress. This doesn't reflect final versions.
 
 **Canonical Token Bridge**
 
-Major changes are applied to the Canonical Token Bridge as described in our [documentation](../docs/get-started/concepts/canonical-token-bridge.mdx).
+Major changes are applied to the Canonical Token Bridge as described in our [documentation](./technology/canonical-token-bridge.mdx).
 
 - **L1 (Goerli)**
 

docs/get-started/concepts/decentralization.mdx → docs/technology/decentralization.mdx

@@ -28,11 +28,11 @@ During this phase we convened the first iteration of the Linea Security Council,
 monitor the network, protect users, and mitigate the risks associated with a new production system. 
 The Security Council is managed through a multi-sig Safe (formerly Gnosis Safe) contract that 
 requires certain thresholds of signatures to be submitted to carry out an action. Details can be 
-found in our [risk disclosures](../../risk-disclosures/index.mdx).
+found in our [risk disclosures](../risk-disclosures/index.mdx).
 
 Finally, the client software used to run a local node on the Linea network was made publicly 
 available, giving any actor the option to verify the Linea state for themselves and minimize trust 
-in the Linea operator. View our [node running guides](../../get-started/how-to/run-a-node/index.mdx) to get started.
+in the Linea operator. View our [node running guides](../get-started/how-to/run-a-node/index.mdx) to get started.
 
 ## Phase 1 — Current
 
@@ -43,7 +43,7 @@ Open-sourcing Linea's software stack is an essential element of our roadmap, fos
 and aligning with web3 values. The Linea software stack is publicly available under the 
 [AGPL-2.0](https://www.apache.org/licenses/LICENSE-2.0) license, which ensures that users have the 
 freedom to view, fork, and modify the code. An overview of Linea's repositories is available in 
-our [architecture section](./index.mdx). 
+our [architecture section](./repos.mdx). 
 
 The second cornerstone of this phase is the implementation of **100% EVM coverage** in the zkEVM 
 arithmetization. Linea will generate proofs of computation for all EVM opcodes and precompiles,

docs/get-started/concepts/network-data.mdx → docs/technology/network-data.mdx

@@ -4,8 +4,6 @@ sidebar_position: 7
 image: /img/socialCards/network-data.jpg
 ---
 
-## Other Functions: Network Data
-
 ### What is it?
 
 One of the main value propositions of a public blockchain network is that it be, well, _public_. This means that the information about what’s going on the network needs to be readily available. Networks like Ethereum have this more or less built in and available as part of the software: each node has an API that will return any information you ask for; if you have a lot of requests, well, you just need more nodes.

docs/get-started/concepts/prover/prover-limits.mdx → docs/technology/prover/prover-limits.mdx

@@ -28,10 +28,10 @@ manageable scope, and that a proof can be generated.
 Transactions rejected for exceeding module limits can be identified through the following
 methods, which return an error:
 
-- [`linea_estimateGas`](../../../api/reference/linea-estimategas.mdx)
-- [`eth_sendRawTransaction`](../../../api/reference/eth-sendrawtransaction.mdx)
+- [`linea_estimateGas`](../../api/reference/linea-estimategas.mdx)
+- [`eth_sendRawTransaction`](../../api/reference/eth-sendrawtransaction.mdx)
 
-Use [`linea_getTransactionExclusionStatusV1`](../../../api/reference/linea-gettransactionexclusionstatusv1.mdx)
+Use [`linea_getTransactionExclusionStatusV1`](../../api/reference/linea-gettransactionexclusionstatusv1.mdx)
 to get the rejection status of a transaction hash, if it was sent and didn't get rejected directly, 
 nor included in a block.
 

docs/get-started/build/repos.mdx → docs/technology/repos.mdx

@@ -10,8 +10,6 @@
 Each repository that hosts the Linea software is listed below, together with a description of its 
 purpose.
 
-For further details about the components and architecture of Linea, see the [concepts section](../concepts/index.mdx).
-
 ## Linea repositories
 
 ### [`linea-monorepo`](https://github.com/Consensys/linea-monorepo)
@@ -52,7 +50,7 @@
 The Linea implementation of Besu, an Ethereum client, extended with plugins.
 
 As Linea is EVM-equivalent, it is compatible with standard Ethereum clients without plugins; for 
-example, you can also [run a Linea node using Geth](../how-to/run-a-node/geth.mdx). 
+example, you can also [run a Linea node using Erigon, Nethermind, or Geth](../get-started/how-to/run-a-node/index.mdx). 
 
 ### [`linea-sequencer`](https://github.com/Consensys/linea-sequencer)
 

docusaurus.config.js

@@ -133,6 +133,12 @@ const config = {
             position: "left",
             label: "Learn",
           }, */
+          {
+            type: "doc",
+            docId: "technology/architecture",
+            position: "left",
+            label: "Technology",
+          },
           {
             type: "doc",
             docId: "api/index",

redirects.json

@@ -1,12 +1,13 @@
 [
     {
-        "to": "/get-started/concepts/message-service",
+        "to": "/technology/message-service",
         "from": [
             "/developers/bridge-architecture/message-service",
             "/developers/use-message-bridge",
             "/architecture/stack/canonical-msg-service/message-service",
             "/architecture/stack/canonical-msg-service",
-            "/architecture/canonical-msg-service"
+            "/architecture/canonical-msg-service",
+            "/get-started/concepts/message-service"
         ]
     },
     {
@@ -129,61 +130,69 @@
         ]
     },
     {
-        "to": "/get-started/concepts/decentralization",
+        "to": "/technology/decentralization",
         "from": [
             "/use-mainnet/decentralization-roadmap",
             "/decentralization-roadmap",
-            "/architecture/overview/decentralization-roadmap"
+            "/architecture/overview/decentralization-roadmap",
+            "/get-started/concepts/decentralization"
         ]
     },
     {
-        "to": "/get-started/concepts/transaction-lifecycle",
+        "to": "/technology/transaction-lifecycle",
         "from": [
             "/architecture/transaction-lifecycle",
-            "/architecture/overview/transaction-lifecycle"
+            "/architecture/overview/transaction-lifecycle",
+            "/get-started/concepts/transaction-lifecycle"
         ]
     },
     {
-        "to": "/get-started/concepts/network-data",
+        "to": "/technology/network-data",
         "from": [
             "/architecture/network-data",
-            "/architecture/overview/network-data"
+            "/architecture/overview/network-data",
+            "/get-started/concepts/network-data"
         ]
     },
     {
-        "to": "/get-started/concepts/canonical-token-bridge",
+        "to": "/technology/canonical-token-bridge",
         "from": [
             "/architecture/bridges",
             "/architecture/stack/bridges",
-            "/architecture/stack/bridges/canonical-token-bridge"
+            "/architecture/stack/bridges/canonical-token-bridge",
+            "/get-started/concepts/canonical-token-bridge"
         ]
     },
     {
-        "to": "/get-started/concepts/coordinator",
+        "to": "/technology/coordinator",
         "from": [
             "/architecture/coordinator",
-            "/architecture/stack/coordinator"
+            "/architecture/stack/coordinator",
+            "/get-started/concepts/coordinator"
         ]
     },
     {
-        "to": "/get-started/concepts/state-manager",
+        "to": "/technology/state-manager",
         "from": [
             "/architecture/evm-state-manager",
-            "/architecture/stack/evm-state-manager"
+            "/architecture/stack/evm-state-manager",
+            "/get-started/concepts/state-manager"
         ]
     },
     {
-        "to": "/get-started/concepts/sequencer",
+        "to": "/technology/sequencer",
         "from": [
             "/architecture/sequencer",
-            "/architecture/stack/sequencer"
+            "/architecture/stack/sequencer",
+            "/get-started/concepts/sequencer"
         ]
     },
     {
-        "to": "/get-started/concepts/prover",
+        "to": "/technology/prover",
         "from": [
             "/architecture/trace-expansion-proving",
-            "/architecture/stack/trace-expansion-proving"
+            "/architecture/stack/trace-expansion-proving",
+            "/get-started/concepts/prover"
         ]
     },
     {
@@ -231,36 +240,60 @@
         ]
     },
     {
-        "to": "/get-started/concepts/architecture",
-        "from": "/architecture"
+        "to": "/technology/architecture",
+        "from": [
+            "/architecture",
+            "/get-started/concepts/architecture"
+        ]
     },
     {
-        "to": "/get-started/build/repos",
-        "from": "/architecture/stack"
+        "to": "/technology/repos",
+        "from": [
+            "/architecture/stack",
+            "/get-started/build/repos"
+        ]
     },
     {
-        "to": "/get-started/concepts/sequencer/conflation",
-        "from": "/architecture/stack/sequencer/conflation"
+        "to": "/technology/sequencer/conflation",
+        "from": [
+            "/architecture/stack/sequencer/conflation",
+            "/get-started/concepts/sequencer/conflation"
+        ]
     },
     {
-        "to": "/get-started/concepts/sequencer/traces-generator",
-        "from": "/architecture/stack/sequencer/traces-generator"
+        "to": "/technology/sequencer/traces-generator",
+        "from": [
+            "/architecture/stack/sequencer/traces-generator",
+            "/get-started/concepts/sequencer/traces-generator"
+        ]
     },
     {
-        "to": "/get-started/concepts/prover/prover-limits",
-        "from": "/architecture/stack/trace-expansion-proving/prover-limits"
+        "to": "/technology/prover/prover-limits",
+        "from": [
+            "/architecture/stack/trace-expansion-proving/prover-limits",
+            "/get-started/concepts/prover/prover-limits"
+        ]
     },
     {
-        "to": "/get-started/concepts/prover/proving",
-        "from": "/architecture/stack/trace-expansion-proving/proving"
+        "to": "/technology/prover/proving",
+        "from": [
+            "/architecture/stack/trace-expansion-proving/proving",
+            "/get-started/concepts/prover/proving"
+        ]
     },
     {
-        "to": "/get-started/concepts/prover/trace-expansion",
-        "from": "/architecture/stack/trace-expansion-proving/trace-expansion"
+        "to": "/technology/prover/trace-expansion",
+        "from": [
+            "/architecture/stack/trace-expansion-proving/trace-expansion",
+            "/get-started/concepts/prover/trace-expansion"
+        ]
     },
     {
-        "to": "/get-started/concepts",
-        "from": "/architecture/overview"
+        "to": "/technology/architecture",
+        "from": [
+            "/architecture/overview",
+            "/get-started/concepts"
+        ]
     },
     {
         "to": "/get-started/tooling/social-login/openfort",