Posts & Pages

Different kinds of content deserve different ways to organize them.

An article announcing a new release and a permanent page explaining the product may use the same editor, but they serve different purposes. One belongs to a stream of publications. The other belongs to the structure of the website.

VerdinCore treats Posts and Pages as distinct content types, each with the controls its job requires. They share a consistent writing and publishing environment without forcing every piece of content into the same organizational model.

Choose the right home for your content

	Posts	Pages
Best suited to	Articles, news, commentary, announcements, and recurring publications	Product information, About pages, documentation, policies, and other lasting content
How they are organized	Individual publications, optionally connected through topics	Parent–child relationships and a defined page order
URL structure	An individual post address derived from its title	A page address that can reflect its place in a hierarchy
Editorial controls	Publication status, featured or unlisted placement, and other post-specific options	Publication status, parent selection, ordering, and page-specific options
How readers find them	Through the site's configured publishing and discovery features	Through direct links, page navigation, and hierarchical context

This separation is useful precisely because it is ordinary. A new article should not require you to reorganize the website. A permanent reference page should not have to behave like the latest news item.

One familiar editing experience

Whether you create a Post or a Page, the essentials stay in the same place: title, excerpt, content, featured image, publication status, and access settings. The central writing area uses VerdinCore's visual editor, while contextual panels keep the additional decisions within reach.

The editor supports more than plain paragraphs. Headings, images, code, tables, links, and embedded content let an article or page take the shape its subject needs. You can work on the content first and make publication decisions without switching to a separate tool.

The surrounding controls change according to the content type. A Post can have a topic selector; a Page has a parent-page selector and ordering controls. That is intentional: related tasks share an interface, but unrelated choices do not need to appear everywhere.

((Screenshot from VerdinCore Admin > Edit Post: open an existing draft with a realistic title, short excerpt, and several formatted paragraphs; show the central editor, Status panel on the left, and Featured Image / Topics panels on the right. Capture at approximately 1920 × 1080, hide private content and account details. Suggested caption: "A consistent editing workspace, with controls specific to the content being created."))

For a closer look at formatting, media insertion, and the editing toolbar, see The Visual Editor.

Posts: content that moves with the conversation

Posts are built for material published over time. They carry their own title, excerpt, body, author, publication information, and optional featured image. VerdinCore generates the Post slug from the title, giving each publication a distinct address.

When the relevant site features are enabled, Posts can be assigned to Topics, connecting individual articles to broader subjects. A publisher can also mark a Post as featured or unlisted, or flag it for review. These are deliberately different controls:

Featured identifies content for featured placement, subject to the site's configuration.
Unlisted limits normal discovery and listing exposure; it does not make a directly accessible Post private.
Pending Review marks content for editorial attention. It is a marker, not a promise of a multi-stage approval workflow.

Together, these options support practical editorial judgment without requiring an elaborate workflow for every article.

Consider a product update. Publish the announcement as a Post, associate it with the relevant Topic if topics are enabled, and let the site's configured content views help readers discover it. Later updates can be published as new Posts without changing the permanent product information.

((Screenshot from VerdinCore Admin > Dashboard > Posts: show a populated list with several realistic Posts and different status badges; include the Status, Flag, and Sort Order controls above the table. Avoid identifiable user or visitor data; approximately 1600 × 900. Suggested caption: "Posts remain manageable as the publication archive grows."))

Pages: content that gives a website its shape

Pages serve a different purpose. They are well suited to material visitors need to find again: company information, product explanations, policies, documentation, and section landing pages.

A Page can be placed beneath another Page and assigned an order. VerdinCore uses that relationship to construct nested page paths and provide the context needed for navigation and breadcrumbs.

For example, a product website might organize its lasting information like this:

Product
├── Features
│   └── Media Management
└── Architecture

That is not merely a visual grouping in the administration area. The hierarchy gives the website a meaningful information structure and can be reflected in its published URLs and navigation, depending on the site's presentation.

The Page editor also checks parent assignments to prevent circular hierarchies. In other words, you can organize content around how readers understand it, without manually constructing every relationship between pages.

((Screenshot from VerdinCore Admin > Edit Page: open a demonstration page named "Media Management" with "Features" selected in the Parent Page control; keep Page Order visible in the left panel, Parent Page visible in the right panel, and the title/content in the center. Capture at approximately 1920 × 1080. Suggested caption: "Parent and order controls give lasting content a clear place in the site structure."))

The complete behavior of nested pages, ordering, and breadcrumbs is covered in Page Hierarchy.

Control the lifecycle, not just the text

Both Posts and Pages support Draft, Published, Scheduled, and Archived states. They can also be moved to Trash and restored when necessary. This lets content move through its useful life without treating every save as a public release.

Scheduling is supported through VerdinCore's configured maintenance process, rather than an independent real-time publishing service. Access settings can also distinguish public content from content intended for signed-in members, where that experience is enabled and configured.

These controls matter because publishing does not end at the Save button. Sometimes content is still being prepared. Sometimes it belongs on the site later. Sometimes it needs to be retired without immediately being destroyed.

For exact status behavior, scheduling prerequisites, and visibility choices, see Publishing Workflows and Visibility & Access.

A simple distinction that scales

Imagine maintaining a growing technology publication alongside a product website. Your articles, release announcements, and commentary evolve continuously. Your About, Product, Architecture, and Support pages form a more stable structure. Both need capable editing. They do not need identical organization.

VerdinCore keeps those responsibilities separate while preserving a coherent workflow for the person doing the work.

Write a Post when the publication is the event. Create a Page when the information needs a lasting place.

That distinction helps a small site stay clear from the beginning, and gives an established site a structure it can continue to build on.

Continue exploring: The Visual Editor · Images & Media · Publishing Workflows