|
|
|
|
|
|
by andegre
3566 days ago
|
|
|
Yes, it is my site. If this was the wrong medium, I can delete the post if I have the ability (no idea as of writing this). Regarding your feedback, THANK YOU! I like getting feedback from more technical people. Yeah, that date (format) is really annoying to look at now that you bring it up. Makes much more sense to have it like you state (5 minutes ago...). More links - I thought I had WAY too many links (been trying to figure out the SEO stuff also). Just about anywhere in the site where you see either a wrestlers name, or a school name, they are always links (except when they are in headers). I can definitely add the links in the headers, the side-effect to that is then they'll be underlined. Cool idea on the photos and links to registration sites. Be fun way to interact with each of the "events" and feel more like you were there. Thanks again for the feedback, I'll definitely work on most/all of those! |
|
|
The question you should have, as a technical matter, is why your users should care about the cache state. Do you need it at all?
You worry that there are too many links. The problem isn't that there are too many links, but that they all look the same. The links I suggested could be icons, rather than text.
On http://www.wrestlestats.com/compare/wrestler I noticed that if the weight class is not given then the names are ordered first by weigh class and second by name, so it isn't alphabetic. As a usability suggestion, pulldown menus are harder to use than selection boxes. There are only 10 weight classes, so you could arrange them as:
so people can do one click to change the class. Similarly, with the names you could have a multiple select box with rows="10" instead of a pulldown. You might also consider a side-by-side layout, because you have so much horizontal space. It would also help the balance of the page.(BTW, the prediction code has an interesting failure mode. If you use the same name for A and B then the scores always differ by 1. Shouldn't the scores be tied?)
In general, I use what's called a user-centered design approach. (Bear in mind that I'm a backend person, so I don't do this often - I'm not an expert.) Come up with about 3-5 different types of personas who might use the site; fans, players, family, coach, etc. It's a bit more specific than that, see Alan Cooper's writings and https://en.wikipedia.org/wiki/Persona_(user_experience) .
Pick the one persona you want to focus on, but keep the others in mind. Figure out what sort of things they want, and optimize for it.
For example, you have a comparison tool. There are two ways to get to a comparison, one from the tool I mentioned, another from the person's page, under "Projected Upcoming Matches". To get to that from the second one, the links are all "comparison".
If you want to optimize for that, then what about putting the prediction there instead, like "18 - 3 TF", and link that to the comparison page? (Of course, then it would be a prediction rather than a comparison, so the column header might change.)
For another example, and going back to the Twitter example, figure out for yourself the scenario where someone would use your app to find a team's Twitter handle, then see if there are ways to make it easier to use.
My one big pointer is that you should be aware that there may be no revenue to this. There used to be many ways to set up forum sites, and many small organizations would could put together specialized newsletters, and make money from specialized advertisement and membership fees. Facebook groups have sucked up most of that.