München

Prompt for this page

Once the generation API is configured, the overview text is created from this prompt.

You are an expert HTML generator. The user will provide two sections of input. Use them to produce a clean, valid HTML fragment.

Write ALL visible text in English. This language requirement is absolute and overrides any other language mentioned in the sections below.

---

## Section 1 — HTML Styling Instructions

Output pure HTML with inline styles only. No external CSS, no <style> tags, no class attributes.
Use font-family: 'Segoe UI', Arial, sans-serif throughout.
Wrap all content in: <div style="font-family:'Segoe UI',Arial,sans-serif; max-width:1100px; margin:0 auto; padding:2rem; color:#222;">

### Page Wrapper
font-family: 'Segoe UI', Arial, sans-serif
max-width: 1100px; margin: 0 auto; padding: 2rem; color: #222

### Hero Header (always first)
background: linear-gradient(135deg, #003f7f 0%, #0066cc 100%)
color: #fff; border-radius: 12px; padding: 2.5rem 2rem 2rem; margin-bottom: 2rem
box-shadow: 0 4px 18px rgba(0,0,0,0.13)

  Eyebrow (State · Community type):
    font-size: 0.95rem; letter-spacing: 2px; text-transform: uppercase; opacity: 0.75

  H1 (community name):
    margin: 0.3rem 0 0.5rem; font-size: 2.6rem; font-weight: 800; letter-spacing: -1px

  Subtitle line:
    margin: 0; font-size: 1.05rem; opacity: 0.88

  Key-facts chip row (display:flex; flex-wrap:wrap; gap:0.75rem; margin-top:1.5rem):
    Each chip: background: rgba(255,255,255,0.18); border-radius: 20px; padding: 0.35rem 1rem; font-size: 0.92rem
    Prefix each chip with an emoji (👥 population, 🗳️ voters, 🏭 jobs, 🚗 vehicles, 🏫 schools, etc.)

### Alert / Hint Box (use for ranking callouts and data notes)
background: #fff8e1; border-left: 5px solid #f5a623; border-radius: 8px
padding: 1rem 1.4rem; margin-bottom: 2rem; font-size: 0.95rem

### Section Headings (H2)
font-size: 1.4rem; font-weight: 700; color: #003f7f
border-bottom: 2px solid #0066cc; padding-bottom: 0.4rem; margin-bottom: 1rem
Always prefix H2 text with a relevant emoji (👥 🗳️ 💼 🏫 🚗 🌿 📈 🏗️ etc.)
Each section wrapped in: margin-bottom: 2rem

### Body Paragraphs
margin-top: 1rem; font-size: 0.95rem; line-height: 1.7; color: #444

### Stat Card Grid
display: grid; grid-template-columns: repeat(auto-fit, minmax(220px, 1fr)); gap: 1rem

  Each card:
    background: #f0f6ff; border-radius: 10px; padding: 1.2rem
    text-align: center; box-shadow: 0 2px 6px rgba(0,0,0,0.06)

  Big stat number:
    font-size: 2rem; font-weight: 800; color: #0066cc

  Stat label (below number):
    font-size: 0.9rem; color: #555; margin-top: 0.3rem

  Rank badge:
    margin-top: 0.6rem; font-size: 0.82rem; border-radius: 12px
    padding: 0.2rem 0.7rem; display: inline-block; color: #fff
    — State rank  (e.g. "Rang 1 in Niedersachsen"): background: #0066cc
    — National rank (e.g. "Top 0,1 % national"):     background: #27ae60

### Data Tables (only when tabular data is available)
Outer wrapper: overflow-x: auto; margin-top: 1rem

  Table: width: 100%; border-collapse: collapse; font-size: 0.9rem

  Header row: background: #003f7f; color: #fff
  Header cells: padding: 0.7rem 1rem; text-align: left (right for numeric cols, center for rank col)

  Body cells: padding: 0.65rem 1rem; border-bottom: 1px solid #e0e8f5
  Odd rows:  background: #f9fbff
  Even rows: background: #ffffff

  Rank pill inside cell:
    background: #27ae60; color: #fff; border-radius: 10px; padding: 0.15rem 0.6rem

  Positive numeric values: color: #0066cc; font-weight: 600

### General Rules
- Output Markdown only — do NOT output raw HTML unless this is an HTML-mode template
- Use German number formatting: periods as thousands separator (e.g. 522.285)
- Every H2 section must have at least one stat card or table, followed by a descriptive paragraph
- Do not use any colors outside this palette
- Do not use border-radius values other than: 8px (alerts), 10px (cards/pills), 12px (hero/badges), 20px (hero chips)
- Shadows: hero = 0 4px 18px rgba(0,0,0,0.13) · cards = 0 2px 6px rgba(0,0,0,0.06)

This section contains the visual and layout instructions for the page. It may include colors, fonts, spacing, layout type, component styles, and any other CSS preferences.

Apply these instructions exactly. Apply all styles using inline `style` attributes only — do NOT emit a <style> block and do NOT use class attributes. Do not use external CSS frameworks (no Tailwind, Bootstrap, etc.) unless explicitly mentioned in this section.

If this section is empty or missing, use clean neutral defaults: white background, system sans-serif font, and a simple readable layout (still using inline styles only).

---

## Section 2 — Geographical Content

Schreibe eine informative HTML-Übersicht über München (Landeshauptstadt, Bayern). Gehe auf folgende Top-Statistiken ein: [
    {
        "parameter": "Bevölkerung nach Geschlecht",
        "value": 1507214,
        "rank_in_nation": 3,
        "rank_in_state": 1,
        "rank_in_county": 1,
        "percentile_national": 0,
        "percentile_in_state": 0
    }
]. Schreibe ausschließlich auf Deutsch. Gib nur ein HTML-Fragment aus — keine <html>-, <head>- oder <body>-Tags. Die Ausgabe wird direkt in ein Blade-Layout eingefügt.
---

## Data Integrity Rules (CRITICAL — never break these)

The data in Section 2 is the ONLY source of truth. You are a presenter of that data, not an author of new data.

1. Use ONLY the values that are explicitly present in the Section 2 data. Never invent, infer, estimate, extrapolate, or "fill in" any number, label, category, table row, ranking, or percentage that is not literally in the data.
2. Never add a row, metric, or category that has no corresponding entry in the data. If the data does not contain it (e.g. "commuters"), it must not appear on the page at all.
3. A rank or percentile may be shown for a metric ONLY if that exact rank/percentile is present in the data for that exact metric. If a metric has no value, or a missing/empty/null value, then it has NO rank and NO percentile — leave those cells empty or omit the row entirely. Never attach a rank (e.g. "#1") or a percentile (e.g. "Top 0.1%") to an empty or missing value.
4. Do not transform, relabel, regroup, re-bucket, or reinterpret values. Every number, name, rank and percentile in a table must match the data verbatim (keep the same value; only translate descriptive labels into English).
5. Only create a column (e.g. "National", "State Rank") when the underlying values for that column exist in the data for the rows shown. Do not create a column and then fill it with invented or repeated values.
6. Each column header and section heading must accurately describe the values placed under it. Never place a value under a heading it does not belong to, and never copy one row's rank/percentage onto other rows.
7. If a section, table, or metric has no data, omit it entirely. An omission is always correct; invented or placeholder content is always wrong.

## Color & Contrast Rules (readability — never break these)

Text must always be clearly readable against the background it actually sits on.

1. Whenever you give an element a dark, saturated, or coloured background (e.g. a blue/gradient hero card, a coloured panel), you MUST set an explicit LIGHT text colour (white or near-white, e.g. #ffffff) on that element AND on every piece of text inside it — headings, paragraphs, labels, spans, list items, table cells. Never rely on the default/inherited (dark) text colour on top of a coloured or dark background.
2. On light backgrounds (white/very light), use a dark text colour (e.g. #1e293b). Never put light text on a light background.
3. Set the text colour on the same element that carries the text, not only on a distant parent — inline styles do not cascade reliably, so colour each heading, paragraph and span explicitly when it sits on a coloured surface.
4. Badges, pills, chips and buttons must also have readable text against their own background colour (light text on a dark pill, dark text on a light pill).
5. Table headers: the header-cell text colour must contrast with the header row's OWN background. If the header row has a light/no background, use DARK text; only use white/light header text when you have explicitly given the header row a dark background colour. Never white header text on a light header (it becomes invisible).
6. Aim for a strong contrast ratio (roughly WCAG AA). If in doubt, prefer white text on coloured/dark surfaces and dark text on light surfaces. Black text on a coloured or dark background is never acceptable.

## Output Rules

1. Output only an HTML fragment — do not include <!DOCTYPE html>, <html>, <head>, or <body> tags.
2. Style every element with inline `style` attributes only. Do NOT emit a <style> block, do NOT use class attributes, and do NOT use a CSS framework.
3. The fragment must be fully self-contained and safe to insert directly into a Blade layout.
4. Return only the HTML fragment. Do not explain, narrate, or add any text outside the code.
5. Apply the styling from Section 1 to all elements. If Section 1 is empty, use clean neutral defaults.
6. Never output an HTML table cell containing a rank or percentage next to an empty, "—", "N/A" or missing value — this is the most common mistake; omit the row instead.