docs: rename Extend to Expand throughout customization docs
This commit is contained in:
parent
c084ed226e
commit
d7853bf5d8
|
|
@ -80,7 +80,7 @@ Concrete example: a team commits a single file telling Amelia to always use the
|
|||
For the full customization surface and worked examples, see:
|
||||
|
||||
- [How to Customize BMad](../how-to/customize-bmad.md) — the reference for what's customizable and how merge works
|
||||
- [How to Extend BMad for Your Organization](../how-to/extend-bmad-for-your-org.md) — four worked recipes spanning agent-wide rules, workflow conventions, external publishing, and template swaps
|
||||
- [How to Expand BMad for Your Organization](../how-to/expand-bmad-for-your-org.md) — four worked recipes spanning agent-wide rules, workflow conventions, external publishing, and template swaps
|
||||
|
||||
## The Bigger Idea
|
||||
|
||||
|
|
|
|||
|
|
@ -270,7 +270,7 @@ The same field conventions cross the agent/workflow boundary: `activation_steps_
|
|||
|
||||
## Worked Examples
|
||||
|
||||
For complete, enterprise-oriented recipes — shaping an agent across every workflow it dispatches, enforcing org conventions, publishing outputs to Confluence and Jira, and swapping in your own output templates — see [How to Extend BMad for Your Organization](./extend-bmad-for-your-org.md).
|
||||
For complete, enterprise-oriented recipes — shaping an agent across every workflow it dispatches, enforcing org conventions, publishing outputs to Confluence and Jira, and swapping in your own output templates — see [How to Expand BMad for Your Organization](./expand-bmad-for-your-org.md).
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: 'How to Extend BMad for Your Organization'
|
||||
title: 'How to Expand BMad for Your Organization'
|
||||
description: Four customization patterns that reshape BMad without forking — org conventions, agent-wide rules, external publishing, and template swaps
|
||||
sidebar:
|
||||
order: 9
|
||||
|
|
@ -33,7 +33,7 @@ These docs are organized into four sections based on what you're trying to do:
|
|||
| **Explanation** | Understanding-oriented. Deep dives into concepts and architecture. Read when you want to know *why*. |
|
||||
| **Reference** | Information-oriented. Technical specifications for agents, workflows, and configuration. |
|
||||
|
||||
## Extend and Customize
|
||||
## Expand and Customize
|
||||
|
||||
Want to expand BMad with your own agents, workflows, or modules? The **[BMad Builder](https://bmad-builder-docs.bmad-method.org/)** provides the framework and tools for creating custom extensions, whether you're adding new capabilities to BMad or building entirely new modules from scratch.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue