Yesterday, some of us had an idea about a cooking site for non-English users. Although there is a site for English-speaking users about cooking, Spanish-speaking users can't use it, since the cultural difference is huge.

I understand the policy, 6 years ago. But right now, the policy has no meaning...

  • We have a translation system fully working for every non-English site.
  • We have a user base that we can get into the site.
  • We have a couple of CM that speak Spanish

Can we at least review the policy?

  • 4
    Cooking in Seasoned Advice is full of references to products only available in US market, making it unsuitable to LatinAmerica/Spanish countries. Even raw vegetables aren't the same.
    – Candid Moe
    Commented Aug 6, 2021 at 16:00

1 Answer 1


There are more considerations to be had than just having some existing tooling in place to support it (e.g. do we use something like es.cooking.se.com or different domains entirely, and what happens if someone proposes a non-English site for a topic that has no English equivalent yet). We have absolutely no game plan for supporting different languages of other sites right now and that game plan isn't going to snap into existence any time soon.

Expanding our non-English presence requires a lot more thought than just new proposals on Area 51 from interested parties. For the time being, we are simply not interested in opening new non-English sites and, as the close reason mentions, we will let you all know if/when that ever changes.

  • In that case, update the policy about non english site requests, since that things are not in the original policy... the other things we are pointing, are invalid right now... Commented Aug 6, 2021 at 16:30
  • 6
    We already removed the link to the old policy from the close description because we didn't view it as relevant today. The close reason pretty succinctly states the policy: we just don't allow non-English proposals right now.
    – animuson StaffMod
    Commented Aug 6, 2021 at 16:32
  • do we use something like es.cooking.se.com or different domains entirely yes, it seems like a fantastic idea! what happens if someone proposes a non-English site for a topic that has no English equivalent yet Doesn't matter. English is not (or should not, any language) be the center of everything. Give me more examples, I bet they are all refutable like these two.
    – Dante S.
    Commented Jan 21, 2022 at 19:39
  • 1
    @DanteS. Those were example questions that are serious infrastructure considerations. E.g. our system is not designed to handle those situations right now, so we cannot support them. It's not as simple as just saying "ok we'll do that." It would be a very significant amount of work.
    – animuson StaffMod
    Commented Jan 21, 2022 at 19:41
  • It may be true, but then why did they agree to create sites in other languages before? What happened in between?
    – Dante S.
    Commented Jan 21, 2022 at 19:43
  • I think it would be better to ask it in a meta question, right?
    – Dante S.
    Commented Jan 21, 2022 at 19:44
  • I apologize for the comment (already deleted). I let myself go a little. I'll say it again, but in a good way. Please, I ask you not to make excuses, if the real reason is that you only care about sites in English, say so. Anyway, before someone wants to answer me, now I perfectly understand their reasons. and I am relieved that it is not to have English in the center.
    – Dante S.
    Commented Jan 22, 2022 at 2:00

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .