Cloud Mist Labs

Logo in code — Cloud Mist Labs

Logo · in code.

The same brand, written ten ways.

Direction · v1

A logo a developer would feel at home with.

Each mark below treats “Cloud Mist Labs” like a code expression. Set in JetBrains Mono, ink on paper, no decoration.

code-logo-bundle/

SVGs ship with the brand kit.

Bundle available on request via press@cloudmistlabs.com until it lands in the public press kit.

Ten variations.

Each at the same size · ink & paper.

  1. 01 · Terminal

    $ cml

    For technical surfaces.

  2. 02 · Tag

    <cloud-mist-labs />

    For footer marks.

  3. 03 · Import

    import { mist }

    For dev-tooling slides.

  4. 04 · Call

    cloud.mist.labs()

    For internal docs.

  5. 05 · Object

    { cloud, mist, labs }

    For three-strata lockups.

  6. 06 · Arrow

    cloud => mist

    For transitions, decks.

  7. 07 · CSS var

    --cloud-mist-labs

    For design-system pages.

  8. 08 · Path

    /cloud/mist/labs

    For URL contexts.

  9. 09 · Comment

    // cloud · mist · labs

    For source-file headers.

  10. 10 · Strata

    cloud. mist. labs()

    For wordmark substitutes.

Pairings.

When the code-logo sits next to the mark.

Mark + terminal
$ cml
Mark + tag
<cloud-mist-labs />
Mark + path
/cloud/mist/labs
Mark + strata
cloud. mist. labs()

In headers.

The wordmark and the code-logo can coexist when context calls for it.

Cloud Mist Labs
<cloud-mist-labs />

Rules.

When the code-logo is fair game, when it isn’t.

Do
  • Use on technical surfaces — RFCs, status pages, internal docs, decks.
  • Set in JetBrains Mono, ink on paper.
  • Pair with the Stratum mark when the surface is brand-facing.
  • Match font size to surrounding mono text.
Don’t
  • Use on marketing surfaces unless context is technical.
  • Colourise — ink only. Signal only when it carries information.
  • Mix two code-logo variants in the same surface.
  • Set in any font that isn’t JetBrains Mono.