Last summer Brendan Sera-Shriar and Chris Bavota launched PressWork, a drag and drop theme framework. They announced the framework at WordCamp Montreal, saying they created it for themselves as much as WordPress beginners and developers. Sixteen months later, and despite helping “tens of thousands” of users to build their sites with PressWork, Bavota and Sera-Shriar have bid PressWork farewell and closed its doors.
“It was really a scaling issue,” Sera-Shriar told WPCandy. “Basic startup problems 101. We needed staff and time and had no budget.”
Back from our Thanksgiving hiatus full of tryptophan and nonsense, the crew has its thirtieth episode in the can. Thirty. Episodes. Milestones are fun. So are italics.
First things first: big thanks to Robert Nienhuis, one of the organizers of WordCamp Orange County, for putting together the new, awesome WP Late Night logo. You can expect to see it showing up in a few more places real soon.
In this week’s episode we discussed the first release candidate of WordPress 3.5, WebDevStudios acquiring Startbox, WordPress maintenance services, and of course our bar tricks. Special guest Brian Richards also joined us for a few minutes to discuss Startbox and WebDevStudios.
The WordPress Theme Review Guidelines, in line with the upcoming release of WordPress 3.5, are under review and discussion by the Theme Review Team. Chip Bennett began the discussion on the Make WordPress Themes blog, where he explained the new version of WordPress will have little effect on themes aside from support for HiDPI screenshots.
Also up for discussion are new guidelines prohibiting themes from bundling custom content shortcodes, reduced criticality for content sidebar implementation in themes, and the importance of automatic feed links support in dot org themes.
A number of other items are brought up in the comments following Bennett’s post, and should be an interesting read for anyone who tries to stay on top of WordPress theme standards.
At the very least, the talk about prohibiting themes from bundling custom shortcodes sounds like a big step in the right direction — at least, I think I know of a few people who think so.
Now’s your chance for input: what would you like to see tweaked about the dot org theme review guidelines?
This episode of Aftertaste follows the continuing discussions of WP Late Night #21 with special guest Drew Strojny. We spoke more about themes, as you might expect, and more about the process behind designing and building Twenty Twelve.
You might remember when the Automattic Theme Team announced their _s theme on ThemeShaper back in February. This week the team announced Underscores.me, a new home for the framework theme and those who build websites with it.
The personified theme (which is always fun, of course) says this on the home page (emphasis mine):
Hi, I’m a starter theme called _s, or underscores, if you like. I’m a theme meant for hacking so don’t use me as a Parent Theme. Instead try turning me into the next, most awesome, WordPress theme out there. That’s what I’m here for.
I find this interesting in a theme climate where everyone is promoting the use of theme frameworks – almost exclusively – as parent themes. Automattic’s team here, though, sees the theme’s goal differently. Ian Stewart, Michael Fields, and Lance Willett were the primary authors of _s, though twelve other folks receive credit for tweaks to the theme via Github on their site.
Have you used _s for a project? Do you think it stands up against other theme frameworks – particularly any of the paid ones?
Episode 21 (we’re legal!) of WP Late Night saw an awesome guest: Drew Strojny of The Theme Foundry and, of course, lead designer for the new Twenty Twelve default theme. We discussed themes (duh), plugin reviews, and of course I asked for Drew’s opinion of Retina/HiDPI displays — much to the dismay of Brad and Dre. Fun ensued.
A default thumbnail is generally not something that’s permanent, so you wouldn’t want to save it, leaving yourself a world of pain if you ever wanted to change it in the future. I’ll keep this simple and afford you that future flexibility. I’ll even show you two ways to do it.