Ellie Help
Ellie Help Home What's new Getting started9 Work with Ellie4
Write and organise content7
Keep your docs up to date1 Publish and brand3 Walkthrough videos2 Changelog2 Measure and improve1 API reference1 Workspace and billing6 Connect AI tools1 Security and data3 Troubleshooting1
Powered by Ellie Docs
Write and organise content/Decide what your docs should cover

Decide what your docs should cover

Updated 30 Oct 2026

On this page

Use Features to choose which code-derived product features should be included in your documentation. You can hide features you do not want documented, review how Ellie classified them, and adjust their audience or release status when needed.

Before you start

This article covers the Features view, where you decide coverage for product features. To organise articles and sections after that, see Tour of the Content page.

Step by step

  1. Open your project, then go to Features.
    The Features page listing features with release status, audience and on/off controls
  2. Review each feature row. Each row includes the feature name, any edited or flag: ... chips, a code-area count, a short summary, a release-status dropdown, an audience dropdown, and an on/off switch.
  3. Use the on/off switch to decide whether the feature is included in docs. When the switch is on, its tooltip is Included in docs. When the switch is off, its tooltip is Hidden from docs.
  4. If you want to review features you already hid, click Show hidden (N).
    The Features list scrolled to the hidden features, shown faded at the end
  5. Change the Audience dropdown if the feature should be treated differently from Ellie’s automatic classification. The available options are customer docs, internal only, and no docs.
  6. Change the release-status dropdown if the feature is not simply live for customers. Available options include released, rolling out, pre-release, and internal only. Some flagged features may also show is this live? until you answer that question.
  7. Switch a hidden feature back on if you want it included again. Hidden features return to the main list when you restore them.
If a feature shows a flag: ... chip, review its release status before publishing changes. Flagged features can start with is this live? instead of released.

Good to know

What does edited mean?

It means you changed that feature by hand. After that, Ellie keeps your choice instead of overwriting it during re-analysis.

What happens if I mark a feature as pre-release?

Its articles may be held back from normal publishing. Depending on your pre-release setting, they are either kept as drafts or published with a label.

Can changing release status unpublish articles?

Yes. Marking a feature as pre-release or internal only can move already published articles back to draft immediately. If that happens, republish them from Content when the feature is ready.

Recent updates

All updates →
On this page