docs(blog): style audit, two new rules, and the German translation of article 3

[astrapi69]

Audits the three-part blog series against the seven formatting rules and completes the style guide.

Method

Read each article in full, not just grep for em-dashes. Some rules (disguised tables, decorative rhetorical questions) are invisible to text search.

Findings

The prose was almost entirely clean already:

Rule	Result across all three articles
No em-dashes	0
Real UTF-8, real umlauts	clean (German examples use ä/ö/ü/ß; no ae/oe/ue/ss)
No hidden control / zero-width chars	0
No emojis	0
Real Markdown tables	all tabular data already in real tables; the bullet lists are genuine prose lists
Closing summary	all three already close with one

One substantive fix:

• Decorative rhetorical question in the lesson creator walkthrough. "Don't like the mix? Regenerate..." became "To change the mix, Regenerate...". Every other question mark in the series carries the argument (the schema-first thesis question, the transition into the extension tier, the core-or-extension decision test) or sits inside a quoted example, so those stay.

Style guide

STYLE.md gained the two rules it was missing, so the guidelines are complete in one place:

• Rhetorical questions (rule 4): allowed only when they frame the problem, bridge a section, or pose a test the reader answers; not as filler.
• Closing summaries (rule 6): a default where an article argues or walks a process.
• The tables rule now also states the converse: a bullet list of prose explanations is a list, not a table to force into columns.

Renumbered to stay contiguous. The header now names the formatierungsrichtlinien-blog-engine-cc alias the task referred to, so a search for that name lands on this file (it does not exist under that name; STYLE.md is the guide).

Note

The two em-dash matches remaining in STYLE.md are the rule text itself (naming the forbidden — and the grep command that checks for it), not violations.

make release-check green.

🤖 Generated with Claude Code

[astrapi69]

Scope grew after the first commit. The German translation of article 3 landed on this branch, and writing it exposed several factual errors in the English article. Summary of the full branch:

Style audit

Rule	Result
No em-dashes (U+2014)	0 across all articles
No faked em-dashes (spaced hyphen as a pause)	9 found and fixed
Real UTF-8, real umlauts	clean
No hidden control / zero-width chars	0
No emojis	0
Real Markdown tables	already correct
Rhetorical questions	one decorative one removed; the rest carry the argument
Closing summary	already present in all

The faked em-dashes are the notable miss: rule 1 forbids them as much as U+2014, and my first pass grepped only for the literal character. STYLE.md's Checking section now greps for both, so the guide's own audit catches what I did not.

German translation

docs/blog/de/create-a-lesson-in-the-app.md with its own screenshot set (DOCS_LANG=de against current develop). A language directory rather than a .de.md sibling. The German text uses German UI labels throughout, because the German screenshots do: the extension picker shows "Kategorisierung", "Diktat" and so on, not the technical ids the English UI displays, so that paragraph and its table were rewritten rather than translated.

Corrections the translation exposed

1. The review checklist has five items, not six. "Language pair is valid" has not been rendered for some time; its i18n key survives in all 11 catalogs with nothing referencing it. Filed as adaptive-learner#1929.
2. Dictation has an audio upload now (adaptive-learner#1911, inline data URI) alongside the typed asset path. The article claimed there was none and listed it as an honest limit. Both corrected; the real remaining limit is that browser recording is not built.
3. The missing-type notice is an instruction, not a label: "Picture choice: add an image to at least two cards", not the bare picture_choice that was quoted.

All English screenshots were refreshed from one consistent develop run, since the article claims every shot comes from a single flow and the app had moved underneath several of them.

make release-check green; all 22 image references resolve.