As part of the Modern WordPress Fast Track course launch, I’m sending out weekly tips and tricks to all subscribers of our FREE newsletter.
We’re kicking things off with a fun little journey through the quirky, chaotic, and clever history of web browsers — from the early days of WorldWideWeb (the actual name of the first web browser) to the performance-focused powerhouses we use today like Chrome and Firefox.
Did you know that web browsers used to include authoring tools for creating websites? A true WYSIWYG experience before even FrontPage and Dreamweaver existed.
Now we can’t even view source on mobile 😅
Luckily we still have very powerful developer tools bundled with the browsers — from inspector (remember Firebug?) to network monitoring and even performance analysis.
Here is PHP running an MCP server over SSE (not stdio) in roughly 70 lines of code 🏃♂️➡️ You don't need any of those JS libraries to use this.
There are so many undocumented features of how MCP clients actually utilize SSE. For example, the initial "endpoint" event to establish the POST request path for the actual messages.
Laravel and JS frameworks are way ahead by being developer focused and fully documented with established best practices for a broad set of web primitives.
WordPress needs to reconsider the current focus on the editor or risk becoming invisible to the next generation of builders.
While CMSs obsess over better WYSIWYGs, AI is skipping ahead by generating raw code directly.
Assembling WordPress blocks with AI feels like a dead-end. The real unlock? Better PHP/JS APIs + clear patterns so that AI can build real products on WP.
Cursor is like the new hire — enthusiastic and way faster than everyone who has been around for a while (VS Code with Copilot).
I had the same project open in both and was checking who would fix an issue with ffmpeg integration in a Swift app first. Eventually, I fixed it manually (is that how we call coding by humans now?) with an answer from StackOverflow 🤷
Just got roasted by an AI 🔥 about my strategy on socials:
> You’re creating technically dense content for an audience that doesn’t want to be lectured or debug with you unless there’s something emotionally or practically in it for them.
Fair. Brutal. True.
Does this resonate with you? What are some tactics that have worked well for you?