wiki-loesung

wiki-loesung

Generate a DokuWiki solution page (Lösung) in the style of the BZZ Modulwiki.

First step: read the config

Before generating anything, read config.txt in this skill's folder. It contains the author footer, license, and default module.

What the user provides vs. what you ask for

A Lösung needs these pieces of metadata. The L-number must match the A-number of the corresponding Aufgabe — that's the convention on this wiki.

Field	Example	Notes
Module	m319	Default to DEFAULT_MODULE from config.txt.
LU number	01	Two digits.
L-number	02	Must match the A-number of the related Aufgabe. If the Aufgabe is LU01.A02, the Lösung is LU01.L02.
Page slug	variablen	Lowercase, hyphen-separated. Usually identical to the Aufgabe's slug — that's the convention.
Title	Variablen (Blockly)	Often the same title as the Aufgabe but with the language/environment in the suffix changed if the solution is shown in a different tool. Full H1: LU01.L02 - Variablen (Blockly).
Solution content	(free-form)	Code, screenshots, explanations. Multiple language variants are common (Python + Blockly, etc.).

If the user references the matching Aufgabe (e.g. "Lösung für LU01.A02"), derive the L-number, slug, and title from it automatically — don't ask again.

Page structure

Lösung pages are lean — usually shorter than even the Aufgabe. The skeleton:

{{tag>mNNN-luXX}}

====== LUXX.L<NN> - <Title> ======

{{<optional-screenshot-image>}}

==== <Language / variant heading> ====

<code <lang>>
…
</code>

==== <Another language / variant, optional> ====

<code <lang>>
…
</code>

----

{{tag>mNNN-LUXX}}

{{<license-image-url>}} <author footer>

Conventions:

• Top tag is just the LU tag (m319-lu01) — same as Aufgabe, no competence-cell tags.
• No introductory prose. Lösungen jump straight to the answer. The student already has the question on the Aufgabe page.
• Screenshot first is common when the original task was visual (Blockly diagram, GUI). Use {{:de:modul:mNNN:learningunits:luXX:loesungen:<slug>.png?w=400|caption}} — note the :loesungen: segment in the media path.
• One H3 per language/variant. A typical pattern is ==== Python ==== and ==== Blockly ==== — same logical solution shown in both representations. If there's only one form, use a single H3 (or omit the H3 entirely if the page is just one code block under the H1).
• Code blocks wrapped in <code python>…</code>, <code java>, etc. Plain <code> for shell or unspecified.
• Total length: ~15–40 lines of source. Lösungen are the shortest of the three page types. If you find yourself writing explanations, stop — the explanation belongs on the theory page.
• No ==== Erklärung ==== or commentary section unless the solution genuinely needs it. The wiki style trusts students to compare their own work to the reference solution and figure out the difference. If a tricky step needs comment, prefer inline # comments in the code over a separate prose section.

DokuWiki syntax cheat-sheet

For markup details see references/dokuwiki-syntax.md. Things to remember for Lösungen:

• Code blocks: <code python>…</code>
• Images: {{:absolute:namespace:path:image.png?w=400|caption}}
• The horizontal rule before the footer is ---- (four hyphens).

Real examples

references/examples.md has actual Lösung pages from m319.

Output

Print the complete DokuWiki source as a single fenced code block. After the block, briefly state:

1. The full page ID (e.g. de:modul:m319:learningunits:lu01:loesungen:variablen).
2. Any media files referenced (screenshots) that need to be uploaded to the media manager — give the namespace path each goes to.
3. A reminder that the matching Aufgabe page should already exist (or note its expected ID) so the user can verify the L-number matches.

Style notes

• Idiomatic, clean code — Lösungen serve as reference solutions students compare against. Use English variable names (count_chicken, not anzahl_huehner), follow the language's standard style (PEP 8 for Python, etc.), and prefer clarity over cleverness.
• No prose explanations of what the code does unless the user explicitly provides one. The code itself, plus inline comments where genuinely useful, is enough.
• Screenshots of Blockly/GUI solutions are first-class content on these pages — when the original Aufgabe involved a visual environment, the screenshot is often more important than the text code.