Benutzerdokumentation Entwicklerdokumentation | |

Pages

Static CMS pages for content that lives outside the blog — About, Contact, Privacy Policy, and similar standalone documents.

Small change. Update URL references from yoursite.com/page-slug to yoursite.com/pages/page-slug. If there are examples showing page URLs, update them all to include the /pages/ prefix.

TL;DR

  • Admin → Pages — create, edit, and delete static pages.
  • Pages use the same dual editor as posts (Markdown or HTML).
  • Published pages are accessible at yourdomain.com/page-slug.
  • Rendered via the theme's page.tpl template.

Details

Pages vs. Posts

Pages and posts share the same dual editor and many of the same fields, but they serve different purposes:

  • Posts are time-ordered blog entries sorted by publish date and displayed in the blog archive.
  • Pages are standalone documents with no publish date. They appear at a fixed URL and are not included in the blog index or RSS feed.

Typical uses for pages: About, Contact, Privacy Policy, Terms of Service, a landing page for a specific topic.

Page Fields

The page editor includes:

  • Title — required. Auto-generates the slug.
  • Slug — the URL path for the page (e.g., about → yourdomain.com/about). Must be unique.
  • Content — same dual Markdown/HTML editor as posts.
  • Content Type — saved per page (markdown/html).
  • Status — Draft or Published. Draft pages are not publicly accessible.
  • Parent Page — select a parent page to create a nested URL structure. Example: a child page with slug team under a parent page with slug about is accessible at yourdomain.com/about/team.
  • Sort Order — a numeric value used to control ordering in navigation menus or page lists.
  • Meta Title and Meta Description — SEO fields, same as posts.

Page Hierarchy

Pages support one level of parent/child nesting. Select a parent from the Parent Page dropdown to nest a page under another. The full URL is constructed from the parent slug + child slug. Deeper nesting (grandchild pages) is not supported.

Setting a Page as the Front Page

To use a static page as the site home page:

  1. Create and publish the page.
  2. Go to Admin → Settings → General.
  3. Set Front Page Type to Page.
  4. Select the page from the Front Page dropdown.

The selected page will render at / instead of the blog index.

Page Template

Pages are rendered by the active theme's page.tpl template. Theme authors can customise the layout of page content independently from blog posts.