Each translation can be difficult and each language does not always have the same word for each concept used by astro
Glossary is like a white paper where translators refer to their approach in their language and ease the continuity between pages and sentence for a better understanding of the user
This issue is here to discuss how we can address this use case and make it available for each translation to have tools they need for the job
My first suggestion was to add a file named glossary.ts with defined terms and can be used for an auto-generated "glossary" page and components for defining abbreviations (with the <abbr> tag) and other words. But it can be tricky to do things the right way and contain issues with the approach.
The other idea was to create a simple glossary.md page but it can be tricky at a larger scale to maintain and keep track of.
Comment with your ideas if you think of another approach with this (like the use of GitHub's wiki, used for example by the french translation team from react docs)
Each translation can be difficult and each language does not always have the same word for each concept used by astro
Glossary is like a white paper where translators refer to their approach in their language and ease the continuity between pages and sentence for a better understanding of the user
This issue is here to discuss how we can address this use case and make it available for each translation to have tools they need for the job
My first suggestion was to add a file named
glossary.tswith defined terms and can be used for an auto-generated "glossary" page and components for defining abbreviations (with the<abbr>tag) and other words. But it can be tricky to do things the right way and contain issues with the approach.The other idea was to create a simple
glossary.mdpage but it can be tricky at a larger scale to maintain and keep track of.Comment with your ideas if you think of another approach with this (like the use of GitHub's wiki, used for example by the french translation team from react docs)