
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.









9 Comments
Just a quick comment for the moment:
Good choice by making themes with a Sandbox-core instead of Sandbox skins—this is exactly what I hope people will use the Sandbox for. Plus, after this continues to occur and the Sandbox core matures, it’ll become that much harder to best.
These are excellent, Adam.
By the way, really enjoy your narrative of the Sandbox versioning.
rawk.
i made the whole narrative up just so i could say “beta-ville”
He he he.
Let’s hope the days of “…based on Kubrick” are close to over.
I haven’t played around with sandbox much. After reading your blog post I feel I need to look into it. Now I need to hunt for some tutorials
the best place to start is probably the readme. previously i would have said lorelle’s starter list, but that’s based on 0.6.1, which is a bit out of date. scott or i should send her an updated version.
Before Lorelle updates hers, we should wait until v0.9.x is available to wp.com blogs.
But perhaps a selector-full, descriptor-empty
example.cssfile is still in order. I’ll post something later tonight on my blog.Thanks adam …. I will look through it.
I love SANDBOX. I can never find out where to start with it though. But I plan on finding out!
4 Trackbacks/Pingbacks
31 May 2007 at 1:46 pm
Weblog Tools Collection » Blog Archive » Announcing The Sandbox Designs Competition
[...] have been more than a few themes/designs built on the Sandbox and released—and for good reason. Its highly semantic, [...]
03 Jun 2007 at 10:53 am
we're going to move some sand « wordpress™ wank
[...] (no stock photography, icons, brushes etc.) and I don’t see the necessity for it since, as adam points out, not even the most rabid free beer fundamentalists can seriously argue that CSS for WP needs to be [...]
03 Jun 2007 at 10:56 am
Sandbox Design Competition « not (that) ugly
[...] (no stock photography, icons, brushes etc.) and I don’t see the necessity for it since, as adam points out, not even the most rabid free beer fundamentalists can seriously argue that CSS for WP needs to be [...]
08 Jun 2007 at 3:04 pm
WeblogToolsCollection Español » Blog Archive » Anunciando la Competencia de Sandbox Designs
[...] habido mas de unos pocos temas/diseños basados en Sandbox y publicados -y por buena razón. Su estructura [...]
Post a Comment