> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tied.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQs

> Question-and-answer sets, and how they differ from articles.

There's a FAQs entry in the Help Center sidebar, sitting next to Articles and Categories — those three are
the sidebar's only children. Locales isn't one of them — it's reached from portal settings, not the
sidebar. See [Locales and translations](/help-center/locales). It's worth being direct about what's
actually behind the FAQs entry right now.

<Warning>
  **FAQs are not a separate content type today.** There's no FAQ model, no dedicated create-or-edit flow, and no way to publish one. Opening the FAQs page shows an empty state — "Frequently asked questions for this portal will appear here" — and nothing populates it. It isn't a filtered view over your articles either; it's a placeholder for a feature that hasn't shipped.
</Warning>

That's a direct correction, not a hedge: if you came looking for a lighter-weight alternative to writing full articles, it doesn't exist yet as its own thing.

## What actually gets you the same result

Nothing stops you from writing FAQ-style content as ordinary [articles](/help-center/articles) today. A short, question-phrased title. A one- or two-paragraph answer. Grouped under a category — "FAQ" or "Quick answers" works fine as a category name if you want the grouping to be explicit.

That gets you everything a dedicated FAQ feature would usually add on top of an article:

| What you might expect from "FAQs" | What an article already does |
| - | - |
| Short question-and-answer format | No length minimum — a two-line article is a valid article |
| Grouped by topic | Categories, same as any other article |
| Searchable | Full-text search across title, description and content |
| Answerable by your AI agent | Any published article is agent knowledge automatically |

There's no gap in outcome, only in the label. A published, well-categorized article that happens to be short and phrased as a question *is* an FAQ, as far as your customers and your agent are concerned.

## Planning around this

If you're structuring a Help Center today, don't hold content back waiting for a dedicated FAQ feature to appear. Write it as an article, category it clearly, and publish it. If a distinct FAQ feature ships later, well-written short articles are exactly the content that would migrate into it cleanly — the reverse isn't true of content you delayed writing.

## Next

<CardGroup cols={2}>
  <Card title="Writing and publishing articles" icon="file-pen" href="/help-center/articles">
    The real mechanism behind question-and-answer content today.
  </Card>

  <Card title="Categories and structure" icon="folder-tree" href="/help-center/categories">
    Grouping short answers under a clear topic.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.