Files
bootnode/brand
zeekay 6c49cb72ca State a version once
A version written into a manifest is written into every manifest that wants it,
which is how eslint came to exist in a hundred and four forms across this estate
and how a package came to resolve twice at run time. The catalog moves the number
out of the manifest: a manifest names the package, the workspace names the
version.

Four are held below their latest because the newer release cannot be used, and
the reason is recorded rather than the version alone: @noble/hashes 2 renamed
every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package
that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels
3 points its types condition at the bundle.
2026-08-29 13:46:56 -07:00
..
2026-08-29 13:46:56 -07:00

Bootnode Brand Guidelines

Following Hanzo ecosystem branding standards.

Logo Usage

  • Use bootnode-logo.svg for main branding
  • Minimum size: 32px height
  • Clear space: 50% of logo height on all sides

Logo Variants

  • Main: Full color with shadow and gradient
  • White: For dark backgrounds
  • Mono: Single color for monochrome uses
  • Icon: Symbol only for compact spaces

Don'ts

  • Don't stretch or distort the logo
  • Don't change colors outside approved palette
  • Don't add effects or modifications
  • Don't use on busy backgrounds without proper contrast

Color Palette

// Primary brand colors
$bootnode-primary: #372929;    // Logo background
$bootnode-white: #ffffff;      // Logo highlight  
$bootnode-gray: #d8d8d8;       // Logo gradient
$bootnode-surface: #f5f5f5;    // UI surfaces
$bootnode-text: #1a1a1a;       // Primary text
$bootnode-muted: #6b7280;      // Secondary text

Typography

  • Primary: Zen (modern, clean)
  • Monospace: Zen Mono (code, technical content)
  • Weights: 400 (normal), 500 (medium), 600 (semibold), 700 (bold)

Voice & Tone

  • Professional yet approachable
  • Technical but accessible
  • Innovative and forward-thinking
  • Reliable and trustworthy
  • Developer-focused language

Messaging

Tagline

"Blockchain Infrastructure for Developers"

Key Messages

  • Complete blockchain development platform
  • Multi-chain support out of the box
  • Enterprise-grade security and reliability
  • Developer-first experience
  • Unified Hanzo ecosystem integration

Applications

Web Applications

  • Use primary logo in header/navigation
  • Apply color palette consistently
  • Follow typography hierarchy
  • Maintain proper spacing and alignment

Documentation

  • Use mono logo for technical contexts
  • Include proper attribution
  • Link back to main platform
  • Follow established information architecture

Admin Interfaces

  • Emphasize security and professionalism
  • Use Hanzo IAM integration badges
  • Clear organizational hierarchy
  • Consistent with main platform design

Integration Standards

Hanzo Ecosystem

  • Maintain visual consistency with other Hanzo properties
  • Use unified authentication (hanzo.id, zoo.id, lux.id, pars.id)
  • Follow shared component library patterns
  • Respect cross-product user journeys

External Integrations

  • Maintain brand integrity in third-party contexts
  • Provide clear attribution and links
  • Use appropriate logo variants for different platforms
  • Follow platform-specific guidelines while preserving brand essence

For questions or brand asset requests, contact the Hanzo brand team.