3
Best Practices for Handling Translations in a Multilingual Website
Source: directus/directus#22682 · opened by @lorenzrabs
Summary Discussing best practices for managing translations in a website with multiple languages. This includes handling cases where pages might exist or be published in only one language, and the implications for data structure and status management. Basic Example We have a pages collection with fields: id, status, translations. Inside translations, we store the slug, title, and seo fields. A potential issue arises when a page exists or is published in only one language. Should we add a status field inside the translations? Motivation To ensure a robust and maintainable approach to managing translations, especially in cases where not all content is available in all languages. This discussion aims to gather insights and best practices to handle these scenarios effectively. Detailed Design • Pages Collection Fields: - id - status - translations: Array of objects containing: - slug - title - [...] (other fields) - seo (m2o relation…
No pledges yet. Be the first to back this.
Comments
Similar requests
Enable field name translations to use "Custom translations"
1 vote · 0 comments
Bundle custom i18n translations with extensions
21 votes · 0 comments
Possibilty to translate dashboard and panel names
18 votes · 0 comments
Revisions don't work together with translations
6 votes · 0 comments
Reusable Field Templates for Consistent and Efficient Schema Design
6 votes · 0 comments
No comments yet.