Brand
Everything needed to put our mark on a site we built, and to have a search engine or an assistant understand who built it. Copy them as they are.
Lockup
The mark is two rotationally symmetric Y-junctions. Both files are set in currentColor and take the colour of the text around them, which is why there is no light variant and no dark one.
- Lockup/brand/wordmark.svg
- Monogram and name, one file. Set in currentColor, so it takes the colour of whatever text it sits in and needs no light or dark variant.
- Monogram/brand/mark.svg
- The mark alone, for a favicon, an avatar, or a credit line where the name is already set as text.
The name is real text rather than part of an image: it is the anchor a crawler reads, and it translates, selects and scales with the rest of the footer. The monogram is inlined so nothing on the page waits on a request to our origin.
<a href="https://www.datanexus.ae/"
rel="noopener"
style="display:inline-flex;align-items:center;gap:.5em;color:inherit;text-decoration:none">
<svg viewBox="0 0 788.11 1000" width="11" height="14" fill="currentColor"
fill-rule="evenodd" aria-hidden="true" focusable="false">
<path d="M762.8 0L757.84 33.02L753.99 47.33L263.62 335.17L261.97 369.29L260.87 654.93L226.2 621.35L226.2 336.27L8.81 207.48L0 160.15L244.36 303.8ZM529.99 350.58L567.42 384.7L567.42 673.64L776 796.37L777.66 798.57L787.56 845.35L574.02 719.87L558.61 711.06L546.51 706.11L218.49 898.18L42.93 999.45L53.38 951.57L529.44 673.64Z"/>
</svg>
<span>Site by Data Nexus</span>
</a>Added to the client's own structured data, this states who built the site as an entity rather than as a string. The @id is the same node every page on this site already references, which is what lets a search engine or an assistant resolve the credit to us instead of to a name that happens to match.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebSite",
"url": "https://client.example/",
"name": "Client name",
"creator": {
"@type": "Organization",
"@id": "https://www.datanexus.ae/#organization",
"name": "Data Nexus",
"url": "https://www.datanexus.ae"
}
}
</script>If the client already publishes a WebSite node, add the creator property to it rather than shipping a second one — two nodes describing the same page is the most common way structured data stops being believed.
- One credit, in the footer
- Not on every page template as a floating badge, and never more than once on a page. A credit that repeats reads as advertising and is treated as such.
- The anchor text stays our name
- “Site by Data Nexus”, not “web design Dubai”. Keyword-rich links spread through the footers of many sites are a link scheme by Google's own definition, and the penalty lands on the client's site first.
- A nofollow is fine if the client prefers it
- It costs us nothing we were after. The value of the credit is the entity reference in the structured data, which is unaffected — so there is never a reason to argue about it with somebody's SEO consultant.
- The colour is inherited, not specified
- Both files are currentColor. Set the colour on the surrounding text and the mark follows, on a light footer or a dark one. Do not recolour the paths, and do not put the mark on a coloured plate of its own.
- Clear space and minimum size
- Leave the height of the monogram clear on every side. Below about 11px tall the two Y-junctions stop resolving and it becomes a smudge — use the name alone at that point.
- Do not redraw it
- No outlines, shadows, gradients, rotations or new lockups. If a placement needs something the two files do not cover, ask us and we will draw it.
Ask rather than redraw. A lockup we have not drawn is a lockup we cannot keep consistent.