Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Incorrect URLs for Social Handles in Ambassadors Section #3798

Open
2 tasks done
Recxsmacx opened this issue Mar 5, 2025 · 2 comments · May be fixed by #3807
Open
2 tasks done

[BUG] Incorrect URLs for Social Handles in Ambassadors Section #3798

Recxsmacx opened this issue Mar 5, 2025 · 2 comments · May be fixed by #3807
Labels

Comments

@Recxsmacx
Copy link

Describe the bug.

The URLs for social handles in the Ambassadors section of the AsyncAPI website are incorrect. Users are being directed to the wrong profiles when they click on the social media icons.

Expected behavior

Clicking on the social media icons should take the user to the correct social media profiles of the ambassadors.

Screenshots

Screen.Recording.2025-03-05.185635.mp4

How to Reproduce

Navigate to the Ambassadors section of the AsyncAPI website.
Click on daniel kocot twitter handles and checkout others profiles too

🥦 Browser

None

👀 Have you checked for similar open issues?

  • I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

Are you willing to work on this issue ?

Yes I am willing to submit a PR!

@Recxsmacx Recxsmacx added the bug label Mar 5, 2025
@Aditya90456
Copy link

i can fix it today

@Aditya90456
Copy link

@Recxsmacx
Image

Recxsmacx added a commit to Recxsmacx/website that referenced this issue Mar 6, 2025
Fixes asyncapi#3798

Update the Twitter handle for Daniel Kocot in the Ambassadors section.

* Change the Twitter handle for Daniel Kocot from "dk_1977" to "dankocot" in `config/AMBASSADORS_MEMBERS.json`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants