Update sitemap links according to language

[harriebird]

This makes the sitemap links change depending on the selected website language.

This fixes issue #151.

[rileychh-dokploy-coscup]

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

• User: harriebird
• Repository: 2026
• Permission Level: read
• Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.

---

This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

• Executing malicious code on the deployment server
• Accessing environment variables and secrets
• Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

[rileychh]

I think we should use useLocalePath to resolve paths instead of hard-coding paths in the translation files. Existing landing page links hard-code because they're external. @mirumodapon, what do you think?

[mirumodapon]

I think we should use useLocalePath to resolve paths instead of hard-coding paths in the translation files. Existing landing page links hard-code because they're external. @mirumodapon, what do you think?

Since the links are already defined in the locale messages, using them directly also seems like a reasonable approach.

That said, if we decide to adopt useLocalePath, we may need a bit more refactoring—ideally, the locale messages should only contain labels, while route definitions are handled in JS.

For now, I personally prefer keeping things simple and using the links directly from the locale messages.

Just wondering—does this approach have any potential drawbacks we should be aware of?

[harriebird]

Good day @rileychh and @mirumodapon. @mirumodapon is right on how I approached it. I just based the fix on the existing implementation of the sitemap links.

[mirumodapon]

Hi there,
for this PR, the main focus is to resolve the current bug. As for whether we should switch to useLocalePath, I think we can continue that discussion separately in a follow-up discussion or refactor.

[mirumodapon]

LGTM

[harriebird]

Thank you @mirumodapon! :)