[Feature]: Create Layout for Authentication Pages

[Vin-Jex]

Is your feature request related to a problem? Please describe. Currently, in version 2 of the project, there is no dedicated authentication page. As a result, the flow begins with layout pages instead of a proper authentication flow or login interface.

Describe the solution you'd like I would like to avoid duplicating layout elements across multiple pages. The goal is to implement a reusable layout that can be consistently applied to all pages, including the authentication pages.

Below is the proposed UI for the Authentication Page:

[SR2090]

I understand the requirement you need a sign up form with buttons. By reusable you mean one text component that can be used for the different fields and one button component that can be reused for layout. A resource file where we can provide the name and the type of the field based on which validation will be provided. And finally the actual layout of the page that will use the components. I can work on this if you assign it to me. If its anything else then do let me know exactly what do you need as it seems interesting.

[Vin-Jex]

I understand the requirement you need a sign up form with buttons. By reusable you mean one text component that can be used for the different fields and one button component that can be reused for layout. A resource file where we can provide the name and the type of the field based on which validation will be provided. And finally the actual layout of the page that will use the components. I can work on this if you assign it to me. If its anything else then do let me know exactly what do you need as it seems interesting.

Thank you for your interest in contributing! It seems there may be a misunderstanding regarding the nature of the issue. To clarify, the image above is divided into two sections: the left content and the right content.

• The left content will remain the same across all authentication-related routes. To avoid code duplication, we need a reusable layout that ensures consistency across these pages without repeating any code.
• The right content, however, will vary depending on the specific authentication route, and it requires a separate solution.

If you would like to contribute or resolve this issue, please create a new issue using one of the provided issue creation templates. If you now have a better understanding of the requirements and feel confident in tackling this, feel free to request assignment to this issue.

Your contributions are appreciated!

[Vin-Jex]

Seems like everyone is struggling to look into this issue so I will resolve it in a moment.