Skip to content

Instantly share code, notes, and snippets.

@BandanaKM
Last active April 28, 2016 03:32
Show Gist options
  • Save BandanaKM/d19170aa06f75685510c5db7360d4cc4 to your computer and use it in GitHub Desktop.
Save BandanaKM/d19170aa06f75685510c5db7360d4cc4 to your computer and use it in GitHub Desktop.
sass-feedback-lesson-3-outline.md
Lession 3: Editorial Review:
Functions and Operations
This is over all good!; overall feedback is to try your best to go a layer deeper than functionality, but also get at the concept
* why are functions and operators in sass?
* why are computations useful?
* why would a conditional statement be useful
there need not be lengthy, but giving a user a reason to learn something helps them understand how it all fits together.
1. Function & Operations
One thing would do is have an exercise at the beginning to introduce the concept of functions and operation in sass.
i. What are they
ii. Why are they useful in Sass. i.e. a student may thing "I thought Sass was about design, why am I doing math in a frontend language
3. Computing can get overly technical quickly. As you continue you to write this, think about structure/organization so this info is clear to users.
5. if()
Remind users of conditionals that they have used in other languages, then give them a basic example of how it works in sass.
you can give them a simple example first, and if you want to move if(), you have full liberty to do this.
7. For loops
editorial answer: natalia, you can conceptually lay the foundation with something like
many programming languages like javascript, python, and ruby have a concept of a for loop to do X. in sass, we can use the for loop to do Y.
i would veer away from talking too much about similarities of syntax! but conceptual similarities is totally fine.
10. generalizations:
make sure you're giving users a reference at the end to review everything.
something like an index of all things they learn would be more helpful than new information. you can provide some new info, just be sure to summarize
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment