---
name: ringier-global-brand
description: Brand guidelines for Ringier AG (global corporate brand). Use for branded presentations, reports, documents, logos, colors, typography, and corporate communications across all Ringier markets.
---

# Ringier AG Brand Identity Guidelines

## Overview

This skill provides comprehensive brand identity guidelines for **Ringier AG**, the global corporate brand. Use this guidance when creating presentations, reports, documents, websites, or any branded materials representing Ringier at the corporate level.

**Scope**: Logo usage, color systems, typography, layout principles, spacing, messaging, and brand application across media.

**How to use**: Quick reference for common needs; load `references/` files for deep specs.

---

## Quick Brand Reference

### Color Palette

**Ringier Primary Colors**:
- **Magenta**: `#e6007e` (RGB: 230, 0, 126 | CMYK: 0, 100, 0, 0 | Pantone: Magenta)
- **Yellow**: `#ffde14` (RGB: 255, 222, 20 | CMYK: 0, 10, 90, 0 | Pantone: 108 U/C)
- **Cyan**: `#009fe3` (RGB: 0, 159, 227 | CMYK: 100, 0, 0, 0 | Pantone: Cyan)
- **Black**: `#000000` | **Light Gray**: `#f6f6f6`

**Ringier Secondary Colors** (for extended palette needs):
Marine `#162d46`, Lilac `#bc93c4`, Sea `#4e81a3`, Turquoise `#31b6b3`, Coral `#ff6b6b`, Tangerine `#f29331`, Lime `#d5de5b`

> **Data Visualization Rule**: When creating charts, infographics, dashboards, diagrams, data tables, maps, or any multi-series visual, **use primary colors (Magenta, Yellow, Cyan) for 1-3 data series**. For 4+ series, switch to a **single-color tint approach** (e.g., Magenta at 100%, 75%, 50%, 25%). On white backgrounds, prefer tints unless there are 3 or fewer data fields. See full guidelines below.

For detailed color usage, CMYK values, tints (75%/50%/25%), and accessibility guidelines: See `references/color-usage.md`

### Logo System

#### Ringier Logo Selection Quick Guide

**Three logo types**:
1. **Standard logo** — Full-colour (rings + logotype), white backgrounds only
2. **Flag logo** — Self-contained flag element (white rectangle + coloured triangle + logo), for **all non-white backgrounds** (the primary branding method)
3. **Monochrome logo** — All-black or all-white, for single-colour printing or simplified contexts on clean solid backgrounds only

**Decision Tree**:

1. **Background = White?**
   - Yes → Use standard logo → `references/assets/ringier/source/standard/Ringier_RGB.svg`
   - No → Use flag logo (see step 2)

2. **Background = Coloured or Photo?**
   - Magenta bg → Cyan flag or Yellow flag → `references/assets/ringier/source/flag/Ringier_FlagC_RGB.svg` or `Ringier_FlagY_RGB.svg`
   - Cyan bg → Magenta flag or Yellow flag → `flag/Ringier_FlagM_RGB.svg` or `Ringier_FlagY_RGB.svg`
   - Yellow bg → Magenta flag (preferred) → `flag/Ringier_FlagM_RGB.svg`
   - Marine/Black bg → Magenta flag → `flag/Ringier_FlagM_RGB.svg`
   - Photo/Busy → Flag logo with best contrast against dominant tones

3. **Format Type?**
   - HTML → **Always use SVG** (scales perfectly, smallest file size, crisp on all screens)
   - Digital (non-HTML) → SVG preferred, PNG fallback

All asset paths relative to `references/assets/ringier/source/`.

#### Logo Do Nots

**Standard Logo Rules**:
- Do not use the standard logo on backgrounds other than white or very light colours
- Do not add effects to the logo (shadows, gradients, outlines, glows)
- Do not distort, stretch, or rotate the logo
- Do not use the logo vertically — always horizontal

**Flag Logo Rules**:
- Do not use the flag logo on white backgrounds — use the standard logo instead
- Do not use the same flag colour as the page background (must always contrast)
- Do not place the standard logo on primary colour backgrounds — use the flag logo instead
- Flag logo placement: always bottom-right corner, touching both edges

**Monochrome Logo Rules**:
- Do not use monochrome (all-black or all-white) logo versions on images, busy backgrounds, or on the flag — monochrome is only for single-colour printing or simplified contexts on clean, solid backgrounds

