I have been on a bit of an update spree on Zebra lately, removing, adding, and changing settings. One of the biggest changes I made was to rewrite the pagelayout.css
@media queries using the HTML5 Boilerplate mobile first design theory.
Work has cooled a little bit on on my California theme for WordPress, partly due to other projects (Moodle themes, Mahara themes, and a NEW WordPress theme), partly due to the fact that it’s pretty much working the way I want and I don’t have much incentive to continue to update it… Anyways here’s a brief overview of the major features that I have implemented:
Boy that’s a lot of ‘P’s! Let’s just jump right in, shall we. Here’s the scenario, a user creates a post that they only want to share with select people because of the private nature of the post (notice I say post, not “content”) so they password their post and publish it. WordPress by default will block
the_content() from displaying as well as
comments_template(). That’s good! What’s not good is the amount of thing it doesn’t block.
One of the things I loved right off the bat about WordPress is that it’s extremely flexible in terms of output and rendering, and that its built in functions are simple but also robust. Here’s an example of what I’m talking about. If you want to output a sidebar (widget area) you simply call the
dynamic_sidebar() function and WP handles the rest. A practical example of that might look something like this:
Moodle 2.0 introduced the ability for a theme to plug in a custom settings page and allow an administrator to change some settings. Moodle 2.0 also introduced a new image renderer that uses an output function. I wanted to allow a user to use either format in a setting, and for it to be as transparent to the user as possible. Thanks to a pointer from Richard Oelmann I was able to do just that. Here’s a short walkthrough of the files necessary and the functions to allow a user to set a custom image, using any format.