Héctor Prieto

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

Then I think the marketing/positioning needs to clearly answer why this is better than, say, Notion or Mintlify if you want considerable adoption. It's too easy to just reach for the name brands as a startup or small business. If I'm building out a kb for my business, I want to have confidence in the platform long term. "WordPress" and "Automattic" do provide some of that confidence, so I wouldn't shy away from it. However "Your data, your rules" is not a selling point imo. It's a nice-to-have. The product itself has to be more compelling than the alternatives.

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.

@priethor Interesting project. I can see this appealing to existing WP users.

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

Notion for WP docs

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

is this notion or WordPress?

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

@priethor Nice work. What’s the long term goal? The competition in this area is steep. Mintlify comes to mind.

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!

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

@priethor Super interesting. Probably the most interesting thing I've seen in the WP space in months.

Plenty of edges still, but evolving fast. Try it locally; issues and feedback welcome: github.com/Automattic/cor…

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.

Wordpress 6.7.1. Release Schedule make.wordpress.org/core/2024/11/1…

WordPress 6.7 “Rollins” is finally here! ✨ Here’s everything you need to know about the latest release of WordPress:

the official WordPress 6.7 release video youtu.be/Ok6JKHMAkH8?fe…

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

@mikemcalister @jeffr0 :) I wish I could still speak to that progress on the roadmap. I only know where things were going while I was still active on it. @mikachan_ @priethor any thoughts on this?

The font manager/library introduced in WordPress 6.5 is one of the coolest features in WordPress. You can install and use fonts from Google without leaving the WordPress backend. make.wordpress.org/core/2024/03/1…

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

@JavierCasares @richtabor Whatever the next thing is, an evolved WP or a prominent fork - it's well past time for a LTS release channel for something this widely adopted.

#WordPress #WPdrama What I expect to happen in the next few days: On Monday, the 21st, Mary Hubbard starts and can put a wall between Matt and the Community (.org). - Access to all blocked contributors is restored, both in Slack, and on Twitter. - The login access checkbox is removed. - The obligation to buy a ticket to a WordPress Event requiring a user access is eliminated. - I have doubts about the ACF/SCF. In any case, although debatable, I do not think it is necessary to restore the community (for now). If these things happen, which indirectly assumes that Matt will focus “on his company stuff” and leave the Community and the Project aside, I think most contributors will actively participate again. But this depends on that vet power that can be applied. If at least the first 3 things on the list don't happen, I think we're already going to mid-January. Why? In mid-November WordPress 6.7 comes out, and I doubt that anyone will start setting up equipment for WordPress 6.8 immediately, for one thing because from late November to early January holidays begin in many parts of the world where most of the contributors are. Add to that, that people will want to get out of the current noise and will want to temporarily get away from the project and rest (which I recommend to everyone, including myself). This means that we are going to early mid January which will be when the 6.8 equipment will be assembled, which also means a delay in the launch date, which would not be in February-March, but in April-May (which would probably lead to only two releases in 2025). And this is where we will really have to see how everything is in general, how is the legal part, how many contributors there are (and if there are not, how Automattic will supply them)… I sincerely hope that the first step happens because if it doesn't, this whole process and the next releases will be uphill.

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

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

@priethor fwiw the folks that came through the table I was working at wanted to get the basics on process and local dev with the desire to contribute to Gutenberg next. Time was a factor I think

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?

@dbchhbr I am :)

Any Windows users interested in trying out the Studio beta?