What oinksoft said. I think it's a common mistake of people who want to teach anything, but I see it frequently in coding (probably because that is what I am t

What oinksoft said. I think it's a common mistake of people who want to teach anything, but I see it frequently in coding (probably because that is what I am trying to learn these days). That problem is usually articulate with this phrase: "Before you get started..." Essentially, when I look for a beginner's guide, I want to start at the beginning. There is nothing before the beginning. If I need to plug something in, turn something on, or install something, I'd like to know how to do that. I exaggerate only slightly. For example, when I was learning to play the piano as a child, I started centered on the first note I played, which was a G, and arranged myself accordingly to accommodate my chosen midpoint, since no one had taught me about Middle C. Oinksoft's points are all crucial. You're clearly knowledgeable, but those details are beyond the scope of my understanding for a Level 0 beginner, so if they are essential, they need to be broken down. If they aren't, then you can leave them out. As a general rule for teaching anything, you should explain, demonstrate, and then solicit a student response or reproduction of the concept. I think the material you have here can be arranged such that it accomplishes these components, and rearranging it thus would make it easier for someone ignorant of the subject, like myself, to follow along. I hope this is helpful criticism. I really like what you're doing and I'm excited by your attitude – 'basics to ninja' – because this is useful for preventing learners from stagnating. With some work on the beginner level information, I think you'll have a solid guide.