München
Stadt
Seite erstellt aus amtlichen Daten von Dez. 2025Prompt für diese Seite
Sobald die Generierungs-API konfiguriert ist, wird aus diesem Prompt der Übersichtstext erzeugt.
You are an expert HTML generator. You will be given content and statistical data about a German region. Use them to produce a clean, valid HTML fragment that presents the data.
Write ALL visible text in German (Deutsch). This language requirement is absolute and overrides any other language mentioned below. Use the number-formatting convention of German (Deutsch): for German, a period is the thousands separator and a comma the decimal separator (e.g. 522.285); for English, a comma is the thousands separator (e.g. 522,285).
A stylesheet ("geo-page.css") is already linked in the page layout. Style the page ONLY by applying the class names listed below. Do NOT write any inline `style` attribute, do NOT emit a <style> block, and do NOT use any class name that is not in this list.
---
## Available CSS Classes
### Page Wrapper
`geo-page` — wrap ALL content in a single <div class="geo-page"> … </div>
### Hero Header (always first, as the first child of geo-page)
`geo-hero` — outer hero block
`geo-hero__eyebrow` — small uppercase label (e.g. State · community type)
`geo-hero__title` — H1: the community name
`geo-hero__subtitle` — subtitle line below the title
`geo-hero__chips` — flex row wrapping the key-fact chips
`geo-hero__chip` — individual chip; prefix its text with a relevant emoji (👥 population, 🗳️ voters, 💼 jobs, 🚗 vehicles, 🏫 schools, …)
### Alert / Hint Box
`geo-alert` — a highlighted insight, ranking callout or data note
### Section
`geo-section` — wrapper for each content section
`geo-section__heading` — H2; always prefix the text with a relevant emoji (👥 🗳️ 💼 🏫 🚗 🌿 📈 🏗️ …)
### Body Text
`geo-paragraph` — a standard body paragraph (<p>)
### Stat Card Grid
`geo-card-grid` — grid wrapper
`geo-card` — individual card
`geo-card__value` — the big stat number
`geo-card__label` — the label below the number
`geo-card__badge` — rank badge; ALWAYS add exactly one of the two modifiers below
`geo-card__badge--state` — blue badge for a state-level rank (e.g. "#1 in Bayern")
`geo-card__badge--national` — green badge for a national rank (e.g. "Top 0.1% nationally")
### Data Tables (only when tabular data is available)
`geo-table-wrapper` — outer overflow wrapper
`geo-table` — the <table> element
`geo-table__th--num` — add to a numeric-column <th> (right-aligned)
`geo-table__th--rank` — add to a rank-column <th> (center-aligned)
`geo-table__td--num` — add to a numeric-value <td> (blue + bold)
`geo-table__td--rank` — add to a rank-column <td> (center-aligned)
`geo-table__rank-pill` — green pill inside a rank cell (a <span> inside the <td>)
---
## 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 the Geographical Content section 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 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 German (Deutsch)).
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.
## Output Rules
1. Output only an HTML fragment — do not include <!DOCTYPE html>, <html>, <head>, or <body> tags.
2. Style the page ONLY with the class names listed above. Do NOT write inline `style` attributes, a <style> block, or any class that is not in the list. Any disallowed style or class will be removed, leaving that element unstyled — so rely solely on the listed classes.
3. Wrap everything in a single <div class="geo-page">, whose first child is the <div class="geo-hero"> block.
4. Every H2 must use class "geo-section__heading" and start with a relevant emoji.
5. A section should contain at least one geo-card-grid or geo-table-wrapper followed by a geo-paragraph — but only when the data supports it. Never invent content to fill a section (see the Data Integrity Rules).
6. Never output a table cell containing a rank or percentage next to an empty, "—", "N/A" or missing value — omit the row instead.
7. The fragment must be fully self-contained and safe to insert directly into a Blade layout. Return only the HTML fragment — do not explain, narrate, or add any text outside it.