Prerequisites

A "prerequisite" means that one article shouldn't be read in isolation, because to understand it you need the context from another article.

For example: if you have separate articles "How to return a product" and "Returns policy", the first is usually written briefly and assumes the customer knows the general rules. By marking "Returns policy" as a prerequisite, you make the bot always reach for both articles together.

Limit

A single article can have up to 5 prerequisites. The limit is deliberate. Chains of eight or ten articles usually mean the content is too fragmented and worth consolidating.

How to set it up

1. Open the article that should have prerequisites.
2. In the panel on the right, find the Prerequisites section.
3. Start typing the title of an existing article, and Fibly will suggest matching entries.
4. Pick an article from the list. You can add up to five.
5. Save your changes.

No cycles

Fibly won't let you create a cycle. If article A requires B, then B can't require A (nor indirectly through C). An attempt to save will end with an error message.

When to use it

• when an article refers to a concept described separately ("free return", "Pro subscription", "delivery zones"),
• when a procedure has several stages split across separate articles (registration, verification, first login),
• when a topic has significant legal or policy context.

What not to mark

• don't mark an article as a prerequisite just because it's "related". Semantic search works across the base anyway.
• don't use prerequisites as tags or categories,
• don't link every article to one "main" article. That will slow down answer generation.

What's next

Once your knowledge base structure is in place, check the content quality. Fibly will automatically assess which articles need improvement.