Use separate routes for sign in and sign up
What does this MR do?
Part of gitlab-org/growth/engineering#20 (closed)
Currently, the sign in and sign up form is on the same page and can be toggled with a tab bar. Growth wants to start an experiment to have separate pages and also adjust the design of the sign up page.
Changes when feature flag experimental_sign_up_flow is enabled:
- Instead of
users/sign_in#login-paneandusers/sign_in#register-paneurls, for the experiment it'susers/sign_inandusers/sign_up. - We redirect to
users/sign_upfromusers/sign_in#register-pane. We're doing this inside<head>on purpose to not render anything from the sign in page beforehand. - It removes "Email Confirmation" field, which will hopefully increase conversion.
- Styling is mostly copied from current login, so we can remove it easier when the experiment is done.
- We always use the invisible captcha in our experimental sign up flow.
There will be a follow up MR to split the sign up flow into two steps, as proposed in gitlab-org/growth/engineering#20 (closed).
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Performance and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Nicolas Dular