docs: blocks terminology update

docs/customize/custom-providers.mdx

@@ -9,7 +9,7 @@ As an example, say you are working on solving a new GitHub Issue. You type '@Iss
 
 ## How Do Context Blocks Work?
 
-You can add context providers to assistants using [`context` blocks](/hub/configs/block-types#context). Explore available context blocks in [the hub](https://hub.continue.dev/explore/context).
+Explore available context blocks in [the hub](https://hub.continue.dev/explore/context).
 
 ## Built-in Context Providers
 

docs/customize/deep-dives/mcp.mdx

@@ -19,8 +19,8 @@ that can be set up with custom tools.
 Currently custom tools can be configured using the Model Context
 Protocol standard to unify prompts, context, and tool use.
 
-MCP Servers can be added to hub configs using `mcpServers` blocks. You can
-explore available MCP server blocks
+MCP Servers can be added to hub configs using `mcpServers`. You can
+explore available MCP servers
 [here](https://hub.continue.dev/explore/mcp).
 
 <Info>MCP can only be used in the **agent** mode.</Info>
@@ -72,8 +72,7 @@ For example, place your JSON MCP config file at `.continue/mcpServers/mcp.json`
 
 To set up your own MCP server, read the [MCP
 quickstart](https://modelcontextprotocol.io/quickstart) and then [create an
-`mcpServers`
-block](https://hub.continue.dev/new?type=block&blockType=mcpServers) or add a local MCP
+`mcpServers`](https://hub.continue.dev/new?type=block&blockType=mcpServers) or add a local MCP
 server block to your [config file](./configuration.md):
 
 ```yaml title="config.yaml"
@@ -94,7 +93,7 @@ When creating a standalone block file in `.continue/mcpServers/`, remember to in
 
 ### How to Configure MCP Server Properties
 
-MCP blocks follow the established syntax for blocks, with a few additional properties specific to MCP servers.
+MCP components include a few additional properties specific to MCP servers.
 
 - `name`: A display name for the MCP server.
 - `type`: The type of the MCP server: `sse`, `stdio`, `streamable-http`

docs/customize/deep-dives/rules.mdx

@@ -76,7 +76,7 @@ Now test your rules by asking a question about a file in chat.
 
 ![pirate rule test](/images/pirate-rule-test.png)
 
-## How to Create Rules Blocks
+## How to Create Rules
 
 ### Creating Local Rules
 
@@ -85,7 +85,7 @@ Rules can be added locally using the "Add Rules" button.
 ![add local rules button](/images/add-local-rules.png)
 
 <Info>
-**Automatically create local rule blocks**: When in Agent mode, you can prompt the agent to create a rule for you using the `create_rule_block` tool if enabled.
+**Automatically create local rules**: When in Agent mode, you can prompt the agent to create a rule for you using the `create_rule_block` tool if enabled.
 
 For example, you can say "Create a rule for this", and a rule will be created for you in `.continue/rules` based on your conversation.
 </Info>
@@ -135,7 +135,7 @@ To move local rules to the Hub:
   recommend Markdown.
 </Info>
 
-Rules blocks can be simple text, written in YAML configuration files, or as Markdown (`.md`) files. They can have the following properties:
+Rules can be simple text, written in YAML configuration files, or as Markdown (`.md`) files. They can have the following properties:
 
 - `name` (**required** for YAML): A display name/title for the rule
 - `globs` (optional): When files are provided as context that match this glob pattern, the rule will be included. This can be either a single pattern (e.g., `"**/*.{ts,tsx}"`) or an array of patterns (e.g., `["src/**/*.ts", "tests/**/*.ts"]`).

docs/customize/model-providers/top-level/tetrate_agent_router_service.mdx

@@ -168,9 +168,6 @@ context:
   - uses: continuedev/terminal-context
   - uses: continuedev/file-context
 ```
-<Tip>
-To customize, see the [model block creation guide](/hub/configs/create-a-block).
-</Tip>
 
 </Tab>
 

docs/docs.json

@@ -203,16 +203,7 @@
                   "hub/configs/edit-a-config"
                 ]
               },
-              {
-                "group": "Blocks",
-                "icon": "cube",
-                "pages": [
-                  "hub/blocks/intro",
-                  "hub/blocks/use-a-block",
-                  "hub/blocks/block-types",
-                  "hub/blocks/create-a-block"
-                ]
-              },
+
               {
                 "group": "Governance",
                 "icon": "building",
@@ -389,7 +380,27 @@
     },
     {
       "source": "/hub/blocks",
-      "destination": "/hub/blocks/intro"
+      "destination": "/hub/introduction"
+    },
+    {
+      "source": "/hub/blocks/intro",
+      "destination": "/hub/introduction"
+    },
+    {
+      "source": "/hub/blocks/use-a-block",
+      "destination": "/hub/introduction"
+    },
+    {
+      "source": "/hub/blocks/block-types",
+      "destination": "/hub/introduction"
+    },
+    {
+      "source": "/hub/workflows/intro",
+      "destination": "/hub/agents/intro"
+    },
+    {
+      "source": "/hub/blocks/create-a-block",
+      "destination": "/hub/introduction"
     },
     {
       "source": "/customize",
@@ -1061,7 +1072,7 @@
     },
     {
       "source": "/hub/blocks/bundles",
-      "destination": "/hub/blocks/intro"
+      "destination": "/hub/introduction"
     },
     {
       "source": "/customize/settings",

docs/hub/workflows/intro.mdx → docs/hub/agents/intro.mdx

@@ -1,6 +1,7 @@
 ---
-title: "Introduction"
+title: "Agents Introduction"
 description: "Run and manage background agents in Mission Control"
+sidebarTitle: "Agents"
 ---
 
 <Info>

docs/hub/configs/create-a-config.mdx

@@ -8,7 +8,6 @@ sidebarTitle: "Create a Config"
 
 To create an config from scratch, select “New config” in the top bar.
 
-
 Choose a name, slug, description, and icon for your config.
 
 The easiest way to create an config is to click "Create config" with the default configuration and then add / remove blocks using the sidebar.
@@ -17,15 +16,15 @@ Alternatively, you can edit the config YAML directly before clicking "Create con
 
 
 
-## How to Remix an config
+## How to Remix a Config
 
 You can also create an config by remixing an existing one. This is useful if you want to start with a pre-configured config and make modifications.
 
 By clicking the “remix” button, you’ll be taken to the “Create a remix” page.
 
 Once here, you’ll be able to
 
-1. add or remove blocks in YAML configuration
+1. add or remove components from the config.
 2. change the name, description, icon, etc.
 
 Clicking “Create config” will make this config available for use.

docs/hub/configs/edit-a-config.mdx

@@ -3,16 +3,17 @@ title: "How to Edit a Config"
 description: "New versions of a config can be created and published using the sidebar."
 ---
 
-First, select a config from the dropdown at the top.
+First, select a config either from the Hub search or one that you've installed.
 
-While editing a config, you can explore the hub and click "Add Block" from a block page to add it to your config.
+While editing a config, you can explore the hub and click "+" to add it to your config.
 
-For blocks that require secret values like API keys, you will see a small notification on the block's tile in the sidebar that will indicate if action is needed.
+For tools or models that require secret values like API keys, you will see a small notification on its tile that will indicate if action is needed.
 
-To delete a block, click the trash icon.
 
-If a block you want to use does not exist yet, you can [create a new block](/hub/configs/create-a-block).
+To delete part of your config, you can remove it from the yaml.
+
+If a rule, prompt, or tool you want to use does not exist yet, you can [create it](/hub/introduction#creating-components).
 
 When you are done editing, click "Publish" to publish a new version of the config.
 
-Click "Open VS Code" or "Open JetBrains" to open your IDE for using the config.
+Reload your terminal or IDE to use the latest version of the config in your agents.

docs/hub/configs/intro.mdx

@@ -1,6 +1,101 @@
 ---
-title: "Introduction"
+title: "Introduction to Configs"
 description: "Custom configuration options include Models, MCP Servers, Rules, Prompts, etc."
+sidebarTitle: "Configs"
 ---
 
-Following the [`config.yaml`](/reference) format, you can create a custom configuration for the Continue CLI and IDE extensions.
+
+## What Are Configs?
+
+Configs are flexible containers that combine multiple components to create powerful AI coding experiences using the Continue CLI or the Extensions. A single config can include:
+
+<CardGroup cols={2}>
+
+  <Card title="Models" icon="cube">
+
+    Large Language Models for chat, autocomplete, editing, and more
+
+  </Card>
+
+  <Card title="MCPs" icon="wrench">
+
+    Model Context Protocol servers that provide tools and capabilities
+
+  </Card>
+
+  <Card title="Rules" icon="shield">
+
+    Guidelines that shape AI behavior and responses
+
+  </Card>
+
+  <Card title="Prompts" icon="message-square">
+
+    Reusable instructions for common coding tasks
+
+  </Card>
+
+</CardGroup>
+
+## How Configs Work
+
+Think of configs as recipes for AI assistance. Each config defines:
+
+- **What models** to use for different tasks (chat, autocomplete, code editing)
+- **Which tools** are available through MCP servers
+- **How the AI behaves** through rules and guidelines  
+- **Pre-built prompts** for common workflows
+
+This flexibility lets you create specialized setups for different contexts, like a Next.js config with React-specific rules and tools, or a data science config with Python analysis capabilities.
+
+## Config Permissions
+
+When creating configs, you can set visibility levels:
+
+- **Personal**: Only you can see and use the config
+- **Public**: Anyone can discover and use your config
+- **Organization**: Members of your organization can access the config
+
+## Working with Configs
+
+You can interact with configs in three main ways:
+
+- **Create**: Build a new config from scratch or start with a template
+- **Edit**: Modify your existing configs by adding/removing components
+- **Remix**: Take someone else's config and customize it for your needs
+
+## Getting Started
+
+<Steps>
+
+  <Step title="Explore existing configs">
+
+    Browse the [Continue Hub](https://hub.continue.dev/?type=assistants) to see what configs others have built
+
+  </Step>
+
+  <Step title="Add a config to your account">
+
+    Click "Install Config" (+) on any config that interests you
+
+  </Step>
+
+  <Step title="Customize as needed">
+
+    Add your API keys and customize components to match your workflow
+
+  </Step>
+
+  <Step title="Use in your IDE">
+
+    Select the config from the dropdown in your Continue extension, type `/config` in the CLI, or use `--config` with the CLI commands
+
+  </Step>
+
+</Steps>
+
+## Config Format
+
+All configs follow the [`config.yaml`](/reference) format, whether you're using the hub interface or editing files locally. This ensures consistency between hub-managed and local configurations.
+
+