# Edit an EventCatalog resource

Copy as Markdown[View as Markdown](/docs/editor/how-to/edit-resource.md)

***

Use this guide when you want to update a resource that already exists in your catalog.

## Open the resource[​](#open-the-resource "Direct link to Open the resource")

Start the editor and choose a resource from the resource list.

The editor supports common EventCatalog resource types, including [domains](/docs/development/guides/domains/introduction.md), [services](/docs/development/guides/services/introduction.md), [events](/docs/development/guides/messages/events/introduction.md), [commands](/docs/development/guides/messages/commands/introduction.md), [queries](/docs/development/guides/messages/queries/introduction.md), [channels](/docs/development/guides/channels/introduction.md), [entities](/docs/development/guides/domains/entities/introduction.md), [data stores](/docs/development/guides/data/introduction.md), [flows](/docs/development/guides/flows/introduction.md), [users](/docs/development/guides/owners/users/introduction.md), and [teams](/docs/development/guides/owners/teams/introduction.md).

![Resource list with a service selected](/assets/images/editor-cb04fe252a011dca91668794595d1dda.png)

## Edit the documentation[​](#edit-the-documentation "Direct link to Edit the documentation")

Use the rich editor to change the resource body.

The rich editor supports common writing blocks such as headings, paragraphs, lists, tables, blockquotes, code blocks, links, and dividers.

Use `/` in an empty paragraph to open the block menu. Slash commands also help you insert EventCatalog components such as diagrams, callouts, steps, tiles, prompts, and resource-aware blocks. Learn more in [Use slash commands](/docs/editor/how-to/use-slash-commands.md).

![Slash command menu showing EventCatalog components](/assets/images/custom-slash-commands-e8f5237c2e7f2eca6e506fdfbd1c4a5c.png)

## Edit resource metadata[​](#edit-resource-metadata "Direct link to Edit resource metadata")

Use the resource fields to update common frontmatter values such as:

* Name
* Summary
* Owners
* Badges
* Repository links
* Draft status
* Resource image or icon

Some resource types have extra fields. For example, services can model sent and received messages, and data stores can describe type, technology, access mode, classification, retention, and residency.

## Edit relationships[​](#edit-relationships "Direct link to Edit relationships")

Use relationship fields to connect resources.

For example:

* Add services to a domain
* Show messages a service sends or receives
* Connect services to data stores they read from or write to
* Connect [owners](/docs/owners.md) to resources

These fields update the same resource metadata that EventCatalog uses when it renders architecture relationships.

## Create related resources[​](#create-related-resources "Direct link to Create related resources")

When a relationship field allows new resources, the editor can create the resource and model how it relates to the current resource.

For example, when creating an event from a service, choose whether the service publishes the event, consumes the event, or only contains the event in its folder.

![Create event dialog showing relationship choices](/assets/images/creating-new-event-modal-9313ea338d7085526e92ac0c696733b3.png)

## Edit flows[​](#edit-flows "Direct link to Edit flows")

Flow resources include a visual Flow Editor for modeling business processes, user journeys, and architecture workflows.

![Flow editor showing a service node in a business flow](/assets/images/flow-editor-937ce8d4a9f7bc699612a92bad0c2ef2.png)

Learn how to [use the Flow Editor](/docs/editor/how-to/use-flow-editor.md).

## Use source mode[​](#use-source-mode "Direct link to Use source mode")

Switch to source mode when you need to edit Markdown, MDX, or frontmatter directly.

![Editor source mode showing Markdown and frontmatter](/assets/images/using-source-mode-5818fdd65a747fb0da734e91b4e542eb.png)

Source mode is useful for:

* Checking exact frontmatter
* Editing custom MDX components
* Making changes the rich editor does not expose yet
* Copying content from another file

## Save conflicts[​](#save-conflicts "Direct link to Save conflicts")

If the file changed on disk after the editor loaded it, the editor protects you from overwriting those changes.

Reload the resource, review the external change, and apply your edit again.