[BUG] Missing "Welcome" Dropdown in Mobile View

[Shriya-Chauhan]

Describe the bug.

The "Welcome" dropdown is missing in the mobile navigation. This results in a confusing UI experience.

Expected behavior

" Welcome " should be appearing on the dropdown for better understanding.

Screenshots

How to Reproduce

Open the AsyncAPI Docs on a mobile device or use Chrome DevTools (F12 → Toggle Mobile View).
Look at the navigation sidebar.
Observe that there is no "Welcome" dropdown, making it difficult to understand the hierarchy.

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

Yes I am willing to submit a PR!

[Shriya-Chauhan]

Hey @anshgoyalevil @devilkiller-ag, I've noticed that the "Welcome" dropdown is missing in the mobile view, likely due to posts.json not having dynamic generation for this section. This affects navigation clarity. Can I go ahead and work on fixing this?

[devilkiller-ag]

@Shriya-Chauhan Go ahead and open a PR for this issue.

[PRAteek-singHWY]

@devilkiller-ag Hey, I noticed this issue was assigned but no PR has been raised yet.
I have a working fix . Please review my PR .

[Shriya-Chauhan]

I believe the root cause is that the content processing in our codebase doesn't properly handle section titles when a _section.mdx file exists in the root directory. While UI fix addresses the symptom, a more comprehensive fix in PR #3741 solves the underlying data generation issue. My approach modifies the walkDirectories function to properly assign section titles from root-level _section.mdx files to all files within that section.

This ensures that the "sectionTitle" property is correctly populated in posts.json for all sections, including the "Welcome" section, which makes it consistently available throughout the application without requiring UI-specific workarounds.

Both approaches can work, but fixing the data at its source will be more maintainable in the long run and prevent similar issues from arising in other parts of the UI.

What do you think @devilkiller-ag ?