<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Foundations on vanityURLs Brand</title><link>https://brand.vanityurls.link/foundations/</link><description>Recent content in Foundations on vanityURLs Brand</description><generator>Hugo</generator><language>en-CA</language><atom:link href="https://brand.vanityurls.link/foundations/index.xml" rel="self" type="application/rss+xml"/><item><title>Common sense</title><link>https://brand.vanityurls.link/foundations/common-sense/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://brand.vanityurls.link/foundations/common-sense/</guid><description>&lt;p&gt;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.&lt;/p&gt;
&lt;h2 id="start-from-the-user-task"&gt;Start from the user task&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;If a visual idea makes that task slower, weaker, or less trustworthy, remove it.&lt;/p&gt;</description></item><item><title>Brand personality</title><link>https://brand.vanityurls.link/foundations/brand-personality/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://brand.vanityurls.link/foundations/brand-personality/</guid><description>&lt;p&gt;The vanityURLs personality is calm, precise, useful, transparent, and quietly technical.&lt;/p&gt;
&lt;h2 id="calm"&gt;Calm&lt;/h2&gt;
&lt;p&gt;The system should reduce anxiety around redirects. Use clear states, predictable layouts, and measured language. Avoid dramatic warnings unless there is a real security or availability concern.&lt;/p&gt;
&lt;h2 id="precise"&gt;Precise&lt;/h2&gt;
&lt;p&gt;Short links are small, but mistakes can be expensive. Use exact labels for domains, aliases, targets, expiration rules, languages, and blocking behavior.&lt;/p&gt;
&lt;h2 id="useful"&gt;Useful&lt;/h2&gt;
&lt;p&gt;Every visual choice should help someone scan, compare, configure, or verify. Decoration is acceptable only when it supports recognition or comprehension.&lt;/p&gt;</description></item><item><title>Voice</title><link>https://brand.vanityurls.link/foundations/voice/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://brand.vanityurls.link/foundations/voice/</guid><description>&lt;p&gt;Use direct, operational language. The reader should feel that vanityURLs is careful with redirects, clear about system behavior, and respectful of their time.&lt;/p&gt;
&lt;h2 id="voice-qualities"&gt;Voice qualities&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Quality&lt;/th&gt;
 &lt;th&gt;Means&lt;/th&gt;
 &lt;th&gt;Avoids&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;Direct&lt;/td&gt;
 &lt;td&gt;Say what the system does&lt;/td&gt;
 &lt;td&gt;Vague promises or abstract benefits&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Precise&lt;/td&gt;
 &lt;td&gt;Use exact domains, states, paths, and time&lt;/td&gt;
 &lt;td&gt;Approximate language when details matter&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Calm&lt;/td&gt;
 &lt;td&gt;Explain problems without drama&lt;/td&gt;
 &lt;td&gt;Alarmist wording for routine states&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Operational&lt;/td&gt;
 &lt;td&gt;Help the reader act or verify&lt;/td&gt;
 &lt;td&gt;Copy that sounds polished but says little&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Honest&lt;/td&gt;
 &lt;td&gt;Describe implemented behavior&lt;/td&gt;
 &lt;td&gt;Implying features or guarantees not present&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="preferred-verbs"&gt;Preferred verbs&lt;/h2&gt;
&lt;p&gt;Use concrete verbs such as &lt;code&gt;create&lt;/code&gt;, &lt;code&gt;redirect&lt;/code&gt;, &lt;code&gt;expire&lt;/code&gt;, &lt;code&gt;block&lt;/code&gt;, &lt;code&gt;audit&lt;/code&gt;, &lt;code&gt;deploy&lt;/code&gt;, &lt;code&gt;verify&lt;/code&gt;, &lt;code&gt;copy&lt;/code&gt;, &lt;code&gt;download&lt;/code&gt;, and &lt;code&gt;configure&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Naming and terms</title><link>https://brand.vanityurls.link/foundations/naming-and-terms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://brand.vanityurls.link/foundations/naming-and-terms/</guid><description>&lt;p&gt;Use consistent names so readers can tell the product, public site, brand site, and generated redirect surfaces apart.&lt;/p&gt;
&lt;h2 id="project-and-domains"&gt;Project and domains&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Name&lt;/th&gt;
 &lt;th&gt;Use&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;vanityURLs&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;The project and product name&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;vanityURLs.link&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;The public documentation and product domain&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;brand.vanityURLs.link&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;The brand standards and design-system domain&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;&lt;code&gt;v8s.link&lt;/code&gt;&lt;/td&gt;
 &lt;td&gt;Demo instance, badge examples, and compact-link examples&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;p&gt;Keep the lowercase &lt;code&gt;vanity&lt;/code&gt; and uppercase &lt;code&gt;URLs&lt;/code&gt; styling in prose. In URLs and hostnames, use the actual domain casing only when it helps recognition; DNS remains case-insensitive.&lt;/p&gt;</description></item></channel></rss>