Well, okay, not all that swiftly. But whatever.
The About page is up!
And with that the purpose of this post has been fulfilled…
Though I guess I might stick some thoughts on this blogging process down? Very well, I’ll get into some of the “how” of it (the “why” may come later).
Writing that ridiculous About page took me about three hours. No coding, just waffling. So this is a bit of a time-consuming process, but rewarding once you get to see it up. So that’s nice.
Prior to even getting along to the About page was a whole lot of fighting and confusion (mostly confusion) with how exactly to do this blog thing. I was trying to make it all fit with some sort of grand, unified plan that I’d yet to formulate, but delayed formulating because I was figuring out how to do things but couldn’t proceed with how because I didn’t know what I wanted to do…
Firstly, I tried to use Concrete5 to build this site and as my blogging, err, platform (?). While it does look to be a great system with a lot of great functionality and interesting features, I just couldn’t seem to wrap my head around it and make something simple that I thought looked nice too. I know it’s possible, and I’ve seen great sites made with it, but it feels like it needs to be used to design a site before you can really get cracking on content (and not knowing WTF I wanted to design didn’t help). Making all the blocks and stacks and “area thingies” work together was driving me nuts, so I scrapped Concrete5 and tried the WordPress route, which is going well. Seems there might be a little less flexibility in the look of one’s site (at least, without CSS wizardry and more in-depth know-how of how WordPress ticks) but the bloggy bits seem to just work right out the box with a little more ease. I also decided to bugger the thought of a plan (at least, for now) and just wing it, and that’s gotten us here.
I’d equate the difference between Concrete5 and WordPress to being similar to Linux and Windows: Linux (Concrete5), perhaps a desktop distro like Ubuntu, may be easy to install and it’s GUI has just about everything an average user needs, but a lot of it’s “admin” power remains in the terminal and needs more in-depth knowledge to unlock (maybe not developer type knowledge but certainly an “occasional use” sysadmin type knowledge). Windows (WordPress) provides a GUI that’s got more of the system’s core tied up into it, so the barrier of entry to “admin” type work is lower because it can pretty much all be found within the GUI. That’s not to say that Concrete5 requires terminal or coding work, it just feels like certain admin functionality is buried deeper.