I've decided to rewrite Bluetrait.
It's had a good run.
Getnews (the blog script that I wrote before Bluetrait) was aimed at providing a very basic blog with commenting support. It did this well, but a lot of it was hardcoded to my domain/style so it wasn't really useful for anyone else.
I wrote Bluetrait 1 as to allow others to easily use/install it. It had/has a very basic template type system. Over the revisions it has been slowly upgraded and now includes:
It has worked well on my site for almost 3 years! But it has some limitations that are starting to annoy me. The biggest problem I currently have with it is the way the CMS side works.
There is no way to categories pages and as my project page grows it is becoming an issue.
So I'm going to take what I've learnt with Bluetrait 1 and rewrite it.
I'm aiming to make Bluetrait 2 able to cope with all kinds of content for example:
The idea is that the core of Bluetrait will have a section that allows people to design their own plugins which allows the system to handle any kind of data output.
Bluetrait 2 will also require PHP 5 as I'm using the PDO database class to allow for almost any kind of database (mysql, sql lite etc).
So the coding has started. Plugin support is almost done. I don't expect to have anything finished this year, hopefully early next year.
You either define each tag in a separate record....or store them with the record they describe as comma separated keywords....option 2 seems better...Not sure if I agree with you there. Why? How often do you post a comment verse how often does a user go through categories/tags. Personally I don't think it matters all that much about how long it takes to insert the new tag. Because you're only dealing with a really small amount of data (compared to that in the database). Plus you can easily setup two mysql servers, one for read, one for write. My plan with categories is to have full breadcrumb/search features. The plan being to have heaps of sub categories that you can browse through. Back on to the topic of tags. I think it would be difficult to sort tags based on how popular they are with your second approach. With a tags_to_posts table it is a very simple count query. I do think your second way would be quick for displaying a single post (or the posts on your front page), but I don't think it would be significant enough to justify it. I've decided to use this category library for Bluetrait 2. Although I think I'll need to rewrite most of it. 5: Comment Link