Skip to content
View DESIGN.md ↓
Atlas collected source screenshot
Northline Interconnect — Style Reference · Source preview ↗

Northline Interconnect — Style Reference

A black, white, and orange B2B connector-sourcing portal with hard-edge grids and deliberate white space.

The visual direction translates a black, white, and orange editorial interface into an original B2B path for connectors, terminals, and accessories: orient by interconnect family → describe application and supply requirements → prepare an RFQ. It is a high-effort industry adaptation. Northline Interconnect is an invented name; all copy, CSS geometry, and interface patterns here are original. It does not reproduce any source identity, code, image, people, metrics, case studies, commercial terms, or claims.

https://bootstrapmade.com

Color Palette

Implementation tokens for this adaptation; use the foreground/background pairs specified in DESIGN.md.

Reference colors

Typography

Font sizes and roles follow the delivered implementation. Check the font-provider requirements in Quick Start before production use.

Type Scale

  1. hero92px · 700 · .92
  2. section42px · 700 · 1
  3. card22px · 700 · 1.05
  4. lead20px · 400 · 1.5
  5. body16px · 400 · 1.6
  6. label13px · 800 · 1.35
  7. caption12px · 700 · 1.4

Fonts

Font family
Weights
700 · 800 · 400
Sizes
12–20px · 4 values
Line heights
1.35–1.6 · 4 values
Fallback
Arial, sans-serif

caption / label / body / lead

Font family
Weights
700
Sizes
22–92px · 3 values
Line heights
0.92–1.05 · 3 values
Fallback
Arial, sans-serif

card / section / hero

Spacing & Shape

Spacing

PurposeValuePreview
Density
Base unit
Page shell
Hero
Phone

Border Radius

PurposeValuePreview
cards
controls
panels
Full spacing scale
  • 1 --space-1
  • 2 --space-2
  • 3 --space-3
  • 4 --space-4
  • 5 --space-5
  • 6 --space-6
  • section --space-section

Guidelines

Do

  • Use orange for actions, rules, sequence cues, and focal geometry.
  • Keep the B2B journey at interconnect-family orientation, application context, supply questions, then RFQ preparation.
  • Use original CSS shapes and approved project assets only.
  • Preserve visible keyboard focus, labels, errors, and reduced-motion behavior.

Don't

  • Do not turn the technical procurement journey into a direct consumer transaction.
  • Do not reuse source logos, HTML, CSS, photography, people, metrics, commercial terms, or case studies.
  • Do not present generic series labels as SKU, stock, certification, test, compatibility, delivery, or performance facts.
  • Do not imply that the local form sends, saves, or submits information.

We use only necessary browser storage to remember privacy preferences and support core site functions.