Follow these rules to create better developer-friendly tutorials.
Your title starts with a verb, such as “build,” “create,” or “write”
Clearly describe the problem within the introduction
Share the final result, the destination of this tutorial
Break the tutorial into high level descriptive sections
Preview the high level sections in the introduction or navigation
Use numbered lists whenever explicit action steps are described
Restart numbered steps within each section—nobody wants a 27 step tutorial
Make it easy to copy-paste code for the reader
Streamline and focus your tutorial, so you aren’t covering too much
Avoid sending the reader to first complete a whole other tutorial
If the last two items conflict, do your best to make the right choice
Conclude with a helpful “next step” for learning or taking this tutorial to production
Sources: