Pre launching the site was quite a painful experience, it included some MORE bug fixes (this time, loads more popped up!) as well as some quick features added onto the thing (such as a navigation bar for news and podcast so you can move to the next and previous podcast / news so news searching is easier). The tags in particular seems to work really well. It does provide an easier way of organising and finding information based on keywords.

After all the bug fixes I had to export the database and import it into my client’s hosting server. After that, a few site configurations and the site was up and ready. I’m quite proud at the overall outcome of the product. Theres quite alot of features which greatly increases the chance of a user reading more pages within the site, theres also a great potential of using digg, reddit and delicious to further increase the exposure of the site to potential visitors.

Now we play the waiting game (not really, I need to write the project now haha).

• The nav bar, I’ve increased the size of the header again so that theres a gap between the nav links (in particular their hover top border) and the subtitle of the site. My client wanted this fixed in particular so it was good that I managed to get that done
• Feeds, the way they are parsed and added onto the news page. They were being escaped when double speech marks were used, a fix was to use the htmlspecialchars() function and then strip slashes on the form. The process was a bit tedious in pinpointing how to correctly parse the thing
• Logging in system, made it work more smoothly now,it will now take you back to the original page you were on
• Logging in system, I’ve also ensured that admin pages are not accessible unless you’re logged in AND you are an admin, I will also do some htaccess on this folder just for added protection
• Include more bookmarking sites on the summary pages
• Fixed the links on the meta box
• Sorted the headlinks, turned them to pink instead of white (since white was the main font so it made sense that way)
• Delete news, that works now. Twas a few typos in the code
• Fixed the comment approval section, was suppose to display “no comments required approving” but it didnt, was a problem with the query, fixed now though

That should be about it for the bug fixes, tommorow I will refresh the database so the id numbers are all nice and new and after that we’ll be able to enjoy a nice site launch. Hopefully.

• Redesign the side so that the navagation menu is at the top rather then at the side to save space.
• Implement tag and song boxes, sort out their admin sections
• Implement comments for news, this includes editing, deleting and adding
• Implement a comments page which enables an admin to approve comments that have been made
• Introduce side boxes; just simple blocks that contain things such as tags for the news, meta data for the site, comments that require moderating, user login and logout
• Implement a user logging in and out system.

I’m going to focus alot more on adding things such as digg, delicious and other social networking integrations. I’ll also be focusing more on my report.

The following requirements needs to be done by Thursday:

• Sorting columns
• Pagination
• Code cleaning

Shouldn’t be too hard, I’ve done the main functionality of the site, include tag clouds, toggle switches and general editing, creating and modifying of the data. Just needs the finishing touches

Right now I’m only using the font size as a way of demonstrating the tag cloud but perhaps if theres time I could go about doing it for font colour too (which might need a bit of configuring to ensure it works).

I’ve managed to stumble upon this article which helped me out on how I should establish the correct distribution of font sizes etc so I’ll be using it for making the tag cloud.

http://semanticvoid.com/blog/2006/01/06/tag-cloud-font-distribution-algorithm/

The article is pretty small but does the job

Ever thought of how the collection of tags with varying fontsizes (known as Tag Cloud) populated. As I say ‘theres an algorithm for everything’, theres an algorithm for this too. Assuming you know all about tag popularity (if not refer previous post) I’ll go ahead explaining it.

The distinct feature of tag clouds are the different groups of font sizes. Now the number of such groups desired depends entirely upon the developer. Usually having six such size-groups proves optimal.

Assume any suitable metric for measuring popularity (for instance ‘number of users using the tag’). We can always obtain the max and min numbers for the same. For example:

max(Popularity) = 130
min(Popularity) = 35

Therefore we can define one block of font-size as :
( max(Popularity) - min(Popularity) ) / 6

For the above values we get one such block range as (130 - 35) / 6 = 15.83 ~ 16
Font-sizes therefore could be bound as follows:

Range Font-Size
35 to 51 1
52 to 68 2
69 to 85 3
86 to 102 4
103 to 119 5
120 to 136 6

Update
Tonight I managed to create the tag cloud. Not only that, I turned it into a function so that it can be used for more then just the admin pages. The coding was pretty much based on the above calculations to come up with the right sizes, I used percentages to portray the font sizes as it seems more relative to the web page.

• New subtitle bit at the top, had to shave the header padding a bit more to compensate the subtitle.
• Dates are now shown on the right of each post via the calender type thing. This makes more room for category and meta bits under the header
• Changed the header a bit, didnt like the rounded edge thing so I changed it to a normal heading, juiced up the size a bit too
• Used a bit more of the random text plugin, some very subtle ones though, I’m sure you can find them quite easily.

• Managed to add some hatching effect on the top menu, slightly more web2.0 haha (i feel like i’m abusing the visual styles used in web2.0 quite alot these days)
• I really like the styles used for typo (a ruby on rails blogging software). Simple stuff like softer body text (using #666 instead of the obvious #000 or even #333) and the font being verdana helps quite alot in making the site more easier to read. I’m considering making my own skin in wordpress, it looks fun.
• I’ve applied a random text plugin which allows me to shove in the occasional random bit of text for fun, one I’m using atm is the list of words you say when you reply, it can vary from x wrote this to x said that.
• I’ve provided more contact methods to be used for contacting me, the email address will be forward to me instead of using my actual one just to make changing emails alot easier (spam and all)
• I’ve pimped up my about page , it includes a photo of me, as well as some more stuff about me
• Very subtle thing, but I’ve increased the font size of the headings on the sidebar
• Adding a bit of padding to the header thing
• Now I have a left and right class on my css, this means I can use it to float images to the left or right. Pretty useful.
• Added some extra images to jazz the site up a bit, you can see them below

You can find the above on the to do list page and the contact page
For my next blog update, I think I’ll be redesigning the theme myself, might publish it and all too!

The following changes included:

Improved the tags section

The tag section now includes a view tag page where you can view the tag and see where it’s been used. This tagging system is used alot in many web2.0 applications (including this blog) and provides users with a unique way of finding articles by tags rather then by a search engine, it’s almost like GIVING you the search terms rather then making you search it yourself

As well as a view tags php, I also managed to implement a quick tag cloud kind of style for the tags page, all that’s been done is that the query used to draw the tags include the number of times they’ve been used (via the tag links table) which means you can use that as a variable for deciding the size of the font. For now, the algorithm used is number of times used x 10 and the font size will be that (in pt units). I’ll definitely need to calculate a mean average for the tags and use that to generate a few steps of sizes (rather then a big bunch of steps). This shouldn’t be hard at all but I felt like doing other stuff before I got to keying in the algorithms, as well as that I might also include the font colour as another tag cloud factor (like my blog) This one is slightly tedious but still doable

Created the song section

Amazingly enough this was probably the easiest task I did. The songs section was used to tag songs into podcasts, this is so users can find out songs used for it and perhaps make it so each page includes a bit more detail about the song (havent looked into that one yet). The good thing about the songs section was the fact that it was almost identical to the tagging system, it was simply a tag, but with song titles. Though I did consider merging them together. It’s probably better to keep them separate in case I want to add additional fields for the songs section.

Implemented a “Feeds” section

This is where I really get into the xml/rss stuff. This section involved configuring the site to include feeds from other site, all you had to do was enter a url and it will instantly generate a page that includes the items inside the feed. I used a little small app called lastRss.php which allowed me to save time in coding the rss parsing, the api system was pretty neat so it was easy to implement what I needed, though I need to look into a bit more so I can see how I can further use it.

The limit field is probably the bit where I would actually need to look into the lastrss php a bit more, I would like to make it possible for the user to simply limit the feed to a certain amount of items, hopefully that can be done quite easily (should be done via the number of tags.

Quick podcast RSS feed

Managed to quickly knock off an RSS feed for the podcast, this used the fields on the podcast to generate most of the information, I’ve already done stuff like this before so now it’s definitely come in handly, will be using the w3c rss validator to ensure that i’ve got everything I need, not only that, I will probably need to use the podcasting standard too to ensure that it’s a valid podcast feed.

Another thing I will look into is getting feedburner to parse the feed, this tool will prove very useful for my client as he will be able to view all the subscribers to the feed. This tool has been used on most of the big sites such as Neowin which was where I initially found it