Refactor configuration slugs for guides; add RedText component in various how-to guides for enhanced readability and emphasis

Author: Sipher

astro.config.mjs

@@ -78,9 +78,9 @@ export default defineConfig({
               label: "Holders",
               collapsed: false,
               items: [
-                { label: "Setup a Wallet", slug: "how-to-guides/participants/setup-a-wallet" },
-                { label: "Bridge from Base", slug: "how-to-guides/participants/bridge-from-base" },
-                { label: "Stake your Torus", slug: "how-to-guides/participants/stake-your-torus" },
+                { label: "Setup a Wallet", slug: "how-to-guides/holders/setup-a-wallet" },
+                { label: "Bridge from Base", slug: "how-to-guides/holders/bridge-from-base" },
+                { label: "Stake your Torus", slug: "how-to-guides/holders/stake-your-torus" },
               ],
             },
             {

src/components/RedText.astro

@@ -0,0 +1,18 @@
+---
+export interface Props {
+  variant?: 'attention' | 'light' | 'soft';
+  class?: string;
+}
+
+const { variant = 'light', class: className = '' } = Astro.props;
+
+const variantClasses = {
+  attention: 'text-red-attention',
+  light: 'text-red-light', 
+  soft: 'text-red-soft'
+};
+
+const redClass = variantClasses[variant];
+---
+
+<span class={`${redClass} ${className}`} style="display: inline;"><slot /></span>

src/content/docs/development/web/overview-and-setup.mdx

@@ -18,7 +18,7 @@ The ecosystem is built using a monorepo with [Turborepo](https://turbo.build/rep
 
 <Aside type="tip">
   To access environments pointing to the testnet nodes, add the `.testnet`
-  subdomain to the URL, eg. `https://allocator.testnet.torus.network/`
+  subdomain to the URL, eg. `https://portal.testnet.torus.network/root-allocator`
 </Aside>
 
 ## Prerequisites

src/content/docs/development/web/querying-data.mdx

@@ -6,7 +6,7 @@ description: Learn how to query the stake weight between keys
 import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
 
 Our API allows you to retrieve information about the stake allocation between keys and agents.
-You can query this data by making a GET request to: `https://allocator.torus.network/api/allocated-weight`.
+You can query this data by making a GET request to: `https://portal.torus.network/api/allocated-weight`.
 
 ## API Response Format
 
@@ -29,12 +29,12 @@ The API response has the following structure:
 
         To filter the response for a specific allocating key, append the userKey query parameter to the API endpoint:
 
-        ```allocator.torus.network/api/allocated-weight?userKey=<SS58Address>```
+        ```portal.torus.network/api/allocated-weight?userKey=<SS58Address>```
     - Filter by Agent Key
 
         To filter the response for specific agents, append the agentKey query parameter to the API endpoint:
 
-        ```allocator.torus.network/api/allocated-weight?agentKey=<SS58Address>```
+        ```portal.torus.network/api/allocated-weight?agentKey=<SS58Address>```
 
 
     <Aside type="note">

src/content/docs/explanations/builders/agent-registration.mdx

@@ -38,7 +38,7 @@ The burn mechanism maintains network quality by creating economic barriers to sp
 
 ### Discovery and Capabilities
 
-Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator page](https://allocator.torus.network/).
+Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator tab](https://portal.torus.network/root-allocator).
 They can participate in the permission system, create named capabilities for other agents to invoke, and engage in governance proposals.
 Agent metadata is stored off-chain via IPFS but referenced on-chain through content hashes.
 

src/content/docs/how-to-guides/builders/create-signal.mdx

@@ -9,6 +9,7 @@ import {
   CardGrid,
   Card
 } from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
 
 In this guide, we'll **create a demand signal** to express your need for specialized capabilities from other agents.
 
@@ -35,7 +36,7 @@ Signaling demand allows you to delegate part of your emissions to agents who can
   </Card>
   <Card title="Available Emission Allocation" icon="seti:license">
     Have incoming emission streams available to offer as incentive for capability providers.
-    You can find a [guide on how to stake TORUS here](https://docs.torus.network/how-to-guides/participants/stake-your-torus/).
+    You can find a [guide on how to stake TORUS here](https://docs.torus.network/how-to-guides/holders/stake-your-torus/).
   </Card>
 </CardGrid>
 
@@ -48,11 +49,11 @@ Signaling demand allows you to delegate part of your emissions to agents who can
 
 
 2. **Connect your Torus wallet**  
-   Connect the wallet that owns the agent you want to signal from.
+   Connect the <RedText variant="light">wallet that owns the agent</RedText> you want to signal from.
 
-3. **Fill in the signal details:**
-   
-   Signals allow agents to express their demand for specialized capabilities in both technical and economic terms. Here's an **example** of what a signal might look like:
+3. **Fill in the signal details**   
+   Signals allow agents to express their demand for specialized capabilities in both technical and economic terms.
+   Here's an <RedText variant="light">example of what a signal could look like</RedText>:
 
    ```
    Title: Short, descriptive name for the capability you need
@@ -90,10 +91,10 @@ Signaling demand allows you to delegate part of your emissions to agents who can
    </Aside>
 
 4. **Review and publish the signal**  
-   Double-check your details and publish to make it discoverable.
+   Double-check your details and <RedText variant="light">publish to make it discoverable</RedText>.
 
 5. **All Done**  
-   Your demand signal is now visible in the Torus graph and signal marketplace for other agents to discover.
+   Your demand signal is now visible in the Torus graph and [signal marketplace for other agents](https://portal.torus.network/signals/signal-list) to discover.
 
 </Steps>
 

src/content/docs/how-to-guides/builders/delegate-emission-streams.mdx

@@ -11,6 +11,7 @@ import {
   Tabs,
   TabItem
 } from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
 
 In this guide, we'll set up **emission permissions** to delegate portions of your token streams to other agents.  
 This enables economic coordination, agent hiring, and revenue sharing structures.
@@ -102,7 +103,7 @@ Emission permissions work with **stream identity preservation**:
    Verify all details before submitting.
 
 7. **Submit emission permission**  
-   Sign the transaction to create the delegation on-chain.
+   <RedText variant="light">Sign the transaction</RedText> to create the delegation on-chain.
 
 8. **Monitor delegation**  
    Track delegation status in the Portal dashboard.
@@ -117,15 +118,15 @@ Emission permissions work with **stream identity preservation**:
 ### Stream-Based Delegation
 
 **Select Streams**: Choose which emission streams to delegate
-- View all your active streams with their StreamIds
-- See current flow rates and sources
-- Select specific streams for delegation
+- View all your <RedText variant="light">active streams with their StreamIds</RedText>
+- See <RedText variant="light">current flow rates and sources</RedText>
+- Select <RedText variant="light">specific streams for delegation</RedText>
 
 **Set Percentages**: Define allocation per stream
 ```
-Stream A (Staking): 25% → Agent Bob
-Stream B (Fees): 50% → Agent Charlie
-Stream C (Root): 10% → Agent Dave
+Stream A (Staking): <RedText variant="light">25%</RedText> → Agent Bob
+Stream B (Fees): <RedText variant="light">50%</RedText> → Agent Charlie
+Stream C (Root): <RedText variant="light">10%</RedText> → Agent Dave
 ```
 
 **Safety Validation**: System ensures totals don't exceed 100% per stream
@@ -136,9 +137,9 @@ Stream C (Root): 10% → Agent Dave
 ### Fixed Amount Delegation
 
 **Amount**: Specify TORUS amount per period
-- Daily allocation: `100 TORUS/day`
-- Weekly allocation: `700 TORUS/week`
-- Monthly allocation: `3000 TORUS/month`
+- Daily allocation: <RedText variant="light">`100 TORUS/day`</RedText>
+- Weekly allocation: <RedText variant="light">`700 TORUS/week`</RedText>
+- Monthly allocation: <RedText variant="light">`3000 TORUS/month`</RedText>
 
 **Payment Schedule**: Define distribution frequency
 - Real-time (continuous)
@@ -147,9 +148,9 @@ Stream C (Root): 10% → Agent Dave
 - Monthly distributions
 
 **Source Priority**: Order which streams fund fixed payments
-1. Staking rewards (priority 1)
-2. Delegation fees (priority 2)
-3. Other streams (priority 3)
+1. <RedText variant="light">Staking rewards</RedText> (priority 1)
+2. <RedText variant="light">Delegation fees</RedText> (priority 2)
+3. <RedText variant="light">Other streams</RedText> (priority 3)
 
 </TabItem>
 </Tabs>

src/content/docs/how-to-guides/builders/edit-your-agent.mdx

@@ -12,13 +12,14 @@ import {
 
 
 import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
 import registeredAgents from '/public/images/how-to-guide/register-an-agent/registered-agent-on-allocator-page.png';
 import editAgent from '/public/images/how-to-guide/edit-your-agent/allocator-card-edit-agent.png';
 import toastExample from '/public/images/how-to-guide/edit-your-agent/allocator-success-toast.png';
 
 
 In this guide, we'll walk through the process of **editing your Agent information** with the Torus Allocator.
-Both the **Registered Agent** and **Root Agent** can edit their information. Just make sure to use the proper filter on the Allocator Page.  
+Both the **Registered Agent** and **Root Agent** can edit their information. <RedText variant="light">Just make sure to use the proper filter on the Allocator tab</RedText>.  
 In this guide we will be editing the information of a **Registered Agent**.
 
 #### Why edit your agent?
@@ -41,11 +42,11 @@ and ensures your agent represents your current capabilities and offerings.
 <CardGrid>
   <Card title="Torus Wallet" icon="seti:license">
     Make sure you have a Torus wallet set up and ready to use.
-    You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/participants/setup-a-wallet/).
+    You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
   </Card>
   <Card title="Torus Balance" icon="seti:shell">
-    Check your balance in the [Torus Wallet](https://wallet.torus.network) and ensure you have enough Free Balance to cover the registration fees.
-    You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/bridge-to-base/).
+    Check your balance in the [Torus Wallet](https://wallet.torus.network) and ensure you have enough **Free Balance** to cover the registration fees.
+    You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
   </Card>
   <Card title="Registered or Root Agent" icon="seti:license">
     You must have a Registered or Root Agent to edit your information.
@@ -56,13 +57,13 @@ and ensures your agent represents your current capabilities and offerings.
   ## Edit your Agent Information
 
 <Steps>
-1. **Find your Agent in the [Allocator App](https://allocator.torus.network/)**   
+1. **Find your Agent in the [Allocator Tab](https://portal.torus.network/root-allocator)**   
     You can either search for your Agent by name or by the address.  
 
-   <ClickableImage src={registeredAgents} alt="Allocator Page" />
+   <ClickableImage src={registeredAgents} alt="Allocator tab" />
 
 2. **Click on the card of your Agent**    
-    The edit is in the Detailed View of the Agent.
+    The edit is in the **Detailed View** of the Agent.
    <ClickableImage src={editAgent} alt="Edit Agent" />
 
 3. **Edit the information and Submit**  
@@ -81,12 +82,12 @@ and ensures your agent represents your current capabilities and offerings.
         - Telegram
     ```
 4. **Sign the Transaction in the SubWallet and Wait for the Confirmation**   
-  You will be prompted by SubWallet to sign the on-chain transaction.
-  Once confirmed, a toast notification will appear to indicate that your allocation was successful.
+  You will be prompted by <RedText variant="light">SubWallet to sign the on-chain transaction</RedText>.
+  Once confirmed, a notification will appear to indicate that your allocation was successful.
     <ClickableImage src={toastExample} alt="Allocator Success Toast" />
 
 5. **All Done**  
-  You can now see your updated information in the Allocator App.
+  You can now see your updated information in the [Allocator Tab](https://portal.torus.network/root-allocator).
 
 
 </Steps>
@@ -95,7 +96,7 @@ and ensures your agent represents your current capabilities and offerings.
 
 After updating your agent information:
 
-- **Monitor your presence**: Check how your agent appears on the [Allocator page](https://allocator.torus.network/)
+- **Monitor your presence**: Check how your agent appears on the [Allocator tab](https://portal.torus.network/root-allocator)
 - **Stay up to date**: Keep your information updated to match the latest changes
 - **Build capabilities**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide services
 

src/content/docs/how-to-guides/builders/manage-capabilities.mdx

@@ -11,6 +11,7 @@ import {
 } from "@astrojs/starlight/components";
 
 import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
 import confirmCapability from '/public/images/how-to-guide/manage-capabilities/create-capability-confirm-information.png';
 
 In this guide, we'll walk through **managing capabilities** in the Torus control space.  
@@ -37,7 +38,7 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
 <CardGrid>
   <Card title="Registered Agent" icon="seti:license">
     You must have a registered agent on Torus.
-    Follow the [agent registration guide](register-an-agent) if needed.
+    Follow the [agent registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) if needed.
   </Card>
   <Card title="Torus Balance" icon="seti:shell">
     Ensure you have enough TORUS to cover capability registration and deposit fees.
@@ -62,7 +63,7 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
    - The `capability-path` is the custom route you define (e.g. `tokens`, `profile_data`, etc.).
 
     <Aside type="note">
-      Capability paths can only contain **lowercase letters**, **numbers**, **hyphens**, and **underscores**.  
+      Capability paths can only contain <RedText variant="light">**lowercase letters**</RedText>, <RedText variant="light">**numbers**</RedText>, <RedText variant="light">**hyphens**</RedText>, and <RedText variant="light">**underscores**</RedText>.  
       You **do not** need to type the agent name or method — they are handled by the UI.
 
       **Examples:**
@@ -94,13 +95,13 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
 
 5. **Review information, Submit and Sign the Transaction**  
     Review the capability path in the **Full Capability Path** field.   
-    If everything is correct, click **Create Capability**.   
-    Open the SubWallet extension and sign the transaction.   
+    If everything is correct, click <RedText variant="light">**Create Capability**</RedText>.   
+    Open the SubWallet extension and <RedText variant="light">sign the transaction</RedText>.   
     <ClickableImage src={confirmCapability} alt="Confirm Capability" />
 
 6. **All Done**   
     You've now successfully created a capability on the Torus control space.
-    Now you can delegatepermissions to it.
+    Now you can delegate permissions to it.
 </Steps>
 
 ### Delete a Capability path

src/content/docs/how-to-guides/builders/manage-permissions.mdx

@@ -11,6 +11,7 @@ import {
   Tabs,
   TabItem
 } from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
 
 In this guide, we'll walk through **managing permissions** in Torus's recursive delegation system.  
 Permissions enable fine-grained control over emission distribution and capability access between agents.