Simon Willison

This is relevant to the big refactor in: - #1518

I spotted in https://github.com/simonw/datasette/issues/1719#issuecomment-1108888494 that there's actually already an undocumented implementation of `?_extras=foreign_key_tables` - https://latest.datasette.io/fixtures/simple_primary_key/1.json?_extras=foreign_key_tables I added that feature all the way back in November 2017! https://github.com/simonw/datasette/commit/a30c5b220c15360d575e94b0e67f3255e120b916

I'll also encourage testing against both Datasette 0.x and Datasette 1.0 using a GitHub Actions matrix.

OK, I'm convinced that it's time to start figuring this out. I've done a little bit of this with Django in the past, but Datasette isn't built on Django. It...

My hope is that Datasette actually has a relatively small i18n footprint - there really aren't that many screens with strings that will need translating. Translating the documentation would be...

Some tutorials that look useful: - https://blog.miguelgrinberg.com/post/the-flask-mega-tutorial-part-xiii-i18n-and-l10n - https://phrase.com/blog/posts/i18n-advantages-babel-python/

I don't want to start any efforts around documentation translation until after the Datasette 1.0 release, because I'd like to be confident that we're not translating documentation that may have...

This is a good idea - it matches the way `datasette .` works for mutable database files already.

This relates to this much larger vision: - #417

I'm going to default maxscale to 2 but provide an extra command line option for `datasette publish cloudrun` which lets people set it to something higher if they want to.