Sometimes... sometimes it's just so, so nice to buy something pretty. Something that is not strictly necessary... but, well - pretty.
That is exactly what I did yesterday. I bought something for the new website. Something that really was not strictly necessary, not even un-strictly necessary... however, I've long been in love with the idea of it. And what better time to change something design-wise if not a website overhaul?
Otherwise, the changes will not be huge. There will some re-ordering of the main page articles, and some more articles on the main page, mostly information about spinning. The logo stays the same, and I'm also still quite happy with the shade of red I have as accent colour, and the general setup of the shop and shop software. The whole site will stay bilingual, and I'll also keep the three sections main page, blog, and shop.
The blog, however, will migrate to a new blog software, hopefully rendering all the comments more reliably, and allowing me to cross-post to Facebook as well.
But everything will be using a new, shiny, pretty font that I'm utterly and completely in love with. Bye bye, Cabin, you widely available but rather boring thing with your not so pretty @ sign and your not so brilliant kerning in the webfont version, which I had to fix with an extra plugin for the old blog software. Hello, shiny new font that is a semi-serif, because of course I could not decide whether I like a serif or a grotesque better (and they both have their pros and cons), and works well in print and on screen, and is just. so. pretty. At least if you ask me.
Here's a sneak peek of how it will look on the new blog:
Ah. I know it's a little nerdy, but I'm all delighted now.
I have a few more articles to fix up, a list of things to check and test, and then it will soon be time to take a deep breath, take the old site offline, make a gazillion of backups of everything and start the migration. I'm a bit scared, to be honest - it will mean migrating the blog plus pulling things from two different sites into a new one, in a mix of setting options and values directly in the backend, file copying, and SQL editing. The latter is the scariest bit, because a) I don't know much about SQL (read: next to nothing) and b) this is where most things can go horribly wrong and wreck the whole new clean shiny (and hopefully flawless) installation.