Topics & Discovery

Topics & Discovery

Publishing creates information. Discovery helps that information find its audience.

A growing website presents an interesting problem. The more you publish, the more valuable your collection becomes, but the harder it can be for readers to find an older article that is still worth reading. A chronological list is excellent for showing what is new. It is less helpful when someone wants to explore a subject.

VerdinCore approaches this with a small set of complementary tools: Topics and Topic Groups for editorial organization, dedicated browsing pages, related articles, archives, and selected content sections such as Featured and Most Popular.

They do different jobs. Together, they help a website become a collection readers can explore rather than an ever-growing list of posts.

Give content a subject, not just a date

A Post can belong to more than one Topic. Each Topic has a name, an address-friendly slug, an optional description, and an assigned Topic Group. Groups provide a broader level of organization without requiring editors to build a complex taxonomy tree.

For example, a technology publication might use the following arrangement:

Software Development             ← Topic Group
├── PHP                         ← Topic
├── JavaScript                  ← Topic
└── Software Architecture       ← Topic

Infrastructure                   ← Topic Group
├── Linux                       ← Topic
└── Server Operations           ← Topic

An article about deploying a PHP application on Linux could be assigned to PHP, Linux, and Server Operations. Readers looking at any of those subjects can encounter the same article, without the publisher copying it into three separate sections.

This is deliberately different from Page Hierarchy. Pages establish where a permanent piece of information belongs. Topics express what an article is about. A Post can cover several subjects at once; a Page has one parent in the page hierarchy.

Manage the taxonomy without leaving the editorial workflow

The Topics administration screen brings topic management into one place. Editors with the appropriate permissions can see existing Topics, their Groups, descriptions and Post counts, then filter the list by Group or change its sort order.

Adding a Topic involves a name, a generated slug, an optional description and a Topic Group. Topic Groups are managed separately, so a publication can refine its editorial categories as its subject matter expands.

((Screenshot from VerdinCore Admin > Dashboard > Topics: populate three or four realistic Topic Groups and at least eight Topics; show the Topics table with Name, Group and Posts columns, the Topic Group filter, and the Add Topic / Add Topic Group controls. Capture approximately 1600 × 950 with readable labels. Hide account details and unpublished or private topic names. Suggested caption: "Organize subjects and editorial groups from a single Topics dashboard."))

The Post editor keeps assignment close to writing. The Select Topics control opens a grouped set of checkboxes, making it possible to classify an article across several subjects without switching to a separate administration screen.

((Screenshot from VerdinCore Admin > Edit Post: open a sample Post titled "Deploying PHP Applications on Linux"; expand the Select Topics popover in the sidebar, showing at least two Topic Groups and selected checkboxes for PHP, Linux and Server Operations. Keep the Post title visible for context. Capture around 1600 × 950; use sample content and hide account information. Suggested caption: "Assign several Topics directly while editing a Post."))

The practical advantage is consistency: a classification is made once, on the Post, and can then support multiple public-facing features.

Turn Topics into destinations

When topic browsing is enabled and presented by the site theme, each Topic can have its own public archive at an address such as:

/topic/php
/topic-group/software-development

A Topic page lists published Posts assigned to that subject. A Topic Group page brings together Posts assigned to Topics within the group. The group view does not need to show the same Post repeatedly just because it belongs to several Topics in that group.

Both views can present a heading and description, with Posts ordered by their publication date and divided into pages where necessary. This gives established subjects a place of their own instead of burying them deep in a chronological feed.

The supplied theme can also expose Topics and Topic Groups through its navigation, with Post counts for the subjects being listed. These counts are drawn from eligible published content rather than simply displaying every administrative assignment.

((Screenshot from a public VerdinCore site with Topics enabled: open the Topics navigation popover showing several Topics and Topic Groups with their Post counts. Include the site header and enough surrounding page context. Capture approximately 1440 × 850; show public sample content only. Suggested caption: "Topic navigation helps readers move from individual subjects to broader editorial groups."))

((Screenshot from a public VerdinCore Topic archive: open /topic/php or another populated sample Topic page; frame the Topic heading, description and at least three Post cards. Capture approximately 1440 × 900; use public sample content only. Suggested caption: "A dedicated Topic page turns a subject into a browsable collection of published Posts."))

