Created
April 28, 2016 04:24
-
-
Save BandanaKM/2b61668478d6e222b37e37e4dd983849 to your computer and use it in GitHub Desktop.
sass-feedback-lesson1-sketches
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lesson 1: Editorial Review | |
Nice, overall wonderful. Below are mostly the points I would change! | |
1. | |
I like this intro , and I like being able to see CSS and Sass side by size. Just make sure that the users eye knows where to go as they compar (I think you have that anyways!) | |
2. Great. Explain all these concepts, mixins, placeholders and nesting. | |
Important part in your explanation is that you don't go too deep into technical jargon, but explain in a simple way what they are. | |
For the instructions, tell the users to look for one or two specific things. "Analyze" may be too broad for them. | |
3. Great | |
For the instructions, write: | |
In the terminal, compile the input sass to css | |
6. Maybe there's a good way of representing this information in a chart or a table. That way you ca have users look at the table to see the example. | |
In the text, you can use simple words to describe what the idea is conceptually, and have the examples in the chart | |
You also have the option of breaking this exercise up into two exercises= | |
sass(y) types i | |
* colors | |
* numbers | |
* strings | |
* booleans | |
* null | |
instruct users to try 2 of the more complicate ones (colors, numbers?) | |
sass(y) types ii | |
* lists | |
* maps | |
that also helps pace the learner, and in both examples you can have a chart. 7 types may be a lot at once to soak in | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment