Books are OmniCon's long-form content type. Where articles are one chunk of HTML and pages are a stack of blocks, a book is a full hierarchy — Parts, Chapters, and Sections — with its own editor, its own AI-assisted drafting flow, and a Word export for when you need to ship a document.
What's in this section
- Creating a book — starting a new book and adding the first Part, Chapter, and Section.
- Book structure — how Parts, Chapters, and Sections nest, and how to reorder them.
- AI-assisted drafting — using the AI generate button at Part, Chapter, and Section level.
- Exporting to Word — how the export works and what it includes.
Key concepts in 30 seconds
- A book has four levels: Book → Part → Chapter → Section.
- Each level can hold content. Sections are where most of the writing happens.
- Every level has an OrderIndex that you change by dragging — that controls reading order.
- Books have an AI reference data field at each level, which the AI uses as context when drafting.
- Books are stored in SQL (not Azure Table Storage like articles) because the nested structure makes relational queries easier.
- A book belongs to exactly one channel.
When to reach for a book
- A multi-chapter guide, manual, handbook, or whitepaper.
- A long-form piece that needs a table of contents.
- Content you want to draft with AI assistance and then export to Word for review or distribution.
- Any document where "one HTML body" (an article) would be too big and "a stack of marketing blocks" (a page) is the wrong shape.
When not to use a book
- A single post → use an article.
- A landing page → use a page.
- A short two-page doc → still probably an article. Reach for a book when the structure actually earns its keep.
Start with Creating a book for the step-by-step, or jump to Book structure if you want to understand the hierarchy first.