Issue19/migrate-to-vite

[prak112]

• Manual migration to Vite, Automated migration through cra-to-vite was outdated
• Reorganise codebase :
  • Setup directories
  • Setup frontend service
  • Setup documentation
  • Setup and Refactor components
  • Renamed and setup routing of components
  • Commented possible improvements in components wherever required
  • Suggested tasks to be implemented in /contexts/UserContext.jsx

[haxwell]

FYI, I'll continue reviewing once the package.json issue is addressed.

[haxwell]

Okay. I've got it running now. Using Vite is working out. We can keep that. But the UI changes, those need to be reverted.

We do have an issue (#16 ) to set the default pages (so that you first see the login page, with a create user option, and then once logged in see the home page. From there, you could create a step). So that will be addressed soon.

This PR should be about the plumbing, the infrastucture, but nothing the user sees should change in this PR. See #16

[prak112]

• I agree and understand that this was out of the context of the issue. But I would like you to consider the possibility as described below.
• The user will still be redirected to registration for authentication (this was just for display).

// work-app-frontend/src/components/Home.jsx ....

/**
 * Redirects to the authentication page.
 */
// const verifyUser = () => {
//     // if authorized navigate to steps
//     // if not, navigate to signup and then login
// }

....

- This redirection logic needs to be implemented via [UserContext.jsx](https://github.com/prak112/savvato-work-app-frontend-app/tree/issue19/migrate-to-vite/work-app-frontend/src/contexts)
- My motivation to change the UI was to give a sneak-peek to the user on what exactly the application does. Since it is not clear in any way about what the application is. 
- Also, when a user is just asked to register without giving an idea of what they are registering for, would be cruel. 
- Consider this and let me know. I will redo the changes if you are not convinced of my logic.

[prak112]

Sorry about that. Still learning to work with PRs and reviewing 😄

[haxwell]

The Unix Principle, do one thing and do it well.. is my motivation here! :)

[haxwell]

I just realized I did not, at least in this PR, directly respond to your last message.

"My motivation to change the UI was to give a sneak-peek to the user on what exactly the application does. .. [and more good points].."

I'm not convinced :) I would respond that the user is not looking at these changes. They are all valid, and useful, certainly as proof of concept. But they belong in a separate PR. Your audience here is other developers, not the end user. Gotta make the PRs for developers, even when they benefit the end user.