Why we write
Most tutorials stop working the moment something changes. A version bumps, a screen looks different, and you are on your own. We write ours the other way around: we build the thing first, note every step and every error, and only then publish. If it is on this site, it ran on our machines.
The HowTo Tutorials desk
Our method
How a tutorial gets made.
01
Build it first
Every guide starts as a real project. We set it up from scratch and keep going until it works end to end.
02
Write it down
Every command, every setting, every error message we hit along the way. You follow the same path we took.
03
Keep it current
Tools change. When a guide no longer matches reality, we retest it and update it, or take it down.

Plate I
№ 01
What you will find
Nine chapters,
one bookshelf.
The archive is organised into nine chapters, from web development, AI and cloud to design, video, DIY, marketing, productivity and money. Each tutorial is a numbered set of steps with the commands included, so you can follow along instead of guessing.
Browse all tutorials →


