My Ikabud Journey (So Far)
If someone told me a year ago that I’d end up building:
- a CMS kernel,
- a cross-platform theme engine,
- a visual builder,
- my own declarative syntax,
- and multiple demo sites…
…I probably would have laughed, cried, or pretended the WiFi connection dropped.
Yet here we are.
Ikabud exists.
DiSyL exists.
Phoenix Theme runs across WordPress, Joomla, and Drupal like it’s the United Nations of themes.
Everything even has documentation — proof that miracles happen.
And the funny part?
This all started because I just wanted a simpler way to build websites.
Where All This Started (A.K.A. The “There Has to Be an Easier Way” Moment)
I’ve set up so many websites over the years that I’ve memorized half of the WordPress admin panel.
I’ve also broken enough websites to qualify for a “professional oops” award.
Every project felt the same:
- install CMS
- configure theme
- add plugins
- fight plugins
- patch plugins
- drink coffee
- Google cryptic errors
- drink more coffee
- eventually deliver something that works
- immediately forget what you did
At some point I thought:
“What if I create something that keeps the good parts of CMSes but removes 90% of the repetitive pain?”
Like any normal person, I responded to this question by building an entire kernel, a mini-language, a template engine, and a rendering pipeline.
Totally a reasonable weekend project.
(Except it took months. And some existential spirals.)
The Birth of DiSyL — a Language Nobody Asked For but I Needed
DiSyL started as:
“What if themes were just declarations?”
Turns out:
If you squint hard enough,
drink enough coffee,
and ignore the voice saying “but nobody else does this”,
you can actually design a mini-language.
It’s not meant to replace PHP or JS or Python or whatever flavor-of-the-week tech people are hyping.
DiSyL is simply:
- Structured
- Human-friendly
- Predictable
- CMS-agnostic
…basically everything theme systems aren’t.
Enter Ikabud — The CMS Kernel That Refuses to Be Normal
Ikabud isn’t a CMS.
It’s a CMS OS — a foundation, a core, a skeleton, a toolkit, a whatever-you-want-to-call-it that powers multiple CMSes from one source.
I wanted a system where:
You don’t reinvent the wheel per CMS.
You don’t rewrite the theme five times.
You don’t maintain plugins per ecosystem.
You can control everything with manifests and renderers.
“Migration” doesn’t feel like dental surgery.
Ikabud is my solution to a decade-long annoyance.
Even if it gains zero traction, I would still use it for my future projects.
And honestly, that’s the first sign a tool is worthwhile.
The Funny Part: The Internet Has Not Exploded (Yet)
- I launched the kernel.
- Released Phoenix theme.
- Pushed all docs to GitHub.
- Set up the official site.
- Built demo subdomains.
- Solved CORS issues that made me question reality.
- Added CSRF, 2FA, hardened configs, reset links — you name it.
And after all that…
The internet shrugged.
But here’s the secret: that’s normal.
Every tool spends time in the quiet phase.
This has nothing to do with quality.
It’s just the ecosystem learning you exist.
Laravel, Vue, Astro, Svelte — all started slow.
What matters is that Ikabud already works, it’s stable, and I’ve proven (to myself most importantly) that the concept is sound.
What Makes This Worthwhile
1. I solved my own problem
I can spin up future projects faster and with consistency.
2. I built something that reduces headaches
Fewer theme rewrites.
Fewer CMS-specific quirks.
More predictability.
3. I learned a ridiculous amount
From CORS nightmares to writing DSL syntax — this journey was basically a crash course in full-stack everything.
4. It’s a foundation for bigger ideas
Now that the kernel exists, I can build:
- plugins
- more themes
- integrations
- headless bridges
- visual builders
Ikabud opens doors that didn’t exist before.
5. Nobody can take this away
Traction or no traction, this creation is real, functional, and mine.
What’s Next? (After a Break, Obviously)
Right now, I’m taking a breather.
I’ve shipped:
- Security features
- Core functions
- Templates
- Documentation
- Demo sites
The next steps can wait.
When I come back—refreshed, hydrated, and hopefully sane—I’ll think about:
Tutorials
Walkthroughs
YouTube demos
A Phoenix 2.0 theme
Developer onboarding
Maybe even packaging Ikabud as a SaaS toolkit someday
But for now?
I’m resting.
Final Thought
If you ever feel like building your own CMS kernel is insane… it probably is.
But sometimes, solving your own problems leads to tools you never knew you needed — and maybe one day, others will need them too.
Ikabud may not be famous (yet), but it’s useful, it’s functional, and it’s growing.
And that’s enough reason to keep going.
After the break, of course.
Ikabud Kernel/CMS OS, DiSyL, Phoenix theme is built using Windsurf + REACT + VITE
Check me/Ikabud at Github
Post created with ChatGPT =)
