YNU-620: Mobile Header Customization & Versioning Robustness #100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚀 Summary
This PR aligns the Mobile Navbar with Figma designs (implementing a custom 2-row layout) and ensures the robustness of the Versioning Lifecycle Scripts (
release,remove,reset).Screenshots:
Mobileview:

Desktop view:

📐 Technical Decision: Mobile Header Customization
The Requirement
Strict adherence to Figma design:
The Solution: Component Swizzling
We chose the Component Swizzling approach to wrapping the
Navbar/MobileSidebar/Headercomponent.Implementation Details
src/theme/Navbar/MobileSidebar/Header/index.tsx(Swizzled)🛠️ Technical Decision: Versioning Scripts & Configuration
The Requirement
A robust command-line flow to Release, Test, and Reset versions without corrupting the project state.
The Fixes
path: '0.5.x'for the frozen version indocusaurus.config.tsto prevent it from colliding with thecurrent(0.6.x) docs at the root path/docs/.legacySidebarreferences fromversioned_sidebarssnapshots, ensuring no warnings about missing directories.release-version.jsto ensure it snapshots correctly before bumping the package version.✅ Verification
npm run version:release 0.5.x 0.6.x-> Success.npm run version:reset 0.5.x-> Cleanly allows reverting to single-version state.