Support browser translation for public Help Center articles

Public Help Center pages currently prevent browser translation of article content. Readers can see Chrome’s Translate option, but the article remains in its original language. Allow readers to translate public documentation using their browser’s built-in translation, while preserving necessary protections for interactive elements. This would make the documentation easier to use when a reader’s preferred language is not available.

Read Help Center article analytics through API and MCP

Get Help Center analytics through the API and MCP: article views, reactions, and search terms, including searches with no results. This would let teams and AI agents find articles that nobody reads, articles with negative reactions, and missing content, and then keep the Help Center up to date from their own tools.

Update Help Center settings through API and MCP

Change Help Center settings through the API and MCP, such as the display name, title, description, search placeholder, navigation links, and visibility. Today these settings can be read through the API but only changed in the dashboard. This would let teams manage their whole Help Center from their own tools or AI workflows.

Image upload endpoint for Help Center articles

Provide a way to attach images to Help Center articles through the API, ideally a multipart upload endpoint that stores the file and returns a Featurebase-hosted URL for use in the article body. Alternatively, add multipart support to articles.create and articles.update, or confirm that base64 data URIs and external URLs in an article body are pulled into Featurebase storage as the changelog docs describe. Local screenshot files have no public URL, and embedding base64 bytes in the tool call is slow, error-prone and bloats the body, so the final step currently has to be done manually in the dashboard editor.

Support dynamic base URLs in the API playground

API documentation readers cannot currently enter a customer-specific base URL. Support reader-entered server URLs without requiring every URL to be listed in the OpenAPI spec. For embedded documentation, also allow the host application to pass the current site’s URL into the playground automatically.

Help Center-wide snapshot and versioning

Provide snapshotting or versioning for the Help Center as a whole, not just per-article history. Article-level version history already exists, but there is no way to restore the entire knowledge base after a destructive change. Broader team access combined with irreversible deletion makes an accidental mass wipe unrecoverable.

More text formatting options in Help Center articles (color, size, highlight) for accessibility and branding

Requested on a demo call: more color options, text sizing, and a highlight option for Help Center article text. This matters both for branding consistency and for ADA/accessibility compliance, since the current color options are limited.

Option to add JSON Schema to help center articles for better AIO/AEO

We’re trying to get our Help Center articles to appear in Google search and other external/third-party AI search results. They rely on JSON schemas that are usually inserted into the HTML of the page. Here’s some details: https://201creative.com/structured-data-ai-search/

Open specific article directly in the app as modal or in messenger

We currently use helpscout and they have a nice option to open a specific knowledge base article using various display styles: modal, in the messenger, etc. Read more here: https://developer.helpscout.com/beacon-2/web/javascript-api/#beaconarticle This allows us to surface relevant help articles directly within our product, one-click away. It is a must have for us before we can migrate our help center to Featurebase.

Custom font size range (~10-48pt) in Help Center article editor, independent of heading levels

Add the ability to set a specific text size (roughly 10pt to 48pt) on any text selection in the Help Center article editor, independent of the H1/H2/H3 heading levels. Today, text sizing is tied to heading levels only \u2014 there's no way to bump body text up or down a couple of sizes for emphasis or readability the way most text editors (including Zendesk's) allow. Related: there's also an existing request for full colour-wheel/hex selection in the same editor (https://feedback.featurebase.app/p/helpdocs-color-palette) \u2014 both come from the same underlying need for finer text formatting control when producing reader-friendly articles. Raised during an active enterprise trial migrating from Zendesk (iClassPro).

Bulk actions in help center

Select multiple Help Center articles and update them in one action. Bulk actions should include: Change visibility and access settings, including Everyone, Team members, and segments Move articles to a collection Publish, unpublish, or delete articles

Automatic Help Center updates with AI

Help center should automatically keep itself up to date with smart suggestions based on your: support conversations changelogs roadmap

Help Center dashboard with filters & custom columns

We have a lot of articles. It would be nice to filter the overview page for them in the dashboard by title, author, publication status, translation status, parent collection, etc. Choose which information to display and filter by, including title, collection, author, publication status, translation status, visibility and segments, last updated date, and article views. This would make it much easier to audit and manage larger Help Centers without opening articles individually.

Add one article to multiple collections

Often, 1 article should be ideally shown in multiple relevant collections (linear example):

llms.txt

Convert our help center to llms.txt format https://help.fables.gg/llms.txt

Support copying links to accordion elements

One of the main use-cases of the accordion elements in FAQ sections is to answer recurring questions. It would make sense to be able to copy a link to these sections (like you can to titles) to easily share them with users.

Search results for Help Center analytics

In Help Center analytics, show what keywords users search, their results, how many didn’t show anything, etc. Basically, everything that Intercom shows 👇

Help center subdirectory hosting

