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

# Create and publish a Help Center article

> Create a draft, preview and publish it, or submit a revision for review without changing the live answer.

Create a Help Center article as a draft, review it, then publish it when customers should see it. Owners and Admins can create and edit articles.

## Create a draft

1. Open **Help Center → Articles → New article**.
2. Enter a clear, task-focused **Title**.
3. Write the **Content** in **Write** mode, or choose **Markdown** to edit its Markdown source.
4. Add a **Short description** for article lists and search results. If it is empty, Protodesk derives one from the article.
5. Confirm the **Language** and choose a **Collection** without child collections.
6. Leave **Status** set to **Draft** and select **Create article**.

An article's language identifies its content; it does not automatically translate the text. For translations of an existing article, use that article's language selector and the **Add translation** option.

## Check article settings

Use **Featured** if the article should be highlighted on the Help home screen. Add focused **Tags** if useful for managing content.

Review the **URL slug** before the first publication. Keep it stable afterward when possible: changing a title does not require changing a shared article URL.

## Review and publish

1. Select **Preview** and read the answer as a customer.
2. Check headings, lists, links, images, tables, and code formatting.
3. Confirm the instructions, role requirements, and limitations against the current product.
4. Change **Status** to **Published** and select **Save changes**.
5. If the whole site is still offline, go to **Help Center → Home → Publish Help Center**.
6. Open the public article and verify its language, content, and links.

Publishing the article and publishing the Help Center site are separate actions. A draft is not public and is not used as published Help Center knowledge for Evelin.

## Update an existing article

Open it from **Articles**. Choose the save action deliberately:

* **Save for review** submits title, short-description, and body changes as a proposal. The current article stays unchanged until a reviewer acts. Keep the slug, status, language, collection, tags, and Featured setting unchanged for this path.
* **Save changes** updates the article directly. If its status is Published, this changes the live answer.

Do not set a published article to Draft just to prepare a revision: saving that change unpublishes it. Use **Save for review** when the existing answer should remain available during review.

If a revision conflict appears, reopen the latest article, compare the changes, and submit the intended revision again. Avoid overwriting another editor's work.

## Remove an article from public view

To keep it for later editing, set **Status** to **Draft** and save. **Delete** removes the article instead; it is not the same as dismissing a review proposal. Review the confirmation carefully before deleting.

For review decisions and their effect on live content, see [Review AI-generated Help Center articles](/guides/review-ai-generated-help-center-articles).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.