Saturday, July 28, 2007, 11:34 AMSo what's next. Here's what I've identified as low hanging fruit that could be implemented in a few weeks:
* Replay Analyzer
* "Replay of the week" feature or "Featured Replay" feature
* New homepage
* New Guides
And of course, not so low hanging fruit:
* New UI
* User accounts
* New Forum
Thursday, July 26, 2007, 07:09 PMMaybe in the future we'll have something for everyone. Submit a quote and a rater / staff member will review and approve/disapprove.
But a peak is neat!
Wednesday, July 25, 2007, 06:40 PMUnforunately, only raters can use it. But know that I created a quote editor with my computer wizardry, and that all of you funny peoples have a chance to be immortalized on the top of the site ^_^.
Raters, check your e-mails for instructions.
Saturday, June 23, 2007, 10:06 AMI've been reading over the old suggestions forum (http://battlereports.com/suggestions_old/). It was something that I missed out on, because I knew I couldn't put the time into.
I see that a lot of initial work was done -- a requirements spec, a cvs server, a production environment (possibly, I'm not sure what its setup was).
It also set out to do a lot of things. JV ultimately saw this as part of a larger Content Publishing and Rating System, and starting from scratch rather than migrating away from the existing PHP system.
A lot could have been done, but it was probably a project doomed to failure. JV didn't have the time, and nobody else had the skills or know-how to carry it in his stead.
So now, the contrast.
This project's aim is to build a bigger community, and bring life to a very old website.
We're still going to be about battlereports, but the emphasis on replays and tournaments will be better defined. There won't be technical migration from PHP to another sort of technology. That's just too risky.
So right now I'm concentrating on re-factoring the code for maintainability. I want to remove the presentation from the logic and data flow, which should make it easier to make changes when the time comes.
And what implemented features will make this change? That I'm not too sure about. It's a group process to figure that much out, and we'll cross that bridge when we come to it.