**General Logo Rules**:
- Do not use logo with old claim attached — claim is always a separate element
- Do not violate the protected area around the logo (height of 'R' for standard, height of triangle for flag)
- Do not recreate or modify the logo — always use official files
- Do not cut off logos with elements of design or text — full logo must always be visible with clear space
- Do not alter logo colours to suit backgrounds — select the correct version instead
- **Do not place more than one logo on a single page/slide** — one logo per page is the rule
- **Do not fabricate, generate, or improvise brand graphics** (e.g., drawing circles to represent the Ringier rings, creating ring illustrations, or inventing decorative elements that mimic brand assets). Only use the official logo files provided in `references/assets/` and `snippets/`. If an asset does not exist as a provided file, do not create a substitute

For complete logo rules, sizing, protected areas, and anti-patterns: See `references/logo-usage.md` and `references/assets/README.md`

### Typography

**Primary Fonts**:
- **Headlines/Display**: Libre Bodoni Std 1 Bold (use at **-40 tracking**, CSS: `letter-spacing: -0.04em`)
- **Body Text**: Ringier Book (regular weight)
- **Emphasis**: Ringier Bold

**Headline tracking is non-negotiable**: The default tracking on Bodoni is too loose and breaks the brand appearance. Every Bodoni headline element must use -40 tracking (`letter-spacing: -0.04em` in CSS). A common mistake is using `-0.02em` — this is wrong and visually too loose.

**Headline style rules**:
- Do not use italic on headline text (`font-style: italic` on headline elements is off-brand). If a word needs visual distinction within a headline, use colour (e.g. magenta `#e6007e`) rather than italic.
- Headlines use **Bold** weight only — never italic, never light.

**Bodoni Moda optical sizing override** (non-negotiable when Bodoni Moda is used): Bodoni Moda has a variable font optical size axis (`opsz`) that makes hairline strokes too thin at display sizes, especially on projectors or lower-res screens. All Bodoni Moda headline/display elements must set:
```css
font-optical-sizing: none;
font-variation-settings: 'opsz' 26;
```

**Fallback Fonts** (3-tier system, use only when primary fonts unavailable):
- **Tier 2 (Google Fonts)**: Bodoni Moda Bold (headlines, at -40 tracking / `letter-spacing: -0.04em`, with optical sizing override above), Lato Light/Regular/Bold (body)
- **Tier 3 (System-Safe)**: Georgia Bold (headlines), Helvetica Neue family (body)
- **Warning**: When fallback fonts are used, flag this to the user (visual weight and metrics will differ)

**Web/HTML Font Stack for Headlines**: Use `@font-face` with multiple `local()` name variants to resolve the installed Libre Bodoni Std 1 Bold, falling back to Bodoni Moda (Google Fonts), then Georgia. See `references/typography.md` for the full `@font-face` declaration.

**Font Color Rules**:
- **Black `#000000` text on light backgrounds** (white, yellow, light gray) — do not use marine `#162d46` for headings on light backgrounds; marine passes contrast ratios but is visually softer than black for a serif headline, especially in projection environments
- White text on dark backgrounds (magenta, cyan, black, photos)

**Signature Style**: Colored periods at end of key statements (use contrasting primary color)

For complete typography specs, sizing, line spacing, and hierarchy: See `references/typography.md`

---

## Design Principles

### 1. Consistency with Flexibility

**Core elements that must remain consistent**:
- Logo usage rules (flag placement, protected areas, no alterations)
- Color palette (exact hex/CMYK values)
- Typography (Bauer Bodoni for headlines, Ringier for body)
- Rounded corners (5mm radius on frames, signature style element)

**Elements with flexibility**:
- Layout and composition (calm ↔ expressive range)
- Graphics scale (smaller/subdued ↔ large/bold)
- Image selection (within imagery guidelines)
- Use of secondary colors (for variety in presentations, charts)

### 2. Calm-Expressive Range

Ringier's brand identity exists on a spectrum:

**Calm** (formal, corporate, toned-down):
- White backgrounds dominate
- Smaller or minimal graphics
- More negative space
- Standard logo (never flag on white backgrounds)
- Black text on white
- *Use for*: Annual reports, investor presentations, legal documents

**Expressive** (dynamic, engaging, eye-catching):
- Colored backgrounds (magenta, cyan, yellow)
- Large graphics (connected rings, bold imagery)
- Layered compositions
- Flag logos on every page
- White text on color
- *Use for*: Marketing presentations, event materials, social media

**Most materials fall in the middle**: Mix of white and colored pages, balanced graphics, flag logos on colored pages only.

### 3. Accessibility

- Ensure sufficient contrast (black on yellow, white on magenta/cyan)
- Never place standard logo on colored backgrounds (fails contrast)
- Test color combinations for color-blind users (avoid red-green reliance)
- Use tints (75%, 50%, 25%) to create hierarchy without introducing new colors

### 4. Medium-Specific Guidance

**HTML / Web**:
- **Always use SVG** — preferred format for all HTML output (scalable, crisp, small file size)
- Use inline SVG elements from `snippets/` for embedded logos
- RGB colour space

**Digital (presentations, screens)**:
- SVG preferred, PNG fallback
- RGB colour space
- Flag logo sizing: 154px wide for 1920x1080px, 216px for 1080x1080px

---

## Common Use Cases

### Use Case 1: Create a Ringier Presentation Slide

**Quick workflow**:

1. **Choose background**: White (calm) or coloured (expressive)
2. **Place logo**:
   - White background: Standard logo (`snippets/standard-logo.html`) — flexible position (top-left, centered, or bottom-right)
   - Coloured background: Flag logo bottom-right — read the matching snippet from `snippets/flag-logo-[cyan|magenta|yellow].html`
3. **Add headline**: Libre Bodoni Std 1 Bold, 55-115pt, -40 tracking (`letter-spacing: -0.04em`), stack words for impact
4. **Add body text**: Ringier Book, 15pt, 20pt line spacing
5. **Add visual element**: Connected rings (cropped/scaled), rounded-corner image, or chart
6. **Apply coloured period**: End headline with coloured period (contrasting colour)

**Example text**:
```
Technology. (with yellow period on cyan background)
Marketplaces. (with cyan period on magenta background)
We are Ringier. (with magenta period on white background)
```

### Use Case 2: Create a Report Header

**Quick workflow**:

1. **Format**: A4 portrait (210mm x 297mm)
2. **Logo**: Standard Ringier logo, top-left or centered, protected area = height of 'R'
3. **Title**: Libre Bodoni Std 1 Bold, 55-80pt, -40 tracking (`letter-spacing: -0.04em`), highlight key word by making it larger
4. **Date/Subtitle**: Ringier Book, 15pt
5. **Frame element** (optional): Rounded rectangle (5mm radius, 0.75pt stroke) to highlight content
6. **Color accent**: Use tint of primary color for subtle visual interest

**Margins**: Maintain protected area around logo, generous whitespace

### Use Case 3: Select Logo for Specific Context

See the Logo Selection Decision Tree above, or `references/assets/README.md` for the full inventory.

### Use Case 4: Create Branded Social Media Graphics

**Quick workflow**:

1. **Format**: Square (1080x1080px) or story (1080x1920px)
2. **Logo**: Ringier flag logo, bottom-right corner
3. **Typography**: Bauer Bodoni for short statements, white text on photo
4. **White space**: Let content breathe — don't fill every pixel

**Flexibility**: Social media allows more creative expression within brand guardrails

**Social Media Content Options** (from Ringier Style Guide):

1. **Unbranded** — Image or typographical composition on its own (no logo). Use when the content speaks for itself.
2. **Flag logo on photo** — Use only when appropriate and when image rights allow. Flag logo placed bottom-right.
3. **Dynamic rings on background** — 3D connected rings placed on photography or solid colored backgrounds. Creates strong brand recognition.
4. **Claim on background** — "We inform. We entertain. We connect." placed on photography or colored backgrounds. Strong corporate messaging.

These four options can be mixed flexibly across social channels for variety and brand consistency.

**Social Media Format Sizes**:
- **Square post**: 1080x1080px (margins: 80px all sides)
- **Flag logo sizing**: Use the sizes specified in the logo section (216px flag width for 1080x1080px)

---

## Progressive Disclosure Guide

This main file provides quick reference for 80% of common needs. For detailed specifications, see:

### Reference Files (Detailed Specs)

