In a recent discussion about our close reasons, it was proposed to add a German explanation. While a basic knowledge of English is required to handle the SE user interface, it is debatable whether understanding a longer phrase like a close reason can still be seen as basic knowledge. We should keep in mind that knowing English is not at all a requirement for learning German in general, and that we might have users here that don't know much more English than needed to translate the "Ask a question" button. We should welcome these users as best as we can and help them to use our site as it is intended. For that objective, I consider it better to use both German and English in some crucial texts on our site than to explain afterwards if we notice that someone doesn't understand English well enough. We might not always notice that!
For that reason, I still support the efforts taken in
Should and can we make more clear to newcomers that we are bilingual?
and
Let’s make a German welcome page/FAQ for visitors who speak little or no English
Additionally, I want to propose
- that we edit parts of our help center so that the texts become bilingual. I figure that we should start with https://german.stackexchange.com/help/on-topic, https://german.stackexchange.com/help/dont-ask and https://german.stackexchange.com/help/closed-questions, but we can discuss other options here
- that we extend all our custom close reasons with links to the help center and to either https://german.stackexchange.com/help/on-topic or https://german.stackexchange.com/help/dont-ask (the one that is better suited to explain the specific close reason) together with the remark "(auch auf Deutsch)". Except for the additional remark, this has been already proposed by Takkat here.
Why not simply have English and German close reasons in parallel? We are limited to 3 custom close reasons, and it seems very unlikely that we, as a beta site, would get an exception. But it wouldn't be no good anyway if some items in the list differed in reason and others only in language.
Why not making the close reasons themselves bilingual? Because each custom close reasons is limited to 400 characters. A bilingual close reason would then have to fit in 200 characters in each language, which might not be enough.