Skip to content

i18n: fixed ES landing title#2341

Open
jmherzo wants to merge 1 commit into
expressjs:mainfrom
jmherzo:jmherzo/change-es-landing-title
Open

i18n: fixed ES landing title#2341
jmherzo wants to merge 1 commit into
expressjs:mainfrom
jmherzo:jmherzo/change-es-landing-title

Conversation

@jmherzo
Copy link
Copy Markdown

@jmherzo jmherzo commented May 22, 2026

Description:
The current landing page title for express.js on spanish (es) is wrong. It's translating literally the word "framework" into "marco" which does not make any sense for spanish speaking web developers.

The proposal is to keep the word "framework" in english which is widely known in spanish speaking countries for web development also, I proposed a small tweak of words to better explain the word "unopinionated" in spanish.

Current landing page title in spanish:
Screenshot 2026-05-21 at 22 19 14

Proposed change:
Screenshot 2026-05-21 at 22 21 11

@jmherzo jmherzo requested a review from a team as a code owner May 22, 2026 04:21
@netlify
Copy link
Copy Markdown

netlify Bot commented May 22, 2026

Deploy Preview for expressjscom-preview ready!

Name Link
🔨 Latest commit d1148a6
🔍 Latest deploy log https://app.netlify.com/projects/expressjscom-preview/deploys/6a0fd9e1cb99bb0008de1e48
😎 Deploy Preview https://deploy-preview-2341--expressjscom-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 97 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: 80 (no change from production)
View the detailed breakdown and full score reports
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@ShubhamOulkar
Copy link
Copy Markdown
Member

Hola👋 @jmherzo, thank you for finding translation issue. We do not manually create or edit translation files. These files are automatically managed by Crowdin and will be overwritten if you make manual changes. All translation updates must go through the Crowdin workflow.

Please read docs on i18n : https://github.com/expressjs/expressjs.com/blob/main/docs/i18n.md
Join translations on Crowdin : https://express.crowdin.com/website

@jmherzo
Copy link
Copy Markdown
Author

jmherzo commented May 22, 2026

Hola👋 @jmherzo, thank you for finding translation issue. We do not manually create or edit translation files. These files are automatically managed by Crowdin and will be overwritten if you make manual changes. All translation updates must go through the Crowdin workflow.

Please read docs on i18n : https://github.com/expressjs/expressjs.com/blob/main/docs/i18n.md Join translations on Crowdin : https://express.crowdin.com/website

Thanks @ShubhamOulkar! I have joined crowdin and I've saved the change in the crowdin ui. what's next?

Screenshot 2026-05-22 at 10 59 45

(it's saying I can't use framework but using the word in english is correct for the spanish speaking devs).

@swarnim-dev
Copy link
Copy Markdown

Supporting @jmherzo's change here — keeping "framework" untranslated is the right call. In Spanish-speaking developer communities, "framework" is universally understood as a technical term and is never translated to "marco". This is consistent with how other major projects (MDN, Vue, React) handle the word in their Spanish docs. The Crowdin flag seems to be a false positive from an overly strict translation rule. Worth overriding it in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants