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 0d7f1de at: https://6932f417e8593695c41da815--layer5.netlify.app

[leecalcote]

@Rajesh-Nagarajan-11, this is great to see. Does this mean no more hardcoded navigation menu for the handbook?

[Rajesh-Nagarajan-11]

Yes @leecalcote no more hard-coded menu