Newsletter subscription form under Community Page displays technical placeholder variables

[ConnectBhawna]

Describe the bug.

When visiting the community page to subscribe to the newsletter, the input fields for name,email and button are displaying technical variable names (newsletterCTA.nameInput) , newsletterCTA.nameEmail) and (newsletterCTA.subscribeBtn) instead of user-friendly text like "Your name", "Your email." and "Subscribe" . This can confuse users, especially beginners who may not understand what these technical terms mean or what information is expected from them in the input fields.

Impact:

• User Experience: New users or non-technical visitors will find it difficult to understand what information they need to provide. This could lead to frustration and potentially lower subscription rates as users may abandon the form.
• Professionalism: The display of raw variable names gives an impression of an incomplete or unpolished product, negatively affecting the brand's image and trustworthiness.
• Accessibility: Some users may rely on these visual cues to guide them through form fields. Without appropriate labels, the form becomes less accessible, especially for users unfamiliar with the form's purpose.

Expected behavior

The community newsletter form should display user-friendly placeholders just like the main page such as:

Name field: "Your name"
Email field: "Your email"
Button Field: "Subscribe"

Screenshots

How to Reproduce

1. I first go under the file NewsletterSubscribe.tsx and add the params for describing the nameInput and all. {Did this just for the information}
2. I then change the name of Placeholder under InputBox.
3. And than it gives the correct output expected.

🥦 Browser

None

👀 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 ?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[ConnectBhawna]

I am done with solving the issue, if the mentors @derberg, @akshatnema and @quetzalliwrites approve this issue.
I would love to submit the PR around the same. Thanks

[JeelRajodiya]

Please note that this issue is similar to #3236

[sambhavgupta0705]

Closing this as duplicate