logo_usage_guidelines.html

---
permalink: /logo_usage_guidelines
layout: article
title: Solid Logo Usage Guidelines
breadcrumbs:
- title: "Solid Logo Usage Guidelines"
---

<div datatype="rdf:HTML" property="description">
    <p>These guidelines are to help you when representing the Solid brand in apps, communications, content, events, projects or assets. They incorporate guidance for visual elements such as logos, colours, typography, iconography and graphic devices. There is also guidance for writing such as tone and format. These guidelines are intended for digital application.</p>
</div>

<section resource="#why_do_we_need_brand_guidelines" inlist="" rel="hasPart" class="article-section">
  <h2 id="why_do_we_need_brand_guidelines" property="name">Why do we need brand guidelines?</h2>
  <div datatype="rdf:HTML" property="description">
    <p>As a defined entity, Solid has an identity. The more consistent that identity is the easier it is to be identified and identify with. While the Solid brand may appear in a range of different places for very different purposes, by following these guidelines you will be helping to retain that consistency and build a stronger identity.</p>
  </div>
</section>

<section resource="#for_app_developers" inlist="" rel="hasPart" class="article-section">
  <h2 id="for_app_developers" property="name">For app developers</h2>
  <div datatype="rdf:HTML" property="description">
    <p>Please use these guidelines for any instances where you are looking to reference Solid. In particular, please pay notice to the guidelines on logo and colour usage as well as how to refer to Solid and its key elements in text.</p>
  </div>
</section>

<section resource="#for_event_organisers_or_communications_content_creators" inlist="" rel="hasPart" class="article-section">
  <h2 id="for_event_organisers_or_communications_content_creators" property="name">For event organisers or communications/content creators</h2>
  <div datatype="rdf:HTML" property="description">
    <p>If you are looking to create Solid communications, collateral or content please follow all aspects of these guidelines.</p>
  </div>
</section>

<section resource="#values" inlist="" rel="hasPart" class="article-section">
  <h2 id="values" property="name">Values</h2>
  <div datatype="rdf:HTML" property="description">
    <p>Solid has core values that should be embodied in everything that it represents or represents it: Interoperability, Self-determination, Equal access, Sourcing, Public Value, Connecting</p>
  </div>
</section>

<section resource="#logo" inlist="" rel="hasPart" class="article-section">
  <h2 id="logo" property="name">Logo</h2>
  <div datatype="rdf:HTML" property="description">
    <p>There is one single Solid logo with two different applications:</p>
    <p><img src="/assets/img/solid-emblem.svg" alt="Solid Logo" /></p>
    <ul>
      <li>
        <h3 id="contained">Contained</h3>
        <p>Lettermark within a solid hex shape</p>
        <p>Usage: can be used on any flat colour or overlaid on an image. Not to be used on complex patterns or in close proximity to other logos, typography or graphic elements.</p>
      </li>
      <li>
        <h3 id="outlined">Outlined</h3>
        <p>Lettermark within an outline hex shape</p>
        <p>Usage: only to be used on solid Royal Lavender (<code class="language-plaintext highlighter-rouge">#7C4DFF</code>) background. Not to be used in close proximity to other logos, typography or graphic elements.</p>
      </li>
    </ul>
  </div>
</section>

<section resource="#colour" inlist="" rel="hasPart" class="article-section">
  <h2 id="colour" property="name">Colour</h2>
  <div datatype="rdf:HTML" property="description">
    <h3 id="primary">Primary</h3>
    <p><strong>Royal Lavender</strong> - <code class="language-plaintext highlighter-rouge">#7C4DFF</code>, <code class="language-plaintext highlighter-rouge">R124 G77 B255</code> Usage: in conjunction with outlined Solid logo as a key branding element e.g. mastheads, footers and for primary CTA buttons. Not to be used as a fill within Avoid using numerous times in any one environment.</p>
    <h3 id="secondary">Secondary</h3>
    <p><strong>Geyser Grey</strong> - <code class="language-plaintext highlighter-rouge">#DAE0E6</code>, <code class="language-plaintext highlighter-rouge">R218 G224 B230</code> Usage: core functionality and signposting e.g. icons and secondary buttons/controls. Avoid use in content.</p>
    <h3 id="tertiary">Tertiary</h3>
    <p><strong>Calatina Blue</strong> - <code class="language-plaintext highlighter-rouge">#083575</code>, <code class="language-plaintext highlighter-rouge">R8 G53 B117</code> Usage: for background fills, UI functionality, dividers, illustration</p>
    <p><strong>Flamengo Pink</strong> - <code class="language-plaintext highlighter-rouge">#FF6969</code>, <code class="language-plaintext highlighter-rouge">R255 G105 B105</code> Usage: for background fills and illustration.</p>
    <h3 id="utility_colours">Utility colours</h3>
    <p><strong>Header Blue</strong> - <code class="language-plaintext highlighter-rouge">#354866</code>, <code class="language-plaintext highlighter-rouge">R53 G72 B102</code> Usage: all non header copy. Avoid using for anything else.</p>
    <p><strong>Body Grey</strong> - <code class="language-plaintext highlighter-rouge">#666666</code>, <code class="language-plaintext highlighter-rouge">R102 G102 B102</code> Usage: all non header copy. Avoid using for anything else.</p>
    <p><strong>Warning Orange</strong> - <code class="language-plaintext highlighter-rouge">#FFA600</code>, <code class="language-plaintext highlighter-rouge">R255 G166 B0</code> Usage: for warning messages only</p>
    <p><strong>Error Red</strong> - <code class="language-plaintext highlighter-rouge">#D0021B</code>, <code class="language-plaintext highlighter-rouge">R208 G2 B27</code> Usage: for error messaging only</p>
  </div>
</section>

<section resource="#typography" inlist="" rel="hasPart" class="article-section">
  <h2 id="typography" property="name">Typography</h2>
  <div datatype="rdf:HTML" property="description">
    <p>The Solid brand features two typefaces:</p>
    <p><strong>Volkhov</strong></p>
    <p>Usage: headlines, sub headlines, buttons, pull quotes</p>
    <p><strong>Neue Einstellung</strong></p>
    <p>Usage: body copy, links, controls, labels</p>
  </div>
</section>

<section resource="#iconography" inlist="" rel="hasPart" class="article-section">
  <h2 id="iconography" property="name">Iconography</h2>
  <div datatype="rdf:HTML" property="description">
    <p>Solid uses icons provided by <a href="https://fontawesome.com">Font Awesome</a>. This is not only for ease but also to ensure icons are as usable/accessible as possible.</p>
  </div>
</section>

<section resource="#gradients" inlist="" rel="hasPart" class="article-section">
  <h2 id="gradients" property="name">Gradients</h2>
  <div datatype="rdf:HTML" property="description">
    <p>Solid has one gradient which combines the Primary (Royal Lavender) and Secondary (Deep Sky Blue, Cerulean Blue) colours in equal parts (33/33/33)</p>
    <p>Usage: as a background or as an overlay to a greyscale image. It should not be used in the logo, typography, icons or graphics.</p>
  </div>
</section>

<section resource="#graphic_elements" inlist="" rel="hasPart" class="article-section">
  <h2 id="graphic_elements" property="name">Graphic elements</h2>
  <div datatype="rdf:HTML" property="description">
    <p><strong>Solid hex pattern</strong></p>
    <p>Usage: only to be used as an unbroken background fill and not to be incorporated into content or graphics.</p>
  </div>
</section>

<section resource="#written_tone" inlist="" rel="hasPart" class="article-section">
  <h2 id="written_tone" property="name">Written tone</h2>
  <div datatype="rdf:HTML" property="description">
    <p>When writing for Solid communications or content you should look to adhere to the following tone of voice principles:</p>
    <h3 id="clear">Clear</h3>
    <p>Being instantly understood by anyone, be they technically-minded or not, is fundamental to ensuring Solid meets its core values (see above). This means describing things in terms everyone will understand and avoiding jargon or ambiguous abbreviation/acronyms. Any terminology which isn't in the vocabulary of the majority of people.</p>
    <h3 id="honest">Honest</h3>
    <p>Being true to what anything is and what it delivers is key to ensuring Solid always remains genuine and trustworthy. Avoid using any embellishment or describing Solid in excessively glowing terms. Accuracy of information is also key to achieving this and the integrity of what Solid says should be protected at all times. Solid should be candid with the truth but at the same time avoid being frank or outspoken.</p>
    <h3 id="open">Open</h3>
    <p>Solid should always be welcoming and approachable in its tone and language - anyone should be made to feel like they can be part of the community. It should always be generous with what it shares and never feel like it is withholding information. Solid should avoid doctrine and being overly-directive in favour of offering guidance and advice.</p>
  </div>
</section>

<section resource="#written_format" inlist="" rel="hasPart" class="article-section">
  <h2 id="written_format" property="name">Written format</h2>
  <div datatype="rdf:HTML" property="description">
    <p><strong>Solid</strong> and <strong>Pod</strong> should always be always be capitalised and never written in all-caps.</p>
    <p><strong>WebID</strong> is semi-capitalised.</p>
    <p>General writing should always be sentence case and avoid all non-standard capitalisation. For example, 'internet' and 'web' are decapitalised.</p>
    <p>British spelling, the serial comma, and the generic 'they' is used to specify a person of unknown gender on the website copy and mailing list.</p>
  </div>
</section>