Guides & tutorials
Practical WordPress tutorials and tips on SEO, speed and accessibility, alongside guides for our desktop software, browser extensions and hosted tools.
ABOUT THE BLOG
Guides that assume nothing
Most guides skip the step where you were actually stuck. These walk the real screens in the order you meet them, with a screenshot of each one, so you always know you are in the right place.
WordPress is where the blog started and is still the largest part of it. Everything else we make gets the same treatment, so a desktop app, a browser extension or a hosted tool is written up to this standard rather than left to a changelog.
Every step, named
Menu paths are written out in full. No "simply navigate to the usual place".
Screenshots throughout
If a guide tells you to click something, it shows you what it looks like.
Written for beginners
Plain language at a grade 7 to 8 reading level, without ever talking down.
No filler
No thousand-word preamble before the fix. The answer always comes first.
WHAT TO EXPECT
How these WordPress tutorials are written
Each guide is written by doing the task on a clean install and photographing every screen, so the steps match what you will actually see. No filler introduction, no history lesson.
Where one of our tools does the same job faster it is mentioned once and then dropped. These WordPress tutorials have to stand up whether or not you buy anything, and so does every guide written for a desktop app, an extension or a hosted service.
QUESTIONS
About these WordPress tutorials
People running their own site who are past the install and into the awkward middle: menus, themes, images, the settings nobody explained. You do not need to write code to follow any of them, and where a guide does touch code it says exactly what to paste and where.
No. The WordPress tutorials cover WordPress itself, using the default screens, and the guides for our other tools work the same way. Where one of our products would genuinely save a step it gets mentioned once and never again, because a tutorial that turns into an advert is a bad tutorial.
Weekly, working through the questions people actually ask rather than whatever happens to rank well. Subscribing to the newsletter is the easiest way to hear about new ones without checking back, and it only goes out when something has genuinely been published. Older guides get revisited too, so a post from six months ago should still match the screens you are looking at today.
Yes, through the contact page. Requests that come up more than once move to the top of the list, because if two people asked, plenty more searched for it and did not ask.
For anything about WordPress core rather than a specific task, the official WordPress documentation is thorough and kept current. These guides exist for the places it assumes more than a beginner has.
Guides are revisited when a release actually changes a screen, rather than being left to drift. Where a step differs between versions, the guide says which version it is describing so you are not left guessing why your dashboard looks different.
Yes. They assume you can log in and nothing beyond that. Terms get defined the first time they appear, menu paths are written out in full, and every screen has a picture. If a guide loses you at a particular step, that is a fault in the guide and worth telling us about.
Please do. Sending a client a link to a step-by-step page beats writing the same explanation for the fourth time, and there is no gate, sign-up or paywall in the way of anyone you send it to. Copying the text wholesale onto your own site is the one thing we would rather you did not do, but linking, quoting and referencing are all welcome and always will be.
Yes, and on the same terms. The WordPress tutorials came first because the plugins shipped first, not because the other product lines count for less. As a desktop app, a browser extension or a hosted tool goes on sale, its guides are written the same way: one task per post, every screen photographed, and no assumption that you have read anything else first.
