Sign up with email

As a user I want to sign up into the app using my email address. Name, Email, Password and a checkbox to accept the terms and conditions.

Once I have entered my data, I want to click the Sign Up button to create my account. After the server successfully create my account, I should be redirected to the main page (TBD, maybe profile page? Or search?).

When implementing this, make sure to create a components/Textfield component, we want this component to be reusable in other parts of the application.

const classes = {
  root: styles.someCustomClassForTheRootElement,
  input: styles.customCssForTheInput,
  label: 'something-here',
};

<Textfield value={value} onChange={onChange} classes={classes} label="Email" />

Same for the Checkbox, we want reusable components.

The scope of this class is only to define the UI in the clientside. For the actual login in the backend take a look at:

https://github.com/Coding-Coach/coding-coach-api/issues/9 https://github.com/Coding-Coach/coding-coach-api/issues/12

[dhrubesh]

@gibsonhan Let’s work together if it’s fine with you?

[swissarmykirpan]

@emmawedekind @crysfel

1. Since we have opted to use Auth0 - we no longer need to implement these pages in the front-end stack. Auth0 has the concept of hosted pages - https://auth0.com/docs/hosted-pages/login
2. The epic needs to be reorganised to consider that information
3. The epic needs to contain information about the entire Signup Flow, all the steps, such as:
   • Are we enabling social and email address/password login - and the rationale behind the choice (we could go completely passwordless either via email or MFA)
   • Are we doing any profile enhancement - https://auth0.com/blog/adding-fullcontact-to-your-auth-process-for-profile-enhancement/
   • What happens after sign up - do we present the user with additional profile information steps?
   • Mailing list sign up?

Each of these bits all fulfill the completion of Signup. It will allow us to create stories for each of the bits of work. At the moment this all looks haphazard. There are multiple issues open for the same thing, and it’s incoherent and so it’s very difficult for:

1. A new person to come onboard and see what is what
2. For a stakeholder like @emmawedekind to understand what progress has been made
3. For the person who has identified what work needs to be done.

I apologise if this is overly critical, but we can do a lot better organising the work.