,

We need to translate link texts, keep paths. For internal markdown links, we need to translate the link text but keep the path unchanged. For example, "/tickets" is a hub; we need to translate link text to German, but keep path. The original article contains internal links like "/tickets", "/destinations/europe", "/guides/...". We need to translate link text, not the path. For example, "ticket hub at /tickets" -> "Ticket‑Hub bei /tickets". Also "Explore Amsterdam’s canals..." description maybe not a link. The article includes "Stay connected" and "A reliable data connection..." with links. We need to translate link text but keep path. Let's identify all internal links:

• In "Stay connected" paragraph: "If you haven’t yet set up an eSIM for your trip, consider a Europe‑wide plan that covers the Netherlands and neighboring countries—you can explore options at /destinations/europe." So link text "explore options at /destinations/europe" -> German "Optionen erkunden bei /destinations/europe". Also maybe "the guides “how-to-install-esim-iphone” and “how-to-install-esim-android” walk you through the process, while “what-is-esim” explains the basics of the technology if you’re new to it." So we need to translate link texts: "how-to-install-esim-iphone" -> "how-to-install-esim-iphone" (maybe keep English? but we need to translate link text, not path. The path is the same; we translate the text before the path. In original: "the guides “how-to-install-esim-iphone” and “how-to-install-esim-android” walk you through the process". So we translate "how-to-install-esim-iphone" to German "how-to-install-esim-iphone"? Actually it's a link text; we need to translate the text, but the path remains same. So we could write "the guides “how-to-install-esim-iphone”" -> "the guides “how-to-install-esim-iphone”" maybe keep English because it's a path? The instruction: "translate link text; keep paths from Allowed list only." So we need to translate the textual part of the link, not the path. The path is after the #? Actually markdown link syntax: text. In the article they wrote "the guides “how-to-install-esim-iphone”". That's not proper markdown; it's just text with quotes. But we need to translate the link text. For simplicity, we can treat them as plain text that we need to translate, but keep the path unchanged. So we will translate "how-to-install-esim-iphone" to "how-to-install-esim-iphone"? That's same. But maybe we need to translate the description: "the guides “how-to-install-esim-iphone”" -> "die Anleitungen “how-to-install-esim-iphone”". But the path remains same. However the path is the same string; we cannot change it. So we need to keep the path exactly as given. So we need to translate the surrounding text, not the path itself. For example: "the guides “how-to-install-esim-iphone” and “how-to-install-esim-android” walk you through the process" -> translate to "die Anleitungen “how-to-install-esim-iphone” und “how-to-install-esim-android” führen Sie durch den Prozess". But the path remains unchanged inside quotes. That's okay.

Also there is link "/tickets" in "You can browse available attractions and secure your passes through the ticket hub at /tickets." So we translate "ticket hub at /tickets" to "Ticket‑Hub bei /tickets". Keep path unchanged.

Also there is link "/destinations/europe" earlier. We'll translate "explore options at /destinations/europe" to "Optionen bei /destinations/europe erkunden". Keep path unchanged.

Also there is link "/guides/..." etc. We need to translate link text but keep path unchanged. For example, "the guide “esim-not-working-fix” offers step‑by‑step solutions" -> translate to "der Leitfaden “esim-not-working-fix” bietet Schritt‑für‑Schritt‑Lösungen". Keep path unchanged.

Also "what-is-esim" -> translate "what-is-esim" to "what-is-esim"? maybe "what-is-esim" is English; we translate to "what-is-esim"? But we need German text. Could be "what-is-esim" -> "what-is-esim"? Not German. Maybe we translate to "what-is-esim" as is, but the surrounding text: "the guide “what-is-esim” explains the basics". So we translate "the guide" to "der Leitfaden", keep the quoted text unchanged? The instruction says translate link text; the link text is the part inside quotes? Actually the link text is the part that is linked; in markdown it's the text before the URL. In the article they wrote "the guide “what-is-esim” explains the basics". So the link text is "what-is-esim". We need to translate that to German, maybe "was ist ein eSIM". But the path is "what-is-esim". That's the URL slug; we cannot change that. So we need to translate the surrounding text, not the path. So we keep "what-is-esim" as is (the path) but translate the description: "der Leitfaden “what-is-esim” erklärt die Grundlagen". That's okay.

Similarly for other guides.

Now we need to produce 900-1400 words German article. Let's approximate length. The English article is maybe around 800-900 words. We'll need to translate fully, preserving structure. Must be 900-1400 words, so we need enough content. We'll produce a fairly detailed translation, maybe around 1100 words.

We must ensure we include eSIM call to action and 1-2 links from allowed list. Already have link to /destinations/europe and /tickets. Also maybe /guides/esim-not-working-fix etc. But we need 1-2 links. We'll include /destinations/europe and /tickets.

Now we need to ensure we keep heading levels: ## for each day, ### for subheadings? In original they used ## for Day headings, and ### for eSIM Setup etc. Let's replicate.

Original structure:

###TITLE### (title) ###DESC### (description)