# Versioning

Copy as Markdown[View as Markdown](/docs/development/guides/services/versioning-and-lifecycle/versioning.md)

***

All content in EventCatalog can be versioned. This allows you to keep historic versions of content which can give context to users why things are changing.

## How to version a service[​](#how-to-version-a-service "Direct link to How to version a service")

1. Create a `/versioned` directory inside the `/services` folder if one is not created already.

2. Create a new folder with the version number inside the folder.
   <!-- -->
   * Example: `/services/Orders/versioned/0.0.1`

3. Copy contents into the new folder, it at least needs your index.mdx file.

   <!-- -->

   * Example: `/services/Orders/versioned/0.0.1/index.mdx`
   * Note: the version inside this index.mdx file would be `0.0.1`

4. Bump the version of the `index.mdx` file in the route of the domain.
   <!-- -->
   * Example `/services/Orders/index.mdx`, change the `version` to `0.0.2`

## How to navigate to versions[​](#how-to-navigate-to-versions "Direct link to How to navigate to versions")

EventCatalog will automatically create links for you within your latest version of your document. Users will also be able to navigate to any version by adding the version in the url (e.g /docs/services/Orders/1.0.2 would load the 1.0.2 version of this service).

![Example](/assets/images/versioned-cb5c80464784c26d425ff797e95b5fa6.png)