Common sense

Practical rules for making brand decisions when the exact answer is not documented.

Brand standards should make everyday decisions easier. When a page, badge, redirect screen, or product surface does not have a specific rule, use these common-sense defaults.

Start from the user task

Every surface should help someone do one clear thing: understand a redirect, trust a destination, copy an asset, manage an instance, or learn the system.

If a visual idea makes that task slower, weaker, or less trustworthy, remove it.

Keep the system honest

• Describe what the product actually does.
• Do not imply analytics, attribution, security guarantees, or uptime promises that are not implemented.
• Show redirects, aliases, blocked targets, and generated pages in plain language.
• Use exact names, paths, dates, and domains when they matter.

Prefer useful restraint

vanityURLs should feel engineered, not decorated. Use brand expression to clarify structure, highlight state, and make assets recognizable.

Avoid ornamental effects that make the system look less durable: excessive gradients, oversized cards, novelty type, vague illustrations, and purely atmospheric imagery.

Write like an operator can act

Good copy answers: What is this? What changed? What should I do next?

Use concrete verbs such as create, redirect, expire, block, audit, deploy, download, and verify. Avoid marketing shorthand when an operational sentence would be clearer.

Make defaults accessible

The accessible option is the default option. Preserve contrast, focus states, readable line length, keyboard navigation, and meaningful link text before adding brand flourish.

Leave space for localization

Badges, redirect pages, and documentation need room for longer translated text. Design with flexible widths, stable layouts, and language-neutral iconography.