PyWeek, the website
OK, I know there's bugs (hello, MD5 upload form, where aaare you??) and I'm working on those.I'd like to solicit some feedback though. Basically, I suck at designing websites :)
What could be improved on this site? How could the layout (both pages and the site as a whole) be improved? What pages work, what pages don't? What pages are missing? Does navigation work? How could that be improved?
Additionally, if there's any keen web developers out there who would like to help develop the site, I'd be happy to hear from you!
(log in to comment)
It would be good for discussions pertaining to a particular game, such as bugs. You'd have an easy way of finding all the relevant comments about a game, instead of having to hunt through everyone's diaries.
Greg that's a neat idea. No idea how it'd work though :)
A better way might be to have two links for each entry, one pointing to the entry as a whole that never changes, and a "Latest Comment" link that gets updated, but never expired.
That would also give you a way of going to the top of a new entry you haven't seen before, instead of getting taken to the bottom and having to scroll up to the top.
Maybe instead of a "Diary Entries" list, the list on the main page should be a "Recent Comments" list -- showing
individual comments, of either type. Sorted most recent first, so you can see what's new without having to hunt down for unvisited links (which isn't reliable at the moment anyway for the reason I pointed out earlier).
In fact, the whole thing is really wanting to be a mailing list server... or even better, an NNTP server...
I'm liking the various ideas flowing about messages. An issue I have at the moment is that I can't just post a message without having an entry (nor can anyone else) hence the admin_6 "entry". Being able to associate a message with an entry either as a "diary entry" or a comment on it (two distinct meanings) is interesting. So is threading of comments. Keep the ideas coming :)
Something I'd be interested to do is look into whether the Django scene has produced any pluggable bits I could use to either enhance or redevelop the site.
It seems there is a developing PyWeek community here, see also the discussion about Pyggy. What we should consider is what we, as a community, want in order to help this community develop further. Besides the website we have had a wiki during this PyWeek and the IRC channel sees a lot of conversation. But all these things are fairly disparate at the moment. By and large, all the projects are unconnected. People discuss each others projects briefly and in passing on the website and occasionally on IRC. Although during PyWeek itself the pressure can be quite high, so maybe people don't have much time to give conversations with other teams a great deal of attention. Is this an attitude to discourage? I'm not sure, because at the end of the day PyWeek produces some amazing games and then everyone talks about them afterwards. Anyway, the above discourse was just because I just wanted to give my thoughts on the game dev culture we're developing. So, the website: in my opinion, the system we have at the moment works, although it has limitations. It should be possible for anyone to start a thread about a particular entry, it should also be possible for anyone to start a thread about no entry at all (for over-arching discussions). Basically when a thread is started the creator should somehow say what it pertains to. I'm not a fan of complex design, especially in community projects. Something should be complex enough to be sufficient and then the community will work out how to use it, anything more and you risk dictating how it should be used.
I'll look at setting up a Google Code project this weekend. We can use that project site to discuss the site and its future.
I also have a Google App account now. If only there was some way to leverage that. LOL. Someone else has already registered a Google App with the name "pyweek"!
I agree that it would be nice to be able to post unaffiliated threads. I'd also like to have a "short" or "summary" entries page, because I don't like having to scroll to find the entry I'm looking for. It would just have a table with a row for each entry, listing just the team name and game name, maybe.
Speaking of which, I'd also like to have an official place to put my game's name, and have that show up on the listings page. It's not clear to me whether the entry name is supposed to be the team's long name or the game name. I would prefer to have both "Full team name" and "Game name" in the entry profile.
I used to get confused between the two pages pyweek.org/ and pyweek.org/6/. They're very similar except that the latter has the "Entry listings" link in the sidebar. It makes sense now, but it the first couple times I had trouble finding the entry listings page because of it.
As for what doesn't work, I wasn't able to edit my team membership after the competition started. I emailed you about it during the competition.
Also, you may edit your game's name in your entry's admin screen. It's not used much yet. Just in the new feature.
1) - I quite liked the "latest screenshot" thing that we used to have. Let you see cool things as the compo was running
@claxo: not really much point, is there? Those entries are only there unsorted for 2 weeks.
Yes, using a WYSIWYG editor would be nice. There's no way I'd ever trust data from a client though, so there'll always be some server-side filtering (as there is now) :)
@pymike: yes, that's definitely something I'd like to see.
Comments
It might also be nice to be able to start a thread not as an entry for things not so associated with your own entry, but then again maybe not.
Then we can to supply some patch for it.
I'd love to add pagination to the diary postings list (like on the front page) but I'm really unsure how to do it in a way that doesn't kill the server (given that it includes a lookup in comments for max(date_created) to figure out the last-modified date for a diary entry).
A technique that's sometimes used with those pagination-type things is to retrieve all the results on the first query and cache them, then just return the requested page from the cache on subsequent queries (until something happens to invalidate the cache).
Greg that's a neat idea. No idea how it'd work though :)
If you mean the one about attaching comments to games, there would be an "Add Comment" button on the page for each game, that anyone could use to add a comment about that game. They would be kept in a separate list accessed by a "Show Comments" button on the game's page.
But rewrite the site isn't easy joy.
Please write a document for website developer.
maybe setup a wiki for write out a TODO list.
Anyhow, if you ever decide to do it, I'm in. Maybe I could do the help section. :)
PS: Whoever registered pyweek there ... JERK!
Right now the only way to see if an entry is a team is to go a user from that team's userpage, and then see what teams they has been in...
I'd definitely help with this - but I'm a very busy right now - but maybe once the site is actually in the svn ;)
Great Job!
2) - The comments form when ranking is very small when an entry has a screenshot on my 1024x768.
3) - The all games link is cool. Seeing games by ranking is nice.
Maybe can be sorted by name before 'judgement day'?
BTW - isn't it missing some?
My bad.
Besides the graphics in my game, heres my deviant art page with some graphical examples...(most recent being the 'my site WIPS')
Click Here
For coding examples i'd have to email you some... I had to take my site done for the time being as I finish up a design for it.
Are you need to limit scope for new website design ?
:)
I like this sound.
Please setup code.google.com to hold pyweek or another version control system, let helper can see the code and support the patch.
You can approve it or not.( If you not approve the patch, please give some reason.)
milker on 2008/04/11 01:59:
Can I help?I am a django user. and have many years experience in this area.