Pages are OmniCon's standalone content type — landing pages, about pages, pricing pages, anything that isn't a dated article. They share the same channel and the same storage as articles, but they're edited with a block-based editor instead of a free-form HTML body.
What's in this section
- Creating a page — how to start a new page and save it.
- Page blocks — the seven block types (Hero, Text, Image + Text, Gallery, CTA, HTML, Spacer) and when to use each.
- Pages vs. articles — which one to pick for what you're building.
- Publishing pages and URLs — how pages are served, permalinks, and the publish window.
Key concepts in 30 seconds
- A page is an article with IsArticle = false. Same table, different UI.
- Instead of one HTML body, a page is a stack of blocks — each block is a small, typed piece (a hero, a text section, an image+text row, and so on).
- Blocks render top to bottom in the order you arrange them.
- Pages have a permalink, a culture, and a publish window, exactly like articles.
- Pages don't show up in the article listing. They're reachable by direct URL and from channel navigation.
When to reach for a page
- A marketing landing page with a hero image, a pitch, and a CTA.
- An About us or Contact page that doesn't fit the chronological article flow.
- A pricing page with image + text rows for each plan.
- A feature tour built out of image-text alternating blocks.
For chronological content — posts, news, help guides — use articles instead. Start with Creating a page if you want the step-by-step.