Hello, do you have any plans to support subdirectories? For example, using ‘helpcenter’ as a directory for my own domain, similar to: xxx.com/help. The reason for doing this is that subdirectories are more beneficial for SEO compared to subdomains.

Export Help Articles

It would be preferrable if we had the capability to export our help section content to maintain our own backup of this content.

More customization of tables in Help Articles

In intercom I can set the background of the actual cell and not just the text. Each cell is able to be a different background color. I would also like to see the ability to merge cells. Row 1, 3 columns. The 2nd two columns would be merged together, etc I would also like the ability to modify borders. When I copy & paste a table from intercom it comes over without borders. It would be nice to capture that.

[API] Article mentions via referencing the articles' ID

It would simplify creation or modification of Help Center Articles via API, if the mentioned links can be inserted via just referencing the Article ID - instead of the full URL. Also documentation of the article format that includes working link mentions - imported via API would also make things more straightforward.

Improve drag and drop for Help articles

Right now it’s very easy to mistakenly reorder items or drag a folder into another. I ended up dragging a folder into another when picking an icon and I was not sure what happened. CMD+Z didn’t work to undo my action. Also, scrolling this list on mobile is impossible, as dragging the list to scroll will actually start the drag-and-drop behaviour and you end up ruining your layout. I’d love to see a “Drag handle / indicator” on these items so we can be more explicit with our intent to reorder. This would also make it possible to scroll this view on mobile without unintentionally reordering items or dragging them into folders.

Manage article access and unpublishing through API and MCP

Control Help Center article visibility and audience access through the API and MCP, and unpublish live articles without deleting them. This would let teams manage access and take outdated content offline from their own tools or AI workflows.

Disabling the Help Center should also stop article suggestions and public access

Today, "disabling" the Help Center only removes the module from the portal menu (Settings → Branding → Portal menu → Delete). The content itself stays live, so after disabling it customers still see: Articles suggested during ticket and conversation creation. Articles reachable and indexable on the public Help Center URL. The expectation is that deactivating a module makes its content and all linked functionality inactive, in one action. Requested behaviour A single workspace-level switch that takes the Help Center fully offline: no article suggestions in the Messenger or ticket forms, no public article URLs, no search-engine indexing. Apply the same principle to the other modules, so turning one off never leaves a surface still serving its content. Make the current behaviour explicit in the interface, since the existing control is a navigation change rather than a content switch. Current workarounds are partial: the Messenger Help module and article search card can be turned off individually in Settings → Support → Messenger → Customization, and articles can be restricted to Team members one at a time, which removes them from suggestions and search indexing but cannot be applied in bulk. Raised by a customer evaluating Featurebase who deactivated the Help Center and found the articles still active.

More Help Center layouts / templates

Would be great to have more possible layouts for the help center.

API for searching in the Help Center

I would like an API endpoint to easily search the help center after relevant articles to my query. The endpoint should return best matching results so I can show them to my user.

Bug: Cannot save post/submission when adding a tag due to "enableAutoTagging" error

I cannot save a post (submission) when I try to add a tag. I receive the error: { "code": 400, "message": "\"enableAutoTagging\" is not allowed" }. The post saves successfully once I remove the tag. This is a bug where the UI is incorrectly including the 'enableAutoTagging' field in the API payload when a tag is selected, which is causing the API to reject the request.

Customize Help Center sidebar styling (expandable collections & text formatting)

Allow admins to fully customize the Help Center sidebar, including the ability to: Make sidebar collections expandable/collapsible for better navigation. Show nested collections breadcrumbs - similarly how the Featurebase Help Center looks like Adjust text styling (e.g., font, capitalization like sentence case instead of ALL CAPS). Collection Collection Subtitle Apply branding-specific typography for a more consistent look and feel.

Option to open Help Center navigation links in new tab

Users want the ability to configure Help Center navigation items to open their URLs in a new browser tab instead of replacing the current tab, as the current behavior is not user-friendly.

Previous/next article buttons + related articles at the bottom of articles

GDPR-compliant YouTube Embeds with Cookie Consent in Help Center

Users need the ability to embed YouTube videos in Help Center articles such that the video only loads and sets cookies after explicit user acceptance, ensuring GDPR compliance. This would involve a mechanism for conditional loading of the video content.

Redirect old help article links and 404 pages to the new custom domain landing page

When migrating our help center to Featurebase and setting up a custom domain, our old article links (e.g., organization.featurebase.app/help/article/slug) result in a 404 error. We need a way to automatically redirect these old URLs to their new counterparts on the Featurebase custom domain to avoid broken links and provide a seamless user experience.

Allow creating multiple help centers in Featurebase

Tabs on top of the help center (site sections)

Support for different “site sections” to organize documentation into different parts or group the documentation of multiple products into a single site

Add an option to draft & delete translated versions of articles

Currently, there’s no way to delete or draft a translation version of an article if needed.