HelpKit uses a strict hierarchy for structuring your knowledge base. This makes navigation predictable and ensures a clean, easy-to-use layout for your customers.
The Two-Level Hierarchy
In HelpKit, your content is organized like this:
- Main Collection
- Sub-Collection(s)
- Articles
There is a maximum of two levels.
- A Main Collection is the top-level group (e.g. “Getting Started”).
- A Sub-Collection sits inside the main collection and groups related articles (e.g. “Account Setup”).
- Articles live inside sub-collections.
One-Level Option
If you don’t need sub-collections, you can also use the single-level setup for specific categories or your entire knowledge base menu depth:
- Main Collection
- Articles directly underneath
Can I Go Deeper?
No — HelpKit does not support sub-sub-collections (three or more levels).
This is by design:
- 🧭 Keeps navigation simple for your readers
- 🖥️ Matches how Notion databases and our render engine work
- 🧩 Covers 99% of real-world documentation structures
If you try to add another level inside a sub-collection, HelpKit unfortunately won’t parse it.
Can I use my own Notion template?
No. You don’t need to build your own Notion template from scratch: in fact, we strongly recommend starting from one of HelpKit’s predefined templates. Our renderer is optimized to work with this structure, so using them ensures everything displays correctly. You can easily duplicate one of our free Notion templates into your own workspace and then adjust it to fit your content and style.
Why We Chose This Structure
When building HelpKit, we researched how most companies organize their docs.
The two-level structure hit the sweet spot:
- Deep enough for organizing complex topics
- Simple enough to avoid endless nesting
This way, your help center stays clean and easy to maintain.
Powered by