Fixed Button Alignment on Onboarding Page [feature/onboarding-button-alignment] #28
+14,289
−1
Conversation
This file contains 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
… on onboarding page (AOSSIE-Org#27)
bibekkd
changed the title
|
too many files changed |
|
try not to create mutiple PRs at once |
|
Thank you, I will remind this, it caused the too many files changes problem |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Description:
This PR fixes the misalignment of the ‘SKIP’, ‘NEXT’, and ‘GET STARTED’ buttons on the onboarding page. Proper spacing and alignment adjustments have been made to ensure a visually consistent and balanced layout.
Changes Made:
Linked Issue:
Closes #27
Benefits:
🎥 Before & After Video Evidence
Frontend.recording.2025-03-11.00.03.01.mp4
Frontend.recording.2025-03-11.00.03.42.mp4
Testing:
Commit Message:
git commit -m "Fix [feature/onboarding-button-alignment]: Corrected button alignment on onboarding page (#27)"