The discussion revolves around translating welcome topics in Discourse. claas points out that certain topics, including “Assets for the site design,” “Welcome to Discourse,” and “READ ME FIRST: Admin Quick Start Guide,” have hardcoded titles and content, which can’t be translated. claas suggests moving these to I18n and removing the corresponding files to avoid inconsistency.
claas goes on to create pull requests (PRs) for these changes, but notes that moving the “Admin Quick Start Guide” might not be desirable due to its current implementation. Instead, a translatable topic could link to the guide.
Falco welcomes the changes, as long as they don’t cause regressions or add complexity. sam mentions that future plans include migrating to a narrative bot, and codinghorror notes that this migration is at least three months away. zogstrip assures that the bot’s content is localizable.
Any reason not to move this to I18n? Probably we should then remove the files WELCOME-TO-DISCOURSE.md and ADMIN-QUICK-START-GUIDE.md to avoid inconsistency, right?! I would be willing to provide a PR for this.
Also, the title of the Uncategorized category seems hardcoded:
Making more stuff i18n, as well as providing language selection on discourse-setup is always welcome, as long it doesn’t trigger a regression and the complexity isn’t too much.
As it turns out, moving the Admin Quick Start Guide probably isn’t desirable, because it specifically invites to submit a pull request to improve the guide. In this case, however, it might be better to not create this as a topic itself, but rather create a translatable topic which links to the guide.
Title is hardcoded.
Body is in I18n.