- **`references/color-system.json`**: Machine-readable color data (hex, RGB, CMYK, Pantone, usage metadata)
- **`references/color-usage.md`**: Color psychology, combinations, tints, accessibility, print vs digital
- **`references/typography.md`**: Complete font specs, sizing, line spacing, tracking, hierarchy, fallbacks
- **`references/logo-usage.md`**: Logo selection matrix, sizing formulas, protected areas, flag logo rules, don'ts
- **`references/spacing-layout.md`**: Grid systems, spacing scale (5mm/0.75pt), DIN A4 proportions, alignment
- **`references/messaging-tone.md`**: Brand voice, claim usage, approved copy
- **`references/stationery.md`**: Letterhead, business card, and envelope specifications

### Examples (HTML Templates)

- **`examples/letterhead.html`**: Complete A4 letterhead with inline SVG logo, content zones, and placeholder text
- **`examples/business-card.html`**: 85mm x 55mm business card with two-zone layout and placeholder contacts

> Use these as starting points for stationery generation — they have correct logos, fonts, margins, and layout already wired up. Read and adapt rather than building from scratch.

> **When generating HTML, always read and embed snippets from `snippets/`** — these contain inline `<svg>` elements ready to paste directly into HTML output. SVG is the preferred format for all HTML output.

### Assets (Logo Source Files)

- **`references/assets/README.md`**: Complete index of all logo files with file paths, format recommendations, and quick selection guide
- **`references/assets/ringier/source/standard/`**: Standard Ringier logos (SVG, PNG, EPS — RGB and CMYK)
- **`references/assets/ringier/source/monochrome/`**: All-black and all-white logos (SVG, PNG, EPS)
- **`references/assets/ringier/source/flag/`**: Flag logos in three colours — Cyan, Magenta, Yellow (SVG, PNG, EPS — RGB and CMYK)

**Token-efficient usage**: Only load reference files when you need deep specifications. For quick questions, this main file should suffice. For HTML generation, prefer the `snippets/` directory over raw assets.

---

## General Image Guidelines

These rules apply to all Ringier branded materials:

- **No low-resolution or pixelated images** — always use high-quality assets (vector preferred; raster at 300dpi for print, 150dpi minimum for digital)
- **No off-palette colors** — only use colors from the approved brand palette (see Color Palette section above)
- **Brand color order** — when primary brand colors appear next to each other in a row (e.g., color bars, swatches, accent strips, decorative elements), they must always follow the order: **Magenta → Yellow → Cyan**

### Optional: Accent Line

A thin gradient accent line (Magenta → Yellow → Cyan) may be used as a subtle page-bottom or section divider. This is an **optional enhancement**, not required on every page.

- **Height**: 1.5–2pt (thin and understated, not a thick block)
- **Style**: CSS linear gradient `linear-gradient(to right, #e6007e, #ffde14, #009fe3)` — smooth colour transition, never segmented blocks
- **Placement**: Bottom edge of white-background pages, or as a section divider between content areas
- **Usage**: Use sparingly for visual polish — not every page needs one. Omit on coloured-background pages (the background colour already provides brand presence)

---

## Data Visualization Color Guidelines

When creating charts, infographics, dashboards, diagrams, data tables with color coding, maps, or any visual that uses color to represent data series, follow these guidelines.

### Color Selection for Data Series

**1-3 data series**: Use primary colors — **Magenta** `#e6007e`, **Yellow** `#ffde14`, **Cyan** `#009fe3`.

**4+ data series**: Use a **single-color tint approach**. Pick one primary color and use its tint scale:
- Example (Magenta): 100% `#e6007e`, 75% tint, 50% tint, 25% tint
- Example (Cyan): 100% `#009fe3`, 75% tint, 50% tint, 25% tint
- Tint values for all colors are defined in `references/color-system.json`

**On white backgrounds**: Prefer tints of a single color, unless there are 3 or fewer data fields (in which case use the primary colors directly).

**When more variety is needed**: Secondary colors (Marine, Coral, Turquoise, Tangerine, Sea, Lilac, Lime) can supplement the tint approach when the single-color scale does not provide enough distinction.

### Adjacency Rule

Avoid placing visually similar colors next to each other in charts and legends. Ensure sufficient contrast between neighboring data series.

**Colors to keep separated** (too similar when adjacent):
- Cyan `#009fe3` and Sea `#4e81a3` (both blue-toned)
- Cyan `#009fe3` and Turquoise `#31b6b3` (both cool blue-green)
- Coral `#ff6b6b` and Magenta `#e6007e` (both red-pink)
- Coral `#ff6b6b` and Tangerine `#f29331` (both warm-toned)
- Yellow `#ffde14` and Lime `#d5de5b` (both yellow-green)

