Zum Hauptinhalt springen

Brand Guide

πŸ€– Generated with Claude Code

⚠️ Not yet reviewed

Co-Authored-By: Claude (noreply@anthropic.com)

Technical brand guide for TOGETHER/CCA documentation and diagrams. It is written for developers and AI agents, not for designers: the colours, logos and D2 conventions here are the ones a document or a diagram has to follow.

Contents​

Shared Assets​

The raw assets live in assets/ at the root of this repository, and are published at the site root β€” assets/colors/… is served as /colors/…:

AssetPurpose
assets/colors/_colors.d2full D2 palette β€” every diagram imports this
assets/colors/_colors-context.d2Context mode: system colours plus alternates
assets/colors/_colors-internal.d2Internal mode: hierarchy ramps plus system colours
assets/colors/_colors-analysis.d2Analysis mode: status colours plus system alternates
assets/colors/colors.cssthe same palette as CSS custom properties
assets/colors/colors.jsonmachine-readable UI colours
assets/colors/architecture.jsonarchitecture-diagram colours
assets/colors/color-tiers-preview.htmlfour-tier colour preview
assets/icons/user.svgperson icon for diagrams
assets/corporate/corporate-style-guide.pdfthe corporate rules the policy derives from

Colours in D2 diagrams​

Import the palette relatively β€” never copy it. The number of ../ follows the depth of the diagram, here from development/ci-cd/diagrams/:

...@../../../assets/colors/_colors.d2

box: "TOGETHER" {
style.fill: ${together}
}

Colours in CSS and in tooling​

@import 'assets/colors/colors.css';

.element {
background: var(--color-orange-peel);
}
import colors from './assets/colors/colors.json';
const primary = colors.categories.primary.colors['orange-peel'].base;

Where the colours come from​

ColoursSource
UI coloursgenerated from the SCSS variables in tis-cca.styleguide (npm run build:v2:colors there), then copied here
Architecture colours (kundensystem, vu, …)defined by Marketing β€” not derived from SCSS

Changing a colour therefore starts in tis-cca.styleguide, not here. See CLAUDE.md.

MDX Files​

The following files use MDX (Markdown + React components) for interactive features:

Colors (all files are MDX)​

  • colors/index.mdx - Color palette overview
  • colors/hierarchy-ramps.mdx - Tier-based color hierarchy
  • colors/analysis-mode.mdx - Analysis mode colors
  • colors/context-mode.mdx - Context mode colors

Logos (all files are MDX)​

  • logos/index.mdx - Logo overview
  • logos/boabot.mdx - BOAbot brand
  • logos/cca.mdx - CCA brand
  • logos/cca-cloudedi.mdx - CCA CloudEdi brand
  • logos/myversum.mdx - myVersUm brand
  • logos/omds-browser.mdx - OMDS Browser brand
  • logos/omdsmanager.mdx - OMDS Manager brand
  • logos/proversum.mdx - proVersUm brand
  • logos/together.mdx - TOGETHER brand
  • logos/together-cca.mdx - TOGETHER CCA brand
  • logos/togethersign.mdx - TOGETHERsign brand
  • logos/vu-logos.mdx - VU (insurance company) logos

Diagrams (icons.mdx only)​

  • diagrams/icons.mdx - Icon usage examples

All other files (.md files, .d2 templates) are pure Markdown and can be used in any context.

For AI Agents​

When creating documentation or diagrams:

  1. Start with Quick Reference for D2 syntax
  2. Import colors from assets/colors/_colors.d2 with a relative path
  3. Follow the Diagram Style Guide
  4. Use the D2 templates in diagrams/templates/ as starting points

Raw Assets over HTTP​

Assets are served from the site root, so assets/colors/… becomes /colors/….

Current β€” the dev-docs container, which requires a SAS token; see DEPLOYMENT.md:

https://tisccacdnstorage.blob.core.windows.net/dev-docs/colors/_colors.d2?<sas-token>
https://tisccacdnstorage.blob.core.windows.net/dev-docs/colors/colors.json?<sas-token>
https://tisccacdnstorage.blob.core.windows.net/dev-docs/icons/user.svg?<sas-token>

Planned, once the site moves to the public CDN:

https://cdn.togethercca.com/colors/_colors.d2
https://cdn.togethercca.com/colors/colors.json
https://cdn.togethercca.com/icons/user.svg

Local Preview​

cd site
npm run start