GitAuto: Turn this website theme and colors into vivid and bright ones (it is dark and lonly now...) #6
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.
Resolves #5
Why is this feature needed?
The website's current theme is dark and somewhat gloomy. This update aims to refresh the look by introducing vivid and bright colors, thereby making the interface more visually appealing and engaging for users.
What and how are we changing? Why this approach?
We modified the Sass variables in the assets/sass/libs/_vars.scss file to update the overall color palette:
These changes were selected to provide a striking contrast and bring more energy to the website's design.
What actions are required from users?
Users should recompile the Sass files or rebuild the website to see the updated theme. No additional configuration changes are required.
How does it work? (Technical details)
The changes are implemented in the Sass variables file:
After merging this PR, running the project's build process will apply the new theme automatically.
Is it backwards compatible?
Yes, this update is fully backwards compatible. Only the color definitions have been modified, and there are no breaking changes to the structure or functionality of the website.
Any other considerations?