Fix: #138 - Implement mobile responsiveness for the tour page UI. #198
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Me-Priyank
force-pushed
the
json-schema-tour-priyank
branch
from
86f428e to
1910a58
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What kind of change does this PR introduce?
Bugfix - Corrected mobile responsiveness issues across the tour page.
Issue Number:
Closes 🐛 Bug: Tour page not adjusted for mobile (#138)
Screenshots/Videos:
responsive.tour.mp4
If relevant, did you update the documentation?
No, this is a code fix to the user interface.
Summary
This Pull Request addresses the lack of mobile responsiveness on the main tour components, specifically the lesson navigator and the main editor/validation area. The goal was to ensure the tour is completely usable and readable on screen widths down to 320px.
Changes include:
Does this PR introduce a breaking change?
No breaking changes. This is solely a front-end UI/UX fix.