This design is a single column, fixed width theme, with 2 footer widget areas. 1 area contains 4 widgets that stack horizontally, the other area contains horizontal widgets that stack vertically. The main page highlights the first post, and shows the next 4 as links below the first.
Some abuse of a stock photo by Ryan Ford.
Based on “for elaine“, which became archGFX v02.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 of the License.
This design is dual-licensed as Creative Commons Attribution-Share Alike 2.5 License. Where possible, please include a link to this page for attribution.
Select the Sandbox-10 theme (currently on page 4). Then open the download link below, and copy the contents into the Edit CSS box, Making sure to check the “Start from scratch and just use this” box.
Promised Land CSS
Scott’s organizing a wordpress design competition, purely in CSS. which means it’s open to:
- wordpress.com users
Also, Sourceforge is running Community Choice awards, so you can go nominate Dream in Infrared, if you’re so inclined:
(Disconnected is also eligible).
Hot on the heels of my own sandbox-based theme, Scott and Andy went ahead and dropped Sandbox v0.9 (0.7 only existed long enough for me to grab it out of SVN and build my theme off of it, and 0.8 had too many revisions to be released. 1.0 existed briefly, before being dragged back into beta-ville). The structural changes are much cleaner, so it’s easier to tweak the hell out of the thing.
The only new design element is that all of the example layouts now use a navigation menu. This is kind of an outgrowth of the skins menu being deleted: the menu HTML is always there, although it can be hidden in CSS (previously skins could disable the HTML).
And yes, the skins menu is gone. this means theme designers can now rely on the sandbox having a specific CSS. hello
template: sandbox. 🙂 Accordingly, my skins have become themes:
The thin line uses about 4 lines of PHP to insert a credit link into the footer. The Joshuaink theme uses that plus the custom header API to help you add your own logo. Both themes are under Creative Commons licenses. Whatever waffling the wordpress developers may do about some themes being necessarily GPL, they can’t touch these themes, since they’re entirely CSS, save for API compliance (if API compliance transmitted the GPL, binary linux applications would be impossible).
Also, I’m discontinuing development on Sandbox Unsleepable. If I were to convert it to a theme, it would compete directly with the original, which is not my goal. Since the original has been installed on wordpress.com, there’s also no reason to develop the custom CSS version either.
(Click for more Screenshots)
I planed to finish this theme before i rebooted this site, so that I’d only have to worry about customizing my own version of it. instead, life got crazy, and i stopped working on it for a few months. So I’ve had to backport some things from this site, and i’ve developed a bunch of features for the theme, that i have yet to put to use here. So a month late, here it is: A fluid width, light on dark theme with lots of CMS features. Based on the rich semantics of the Sandbox theme
Read about the features | Check out the Demo Blog | Download
while i was getting ready for the reboot, i set up my blog to pull down wordpress from SVN (the 2.1 branch). it went alright, except that after i moved over my theme and my plugins, i forgot to move over my uploads. (i’m not very bright). Then again, that folder really shouldn’t be there. So, in addition to having a half-finished reboot, i’m also missing images from any posts earlier than, say, 3 days ago.
but, you know, go vote for the rest of it: CSS reboot (before), Standards Reboot.
dunstin’s site has a new web2.0 looking logo this year. so that your site isn’t as ugly as last year. it’s not really important, though. the whole concept is still
self serving, confusing and disenfranchising to users
so no, i’m still not doing it.
standards are nothing if they’re not also best practices.
This is a somewhat sort of half-assed port of a theme that i’m working on. the theme itself hacks a sandbox core to bits, but this is purely sandbox. we’ll see if i can live with the bog-standard state-switching capabilities of the sandbox. naturally, i’m still in the midst of fucking it up, so watch your step.