This guide walks you through creating help center articles manually using the article editor. You'll learn how to create, edit, and publish articles without using AI-powered tasks.
Prerequisites
Before creating articles manually, ensure you have:
Admin or editor role permissions
At least one collection created in your help center
You can also use AI-powered tasks to create articles in seconds.
Creating a new article
Follow these steps to create an article manually:
Navigate to your dashboard and open the Help Center section in the sidebar
Find the collection where you want to create the article
Hover over the collection name and click the + button that appears
In the dialog that opens, enter a Title for your article (required)
Optionally, add a Subtitle to provide additional context
Click Create
Your new article will open in the editor, ready for you to add content.
Editing article content
The article editor provides a rich text editing experience with auto-save functionality:
Auto-save: Your changes are automatically saved as drafts every few seconds
Rich text formatting: Use the editor toolbar to format text, add links, insert images, and more
Title and subtitle: Edit these fields directly at the top of the editor
Collection placement: Change which collection contains your article using the breadcrumb navigation
All changes are saved as drafts until you publish. Your readers won't see unpublished changes.
Publishing your article
When your article is ready to go live:
Review your content in the editor
Click the Publish article button in the header (or Publish changes if updating an existing article)
Your article will be published immediately and visible to users in your help center
You'll see a success confirmation once the article is live.
Troubleshooting common issues
Article appears read-only
If your help center is integrated with an external provider (ex. Intercom or Zendesk) and the article exists on that platform, it will be read-only to prevent conflicts. Manage the article directly in your external platform instead.