**Good adjacent pairings** (high contrast):
- Marine + Coral, Marine + Lime, Turquoise + Tangerine, Sea + Coral, Lilac + Marine

### Accessibility in Data Visuals

- Never rely on color alone — always pair with labels, patterns, or position
- Test adjacent colors for color-blind distinguishability (especially red-green pairs like Coral + Lime)
- Use the adjacency rule above to maximise visual distinction

For complete color specifications and tint values: See `references/color-usage.md`

---

## Asset Handling

Brand assets (logos, icons) live in this skill's `references/assets/` directory. How they reach the output depends on what you're generating.

### Single-file output (HTML presentation, report, email)

**Embed assets as inline `<svg>` elements.** This makes the file fully self-contained and portable.

**Preferred approach**: Use the pre-built snippets from `snippets/` which already contain `<svg>` elements. Just read the snippet and copy the `<svg>` element directly into your output.

**Manual approach** (if snippets don't cover your case):
1. Read the required SVG logo file from `references/assets/ringier/source/`
2. Strip the `<?xml ...?>` declaration and any `<!-- Generator: ... -->` comment
3. Paste the `<svg>` element inline into your HTML output

**Always use SVG for HTML output** — never use PNG when SVG is available. SVG scales perfectly, has smaller file size, and renders crisply on all screen densities.

This is the **default mode** — most branded output from this skill is single-file HTML.

### SVG Sprites for Multi-Page Output

**For presentations, reports, or any HTML with multiple pages/slides, define each SVG logo once and reuse it via `<use>`.** Repeating the full SVG markup on every slide wastes output tokens and can cause generation to hit token limits on longer documents.

**Technique**:

1. Place a hidden sprite block at the top of `<body>` containing each logo as a `<symbol>`:
   ```html
   <svg xmlns="http://www.w3.org/2000/svg" style="display:none">
     <symbol id="ringier-flag-magenta" viewBox="...">
       <!-- full flag SVG paths from snippet, pasted once -->
     </symbol>
     <symbol id="ringier-standard" viewBox="...">
       <!-- full standard logo SVG paths from snippet, pasted once -->
     </symbol>
   </svg>
   ```
2. On each page/slide, reference the symbol instead of repeating the full SVG:
   ```html
   <svg style="width:154px" viewBox="..."><use href="#ringier-flag-magenta"/></svg>
   ```
3. The `viewBox` on the `<symbol>` comes from the original snippet's `<svg>` element. Copy it exactly.

**When to use sprites vs inline**: If a logo appears on **2+ pages**, use the sprite approach. For single-page output (letterhead, business card, social graphic), inline is fine.

### Important

- **Never use relative paths pointing back to the skill directory** — the skill may not be mounted in future sessions or on other machines
- **Never use absolute `file://` paths** — they are machine-specific and will break when shared
- The rule "never load logo files into context" refers to conversation context (token cost). Reading a snippet file to copy its `<svg>` element into output is correct and expected.

---

## Required Asset Snippets

**When generating HTML, use the pre-built snippets in `snippets/` to embed logos.** Do not create empty containers or placeholder divs.

### Available Snippets

| Snippet | File | When to Use |
|---|---|---|
| **Flag logo (cyan)** | `snippets/flag-logo-cyan.html` | Magenta, yellow, or warm photo backgrounds |
| **Flag logo (magenta)** | `snippets/flag-logo-magenta.html` | Cyan, yellow, marine, black backgrounds (most common) |
| **Flag logo (yellow)** | `snippets/flag-logo-yellow.html` | Magenta, cyan, or cool photo backgrounds |
| **Standard logo** | `snippets/standard-logo.html` | White background pages — any position (top-left, centered, or bottom-right) |

Each flag snippet is a self-contained `<svg>` element with the complete flag logo (coloured triangle + white rectangle + Ringier logo) rendered inline. No wrapper div is needed.

### Workflow

1. **Choose** the correct flag colour (must contrast with page background) or standard logo (white bg)
2. **Read** the snippet file
3. **Embed** the logo:
   - **Single-page output**: Copy the `<svg>` element directly into your output
   - **Multi-page output** (presentations, reports): Define the `<svg>` as a `<symbol>` in a sprite block once at the top of `<body>`, then use `<svg><use href="#..."/></svg>` on each page (see *SVG Sprites for Multi-Page Output* above)
4. **Adjust** the `style="width:..."` on the `<svg>` element if needed (default: 154px for 1920x1080, 216px for 1080x1080)

> **Inline SVG is the required format for HTML logos.** All snippets use inline `<svg>` elements — never use `<img>` with PNG when generating HTML. SVG scales perfectly and renders crisply on all screen densities. For multi-page documents, use SVG sprites to avoid repeating the full markup on every page.

For full details on all snippet files: See `snippets/README.md`

---

## Pre-Flight Checklist

Before finalizing any HTML output, verify every item below. Do NOT skip this step.

- [ ] **Every slide/page has a logo**: flag logo on non-white backgrounds, standard logo on white backgrounds. Never flag on white. No slide should be logo-free unless explicitly requested.
- [ ] **Logos use inline SVG**: all logos are embedded as `<svg>` elements pasted directly into the HTML. Never use `<img>` with PNG in HTML output.
- [ ] **SVG sprites for multi-page**: if the output has 2+ pages/slides, each unique logo is defined once as a `<symbol>` in a sprite block at the top of `<body>` and referenced with `<use>` on each page — never repeat full SVG markup per slide.
- [ ] **Flag logo colour contrasts with page**: cyan flag on magenta/yellow bg, magenta flag on cyan/yellow/dark bg, yellow flag on magenta/cyan bg. Never same colour as page.
- [ ] **Flag logos are self-contained**: each flag `<img>` contains the complete flag element (triangle + white rectangle + logo). No wrapper div with background colour needed.
- [ ] **Coloured periods are present**: key headlines end with a `<span>` coloured period in a contrasting primary colour.
- [ ] **Bodoni tracking is set**: all headline elements have `letter-spacing: -0.04em` (not `-0.02em` — that is too loose).
- [ ] **Bodoni Moda optical sizing is overridden**: headlines using Bodoni Moda have `font-optical-sizing: none; font-variation-settings: 'opsz' 26`.
- [ ] **No italic on headlines**: headline elements do not use `font-style: italic`. Use colour for emphasis within headlines instead.
- [ ] **Headline colour on light backgrounds is black `#000000`**: do not use marine `#162d46` for headings on white/light backgrounds.
- [ ] **Colour order is correct**: when M/Y/C appear adjacent (strips, bars), order is always Magenta → Yellow → Cyan.
- [ ] **One logo per page**: no page has more than one logo (standard or flag).
- [ ] **No fabricated brand graphics**: all visual assets come from `snippets/` or `references/assets/` — no hand-drawn rings, improvised icons, or invented decorative elements that mimic brand assets.

---

## Key Reminders

1. **Inline SVG for all HTML logos** — Always use inline `<svg>` elements from `snippets/` when generating HTML. Never use `<img>` with PNG or base64 data URIs.
2. **Flag logo is mandatory** for non-white backgrounds — Three variants: cyan, magenta, yellow. Choose contrasting colour. **Never use flag on white** — use standard logo instead.
3. **Flag logos are self-contained** — Each SVG includes the coloured triangle + white rectangle + logo. No wrapper div needed.
4. **Bodoni at -40 tracking (`letter-spacing: -0.04em`)** — Never use default tracking for Ringier headlines. `-0.02em` is wrong — must be `-0.04em`
5. **Rounded corners (5mm)** — Signature Ringier style element for frames and images
6. **Coloured periods** — End key statements with contrasting primary colour period
7. **Protected areas** — Always maintain; height of 'R' for standard logo, height of triangle for flag logo
8. **Claim separation** — "We inform. We entertain. We connect." is NEVER adjacent to Ringier logo
9. **Calm ↔ Expressive range** — Adapt formality to context (investor deck vs marketing campaign)
10. **Data visuals: primary colours for 1-3 series, tints for 4+** — Use Magenta, Yellow, Cyan for up to 3 data series; for 4+ series, use a single-colour tint approach (100%/75%/50%/25%); on white backgrounds, prefer tints unless 3 or fewer fields
11. **Data visuals: avoid similar adjacency** — Don't place visually similar colours next to each other in charts

---

**Source material**: Ringier guidelines derived from Ringier Style Guide 2021-12-01 (76-page PDF).

---

*Version 2.0.0 | Ringier AG Corporate Brand Identity | April 2026*
