Skip to content

DFC Bridge brand system

DFC Bridge

Use this page when naming a DFC Bridge product or choosing its mark for a site, diagram, or release. Keep the public identity consistent without renaming the stable identifiers used by the transfer contract.

  • Public name: DFC Bridge — Design Frontend Contract on first explanation; DFC Bridge thereafter.
  • Spoken shorthand: Bridge (Russian: Бридж). Do not force people to pronounce the acronym in conversation.
  • Products: DFC Bridge Assistant, DFC Bridge Explorer. Technical slugs: dfc-bridge, dfc-bridge-*.
  • Keep the six Bridge principles and the existing B mark. The rebrand changes the wordmark, not the methodology.
  • bridge, bridgeKey, [bridge-exception=…], schema IDs and published data endpoints remain stable contract identifiers, not alternate public names.
  • Historical releases retain their original names. Current links keep their working repository/Pages addresses until a coordinated external move; a repository redirect is not a Pages redirect.

The mark is built from six ordered modules:

  1. B — Breakpoints
  2. R — Roles
  3. I — Identity
  4. D — Dependencies
  5. G — Geometry
  6. E — Exceptions

The modules keep a shared rhythm while alternating between structural blocks and open-ended spans. Together they form an abstract B: one identity composed from explicit parts, readable at every size.

The mark deliberately avoids a literal bridge illustration. DFC Bridge describes a transfer contract, so the symbol expresses stable structure and continuity rather than a place or object.

Token Value Meaning
DFC Bridge Ink #1E1E1E Structure, technical truth, primary wordmark
DFC Bridge Blue #0D99FF Declared intent, active transfer path
White #FFFFFF Contrast and open space

The primary mark uses only these three colors. Product status colors such as error, warning, and draft are interface semantics and must not be introduced into the logo.

  • Use the complete color mark whenever the surface supports it.
  • Use the one-color mark for stamps, small technical diagrams, or restricted production.
  • Keep clear space equal to at least one internal module gap.
  • Minimum size: 16 × 16 px for the mark; 120 px wide for the lockup.
  • Preserve module order, spacing, corner geometry, and the alternating blue/white rhythm.
  • Do not add gradients, shadows, outlines, extra labels, or a literal bridge arch.
  • Do not use the six modules as unrelated decoration; their order carries meaning.

Canonical sources live in assets/brand:

  • dfc-bridge-mark.svg — primary square mark;
  • dfc-bridge-mark-mono.svg — one-color mark;
  • dfc-bridge-lockup-light.svg — lockup for light surfaces;
  • dfc-bridge-lockup-dark.svg — lockup for dark surfaces;
  • social-preview-1280x640.png — ready-to-upload GitHub social preview;
  • social-preview-1280x640.svg — editable social preview source.

The identity does not change the methodology grammar or validator contract. Those remain defined by the DFC Bridge documentation and rule catalog.

Zoom and scroll to read details. Esc closes.