---
title: "Publishing"
slug: "publishing"
updated: 2025-10-09T11:01:59Z
published: 2025-10-09T11:01:59Z
canonical: "learn.servitly.com/publishing"
---

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

# Publishing

When editing a component, you can:

- Create multiple [versions](/docs/component-versioning) of the component.
- For each version, you can manage the [Availability](/docs/component-availability) in the various environments (DEVELOP, STAGING, PRODUCTION) you have access.

By combining versions and availability, you can follow these steps to publish your components to a PRODUCTION environment.

1. We suggest that you develop your component by using a draft version installed on a DEVELOP environment. In this way, you can easily [debug](/docs/component-debug) your code without affecting any production environment.
2. When you complete the development, you can promote the draft version to a public version: ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(666).png?sv=2026-02-06&spr=https&st=2026-10-16T18%3A27%3A24Z&se=2026-10-16T19%3A27%3A24Z&sr=c&sp=r&sig=qJlQTgNauI940lH3fjTtO5RDpUEIPsfcCpk0pQxw8wY%3D)
  1. You should promote the draft version to the existing one in case you are making bug fixing or minor updates.
  2. In case you are introducing new features with a big impact on your source code or DPS user experience, you should promote the draft to a new version. This will allow you to have more control over your code and possibly roll it back to a previous version, if needed.
3. In case you have created a new version (e.g., v2), within the [Availability](/docs/component-availability) page, you can define in which environments the new version will be available.

You should start with STAGING and then PRODUCTION.
4. When you change the availability, the component must be manually installed, and you have to go to the [Components](/docs/components) page of the environment.

If the component was already installed, you will find an update, so click the *Update* button, and the component must be activated. ![](https://cdn.document360.io/6759e9c9-3ce3-49df-965a-7231d2d9a10a/Images/Documentation/image(667).png?sv=2026-02-06&spr=https&st=2026-10-16T18%3A27%3A24Z&se=2026-10-16T19%3A27%3A24Z&sr=c&sp=r&sig=qJlQTgNauI940lH3fjTtO5RDpUEIPsfcCpk0pQxw8wY%3D)
5. Navigate the DPS where the component version is installed or updated, and check that everything is working fine.
6. If STAGING, repeat steps 3 and 4 for the PRODUCTION environment.