Free WordPress plugin First release in preparation

Build WordPress content architecture outside the theme.

Veyra Custom Content Manager gives custom content structures a dedicated home in WordPress—so the content model can remain clearer, more portable and easier to maintain as the website evolves.

Follow the release Product support
Product Veyra Custom Content Manager
Platform WordPress
Initial access Free public release
Veyra Custom Content Manager WordPress admin
Content architecture Add structure
Projects Custom content structure Active
Project types Connected taxonomy Active
Editorial structure Managed in one place Clear
Theme-independent model Presentation remains separate Portable
The structural problem

Your content model should not disappear with a redesign.

Custom content often begins as a few lines in a theme, a code-snippet plugin or a collection of settings spread across several tools. That works—until the site changes.

When structure and presentation become tightly coupled, switching themes, maintaining client projects or understanding the system months later becomes harder than it needs to be.

Keep structure in a dedicated plugin layerContent architecture remains separate from the active theme and its visual templates.
Make the model visibleUse one focused area to understand which structures exist and how they belong together.
Prepare for changeBuild a cleaner base for future templates, editors, imports, APIs and product-specific workflows.
Core product scope

A focused manager for custom WordPress content structures.

The first release concentrates on the architecture itself. Final field names and detailed controls will be confirmed against the audited release package.

Custom content types

Create and manage the structures that represent distinct kinds of content inside WordPress.

Exact configuration fields to be verified before release.

Taxonomy structures

Organise content through reusable classification systems that belong to the content model rather than the theme.

Supported relationships to be confirmed from the final package.

Dedicated management UI

Review and manage the site’s custom architecture from a focused interface within WordPress administration.

Final screenshots will replace the illustrative preview.

Theme-independent foundation

Keep content registration in a plugin so themes can concentrate on presentation and templates.

Structural separation is the central product principle.

Clearer project handoff

Make it easier for another developer or future version of the project to understand the intended content model.

Useful for maintained sites, client work and internal products.

Developer-readable architecture

Use WordPress concepts directly instead of hiding the structure behind an unrelated proprietary platform.

Export, import and developer APIs are not claimed until verified.
A simple workflow

Define the model, then build the experience around it.

01 · Model

Identify the content

Decide which information deserves its own reusable content structure.

02 · Organise

Connect classifications

Use taxonomies where editors need meaningful ways to group or filter content.

03 · Present

Build the templates

Let the active theme or site-building layer decide how that content is displayed.

04 · Evolve

Change presentation safely

Redesign the website without making the content architecture depend on the old theme.

Where it fits

Useful whenever standard posts and pages are not enough.

Product and service catalogues

Separate structured listings from ordinary editorial content while keeping presentation flexible.

Teams, portfolios and directories

Represent repeatable entities with their own archive, single view and organisational logic.

Editorial and knowledge systems

Create dedicated structures for guides, documentation, resources, case studies or specialised publications.

Location and event content

Model content that needs dedicated attributes, categorisation and frontend templates beyond standard posts.

Separation of concerns

The structure stays. The presentation can change.

Veyra CCM is designed around a clear boundary between the content model and the layer that renders it.

The plugin manages the structural registration. WordPress stores the content. The theme, block templates or future application layer decide how visitors experience it.

Veyra CCM Registers and manages the custom content model.
WordPress data Content remains stored in the WordPress installation.
Theme or UI Templates and interfaces control presentation.
Licence Final package identifier will be verified from the release ZIP before publication.
Remote communication Any update checks, telemetry or Veyra service connections will be documented before release.
Data ownership Content remains part of the WordPress installation and its normal database and backup processes.
Commercial layer The first public release is free; future products or services will be described separately.
Release information

Everything needed before installation—without hidden assumptions.

The exact compatibility matrix and download channel will be completed from the audited release package.

Technical requirements

WordPress[[MINIMUM AND TESTED WORDPRESS VERSIONS]]
PHP[[MINIMUM AND TESTED PHP VERSIONS]]
Multisite[[SUPPORTED / NOT TESTED / LIMITATIONS]]
LanguageEnglish interface at initial launch; translation readiness to be verified.
Current version[[PUBLIC RELEASE VERSION]]
Download[[WORDPRESS.ORG OR OFFICIAL DOWNLOAD URL]]

Installation path

Install the official packageUse the final WordPress.org listing or the download route published by Veyra.
Activate Veyra CCMActivate it from the WordPress Plugins screen using an administrator account.
Open the managerUse the dedicated Veyra CCM administration route to review or create structures.
Build presentation separatelyCreate the templates, blocks or application views that render the registered content.
Common questions

What to know before the first release.

Is Veyra CCM a page builder?

No. Its purpose is the custom content architecture. The theme, block editor, templates or another presentation layer remain responsible for layout and frontend design.

Does it replace WordPress posts and pages?

No. Standard content can continue using posts and pages. Veyra CCM is intended for projects that need additional, clearly defined structures.

Will changing themes remove the custom content model?

The central product principle is to keep registration in the plugin layer rather than the theme. The final release will be tested around that separation.

Is the first version free?

Yes. The initial public release is planned as a free WordPress plugin. Any future commercial products, services or add-ons will be presented separately.

Does the plugin send data to Veyra?

The final release documentation and Privacy Policy will state exactly which remote requests, if any, are made by the distributed package.

Where will documentation be published?

The product landing contains the essential launch information. A dedicated documentation system will grow after the public MVP is online.

Where can I report a bug or request a feature?

Use the dedicated Bug Report and Feature Request routes available from the Veyra Support hub.

When will the plugin be downloadable?

The download route will be added after the release audit, packaging, screenshots and distribution information are complete.

First public release

Veyra CCM is being prepared as the first free product in the ecosystem.

Follow the roadmap for release progress or use Support to report questions connected with the plugin and its public launch.

View release progress Open Support