Today marks a defining milestone for the Ikabud ecosystem.
After months of engineering, testing, and refining the architecture, we are proud to announce the public release of DiSyL (Declarative Ikabud Syntax Language) together with Phoenix, the first cross-CMS theme powered by the Ikabud Kernel.
This release sets the foundation for a new way of building, designing, and delivering themes — one where a single template folder can run natively on multiple CMS platforms, without rewriting logic or layouts.
🔥 What’s New in This Release
1. DiSyL v0.6.0 Beta — A Declarative Layout Language
DiSyL introduces a modern, component-first templating paradigm:
- Familiar, human-readable syntax
- Logic blocks (, ) with scoped variables
- Expression pipelines (
| upper,| esc_html, etc.) - Strict EBNF grammar definition
- Multi-CMS safety through predictable behavior
- Automatic escaping & filter engine
- Support for includes, components, and nested structures
- Clean separation of view templates from CMS internals
DiSyL is intentionally minimal, predictable, and portable — making it the first templating language created with multi-CMS consistency as a primary goal.
🔥 Phoenix Theme — One Theme, Three CMS
Phoenix demonstrates DiSyL’s capabilities by running the same /disyl/ templates across:
- WordPress
- Joomla
- Drupal
No forks.
No CMS-specific rewrites.
Just one templating folder that renders everywhere.
Phoenix includes:
- Responsive layout system
- Typography components
- Sections & containers
- WP/Joomla/Drupal-native menu handlers
- Widgets + sidebars powered by DiSyL
- Post/archive templates
- Component-based includes
- Full integration with the Ikabud Kernel renderer
Phoenix is not just a theme — it’s proof that cross-CMS theming is finally possible.
⚙️ Backed by the Ikabud Kernel
The Ikabud Kernel sits underneath Phoenix and DiSyL, providing:
- A universal rendering engine
- A unified component resolver
- CMS runtime adapters
- Hooks for filters, sanitization, and security
- A clean separation between CMS logic and view logic
- The beginnings of multi-core, multi-instance architecture
This release establishes Ikabud as a stable, developer-ready foundation.
🌍 Demo Sites Now Live
To showcase the full cross-CMS experience, Phoenix is deployed on all three platforms:
- WordPress Demo
- Joomla Demo
- Drupal Demo
Each demo uses the same theme, same components, and same DiSyL templates, proving the central promise of Ikabud:
Write once, run anywhere.
Content will be synchronized from the main Ikabud Kernel website so that all demos reflect the same real-world usage.
📦 MIT-Licensed — Fully Open Source
The entire stack is available under the MIT License:
- Ikabud Kernel
- Phoenix Theme
- DiSyL Grammar
- CLI Tools
- Adapters & utilities
This ensures maximum freedom for developers, integrators, educators, and enterprise adoption.
GitHub: https://github.com/aKira041795/Ikabud-CMS-Kernel
📘 Documentation Now Live
Full documentation is available in the GitHub repository, including:
- DiSyL grammar (EBNF v0.2)
- Quickstart for all three CMS
- Phoenix component reference
- CLI usage
- Best practices for cross-CMS runtime adapters
- Theme structure overview
Each demo site will include documentation excerpts and examples, keeping the experience consistent across platforms.
🚧 What’s Next for Ikabud
With the kernel and Phoenix released, we now shift focus to:
- DiSyL syntax highlighting (VSCode plugin)
- The first Ikabud CMS (file-based)
- Visual Layout Builder (drag & drop DiSyL editor)
- A component marketplace
- Phoenix Pro with extended UI kits
- More adapters (Laravel CMS, SSG adapters)
- Multi-instance kernel capabilities
This is the beginning of a broader ecosystem.
🎉 A New Path Forward
Today’s launch solidifies Ikabud as:
- A new way to think about CMS architecture
- A bridge between previously incompatible systems
- A modern alternative to template overrides
- A platform that empowers developers to write once and deploy anywhere
DiSyL + Phoenix represent the first real-world demonstration of the kernel’s design philosophy — and a strong foundation for what comes next.
Welcome to the new era of cross-CMS theming.
