Editorial standards

Why there is no personal byline

Guides here are attributed to Zepe rather than to a named individual. This is worth being explicit about, because the convention on sites like this one runs the other way: a portrait, a first name, a paragraph of biography, an anecdote about the author's first PC.

When those details are real they are genuinely useful, and they are the right way to demonstrate experience. When they are invented — which, on content-farm sites, they frequently are — they are a misrepresentation of who is speaking and what they know. We would rather carry the site's name honestly than a person's name dishonestly.

How a guide is put together

1. The question comes first

Topics are chosen from what people actually search for, then rewritten into the problem behind the search. "How to reduce brightness in Windows 10" is often really "my brightness slider is missing", and a guide that only answers the first version is useless to the person asking the second. One guide owns one problem, so you are never bounced between three near-identical pages.

2. The mechanism before the steps

Before any numbered list, a guide establishes what is actually happening — which attribute, which service, which piece of firmware. This is the part that makes the steps memorable and lets you adapt when your machine does not match the screenshot.

3. Steps written to be followed, not skimmed

Commands appear in full. Menu paths are given for the versions of Windows they apply to. Where a step is destructive or reduces security, the warning sits at that step rather than in a preamble nobody reads.

4. Sourcing

Claims about how Windows behaves are grounded in primary documentation — Microsoft Learn and Microsoft Support — in preference to secondary write-ups. Every source is listed with a one-line note naming the specific claim it supports, so you can check a single point without reading the whole reference. Every cited URL is checked before publication, and any academic citation is verified against the Crossref registry rather than assumed from a title.

How we handle uncertainty

Windows behaviour varies by build, edition, OEM and management state, and some of it is not documented at all. Where that is the case a guide says so, in those words. We would rather write "this varies by manufacturer and we cannot give you a single answer" than invent a confident one.

We also flag what has stopped working. Several widely repeated methods for disabling Windows Update, for example, have been closed off by servicing changes. Listing them anyway would make an article look more thorough and cost the reader an afternoon.

Corrections

Every guide carries a "last reviewed" date, and that date changes when the content does. When we get something wrong:

• the error is fixed on the page rather than quietly deleted;
• the review date is updated, and the change is reflected in the sitemap and RSS feed;
• where a correction changes the recommendation rather than a detail, it is noted in the guide itself; and
• whoever reported it gets a reply.

Reporting an error takes one email to contact@zepe.online. Including your Windows version helps — press Win + R, type winver, and copy what the box says.

Scope and refusals

Some searches are declined. We do not publish methods for circumventing Windows activation, recovering passwords for accounts or networks you do not own, or obtaining paid software without paying. These are reliable traffic and we would rather not have it. Where a legitimate form of the question exists, that is what gets documented. The disclaimer lists this in full, along with the real risks — data loss, security trade-offs — that our guides carry.

Independence and funding

This site carries display advertising. Advertisers see no content before publication, have no input into what is written, and cannot influence a recommendation. Ad placement is decided by layout, not by which guide performs commercially.

We accept no payment for a mention, a link, or a favourable comparison. Any content that was ever paid for would be labelled as such at the top of the page, unmissably. No guide currently on this site is sponsored.

Zepe is independent of Microsoft. We link to Microsoft's documentation constantly because it is the primary source for how Windows behaves, not because of any relationship with the company. Microsoft, Windows and related names are trademarks of Microsoft Corporation.

Use of AI tools

Editorial tooling is used in producing this site, as it is at most publications now. It does not change who is accountable: every factual claim is checked against primary documentation before publication, every cited URL is verified to resolve, and errors reported to us are corrected by hand. If a guide is wrong, that is our responsibility, not a tool's.

What you can verify yourself

Rather than asking you to trust any of the above, several of these claims are checkable from where you are sitting:

• Open developer tools on any page here. You should see no cookies and no requests to any host other than zepe.online.
• Add .md to any guide's URL to read its full plain-text source, sources and all.
• Check any citation. Each one names the claim it supports, so the check is a short one.
• All 37 guides are listed at /guides and indexed in llms.txt.