Ferndesk
Write articles with AI

Create and edit articles with Fern

Tasks are how you tell Fern what to create or update in your help center. Fern handles the research and writing, you provide the instructions and review the results.

Tasks appear on the Fern page at app.ferndesk.com/fern.

Creating a task

1

Open the task prompt

Go to the Fern page in your dashboard sidebar, or press ⌘N (Mac) or Ctrl+N (Windows/Linux) from anywhere in Ferndesk.

2

Type your instructions

Describe what you need in plain language. Be specific for best results:

  • "Write a getting started guide for new users"

  • "Update the API authentication article with the new OAuth flow"

  • "Create troubleshooting docs for login errors"

Click any template card below the prompt box to pre-fill common requests.

3

Add context and attachments

The more context you provide, the better Fern's output. You can attach:

  • Files: Images (PNG, JPEG, GIF, WebP), videos (MP4, WebM, QuickTime), or documents (PDF, TXT, DOC, XLS, CSV)

  • Links: Paste external URLs or YouTube videos for Fern to reference

  • References: Select existing articles, collections, or support threads to give Fern background information

Drag and drop files, paste screenshots, or use the attachment buttons in the task creation dialog.

4

Submit and track progress

Submit your task and Fern begins researching and drafting. The task appears in your Fern feed where you can monitor progress. Tasks with unpublished drafts show an article icon indicating pending review.

There are three ways to create tasks:

  • From the Fern page: Use the methods above to create tasks directly

  • From audit recommendations: When Fern identifies content gaps or outdated articles in audits, click "Draft with Fern" to generate a task with context already attached

  • From integrations: If you've connected Linear, create documentation tasks directly from issues. See How to use Fern in Linear issues.

What tasks can do

Fern can handle multiple types of documentation work:

  • Create new articles from scratch based on your description

  • Update existing content to reflect product changes or fix errors

  • Research and write from support signals, recommendations, or audits

  • Edit for clarity by rewriting sections or improving structure

  • Create and delete collections to reorganize your help center structure

  • Create sections for top-level navigation tabs

  • Move articles and collections between different locations

  • Delete articles and collections that are outdated or no longer needed

What tasks can't do

  • Answer questions about using Ferndesk: Find answers in the help center instead.

Reviewing and publishing

When Fern finishes drafting an article, it appears at the bottom of your task thread.

  • If the output looks good: Click "Publish changes" to make them live in your help center immediately

  • If it needs changes: Message Fern with additional instructions (e.g., "add more code examples" or "make the tone less technical"), or close the task and create a new one with refined instructions

  • If you don't want it: Close or discard the task

Nothing is published until you explicitly approve it. Fern never auto-publishes drafts.

Tasks that get stuck or stall can usually be resumed by sending Fern a message in the task thread asking it to continue.

After a task is published

Once you publish a task, it becomes read-only.

This is intentional. Published tasks are locked so you can review what was changed without accidentally editing it again.

How to make more changes

If you need to update content that was already published through a task:

  1. Go to the Fern page to start a new task

  2. Describe what you want to change

  3. Attach the same articles or collections as references so Fern has the right context

The new task will pick up where the previous one left off, with full access to the current state of your help center.

Tips for better results

  • @mention articles or collections to tell Fern to focus on them

  • Provide examples: If you want a specific format or style, include an example or reference a similar article

  • Attach supporting materials: Screenshots, spec docs, API response examples—anything that helps Fern understand the feature

  • Link related content: Reference existing articles so Fern maintains consistency with your current documentation

  • Be direct about tone and audience: Specify if you're writing for developers, end users, admins, etc.

Be specific in your prompts. Instead of "write about webhooks," try "write a setup guide for webhooks with code examples showing the payload structure."

Common issues

Task appears stuck

Try refreshing the page. If that doesn't work, try messaging Fern in the task thread to resume progress. Say something like "continue" or "keep going."

Unsupported file types

Convert files to supported formats before attaching: PDF for documents, PNG/JPEG/WEBP for images, MP4/WebM for videos.

Output doesn't match expectations

Try again with a more detailed prompt, additional context, or a reference example of what you want.

Was this helpful?