Perhaps ironically, this blog post has sat as a draft with a mere title and no content for a couple of days now. Progress, my friend!
Two and a half months ago (wow, really that long?), I of course, ambitious as ever, said I would create a content management system – some blogging software.
Well I haven’t given up, but I have only put in about a days work total. As usual, it was one of those “think of a mildly good idea before falling to sleep” kind of ideas… I had it all planned out in my head, but by the morning it had all gone. All I was left with was a silly name. SnowyCMS.
The other day I decided I fancied learning some git – the software version control system. It always sounded interesting when I’ve read about it in the past. I always thought git was some kind of super complicated thing that only the cool programmers use, but no, the main functionality and commands, at least, are extremely easy to understand.
With git, came a renewed excitement towards the project. It made me feel that the project had increased in importance and sophistication, even though it was just a private repository. So, I’ve started working on it again.
I would really like to finish this project off, even if it takes me a half a year, or two years… whatever it is – I just want to do it to prove to myself that I can finish it. Hell, it’s probably not going to be half as good as I want it to be, I’m no PHP master, but if I can finish it to a reasonable standard then I will be happy.
Of course, I want there to be a distinction between what I want my software to be and what I can already go and download right now online. Many modern CMS systems focus on things that I wouldn’t, simply because I find them to be negligible features that do nothing more than be annoying – for my usage scenarios. I currently use WordPress, which has a lot of extensibility and a huge array of functionality for bloggers. For me though, the only plugins I have are security enhancements, and the only functionality I use is the Add Post and Edit Post buttons.
I really have had no idea what my plan for SnowyCMS is. I feel as though I need to reconsider what I actually want from it, so here’s the general idea of what I’m thinking:
- Lightweight flat file CMS.
- For experienced/power users who prefer control over usability (not to say that the blog would be difficult to navigate, merely the admin panel would be simple but with advanced capability).
Well, that wasn’t really worth two bullet points. Essentially though, what I’m thinking is, I’d like to make a simple CMS which has less of the automatic features that popular CMS’ tend to. I don’t like it when WordPress does everything for me, creating that giant folder of messy, duplicated thumbnails all over the place. Not to say I want to boot up some image resampling software and downsize my images manually every time, but some extra control would be nice. Perhaps I’m just not cool enough to understand WordPress.
When I blog, I overcome no challenges in actually producing the final post (aside from me being generally bad at writing blog posts, of course). Since I’m a fan of occasionally and spontaneously learning better standards, improving my disappointingly bad knowledge of markup languages, and whatever else – why not just make it so writing a blog post sort of does all these same things at the same time? It would be nice to improve the formatting and structure of my blog and its posts, but I’m not very good at it.
If I had to do it though, it surely wouldn’t take long to learn.