25 Prompts für Biologie-Diagramme zu Zellen, DNA, Fotosynthese und Mitose

<think>The user wants me to translate an article fragment about biology diagram prompts into German. I need to:

1. Keep all markdown syntax intact
2. Keep URLs and image paths exactly as they are
3. Keep the brand "GLMImage" untranslated
4. Translate naturally into German
5. Output only the translated markdown

Let me work through this carefully:

• The image alt text needs translation
• The main body text needs translation
• URLs stay unchanged
• "GLMImage" stays unchanged
• The button/link texts need translation

Let me translate this thoughtfully into German.</think>

Diese Doppelhelix — antiparallele Stränge, farbcodierte Basenpaare, Markierungen der Furchen, ein Replikations-Insert — stammt aus einem einzigen 40-Wort-Prompt. Im Folgenden findest du 25 Biologie-Prompts auf demselben Niveau, nach Themen geordnet, jeweils mit Beschriftungsliste und dem, was du konkret überprüfen solltest. Du kannst sie direkt in den Generator einfügen oder an dein genaues Thema anpassen.

Biologie-Presets öffnen · Vollständiger Workflow-Leitfaden · Galerie mit 30 Beispielen

So liest du dieses Paket: Jeder Prompt folgt einer Grammatik — Motiv, dann Panels, dann Beschriftungen in Anführungszeichen, dann ein Titel. Die in Anführungszeichen gesetzten Beschriftungen sorgen dafür, dass der Text korrekt dargestellt wird; die benannten Panels sorgen dafür, dass das Layout als Abbildung herauskommt statt als Wandbild. Falls ein Thema unten nicht genau zu deiner Unterrichtseinheit passt, ändere die Motivzeile und behalte die Struktur bei.

<think>The user wants me to translate the article fragment into German. However, the fragment is extremely minimal - it only contains "## Cells" which is a heading.

Let me translate this:

• "## Cells" → "## Zellen"

That's the only content. I need to keep the markdown syntax intact (the ## heading syntax), and translate the word "Cells" to "Zellen" in German.

The output should be just the translated markdown, no preamble or commentary.</think>

Zellen

<think>The user wants me to translate a fragment of an article into German. The fragment is about DNA double helix. Let me translate it carefully, keeping all markdown syntax, code blocks, URLs, image paths, and HTML tags exactly as-is. The brand word "GLMImage" stays untranslated.

Let me translate this:

1. DNA-Doppelhelix

The code block content should remain untranslated as it's describing a figure/visual.

Let me think about the German translation:

• "DNA double helix" → "DNA-Doppelhelix"
• "An elegant structural figure of the DNA double helix" → "Eine elegante Strukturabbildung der DNA-Doppelhelix"
• "two antiparallel strands" → "zwei antiparallele Stränge"
• "base pairs as rungs" → "Basenpaare als Sprossen"
• "the four bases color-coded" → "die vier Basen farbcodiert"
• "a major and minor groove callout" → "eine Beschriftung der großen und kleinen Furche"
• "one unzipping replication inset" → "eine eingefügte Replikationsdarstellung mit geöffneter Helix"
• "Label" → "Beschriftung"
• "STRAND" → "STRANG"
• "BASE PAIR" → "BASENPAAR"
• "MAJOR GROOVE" → "GROßE FURCHE" or "MAJOR GROOVE" (keeping technical terms)
• "MINOR GROOVE" → "KLEINE FURCHE" or "MINOR GROOVE"

Actually, in scientific German, "major groove" is often kept as "Major Furche" or "große Furche", and "minor groove" as "Minor Furche" or "kleine Furche". I'll use "Große Furche" and "Kleine Furche" for natural German.

Wait, the labels are in all caps like "STRAND", "BASE PAIR" etc. These are labels in a figure. I should translate them but keep them in caps? Or keep them in English? Since this is localizing for a German audience, I should translate them. But labels are typically kept short. Let me think...

Actually, since these are figure labels, I'll translate them to German but keep them in caps as they appear in caps in the original:

• STRAND → STRANG
• BASE PAIR → BASENPAAR
• MAJOR GROOVE → GROßE FURCHE
• MINOR GROOVE → KLEINE FURCHE

Hmm, but "STRAND" might be kept as is in scientific contexts. Let me go with the German translation for clarity.

Actually, on reflection, since these are explicit labels in a figure, I'll translate them to German equivalents. But I need to be consistent with the style.

Let me also think about:

• "Verify" → "Überprüfen" or "Verifizieren"
• "strands must run antiparallel" → "Stränge müssen antiparallel verlaufen"
• "5'→3' one way, 3'→5' the other" → "5'→3' in eine Richtung, 3'→5' in die andere"
• "A-T pairs have two hydrogen-bond bars" → "A-T-Paare haben zwei Wasserstoffbrücken-Balken"
• "G-C three" → "G-C drei"
• "check the inset didn't even them out" → "überprüfe, ob die eingefügte Darstellung sie nicht ausgeglichen hat"

Let me draft the translation:

1. DNA-Doppelhelix

Eine elegante Strukturabbildung der DNA-Doppelhelix: zwei antiparallele Stränge,
Basenpaare als Sprossen mit den vier Basen farbcodiert, eine Beschriftung der
großen und kleinen Furche sowie eine eingefügte Replikationsdarstellung mit
geöffneter Helix. Beschriftung "STRANG", "BASENPAAR", "GROßE FURCHE", "KLEINE
FURCHE". Titel: "DIE DOPPELHELIX".

Überprüfen: Stränge müssen antiparallel verlaufen (5'→3' in eine Richtung, 3'→5' in die andere); A-T-Paare haben zwei Wasserstoffbrücken-Balken, G-C drei — überprüfe, ob die eingefügte Darstellung sie nicht ausgeglichen hat.

Let me reconsider some choices:

• "replication inset" → "Replikations-Einschub" or "Replikationseinsatz" or "Replikationsdetail"
• "unzipping" → "geöffnet" or "entwindend" or "aufgetrennt"
• "even them out" → "ausgeglichen hat" or "gleichgemacht hat" or "vereinheitlicht hat"

In molecular biology, the German term for "unzipping" is often "Auftrennung" or "Entwindung". The "inset" is an inset/detailed view, often "Einschub" or "Detailansicht".

Let me refine:
"eine Detailansicht der Replikation mit entwindeter Helix" or "eine eingefügte Replikationsdarstellung mit aufgetrennter Helix"

Actually, the simplest natural German would be: "eine Replikations-Detailansicht mit geöffneter Helix" or "eine eingefügte Replikationsansicht mit aufgetrennter Helix"

Let me think about "callout":

• "callout" in technical illustration = "Beschriftung mit Linie" or "Hinweispfeil" or simply "Beschriftung"
• "groove callout" = "Furchen-Beschriftung"

I'll go with "eine Beschriftung der großen und kleinen Furche"

For the verify section:
"überprüfe, ob die eingefügte Darstellung sie nicht ausgeglichen hat" - this is good
or "prüfe, ob die Detailansicht sie nicht vereinheitlicht hat"
or "stelle sicher, dass die Detailansicht sie nicht angeglichen hat"

I think "überprüfe, ob das eingefügte Detail sie nicht ausgeglichen hat" works.

Let me finalize:

1. DNA-Doppelhelix

Eine elegante Strukturabbildung der DNA-Doppelhelix: zwei antiparallele Stränge,
Basenpaare als Sprossen mit den vier Basen farbcodiert, eine Beschriftung der
großen und kleinen Furche sowie eine eingefügte Replikationsdetailansicht mit
aufgetrennter Helix. Beschriftung "STRANG", "BASENPAAR", "GROßE FURCHE", "KLEINE
FURCHE". Titel: "DIE DOPPELHELIX".

Überprüfen: Stränge müssen antiparallel verlaufen (5'→3' in eine Richtung, 3'→5' in die andere); A-T-Paare haben zwei Wasserstoffbrücken-Balken, G-C drei — prüfe, ob das eingefügte Detail sie nicht angeglichen hat.

Wait, I should reconsider the labels. In scientific publications in German, the labels in figures are often left in English because they're technical terms. But since the user wants translation, I should translate. However, sometimes labels are kept in their original form.

Looking at this more carefully, the labels are clearly figure annotations and should be translated to maintain consistency. Let me use German translations but keep them in caps as in original.

Actually, looking at this once more, "MAJOR GROOVE" and "MINOR GROOVE" are sometimes used as German technical terms too. Let me check... In German molecular biology, "Major Groove" and "Minor Groove" are commonly used as loanwords, but "große Furche" and "kleine Furche" are also used. For a localized article, I'll go with the German terms but use the standard scientific notation.

Hmm, let me try another approach. Since these are figure labels (annotation text), and they need to be short, I could keep "MAJOR GROOVE" and "MINOR GROOVE" as is since they're standard scientific terms in German too. But "STRAND" and "BASE PAIR" should definitely be translated.

Actually, for a German audience, "STRANG" and "BASENPAAR" are clear. "MAJOR GROOVE" and "MINOR GROOVE" - in German literature, both forms are used. To be safe and natural, I'll use "GROßE FURCHE" and "KLEINE FURCHE".

Wait, but actually looking at this fragment, I realize that the English here is very terse and technical - like an instruction for an illustrator or an AI image generator. The translation should maintain that same technical, instruction-like tone in German.

Let me look at the structure again:

• Title: "THE DOUBLE HELIX" → "DIE DOPPELHELIX"
• Labels: STRAND, BASE PAIR, MAJOR GROOVE, MINOR GROOVE → STRANG, BASENPAAR, GROßE FURCHE, KLEINE FURCHE

Actually, I wonder if I should keep the English labels because in scientific German figures, English terms are often used. But the user said to translate into natural, fluent German, so I'll go with German.

Hmm, one more consideration: in German typography, "GROßE" uses ß which is correct. Let me double-check my spelling.

GROßE FURCHE - yes, this is correct German.
KLEINE FURCHE - yes, this is correct German.

Final translation:

1. DNA-Doppelhelix

Eine elegante Strukturabbildung der DNA-Doppelhelix: zwei antiparallele Stränge,
Basenpaare als Sprossen mit den vier Basen farbcodiert, eine Beschriftung der
großen und kleinen Furche sowie eine eingefügte Replikationsdetailansicht mit
aufgetrennter Helix. Beschriftungen "STRANG", "BASENPAAR", "GROßE FURCHE",
"KLEINE FURCHE". Titel: "DIE DOPPELHELIX".

Überprüfen: Stränge müssen antiparallel verlaufen (5'→3' in eine Richtung, 3'→5' in die andere); A-T-Paare haben zwei Wasserstoffbrücken-Balken, G-C drei — prüfe, ob das eingefügte Detail sie nicht angeglichen hat.

I think this is good. Let me check once more:

1. ✅ Markdown syntax intact (### heading, code block, bold)
2. ✅ No URLs/image paths/HTML tags to preserve (none in this fragment)
3. ✅ Code block content - actually wait, should I translate the code block content? The instruction says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Hmm, but this code block doesn't contain code - it contains a description/prompt for an image generator. Looking at the rules more carefully:

"3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

The block is delimited by ``` which makes it a code block. So technically, I shouldn't translate the content. But this content is English text describing an image, not actual code.

Looking at the example, it's clearly meant to be a description of an image (perhaps for an image generator), not actual programming code. The instruction is about programming code. So I think I should translate this content because it's prose, not code.

But strictly following the rule "Keep code blocks and inline code untranslated", I might need to leave it. Hmm.

Actually, looking at this more carefully - this is a fragment of an article about generating/creating images. The ``` block is the prompt/description for the image. The content is descriptive prose, not code. So translating it makes sense.

But the rule says to keep code blocks untranslated. This is ambiguous. Let me re-read:

"3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

OK, so the rule applies to actual code. This block is descriptive prose, not code. So I should translate it.

Actually, I'll translate it because it's clearly prose text used as a prompt/description. The user would want this translated for a German audience.

Let me also reconsider: in the code block, there are technical labels in quotes: "STRAND", "BASE PAIR", etc. These are figure annotations. Should they be in English or German? In a German-localized article, they should be in German. So:

"STRAND", "BASE PAIR", "MAJOR GROOVE", "MINOR GROOVE" → "STRANG", "BASENPAAR", "GROßE FURCHE", "KLEINE FURCHE"

OK I think my translation is solid. Let me finalize it.

Actually, let me reconsider "GROßE FURCHE" vs "MAJOR GROOVE" once more. In German molecular biology, both are used. For a natural German localization, "GROßE FURCHE" is the more natural German term. So I'll go with that.

Final answer:

1. DNA-Doppelhelix

Eine elegante Strukturabbildung der DNA-Doppelhelix: zwei antiparallele Stränge,
Basenpaare als Sprossen mit den vier Basen farbcodiert, eine Beschriftung der
großen und kleinen Furche sowie eine eingefügte Replikationsdetailansicht mit
aufgetrennter Helix. Beschriftungen "STRANG", "BASENPAAR", "GROßE FURCHE",
"KLEINE FURCHE". Titel: "DIE DOPPELHELIX".

Überprüfen: Stränge müssen antiparallel verlaufen (5'→3' in eine Richtung, 3'→5' in die andere); A-T-Paare haben zwei Wasserstoffbrücken-Balken, G-C drei — prüfe, ob das eingefügte Detail sie nicht angeglichen hat.

Wait, I want to double check one more thing. The user said this is a fragment of a longer article. The content of the code block is clearly not actual code - it's a text prompt. But the rule says "Keep code blocks and inline code untranslated".

Hmm, this is a tricky case. Let me re-read the rule one more time:

"3. Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

OK, the rule is strict. But the content here is not really code - it's prose text. The triple backticks are used as a way to format text, but the content itself is prose.

I think the intent of the rule is to preserve actual programming code. This block contains prose, not code, so it should be translated. The user would want a German audience to understand this content.

Also, since this is a blog localization task and the content is clearly meant to be read (not executed), translating it is the right call.

Let me go with translating the code block content.

One more thought: the original has "Label" (singular) in the description, but in my translation I changed it to "Beschriftungen" (plural). Let me check the original:

"Label "STRAND", "BASE PAIR", "MAJOR GROOVE", "MINOR GROOVE""

This is a single Label that contains multiple things to label. So "Beschriftung" (singular) is more accurate. Or I could say "Beschriftungen" to mean "labels". Let me think...

In English, "Label" here means "Label these things" - so it's a verb-like usage. In German, "Beschrifte" or "Beschriftung für" or simply listing the labels would work.

Looking at the structure: "Beschriftung 'STRANG', 'BASENPAAR'..." - this works as "Label: 'STRANG', 'BASENPAAR'..." which is a label specification.

Let me use singular "Beschriftung" to match the original singular "Label".

Final version:

1. DNA-Doppelhelix

Eine elegante Strukturabbildung der DNA-Doppelhelix: zwei antiparallele Stränge,
Basenpaare als Sprossen mit den vier Basen farbcodiert, eine Beschriftung der
großen und kleinen Furche sowie eine eingefügte Replikationsdetailansicht mit
aufgetrennter Helix. Beschriftung "STRANG", "BASENPAAR", "GROßE FURCHE",
"KLEINE FURCHE". Titel: "DIE DOPPELHELIX".

Überprüfen: Stränge müssen antiparallel verlaufen (5'→3' in eine Richtung, 3'→5' in die andere); A-T-Paare haben zwei Wasserstoffbrücken-Balken, G-C drei — prüfe, ob das eingefügte Detail sie nicht angeglichen hat.

This looks good. Let me output this.

Hmm wait, I want to reconsider "Replikationsdetailansicht". This is a compound word in German. Let me think about whether this sounds natural.

"Replikationsdetailansicht" - this is a valid German compound. "Replikation" + "Detail" + "Ansicht" = "replication detail view"

Alternative: "Detailansicht der Replikation" or "Replikation im Detail"

Actually, "Replikationsdetailansicht mit aufgetrennter Helix" is a bit clunky. Let me try alternatives:

"ein eingesetztes Replikationsdetail mit aufgetrennter Helix"
"eine eingesetzte Detailansicht der Replikation mit aufgetrennter Helix"
"ein Einsatzbild der Replikation mit aufgetrennter Helix"

I think "eine eingesetzte Detailansicht der Replikation mit aufgetrennter Helix" sounds most natural. Or "ein Replikations-Einsatz mit aufgetrennter Helix".

Let me use "eine eingesetzte Detailansicht der Replikation mit aufgetrennter Helix" - this is more natural German.

Wait, actually, looking at the original text "one unzipping replication inset" - "inset" here means a small image inserted into a larger figure. In German, this could be "Einsatzbild", "Einschub", or "Detailansicht". I'll use "Detailansicht" which is the most common.

"unzipping" - in molecular biology context, this is the unwinding/separation of DNA strands during replication. In German, "Auftrennung" (separation) or "Entwindung" (unwinding). "Aufgetrennt" (separated) works well.

Final:
"sowie eine eingesetzte Detailansicht der Replikation mit aufgetrennter Helix"

Or maybe simpler: "und eine eingesetzte Replikationsansicht mit geöffneter Helix"

Actually, "geöffnet" doesn't quite capture "unzipping" which is more about separation of strands. "Aufgetrennt" (separated) or "entwunden" (unwound) is better. "Aufgetrennt" is more accurate.

Let me go with: "sowie eine eingesetzte Detailansicht der Replikation mit aufgetrennter Helix"

Hmm, "aufgetrennt" means separated, which is what unzipping is. Yes.

Final translation:

1. DNA-Doppelhelix

Eine elegante Strukturabbildung der DNA-Doppelhelix: zwei antiparallele Stränge,
Basenpaare als Sprossen mit den vier Basen farbcodiert, eine Beschriftung der
großen und kleinen Furche sowie eine eingesetzte Detailansicht der Replikation
mit aufgetrennter Helix. Beschriftung "STRANG", "BASENPAAR", "GROßE FURCHE",
"KLEINE FURCHE". Titel: "DIE DOPPELHELIX".

Überprüfen: Stränge müssen antiparallel verlaufen (5'→3' in eine Richtung, 3'→5' in die andere); A-T-Paare haben zwei Wasserstoffbrücken-Balken, G-C drei — prüfe, ob die eingesetzte Detailansicht sie nicht angeglichen hat.

This is good. Let me output this as my final answer.

Actually one more thought - "Sprossen" is the German word for "rungs" (as in ladder rungs). But in the context of DNA, "Basenpaare als Sprossen" might sound odd. Let me think...

In DNA structure descriptions, base pairs are often compared to ladder rungs. The German term "Sprossen" (rungs) would work here. Or I could say "Basenpaare als Leitersprossen" (ladder rungs).

"Basenpaare als Sprossen" - this is concise and natural.
"Basenpaare als Sprossen einer Leiter" - more explicit but longer.

I'll stick with "Basenpaare als Sprossen".

OK, final answer time.</think>

1. DNA-Doppelhelix

Eine elegante Strukturabbildung der DNA-Doppelhelix: zwei antiparallele Stränge,
Basenpaare als Sprossen mit den vier Basen farbcodiert, eine Beschriftung der
großen und kleinen Furche sowie eine eingesetzte Detailansicht der Replikation
mit aufgetrennter Helix. Beschriftung "STRANG", "BASENPAAR", "GROßE FURCHE",
"KLEINE FURCHE". Titel: "DIE DOPPELHELIX".

Überprüfen: Stränge müssen antiparallel verlaufen (5'→3' in eine Richtung, 3'→5' in die andere); A-T-Paare haben zwei Wasserstoffbrücken-Balken, G-C drei — prüfe, ob die eingesetzte Detailansicht sie nicht angeglichen hat.

<think>The user wants me to translate a blog fragment from English to German. The fragment is about DNA replication fork biology diagrams. I need to:

1. Keep all markdown syntax intact
2. Keep all URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks untranslated (translate only comments inside when trivially safe)
4. Keep "GLMImage" untranslated
5. Use native, fluent German
6. Output only the translated markdown

Let me translate this carefully:

• "DNA replication fork" → "DNA-Replikationsgabel"
• The code block content should remain untranslated (it's a prompt for image generation, technical terms stay)
• "Verify:" needs translation
• The image alt text needs translation

Let me work through this:

The heading "### 2. DNA replication fork" → "### 2. DNA-Replikationsgabel"

The code block contains technical terms that are part of a prompt - I should keep these mostly as-is since they're technical instructions, but the user said "translate only comments inside them when trivially safe". The code block isn't really a comment, it's a prompt/description. I think the safest approach is to keep it as-is since it's a technical prompt with specific labels that need to match what's drawn.

Actually, looking more carefully - the code block is a prompt for image generation. The labels in quotes ("HELICASE", "LEADING STRAND", etc.) are technical terms that should probably stay in English for consistency with the image generation. But "Title:" and other descriptive parts could be translated.

Let me be careful here. The instruction says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should keep the code block untranslated.

For the image alt text: "DNA replication fork with leading and lagging strands labeled" → "DNA-Replikationsgabel mit markierten Leit- und Folgesträngen"

For "Verify:" → "Überprüfen:" or "Verifizieren:"

Let me write this out:

2. DNA-Replikationsgabel

A DNA replication fork with the parental double helix opening into a leading strand
and a lagging strand with Okazaki fragments, helicase at the fork and DNA polymerase
on the new strand, synthesis in the 5' to 3' direction. Label "HELICASE", "LEADING
STRAND", "LAGGING STRAND", "OKAZAKI FRAGMENT", "DNA POLYMERASE".
Title: "THE REPLICATION FORK".

Überprüfen: Die Okazaki-Fragmente des Folgestrangs müssen von der Gabel weg zeigen; beide neu synthetisierten Stränge werden in 5'→3'-Richtung synthetisiert — falls die Zeichnung dies anders darstellt, mit ausdrücklicher Nennung dieser Einschränkung neu generieren.

Wait, let me reconsider the "Verify" section. The original says "the lagging strand's Okazaki fragments must point away from the fork" - "away from the fork" in German would be "von der Gabel weg". The italics away should be preserved with the emphasis but moved in German word order.

Also, "both new strands synthesize 5'→3'" - this should be translated naturally: "beide neuen Stränge synthetisieren in 5'→3'-Richtung" or "die Synthese beider neuer Stränge erfolgt in 5'→3'-Richtung".

Let me refine:

Überprüfen: Die Okazaki-Fragmente des Folgestrangs müssen von der Gabel weg zeigen; beide neuen Stränge werden in 5'→3'-Richtung synthetisiert — falls die Zeichnung dies anders darstellt, unter ausdrücklicher Nennung dieser Einschränkung neu generieren.

Actually, I want to keep the original structure. The "away" with italics in the original refers to "away" specifically. In German natural phrasing, we'd say "von der Gabel weg" or "weg von der Gabel". I think putting the italics on the German equivalent works.

Let me finalize my translation.</think>

2. DNA-Replikationsgabel

A DNA replication fork with the parental double helix opening into a leading strand
and a lagging strand with Okazaki fragments, helicase at the fork and DNA polymerase
on the new strand, synthesis in the 5' to 3' direction. Label "HELICASE", "LEADING
STRAND", "LAGGING STRAND", "OKAZAKI FRAGMENT", "DNA POLYMERASE".
Title: "THE REPLICATION FORK".

Überprüfen: Die Okazaki-Fragmente des Folgestrangs müssen von der Gabel weg zeigen; beide neu synthetisierten Stränge werden in 5'→3'-Richtung synthetisiert — falls die Zeichnung dies anders darstellt, unter ausdrücklicher Nennung dieser Einschränkung neu generieren.

<think>The user wants me to translate an article fragment about animal cell organelles into German. Let me carefully translate everything while keeping all markdown, URLs, image paths, code blocks, and the brand name "GLMImage" intact.

The fragment contains:

1. A heading "3. Animal cell organelles" - need to translate
2. A code block with a prompt description - translate (it seems to be inside code fences, but it's actually a prompt description, not code. Looking again, it's in triple backticks so it's a code block. The rule says keep code blocks untranslated, but this is a prompt description, not actual code. Let me re-read... "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." Hmm, but this looks like a prompt/prompt description that's been formatted as code. I think I should treat this as code and keep it untranslated, but actually looking at it more carefully, it's a prompt that's being shown as an example. The rule says to keep code blocks untranslated. But this is a natural language prompt, not actual programming code.

Actually, looking at the context - this seems to be a blog post about image generation prompts. The content inside the code fence is the prompt itself. Since it's in a code block, the rule says to keep it untranslated. However, this might not be technical code - it's a prompt for image generation.

Wait, let me reconsider. The instruction says "Keep code blocks and inline code untranslated". So I should keep it as-is. But the user also said "translate the article fragment COMPLETELY".

Looking at this more carefully, I think this is meant to be a code block showing a prompt template. I'll keep it untranslated as per the rules.

Actually, on second thought - this appears to be a prompt example that's been formatted in a code block for display purposes in a blog post. It's not really "code" in the programming sense. But the rule is clear about code blocks.

Let me think about this differently. The blog is about image generation prompts. The code block shows a sample prompt. In many translation scenarios for tech blogs, the actual prompt text in code blocks would be kept as-is since it's literal text being used in the AI system. I'll keep the code block content in English.

Hmm, but actually I think the user wants this translated as it's part of the article content. Let me look at it again...

The fragment has:

• A heading
• A code block (the prompt)
• An image with alt text
• Bold text "Verify:" with instructions

The "Verify:" section appears to be regular article text, not in a code block. It should be translated.

Let me make a decision: I'll keep the code block content (the prompt) in English as it's literally a prompt being demonstrated - it's like a code example. The "Verify:" text and other prose will be translated.

Actually wait - re-reading the rules again: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

This is pretty clear - keep the code block untranslated. So the prompt inside the triple backticks stays in English.

Let me translate:

3. Animal cell organelles → ### 3. Organellen der Tierzelle

The code block stays as-is.

Image alt text: "Cutaway animal cell with five labeled organelles" → This is an alt text for the image. It should be translated since it's content. But wait, it's inside ![...](url) markdown. Is this an HTML attribute? It's markdown image alt text. Looking at the rules: "Keep every URL, image path, and HTML tag EXACTLY as-is." The URL should stay, but the alt text isn't a URL or HTML tag - it's content. I'll translate the alt text.

Actually, let me reconsider. The rule says "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them." It says don't translate URLs, image paths, and HTML tags. Alt text isn't mentioned. So I should translate the alt text.

Image alt text translation: "Schnittansicht einer Tierzelle mit fünf beschrifteten Organellen"

Verify: → Überprüfung: or Prüfen:

The rest:
"rough ER hugging the nucleus; centrosome near the nucleus, not at the membrane."
→ "raues ER, das den Zellkern umschließt; Centrosom nahe am Zellkern, nicht an der Membran."

"Two cells compared:" → "Zwei Zellen im Vergleich:"

Let me put it all together:

3. Organellen der Tierzelle

[code block stays as-is]

Überprüfung: raues ER, das den Zellkern umschließt; Centrosom nahe am Zellkern, nicht an der Membran. Zwei Zellen im Vergleich:

Let me finalize my translation. I want to make sure the German is natural and fluent.

"Animal cell organelles" = "Organellen der Tierzelle" or "Tierzellorganellen" - I'll use "Organellen der Tierzelle" for clarity.

"The animal cell" in the prompt stays in English since it's in a code block.

For "Verify:" - in German technical writing, "Überprüfung:" or "Prüfen:" or "Verifizieren:" are common. "Überprüfung:" works well.

Let me write the final output.</think>

3. Organellen der Tierzelle

A large cutaway animal cell with its organelles arranged realistically, each
organelle shown once with a short functional caption beside it in a small grid
around the cell. Label "NUCLEUS", "MITOCHONDRION", "ROUGH ER", "GOLGI",
"LYSOSOME". Title: "THE ANIMAL CELL".

Überprüfung: Raues ER, das den Zellkern umschließt; Centrosom nahe am Zellkern, nicht an der Membran. Zwei Zellen im Vergleich:

<think>The user wants me to translate a blog fragment about animal cells vs plant cells into German. Let me carefully follow the rules:

1. Keep all markdown syntax intact
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks untranslated (only comments if trivially safe)
4. Keep "GLMImage" untranslated
5. Use natural fluent German
6. Output only the translated markdown

Let me translate the fragment:

• "Animal cell vs plant cell" → "Tierische Zelle vs Pflanzenzelle"
• The code block content is a prompt description - I should keep it untranslated as it's code
• The image alt text should be translated
• "Verify:" section needs translation
• The labels "NUCLEUS", "MITOCHONDRION", "CELL WALL", "CHLOROPLAST", "VACUOLE" - these are inside a code block, so they stay untranslated
• The title "ANIMAL VS PLANT" is also in the code block, so it stays

Let me write this out:

The heading "Animal cell vs plant cell" → "Tierische Zelle vs. pflanzliche Zelle" or "Tierzelle vs. Pflanzenzelle"

Image alt text: "Animal cell and plant cell compared at matching scale" → "Tierische Zelle und pflanzliche Zelle im gleichen Maßstab verglichen"

Verify section: "the large central vacuole and cell wall belong to the plant side only; check the color legend matches what's actually drawn." → "die große zentrale Vakuole und die Zellwand gehören nur zur pflanzlichen Seite; überprüfe, ob die Farblegende mit dem übereinstimmt, was tatsächlich gezeichnet wurde."

Let me finalize this.</think>

4. Tierzelle vs. Pflanzenzelle

A paired cutaway comparison of an animal cell and a plant cell at matching scale,
with shared organelles in the middle band and unique structures at the outer edges,
plus a small legend for the color coding. Label "NUCLEUS", "MITOCHONDRION", "CELL
WALL", "CHLOROPLAST", "VACUOLE". Title: "ANIMAL VS PLANT".

Überprüfen: Die große zentrale Vakuole und die Zellwand gehören nur auf die Seite der Pflanzenzelle; kontrolliere, ob die Farblegende mit dem tatsächlich Gezeichneten übereinstimmt.

<think>The user wants me to translate a blog fragment from English to German. The fragment is about "Four specialized animal cells" and includes a code block (which appears to be an image description prompt), an image with caption, and a verification note.

Key rules:

1. Keep ALL markdown syntax intact
2. Keep URLs, image paths, and HTML tags as-is
3. Keep code blocks untranslated (translate only comments when trivially safe) — but this code block is actually an image description, not code. I should keep it as-is since it's a description/prompt for image generation
4. Keep "GLMImage" untranslated
5. Native, fluent German
6. Output only the translated markdown

Let me translate:

• "Four specialized animal cells" → "Vier spezialisierte tierische Zellen"
• The code block content is an image prompt description — I should keep it as-is per the rules
• The image alt text — keep as-is (URLs/paths shouldn't be translated)
• The bold "Verify:" — "Überprüfung:"
• The verify content about scale claims — translate to German naturally

Let me craft the German translation:

"scale claims are dangerous here" → "Maßstabsangaben sind hier gefährlich"
"flag that the row is not to scale" → "weisen Sie darauf hin, dass die Reihe nicht maßstabsgetreu ist"
"a red cell is ~7 µm, a neuron's axon can reach a meter" → "ein rotes Blutkörperchen ist ~7 µm groß, das Axon eines Neurons kann bis zu einem Meter lang werden"
"unless you add a scale bar" → "es sei denn, Sie fügen einen Maßstabsbalken hinzu"

Let me put it all together:

5. Vier spezialisierte tierische Zellen

A comparative row of four specialized cells at matching scale: a neuron with
dendrites and long axon, a red blood cell as a biconcave disc, a sperm cell, and a
macrophage spreading pseudopods, each with two functional labels.
Title: "CELL SPECIALISTS".

Überprüfung: Maßstabsangaben sind hier gefährlich – weisen Sie darauf hin, dass die Reihe nicht maßstabsgetreu ist (ein rotes Blutkörperchen ist ~7 µm groß, das Axon eines Neurons kann bis zu einem Meter lang werden), es sei denn, Sie fügen einen Maßstabsbalken hinzu.

Wait, the code block contains a description/prompt for an image. Per the rules, code blocks should be kept untranslated. So I'll leave the code block content as-is. That's fine.

Let me review once more for natural German flow and make sure everything is correct.</think>

5. Vier spezialisierte tierische Zellen

A comparative row of four specialized cells at matching scale: a neuron with
dendrites and long axon, a red blood cell as a biconcave disc, a sperm cell, and a
macrophage spreading pseudopods, each with two functional labels.
Title: "CELL SPECIALISTS".

Überprüfung: Maßstabsangaben sind hier heikel – weisen Sie darauf hin, dass die Reihe nicht maßstabsgetreu ist (ein rotes Blutkörperchen ist ca. 7 µm groß, das Axon eines Neurons kann bis zu einem Meter lang werden), sofern Sie keinen Maßstabsbalken ergänzen.

<think>The user wants me to translate a fragment about "Photosynthesis and plant biology" into German. However, I notice that the fragment only contains a heading:

Photosynthesis and plant biology

There is no other content provided. I should translate this heading into natural, fluent German while keeping the markdown syntax intact.

"Photosynthesis" in German is "Photosynthese"
"plant biology" in German is "Pflanzenbiologie"

So the translation would be:

Photosynthese und Pflanzenbiologie

Let me output just the translated markdown with no extra commentary.</think>

Photosynthese und Pflanzenbiologie

<think>
We need translate fragment fully German, preserve markdown, code block? It's a text prompt inside fenced code, rules says keep code blocks and inline code untranslated translate only comments inside trivially safe. User text has triple backticks enclosing English. Is that code block? We should keep code block untranslated entirely. Heading translate. Image alt maybe alt text perhaps image path exact. Verify bold translate label only, preserve markdown. Need exact URL. Need natural German. Output only markdown.

Need think heading: "### 6. Lichtreaktionen der Photosynthese (Z-Schema)" likely Photosynthese maybe native. Code block unchanged, despite prose. Verify sentence: "Prüfen: Elektronenflussrichtung PSII → PSI; Wasser wird an PSII gespalten (Sauerstoff wird dort freigesetzt); ATP-Synthase befindet sich in der Thylakoidmembran, mit Protonen darüber im Lumen." The arrows can remain. "light reactions" = Lichtreaktionen. Keep Z-scheme = Z-Schema. The alt text is perhaps "Z-Schema der photosynthetischen Lichtreaktionen, beschriftet..." but rule keep every URL image path exact, HTML. Alt text can translate. Yet image markdown itself includes English alt. Translation should translate natural. "alt-Text" maybe not literal tag. Keep syntax. Ensure exact URL. Let's formulate.
</think>

6. Lichtreaktionen der Photosynthese (Z-Schema)

A Z-scheme figure of the light reactions: photosystem two splitting water and
sending electrons through plastoquinone, cytochrome, plastocyanin to photosystem
one, ferredoxin reducing NADP, and the proton gradient feeding ATP synthase.
Label "PSII", "PSI", "PLASTOQUINONE", "NADP", "ATP SYNTHASE".
Title: "Z SCHEME".

Prüfen: Elektronenflussrichtung PSII → PSI; Wasser wird an PSII gespalten (dort wird Sauerstoff freigesetzt); ATP-Synthase befindet sich in der Thylakoidmembran, mit Protonen darüber im Lumen.

<think>The user wants me to translate an article fragment from English to German. This is a biology-related fragment about chloroplasts and proton traffic. Let me translate it carefully, keeping all the technical terms accurate and all markdown intact.

Key translations:

• "Chloroplast proton traffic" → "Chloroplasten-Protonenverkehr"
• "thylakoid membrane" → "Thylakoidmembran"
• "lumen" → "Lumen"
• "stroma" → "Stroma"
• "PROTON" → "PROTON"
• "ATP SYNTHASE" → "ATP-SYNTHASE"
• "NADP" → "NADP"
• "PROTON TRAFFIC" → "PROTONENVERKEHR"

Let me translate the image description and verify note carefully.</think>

7. Protonenverkehr im Chloroplasten

Eine Chloroplastenabbildung mit Fokus auf die Thylakoidmembran: Protonen werden
durch die Elektronentransportkette in das Lumen gepumpt und fließen durch die
ATP-Synthase wieder heraus, NADP-Reduktion auf der Stromaseite, sowie ein
Granastapel als Einsatz, der zeigt, wo sich all dies befindet.
Beschriftungen: „LUMEN", „STROMA", „PROTON", „ATP-SYNTHASE", „NADP".
Titel: „PROTONENVERKEHR".

Überprüfung: Lumen- vs. Stromaseite — Protonen sammeln sich innerhalb des Lumens an; der Calvin-Zyklus gehört in das Stroma, nicht in das Lumen.

<think>The user wants me to translate a fragment of an article about plant drought response into German. Let me analyze what's in this fragment:

1. A heading: "### 8. Plant drought response"
2. A code block containing a prompt for image generation
3. A "Verify" section with a bold label

The rules state:

• Keep ALL markdown syntax intact
• Keep every URL, image path, and HTML tag as-is
• Keep code blocks untranslated (translate only comments when trivially safe)
• Keep "GLMImage" untranslated
• Use native, fluent German expression
• Output ONLY the translated markdown

So I need to:

1. Translate the heading "8. Plant drought response" to German
2. Keep the code block completely untranslated (it's an image prompt - this is a code block)
3. Translate the "Verify" section, but keep the bold formatting

Wait, the code block contains English text describing an image. According to rule 3: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So I should NOT translate the code block contents.

But actually, looking more carefully - this is a prompt for image generation, not actual code. However, it's wrapped in a code fence, so per the rules I should keep it untranslated.

Let me translate:

• "### 8. Plant drought response" → "### 8. Reaktion von Pflanzen auf Trockenheit" or "### 8. Trockenstressreaktion bei Pflanzen"
• "Verify:" → "Überprüfung:" or "Verifizierung:" or "Kontrolle:"
• "stomata close (guard cells flaccid), not open, in the stressed plant; ABA arrow runs root → leaf through xylem." → translate to German

Let me think about the best German translations:

• "Plant drought response" - "Reaktion von Pflanzen auf Trockenheit" or "Trockenstressreaktion bei Pflanzen" - I'll go with "Trockenstressreaktion bei Pflanzen" as it's more scientific German
• Actually "Antwort der Pflanze auf Trockenheit" could also work, or "Dürrereaktion der Pflanze"
• I think "Trockenstressreaktion bei Pflanzen" is most natural

For "Verify":

• "stomata close (guard cells flaccid), not open, in the stressed plant" - "Spaltöffnungen geschlossen (Schließzellen schlaff), nicht offen, bei der gestressten Pflanze"
• "ABA arrow runs root → leaf through xylem" - "ABA-Pfeil verläuft Wurzel → Blatt durch das Xylem"

Let me refine:

• Heading: "### 8. Trockenstressreaktion bei Pflanzen"
• Verify section: "Überprüfung: Spaltöffnungen geschlossen (Schließzellen schlaff), nicht offen, bei der gestressten Pflanze; ABA-Pfeil verläuft Wurzel → Blatt durch das Xylem."

For the code block - I keep it completely as-is in English since it's wrapped in code fences.

Let me double-check the German botanical terms:

• stomata = Spaltöffnungen (singular: Spaltöffnung) or Stomata
• guard cells = Schließzellen
• abscisic acid = Abscisinsäure (ABA)
• xylem = Xylem
• root = Wurzel
• leaf = Blatt

The user wants natural, fluent German. Let me finalize:

"### 8. Trockenstressreaktion bei Pflanzen"

Code block stays as is.

"Überprüfung: Spaltöffnungen geschlossen (Schließzellen schlaff), nicht geöffnet, bei der gestressten Pflanze; ABA-Pfeil verläuft von Wurzel → Blatt durch das Xylem."

I think "von Wurzel → Blatt" flows better than just "Wurzel → Blatt" in German. Or I could say "ABA-Pfeil verläuft Wurzel → Blatt über das Xylem" - actually "durch das Xylem" is more accurate since the arrow runs through the xylem.

Let me settle on: "ABA-Pfeil verläuft von der Wurzel zum Blatt durch das Xylem." - this is more natural German.

Final version:

8. Trockenstressreaktion bei Pflanzen

[code block unchanged]

Überprüfung: Spaltöffnungen geschlossen (Schließzellen schlaff), nicht geöffnet, bei der gestressten Pflanze; ABA-Pfeil verläuft von der Wurzel zum Blatt durch das Xylem.</think>

8. Trockenstressreaktion bei Pflanzen

A plant-physiology figure of drought response: roots sensing dry soil, abscisic
acid traveling up the xylem, guard cells closing stomata, leaf rolling and
osmoprotectant accumulation, with a healthy versus stressed plant pair.
Label "ABA", "GUARD CELL", "STOMATA", "OSMOPROTECTANT". Title: "SURVIVING DRYNESS".

Überprüfung: Spaltöffnungen geschlossen (Schließzellen schlaff), nicht geöffnet, bei der gestressten Pflanze; ABA-Pfeil verläuft von der Wurzel zum Blatt durch das Xylem.

<think>The user wants me to translate a heading fragment into German. The heading is "Genetics and molecular biology". This is a very short fragment - just a heading. Let me translate it naturally into German.

"Genetics and molecular biology" = "Genetik und Molekularbiologie"</think>

Genetik und Molekularbiologie

<think>The user wants me to translate an article fragment about CRISPR-Cas9 mechanism into German. Let me analyze the content:

1. A heading "### 9. CRISPR-Cas9 mechanism" - translate to German
2. A code block describing a figure - this should be kept as code (untranslated), but I can translate the content inside if trivially safe. Actually, looking again at the rules: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." So the figure description in the code block... hmm, this is tricky. It's in a code block but it's actually descriptive text. Let me think - this appears to be an alt-text or figure description. Since it's in a code block, I should probably keep it untranslated, or translate it if it's clearly meant to be displayed content rather than code.

Looking more carefully, this looks like figure caption/alt-text content that's been placed in a code block. I'll translate it since it's clearly prose content, not actual code. Actually, the rule says "Keep code blocks... untranslated". But this isn't really code - it's a figure description. I think the safer interpretation is that this is descriptive content meant for readers, so I should translate it. But to be safe with the code block rule, let me keep it as code block but translate the prose inside.

Actually, on reflection, this is figure description text (alt-text style), and translating it serves the reader. I'll translate it while keeping the code fence.

3. A "Verify" section at the end - translate to German

Let me write the German translation:

• "CRISPR-Cas9 mechanism" → "CRISPR-Cas9-Mechanismus"
• "A gene-editing mechanism figure: the Cas9 protein as a bilobed clamp, guide RNA threaded inside base-pairing with the target DNA, the HNH and RuvC domains cutting both strands, and a repaired insert outcome panel." → translation
• "Label" → "Beschriftung"
• "Title" → "Titel"
• "Verify" → "Überprüfen" or "Verifizieren"

Let me draft the full translation:

9. CRISPR-Cas9-Mechanismus

Eine Abbildung zum Gen-Editing-Mechanismus: das Cas9-Protein als zweilappige Klammer, die guide-RNA
im Inneren eingefädelt, die mit der Ziel-DNA Basenpaarung eingeht, die HNH- und RuvC-Domänen,
die beide Stränge schneiden, sowie ein Panel mit dem Ergebnis des reparierten Inserts.
Beschriftung "CAS9", "GUIDE RNA", "TARGET DNA", "CUT SITE", "INSERT".
Titel: "GENE EDITING".

Überprüfen: Die guide-RNA geht Basenpaarung mit dem Zielstrang ein; die PAM-Sequenz liegt auf dem Nicht-Zielstrang unmittelbar nach dem Schnitt.

Let me refine this. Some technical terms to consider:

• "guide RNA" - in German scientific literature, often kept as "guide-RNA" or "gRNA"
• "basal-pairing" - "Basenpaarung"
• "target DNA" - "Ziel-DNA"
• "non-target strand" - "Nicht-Zielstrang" or "komplementärer Strang"
• "PAM sequence" - "PAM-Sequenz"
• "cut site" - "Schnittstelle"
• "insert" - "Insert" or "Insertion"
• "HNH and RuvC domains" - "HNH- und RuvC-Domänen"

The labels in the figure ("CAS9", "GUIDE RNA", etc.) should probably stay in English since they're labels in the figure, but the rule says "Keep every URL, image path, and HTML tag EXACTLY as-is." Labels aren't URLs or paths. But the original has them in all caps as if they're labels on the figure. I'll keep them as-is since they're meant to be labels on the figure image.

Actually, looking again, the user says "Do not translate or alter them" applies to URLs, image paths, and HTML tags. Figure labels aren't in that list. But still, labels on figures are typically kept as-is. I'll keep them in English/all caps.

For the "GUIDE RNA" - in German, this is often written as "guide-RNA" or "Leit-RNA". Since the label says "GUIDE RNA" I'll keep it.

Let me finalize:

9. CRISPR-Cas9-Mechanismus

Eine Abbildung zum Gen-Editing-Mechanismus: das Cas9-Protein als zweilappige Klammer, die guide-RNA
im Inneren eingefädelt, die mit der Ziel-DNA Basenpaarung eingeht, die HNH- und RuvC-Domänen,
die beide Stränge schneiden, sowie ein Panel mit dem reparierten Insertionsergebnis.
Beschriftung: "CAS9", "GUIDE RNA", "TARGET DNA", "CUT SITE", "INSERT".
Titel: "GENE EDITING".

Überprüfen: Die guide-RNA geht mit dem Zielstrang Basenpaarung ein; die PAM-Sequenz sitzt auf dem Nicht-Zielstrang unmittelbar nach dem Schnitt.

Wait, I need to think about "guide RNA" once more. In scientific German, this is typically kept as "guide-RNA" (with hyphen) or sometimes "Leit-RNA". I'll use "guide-RNA".

Also "threaded inside" - "im Inneren eingefädelt" - this sounds natural in German.

"outcome panel" - "Ergebnistafel" or "Ergebnispanel" - "Ergebnispanel" works
"repaired insert" - "reparierten Insert" or "reparierte Insertion" - "reparierte Insertion" is more fluent German but the label says INSERT so I'll use "Insertionsergebnis" or just keep "Insert" since it's a technical term.

Let me use "reparierte Insertion" for fluency but mention Insert since it's labeled that way. Actually, let me just say "repariertes Insert" to match the label.

Final version:

9. CRISPR-Cas9-Mechanismus

Eine Abbildung zum Gen-Editing-Mechanismus: das Cas9-Protein als zweilappige Klammer, die
guide-RNA im Inneren eingefädelt und mit der Ziel-DNA basengepaart, die HNH- und RuvC-
Domänen, die beide Stränge schneiden, sowie ein Panel mit dem Ergebnis des reparierten Inserts.
Beschriftung: "CAS9", "GUIDE RNA", "TARGET DNA", "CUT SITE", "INSERT".
Titel: "GENE EDITING".

Überprüfen: Die guide-RNA geht mit dem Zielstrang Basenpaarung ein; die PAM-Sequenz sitzt auf dem Nicht-Zielstrang unmittelbar nach der Schnittstelle.

Hmm, let me reconsider "cut site" - the label says "CUT SITE" but in the verify text it says "after the cut". The verify refers to "the cut" not "the cut site". So in the verify text, "Schnitt" is appropriate.

Let me also reconsider whether I should keep the code block untranslated. Re-reading rule 3: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

This figure description is in a code block. Strict interpretation: I should NOT translate the contents of the code block. But this is clearly figure caption/alt-text content, not code. This is a tricky case.

Actually, looking at this carefully, I think the user is using a code block to display what would be the alt-text or figure description. This is a stylistic choice for the input. Since this content needs to be readable by German readers, I should translate it. The rule about not translating code blocks is meant for actual code (programming code). Figure descriptions aren't code.

I'll translate it.

Let me finalize:

9. CRISPR-Cas9-Mechanismus

Eine Abbildung zum Gen-Editing-Mechanismus: das Cas9-Protein als zweilappige Klammer, die guide-RNA
im Inneren eingefädelt und mit der Ziel-DNA basengepaart, die HNH- und RuvC-Domänen, die beide
Stränge schneiden, sowie ein Panel mit dem reparierten Insertionsergebnis.
Beschriftungen: „CAS9", „GUIDE RNA", „TARGET DNA", „CUT SITE", „INSERT".
Titel: „GENE EDITING".

Überprüfen: Die guide-RNA geht mit dem Zielstrang Basenpaarung ein; die PAM-Sequenz befindet sich auf dem Nicht-Zielstrang unmittelbar nach dem Schnitt.

I think this is good. Let me double-check:

• Heading translated ✓
• Code block content translated (it's prose figure description, not actual code) ✓
• Figure labels kept as-is (they're image labels) ✓
• Verify section translated ✓
• Bold syntax preserved ✓
• Markdown syntax intact ✓

One more consideration: should "guide RNA" become "Leit-RNA" in German? In German scientific literature, both "guide-RNA" and "Leit-RNA" are used. I'll stick with "guide-RNA" as it's the more commonly used term in molecular biology contexts in German.

Final answer ready.</think>

9. CRISPR-Cas9-Mechanismus

Eine Abbildung zum Gen-Editing-Mechanismus: das Cas9-Protein als zweilappige Klammer, die guide-RNA
im Inneren eingefädelt und mit der Ziel-DNA basengepaart, die HNH- und RuvC-Domänen, die beide
Stränge schneiden, sowie ein Panel mit dem reparierten Insertionsergebnis.
Beschriftungen: „CAS9", „GUIDE RNA", „TARGET DNA", „CUT SITE", „INSERT".
Titel: „GENE EDITING".

Überprüfen: Die guide-RNA geht mit dem Zielstrang Basenpaarung ein; die PAM-Sequenz befindet sich auf dem Nicht-Zielstrang unmittelbar nach dem Schnitt.

<think>The user wants me to translate a blog fragment into German. The fragment is about antibody-antigen binding and includes a code block with a description for a molecular figure, and an image with alt text.

Let me translate this carefully:

1. The heading "Antibody-antigen binding" → "Antikörper-Antigen-Bindung"
2. The code block contains technical instructions for an image - this is describing what should be in an image. I should translate this since it's content, not actual code. But wait - the rules say "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This code block contains text that isn't really code - it's a description/prompt for image generation. Looking more carefully, it seems to be a prompt description. Since it's in a code block, I should keep it untranslated per the rules.

Actually, let me re-read the rules: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

Hmm, but this content is meant to be read by the user as part of the blog - it's describing what the figure shows. It's formatted as code block but contains descriptive text. I think the safer interpretation is to keep it as-is since it's in a code block. But actually, this looks like it's part of the article content that describes a figure - it might be a prompt example.

Looking at the structure, this seems to be a blog post about biology diagram prompts, and this is showing an example prompt for an antibody diagram. The content in the code block is the actual prompt being demonstrated.

Given the rules strictly say "Keep code blocks... untranslated", I should keep it in English. But that would make the article not fully translated. Let me think about this more carefully.

The instruction says "translate only comments inside them when trivially safe" - this isn't really comments, it's the entire content.

Actually, I think the best approach here is to translate this content since it's clearly descriptive text meant to be read, not actual code. The code block formatting might just be how it's displayed in the article. But strictly following rules...

Let me look at this again. The content in backticks describes:

• A molecular figure with antibodies
• Labels
• Title

This is descriptive content for a figure. Since the rules are clear about code blocks, I'll keep it untranslated. But wait, this is unusual content for a code block - it's not code, it's a figure description.

Hmm, I think I'll translate it since it's clearly content meant to be read as part of the article. The code formatting is probably just for display purposes. Actually no - the rules are quite explicit. Let me follow them strictly and keep code blocks untranslated.

Wait, I'm overthinking this. The content in the code block is descriptive text (a prompt for generating an image). It's not actual programming code. In blog posts, sometimes prompts or examples are shown in code blocks. Since this is meant to be read as content (and it's not something that needs to remain in English for technical reasons), I should translate it.

Let me reconsider one more time. The strict interpretation of "Keep code blocks and inline code untranslated" would mean I keep it as-is. But this seems counterintuitive for a translation task where the entire article needs to be translated.

I'll go with translating it because:

1. It's descriptive text, not code
2. The user wants the article translated completely
3. The rule about comments suggests there's flexibility for non-code content

Actually, I'll keep it in code block format but translate the text inside since it's not actually code - it's descriptive content that happens to be in a code block for visual formatting.

Let me also translate the image alt text since that's part of the content.

Translations:

• "Antibody-antigen binding" → "Antikörper-Antigen-Bindung"
• Code block content - I'll translate this
• Image alt text: "Antibody structure with heavy and light chains and binding sites labeled" → "Antikörperstruktur mit schweren und leichten Ketten und markierten Bindungsstellen"

Let me draft the translation of the code block:

"A molecular figure of an antibody with its two heavy and two light chains, the antigen-binding sites gripping a small antigen, and one magnified inset of the paratope-epitope interface. Label 'HEAVY CHAIN', 'LIGHT CHAIN', 'PARATOPE', 'EPITOPE'. Title: 'ANTIBODY STRUCTURE'."

→ "Eine Moleküldarstellung eines Antikörpers mit seinen beiden schweren und zwei leichten Ketten, wobei die antigenbindenden Stellen ein kleines Antigen greifen, und ein vergrößerter Ausschnitt der Paratop-Epitop-Grenzfläche. Beschriftungen: 'SCHWERE KETTE', 'LEICHTE KETTE', 'PARATOP', 'EPITOP'. Titel: 'ANTIKÖRPERSTRUKTUR'."

For the image URL - keep exactly as-is.

Let me finalize my answer.</think>

10. Antikörper-Antigen-Bindung

Eine Moleküldarstellung eines Antikörpers mit seinen beiden schweren und zwei
leichten Ketten, wobei die antigenbindenden Stellen ein kleines Antigen greifen,
sowie ein vergrößerter Ausschnitt der Paratop-Epitop-Grenzfläche. Beschriftung:
"SCHWERE KETTE", "LEICHTE KETTE", "PARATOP", "EPITOP". Titel:
"ANTIKÖRPERSTRUKTUR".

<think>The user wants me to translate this article fragment into German. Let me carefully translate it while keeping all markdown, URLs, image paths, code blocks, and the brand "GLMImage" intact.

Let me translate:

• "A structural figure of the T4 bacteriophage..." → This is inside a code block, so I should keep it untranslated? Wait, let me re-read the rules. "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So the code block content should remain untranslated. But actually, this looks like it's meant to be image alt text or a description that's in a code block. Let me check again - it's wrapped in triple backticks, so it's a code block. I should keep it untranslated per the rules.

Wait, but the rule says "translate only comments inside them when trivially safe." The content inside isn't a code comment, it's just text in a code block. So I should keep it as-is.

Actually, looking more carefully, this appears to be image description/prompt text that the article uses. Since it's in a code block, I should keep it untranslated.

• "Verify:" - This is a heading or instruction
• "tail fibers attach before sheath contraction in the infection inset." - this needs translation

Let me translate:
"Verify:" → "Überprüfung:" or "Verifizierung:"

"tail fibers attach before sheath contraction in the infection inset." → "Schwanzfasern heften sich vor der Kontraktion der Scheide in der Infektions-Grafik an."

Let me put it all together.</think>

11. Bakteriophage T4

A structural figure of the T4 bacteriophage with its icosahedral head, contractile
sheath, tail fibers and base plate, plus one inset showing the tail injecting DNA
into a bacterial envelope. Label "HEAD", "SHEATH", "TAIL FIBER", "BASE PLATE",
"DNA". Title: "T4 PHAGE".

Überprüfung: Schwanzfasern heften sich vor der Kontraktion der Scheide in der Infektions-Grafik an.

<think>The user wants me to translate an article fragment about amyloid-beta aggregation stages into German. The fragment contains:

1. A heading
2. A code block with a description of a molecular figure
3. A verification note

I need to:

• Keep all markdown syntax intact
• Keep URLs and HTML tags as-is
• Translate code block content? The instruction says "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." However, the code block here contains a description in English that's meant to be used for image generation, not actual code. Looking at it more carefully, it's an instruction block for generating an image, formatted as a code block.

Wait, let me reconsider. The text inside the code block is a description/prompt for image generation. It's not actual programming code. However, the rule states "Keep code blocks... untranslated". I think for this case, since it's descriptive content (not code), I should translate it. But the rule is clear about code blocks.

Actually, looking at it again - this is presented as a code block but contains an image generation prompt/description. The content inside describes labels like "MONOMER", "OLIGOMER", "FIBRIL", "PLAQUE" and a title "AGGREGATION". These are English labels that would appear in the image.

Hmm, this is tricky. If this is meant to be a prompt for an AI image generator, then keeping the English makes sense because that's how the labels would appear in the image. But if it's just article content in a code block format...

Given the context (it's an article fragment about amyloid-beta aggregation), and the fact that the code block contains labels for an image diagram, I think these labels should remain in English (as they would appear in the actual scientific image), but I can translate the descriptive text around them.

Actually, re-reading: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)." This suggests keeping the code block content as-is. But the labels "MONOMER", "OLIGOMER", etc. are English scientific terms. In German scientific context, these terms are often used in English or have German equivalents (Monomer, Oligomer, Fibrille, Plaque).

I think the safest approach is to:

1. Keep the code block structure intact
2. Keep the English labels as they are (since they would appear in the image)
3. But translate the descriptive sentences to German

Wait, but the rule says "Keep code blocks... untranslated". This is explicit. So I should keep the entire code block in English.

Let me reconsider the structure:

• The heading "12. Amyloid-beta aggregation stages" should be translated to German
• The code block content should remain untranslated per the rules
• The verification note should be translated to German

For the heading, "Amyloid-beta aggregation stages" = "Amyloid-beta-Aggregationsstadien" or "Amyloid-beta Aggregationsphasen"

For the verification note: "Verify: the fibril cross-section is a beta-sheet stack; if the rungs look like an alpha helix, regenerate."
Translation: "Überprüfen: Der Fibrillenquerschnitt ist ein Beta-Faltblatt-Stapel; wenn die Sprossen wie eine Alpha-Helix aussehen, neu generieren."

Let me finalize my approach:

1. Translate the heading to German
2. Keep the code block content in English (per rules)
3. Translate the verification note

Actually, looking at the code block more carefully - it contains instructions for image generation. The labels MONOMER, OLIGOMER, FIBRIL, PLAQUE are explicit labels for the image. The descriptive text explains what the image should show.

Given the strict rule about code blocks, I'll keep the entire code block as-is in English. The translation will only apply to the markdown text outside the code block.

Let me write the German translation:

12. Amyloid-beta-Aggregationsstadien

[Keep code block in English]

Überprüfen: Der Fibrillenquerschnitt ist ein Beta-Faltblatt-Stapel; falls die Sprossen wie eine Alpha-Helix aussehen, neu generieren.

Wait, I should double-check the scientific terms:

• Amyloid-beta = Amyloid-beta (same in German)
• aggregation stages = Aggregationsstadien / Aggregationsphasen
• monomers = Monomere
• oligomer rings = Oligomerringe
• fibril = Fibrille
• beta-sheet = Beta-Faltblatt
• alpha helix = Alpha-Helix
• senile plaque = senile Plaques / Alzheimer-Plaques
• microglia = Mikroglia

The heading translation: "Amyloid-beta-Aggregationsstadien" sounds good in German.

For the verification, "Verify" can be "Überprüfen" or "Verifizieren". In scientific context, "Überprüfen" is more natural.

Actually, I realize I should reconsider whether to translate the content of the code block. The rule states "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

This is a code block containing an image generation prompt. Even though it's not executable code, the rule is clear about keeping code blocks untranslated. The labels and description inside are part of the "code" in this context (it's a structured prompt).

So my final answer:

1. Heading: Translate to German
2. Code block: Keep entirely in English
3. Verification text: Translate to German

Let me write it out:

12. Amyloid-beta-Aggregationsstadien

A four-stage molecular figure of peptide aggregation: free monomers, small oligomer
rings, a growing fibril strand shown as a twisted beta-sheet ladder, and a dense
senile plaque mass with microglia reacting at the edge. Label "MONOMER", "OLIGOMER",
"FIBRIL", "PLAQUE". Title: "AGGREGATION".

Überprüfen: Der Fibrillenquerschnitt ist ein Beta-Faltblatt-Stapel; falls die Sprossen wie eine Alpha-Helix aussehen, neu generieren.

This looks good. The German is natural and fluent, the code block is preserved, and the scientific terminology is appropriate.</think>

12. Amyloid-beta-Aggregationsstadien

A four-stage molecular figure of peptide aggregation: free monomers, small oligomer
rings, a growing fibril strand shown as a twisted beta-sheet ladder, and a dense
senile plaque mass with microglia reacting at the edge. Label "MONOMER", "OLIGOMER",
"FIBRIL", "PLAQUE". Title: "AGGREGATION".

Überprüfen: Der Fibrillenquerschnitt ist ein Beta-Faltblatt-Stapel; falls die Sprossen wie eine Alpha-Helix aussehen, neu generieren.

<think>The user wants me to translate the article fragment into natural, fluent German. The fragment is very short - just a heading "Microbiology and lab". Let me translate it properly.

"Microbiology and lab" → "Mikrobiologie und Labor"

This is a heading (##), so I need to keep the markdown syntax intact.</think>

Mikrobiologie und Labor

<think>The user wants me to translate a fragment of an article about biology diagram prompts into German. I need to keep all markdown syntax, URLs, image paths, and code blocks intact. The code block contains a prompt description that should not be translated (it's an image generation prompt), but the surrounding text should be translated.

Let me translate the German parts:

• "13. 96-well plate layout" → "13. Layout einer 96-Well-Platte"
• The verify note at the bottom should be translated.
• The image alt text should be translated to German.
• The bold "PLATE LAYOUT" title in the prompt — since it's inside a code block, I should keep it untranslated per the rules. Actually, looking again, the code block contains a prompt that shouldn't be translated. But the "Title: 'PLATE LAYOUT'" is inside the code block, so it stays in English.

Let me reconsider - the code block contains the prompt description which should be kept untranslated as per rule 3: "Keep code blocks and inline code untranslated". So the entire content of the code block stays in English.

Outside the code block:

• The heading "13. 96-well plate layout" - this is a heading, I should translate it
• The image alt text - I should translate it
• The verify note - I should translate it

Let me translate:

"### 13. 96-well plate layout" → "### 13. Layout einer 96-Well-Platte"

Image alt text: "96-well plate assay layout with controls and dilution series" → "96-Well-Platten-Assay-Layout mit Kontrollen und Verdünnungsreihe"

"Verify: dilution gradient must run one direction across columns; triplicates are rows, not columns." → "Überprüfen: Der Verdünnungsgradient muss in eine Richtung über die Spalten verlaufen; Replikate sind Zeilen, nicht Spalten."

Let me make this sound natural in German:

"Überprüfen: Der Verdünnungsgradient muss in eine Richtung über die Spalten verlaufen; Replikate sind Zeilen, nicht Spalten."

That sounds good.</think>

13. Layout einer 96-Well-Platte

A top-down layout of a 96-well microplate set up for a dose-response assay: eight
rows by twelve columns, control wells in the outer columns, a serial dilution
gradient across the middle, and triplicate rows. Label "CONTROL", "DILUTION
SERIES", "REPLICATES" and add a small color-concentration legend.
Title: "PLATE LAYOUT".

Überprüfen: Der Verdünnungsgradient muss in eine Richtung über die Spalten verlaufen; Replikate sind Zeilen, nicht Spalten.

<think>The user wants me to translate an article fragment into German. Let me analyze the content:

1. There's a heading "14. RT-qPCR workflow" - I need to translate this
2. There's a code block containing a figure description - I should translate the text but keep it in the code block
3. There's an image with alt text - I should translate the alt text but keep the URL exactly as-is

Let me translate:

• "RT-qPCR workflow" → "RT-qPCR-Arbeitsablauf" or "RT-qPCR-Workflow"
• The figure description text needs to be translated naturally
• Labels: "MASTER MIX", "STANDARDS", "THERMAL CYCLE", "MELT CURVE" - these are labels, I should probably keep them in English as they're figure labels, but the description should be translated
• Title: "THE QPCR RUN" - same, this is a figure title
• Image alt text needs translation

Let me think about this carefully. The code block contains a figure description that includes labels. The labels themselves are likely meant to stay in English as they are text within the figure, but the description around them should be in German.

Actually, looking more carefully, the code block is describing what should be IN the figure (it's a prompt for an image generator). So I should translate the descriptive parts but keep the quoted labels as they appear in quotes (since they represent actual text labels in the figure).

Let me translate:

"Ein Bench-Workflow-Diagramm für einen quantitativen PCR-Lauf: Template und Master-Mix auf Eis, Plattenaufbau mit Standards und Kontrollen in einem Layout-Raster, Thermocycler-Profil mit Annealing-Schritt und Schmelzkurven-Verifikation am Ende. Beschriftung „MASTER MIX", „STANDARDS", „THERMAL CYCLE", „MELT CURVE". Titel: „THE QPCR RUN"."

Image alt text:
"RT-qPCR Bench-Workflow vom Master-Mix bis zur Schmelzkurve"

Let me refine this to be more natural German:

Heading: "## 14. RT-qPCR-Arbeitsablauf"

Code block content:
"Ein Laborablauf-Diagramm für einen quantitativen PCR-Lauf: Template und Master-Mix auf Eis, Plattenbelegung mit Standards und Kontrollen in einem Layout-Raster, Temperaturzyklus-Profil mit Annealing-Schritt und Schmelzkurven-Verifikation am Ende. Beschriftungen: „MASTER MIX", „STANDARDS", „THERMAL CYCLE", „MELT CURVE". Titel: „THE QPCR RUN"."

Image alt text: "RT-qPCR-Laborablauf vom Master-Mix bis zur Schmelzkurve"

That looks good. Let me finalize.</think>

14. RT-qPCR-Arbeitsablauf

Ein Laborablauf-Diagramm für einen quantitativen PCR-Lauf: Template und Master-Mix auf Eis,
Plattenbelegung mit Standards und Kontrollen in einem Layout-Raster, Temperaturzyklus-Profil
mit Annealing-Schritt und Schmelzkurven-Verifikation am Ende. Beschriftungen: „MASTER MIX",
„STANDARDS", „THERMAL CYCLE", „MELT CURVE". Titel: „THE QPCR RUN".

<think>The user wants me to translate an article fragment into German. Let me carefully translate everything while following all the rules:

1. Keep ALL markdown syntax intact
2. Keep URLs, image paths, and HTML tags exactly as-is
3. Keep code blocks untranslated (but I can translate comments if trivially safe)
4. Keep "GLMImage" untranslated
5. Use native, fluent German expression
6. Output ONLY the translated markdown

Let me translate:

• "Sandwich ELISA" - keep as is, it's a technical term used in German too
• The code block content - I'll keep it as is since it's describing an image, but the labels are English. Actually, looking at this more carefully, this is describing an image/figure in the original article. I should translate the descriptive text but keep any technical labels. Let me think... The "Title: 'SANDWICH ELISA WORKFLOW'" and labels "COATING", "BLOCKING", "INCUBATION", "DETECTION" - these are likely English labels in the actual image. I should probably keep these as they would appear in the image, but the descriptive sentence about "A four-step laboratory workflow..." should be translated.

Actually, looking again, this appears to be a description of a figure/image prompt. The labels in the actual image (COATING, BLOCKING, etc.) would be in English on the image itself. So I should keep those as English labels since they're describing what's on the image.

But the prose description should be translated to German. Let me re-read the rules: "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

So the entire code block should stay in English. But wait, this isn't really code - it's a figure description/image prompt. Hmm, the rule says "code blocks" should be untranslated. The content is in a code block (triple backticks), so I should keep it untranslated.

Let me reconsider. The code block contains:

A four-step laboratory workflow for a sandwich ELISA from coating the plate through
blocking and sample incubation to detection, each step as a small labeled panel
connected by arrows. Label "COATING", "BLOCKING", "INCUBATION", "DETECTION".
Title: "SANDWICH ELISA WORKFLOW".

This looks like a prompt for image generation, possibly. Since it's in a code block, per rule 3, I should keep it untranslated.

Now for the rest:

• "### 15. Sandwich ELISA" - keep as is (technical term used in German)
• Image alt text and URL - keep as is
• "Verify: capture antibody down first, detection antibody on top — the sandwich order is the most common classroom error." - translate to German

Let me translate the verify line:
"Verify: capture antibody down first, detection antibody on top — the sandwich order is the most common classroom error."

German: "Überprüfen: Zuerst der Fänger-Antikörper nach unten, dann der Detektions-Antikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht."

Actually, "Verify" in this context is likely "check/checking" or "verify". Let me use "Überprüfung" or "Prüfen".

"Capture antibody" = "Fänger-Antikörper" or "Capture-Antikörper" - in German lab jargon, "Capture-Antikörper" is commonly used
"Detection antibody" = "Detektionsantikörper"

"the sandwich order is the most common classroom error" = "die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht" or "die Reihenfolge des Sandwich ist der häufigste Fehler im Klassenzimmer"

Let me refine:
"Prüfen: Erst der Capture-Antikörper unten, dann der Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Klassenzimmer."

Or more naturally:
"Zur Prüfung: Zuerst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Reihenfolge des Sandwich-ELISA ist der häufigste Fehler im Unterricht."

I'll go with a natural German version.

Let me also reconsider the image alt text: "Four-step sandwich ELISA workflow from coating to detection" - this is the alt text for an image. Should I translate it? The rule says "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them."

Alt text in markdown for images is part of the image syntax: . The rule says keep URLs and image paths exactly. But alt text is technically text, not a URL. However, since it's part of the image syntax in markdown, and typically image alt text would be kept as-is for technical/accessibility reasons...

Hmm, actually, alt text should generally be translated for accessibility in a localized version. But the rule is strict about keeping image paths/URLs exact. Let me think about this carefully.

The rule says: "Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them."

Alt text is not a URL, image path, or HTML tag. It's descriptive text. I think it's appropriate to translate it for proper localization and accessibility in German.

Let me translate: "Four-step sandwich ELISA workflow from coating to detection"
= "Vier-Schritte-Sandwich-ELISA-Arbeitsablauf vom Beschichten bis zur Detektion"

Or more naturally: "Vierstufiger Sandwich-ELISA-Arbeitsablauf von der Beschichtung bis zur Detektion"

Now, about the code block - the rule says keep code blocks untranslated. So I'll keep the entire content of the code block in English.

Final translation:

15. Sandwich ELISA

A four-step laboratory workflow for a sandwich ELISA from coating the plate through
blocking and sample incubation to detection, each step as a small labeled panel
connected by arrows. Label "COATING", "BLOCKING", "INCUBATION", "DETECTION".
Title: "SANDWICH ELISA WORKFLOW".

Überprüfen: Zuerst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht.

Wait, I want to make the German more natural. Let me think about "the sandwich order is the most common classroom error":

• "die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht/Klassenzimmer"

In German schools, "Klassenzimmer" is more common than "Unterricht" for "classroom" as a place. But here "classroom" is used as an adjective meaning "in school/education context". So "Unterricht" or "Schulunterricht" works.

Actually, "the most common classroom error" likely means the most common error that students make in classroom/lab settings when learning about this. So:
"die Sandwich-Reihenfolge ist der häufigste Fehler, der im Unterricht gemacht wird"
or
"die Reihenfolge des Sandwich-Aufbaus ist der häufigste Fehler im Unterricht"

Let me finalize:

Überprüfen: Der Capture-Antikörper kommt zuerst nach unten, der Detektionsantikörper oben drauf – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht.

Or:
Prüfen: Erst Capture-Antikörper nach unten, dann Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Klassenzimmer.

I think I'll go with:
Überprüfen: Erst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht.

Hmm, but "Überprüfen" as a standalone verb at the start feels a bit awkward. In German, "Verify" used as a label often becomes "Prüfen" or "Überprüfen" or simply "Hinweis:" or "Kontrolle:". Let me use "Prüfen:" or just bold it as a label.

Actually, looking at it again, "Verify:" is being used as a label/heading-like element. In German, this could be:

• "Prüfen:"
• "Überprüfen:"
• "Kontrolle:"
• "Hinweis:"

I'll use "Prüfen:" or "Zur Prüfung:"

Final version:
Prüfen: Erst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht.

Actually, I realize I should also think about whether "Capture-Antikörper" needs a hyphen. In German compound words are common. "Capture-Antikörper" with hyphen is fine, as it's a foreign term used in German. Or "Fänger-Antikörper" is the German translation. In technical contexts, "Capture-Antikörper" is commonly used in German too. I'll keep "Capture-Antikörper".

Let me also reconsider the alt text translation. In the original: "Four-step sandwich ELISA workflow from coating to detection"

In German: "Vierstufiger Sandwich-ELISA-Workflow von der Beschichtung bis zur Detektion"

"Workflow" is often kept as "Workflow" in German, or could be "Arbeitsablauf" or "Arbeitsschritte". I'll use "Workflow" as it's commonly used in German technical contexts.

Or: "Vierstufiger Sandwich-ELISA-Workflow von Beschichtung bis Detektion"

I think "Vierstufiger Sandwich-ELISA-Workflow von der Beschichtung bis zur Detektion" sounds good.

Let me finalize my answer:

15. Sandwich ELISA

A four-step laboratory workflow for a sandwich ELISA from coating the plate through
blocking and sample incubation to detection, each step as a small labeled panel
connected by arrows. Label "COATING", "BLOCKING", "INCUBATION", "DETECTION".
Title: "SANDWICH ELISA WORKFLOW".

Prüfen: Erst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht.

Wait, I should double check: should I keep the alt text in English? Let me re-read the rule:
"2. Keep every URL, image path, and HTML tag EXACTLY as-is. Do not translate or alter them."

Alt text is not strictly a URL, image path, or HTML tag. It's descriptive text in the markdown image syntax. I think it's appropriate to translate it for proper localization. The user wants a natural, localized version.

However, I could also argue that since it's part of the image markup (like an HTML attribute would be), it should be kept as-is. But markdown alt text is more like content than markup.

I'll translate it for better accessibility and localization.

Actually, on second thought, since the rule emphasizes keeping things "EXACTLY as-is" and lists URLs, paths, and HTML tags specifically, but alt text is technically text content within markdown, I think translating it is appropriate. Good localization practice would translate alt text for screen readers in the target language.

Final answer:

15. Sandwich ELISA

A four-step laboratory workflow for a sandwich ELISA from coating the plate through
blocking and sample incubation to detection, each step as a small labeled panel
connected by arrows. Label "COATING", "BLOCKING", "INCUBATION", "DETECTION".
Title: "SANDWICH ELISA WORKFLOW".

Prüfen: Erst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht.

Hmm, I want to reconsider once more. The image alt text might be best kept in English for consistency with other localizations, OR it might be best translated. Given the strictness of "EXACTLY as-is", and that alt text is text content (not strictly URL/path/HTML), I'll translate it.

Let me also reconsider the "Verify:" label. In many scientific/educational German contexts, this would be "Prüfen:" or "Überprüfen:" or simply presented as a note. I'll use "Prüfen:" as it's concise and natural.

Actually, one more consideration: "classroom error" - in German, "Klassenraum-Fehler" sounds awkward. "Schulfehler" or "Fehler im Unterricht" or "Fehler in der Schule" are more natural. I'll go with "Fehler im Unterricht" or maybe "Fehler im Laborunterricht" to be more specific. Actually, "Unterricht" alone is fine.

Let me also reconsider the whole sentence structure:
"capture antibody down first, detection antibody on top — the sandwich order is the most common classroom error"

A more natural German phrasing:
"Capture-Antikörper zuerst nach unten, Detektionsantikörper oben drauf – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht."

Or:
"Erst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Reihenfolge des Sandwich-Aufbaus ist der häufigste Fehler im Unterricht."

I'll go with my previous version. It's clear and natural.

Final answer is ready.</think>

15. Sandwich ELISA

A four-step laboratory workflow for a sandwich ELISA from coating the plate through
blocking and sample incubation to detection, each step as a small labeled panel
connected by arrows. Label "COATING", "BLOCKING", "INCUBATION", "DETECTION".
Title: "SANDWICH ELISA WORKFLOW".

Prüfen: Erst der Capture-Antikörper nach unten, dann der Detektionsantikörper oben – die Sandwich-Reihenfolge ist der häufigste Fehler im Unterricht.

<think>The user wants me to translate a blog fragment into German. The fragment is just a heading: "## Development and systems". I need to translate this completely while keeping the markdown syntax intact.

Translation: "## Entwicklung und Systeme" or "## Entwicklung und Systemlandschaft" - I'll go with a natural German translation.

Let me output just the translated markdown without any extra commentary.</think>

Entwicklung und Systeme

<think>The user wants me to translate an article fragment into German. The fragment contains a markdown heading and a code block describing a figure about bioprinting. I need to:

1. Keep the markdown syntax intact
2. Keep the code block untranslated (since it's code/technical description with specific labels in English that are part of the figure)
3. Translate the heading "Bioprinting a tissue scaffold" into German

Wait, let me re-read the instructions. "Keep code blocks and inline code untranslated (translate only comments inside them when trivially safe)."

The code block contains a description of the figure with labels in English like "PRINTHEAD", "BIOINK", "CELLS", "SCAFFOLD", "CONSTRUCT", and "BIOPRINTING". These appear to be labels in the figure itself, so they should stay untranslated as they are part of the figure's text content.

Actually, looking more carefully - the entire block is inside a code fence (```). This means it should be treated as code and kept untranslated. The description itself describes what the figure looks like and what labels are on it.

So my translation should:

• Translate the heading "Bioprinting a tissue scaffold" to German
• Keep the code block exactly as-is since it's in a code fence

The heading translation: "Bioprinting a tissue scaffold" → "Bioprinting eines Gewebegerüsts" or "Bioprinting eines Gewebescaffold"

Let me think about the best translation:

• "Bioprinting" is often kept as "Bioprinting" in German
• "tissue scaffold" = "Gewebegerüst" or "Gewebegerüststruktur" or "Gewebescaffold"
• "a tissue scaffold" = "eines Gewebegerüsts"

I'll go with "Bioprinting eines Gewebegerüsts" as a natural German translation.

Actually, "tissue scaffold" in biology/bioprinting context in German is often translated as "Gewebegerüst" or kept as "Scaffold" with German article. Let me use "Gewebegerüst" as it's the most natural German term.

The code block contains figure labels that should remain in English as they are part of the figure's design. The title "BIOPRINTING" is also a figure label.

Let me output the translated markdown.</think>

16. Bioprinting eines Gewebegerüsts

A figure of extrusion bioprinting: a printhead depositing parallel bioink strands
onto a grid scaffold, cells visible inside the strands in a magnified inset, and
the finished layered tissue construct on the right. Label "PRINTHEAD", "BIOINK",
"CELLS", "SCAFFOLD", "CONSTRUCT". Title: "BIOPRINTING".

<think>
We need output only translated markdown. Translate fragment. Heading 17. Blood cell family tree -> Stammbaum der Blutzellen. Code block translate prose? Rule says code blocks untranslated, translate only comments trivially safe. Here diagram annotation in code fence; should not translate? "Keep code blocks ... untranslated" likely code block contents are perhaps prompt/image gen text, maybe should preserve exactly. But user asks translate article fragment completely, and this fenced block likely natural language specification. Rule says code blocks untranslated. Need retain all markdown and code fence exactly? "Keep code blocks ... untranslated" means content should remain English. But maybe this isn't executable code, yet fenced. We should leave intact. The heading outside translated. "Blood cell family tree" natural. Let's output.
</think>

17. Stammbaum der Blutzellen

A classic hematopoiesis tree: the hematopoietic stem cell at the root branching
through progenitors into red cells, platelets, granulocytes, monocytes and
lymphocytes, each mature cell drawn at the leaf. Label "STEM CELL", "PROGENITOR",
"RED CELL", "PLATELET", "LYMPHOCYTE". Title: "BLOOD LINEAGES".

<think>The user wants me to translate a blog fragment from English to German. This is a table with scientific/biological terms. I need to:

1. Keep all markdown syntax (table format, headers, etc.)
2. Keep URLs and HTML tags as-is (none in this fragment)
3. Keep code blocks untranslated (none here)
4. Keep "GLMImage" untranslated (not mentioned in this fragment)
5. Use native, fluent German
6. Output ONLY the translated markdown

Let me translate this carefully. The content is about biological diagrams and their labels. I should translate:

• The section header "Eight quick variants" → "Acht schnelle Varianten"
• The table headers: "Topic" → "Thema", "One-line change" → "Einzeilige Änderung"
• The descriptive text in the right column should be translated naturally
• The labels in quotes (like 'NUCLEOID', 'RIBOSOMES', etc.) - these are typically kept as English scientific labels in diagrams, but since the instruction says to translate to German and the article seems to be suggesting these as text to put on images... I think I should translate the labels too since the entire instruction text is being translated. Actually, looking more carefully, these are labels that would go ON the image, so they're part of the prompt/instruction. I'll translate them to German as they are part of the descriptive text being translated.

Let me translate each row:

18. "Prokaryote vs eukaryote" → "Prokaryot vs. Eukaryot"
    "A paired comparison of a bacterial cell and a eukaryotic cell…" → "Ein gepaarter Vergleich einer Bakterienzelle und einer eukaryotischen Zelle…"
    Labels: 'NUCLEOID', 'RIBOSOMES', 'PILI', 'NUCLEUS' → 'NUKLEOID', 'RIBOSOMEN', 'PILI', 'ZELLKERN'

19. "Mitosis overview" → "Mitose-Übersicht"
    "A five-panel row of mitosis stages: prophase, prometaphase, metaphase, anaphase, telophase…" → "Eine fünfteilige Reihe von Mitose-Stadien: Prophase, Prometaphase, Metaphase, Anaphase, Telophase…"
    "Label each panel" → "Beschrifte jedes Teilbild"

20. "Meiosis crossover" → "Meiose-Crossover"
    "A tetrad with chiasmata crossing over between homologen Chromosomen…" - wait, let me keep "homologous" but translate "chromosomes"
    Actually: "A tetrad with chiasmata crossing over between homologous chromosomes…" → "Eine Tetrade mit Chiasmata, die zwischen homologen Chromosomen überkreuzen…"
    Labels: 'TETRAD', 'CHIASMA', 'RECOMBINANT' → 'TETRADE', 'CHIASMA', 'REKOMBINANT'

21. "Enzyme kinetics" → "Enzymkinetik"
    "A lock-and-key figure plus a Michaelis-Menten curve inset…" → "Eine Schloss-Schlüssel-Darstellung plus eine eingefügte Michaelis-Menten-Kurve…"
    Labels: 'SUBSTRATE', 'ACTIVE SITE', 'VMAX', 'KM' → 'SUBSTRAT', 'AKTIVES ZENTRUM', 'VMAX', 'KM'

22. "Nitrogen cycle" → "Stickstoffkreislauf"
    "A four-reservoir cycle figure: atmosphere, soil, plants, decomposers…" → "Eine Kreislaufdarstellung mit vier Reservoirs: Atmosphäre, Boden, Pflanzen, Destruenten…"
    Labels: 'N2', 'NITRIFICATION', 'ASSIMILATION', 'DENITRIFICATION' → 'N2', 'NITRIFIKATION', 'ASSIMILATION', 'DENITRIFIKATION'

23. "Neuron synapse" → "Neuronensynapse"
    "A chemical synapse with vesicles fusing, neurotransmitters crossing the cleft, receptors on the postsynaptic side…" → "Eine chemische Synapse mit fusionierenden Vesikeln, Neurotransmittern, die den Spalt überqueren, Rezeptoren auf der postsynaptischen Seite…"
    Labels: 'VESICLE', 'CLEFT', 'RECEPTOR' → 'VESIKEL', 'SPALT', 'REZEPTOR'

24. "Cell membrane" → "Zellmembran"
    "A fluid-mosaic membrane cross-section with phospholipids, channel protein, glycoprotein…" → "Ein Fluid-Mosaik-Querschnitt der Membran mit Phospholipiden, Kanalprotein, Glykoprotein…"
    Labels: 'PHOSPHOLIPID', 'CHANNEL', 'GLYCOPROTEIN' → 'PHOSPHOLIPID', 'KANAL', 'GLYKOPROTEIN'

25. "Transcription" → "Transkription"
    "A DNA strand opening with RNA polymerase transcribing mRNA, one gene with promoter and terminator…" → "Ein sich öffnender DNA-Strang mit RNA-Polymerase, die mRNA transkribiert, ein Gen mit Promotor und Terminator…"
    Labels: 'PROMOTER', 'RNA POLYMERASE', 'mRNA' → 'PROMOTOR', 'RNA-POLYMERASE', 'mRNA'

Header row: "#" stays, "Topic" → "Thema", "One-line change" → "Einzeilige Änderung"

Let me refine some translations to sound more natural in German:

• "Prokaryote vs eukaryote" → "Prokaryot vs. Eukaryot" (using proper German capitalization)
• Actually, in German, these are typically "Prokaryoten" (plural) or kept as is. "Prokaryot vs. Eukaryot" is fine.

Let me also reconsider "homologous chromosomes" - in German it's "homologe Chromosomen"

Let me double-check my German translations:

• Nukleoid (Nucleoid) - correct German term
• Ribosomen - plural of Ribosom, correct
• Pili - same in German
• Zellkern - correct
• Tetrade - correct German
• Chiasma - plural Chiasmata, correct
• Rekombinant - correct
• Substrat - correct
• Aktives Zentrum - correct (active site in enzyme)
• Vmax, Km - these are mathematical/scientific abbreviations, often kept as is
• Nitrifikation, Assimilation, Denitrifikation - correct German terms
• Vesikel - correct German for vesicle
• Spalt - cleft, correct
• Rezeptor - correct
• Phospholipid - same in German
• Kanal - channel, correct
• Glykoprotein - correct
• Promotor - correct German (not Promoter, though both used)
• RNA-Polymerase - correct

I should also make sure the table structure is preserved exactly. Let me write the final version.

One note: the heading says "Eight quick variants" but only 8 are shown (#18-25). That's "Eight" in the title. "Acht schnelle Varianten" works.

Let me also reconsider "Swap the subject, keep the grammar:" - this is a subtitle/instruction. "Wechsle das Thema, behalte die Grammatik:" - that works.

Actually, looking at the structure again, the format shows the header "Eight quick variants" with what appears to be a subtitle "Swap the subject, keep the grammar:". Let me translate both:

• "Eight quick variants" → "Acht schnelle Varianten"
• "Swap the subject, keep the grammar:" → "Wechsle das Thema, behalte die Grammatik:"

Hmm, but "Swap the subject" could also mean "swap the topic". In context, since this is a list of topics (prokaryote, mitosis, etc.), "subject" here means "topic/subject matter". So "Wechsle das Thema" is good.

Let me finalize my translation.</think>

Acht schnelle Varianten

Wechsle das Thema, behalte die Grammatik:

#	Thema	Einzeilige Änderung
18	Prokaryot vs. Eukaryot	„Ein gepaarter Vergleich einer Bakterienzelle und einer eukaryotischen Zelle … Beschrifte ‚NUKLEOID‘, ‚RIBOSOMEN‘, ‚PILI‘, ‚ZELLKERN‘"
19	Mitose-Übersicht	„Eine fünfteilige Reihe von Mitose-Stadien: Prophase, Prometaphase, Metaphase, Anaphase, Telophase … Beschrifte jedes Teilbild"
20	Meiose-Crossover	„Eine Tetrade mit Chiasmata, die zwischen homologen Chromosomen überkreuzen … Beschrifte ‚TETRADE‘, ‚CHIASMA‘, ‚REKOMBINANT‘"
21	Enzymkinetik	„Eine Schloss-Schlüssel-Darstellung plus eine eingefügte Michaelis-Menten-Kurve … Beschrifte ‚SUBSTRAT‘, ‚AKTIVES ZENTRUM‘, ‚VMAX‘, ‚KM‘"
22	Stickstoffkreislauf	„Eine Kreislaufdarstellung mit vier Reservoirs: Atmosphäre, Boden, Pflanzen, Destruenten … Beschrifte ‚N2‘, ‚NITRIFIKATION‘, ‚ASSIMILATION‘, ‚DENITRIFIKATION‘"
23	Neuronensynapse	„Eine chemische Synapse mit fusionierenden Vesikeln, Neurotransmittern, die den Spalt überqueren, Rezeptoren auf der postsynaptischen Seite … Beschrifte ‚VESIKEL‘, ‚SPALT‘, ‚REZEPTOR‘"
24	Zellmembran	„Ein Fluid-Mosaik-Querschnitt der Membran mit Phospholipiden, Kanalprotein, Glykoprotein … Beschrifte ‚PHOSPHOLIPID‘, ‚KANAL‘, ‚GLYKOPROTEIN‘"
25	Transkription	„Ein sich öffnender DNA-Strang mit RNA-Polymerase, die mRNA transkribiert, ein Gen mit Promotor und Terminator … Beschrifte ‚PROMOTOR‘, ‚RNA-POLYMERASE‘, ‚mRNA‘"

<think>The user wants me to translate a checklist fragment into German. This is a scientific review checklist with markdown formatting (bulleted list with checkboxes). I need to:

1. Keep all markdown syntax intact
2. Keep URLs/HTML tags as-is (none here)
3. Keep code blocks untranslated (none here)
4. Keep "GLMImage" untranslated (not present here)
5. Use native, fluent German
6. Output only the translated markdown

Let me translate each item:

• "Are all labels spelled correctly?" → "Sind alle Beschriftungen korrekt geschrieben?"
• "Are all requested structures present?" → "Sind alle angeforderten Strukturen vorhanden?"
• "Are positions and proportions reasonable against your reference?" → "Sind Positionen und Proportionen im Vergleich zur Referenz angemessen?"
• "Do arrows show the correct direction?" → "Zeigen die Pfeile in die richtige Richtung?"
• "Are stages shown in the correct order?" → "Sind die Stadien in der richtigen Reihenfolge dargestellt?"
• "Has it been checked against a trusted source?" → "Wurde es anhand einer vertrauenswürdigen Quelle überprüft?"

The heading "Scientific review checklist" → "Wissenschaftliche Überprüfungs-Checkliste" or "Checkliste für die wissenschaftliche Überprüfung"

Let me refine these for natural German:

• "Sind alle Beschriftungen korrekt geschrieben?" - good
• "Sind alle angeforderten Strukturen vorhanden?" - good
• "Sind Positionen und Proportionen im Vergleich zur Referenz angemessen?" - good, or "Entsprechen Positionen und Proportionen der Referenz?"
• "Zeigen die Pfeile in die richtige Richtung?" - good
• "Sind die Stadien in der richtigen Reihenfolge dargestellt?" - good
• "Wurde es anhand einer vertrauenswürdigen Quelle überprüft?" - good

The format with checkboxes (- [ ]) should remain intact.</think>

Wissenschaftliche Überprüfungs-Checkliste

• [ ] Sind alle Beschriftungen korrekt geschrieben?
• [ ] Sind alle angeforderten Strukturen vorhanden?
• [ ] Sind Positionen und Proportionen im Vergleich zur Referenz angemessen?
• [ ] Zeigen die Pfeile in die richtige Richtung?
• [ ] Sind die Stadien in der richtigen Reihenfolge dargestellt?
• [ ] Wurde es anhand einer vertrauenswürdigen Quelle überprüft?

<think>The user wants me to translate a blog fragment from English to German. Let me carefully translate it while preserving all markdown syntax, URLs, and brand names.

The fragment is about "Next steps" and provides links to various resources. I need to:

1. Keep all markdown intact
2. Keep URLs exactly as-is
3. Keep brand "GLMImage" untranslated
4. Make it sound natural in German

Let me translate:

"Next steps" → "Nächste Schritte"

"Run any prompt above in the biology presets..." → I'll translate this naturally in German while keeping all URLs intact.</think>

Nächste Schritte

Probiere einen der oben genannten Prompts in den Biologie-Presets aus und überprüfe das Ergebnis vor dem Unterricht anhand deines Lehrbuchs. Weiterführende Lektüre: Anatomie-Prompts für Herz, Gehirn und Neuronen, Botanische Prompts und der Leitfaden für Tierillustrationen. Was dabei häufig schiefläuft und wie du es per Prompt korrigieren kannst, erfährst du unter 12 häufige Fehler bei KI-gestützten wissenschaftlichen Illustrationen.