Editorial standards
Gerris Corp is one consultant, so every guide, case study, and service page on this site is mine to stand behind. These are the rules I hold them to.
Experience comes first
A case study here exists because I did the work: I was hired, I ran the diagnosis or the build, and I can say exactly which parts were mine and which belonged to the client's developer or agency. Guides grow out of the same engagements. If I haven't done something with my own hands, I don't write a how-to about it.
Claims point to their source
When a guide says how Googlebot renders a page, how Bing treats a tag, what an RFC requires of a DNS record, or what a consent setting actually does, the page lists the documentation behind it under "References." The same list is published in the guide's structured data. Official documentation changes, so a reference is a starting point for your own check, not a replacement for it.
AI in the workflow, with a human at the end
I build with AI tools every day, including Claude Code, and this site's generator and many first drafts came out of that work. The rule is simple: nothing goes live until I've read it, corrected it, and verified every factual statement. Biographical details about me come from my own records and published sources I can point to, never from what a chatbot has decided about me. The build itself refuses pages that break the house rules for titles, length, duplication, and voice.
Confidentiality is part of accuracy
Clients are described by industry and problem. No names, addresses, revenue, case numbers, or private screenshots, and nothing that would let a reader work out who the client is. Ongoing and paused engagements are labeled that way. Outcomes are reported only when the evidence supports them, and "under way" is an honest status.
No one pays to be mentioned
This site carries no affiliate links, sponsored content, or paid reviews. When I name a tool, a host, or a platform, it's because I use it or a client runs on it.
Dates mean something
Every page shows its last update, and guides show both their publication and revision dates. When Google, Bing, or a standard changes in a way that affects a guide, the guide is revised and the date moves.
Found a mistake?
Email chris@gerriscorp.com with the page address and the problem. I'll check it against the source and correct the page if you're right, and note any substantive change on the page itself.
More about me
My background is on the About page, how engagements run is on Work With Me, and you can reach me through the contact page.
Updated October 6, 2026
