[Discussion] : Tech stack decisions for webapp.

[punitkr03]

This issue is created to have a discussion about the tech stack to be used inthe process of making the web application foor the GC server. Current decisions of tech stack is as follows:

• Next.JS for routing and image optimization (also SSR).
• Redux toolkit for state management.
• UI libraries (expendable): Shadcn, Accertainity UI, Magic UI(TBD).

New suggestions are welcome so feel free to share any other technologies.

CC: @majorbruteforce @zakhaev26

[zakhaev26]

I will be providing the common API collection made till now,and feature lists / screen by EOD
@majorbruteforce simultaneosly would be working on streaming part while we build the web interface adn rest APIs.

[ujsquared]

here is the figma https://www.figma.com/design/SssaYtsbzcGpUTQKiUx7eJ/GC-App?node-id=2-2&t=cQ3FCMnfVcYLNP4x-1 for reference

Here are some key issues to be dealt with currently

• Tech Stack to be use
• Handling of issues

let's finalise the tech stack first, from UI libraries to routing. I have very little idea on how front-end works.
@anurag6569201 can you share what all tech stack decisions to be take?

[majorbruteforce]

@punitkr03 please oversee progress in this

[anurag6569201]

so UI library i found Shadcn, Accertainity UI best as punit bhaiya already mentioned that can be great choice for this and frontend in react + vite @ujsquared

[ujsquared]

what about tailwind?

[anurag6569201]

yup tailwind also because those framework using tailwind internally

[ujsquared]

accha, typescript or vanilla js?
also yarn or npm?

[anurag6569201]

npm and vanilla js if the frontend in react + vite with js rather then tx

[ujsquared]

So as per mutual agree with @anurag6569201, here's the following final tech stack for our website:

• JavaScript + npm (won't need much type checking so went for JS; familiar with npm unlike yarn)
• Vite
• React
• Shadcn + Aceternity UI + Tailwind CSS
• Redux

Any more of these technology or stack decisions to be taken will be documented here.
@majorbruteforce @punitkr03 @zakhaev26

[zakhaev26]

Seems productive ..!
would be great if you could write up a piece on this (ofc after setting up the structure) and other things in docs as discussed

CC @ujsquared @anurag6569201

[punitkr03]

Use Typescript for the project, will be a good learning experience and also you will learn to write quality code with accountability. It'll be maintainable in the long term. Also I will suggest to use Zustand instead of redux, it has less boiler plate code.
@ujsquared @anurag6569201

[majorbruteforce]

LGTM

[ujsquared]

Use Typescript for the project, will be a good learning experience and also you will learn to write quality code with accountability. It'll be maintainable in the long term. Also I will suggest to use Zustand instead of redux, it has less boiler plate code. @ujsquared @anurag6569201

• i have no problems with using typescript @anurag6569201, your call.
• Looking into zustand rn

[anurag6569201]

ok we can go with tx but i dont think prefering zustand, its good for small and quickstart webapps , better to stick with redux

Use Typescript for the project, will be a good learning experience and also you will learn to write quality code with accountability. It'll be maintainable in the long term. Also I will suggest to use Zustand instead of redux, it has less boiler plate code. @ujsquared @anurag6569201

[ujsquared]

Seems productive ..! would be great if you could write up a piece on this (ofc after setting up the structure) and other things in docs as discussed

CC @ujsquared @anurag6569201

by write-up, you mean documenting our decisions and the reasoning behind it too?
honestly i have no clue about the reasoning and will have to learn stuff on the get go. So i won't have much to write. Maybe down the line when we have an idea of the project and made some progress?

[anurag6569201]

Seems productive ..! would be great if you could write up a piece on this (ofc after setting up the structure) and other things in docs as discussed
CC @ujsquared @anurag6569201

by write-up, you mean documenting our decisions and the reasoning behind it too? honestly i have no clue about the reasoning and will have to learn stuff on the get go. So i won't have much to write. Maybe down the line when we have an idea of the project and made some progress?

we will document all those as we proceed with our task day by day

[zakhaev26]

Seems productive ..! would be great if you could write up a piece on this (ofc after setting up the structure) and other things in docs as discussed
CC @ujsquared @anurag6569201

by write-up, you mean documenting our decisions and the reasoning behind it too? honestly i have no clue about the reasoning and will have to learn stuff on the get go. So i won't have much to write. Maybe down the line when we have an idea of the project and made some progress?

yes. ofc keep a development first approach - but key design decisions must be documented. would be good experience for project explorers & improve quality.

[punitkr03]

ok we can go with tx but i dont think prefering zustand, its good for small and quickstart webapps , better to stick with redux

Use Typescript for the project, will be a good learning experience and also you will learn to write quality code with accountability. It'll be maintainable in the long term. Also I will suggest to use Zustand instead of redux, it has less boiler plate code. @ujsquared @anurag6569201

Seems fine, you can proceed with this.