Adding localization options to `posts` model #239

ajolipa · 2025-09-04T01:42:20Z

In this PR

Adds the ability to specify different title and body content for a post for each configured language. In TinaCMS, this will show up below the main rich-text field when creating the post, with one bar for each language other than the default:

On the front end, the localized title and body will be used if they exist, and otherwise the title and body for the default language will be used.

netlify · 2025-09-04T01:42:24Z

✅ Deploy Preview for padp-staging ready!

Name	Link
🔨 Latest commit	`845cde7`
🔍 Latest deploy log	https://app.netlify.com/projects/padp-staging/deploys/68c9a4ee81b78100086f2aa8
😎 Deploy Preview	https://deploy-preview-239--padp-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

netlify · 2025-09-04T01:42:24Z

✅ Deploy Preview for gbof-c19nyc-staging ready!

Name	Link
🔨 Latest commit	`845cde7`
🔍 Latest deploy log	https://app.netlify.com/projects/gbof-c19nyc-staging/deploys/68c9a4ee8b63a50008fe3055
😎 Deploy Preview	https://deploy-preview-239--gbof-c19nyc-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

netlify · 2025-09-04T01:42:24Z

✅ Deploy Preview for juel-staging ready!

Name	Link
🔨 Latest commit	`845cde7`
🔍 Latest deploy log	https://app.netlify.com/projects/juel-staging/deploys/68c9a4ee38d78300080c1fd2
😎 Deploy Preview	https://deploy-preview-239--juel-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

netlify · 2025-09-04T01:44:23Z

✅ Deploy Preview for pss-scavenger-hunt ready!

Name	Link
🔨 Latest commit	`845cde7`
🔍 Latest deploy log	https://app.netlify.com/projects/pss-scavenger-hunt/deploys/68c9a4eeca7a0c00089032da
😎 Deploy Preview	https://deploy-preview-239--pss-scavenger-hunt.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

dleadbetter · 2025-09-04T10:54:20Z

Is there a reason we don't want to keep localization for posts/paths consistent with the way we're doing it for pages? (e.g. allowing users to create folders /en/My-Awesome-Post.mdx).

jamiefolsom · 2025-09-04T13:20:20Z

Is there a reason we don't want to keep localization for posts/paths consistent with the way we're doing it for pages? (e.g. allowing users to create folders /en/My-Awesome-Post.mdx).

Agree, it would be great if any page could be routed via /[lang]/whatever/path, unless there are compelling alternatives.

ajolipa · 2025-09-04T14:14:17Z

Is there a reason we don't want to keep localization for posts/paths consistent with the way we're doing it for pages? (e.g. allowing users to create folders /en/My-Awesome-Post.mdx).

When Anindita and I discussed it we both felt it was a more intuitive user experience to be able to add localized content directly to a specific post rather than having to create a new file for every language for every post. The effect on the routing is the same, with the difference that the slugs aren't localized I guess -- the Spanish version of a post (or whatever) is at /sp/posts/[slug]. I do think this structure gives a better user experience, but not by a huge factor, so if the consensus is to change it then I'll change it. @absempere any thoughts?

absempere · 2025-09-04T15:31:01Z

In terms of translation, it's much easier to translate on the same page instead of having to switch between browser tabs or windows. Given the number of blog posts that could be added, seems like a lot to redo an entire folder of posts multiple times.

It'd be helpful to have localized post titles if possible. It seems a bit odd to have an English title/URL and Portuguese text.

One question: does this mean that every post will have to have an English version? Is it possible to have a post that's only in Spanish, or would that post then have to be a page?

ajolipa · 2025-09-04T20:53:11Z

In terms of translation, it's much easier to translate on the same page instead of having to switch between browser tabs or windows. Given the number of blog posts that could be added, seems like a lot to redo an entire folder of posts multiple times.

Hmm... that makes sense but the way this method works out you're still translating in a different tab, since you have to click through to e.g. the sp object and then enter the title and body. I suppose it would be possible to do a flattened version where all of the different language fields appeared on literally the same page, but then I'd have to update the logic for fetching the localized content on the consuming end... 🤔

It'd be helpful to have localized post titles if possible. It seems a bit odd to have an English title/URL and Portuguese text.

With this set-up the slug isn't localized but the title is. I think there are fancy ways to make like aliases so that the user could add a localized slug and it would display in the URL bar if available, but I'd have to look into that further. This is how we've done it for other sites like MiCA, having the title localized and the slug fixed.

One question: does this mean that every post will have to have an English version? Is it possible to have a post that's only in Spanish, or would that post then have to be a page?

Easy enough to filter out posts with empty title and/or body from the index, so then if a post has no English content it wouldn't show up if you're set to English. What user experience do we want if e.g. you're set to a non-default language and go to the posts index? Should you only see posts that have content in that language? My assumption was you should still see all the posts, with default language text where no localization exists, but is that wrong?

dleadbetter · 2025-09-11T12:19:36Z

Bumping this before it falls off my radar: My concern with this implementation is that we will now have two different ways to localize content: Pages use a directory based method, while posts use a field based method. I'm indifferent about which method is used, but I think it should be consistent across the different content collections.

I chose the directory based method for pages because it simplifies the Tina schema by not requiring additional fields per locale.

