Estos últimos días estuve trabajando en unos cambios del diseño de formulario de registro ya que el jefe solicitó que tuviera un sistema registro visualmente diferente.
En un principio contábamos con un solo formulario de registro opciones para elegir el tipo de rol pero actualmente decidimos que se muestran los roles disponibles para registrarse con sus características que tendrán dentro de la web.
These past few days, I've been working on some changes to the registration form design because the boss requested a visually different registration system. Initially, we had a single registration form with options to choose the role type, but we've now decided to display the roles available for registration, along with their respective features, on the website.
Una vez que el usuario elige error al cual se va a registrar el formulario se ejecutará una vez por cada campo que debo rellenar.
Once the user selects the error to be registered, the form will be executed once for each field that must be filled out.
By this, I mean that for each required field, there is a form, not exactly in code, but visually, because it's not optimal to apply a registration form for each field the user has to fill out. This work took me a little longer than I expected because I need to validate each form step and display all the necessary alerts for each step, plus some security measures to prevent skipping required steps.
I've attached some images of what the form looks like, both in code and on the client side. Regarding the code, to avoid having to import a large number of forms, I decided to use dynamic rendering with a variable within the form so that it appears as if each field can be completed, allowing you to move on to the next.