When to use Pages versus Content types.
Pages
Pages (Admin → Pages) are ideal for fixed site structure:
- About, Contact, legal text, landing pages
- Block builder layouts with hero, FAQ, pricing sections
- Optional SEO fields per page
- URLs at
/p/{slug}(or homepage when designated)
Content types
Content types suit repeating models:
- Blog posts, products, guides, team members, documentation articles
- Custom fields per type (price, excerpt, entry references, …)
- Archive URL at
/{typeSlug}when public route is enabled - Single entry at
/{typeSlug}/{entrySlug}
Comparison
| Need | Use |
|---|---|
| One About page | Page |
| 50 blog posts with categories | Content type (Blog) |
| Product catalog with cart | Content type (Product) + Commerce |
| Marketing homepage with blocks | Page or theme home.twig |
Choosing
If you need many similar items with custom fields, taxonomies, and listings, use a content type. If you need one-off layouts with the block builder, use a page.
Can I convert later?
There is no automatic page-to-entry conversion. Plan structure early, or create a content type and manually recreate high-value pages as entries if you later need archives or APIs.