Also, maybe out of scope for this task, but we should probably also localize paths for completeness.

ajolipa · 2025-09-15T23:29:28Z

Okay, after further discussion, updated the PR to be consistent across the different models. This involves the following changes:

Adding the ui.allowedActions.createNestedFolders: true parameter to the models with localized content; without this flag set, I was observing the behavior that I would create a folder via the Tina interface and then not be able to access it or its content.
- Question: Does this now allow too much freedom? Was that flag not set to true because we want to create all of the necessary localization folders during initial setup and not allow users to add them? I played around with just creating the folders in the content repo but still wasn't seeing them show up in the CMS though.
Changing localize_pages to localize_content in the config file. The downside of this is backward compatibility obviously but I think the number of sites affected is pretty small and the old name felt misleading if it's actually controlling the setup for pages, paths, and posts. Open to being talked out of it though.
The pages in the navigation no longer default to the default locale pages if the current locale has none. This matches the desired behavior with paths and posts. The home page will still default to the default locale if necessary.

dleadbetter · 2025-09-16T15:02:46Z

src/pages/[lang]/paths/[slug].astro


-  const locales = config.i18n.locales;
-  const paths = await fetchPaths();
+  for (const lang of config.i18n.locales) {


This looks like re-formatting? Any reason for this change?

I wasn't sure how _.each plays with async functions so I just changed it to match how we're getting the static paths here, since we need to fetch paths for each locale separately. (Or is the re-formatting you're referencing something smaller? Definitely possible that some auto-formatting slipped through my notice; VSCode likes to forget that I told it not to auto-format on save...)

Ahh, I see. fetchPaths now requires the locale to be passed as an argument. That makes sense. Yes, good call switching to for, _.each does not handle async requests. 👍

dleadbetter · 2025-09-16T15:04:58Z

src/pages/[lang]/paths/index.astro

    </h1>
    <Cards>
-      { _.map(paths, (path) => (
+      { paths?.length ? _.map(paths, (path) => (


Ternary operators in JSX make things hard to read. Could we do something like:

( !_.isEmpty(paths) && (...) ) ( _.isEmpty(paths) && (...) )

dleadbetter · 2025-09-16T15:08:16Z

tina/content/templates.ts

@@ -0,0 +1,143 @@
+import TinaMediaPicker from '../components/TinaMediaPicker';


Can this be moved back into the content collections? It looks like only two fields are shared between the two.

dleadbetter

Looks good! 👍

ajolipa requested a review from dleadbetter September 4, 2025 01:45

dleadbetter added the v1.4.0 Issues in v1.4.0 label Sep 11, 2025

dleadbetter added next release Issues in the next release and removed v1.4.0 Issues in v1.4.0 labels Sep 12, 2025

ajolipa added 2 commits September 15, 2025 19:33

adding localization for posts content

4b7cbdd

hiding non-localized content

addde41

ajolipa force-pushed the RB-content-i18n branch from 7301142 to addde41 Compare September 15, 2025 23:37

fixing some formatting

ecbdf6a

dleadbetter reviewed Sep 16, 2025

View reviewed changes

ajolipa added 2 commits September 16, 2025 13:51

removing ternary statement from JSX

5c97163

adding template lists back to paths/posts schema directly

845cde7

ajolipa requested a review from dleadbetter September 16, 2025 17:59

dleadbetter approved these changes Sep 16, 2025

View reviewed changes

		@@ -0,0 +1,143 @@
		import TinaMediaPicker from '../components/TinaMediaPicker';

Adding localization options to posts model #239

Are you sure you want to change the base?

Adding localization options to posts model #239

Uh oh!

Conversation

ajolipa commented Sep 4, 2025

In this PR

Uh oh!

netlify bot commented Sep 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for padp-staging ready!

Uh oh!

netlify bot commented Sep 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for gbof-c19nyc-staging ready!

Uh oh!

netlify bot commented Sep 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for juel-staging ready!

Uh oh!

netlify bot commented Sep 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for pss-scavenger-hunt ready!

Uh oh!

dleadbetter commented Sep 4, 2025

Uh oh!

jamiefolsom commented Sep 4, 2025

Uh oh!

ajolipa commented Sep 4, 2025

Uh oh!

absempere commented Sep 4, 2025

Uh oh!

ajolipa commented Sep 4, 2025

Uh oh!

dleadbetter commented Sep 11, 2025

Uh oh!

ajolipa commented Sep 15, 2025

Uh oh!

dleadbetter Sep 16, 2025

Choose a reason for hiding this comment

Uh oh!

ajolipa Sep 16, 2025

Choose a reason for hiding this comment

Uh oh!

dleadbetter Sep 16, 2025

Choose a reason for hiding this comment

Uh oh!

dleadbetter Sep 16, 2025

Choose a reason for hiding this comment

Uh oh!

dleadbetter Sep 16, 2025

Choose a reason for hiding this comment

Uh oh!

dleadbetter left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Adding localization options to `posts` model #239

Adding localization options to `posts` model #239

netlify bot commented Sep 4, 2025 •

edited

Loading

netlify bot commented Sep 4, 2025 •

edited

Loading

netlify bot commented Sep 4, 2025 •

edited

Loading

netlify bot commented Sep 4, 2025 •

edited

Loading