Use new design and add user flows as dummy pages WD-8469

[edlerd]

• adjusted to new design
• added dummy pages for register, reset, device and setup

[codecov]

Codecov Report

Attention: 21 lines in your changes are missing coverage. Please review.

Comparison is base (0f7031f) 76.55% compared to head (88bb621) 75.60%.
Report is 118 commits behind head on main.

Files	Patch %	Lines
internal/monitoring/noop.go	0.00%	11 Missing ⚠️
pkg/kratos/handlers.go	83.33%	3 Missing and 1 partial ⚠️
internal/logging/noop.go	0.00%	2 Missing ⚠️
pkg/kratos/service.go	94.44%	1 Missing and 1 partial ⚠️
pkg/status/service.go	33.33%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #216      +/-   ##
==========================================
- Coverage   76.55%   75.60%   -0.95%     
==========================================
  Files           9       11       +2     
  Lines         627      537      -90     
==========================================
- Hits          480      406      -74     
+ Misses        134      116      -18     
- Partials       13       15       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[shipperizer]

it is quite a lot of code in just one commit, any chance to split it into smaller ones?

[edlerd]

it is quite a lot of code in just one commit, any chance to split it into smaller ones?

It's not that many code changes, most of the lines are due to dependency updates in package-lock.json, which are a prerequisite for other changes. So factoring them out into individual PRs is painful, because they would rely on each other.

Edit: I changed the structure of the PR, keeping the changes, but breaking them into a bit smaller commits.

[nsklikas]

LGTM other than the comment I made on the login page. One thing I don't understand is what the plan is for these registration pages, the fields are going to come from Kratos and I would expect that we are going to ask for more attributes rather than just username and password. We can iterate on this further when we do the work on the backend so I have no problem with merging this once the issue on the login page is fixed.

Here are some screen shots on what the new pages look like:
Login Page:

OIDC Error:

Register Secure:

Register Complete:

Register Email:

Register Password:

Register Secure:

Reset Check:

Reset Complete:

Reset Email:

Reset Password:

Setup Complete:

Setup Password:

Setup Secure:

[shipperizer]

@edlerd looks good to me afaict, what is the policy for frontend tests?how do we catch broken UI?

[nsklikas]

One more minor thing and I think we can merge it

[nsklikas]

LGTM

[lukasSerelis]

Looks good. MFA options obviously missing but I assume this is out of scope at this stage