Move the frontend to a JavaScript framework #26
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This Pull Request is huge (because I had to change practically every part of the frontend), so bear with me. The main idea is that now every part of the frontend application is contained within a well structured application built with Nuxt.js (the Vue version of Next.js) and to implement SSR. I used Nuxt simply because SSR comes built in and I wanted to experiment with the framework (turned out to be a real delight). The SSR should be done through one of the serverless functions, returning the rendered page of the frontend.
I also used Vuetify to build the frontend. I know that we talked about using Tailwind on #21, but if I used Tailwind this PR would have consumed twice the time to write. I think that we can migrate to Tailwind once the app is correctly functioning with the new setup.
Closes #20, closes #23.
Requirements
None.
Additional changes
None.