Skip to content
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

[FEATURE REQUEST] Migrating Website to Next.js, TypeScript, and Tailwind CSS #935

Closed
s2sharpit opened this issue Jun 27, 2023 · 4 comments
Closed

Comments

@s2sharpit
Copy link

s2sharpit commented Jun 27, 2023

Description

I would like to propose migrating our website to Next.js, TypeScript, and Tailwind. I believe that this would improve the performance, maintainability, and overall quality of our website.

Benefits of migrating to Next.js

  • Performance: Next.js is a server-rendered framework, which means that our website will be pre-rendered on the server before it is sent to the client. This will improve the loading speed of our website, especially for users with slow internet connections.
  • Maintainability: Next.js is built on top of React, so we will be able to use all of the same React components and libraries that we are already using. This will make it easier to maintain our website, as we will not have to learn a new framework.
  • Quality: Next.js comes with a number of features that can help us to improve the quality of our website, such as automatic code splitting, static site generation, and server-side rendering. These features can help us to improve the performance, SEO, and security of our website.

Benefits of using TypeScript

  • Type safety: TypeScript is a typed language, which means that the compiler will check the types of our variables and expressions. This can help us to catch errors at compile time, rather than at runtime.
  • Code clarity: TypeScript can help to make our code more clear and concise. This is because TypeScript allows us to use type annotations to document our code.
  • Refactoring: TypeScript can make it easier to refactor our code. This is because the compiler will be able to check that our code is still valid after we have made changes.

Benefits of using Tailwind CSS

  • Speed: Tailwind CSS is a utility-first CSS framework, which means that we can only import the CSS that we need. This can help to improve the loading speed of our website.
  • Flexibility: Tailwind CSS is very flexible, which means that we can customize the look and feel of our website without having to write a lot of CSS.
  • Simplicity: Tailwind CSS is very simple to learn and use. This makes it a good choice for beginners and experienced developers alike.

Proposal

I propose that we start migrating our website to Next.js, TypeScript, and Tailwind in the next sprint. I have already created a starter project that we can use as a starting point. I would be happy to help with the migration process.

Questions

  • Do you have any questions about my proposal?
  • Are you interested in starting the migration process in the next sprint?
@github-actions
Copy link

Congratulations, @s2sharpit! 🎉 Thank you for creating your issue for Moksh. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work! Should you have any queries or require guidance, do not hesitate to ask.

@s2sharpit
Copy link
Author

Hey @akshitagupta15june

I would like to work on this under GSSoC.
Please add the label gssoc23.
And assign it to me.

धन्यवाद

@s2sharpit s2sharpit changed the title [FEATURE REQUEST] Migrating React.js Website to Next.js, TypeScript, and Tailwind CSS [FEATURE REQUEST] Migrating Website to Next.js, TypeScript, and Tailwind CSS Jun 27, 2023
@karthiknadar1204
Copy link
Contributor

@s2sharpit This project is intended to be beginner friendly for people just getting started out so we don't plan on migrating to a new tech stack any time sooner.
Please close this issue for now and explore the tissues to contribute to.
Thank you

@s2sharpit
Copy link
Author

@s2sharpit This project is intended to be beginner friendly for people just getting started out so we don't plan on migrating to a new tech stack any time sooner. Please close this issue for now and explore the tissues to contribute to. Thank you

Thank you for considering my proposal and providing your feedback. I completely understand the intention to keep the project beginner-friendly, and I appreciate your perspective.

While I agree that introducing a new tech stack can have its complexities, I'd like to emphasize the potential benefits it could bring, particularly in terms of performance, maintainability, and overall quality. However, I respect the decision to prioritize a beginner-friendly environment.

If there are any specific areas within the current tech stack where improvements could be made, I'd be more than happy to contribute and help enhance the project in any way possible.

Once again, thank you for your time and consideration. I'll be exploring other issues to contribute to and supporting the project in any way I can

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants