[Documentation] Add translation guide for adding new languages #78

[Atharavkag]

Linked Issues

Closes #78

Summary

Adds comprehensive documentation and step-by-step guides for translating go-fast-cdn into new languages. This ensures the project is accessible to international contributors.

Changes

• New Guide: Created docs/how-to-add-a-language.md with a step-by-step workflow.
• Examples:Added Spanish (es/) and French (fr/) directories to demonstrate the pattern.
• Tracking: Included README files within language folders for translation progress.
• References: Updated links to the existing Danish (da/) documentation.

Why this is important

• Solves the lack of contributor guidance for i18n (Internationalization).
• Lowers the barrier to entry for non-English speaking developers.
• Standardizes how translations are structured across the repo.

Verification & Testing

• Content Check:Verified all Markdown links are functional.
• Structure: Confirmed new folders match the existing documentation architecture.
• Scope: Documentation only; no functional code changes included.

[kevinanielsen]

For some reason, I can't add comments per line, but the abbreviation for French in step 1 should be /fr, not /r/.

The formatting for code snippets also looks wrong. Use three backticks, ``` instead of the backslashes. e.g. for a bash snippet:

```bash
hello!
```

There are issues with backslash vs regular slashes in a lot of places.

[kevinanielsen]

This file should not be committed

[Atharavkag]

@kevinanielsen Thank you for the thorough review. I've addressed all the issues you pointed out:

1. Fixed Markdown formatting in docs/add-language.md:

   • Corrected all code blocks to use proper triple backticks (bash)
   • Fixed inline code formatting (e.g., /docs/ instead of \/docs/\)
   • Standardized path separators

2. Removed package-lock.json as requested.

All changes have been pushed. Please let me know if there's anything else that needs adjustment.