We need to configure Phrase to be able to parse the yml files where the marketing website content is stored: https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/tree/main/content/en-us?ref_type=heads On the main issue there's this thread already with relevant conversations: * Are there any existing guidelines for these YAML files? I have some edge cases when selecting if content is translatable or non-translatable. For example, there are some elements (like `id` or `href` in the example below) that would normally be set as untranslatable, but they appear as translated in Spanish files. https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/651#note_3116623325 * Link localization script takes care of that: https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/651#note_3119659344 * @laurenbarker confirmed: Let's not localize the `id` or `href` or `dataGA` attributes. See https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/651#note_3119758783 * TM creation: https://gitlab.com/gitlab-com/localization/localization-team/-/work_items/651#note_3124652618