Skip to content

i18n (DE): add 'install-and-setup' - #14296

Open
rdwz wants to merge 13 commits into
withastro:mainfrom
advanced-astro:i18n-de/install-and-setup
Open

i18n (DE): add 'install-and-setup'#14296
rdwz wants to merge 13 commits into
withastro:mainfrom
advanced-astro:i18n-de/install-and-setup

Conversation

@rdwz

@rdwz rdwz commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

German translation of the page 'install-and-setup'

@github-actions github-actions Bot added the i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help! label Jul 23, 2026
@astrobot-houston

astrobot-houston commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
de/basics/project-structure.mdx Localization changed, will be marked as complete.
de/install-and-setup.mdx Localization added, will be marked as complete.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@github-actions

github-actions Bot commented Jul 23, 2026

Copy link
Copy Markdown

Preview deployment

❌ Deployment failed!

@randomguy-2650 randomguy-2650 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left lots of nits that I found.

title: Astro installieren
sidebar:
label: Installation
description: "So installierst du Astro und startest ein neues Projekt."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don’t like how this is written for some reason…

In my opinion, my suggestion is probably not good either but could maybe be used to improve the translation:

---
description: "Wir zeigen dir, wie man Astro installiert und ein neues Projekt startet."
---

The current translation just sounds a bit “clickbaity” to me.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see any clickbait here, nor any reason not to keep the desc brief and to add an extra meta-level:
"Wir zeigen dir, wie man..." 🆚 "So..."

Style Guide Wir bleiben möglichst nah am englischen Originaltext.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about something like:

Suggested change
description: "So installierst du Astro und startest ein neues Projekt."
description: "Eine Anleitung zur Installation von Astro und zum Starten eines neuen Projekts."

It's more passive so definitely less clickbait if you insist @randomguy-2650. IMHO all suggestions here and the original are fine as well 👍

Comment thread src/content/docs/de/install-and-setup.mdx Outdated
Comment thread src/content/docs/de/install-and-setup.mdx Outdated

## Browser‑Kompatibilität

Astro basiert auf Vite, das standardmäßig moderne Browser mit aktueller JavaScript‑Unterstützung anvisiert.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Astro basiert auf Vite, das standardmäßig moderne Browser mit aktueller JavaScript‑Unterstützung anvisiert.
Astro basiert auf Vite, das standardmäßig moderne Browser mit aktueller JavaScript‑Unterstützung anvisiert.

Just in case for compatibility.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no paragraph here in the original text

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know but if for some reason the MDX parser’s behaviour changes in the future, this will make it still work.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@randomguy-2650 I think if you look at the original text, it is intended to be in one line. I think @rdwz just separated both sentences to individual lines for readability, which will render as no newline, so I think it is correct as is, no empty line needed.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One thing I would like to simplify though for readability, is:

Suggested change
Astro basiert auf Vite, das standardmäßig moderne Browser mit aktueller JavaScript‑Unterstützung anvisiert.
Astro basiert auf Vite, welches standardmäßig Browser mit moderner JavaScript‑Unterstützung anvisiert.

I personally like to use "welches" in such cases because it makes it less confusing with the variety of meanings of "das" in the German language (better readability).

Comment thread src/content/docs/de/install-and-setup.mdx Outdated
Comment thread src/content/docs/de/install-and-setup.mdx Outdated
Comment thread src/content/docs/de/install-and-setup.mdx
Comment thread src/content/docs/de/install-and-setup.mdx
Comment thread src/content/docs/de/install-and-setup.mdx
}
```

7. Projektstruktur

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
7. Projektstruktur
7. Bereite die Projektstruktur vor.

I don’t like list items where it’s just one word. @trueberryless

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

However, this only shows the structure that has been created up to this point. No further preparation is required.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But one word still feels weird to me. Maybe:

So soll die Projektstruktur aussehen.

rdwz and others added 11 commits July 31, 2026 13:19
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
Co-authored-by: randomguy-2650 <150704902+randomguy-2650@users.noreply.github.com>
@rdwz
rdwz requested a review from randomguy-2650 July 31, 2026 12:17
@rdwz

rdwz commented Jul 31, 2026

Copy link
Copy Markdown
Contributor Author

Left lots of nits that I found.

Thanks for the review. I have now left some conversations open and made some changes.

I'm still not sure how to do PR reviews correctly. If I have broken any rules, please let me know what I need to do to get this done properly 🤓

@randomguy-2650 randomguy-2650 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks pretty good once the remaining stuff is resolved.

Other stuff if you’re bothered to read it

That will maybe wait if @trueberryless doesn’t give another opinion yet, but his “Sommerferien” will end in around September, I don’t really think we would wait till then if he is on his holiday right now but…?

@randomguy-2650

randomguy-2650 commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

TL;DR: https://docs.github.com/en/pull-requests/how-tos/review-pull-requests/reviewing-proposed-changes-in-a-pull-request#starting-a-review

And about the reviewing PRs thing, you have to go to the Files changed tab in the PR, click on the + icon when hovering over the line you want to review, and comment about it (if it’s just one, click on Comment, otherwise Start a review).

To add a suggestion, click on the ± symbol enclosed in a file icon silhouette. It will automatically add the contents of the line and you can edit it to change it according to your suggestion in your mind.

(Only applies if you clicked on Start a review:) Once you’re done commenting all of the proposed changes, you can click on the accent button labelled Review changes and pick if you want to Comment, Approve or Request changes to the PR. See the descriptions of each radio button for more information.

There you go, that’s how you review a PR.

Tip

Use four or more backticks for fenced code blocks in Markdown to add fenced code block syntax in a code block.

This is how you embed code block syntax inside a code block to demonstrate:

````markdown
Look at this code!

```javascript
console.log("I’m a line of code!");
```
````

@yanthomasdev

Copy link
Copy Markdown
Member

Thanks @rdwz, a few links are broken here. Could you update them?

/de/basics/project-structure/
  [ # ] /de/install-and-setup/#manual-setup

/de/install-and-setup/
  [ # ] /de/develop-and-build/#start-the-astro-dev-server

*** Found 2 link issues:
  [ # ] 2 broken fragment links

Error: Broken fragment link in src/content/docs/de/basics/project-structure.mdx, line 121: The linked page does not contain a fragment with the name "#manual-setup". Available fragments: #theme-icons, #gradient, #starlight__sidebar, #__tab-tutorial, #__tab-anleitungen-und-beispiele, #__tab-referenz, #__tab-ökosystem, #starlight__mobile-toc, #starlight__on-this-page--mobile, #starlight__on-this-page, #learn-astro-course-1, #_top, #voraussetzungen, #browserkompatibilität, #installation-über-den-cliassistenten, #tab-68, #tab-69, #tab-70, #tab-panel-68, #tab-panel-69, #tab-panel-70, #tab-71, #tab-72, #tab-73, #tab-panel-71, #tab-panel-72, #tab-panel-73, #clioptionen, #integrationen-hinzufügen, #tab-74, #tab-75, #tab-76, #tab-panel-74, #tab-panel-75, #tab-panel-76, #theme-oder-startervorlage-verwenden, #tab-77, #tab-78, #tab-79, #tab-panel-77, #tab-panel-78, #tab-panel-79, #manuelle-installation, #tab-80, #tab-81, #tab-82, #tab-panel-80, #tab-panel-81, #tab-panel-82, #tab-83, #tab-84, #tab-85, #tab-panel-83, #tab-panel-84, #tab-panel-85, #docsearch-lvl0, #learn-astro-course-2
Error: Broken fragment link in src/content/docs/de/install-and-setup.mdx, line 90: The linked page does not contain a fragment with the name "#start-the-astro-dev-server". Available fragments: #theme-icons, #gradient, #starlight__sidebar, #__tab-tutorial, #__tab-anleitungen-und-beispiele, #__tab-referenz, #__tab-ökosystem, #starlight__mobile-toc, #starlight__on-this-page--mobile, #starlight__on-this-page, #learn-astro-course-1, #_top, #bearbeite-dein-projekt, #starte-den-astro-entwicklungsserver, #tab-9, #tab-10, #tab-11, #tab-panel-9, #tab-panel-10, #tab-panel-11, #arbeit-im-entwicklungsmodus, #erstelle-deine-website-und-schaue-dir-eine-vorschau-an, #tab-12, #tab-13, #tab-14, #tab-panel-12, #tab-panel-13, #tab-panel-14, #nächste-schritte, #konfiguriere-deine-entwicklungsumgebung, #entdecke-astros-funktionen, #nimm-am-einführungs-tutorial-teil, #docsearch-lvl0, #learn-astro-course-2

@trueberryless trueberryless left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the translation @rdwz!

No worries, I am not totally inactive during summer holidays. So I went through some already existing nit picks to give some opinions and guidance.

Some bigger points I want to highlight without dedicated line suggestions (because it would be too many):

  1. It seems that some sentences went completely missing during the translation. I especially noticed that the many sentences in each step of the "Manual installation" section was often completely forgotten. To give some examples: One, two, three, four, etc. Could you please "self-review" the translation and compare the original with your translation. We would like to make sure that all sentences get the honor of being translated 😅

  2. I would like you to include full empty lines before and after each <Steps> and </Steps> usage. The reason for this seemingly nitpicky suggestion is that we noticed some parser issues in the past, which completely ruined the layout (Discord). If you are not on the Discord yet and can't access the conversation, I can recommend joining of course. But just in case, here is a screenshot of the important info:

    Image

And would you do me a favour and rename the PR title to: i18n(de): translate install-and-setup.mdx

Otherwise the translation looks really solid.

title: Astro installieren
sidebar:
label: Installation
description: "So installierst du Astro und startest ein neues Projekt."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about something like:

Suggested change
description: "So installierst du Astro und startest ein neues Projekt."
description: "Eine Anleitung zur Installation von Astro und zum Starten eines neuen Projekts."

It's more passive so definitely less clickbait if you insist @randomguy-2650. IMHO all suggestions here and the original are fine as well 👍

Comment thread src/content/docs/de/install-and-setup.mdx
Comment thread src/content/docs/de/install-and-setup.mdx

## Browser‑Kompatibilität

Astro basiert auf Vite, das standardmäßig moderne Browser mit aktueller JavaScript‑Unterstützung anvisiert.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@randomguy-2650 I think if you look at the original text, it is intended to be in one line. I think @rdwz just separated both sentences to individual lines for readability, which will render as no newline, so I think it is correct as is, no empty line needed.


## Browser‑Kompatibilität

Astro basiert auf Vite, das standardmäßig moderne Browser mit aktueller JavaScript‑Unterstützung anvisiert.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One thing I would like to simplify though for readability, is:

Suggested change
Astro basiert auf Vite, das standardmäßig moderne Browser mit aktueller JavaScript‑Unterstützung anvisiert.
Astro basiert auf Vite, welches standardmäßig Browser mit moderner JavaScript‑Unterstützung anvisiert.

I personally like to use "welches" in such cases because it makes it less confusing with the variety of meanings of "das" in the German language (better readability).

- tsconfig.json
</FileTree>

8. Starte jetzt den Astro‑Entwicklungsserver und sieh dir die Live‑Vorschau deines Projekts an!

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add the link to our other docs page here as it is done in the original:

Suggested change
8. Starte jetzt den Astro‑Entwicklungsserver und sieh dir die Live‑Vorschau deines Projekts an!
8. [Starte jetzt den Astro‑Entwicklungsserver](/de/develop-and-build/#starte-den-astro-entwicklungsserver) und sieh dir die Live‑Vorschau deines Projekts an!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

i18n Anything to do with internationalization & translation efforts - ask @YanThomas for help!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants