The article gives some useful tips. But (if I may) I'll disagree with a couple of small parts: > Write for beginners I prefer "write for your audience". For e

The article gives some useful tips. But (if I may) I'll disagree with a couple of small parts: > Write for beginners I prefer "write for your audience". For example, in the first lesson for my canvas library[1], I'm aiming at an audience of front-end developers - they should know how to code a very basic HTML page and start a local server to view it. Of course, my lesson fails here. I'll add a line near the top of the copy to say who the intended audience is, and a link to the MDN frontend developer course[2] for any complete beginners who (somehow) found the lesson. > Make code snippets copy/pasteable Maybe I'm an outlier but, when I blindly copy-paste code, I rarely learn about that code: it's just some magic that I feed into the computer to get results. I learn better when the tutorial forces me to type out the code (and I do nasty things in my tutorial to persuade learners to type rather than copy-paste). [1] - https://scrawl-v8.rikweb.org.uk/learn/first-lesson https://scrawl-v8.rikweb.org.uk/learn/first-lesson [2] - https://developer.mozilla.org/en-US/docs/Learn_web_development https://developer.mozilla.org/en-US/docs/Learn_web_developme...