In #112, I added some new string literals to our blog cards but didn't wrap them in internationalization macros, as many of the other strings are. Daniel pointed out that I should for consistency, but then we talked about how I wasn't really set up to provide the translations for all the other languages, and how it was also a little silly to do that given that (a) we aren't generating international versions of our website and (b) there's lots of content on the website that isn't wrapped in internationalization code. That led us to propose potentially just ripping out the internationalization (both the use, and the files supporting it) to simplify things. This issue captures that proposal.
In #112, I added some new string literals to our blog cards but didn't wrap them in internationalization macros, as many of the other strings are. Daniel pointed out that I should for consistency, but then we talked about how I wasn't really set up to provide the translations for all the other languages, and how it was also a little silly to do that given that (a) we aren't generating international versions of our website and (b) there's lots of content on the website that isn't wrapped in internationalization code. That led us to propose potentially just ripping out the internationalization (both the use, and the files supporting it) to simplify things. This issue captures that proposal.