fix: frontend improvements #2754
Merged
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
|
With these being mostly (entirely?) visual changes, are you able to include before/after screenshots in the PR description to show the changes please @p0lycarpio? |
|
Sure @boc-the-git |
boc-the-git
approved these changes
Nov 26, 2023
There was a problem hiding this comment.
Changes look good! Thanks for adding the images @p0lycarpio
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.
What type of PR is this?
(REQUIRED)
What this PR does / why we need it:
(REQUIRED)
This PR aims to improve severals components/pages :
Spacing & margins
Before/After
Markdown on comments & timeline
Before
After
Before
After
Backup/restore page
Before
After
Before/After
Which issue(s) this PR fixes:
(REQUIRED)
N/A