WordPress runs anywhere. Why doesn't your knowledge base?
Meet #Cortext (alpha): an OSS KB in #WordPress, built with my colleague Miguel Fonseca for #RadicalSpeedMonth. Pages, collections, blocks. Self-host, SaaS, or locally in Playground.
What would actually make you switch?
As promised: the #Cortext beta is live.
A #WordPress-powered knowledge base you can poke around with in Playground right now, while we finish the Plugin Directory listing and desktop app:
https://t.co/uwSApA0yOF
Building #cortext, your WordPress-powered knowledge
base, in the open; the path to Beta is now ready.
If you want to see what's planned (or pitch in),
it's all here:
https://t.co/w6L4y6AbNi
@nickmdiego Fair point, ownership alone isn't the pitch. But as a current KB SaaS user who's tried OSS alternatives, "I wish I could self-host or move this elsewhere later" keeps coming back as a thought. Mostly for futureproofing. Niche, but real.
WordPress runs anywhere. Why doesn't your knowledge base?
Meet #Cortext (alpha): an OSS KB in #WordPress, built with my colleague Miguel Fonseca for #RadicalSpeedMonth. Pages, collections, blocks. Self-host, SaaS, or locally in Playground.
What would actually make you switch?
@nickmdiego Thanks! Not just WP users either: it'll also ship as
a standalone desktop app. No WordPress branding, no
"back to WP" button. Just the workspace.
@nickmdiego Thanks, fair question. The goal: lean into what WordPress already does well.
- Mature publishing (themes, blocks, REST)
- Runs anywhere WP runs
- Inherits every WP upgrade for free
- Open source and extensible
Your data, your rules! 🔓
The power of @WordPress is its ability to run anywhere. 🌍
This is a great example of how the block editor can be reimagined for seamless knowledge management.
Excited to see where this alpha goes!
What if you didn't have to pick a theme for your site, what if you didn't have to create assets, what if you didn't have to fumble with a logo....
What if AI just created your @WordPress site for you?
Well, now it does. And it manages it too.
Oh, and for free ⬇️
i cloned my voice with @play_ht to create an ai voice support agent for my WordPress theme, Kanso.
what started as a simple way to add audio to my blog posts became something much more interesting.
making it work was surprisingly straightforward—only needed 23 seconds of my voice to create a convincing clone. wild.
i compiled faqs from the launch post, support emails, slack DMs, etc, into a structured JSON file as custom instructions. then i made a @WordPress block to render it with the PlayAI Web SDK (didn't like the provided embed's ui/ux).
fine-tuning was a bit surreal—hearing an uncanny version of my voice explaining my ideas back to me. strange and intriguing at the same time.
maybe this is what support will look like: your voice, your knowledge, any time.
@jeffikus@mikemcalister@jeffr0@mikachan_ I don't want to overpromise, but responsive design tools are as close as they have ever been. Stay tuned for upcoming roadmaps :)
@mattbeck@JavierCasares@richtabor The thing is, WP releases are LTS by default, even more from a security perspective: with every major release, backporting security patches becomes more difficult and time-consuming.
The non-LTS channel is actually the Gutenberg plugin.
Excited to see most #WCUS Showcase Day presentations focused on Gutenberg! However, the Editor/Gutenberg table at Contributor Day was mostly empty. 😔
What's your number one deal-breaker in contributing to Gutenberg?