supernaut wordpress

Six months ago, deliriously annoyed with Movable Type, and deeply envious of all those people using WordPress. I install WP, throw a theme framework on top and promptly run away, terrified of what harrowing coding ordeals would ensue when I tried to make new look like old.

I have an end of year list of things to do. Coding for some, editing for others, rsync, asr, and other delights of command line backups for still another. For me, one was to use the brilliant, entirely CSS 100% background image for francesdath.info. That took all of 40 minutes or so, mostly in cleaning out my old junk from when I decided to code that version in an afternoon.

The other, of course, forced me to look at supernaut once more.

I’ve been using WordPress for all my projects lately, and the more I fall into it, the more I love it. A while ago, after much looking around, thinking, reading, and even a couple of trials, I decided on Blueprint CSS as the typographic CSS framework to build sites upon. Rather than lose time that could be spent sleeping…

Blueprint is a CSS framework, which aims to cut down on your development time. It gives you a solid foundation to build your project on top of, with an easy-to-use grid, sensible typography, useful plugins, and even a stylesheet for printing.

— Blueprint

… and a Photoshop layout to build designs upon that then can be transferred ridiculously quickly into a real site.

Of course the limitations are firstly of setting up a WordPress theme with all the necessary IDs and classes. Lucky someone else did that for me. Combining the Sandbox theme framework with the WSB Child Theme

WSB is a Sandbox child theme that provides tight integration with the Blueprint CSS. This is the conclusion of the method of integration discussed here. Using WordPress functions file, Sandbox template files, and Blueprint CSS files creates a excellent minimalist theme that is a very strong starting point for further theme development and customization

— Nedsferatu.com

… I began this afternoon and lazily poked at some CSS, a little hackery in one or two of the functions.php, some shuffling of the Sandbox templates php (which I could have done in css and left all this untouched but I was feeling lazy – much cheese and chocolate). To be pedantic, I began around 18h and it’s now 2315-ish, and with a good hour or more break in that time, so perhaps 4 hours of actual conscious attention, supernaut went from before to after.

(Mostly.)

moving…

I have spent a lazy Saturday transferring supernaut over to WordPress (more on that there). The result of that for the moment is the old Movable Type site exists at supernaut.info/index1.html and in the static archives while the new at the usual address.

This means also the RSS feed has changed, so for those of you who like feeds, I am now at: https://supernaut.info/wordpress/?feed=rss2.

I won’t be deleting the old version yet, as the new one needs a lot of construction I shall only have scant time for, but distinctly odd weirdness (like this feed showing garbled rubbish for instance) would make a good moment to email me with the offending instance.

Movable Type was good four years ago, but in the intervening time much has changed and it is too much of a hassle to work with any longer. I hope I spend the next few years enjoying WordPress as much as I have over the last while, and find maybe some new ways to blog.

from ecto 3 to wordpress 2.8

uuhhh…

When I started finding odd stuff in my Movable Type install for supernaut I knew the end was near. I’ve been putting this off for a long time, especially doing projects for others using WordPress and thinking, “uuhhh… this is so much better…”.

Something made me decide to do it today… teaching myself about .htpasswd and so on, and crappy MT plaugins, I wondered… “If I install WordPress in its own directory then link it to supernaut’s SQL database, will that work?” Immediately before trying I realised it would/wouldn’t, so set up a new database (the bit that wouldn’t) installed WordPress (would) messed around for a bit…

… dumped a file called index.php in the root directory pointing to the WordPress install…

Hell-0 )))!!!

Funnily enough, that was all. Everything seems to be here, much is broken, obviously the old theme has yet to make the jump (shall wait on that…), but words and pictures!

So then I decided to get ecto, my looooong time trusty blog client to work. Messed around, lost 1400 entries. oops…, I thought, hope they come back… Found them again. More messing around, wondered if ecto 3 would be worth a try. More of the same…

Hello blogging from ecto 3 to supernaut on WordPress 2.8. Total time it took was about an hour.

I have no idea what might not be working, but shall continue like this.

Oh! RSS feed! supernaut RSS feed.

In the meantime, I shall mangle this theme a little to see if I can at least have the existing content… umm… re-exist.

Keywords? ecto doesn’t seem to support keywords with WordPress, instead using Tags, which still work, but not as fast for me as entering a string of words. But, contra that, the 1500 tags I have I can search and so perhaps shall be a bit more economic in inventing.

Aaaaanyway, I am rather impressed how simple it was to get this far with so little work, and shall thank Berlin for that.