Reorganize Legal repo for optimized Smartling configuration

[gueroJeff]

The current structure of the legal repo makes it difficult to scale localization through Smartling. We need to adjust the repo structure and file naming conventions to reflect this structure:

• Source path = "/(en|en-US)/.*.md"

• • All ftl files within either the "en" or "en-US" folders

• Target path = "/locale-code/[same as source path / file name].md"

Create a standard template for translating legal doc content through Smartling. Template must be a .md file with the appropriate Smartling directives. Template must be discoverable to legal teams.

The following specifications must be met for a legal content template.

Dependency of Legal Repo issue :

• [x] Legal repo restructuring [x] Change doc_name/locale.md to locale/doc_name.md [x] Identify docs for obsolete or EOLed docs and archive them [x] Identify products with docs directly integrated to the repo so nothing breaks
• [ ] Changes/improvement (Got buy-ins): [x] Standardize file naming convention [x]en-US is a locale, en is the source of localizable content. [ ] CI automation [ ] Create a metadata file to show which doc is localized in what locales.
• [x] Process [x] Set up new branch to reflect the above change requests [x] Once good to go, changes to be made in Bedrock, and share info with teams that have direct integration to the repo [x] QA and verify [x] Switch to new repo.

[peiying2]

New repo structure: https://github.com/mozilla/legal-docs/tree/restructure ready for testing.

• Bedrock (most of legal docs) can make both structures co-exist during transition
• Products with direct integration have different timely to implement the change. Both repos will co-exist to support this need (FxA needs more time).

[peiying2]

1). Legal repo is officially in the new configuration: locale/filenames. 2). Informed CV, FxA and Hubs teams to make code changes accordingly.