Big update coming: WP Smart TV is evolving into MediaBlaster 🚀
Something unexpected happened after I sent out the first email about this Skool community. A bunch of people replied. And the thing that stood out was this: A lot of you are still using WP Smart TV. Honestly, I didn’t fully realize that. I knew people had installed it over the years, but after Roku Direct Publisher shut down and the IPTV landscape changed, I assumed most people had moved on. Meanwhile, behind the scenes, I’ve actually been working on a major transformation of WP Smart TV for about a year. The new version is called MediaBlaster. And for a while, it was just sitting on my hard drive. Not because I didn’t believe in it. But because I wasn’t sure if people still cared about this problem. Then the emails came in. People were asking about IPTV apps. Video publishing. Roku-style front ends. Using WordPress as the engine for their media platform. That changed things. So now we’re bringing MediaBlaster back to the front burner. The old WP Smart TV plugin was built to help people publish video content from WordPress. MediaBlaster is the next evolution of that idea. It’s being rebuilt for creators, agencies, publishers, and AI-powered media builders who want to turn WordPress into the backbone of a real media platform. Here’s what we’re working toward: ✅ Better video publishing tools ✅ Vimeo importing and management ✅ Podcast support with shows and episodes ✅ REST API endpoints for headless sites and apps ✅ Subscription and premium content tools ✅ AI-agent-friendly workflows ✅ Documentation for building front ends and apps ✅ Tutorials for using AI to move faster ✅ A clearer path from “I have content” to “I have a media platform” The bigger vision is simple: MediaBlaster should help you build your own video site, podcast network, course library, streaming-style platform, or AI-powered media brand using WordPress as the engine. And this Skool community is going to be a big part of that. We’ll share the build process, the prompts, the tutorials, the documentation, the mistakes, and the workflows we’re using along the way.