Kicking off the second OCWP Developer day, here on international slurpee day. Is there no holiday sacred from WordPress developers?
alex vasquez – @alexjvasquez
You know it’s developer day when… @zengy is wearing a thong #ocwp
So, things started off debating the difference between undergarments and sandals. The jury’s still out on this one. Let’s just hope this stays PG.
Loren kicked things off by covering some challenges with WP Touch Pro. It looks like there is a potential glitch in the way that WP Touch uses its own get_posts() function. The peanut gallery’s opinion included tweaking the arguments for number of posts; but it doesn’t look like that did the fix. The real big question – when is WP Touch going to get ousted as the preferred mobile theming solution for WP? It’s not very attractive. Who’s got a real competitor in the works?
Quick segue… If you’re interested in learning CSS Media Queries (so you can do conditional CSS3 formatting) this NetTuts article seems to be a pretty good place to start.
Moving on, we’re learning a little bit about PressWork.me – a new framework released this past weekend at WordCamp Montreal. The feedback so far is fairly positive, obviously taking in to account the fact that it’s only a few days old (in the wild). Looks like Pagelines and Headway have some new (sorta) competition in the WYSIWYG theme editor space.
A quick tip of the hat to the audience for suggesting ServerBuddy for doing WP testing. Thanks!
Next up on the plate – child themes – launched by Steve Zehngut and then a deep dive by Brandon Dove.
If you want to build your own child theme, you can get the basics covered on the WP Codex.
Here’s the “sample”:
/* Theme Name: Twenty Ten Child Theme URI: http: //example.com/ Description: Child theme for the Twenty Ten theme Author: Your name here Author URI: http: //example.com/about/ Template: twentyten Version: 0.1.0 */
The important thing to remember is to make sure the template exactly matches the directory name of the theme that will be the parent of your new child. Another good tip is to check the bloginfo codex entry… Template Directory and Stylesheet Directory are two different things… Stylesheets are for child themes; templates will be found in the parent.
Now Brandon Dove (pictured above waving his hands to emphasize the importance of actions & filters) is covering child themes in the Genesis framework. As an overview; if you want to do fancy things with your themes beyond just the stylesheet updates, you want to play around with action hooks and filter hooks to make things run.
Jeff Turner – @respres
“Actions and filters are what make WordPress possible.” via @brandondove #ocwp
Zeek.com – @zeekinteractive
“@alexjvasquez: Also remember the genesis simple hooks plugin. makes playing “hooky” easy. #ocwp”
This is the main argument Brandon is making – using a good framework is more than just a pretty facade. Frameworks like Genesis include numerous additional hooks to hold the theme together, and help developers add custom functionality as you go.
Helpful links, thanks Jon! For those of y’all working on Genesis toys.
Ross Teasley – @RossTeasley
Total “awesome” count by @brandondove at #wpoc: 5
Brandon is pretty notorious for his pro-awesome position.
Now, Suzette is going to give us a dev-take on BuddyPress. Oh my gosh – an actual presentation! OH: “You’re classing the place up!”
She’s really doing a really deep dive in to BP… I’m tapped for the evening, but hopefully she’ll consider posting some or all of her presentation about BuddyPress. There’s a lot to cover on it, including how to configure the database, organize the users, and also a lot of the new widgets that you get to help create better user experiences. Pay attention to the themes – child themes are effective in BuddyPress, so make sure to take advantage of building custom child themes when deploying new themes.
Well, that’s it for me folks. It’s been a great OCWP! I’ll update the post later if I catch any other good points or takeaways from the day.
Looking forward to seeing some of y’all at the WordCamp San Diego!