Meh, I thought I would just throw this idea out - why not right, brainstorming and such. Maybe we could change the layout of the Projects/Resources boards to be more intuitive/accommodating?
- Zelda Projects
- Other Projects
- Beginner/Simple Coding
- Advanced/Complex Coding
Zelda Projects and Other Projects would also contain engines. A lot of the time when people have posted engines, they have posted them into either Zelda Projects or Other Projects boards. Instead of there being ambiguity as to if they should be in Coding or in Zelda Projects or Other Projects, let's encourage engine development. This would also ease up on the project rules with regard to story writing and game features; namely that if a project demo was not too great in terms of its story or game features, essentially this would make it like an ambiguous engine. Addtionally, as you can see I did not include Completed Projects - this is due to there just being fewer projects that meet this classification - and because from an active hobby forum standpoint, project development is more crucial than project completion.
I think Graphics/Audio should be promoted up from Resources and combined into one board, similar to Mario Fan Game Galaxy. This should not cause that much confusion given that Graphics topics outnumber Audio, it would mask the low activity of the Audio board, and it would promote creative graphic and audio works as not just being something to use in a project but being something for which creativity/effort was put into that can stand on its own right.
Things like tutorials would not need their own separate board under a scheme like this. A tutorial for a Graphics or Audio style would fit well within a development board. A tutorial for coding would essentially be coding help which would be best in a coding board. If someone had a request for a tutorial that did not exist at the current time, they could post it in Requests/Rips and if the topic is solved (meaning that a tutorial is provided), the topic could be moved to a development board accordingly.
The Requests/Rips board would allow people to still request graphics, audio, coding examples, etc. which would help them out. It would also be for rips of resources from existing games. I think that this distinction would make the board very practical and helpful to have. Additionally, and most importantly, topics in this board could be more ably managed - request topics that get completed could be locked with the solution to the request topic uploaded to the Wiki, rip topics could also be uploaded to the Wiki. There are a few benefits to this: 1) these topics are forum searchable, 2) we could keep track of commonly requested items, 3) we could promote the Wiki, 4) in promoting the Wiki, we could help upload resources to it to help avoid broken URL links.
Finally, I was thinking that Coding could be broken up into Beginner/Simple and Advanced/Complex. This might not be the most ideal division but practically it would be divided between most efforts made in Game Maker / other RAD tools, simple questions/how-tos, HTML, where to start topics --- compared to more "difficult" efforts in C/C++/etc., complicated Game Maker setup questions, etc. Well I am not too sure exactly about this but separating out C/C++/etc. efforts and/or promoting them more so they grow would be beneficial to the forum - and keeping it to where when the coding boards are more active that the simple topics didn't bog down their activity would be nice to have.