Migrate Handbook Pages into MDX Collections

[Rajesh-Nagarajan-11]

Currently

• The Community Handbook pages are currently managed statically, with each page and navigation item

Description

• This PR fixes [Handbook] Table of Contents need to be dynamically generated #6926
• This PR migrates the community handbook pages into an MDX collection and enables dynamic navigation rendering for improved maintainability.

Notes for Reviewers

• Migrate all pages into the MDX collection under src/collections/handbook
• Move all images into their respective collection folders (if any)
• Ensure all content is properly migrated to MDX
• Ensure all styles are preserved after migration
• Remove unwanted files (old pages) and unused assets
• Configure GraphQL queries for MDX collections
• Ensure all collections are dynamically generated
• In this PR, two files : src/sections/Community/Handbook/BookComponent/BookComponent.js and src/sections/Community/Meshmates/index.js — are shown as modified, but there are actually no changes in them. Please ignore those files.

Signed commits

• Yes, I signed my commits.

[l5io]

🚀 Preview for commit f75ad16 at: https://693471861e48342986c632ee--layer5.netlify.app

[saurabhraghuvanshii]

@Rajesh-Nagarajan-11 I noticed another issue with the current change. Clicking on items in the Table of Contents causes the page to reload, but it should navigate smoothly without reloading.

[l5io]

🚀 Preview for commit fc93e77 at: https://693540553ed019cbadb59950--layer5.netlify.app

[Fireentity]

@Rajesh-Nagarajan-11 Thank you for your contribution! Let's discuss this during the website call tomorrow at 6:30 PM IST | 8 AM CT Add it as an agenda item to the meeting minutes, if you would 🙂