Centralize design decisions #168
Description
I have a hard time finding information on the design of the game.
Beside this wiki page, I feel like the documentation on what the game actually is supposed to be (beside the very broad goal of being a Pokémon clone) is either non-existing or very well hidden.
In my opinion, the first step should be to have a small design document that can be easily found from the git repository. This design document should establish the following things:
- Commonalities and differences with mainline Pokémon games (already explained in the wiki page, tough I think it could be more detailed).
- Used technology and targeted platforms (C++ with SFML, etc.).
- Technical choices such as screen size, etc. This was already discussed, but I don't feel like the outcome of the discussion was recorded.
- Several mockups of the interface of the game, as Pokémon games are mostly UI-based.
- Broad outline of the progression of the player in the gamer (i.e. start in town A, go to town B, etc.).
In order to make our progress more tangible, I am also in favor of a very detailed description of, say, the first town of the game (layout, events, etc.). This way we could focus on implementing the necessary features to make this first town come alive. This would help motivate the people who contribute to the project, as this is a very concrete and (relatively) short-term goal.