Feature Request(s) / Feedback

[lukeminall]

I just completed the game and it is very informative. I like how the challenges get progressively more difficult, while maintaining the option for help with the hovers, you really did a good job of it!

The thing with learning something new is that there is no way of remembering this stuff without repetition & at the end of the game, the user is told that they have done well and are sent on their way, my first feature request would be a cheat-sheet that they can download, to help them remember what they have learned.

It would be good if the contributors could make one that is frog themed. Or, with the authors permissions, we could add links to an existing cheat-sheet such as one of the following:

• https://css-tricks.com/snippets/css/a-guide-to-flexbox/
• http://jonibologna.com/flexbox-cheatsheet/
• http://yoksel.github.io/flex-cheatsheet/

Secondly, even if the user gets the correct answer they may not understand the logic, that is why websites such as Code Academy and Udacity have answer text / videos respectively, to explain the logic behind the answer.

Maybe you could have an explanation of the answer shown once the user has answered correctly, just to walk them though the logic.

I realise that I have touched on a lot of points here & I would quite happily be a contributor to your project, I'm just putting my thoughts on the table.

[thomaspark]

Hey @ocelotluke, thanks for your thoughtful suggestions. I'm very open to the idea of providing supplemental materials, which could take many different forms.

The GitHub wiki might be a good way to collaborate on this. Pages can be created for per-level explanations as well as a cheat sheet that explains in more detail the different properties/values, and also links to additional resources. And then we could link back from Froggy to the individual wiki pages where relevant. Downside of this is that when Froggy is used as a class activity, students can just copy & paste answers from the wiki instead of working through it.

Or we could have the explanations more deeply integrated with the game. Make full explanations only available when a level is completed.

I have gotten notes from people that they use Froggy as an interactive reference. They go back to specific levels and experiment with different values to get a better grasp on a certain property. Maybe if the levels had descriptions (e.g., hover over a number in the level menu to get a tooltip of its topic), it could help this use case.