wiki-aufgabe

wiki-aufgabe

Generate a DokuWiki exercise page (Aufgabe) 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 — values the user (or colleagues) may have customized after installing the skill.

What the user provides vs. what you ask for

An Aufgabe needs these pieces of metadata. Pull whatever the user has already given you out of their request, then ask once for the rest in a single compact prompt.

Field	Example	Notes
Module	m319	Default to the value of DEFAULT_MODULE in config.txt.
LU number	01	Two digits, zero-padded.
A-number	02	Two digits. The full identifier becomes LU01.A02.
Page slug	variablen	Lowercase, hyphen-separated. Often the same slug as the related theory page.
Title	Variablen (BlockPy)	Human-readable. Full H1: LU01.A02 - Variablen (BlockPy). The parenthesised suffix often names the tool/environment (BlockPy, PyCharm, Blockly, Console).
Task description	(free-form)	What the student must do.
Submission instructions	(free-form, optional)	How the student turns it in (screenshot upload, GitHub link, etc.). If not specified, ask whether to include the standard "Screenshot hochladen" pattern or skip the Abgabe section.

Page structure

Aufgabe pages are short and instructional. The skeleton:

{{tag>mNNN-luXX}}

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

<one-or-two-line lead-in stating what to do>

==== <Tool / context section, optional> ====

[[<external-link-to-tool>|<tool name>]]

==== <Task specifics section> ====

<the actual task — bullet list, table, or short prose>

==== Abgabe ====

<how to submit — screenshot upload, link, etc.>

----

{{tag>mNNN-LUXX}}

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

Conventions worth following:

• Aufgabe pages are typically 30–80 lines of source. Much shorter than theory pages. If your draft balloons past 100 lines, you're probably over-explaining — the theory belongs on the theory page, the task page just gives instructions.
• The top tag block is usually just the LU tag (m319-lu01) — no competence-cell tags. Aufgaben don't need them; the linked theory page already provides them.
• The lead-in (the prose before any H3) is usually 1–3 sentences telling the student in imperative form what they're going to do. "Erstelle die beschriebenen Variablen…", "Schreibe ein Programm das…".
• Common H3 sections (use what fits, skip what doesn't):
  • ==== <Tool name> ==== — link to the IDE or environment (BlockPy, BlockPy, replit, etc.)
  • ==== Aufgabenstellung ==== or ==== Auftrag ==== — the detailed task
  • ==== Vorgaben ==== — provided code, data, or constraints
  • ==== Anforderungen ==== — what the solution must demonstrate
  • ==== Hinweise ==== — tips
  • ==== Abgabe ==== — submission instructions (almost always present)
• Use bullet lists for sub-tasks, requirements, or expected variables/outputs. The wiki style is "bulleted instructions", not paragraphs of prose.
• Use address form du / imperative — same voice as theory pages.
• The Abgabe section is often a single sentence: "Erstelle einen Screenshot des BlockPy-Diagramms und lade den Screenshot hier hoch." — adapt to whatever submission channel applies.

DokuWiki syntax cheat-sheet

For markup details (headings, lists, code blocks, links), see references/dokuwiki-syntax.md. The Aufgabe-specific things to remember:

• Lists need two leading spaces: * item
• Inline code/values use ''…'', not backticks
• External links to tools: [[https://blockpy.cis.udel.edu/blockpy/load|BlockPy]]

Real examples

references/examples.md contains real Aufgabe pages from m319 — read them when in doubt about depth or section choice.

Output

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

1. The full page ID (e.g. de:modul:m319:learningunits:lu01:aufgaben:variablen).
2. The matching Lösung page ID, which the user typically creates next: de:modul:m319:learningunits:lu01:loesungen:variablen with title LU01.L02 - … (L-number matches A-number).
3. Anything you guessed.

Style notes

• Aufgabe pages on this wiki are terse and operational. The student needs to know what to do, with what tool, and how to hand it in. Don't pad with motivation or context — that's what the linked theory page is for.
• Keep prose in German with du address. Code identifiers in any provided snippets stay English.
• A-numbering convention: A01, A02, A03 within a single LU. Look at the LU's start page in the wiki to see what's already taken. If the user doesn't specify, ask which number to use.