I do want to post the website soon, and then turn my attention to 5.6.2.
Sure. But this is something that people who aren't me can do, fairly easily. I'm hoping people will step up. (And people have already.)mikey wrote: - the game list should definitely have screenshots, maybe even 2 or 3, just to make it a bit more eye-candyish
Sure... but someone who isn't me should be the one to write that sort of page. I think I'm too close to Ren'Py to know what new users want.- the main download page for ren'py should also have a picture of how it looks like - maybe two or three as well - a shot of the demo, a shot of the menu/prefs and so on, it will definitely be more catching (since appeal is probably what we want) - also, if it's unfitting for that page, maybe a "features" subpage could do the trick:
Discover Ren'Py
- Ren'Py Games
- Features (and here, you could have loads of catchy screenshots with effects and descriptions, as well as to-the-point statements - such as "completely free", "obfuscating possible" and formats support etc.)
So Mac/Linux/Other would link people to a disambiguation page? I could see that. But do we really need to conserve the sidebar space?IMO Mac/Linux/Other Platforms should have separate pages, but not separate tabs on the sidebar - it could be called "Mac/Linux/Other" or so, and when you click on it, you'd have the option of selecting your OS from within that page, not directly from the sidebar - it's a bit confusing to have those buttins there, at least for me.
I'm not sure I'm a fan of dumbing things down that much. At the end of the day, Ren'Py is a tool, and if people can't figure out what the tutorials are, then I don't think there's much hope for them sucessfully using it.I'd also reconsider "Tutorials" and "Reference" and probably replace them with something more newbie-oriented, such as "Getting Started Tutorials (First Steps...)" and "Big Command Reference (Big Manual)" or similar. Maybe it's a bit kindergarten, but first, kindergarten is very cool, and second, to newcomers the difference between a tutorial and a reference isn't very apparent, you have to think a bit until you realize - which you shouldn't.
Although perhaps it might make sense to have a single documentation page, that would then describe the tutorials, the rm, the cookbook, and so on.
