When you ship something big
When a big feature ships, customers look for it in your docs the same day. Get the article, the changelog entry and the screenshots ready before you announce, so the docs match the launch.
The person who owns the launch runs this. An owner or admin publishes. Contributors can prepare drafts and submit them for review.
Ask Fern the day it merges
Don't wait for the weekly review. Start a task with the pull request, the spec or the Linear issue, and say who the feature is for. If Fern already drafted from the merge, add your notes to that task instead. See Ask Fern to write or update articles.
Review and publish before the announcement
Check the names, the plan it is on, the limits and the rollout. If the feature stays behind a flag until launch day, keep the draft and publish when it is on.
Post the changelog entry and announce it
Ask Fern for the changelog entry in the same task. When you publish the entry, choose whether to announce it in the widget. See Publish a changelog.
Refresh the screenshots
Once the release is live on the dashboard Fern signs in to, ask Fern to retake the screenshots in articles that show the changed screens. See Capture screenshots automatically.
Check what your AI agent says
Your AI agent answers from published articles. Ask it the questions customers will ask about the feature, and fix the article if an answer is off. See Review your AI agent's answers each week.
Who does what
Step | Who |
|---|---|
Ask Fern for the article | Whoever built or shipped the feature |
Review and publish | An owner or admin |
Changelog entry and widget announcement | An owner or admin |
Screenshots | The launch owner, once the release is live |
Check your AI agent | Whoever answers support |