I’m getting the itch to code Inklog again. bBlog’s been doing pretty well for me. But I’ve got some more functionality that I’d really like.
I dislike that my URLs (as clean as they are) only have ID numbers in them. Not very useful for trying to figure out what something is without looking at it. Dates, or title words, or both would be more useful. Adding another field into bBlog to allow for this would be fairly easy, I think.
Additionally, I’m getting the hankerin’ to have multiple blogs again. I know, every attempt I’ve made in the past to split my life into nice little chunks has failed miserably. But, none the less, I’d like three main sections: Tech, Life and Art. Really, they should all be on one blog. So, I may end up doing some super-complicated category assignment to handle what shows up where and why. But that’s confusing. I’m thinking that I’ll have SUPER categories for the various sections of the site (which are already mostly employed). This would be things like “Tech”, “Life” and “Art”. Then, I’ll add another category called “Front Page” which is for items worthy enough to make the Front Page of the site. Then, the actual Front Page will be broken up into three pieces, each showing the most recent entries from each of the three sections but ONLY including those items found in the “Front Page” category. People using RSS readers can then subscribe to the entire site, just one (or more) categories, or just the Front Page category, getting just the good stuff (as I deem them “good”).
One of the reasons for wanting different sections of the site is to allow each of them to have a different look and feel. This can also probably be implemented in bBlog fairly easily.
I really like to improve bBlog as opposed to rolling my own, because that way I’m working towards the greater good of open source software and fostering interaction and improvement. The bBlog project has been very generous to me, allowing me direct CVS access and the ability to modify whatever I please. However, sometimes, retaining backward compatibility and upgradability is difficult. And having to keep that in mind makes coding a little bit more difficult. There are many changes that exist in MY code, that I have not commited to bBlog CVS, simply because too many things would break for other people if I did. The problem with that is, when bBlog gets updated in anyway, my code has severe problems. And, because fixing things that aren’t broken isn’t exactly what I call fun, it’s easier to just not update my copy of the code than it is to fix all the problems that doing so would bring. However, now that I’m planning on altering the code again, and not just updating, I’ll have to sync up before I can begin.