-
Rn Roman Numeral Tattoos & Engravings
Which order, which separator, and how to avoid a mistake that's permanent — for anyone about to get a birthday, wedding, or anniversary date inked or engraved.
Read the guide → -
Ut UTM Tracking for Marketing Campaigns
A naming system that stops "Facebook" from splitting into three different rows in your analytics, plus the per-channel conventions that keep campaign data usable.
Read the guide → -
M5 Verifying Text & Data with MD5
How to confirm two copies of a config value, API key, or pasted string are identical — without ever putting the sensitive text itself in a chat message.
Read the guide → -
Sp Passwords That Actually Keep You Safe
Why length now beats complexity, what current guidance actually recommends, and how a long random string paired with a password manager beats a "clever" one.
Read the guide → -
Mt Mirror Text for Signage, Practice & Design
From ambulance windshields to dyslexia practice sheets — the real reasons people flip text, and how to get the mirroring right for each one.
Read the guide →
Why use-case guides, not just tool pages?
Each tool's own page explains what its options do. These guides start from the other direction: a real situation someone is actually in, and what they need to know before they act on it — often including things a converter's interface can't tell you, like which convention a tattoo artist expects, or what your analytics platform will do with a UTM value you haven't thought through.
There's a pattern across all five. In each one, the tool itself is the easy part — the conversion, the hash, the generated string is correct every time. What actually decides whether the result is right happens outside the tool: a convention someone else will read it by, a platform that will treat two spellings as two things, a constraint of the material it's going onto. That's the gap these guides are written to close.
More of these will go up as they're written. If there's a tool on the site you'd like a use-case guide for, let us know.
Who writes these guides?
They're written by the same person who builds and maintains the tools, which is why each one is specific about what its tool can and can't do — including where a tool is the wrong choice and something else should be used instead. Where a guide makes a factual claim about a standard or a platform's behaviour, it links to the primary source.
Do I need to read the guide to use the tool?
No. Every tool works on its own and every guide links straight to it. The guides exist for the decisions a tool interface can't make for you — which date order an engraver expects, which UTM value your analytics will split in two, whether a hash is appropriate for what you're checking.