Héctor Prieto

WordPress Core Contributor @Automattic

[Héctor Prieto @priethor]

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?

[Héctor Prieto @priethor]

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

[Héctor Prieto @priethor]

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

[Héctor Prieto @priethor]

@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.

[Héctor Prieto @priethor]

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?

[Héctor Prieto @priethor]

@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.

[Héctor Prieto @priethor]

@Gtarafdarr That's the goal: best of both worlds. Workspace UX,
WP stack. Pages and typed collections with multiple
views.

[Héctor Prieto @priethor]

@richtabor WordPress in a trench coat, and a surprisingly fitting
one. Underneath: just CPTs, blocks, REST. All the pieces
were already there. 🧱

[Héctor Prieto @priethor]

@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! 🔓

[Automattic @automattic]

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!

[Héctor Prieto @priethor]

@jeffikus Thanks, Jeff! What would change it from "interesting" to
"I'd use it"?

[Héctor Prieto @priethor]

Plenty of edges still, but evolving fast. Try it locally; issues and feedback welcome:
https://t.co/UyG9PHIb23

[Artur Piszek @artpi]

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 ⬇️

[Rich Tabor @richtabor]

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.

[Jonathan Desrosiers @desrosj]

Wordpress 6.7.1. Release Schedule https://t.co/cydbCrjQqR

[Rich Tabor @richtabor]

WordPress 6.7 “Rollins” is finally here! ✨

Here’s everything you need to know about the latest release of WordPress:

[Rich Tabor @richtabor]

the official WordPress 6.7 release video

https://t.co/DuKccrS6su

[Héctor Prieto @priethor]

@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 :)

[Héctor Prieto @priethor]

@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.

[Héctor Prieto @priethor]

@vforvicente_ I hope you already patched the lock and didn't disclose a zero-day vulnerability on Twitter😆

[Héctor Prieto @priethor]

@antpb What table was that? If you have their contact, I would be happy to reach out during WCUS and help onboard them 🙂

[Héctor Prieto @priethor]

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?