About Document Basics

About Document Basics

What is on this site

This site collects tutorials, troubleshooting guides, and practical advice for everyday tech problems—from fixing a frozen Windows update to mastering Linux commands or troubleshooting a stubborn hardware issue. Every article breaks down the kernel of a problem: what’s really happening, why it matters, and how to fix it without guesswork.

The site is organised into clear sections: Operating Systems for deep dives into Windows, Linux, and macOS; Productivity Tools for mastering software like Outlook, PowerPoint, or the Office Suite; Hardware Guides for diagnosing and repairing computers, peripherals, and networking gear; and How-To for step-by-step solutions to common frustrations.

Each guide follows the same structure so you can find what you need fast.

WhereWhat is thereGo here if
Operating SystemsIn-depth guides for Windows, Linux, and macOSyour system is slow or acting strangely
Productivity ToolsTutorials for Office Suite, Outlook, PowerPoint, and other softwareyou’re stuck on a feature or workflow
Hardware GuidesTroubleshooting for PCs, laptops, storage, and peripheralsa device isn’t working as expected
How-ToStep-by-step fixes for common tech problemsyou need a quick solution without jargon
The site’s main sections and their purpose

How to read a page here

Every page starts with a clear title and a one-sentence summary of what you’ll learn. Below that, numbered steps walk you through the solution in order, with screenshots or diagrams where needed.

Numbers like *Step 1*, *Step 2*, or *Note X* keep things linear—ignore the sidebars or footnotes on your first read unless they’re marked as essential.

Timings are given in minutes or seconds where relevant, and measurements (like file sizes or temperatures) use standard units with no ambiguity. If a guide references tools or commands, they’re listed upfront so you can skip ahead if you already have what you need.

The ‘Key Takeaways’ box at the end sums up the most critical actions—bookmark that if you’re in a hurry.

Use the table of contents on longer guides to jump to the section that matches your issue. If a step doesn’t apply to your setup, the text will say so explicitly.

And if you hit a dead end, the ‘Still Stuck?’ section at the bottom points to related guides or deeper explanations.

When it does not work

A roast that went wrong, dry and split

If a guide isn’t solving your problem, it’s usually because the symptoms match but the root cause doesn’t. Many tech issues have multiple solutions depending on your exact setup—older hardware, a specific software version, or a misconfiguration you haven’t spotted yet.

Before you give up

  • Double-check your system specs or software version against the guide’s assumptions
  • Look for ‘Also try’ or ‘If that fails’ sections—those often hold the real fix
  • Search the site for your exact error message or model number (many guides reference them)
  • Check the ‘Comments’ section at the bottom—someone may have solved your issue there

Who we are

Stanley Mancuso

This site is built by someone who still remembers the frustration of staring at a flickering green-screen monitor, wondering why a simple command wouldn’t work. The colophon below explains how the work gets done.

The colophon
Written byStanley Mancuso, who runs the site and writes most of the guides, testing every solution in a home office setup with a mix of old and new hardware
Tested inA cluttered desk with three monitors, a 2015 MacBook Pro, a Raspberry Pi cluster, and a Windows 11 VM—plus whatever gear breaks next
Written withVS Code for code snippets, Obsidian for notes, and a mechanical keyboard that’s seen too many spilled coffees
Learned fromA high school tech teacher who taught patience over speed, and a decade of fixing friends’ and family’s computers
Still getting wrongExplaining why some hardware quirks (like USB-C power delivery) work differently on every device—it’s a rabbit hole even experts avoid

The goal here isn’t to make you an expert overnight, but to give you the confidence to debug your own problems. Tech should work for you, not the other way around—and if it doesn’t, there’s usually a reason, and a way to fix it.

If you need something that is not here

If you’re looking for a topic that isn’t covered—like a niche software tool, an obscure hardware model, or a problem no one’s documented yet—start by checking the ‘Related Guides’ at the bottom of any page. If it’s truly missing, the contact page is the best place to suggest it.

We prioritise requests that explain *why* the topic matters to real users.

The guides are grouped by category: App, Coding, Operating System, Outlook, PowerPoint and Review.

Read our guides