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
wordpress 2.2 is out. Easy upgrading is still a ways off. unless you’re me, and you’ve moved to SVN. then it’s just
svn switch http://svn.automattic.com/wordpress/branches/2.2/ 😀
the latest undocumented features include atom API support. all that coding in app.php does little good if you don’t reference it. going off of what my wordpress.com blog looks like, you should add this to the head of your blog:
<link rel="introspection" type="application/atomserv+xml" title="Atom API" href="<?php bloginfo('url') ?>/app.php" />
you can implement that as a plugin, or in your theme. i’d love to see XML support moved to the core, but that might just be me.
I’ve merged my geek blog back into my main blog, so watch your step. wordpress.com readers may want to bookmark my feedburner feed, as i don’t think i’ll be triple-cross-posting for long.
Sometime last year i started maintaining a separate geek blog, where i was posting all the geeky sort of stuff about wordpress. What started as a list of hacks turned into something resembling a real blog, mainly because people were paying attention to the geeky stuff. When i started, i wanted to focus on writing more architecture/design related posts here. As it turned out, it was easier to bang out 5 minute posts on a new hack, or a new gripe with wordpress. Since i’ve barely had time to even post in one blog, this blog’s been a bit of a graveyard. To the point that i even started posting semi-design related things in the geek blog. So i’m giving up on the split.
However, i don’t want to lose all the lovely traffic that wordpress.com has brought me in the last year. Naturally, it’s not trivial to merge two blogs without breaking any links. but it’s the steps aren’t too bad one at a time:
- buy domain mapping on wordpress.com. once it’s been running for about a week, you can safely start the rest of the steps. the wp.com servers will start redirecting people from username.wordpress.com to username.yourdomain.com.
- export your entries. make sure to delete spam before you do. this shrank the size of my *.WXR file to a fifth of what it was.
- set up a subdomain with your host. most hosts do this fairly easily. bluehost definately made it a breeze. the process is going to be different for every host, though.
- install wordpress in said subdomain, immediately. until you’ve got wordpress set up, people are going to see an empty directory listing for every entry.
- import all your old entries into the subdomain blog.
- change your permalink structure to “date and name based” to match wp.com permalinks.
- install the Permalink Redirect plugin.
- in the “Old Permalink Structure” field, paste in
/%year%/%monthnum%/%day%/%postname%/, and check the “redirect hostname” box.
- somewhere around here you should double check that any links to your wp.com blog are landing on your new subdomain blog.
- import the same entries into the destination blog.
- change the permalink structure of the subdomain blog to match the destination blog.
- check that all the entries have similar url’s. if you have posts in multiple categories, wordpress my change up the order on you. since my geek blog was pretty focused, i trimmed everything down to one category (with a whole lot of tags).
- Last step: double check everything before you do this (expecially the checkbox on step 8): on the subdomain blog, in general options, change your Blog Address (URL) to the address of your destination blog.
That will make the permalink redirect plugin start sending everyone to your destination blog’s URL, with the matching permalink structure. The plugin only works for posts that exist, though. it can’t just make up category names (or whatever else is in your permalink structure). As long as you don’t change the WordPress Adress option, you should still be able to access the backend of your subdomain blog (should you want to make placeholder posts).
Anyway, i don’t know how much use this is to anyone else, since most people have the good sense to not try to write two blogs at once, but there it is.
so yeah. apparently when you set up a subdomain with bluehost it IMMEDIATELYDONOTPASSGODONOTCOLLECT$200 deletes any CNAME records for said subdomain. odd, considering that you have to petition their support to even add CNAME records.
So no, i didn’t mean to move this blog off of wordpress.com (gratuitous link for people who meant to continue surfing their dashboard) right this very second, i was going to do it eventually. I was planning on giving mark & co. a little more time to take me out of the global tags. granted, i did already have a conversation to that effect:
Me: “I’M IN UR GLOBAL TAGS POSTIN DEM SEXY FOTOS”
Mark: “We’ll keep a close eye on that one, can’t trust one hippy let alone a whole bunch 🙂 ”
clearly, my continued obsession with icanhascheezburger is hampering my ability to communicate with anyone who is not inside my head.