Please check if the PR fulfills these requirements
[X] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR is purely a feature PR.
Before (left), After (right)
What is the current behavior? (You can also link to an open issue here)
The current application doesn't have translations, form validation is implemented manually and the design components are basic HTML with sprinkled CSS.
The header is a very basic text as a logo.
Desktop browsers were not taken into account for the design/behavior of the page.
What is the new behavior (if this is a feature change)?
Added solid-i18next for translation support.
Added Hope-UI for design components.
Added felte/Solid for form validation.
Refactored the Login page code/JSX/CSS to change both how form validations are being conducted and the look&feel.
Added support for SVGO and a new logo in both SVG and PNG.
Changed the page design to work on both mobile and desktop.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
This PR changes the behavior of the Login page including validations for the email and password fields.
While the Login page is a standalone page, the password validation change can affect existing customers who created weaker password and will have an issue to login.
Following this PR, the signup form should change to reflect the password validation requirement for newly registered users.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR is purely a feature PR.
Before (left), After (right)
What is the current behavior? (You can also link to an open issue here)
The current application doesn't have translations, form validation is implemented manually and the design components are basic HTML with sprinkled CSS.
The header is a very basic text as a logo. Desktop browsers were not taken into account for the design/behavior of the page.
See Issues:
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
This PR changes the behavior of the Login page including validations for the email and password fields. While the Login page is a standalone page, the password validation change can affect existing customers who created weaker password and will have an issue to login.
Following this PR, the signup form should change to reflect the password validation requirement for newly registered users.
Other information:
None.