Everything on your published site is derived from a single Notion page tree. Once you understand how that tree maps to the site, every other how-to in this section becomes obvious.
The Two-Level Hierarchy
Your connected root page is the anchor. Below it, Emovart reads up to two levels of grouping:
- Collections — the pages directly under the root. They become the category cards in the Help Center layout and the top tabs in the Documentation layout.
- Sub collections — the pages inside a collection. They become the group headers that organize articles, including the sidebar groups in the Documentation layout.
- Articles — the pages inside a sub collection. This is where your actual content lives.
Page order in Notion is the order visitors see, and every page's icon travels with it. Rename, reorder, or move a page in Notion, and the site follows on the next sync.
One-Level Option
Sub collections are optional. Drop article pages directly under a collection and they render as a flat list — handy for FAQs and small categories. 📂 Creating a Single-Level Category walks through it.
Can I Go Deeper?
No — two levels of grouping is the maximum. Pages nested below an article don't create another navigation layer. If an article keeps growing, split it into several articles inside the same sub collection instead: shorter pages are easier to search, easier to link to, and easier to keep up to date.
Can I use my own Notion template?
Absolutely. Emovart doesn't require a special template — any page tree works as long as it follows the shape above. Connect your existing page with Browse my Notion pages (or paste its link) in Settings → Help Centers, then drag pages around until the tree reads root → collections → sub collections → articles.
Why We Chose This Structure
Deep trees feel powerful for writers and miserable for readers: content ends up buried four clicks down, and nobody remembers where anything lives. With two levels, every article sits at most two clicks from your homepage, the sidebar stays scannable, and search results map onto categories people actually recognize. It's the structure well-run knowledge bases tend to converge on — we simply made it the default.