[BUG] Newsletter page does not have correct button labels

[JeelRajodiya]

Describe the bug.

The labels for the buttons and input fields simply have the i18n placeholders instead of the actual labels

Expected behavior

These are the expected labels

How to Reproduce

1. Go to https://www.asyncapi.com/newsletter or https://www.asyncapi.com/community/tsc
2. You will notice the improper labels

🥦 Browser

Google Chrome

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

No, someone else can work on it

[jayp5545]

I can work on it!

[sambhavgupta0705]

How do we access newsletter page?

[JeelRajodiya]

How do we access newsletter page?

I am not sure either, I was just going through the codebase and found that we have pages/newsletter.tsx file. Which means the page exists at https://www.asyncapi.com/newsletter

[sambhavgupta0705]

@akshatnema do we need this url as we only have newsletter at the home page which is working fine

[hkv24]

@sambhavgupta0705 look at 'components/NewsletterSubscribe.tsx'

[prashantrai-30]

Hey,@JeelRajodiya can you assign this to me.

[JeelRajodiya]

Found it. Here is how you can access the /newsletter page

1. Go to the footer of the website.

2. Click on About

3. Now on the about page. you will find a link to the newsletter

That's not it. The newsletter page is also linked from multiple blogs

[JeelRajodiya]

Hey,@JeelRajodiya can you assign this to me.

Issues are not assigned on the website repo (AFAIK). If the issue is valid, you can start working on it and a create PR.

[Aryan4884]

@JeelRajodiya I can still see this issue present on the website.Can i work on this ?

[JeelRajodiya]

@JeelRajodiya I can still see this issue present on the website.Can i work on this ?

I think PR #3308 is relevant to this issue and is still under review. You should avoid working on the issues which already have a PR open.

[sambhavgupta0705]

Reopening this one

[JeelRajodiya]

@sambhavgupta0705 I think the issue was resolved in #3308. We can close this issue.