Do not remove documentation about properties and values from last level. about flexboxfroggy HOT 12 CLOSED

+1

from flexboxfroggy.

+1

from flexboxfroggy.

I intended for the last level to be like a video game boss fight, so it is meant to be tougher than the others for sure.

But that doesn't mean I expect people to memorize all of the properties and values. I actually added a few features (which might not all be obvious) to encourage people to flip back and forth to earlier lessons as reference:

• You can hit the back and prev level buttons

• Your state is saved whenever you move to a different level

• You can hover any property name to view a tooltip reference

  

• You can click "Level n of 24" to jump directly to any level and see their completion state

  

I only did this at the end so it doesn't break the flow. My hope is the last level gives players a real sense of accomplishment for beating the game.

from flexboxfroggy.

Game state is retained, but the mental state is not... Every time i switch away I'd have to remember what it is that I'm trying to do, and since most properties are scattered across levels, and there's no clear indication which level has which property it turns into an unnecessary hunt.

Learning is not supposed to be frustrating, this is not high school :D

from flexboxfroggy.

That's fair enough. Listing all of the properties in the final level text would definitely reduce frustration, and should keep much of the challenge.

from flexboxfroggy.

I wonder if having the properties not initially shown, but showable, is a better idea. Part of what I've been looking for in a tutorial is having to memorize the names and effects of properties.

As an aside: can I just say that I really really like this tutorial?

EDIT: After completing the tutorial, I did end up writing down the elements on a piece of paper.

from flexboxfroggy.

I suggest just making a legend that shows somewhere after the property has been introduced and user can see values. I had to look this up by going back a few levels after I got to level 24. The legend for quick lookup would be really helpful

from flexboxfroggy.

I agree with @d48. Having some sort of reference that is there only if the learner needs it would be helpful. I think a popover reference would be better then a tooltip reference, as it requires more a little more work for the learner to view it and thus would encourage them not to overuse it.

from flexboxfroggy.

+1, for a newcomer like me that last level is a pain, having to go back through all different levels to access the docs.

Sure, people could search for these docs elsewhere on the Web, but people are lazy, and it's sad loosing them because of that.

Game state is retained, but the mental state is not

This so much.

from flexboxfroggy.

I appreciated the boss fight ending of the last level. It was a real challenge. Great game!

from flexboxfroggy.

Might be in the minority, but I actually liked this because it got me to go to MDN and look up the properties, like I would have in real life :)

https://developer.mozilla.org/en-US/docs/Web/CSS/flex-flow
https://developer.mozilla.org/en-US/docs/Web/CSS/flex-wrap

Maybe add a link to look up documentation instead?

from flexboxfroggy.

+1 to @cecyc

It is always valuable to make sure new devs know about MDN. w3schools be damned!

from flexboxfroggy.