-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shifting to NextJS #58
Comments
Also i would like to contribute to this issue. |
Hello @Ayush4web, Welcome to the Community. |
You can start working on it. |
REMEMBER: Create a new branch for these changes and also open a draft PR for this issue so that I am able to look into. |
Hey @Ayush4web Are you currently working on this issue? |
@arpitghura I'd love to take this up if it's not being currently worked on |
Hey @abdullahranginwala You can work on this repo as @Ayush4web is not responding. If he is available, he will assist you. I am assigning this issue to you. REMEMBER: Create a new branch for these changes and also open a draft PR for this issue so that I am able to look into. |
I would like to take this up if the current progress is not satisfactory. |
@abdullahranginwala are you currently working on this issue? |
Hey @zemetskiym You can contribute to this. |
SPA provides a better user experience & Fast loading of webpages.
NextJS is good option for the SSR and SPA
We can keep the current styling and markup maybe tweek something and shift this application to next and it would provide us with some of the great features of NextJS.
Also we will use containers since this is a production application.
The text was updated successfully, but these errors were encountered: