Branding

NØDE identity guidelines and assets.

Colors

The NØDE palette is dark, grounded, and field-functional. These are exact values. Never substitute.

Charcoal #1C1C1C Primary background
Pine Green #1F3A2E Section fills, alt backgrounds
Earth Brown #5A3E2B Secondary accent
Burnt Orange #C65D1E Highlights, signal arcs — sparingly
Deep Indigo #3F1F6B Digital references — minimal
Cream #EBEBE1 Text on dark backgrounds

Never use: bright neon, glossy gradients, or white (#FFFFFF) as primary.


Typography

UI / Body — Inter

Distributed field signal network. Deploy. Test. Iterate. Transmit.

NØDE // Bold weight for headings and marks.

Code / Monospace — JetBrains Mono

40m / SSB / FT8 // K-0231 // 47 contacts

Rules:

  • NØDE always uppercase, always with zero (0)
  • No script fonts, no decorative typefaces
  • Readable at distance — test at arm’s length
  • Prefer weight and spacing over size

Core Mark

The NØDE core mark is the primary brand identifier. Use it:

  • On dark backgrounds (Charcoal, Pine Green)
  • At sufficient size — minimum 32px digital, 0.5 inch print
  • With adequate clear space (equal to the height of the zero on all sides)
  • In Cream on dark, or Charcoal reversed on light (print only)

Do not:

  • Stretch or distort the mark
  • Apply drop shadows or glows
  • Place on busy backgrounds without contrast treatment
  • Use the letter O in place of the zero

Assets


Field Patch Variant

The field patch variant is optimized for embroidery, vinyl, and reproduction at small sizes. It uses simplified geometry — no fine detail, no gradients.

Use the patch variant for:

  • Physical patches (3 inch, 2 inch)
  • Vehicle magnets
  • Stickers
  • Anything reproduced below 100px digital or 1 inch print

Sub-Mark Expansion

NØDE sub-marks follow this pattern: NØDE // [identifier]

Examples:

  • NØDE // 73 — general sign-off variant
  • NØDE // PNW — regional node variant
  • NØDE // MESH — mesh operations variant
  • NØDE // SOTA — summit activation variant

Rules:

  • Identifier is always uppercase
  • Separator is always // (space, double slash, space)
  • Sub-marks use the same typography and color rules as the core mark
  • Do not invent sub-marks without field justification

Brand Test

Apply before any output — design, copy, or code:

— Does this feel competent?

— Would this look good on a Pelican case?

— Would this still look clean in 5 years?

— Does this avoid ego?

— Does this reflect field capability?

If no to any of these — rethink it.