Today I interviewed for a job as webmaster for the UBCO Phoenix. Its an university newspaper, published bi-weekly.

They’re an interesting group, pretty fun. All macs in the office, something else to note. It seems like creative groups always use macs, but thats aside from the point.

They want a webmaster, because, to put it plainly, their website is boring. Also, their was a bit of work involved in posting each story.

What they want is a rebuilt website that changes both of those, and I offered a few ideas. Of all print publications, a student newspaper can try new things out, new methods, new ways of news and interacting with their readers.

They also have the benefit that they’re writing for the new generation of movers and shakers. This audience, aged 18-24, are the people that put Facebook and Myspace on the map. Okay, I grant that that doesn’t mean too much in a sense, but it also means that these people love interaction. They love media. And a student newspaper can provide a new angle on news gathering and interaction.

They(the editors of the Phoenix) discussed an issue about how, due to their bi-weekly schedule, they get submissions that they just can’t publish. It would be too late, or too early, or just not right. A good website could change that. One thing thats annoyed me, is how news will publish stories, but there are no updates, no follow-ups, no linking together. Its still them pushing the news, what they decide as news, to us.

I do have to point out the one exception to this generality, CBC news. (I think its them, correct me if I’m wrong) They have a tag cloud, linking relevant news stories together. That is quite cool, and very very useful. What a tag cloud does, is that it takes the tags people place on the stories, and you can check out other stories with similar tags. Take for example, “Iraq”. You’d be able to see all the articles tagged with “Iraq” as well as common tags on those articles. Those tags are seen as being related, say, “US Foreign Policy” as an example.

The ideas I threw out for their website were as follows: staff blogs, forums, and online-only articles, on timely and relevant news. Say for example, the recent cougar sightings.

And here’s the best idea: individualized filters, ratings for each articles that contribute to your personal filter, which will contribute to feedback to the staff members on which stories were liked, and weren’t liked. Ones that people wanna hear more about will be rated higher, and the news staff can see this, and this is big: tailor their stories to satisfy this demand.

Those are my ideas for their website, and hopefully I get the job, despite the low pay. It will be a very interesting experience, will look good on a resume, and give me much needed experience.

A current project of mine, aside from pesky schoolwork, is an rpg, with my best friend, Ruby. The first tool we need is a map making tool, which is in the progress. See, with our own map making tool, we could add the features /we/ wanted to it.

This brings an interesting problem to the table, however. How do you deal with asset management on a large scale? Particularly, for people that may not be that techologically adept. Of course, Ruby has no problem in that arena. For an rpg, even one as short as the one we plan, there will still be hundreds, if not thousands of images, music files, animations, map files, everything.

For the map maker then, it would need to, behind the scenes at least, manage the assets for the user, namely Ruby. When the user saves a map file, the assets used would be moved into their own folders, along the lines of “Animations” for the animation files, “Tiles” for the tiles, “BigTiles” for the big tiles, etc. Now, these folders will be invisible, and will sit in the same directory where the map file is saved.

The best part is this: the map file will also list the last known locations for the original assets, and if they’ve changed, will add them to the folders. As well, it will back up the old versions, by creating diffs of the files. So, the user can, and most likely will need to revert their files. Lo and behold, backups have been done for them!

This is kind of sneaking around the primary issue, I admit. Sneaking in primitive source control, but when you get them started on something small, and they find it useful, its easier to suggest a bigger solution. Like, say, actual source control.

Then again, adding in such functionality is kind of bigger than what is needed out of the application, and I’m still trying to decide what to do.

Any suggestions, give me a shout in the comments.