Update documentation for MASQ Network, including renaming the web3 privacy browser, adding client redirects, and enhancing the sidebar structure.

- Changed title from 'MASQ Docs' to 'MASQ Network Documentation'.
- Implemented client redirects for legacy paths to ensure smooth navigation.
- Updated sidebar categories and labels for improved clarity and organization.
- Removed outdated documentation related to the MASQ web3 privacy browser and consolidated relevant content.
- Added linting step to CI workflows for better code quality assurance.

Author: kauri-hero

.eslintrc.js

@@ -0,0 +1,24 @@
+/** @type {import('eslint').Linter.Config} */
+module.exports = {
+  root: true,
+  extends: ['plugin:@docusaurus/recommended'],
+  env: {
+    browser: true,
+    node: true,
+    es2022: true,
+  },
+  parserOptions: {
+    ecmaVersion: 'latest',
+    sourceType: 'module',
+    ecmaFeatures: {
+      jsx: true,
+    },
+  },
+  ignorePatterns: [
+    'build/',
+    '.docusaurus/',
+    'node_modules/',
+    'working-docs/',
+    'gitbook-src/',
+  ],
+};

.github/workflows/deploy.yml

@@ -19,6 +19,8 @@ jobs:
           cache: npm
       - name: Install dependencies
         run: npm ci
+      - name: Lint
+        run: npm run lint
       - name: Build website
         run: npm run build
       - name: Upload Build Artifact

.github/workflows/test-deploy.yml

@@ -23,5 +23,7 @@ jobs:
           cache: npm
       - name: Install dependencies
         run: npm ci
+      - name: Lint
+        run: npm run lint
       - name: Test build website
         run: npm run build

AGENTS.md

@@ -140,5 +140,5 @@ When continuing polish / visual QA (see `working-docs/HANDOVER-HARDENING.md` if
 ```powershell
 git status -sb
 npm run build
-# spot-check: npm start → /, /masq-web3-privacy-browser, /resources/installer-checksums
+# spot-check: npm start → /, /masq-privacy-browser, /resources/installer-checksums
 ```

docs/advanced-use/cli-startup-guides/index.mdx

@@ -1,11 +1,15 @@
+import DocCardList from '@theme/DocCardList';
+
 # CLI Startup Guides
 
-This are targeting to Quality Assurance (QA) testing for our development, but will be helpful for you to prepare your machine to run from Command Line (CLI)
+These guides target Quality Assurance (QA) testing for our development, but they also help you prepare a machine to run MASQ from the command line (CLI).
 
 :::warning
 
 Running MASQ from CLI **will** require technical knowledge and possibly adjustments to the network adaptor settings.
 
 MASQ and the developers are not responsible for any issues that arise from user changes to their environment or machine!
 
-:::
+:::
+
+<DocCardList />

docs/core-concepts/cores-packages/index.mdx

@@ -1,3 +1,5 @@
+import DocCardList from '@theme/DocCardList';
+
 # CORES Packages
 
 A CORE(s) package is a series of instructions bundled in a way that allows each node within the network to receive just enough information to make a decision on how to handle a request. CORES stands for **C**lient-**O**rigin-**R**elay-**E**xit-**S**erver
@@ -14,4 +16,6 @@ Each Node that handles a CORES package plays a specific role in the life-cycle o
 * **Originator:** The identity of the originating request node.
 * **Relay:** Identifies Nodes that will be used to hop along routes to get to its destination.
 * **Exit:** The exit node will make the true web request on behalf of the originator and send it back along the route stack.
-* **Server:** Information about the server that is hosting the requested information.
+* **Server:** Information about the server that is hosting the requested information.
+
+<DocCardList />

docs/core-concepts/index.mdx

@@ -1 +1,7 @@
-# 📑 Core Concepts
+import DocCardList from '@theme/DocCardList';
+
+# Core Concepts
+
+How the MASQ Network works under the hood — neighborhoods, gossip, CORES packages, encryption, and clandestine routing.
+
+<DocCardList />

docs/core-concepts/neighborhoods/index.mdx

@@ -1,7 +1,11 @@
+import DocCardList from '@theme/DocCardList';
+
 # MASQ Neighborhoods
 
 Each MASQ Node in the MASQ Network contains a subsystem that we call the Neighborhood. The Neighborhood is responsible for keeping track of other Nodes in the network, remembering how (and whether) they're connected to one another, and storing other information about them as well.
 
 Currently, there are plans for neighborhoods to also remember things like when they were last used, what region they are operating in, how fast they have proven to be and whether they're acting suspiciously. Also, whenever a consuming Node wants to send a CORES package through the network, its Neighborhood is responsible for analyzing the network and determining what route the CORES package should take. This takes place through a 'routing engine' in the Node which evaluates all possible known routes in the Neighborhood and ranks them according to the most desirable (usually based on price of the route, number of hops etc).
 
 The concept of MASQ Neighborhoods is also such that no single MASQ Node will be able to have awareness or knowledge of the entire MASQ Network - neighborhoods have a limitation in number of Nodes within reach of the Gossip protocol.
+
+<DocCardList />

docs/developers/dev-docs/index.mdx

@@ -1,5 +1,5 @@
 # Technical Documentation
 
-Some helpful documentation and notes for developers
+Some helpful documentation and notes for developers.
 
-More information and links to README files from our Node repo will be added periodically
+More information and links to README files from our Node repo will be added periodically.

docs/ecosystem-accelerator/summary/index.mdx

@@ -2,7 +2,7 @@
 
 MASQ Network is proud to announce the initiation of its Ecosystem Accelerator. This program is a strategic effort to foster growth within the MASQ ecosystem - by honouring and rewarding users, developers and community members who bring growth and innovation within MASQ’s web3 privacy space.
 
-**The Ecosystem Accelerator Program reflects our unwavering commitment to fostering a vibrant and dynamic ecosystem, where community engagement and development are not just encouraged, but actively facilitated.** 
+**The Ecosystem Accelerator Program reflects our unwavering commitment to fostering a vibrant and dynamic ecosystem, where community engagement and development are not just encouraged, but actively facilitated.**
 
 ***