> ## Documentation Index
> Fetch the complete documentation index at: https://archie.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Editing modules

> Add, remove, and refine the modules in your blueprint.

Modules are the major features of your app — for example, "user accounts," "course catalog," "checkout," "admin dashboard." This page covers how to edit them.

## What a module looks like

Each module in the blueprint has a name, a short description, and a connection to the user types and services it uses. Modules are the building blocks the generator turns into pages, components, and APIs.

<img src="https://mintcdn.com/archie-e998dbf6/eiHdGPkQDkoCG39-/features/blueprint/modules-card-entries.png?fit=max&auto=format&n=eiHdGPkQDkoCG39-&q=85&s=b3071b541e0f0ea31253366a59244b68" alt="Module entry with name, description, and supported user types" width="1182" height="1228" data-path="features/blueprint/modules-card-entries.png" />

## Adding a module

1. Open the **Modules** card on the blueprint page.
2. Click **Add module**.
3. Type a name and a short description.
4. Save.

<img src="https://mintcdn.com/archie-e998dbf6/eiHdGPkQDkoCG39-/features/blueprint/adding-a-module.png?fit=max&auto=format&n=eiHdGPkQDkoCG39-&q=85&s=f7e0a0bd2ade7169c6a38a55eddb7092" alt="Add module form with name, icon, and description" width="1163" height="1022" data-path="features/blueprint/adding-a-module.png" />

The new module is wired into the blueprint immediately. The generator will pick it up on the next build.

## Removing a module

Click the module to open it, then delete. Removing a module also removes references to it from related sections — for example, if a user type's permissions referenced the module.

<img src="https://mintcdn.com/archie-e998dbf6/eiHdGPkQDkoCG39-/features/blueprint/removing-a-module.png?fit=max&auto=format&n=eiHdGPkQDkoCG39-&q=85&s=89513e91cd3281206553adee57ddbf80" alt="Module menu with Remove option" width="940" height="1090" data-path="features/blueprint/removing-a-module.png" />

## Refining a module

You can refine a module two ways:

* **Direct edit** — open the module, change its name or description, save. Best for small changes.
* **Blueprint chat** — describe what you want ("the checkout module should support guest checkout, not just logged-in users"). The chat updates the module in place. Best for substantive changes.

## Common patterns

* **Split** a vague module into two: "Account" → "User profile" + "Account settings."
* **Merge** two related modules: "Notifications" + "Email preferences" → "Notifications."
* **Rename** for clarity: "Admin stuff" → "Admin dashboard."
* **Drop** anything you do not actually need yet — building it later is easier than removing it later.

## FAQ

<AccordionGroup>
  <Accordion title="How many modules should an app have?">
    Most apps have between three and twelve. Anything beyond that suggests modules you should merge or features you can defer to a later build.
  </Accordion>

  <Accordion title="Will edits propagate to user types?">
    Edits do not auto-propagate. If you remove a module, check the related user types and update their permissions.
  </Accordion>
</AccordionGroup>
