WordPress-powered Enyo Theme? Let's make this happen!

For years, I've been asking one main question (okay, not a main question, but bear with me).

Why the bleep hasn't a WordPress theme/app platform been made using Enyo?

When you think about it, most of the WordPress mobile and tablet formatted stuff stinks. In the end, you wind up having to port in some really ugly third party app, or use a mobile theme that, let's be honest, stinks. Sorry WP-Touch, you stink. And I'm a paying customer.

Enyo solved a real pain-point for mobile and desktop - having a consistent UX that rocks. Why not loop in WordPress and have an Enyo-powered CMS that everyone is already using?

I realize, this is a challenge. You're talking about wiring up a CMS, with all its calls and eccentricities into a JS framework that may not have all the relevant features perfectly aligned (galleries, etc). Then you're talking extensibility with giving people thematic controls, places to brand and put advertising, yadda, yadda. These, from what I can see from Enyo, are all solve-able issues.

The benefits are just too much to ignore. Imagine if each WordPress site could tap Enyo, and truly become an app both on desktop and on tablet?

WordPress needs this more than Enyo does, in my opinion. You look at mega-sites like Gawker, and they're killing smaller blogs because they have the R&D budgets to create unique app-friendly experiences using newer JS and HTML calls.

So, let's make this happen. If it costs money and engineering time, this is something that I think, if mocked up and presented properly, the WordPress community would be happy to fund via Kickstarter. And I, for one, will put the sweat equity in to help make that happen.

Who's with me?


  • I've considered the same thing but I've done very little work with Wordpress so I haven't invested any time in it. I'm open to helping as I can.
  • +1
    I like the idea and wonder how easy this can be done.
  • There are big obstacles here. IMO, the problem is that Wordpress works on a page generation model where navigation moves from page to page on a site, where Enyo's sweet spot is having a single-page app pulling content from another source.

    However, one good base might be to take one of the many Enyo RSS readers and adapt it as a "single-page reader" that can be embedded on a site, with the feed for that site hardcoded to it. Then, Wordpress really becomes about editing the content and pushing the feed, while web site visitors would be put into the reader interface.
  • Perhaps an API Plugin like this: http://wordpress.org/plugins/json-api/

    Again, complete conjecture on my part
  • There is / was also: WordPress for webOS is an Open Source project released under the GNU General Public License v2.0: http://webos.wordpress.org/development/
  • WordPress for webOS was focused on the backend; posting and administrative tasks. But it does give some nice design cues.

    I'm a bit wary of using RSS to parse things, WordPress does not pass everything through RSS, elements like comments/disqus/galleries/widgets do not load that way. To do it right, it's gotta replicate most of the WordPress core display elements (basically everything in and around the "WordPress loop" as it's known).

    My understanding is that Enyo can parse XML-RPC HTTP requests, though JSON is easier. The WordPress JSON API was never really supported, and has been abandoned, but XML-RPC is well supported.
  • I'm working on something, so you can start raising your expectations. ;)
Sign In or Register to comment.