Writing a tutorial really depends on how in-depth you want them to be. Of course, being in-depth is very helpful, especially for those who were just starting out or simply having a hard time understanding. Screenshots help a lot, and if you're writing a coding tutorial, code snippets and code blocks really help.
I like being in-depth because when I write my tutorials, it's the same as me taking notes and writing what I understood from the lessons I've learned.
There really isn't a "set" format for a good tutorial, because that all depends on how you want to approach it. I could give you a few tips with them though. But first, ask yourself (some of) these questions:
- To whom you are aiming this tutorial for? Beginners? People with a bit of experience? Professionals who are just learning something new?
- When you learn how to do this for the first time, what part of the learning process you went through that helped you? Would you do the same/incorporate it in your tutorial?
- Will it be easier for you to create videos or post screenshots of your tutorials for those who don't really like reading oodles and oodles amount of text?
- Should I just write notes and post screenshots or other visuals like code blocks? Or should I just create a "let's build together" style of tutorial, where we have one project sample and we recreate that sample into a completed project?
Next, gather your materials and your sources. Then write a quick outline on how you're going to present your tutorial in steps. And then, write a few rough drafts of sort and maybe have another person take a look at your drafts and have them give you feedback. After you finally decided on how you want your format would be, just write them out, use the incorporated visuals when you need, and when you're done, have another peer feedback, and when everything's finalized, just post them up.
Well, that's how I do my tutorials. Others ( @Mikari ?) may create them a little differently.