Community guidelines

  1. Write what you know. First-hand experience or an official source. Say when you last checked prices, fees and opening hours.
  2. Link the authority. Bureaucracy guides must link the official page for the country the guide applies to — the city's own service portal, a ministry, a law.
  3. No advertising disguised as content. If you own a place, claim it; do not write a guide that recommends your own business.
  4. No personal data of other people. No names of officials, no phone numbers of private persons, no photos of people without consent.
  5. No legal, tax or medical advice. Describe how a procedure works and what happened to you. Do not tell people what they should do in their individual case.
  6. Be kind and specific. Criticism of a place or an office is fine when it is factual.
  7. Respect the licence. Everything you publish is CC BY-SA 4.0. Only upload text and photos you have the rights to.

Moderation and reporting

Every page has a Report button, usable without an account, and moderators also read new comments without waiting for a report.

When a comment is removed, its author is told — in the app and by email — which of these it was: advertising or spam, personal data about someone else, a personal attack or harassment, unlawful content, not about this page, or another breach of these guidelines. The comment stays in your own record and in your data export; a line in the thread says a comment was removed, so nothing disappears silently. You can delete your own comment at any time, unless a moderator has already removed it.

Some comments wait before they appear. A comment with several links, a first comment from an account that has not confirmed its email address, or the same text posted again within a day is held for a person to look at. Only you can see it until then. Nothing is ever removed automatically and nothing here judges what you wrote — a human decides every case.

Between a warning and losing an account, a moderator can pause commenting on an account for a day, a week or a month. It ends on its own; reading, saving, reporting and editing keep working throughout. Repeated or serious breaches still lead to suspension.

This is our notice-and-action process under the EU Digital Services Act; the contact point is listed in the Impressum.

How many notices we receive and what we decide is published, as totals only, in our transparency report.

Writing accessible content

Many people read this site through a screen reader, a machine translator or a small phone screen, often in their second or third language. What works for them works for everybody. The check under the Content field in the editor looks for some of the points below while you type; the rest need a person.

  • Headings are an outline, not a font size. The page title is the only level-1 heading, so start sections with ## and go down one level at a time (##, then ###). Screen-reader users jump from heading to heading: a skipped level, or a line of bold text standing in for a heading, hides a section from them.
  • Say where a link goes. “Book an appointment at the citizens’ office” works as link text. “Click here”, “read more”, “hier”, “buraya tıkla” or a bare web address do not — links are often read out as a list, without the sentence around them. Never leave a link without text.
  • Use plain language. Short sentences, one idea each, everyday words. Explain an official term the first time you use it and keep the local word next to your explanation, because that is what the reader will see on the form. Split paragraphs of more than about 120 words.
  • Don’t rely on colour, shape or position. “Press the green button” or “the form on the right” means nothing to somebody who cannot see it. Name the button by its label, or the form by its title.
  • Tables are for data. Give every table a header row with the column names, keep it small, and never use a table to lay text out.
  • No text in capitals. A sentence in capitals is harder to read, and some screen readers spell it out letter by letter. Use bold, sparingly, for emphasis. Abbreviations such as EU or BVG are fine.
  • Easy-to-read language goes further than plain language and is written for people who find reading hard. If that is who your guide is for, follow an established standard: the European easy-to-read standards published by Inclusion Europe, or Leichte Sprache for German. Have the text checked by somebody from that audience if you can.
  • What the editor reminds you of. Besides the points above, the check under the Content field suggests naming a button or a field by its label when the text names it by its colour (“the green button”), and the Sources box warns about a bureaucracy guide without an official source. Both are reminders: they never stop you saving or publishing.

The check in the editor is a helper, not a judge. It never stops you saving a draft, and it asks once before you publish over an error. It cannot tell whether your text is clear — only you and your readers can.

Writing style

How a page is written matters as much as what it says. This is the short version of the editorial style guide; reviewers use the full one.

  • Answer first. The summary and the step titles must work on their own. Say what is different in this city and link the country-level page for the rest.
  • Keep the local word. Write the official term (Anmeldung, Meldezettel) in bold the first time, with the translation beside it, then use it alone. Never invent a translation for the name of a form or an office.
  • Dated numbers, real units. Write 63 € per month (as of January 2026), 10 to 20 minutes, 2 to 6 weeks, or “Free”. Never “fast” or “soon”.
  • One official source for every rule, fee and deadline. Link the page you actually read, not the front page. Say “in our experience” when it is experience.
  • Say how sure you are. “Usually”, “as of September 2026”, “varies by district”. When an office disagrees with its own website, write both and the date.
  • Describe, never advise. Say what happens and what the options cost, not what a reader should do. Never recommend a lawyer, adviser or provider by name.
  • Plain language, inclusive wording. Short sentences, no idioms, abbreviations spelled out once, and wording that fits every reader: “they” in English, gender-neutral forms in German, no assumptions about family or origin.
  • Your own photos only. No faces without consent, no documents showing personal data, and alt text that says what the picture shows.