The Emovart starter template is more than a pretty starting point — its page hierarchy is exactly what Emovart reads when it syncs your site. The root page holds your collections, each collection may hold optional sub collections, and your articles live inside those as regular Notion pages.
Whether you build on the template or bring your own page, keep these rules in mind:
- Keep the hierarchy intact: root page → collections → optional sub collections → articles.
- Don't nest pages any deeper than that — pages buried below the article level won't be imported.
- Keep every page accessible to the Emovart connection. A page moved outside the shared root disappears from your site on the next sync.
- Renaming pages is fine, but article URLs come from page titles, so existing links to a renamed article will change.
⚠️
Please don't restructure the top levels of the tree. Turning collections into plain text blocks, toggles, or database views — or dragging articles up next to your collections — means Emovart can no longer tell what's a category and what's an article, and those pages will be skipped.
Trouble syncing your knowledge base?
If a page isn't showing up the way you expect, start with Syncing your knowledge base and Common issues when syncing your knowledge base. Still puzzled? Press the Contact button and we'll take a look together.