docs: i18n example useless import

[edimitchel]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Useless import of localeProperties

PS: Thank you for that example which comes a bit late but I know will help a lot for others!

That said, I still think this way is very difficult to use in long term when content evolves.. We systematically need to update other content.. I found a solution by using AI which creates PR of the content translated in order to review. I think we could improve the UI to help the content editor to switch between languages..

[vercel]

@edimitchel is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/content@3479

commit: 6ca5e54

[farnabaz]

That said, I still think this way is very difficult to use in long term when content evolves.. We systematically need to update other content.. I found a solution by using AI which creates PR of the content translated in order to review. I think we could improve the UI to help the content editor to switch between languages..

Feel free to open an issue to discuss it

[edimitchel]

There it is :)
#3492