[UXIT-3888] Move metadata texts to translations

[CharlyMartin]

📝 Description

This PR adds i18n support for metadata by moving SEO metadata from hardcoded constants to translation files.

🛠️ Key Changes

• Created getTranslatedMetadata utility for consistent metadata fetching via next-intl
• Moved metadata from constants/seo.ts to i18n/translations/en.json and i18n/translations/zh-cn.json. For now, Chinese translations are marked as TODO.
• Removed all constants/seo.ts
• Updated Cypress tests to handle translation-based metadata.

Note

Cypress currently only tests English pages. Chinese support will be done in another PR.

🧪 How to Test

1. npx turbo filecoin-site#dev
2. Visit all updated pages in both English and Chinese locales
3. Inspect page <title> and <meta name="description"> tags
4. Verify metadata matches translations/*.json files

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
filecoin-site	Ready	Preview, Comment	Feb 11, 2026 7:09pm

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
ffdweb-site	Skipped		Feb 11, 2026 7:09pm
filecoin-foundation-site	Skipped		Feb 11, 2026 7:09pm
filecoin-foundation-uxit	Skipped		Feb 11, 2026 7:09pm

[notion-workspace]

[filecoin.io V3] Add locale to createMetadata

[barbaraperic]

Not related to this PR, but we should probably add translation button to mobile?

[barbaraperic]

Just an idea!

What do you think if we included translationKey in the PATHS object? In that way path and translation namespace live together - when you work on a route, you see path, label and which i18n key it uses.

So if we have something like this

type PathConfig = {
  path: NextRouteWithoutLocale
  label: string
  entriesPath?: string
  translationKey?: TranslationKey
}

export const PATHS = {
  BLOG: {
    path: '/blog',
    label: 'Blog',
    entriesPath: `${CONTENT_ROOT}/blog/posts`,
    translationKey: 'blog',
  },
...
}

in the page we can do:

const { translationKey } = PATHS.BLOG

const metadata = await getTranslatedMetadata(translationKey)

and in the tests:

const { path, translationKey } = PATHS.BLOG

const { title, description } = translations[translationKey].metadata

That way we can make sure that path and key stays in sync, and we don't have to use string literals like TRANSLATION_NAMESPACE.

Hope it makes sense!

[CharlyMartin]

Yes, that makes a lot of sense. I will give it a try! Thanks :)