What problem do you want to solve?
Right now we have eight different language sites, most of which don't get much traffic.
Unfortunately, Netlify has changed how they charge and instead of build minutes they are now charging per production deploy. That means every time we merge a change in this repo it does 8 production deploys, and if we multiply that times the number of dependencies that get updated, that's a lot of deploys for not much additional benefit.
What do you think is the correct solution?
We could collapse all of the sites into eslint.org instead of having separate sites.
There is a convention of using /language-code, such as /en for English, to indicate the language. That also allows us to easily switch languages at any time and add new languages when we want.
I'd also suggest switching to Astro as part of this process, which makes it easy to render multiple different versions of the same page.
Participation
Additional comments
No response
What problem do you want to solve?
Right now we have eight different language sites, most of which don't get much traffic.
Unfortunately, Netlify has changed how they charge and instead of build minutes they are now charging per production deploy. That means every time we merge a change in this repo it does 8 production deploys, and if we multiply that times the number of dependencies that get updated, that's a lot of deploys for not much additional benefit.
What do you think is the correct solution?
We could collapse all of the sites into eslint.org instead of having separate sites.
There is a convention of using
/language-code, such as/enfor English, to indicate the language. That also allows us to easily switch languages at any time and add new languages when we want.I'd also suggest switching to Astro as part of this process, which makes it easy to render multiple different versions of the same page.
Participation
Additional comments
No response