[CAL-3880] remove i18n for all <Meta> or figure out how to SSR

[PeerRich]

we have a lot of key/string pairs in social media previews:

either option 1: we remove all t("no_meeting_found") etc. with  → "No meeting found" and enforce english for page titles

option 2: we figure out how to SSR the translations for Meta

_CAL-3880

[PeerRich]

/bounty 20

[algora-pbc]

💎 $20 bounty • Cal.com, Inc.

Steps to solve:

1. Submit work: Create a pull request including /claim #15354 in the PR body to claim the bounty
2. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to calcom/cal.com!

Add a bounty • Share on socials

[adithyaakrishna]

/attempt

Algora profile	Completed bounties	Tech	Active attempts	Options
@adithyaakrishna	5 bounties from 1 project	JavaScript, TypeScript, Go & more		Cancel attempt

[adithyaakrishna]

@PeerRich IMO the easiest way would be to go with Option-1 but if we choose to go with option-2, we might have to use the locale param in the opengraph API along with SSR

[rohanjadhav05]

/attempt

Options

• Cancel my attempt

[akashMasih]

attempt #15354

[panzacoder]

/attempt

[panzacoder]

@PeerRich Could you provide an example of a link that is incorrectly SSRing for different locales? Or is it all pages and only for certain locales? It seems from a quick peruse of the i18n code that server-side translations are already enabled so this ticket seems a bit more nuanced than just "figuring out" SSR.

Thanks in advance for any clarity you can provide!

[ydv129]

/attempt

[dfordp]

/attempt

[ranjanmangla1]

/attempt

[Suvendu-UI]

is it still open?

[Suvendu-UI]

/attempt #15354

Options

• Cancel my attempt

[snehalbaghel]

/attempt #15354

Options

• Cancel my attempt

[arshad-muhammad]

@PeerRich since the issue is not closes yet i would like to work on this.