This component is available at http://localhost:3000/signup. Or through the login dialog.

I changed the status back to 'In progress' because I need to:

• Add Captcha functionality,

• Move login (email and social) part to modal login component ([#SWIK-243])

Thanks for the comments.
Right now I can think of these two reasons why it might crash:
1) if it's run in build mode there are some problems with connections to microservices, for some reason - as Ali said yesterday, the platform is experiencing some problems with 'build' process, because on 'dev' things look good;
2) if microservices are not configured (cp ./configs/microservices.sample.js ./configs/microservices.js).

I've managed to look at the page (although it crashes if I activate a button).

The form fields needs to have labels as well as placeholder text. Usual practice is also to put * on the labels of required fields. This will improve accessibility and usability. Required fields should also have aria-required="true".

Here's an example from the semantic UI site I've made accessible:

<form class="ui form">
<div class="field">
<label>First Name *</label>
<input type="text" name="first-name" placeholder="First Name" aria-required="true">
</div>
<div class="field">
<label>Last Name *</label>
<input type="text" name="last-name" placeholder="Last Name" aria-required="true">
</div>
<div class="field">

I can't test the functions of the buttons and I think the next step is to agree the workflow for a user signing in / creating a new account / forgotten password which we can discuss at the meeting this week. This will then allow us to simplify the forms.

I have added a new library (js-sha512) for password hashing. , could you, please, try 'npm install' and then run the app again?