REST API
Versioned Core, product, license and distribution endpoints for integrations and tooling.
Open reference →Nakreos DevelopersBuild on the platform,
Build on the platform,
not around it.
Create themes, plugins, Builder elements and integrations against stable Nakreos APIs, then distribute them through the same Hub that powers licensing and updates.
plugin.phpCore 1.9.27
add_action('nakreos_init', function () {
register_my_extension();
});
Product Slug: my-extension
Requires Nakreos: 1.9.27License: Hub DynamicTheme APIPlugin APIRESTHub
Theme Platform
Keep presentation independent from Core with theme headers, lifecycle hooks and Builder locations.
Theme guide →Plugin Platform
Add capabilities through hooks, filters and package contracts without modifying the CMS Core.
Plugin guide →Visual Builder SDK
Register elements, dynamic data and theme locations while keeping the document model portable.
Builder SDK →Extension architecture
A clean boundary for every layer.
Core owns the runtime. Themes own presentation. Plugins own capabilities. Hub owns distribution, licensing and release metadata.
DEVELOPER PATHS
Choose where to start.
Each guide follows the current Nakreos package and Hub contracts.
BUILD, TEST, PUBLISH
A product path designed for independent releases.
Keep development local, validate package metadata, publish a version in Hub and let compatible CMS installations discover it.
Develop locally
Use documented hooks, filters, content APIs and theme locations.
Package consistently
Product slug, version and requirements stay in predictable package metadata.
Distribute from Hub
Publish releases once and use the same catalog identity for updates, trials and licenses.
PACKAGE CONTRACT
Predictable packages are easier to build and distribute.
Use a stable product slug, explicit version requirements and the existing Nakreos APIs instead of coupling a product to one installation.
Product identity
Slug and version metadata connect Hub catalog, licensing and updater behavior.
Extension APIs
Use hooks, filters, content types, settings and theme locations instead of editing Core files.
Release discipline
Publish immutable ZIP packages and let Hub own distribution metadata and integrity hashes.