Having taught small groups of children HTML, CSS, and JS as holiday programmes, my thoughts are:

• be aware that many parents send their kids to classes for one or both of these reasons:
  • to babysit them
  • to "enrich" the children in something the children are not really interested in.
• If young students (< 12) are not interested, you can get them about as far as understanding that there are bits of the code they can change that will change messages or backgrounds. If older students are not interested, they will get more out of it, but you will have to focus more on "making it cool" than understanding concepts.
• Whether or not there is a good level of interest, the children will at times be bored, tired, or some will be behind and others ahead. You need to have some easy and fun distractions/topic changes, or ways to keep the fast ones busy, and look for signs that students are losing the ability to concentrate. At this point it is unlikely to re-invigorate them with some whiz-bang, they either need a break or have reached their limits for the day. (So you need activities they will enjoy that don't require concentration.)
• In the 5-10 age range there is a mixed bag of typing skills. Some students are very slow or struggle to recognise special characters. (So, Scratch. Or GameFroot)
• I would say that age is much less important than age range. If you have everything from 5 to 15 year olds, you are not teaching them all the same thing, even if they are all doing the same activity. If the students are of a similar age, you can teach concepts appropriate for that age without trouble and be aware of who is falling behind.
• Parents and children should be OK; the parents expect that the content is at a level the children will understand. But children and adults is not good, because the children slow things down so much. However 15+ is fine, and 12+ is probably OK, especially if they are interested.

Having taught small groups of children HTML, CSS, and JS as holiday programs, my thoughts are:

• be aware that many parents send their kids to classes for one or both of these reasons:
  • to babysit them
  • to "enrich" the children in something the children are not really interested in.
• If young students (< 12) are not interested, you can get them about as far as understanding that there are bits of the code they can change that will change messages or backgrounds. If older students are not interested, they will get more out of it, but you will have to focus more on "making it cool" than understanding concepts.
• Whether or not there is a good level of interest, the children will at times be bored, tired, or some will be behind and others ahead. You need to have some easy and fun distractions/topic changes, or ways to keep the fast ones busy and look for signs that students are losing the ability to concentrate. At this point it is unlikely to re-invigorate them with some whiz-bang, they either need a break or have reached their limits for the day. (So you need activities they will enjoy that don't require concentration.)
• In the 5-10 age range there is a mixed bag of typing skills. Some students are very slow or struggle to recognize special characters. (So, Scratch. Or GameFroot)
• I would say that age is much less important than age range. If you have everything from 5 to 15-year-olds, you are not teaching them all the same thing, even if they are all doing the same activity. If the students are of a similar age, you can teach concepts appropriate for that age without trouble and be aware of who is falling behind.
• Parents and children should be OK; the parents expect that the content is at a level the children will understand. But children and adults are not good, because the children slow things down so much. However 15+ is fine, and 12+ is probably OK, especially if they are interested.