Issue: Create Login Screen with Vuetify without logic implementation

[MarkCarraschi]

Sure! Here’s a sample GitHub issue that you can add for building the login screen in Vue 3 using the Vuetify framework:

---

Issue: Create Login Screen with Vuetify (No Logic Implementation)

Description:

Build a login screen using Vue 3 with the Vuetify framework. This screen will include:

• Two text fields (email and password).
• Validation rules for user input.
• Two buttons (Remember Password and Login).

However, the logic for button actions (Remember Password and Login) will not be implemented in this issue. The focus is solely on the UI and validation setup.

Requirements:

1. Text Fields:

   • Create two Vuetify <v-text-field> components for:
     • Email: with validation rules such as "required" and "valid email format".
     • Password: with validation rules such as "required" and a minimum of 8 characters.

2. Validation Rules:

   • Add validation rules for each text field:
     • Email Field: Required and should be a valid email.
     • Password Field: Required and should have a minimum of 8 characters.

3. Buttons:

   • Create two buttons using Vuetify <v-btn> component:
     • Remember Password button (no logic implementation).
     • Login button (no logic implementation).

4. Layout:

   • Use Vuetify’s grid system to layout the components appropriately (centered form, properly spaced buttons).

UI Components:

• Two text fields: (Vuetify Text Fields)
  • Email
  • Password
• Two buttons:
  • Remember Password (- Vuetify CheckBox)
  • Login(- Vuetify Btn)

Validation Details:

• Email field:

  • Required.
  • Valid email format (basic validation like the presence of '@').

• Password field:

  • Required.
  • Minimum of 8 characters.

Notes:

• No backend logic or API integration is required in this issue.
• No functionality for the "Remember Password" or "Login" buttons should be implemented at this stage.

Reference:

• Vuetify Documentation

---

You can use this as a template and adjust it to your needs before adding it as a GitHub issue.

[MarkCarraschi]

This is related with issue #17