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] Mobile view missing "Specification Explorer" & spelling inconsistency in "Migration" #3727

Closed
2 tasks done
PRAteek-singHWY opened this issue Feb 24, 2025 · 4 comments · Fixed by #3737
Closed
2 tasks done
Labels

Comments

@PRAteek-singHWY
Copy link
Contributor

Describe the bug.

When visiting the AsyncAPI website:

On desktop view, the dropdown menu Docs on hovering contains 8 options:

Concepts
Tutorials
Guides
Tools
Reference
Migration
Community
Specification Explorer ✅ (Present)

But

On mobile view, only 7 options are displayed:

Specification Explorer is missing ❌
&
Spelling inconsistency:
Desktop: "Migration"
Mobile: "Migrations" (extra 's' present)

This leads to inconsistencies in navigation, especially for users switching between desktop and mobile.

Expected behavior

The "Specification Explorer" tab should be visible in the mobile dropdown when we click the DOCS drop-down menu, just like on desktop.

The spelling of "Migration" should be consistent across all views (either "Migration" or "Migrations", but not both).

Screenshots

Desktop:-
Image

Mobile View:-
Image

How to Reproduce

  1. Open the AsyncAPI website on desktop.
  2. Hover over the dropdown menu and note that "Specification Explorer" is visible.
  3. Now, open the same website on mobile view.
  4. Open the DOCS dropdown and observe that "Specification Explorer" is missing.
  5. Compare the spelling of "Migration" in both views.

(CHROME and SAFARI)

🥦 Browser

Google Chrome

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

@PRAteek-singHWY
Copy link
Contributor Author

Heyii @ @devilkiller-ag @anshgoyalevil
I have found this bug under the DOCS drop down menu , on mobile window , can I work over it .

@PRAteek-singHWY
Copy link
Contributor Author

@devilkiller-ag sir
Is this the way open source works , because i was waiting on response from you to assign me the issue , because even I had the update ready , but i didn't raised a pull request like @rathoretaruncodes
without getting it assigned.
Spending hours of observation to find any bugs , so that I could contribute but this' real unfair

I request you to please tell me if my take is wrong on this @devilkiller-ag @anshgoyalevil @Mayaleeeee

@devilkiller-ag
Copy link
Member

devilkiller-ag commented Feb 24, 2025

Hey @PRAteek-singHWY, you can submit your PR too. We will approve the best one.
Also, you don't need to wait to get assigned. You can open PR immediately (except for design related).

@PRAteek-singHWY
Copy link
Contributor Author

Hey @PRAteek-singHWY, you can submit your PR too. We will approve the best one. Also, you don't need to wait to get assigned. You can open PR immediately (except for design related).

Yes Sir I got the point , sorry for raising a Design related PR without permission previously.

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