i18n(de): use consistent heading in deploy guides [lunaria-ignore]#14175
Open
trueberryless wants to merge 1 commit into
Open
i18n(de): use consistent heading in deploy guides [lunaria-ignore]#14175trueberryless wants to merge 1 commit into
trueberryless wants to merge 1 commit into
Conversation
Contributor
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
|
Preview deployment ✅ Deployment complete!
|
randomguy-2650
approved these changes
Jun 29, 2026
randomguy-2650
left a comment
Contributor
There was a problem hiding this comment.
✅
(Definitely prefer those line breaks between frontmatter and import statements in MDX.)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR updates headings in almost all currently translated
guides/deployfiles of the German translation and consistently changes them to say:"Vorgehensweise der Bereitstellung"(EN:"Deployment Procedure"), because this is a better objective heading than previous translations for"How to deploy"like"Wie man veröffentlicht"or"So funktioniert die Veröffentlichung"- these sound unnatural for a German heading in technical documentation.Additionally, some newlines have been added / removed to make them consistent as well.
It seems like the norm for newlines after the frontmatter and before import statements of Astro components in MDX files in the English version is to not have an empty line. In the current German translation, we mainly use an empty line tho, probably because I always added it because I like the structural independence more 😅
We might adapt it in the future, but for now, let's keep the German newline 😆