Mobile Specific Sites Hurt

I've said it before I don't want a different experience on mobile vs desktop. I always am scrolling around a mobile version of a site to find the link to get to the full site because whoever designed it deemed that I as a mobile user wouldn't appreciate the functionality the site brought. I still agree with the responses to Jakob Nielson's recent publication that we should have mobile versions of our sites. I agree whole-heartedly with the responses from smashing magazine here and Josh Clark and many others. It's encouraging to see the flood of people coming out to contradict the uncharacteristically unwise council from this UX giant. Here Bruce Lawsen gives a great recap of the whole story and the points argued by both sides.

Embedded Link

Why We Shouldn't Make Separate Mobile Websites | Smashing Magazine
There has been a long-running war going on over the mobile Web: it can be summarized with the following question: “Is there a mobile Web?” That is, is the mobile device so fundamentally…

Why Decouple WordPress Functionality from your Theme in a Plugin?

So this is all about writing CPTs into a plugin and not in your theme. Is there a time to not do that and include it into the theme? I'm thinking specifically when you are making the custom theme for the client rather than for stock. The client won't really be changing themes willy nilly, since they paid me to do it. I think separating the code sometimes can make it more complicated. It's not like if they change themes and notice some content is gone they can't change back, since the content isn't actually lost, but no longer supported by other themes. If they are my client and I do maintenance on the site or update the theme, I'd be sure to keep the CPT code in any new theme that is developed. And I'd expect that if someone else was doing the same they'd know where to look and how to continue support for the CPTs. I guess it comes down to the expectation that clients don't really need to be changing the theme. If they knew what they were doing changing themes, then I think they should understand that some functionality may be tied to the theme. Or maybe that's the point. Functionality traditionally has been in themes, and we should be moving away from that?

Personally I think it's easier to tell a client to come to me or at least ask if they want to change the theme (not that I'm locking into being my customer) that it would be for them to figure out some message saying the site requires a theme and a plugin in tandem, while it will still kinda work with one and not the other, it will be incomplete either way. Are we expecting them to be able to change themes, and update to new one to display the CPTs properly?

Embedded Link

Theme-ready Custom Post Types in WordPress – Jumping Duck Media
Good advice on decoupling WordPress Custom Post Type implementation from your themes. How to notify a user that some functionality of the theme might depend on a plugin that defines the CPTs. How to override theme template selection from a plugin.
Theme-ready Custom Post Types in WordPress – Jumping Duck Media
Original Article: Theme-ready Custom Post Types in WordPress – Jumping Duck Media
Dougal Campbell's geek ramblings – WordPress, web development, and world domination.

Promising Core WP Theme from studionashvegas

Check out the parent theme on github and use what works for you. I'm very interested to see the functionality Mitch has included in here. It is blazing fast very responsive and looks like a great place to start a new site. Check a demo: http://dev.studionashvegas.com/coretheme/

Embedded Link

I’m Open Sourcing My Core Theme
The last few posts I’ve made on here were diving into the introductions of a Responsive Design (and I plan on finishing