The IT Resource Center is meant to be something you can rely on. Five well-checked guides are worth more than fifty quick ones, so here's the process every guide goes through before it's published.
Every guide goes through review#
Each guide moves through these stages, and only the last one is visible to the public:
- Draft: the guide is written and its sources are collected.
- Technical review: every command, setting, version number and factual claim is checked against the official documentation listed at the end of the guide. AI tools help with drafting and with these source checks. I review the result and approve each guide before it's published. Each guide says what it applies to, and that nothing was lab-tested unless it says so.
- Editorial review: each guide is checked for clarity, tone, links and disclosures, with help from AI tools, and I approve the final wording before it's published.
- Approved: I sign off on it.
- Published.
The site's build system enforces this: a guide can't be published without recorded technical review, editorial review, and approval, with the reviewer's name and date. Published guides show their review history at the bottom.
What every guide tells you#
- Who it's for and what you need before you start.
- What it applies to: the software versions or hardware it was checked against. Instructions for one version can be wrong for another.
- When it was last reviewed, and when it's due for its next review.
- Risks: commands or changes that can delete data, cause downtime, or lock you out are marked with a warning.
- Sources: links to the official documentation it relies on.
Honesty about experience and testing#
- I don't claim hands-on testing, benchmarks, or results that didn't happen. If a guide is based on vendor documentation and general practice rather than a specific test, that's what it says.
- No made-up screenshots, statistics, testimonials, or performance numbers.
- No pretending a product is certified for something unless the manufacturer says so.
AI assistance#
AI tools help me draft guides and check them against their sources. An AI tool is never named as a reviewer. I'm responsible for everything published here, and I approve each guide.
Recommendations and affiliate links#
Some recommendation links can earn me a commission. Those links are labeled paid link, and the full rules are on the affiliate disclosure page. The short version: fit for the job comes first, every recommendation lists its limitations, and non-affiliate options are included when they're better.
Corrections and updates#
Technology changes fast. If you find a mistake or something out of date, email hello@jeremiahellington.com. Corrections are made promptly, and significant ones are noted in the guide's "Updated" date.