Cloud Weblogging

The Loop: The future of WordPress

The Loop: “Do something like Medium or Svbtle that doesn’t have the complicated backend and code. That’s what I want.”

Hello, Dr. Jones.I probably harp on this too much. I’ve been browsing around for a simplified weblogging tool, but WordPress is just too darned good to give up. I would, however, love to see a version of WordPress that would allow me to publish everything as static HTML. Decouple the composition from publishing, make them separate services. I compose a post, save it, when I click “Publish” the site is regenerated and pushed to my domain. That’s it. I would also be nice to have a quick and dirty post editor that doesn’t include all of the administrative functionality, think QuickPress in a standalone web app, or maybe a desktop app (that would be really nice.)

Make sure you read the linked article, The future of WordPress: “By incorporating a RESTful application programming interface (API), current WordPress apps could be supported, as well as mobile apps that use WordPress as a backend.”

This is how all sites, web app type sites, should be constructed. It’s all about services. Create a service, use the same service from the web app and mobile and anything else connected to the internet. Yes, yes, yes!

By Rob Fahrni

Husband / Father / Developer

5 replies on “The Loop: The future of WordPress”

This is something that I’ve been hoping for as well. I wish WordPress worked more like a push system where the generated pages are just static HTML. If anything were to go wrong with the system, the static pages wouldn’t be affected.

That’s exactly right. Just plain old HTML is all I need, but I love the editing and site management aspects. Just decouple the publishing, BING!

as was mentioned on the most recent YAPcast, “when MARVEL publishes an API, so you can programmatically find out what issue Spiderman was introduced, there’s no reason for anyone not to build an API to their data.” The glue that binds the Internet together is moving (has moved?) from HTML to HTTP/Rest.


It seems the natural way. If you’re not creating a web API, of some sort, you’re missing and entire segment of the market; mobile.

Of course you can give folks a mobile site, but a nice native application communicating with an API can give a much better user experience. That will, of course, change over time as the browser and its support for different development languages comes to pass.

I’m still holding out hope for someone to do a full CLI implementation. Microsoft should partner with Apple to do that in IE and Safari. 🙂

not to mention that if you’re not creating a web API, of some sort, you’re also missing an entire set of (potentially more proficient) programmers and designers that could add value to your product (while simultaneously perhaps adding value to their portfolio and financial records).

Comments are closed.