Availability depends on site configuration and theme presentation. The taxonomy model and archive routes are implemented, but not every VerdinCore site has to expose every discovery surface.

Related Posts: relevance from editorial context

A reader who finishes an article may want to continue with a connected subject. VerdinCore's optional Related Posts section uses the Topics already assigned to Posts to make that connection.

The approach is straightforward:

1. Find other published Posts that share one or more Topics with the current Post.

2. Give priority to Posts sharing more of those Topics.

3. Use publication recency to help order Posts with comparable overlap.

4. If there are no matching Posts, fall back to a selection ordered by recent views.

This is not an AI recommendation engine, and it does not require an editor to maintain a hand-written list of related links beneath every article. It makes use of the editorial structure that already exists.

Imagine a reader opening a Post tagged PHP, Linux and Server Operations. An article tagged with all three subjects is a stronger topical match than one tagged only with Linux. That relationship can remain useful long after both Posts have disappeared from the front page.

((Screenshot from a published VerdinCore Post: scroll to the Related Posts section beneath an article that has at least three Topics; show the Related Posts heading, several genuine topic-overlap results and enough of the article footer to establish placement. Capture approximately 1440 × 800. Suggested caption: "Related Posts uses shared editorial Topics to help readers continue exploring."))

The section is configurable, including whether it is shown and how many results it requests. Its relevance depends on sensible Topic assignments; creating dozens of vague Topics does not automatically improve recommendations.

A useful taxonomy earns its place twice: first when editors organize content, and again when readers discover it.

Different ways to surface worthwhile content

Not every valuable Post is necessarily the newest, or the one with the closest Topic match. VerdinCore includes several distinct ways for a theme to bring Posts back into view.

A website can use these sections selectively rather than placing all of them on every page. Discovery is as much about presentation choices as it is about available data. A well-chosen related section can help more than another crowded sidebar.

Featured content: editorial choice or optional automation

Posts have a Featured flag, allowing a site to give certain articles greater visibility where its theme provides a Featured section.

VerdinCore also supports an optional automatic featuring process. When enabled and run through scheduled maintenance, it evaluates eligible Posts using signals such as readership, activity over time, recency and content depth. Configuration controls how selectively Posts are featured.

This is a deterministic, rule-based process, not AI curation. It is also not a substitute for editorial judgment: whether to use manual selection or the automated mechanism is a product configuration decision.

A publisher might prefer hand-picked Featured Posts for a tightly curated product website, or automatic selection for a publication with a substantial stream of articles. Neither approach has to be universal.

Archives and search: another route into older work

The optional Archive provides a separate entry point for older Posts. Readers can narrow the collection by calendar year and month, or submit a keyword query that searches Post titles, excerpts and content.

This search is intentionally lightweight. It is a database-backed search within the Post archive, not a dedicated full-text engine, semantic search system or site-wide search across every content type.

For a publication with a growing back catalogue, that can be enough to answer practical questions: What did the site publish around that period? or Where was that article about Linux?

Discovery should respect publishing decisions

A useful discovery system must not casually treat every saved Post as public content. Normal topic and archive listings operate on published material and apply audience visibility rules. Unlisted Posts are excluded from standard Post discovery queries, while remaining accessible by direct URL where access rules permit.

Unlisted is not a privacy mechanism. Likewise, a Post marked Featured does not override its publication status or make it appropriate for every audience. These distinctions matter when configuring a public website, particularly one that offers member-oriented content.

See Visibility & Access for the full editorial distinction between status, access level and discoverability.

Build a body of work people can actually explore

The value of Topics grows with the content library. A small publication can begin with a handful of well-defined subjects. As it develops, those subjects provide multiple ways into the same body of work: topic pages, group pages, related reading and meaningful navigation.

VerdinCore does not require an elaborate recommendation platform to make that possible. It uses clear editorial relationships, supported by optional ways to surface content according to context, recency and readership.

The result is more than a chronological stream. It is a publication that remains navigable as its library grows.

Continue exploring: Posts & Pages · Page Hierarchy · Visibility & Access · SEO & Distribution