Content heritance for better internationalization

[edimitchel]

Is your feature request related to a problem? Please describe

When doing international content, there is information in formatter which are not always necessary to be translated (dates, type, etc...)
When I change a content from the main language (i.e. english), I have to do the exact change to the other language even it's not different.

Describe the solution you'd like

My first idea was to create a reference to the main content on the dependent content (ex: FR content refers to EN content).
Then all formatter information would be retrieved from the main content to the dependent and any conflictual information on the dependent will be overridden by the one specified on the dependent.

Describe alternatives you've considered

If Nuxt Content could leverage for a internationalization system, dependencies could be identified based on the same name of file with just the folder difference.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[JonathanXDR]

Hey @edimitchel, I had a similar problem here with #3509 but found another solution, what do you think?

[edimitchel]

As my idea is suggested into #3509, I'm closing this one. The other issue is more detailed and suggests other alternatives.