Added responsive contact form with custom styling

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
department-of-it	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 21, 2024 11:53am

[devdaim6]

@Naveed-SNR cxe goy preview fail

gode.karu su theek

[Naveed-SNR]

@Naveed-SNR cxe goy preview fail

gode.karu su theek

jo issues ma log h whi problem h na sirf

[Naveed-SNR]

@devdaim6 check

[devdaim6]

image not required and button wech no border

[Naveed-SNR]

image not required and button wech no border

yi chu lakut msle next commit ma thk karu ga

[Naveed-SNR]

image not required and button wech no border

yi chu lakut msle next commit ma thk karu ga

filhal kar cxe merge

[devdaim6]

and i was thinking of adding a select button in contact too , for categorizing website bug realted contact , or information regarding clubs or something like this may b

[devdaim6]

Message me ? remove that🤣🤣

[Naveed-SNR]

and i was thinking of adding a select button in contact too , for categorizing website bug realted contact , or information regarding clubs or something like this may b

Ath ha chu teli UI ti shearun. Thav wo message ma hii user likhe ga

[devdaim6]

@Naveed-SNR

[devdaim6]

box ko nechay kaha amrica beja hai ? su haav ending if box beyi yus contact info chuna su lagav box nebre kani bone kani ....form aur footer ke beech mai

[Naveed-SNR]

box ko nechay kaha amrica beja hai ? su haav ending if box beyi yus contact info chuna su lagav box nebre kani bone kani ....form aur footer ke beech mai

Ye badi screens p ajeeb hota h agr bahar nikale g box k

Ye acha h aise hii

[devdaim6]

on submit toast sonner i told you to use and clear form fields to ""

[Naveed-SNR]

on submit toast sonner i told you to use and clear form fields to ""

Sorui kati kar aki doh pga wechav waen su

[devdaim6]

@TAWSEEFSHAMIM @Naveed-SNR why all the stuff on a single page ? it should work either conditionally or just new route for the next step but for new routes you have to keeep track of previous state as well

[Naveed-SNR]

@TAWSEEFSHAMIM @Naveed-SNR why all the stuff on a single page ? it should work either conditionally or just new route for the next step but for new routes you have to keeep track of previous state as well

@TAWSEEFSHAMIM was only in charge of designing the sections. Arranging these is my part of the job and I'll start working on it today.

[Naveed-SNR]

@devdaim6 merge this PR, anything that's not working will be fixed later.

[devdaim6]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

[devdaim6]

just have contact and registration page here from now until we merge this until create new seperate branches for each feature , will be easy to manage / merge and probably no conflicts to resolve

[Naveed-SNR]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

You should merge. Other contributors also have to pull and they may face issues like large no. of conflicts if there are too many commits in a single PR.

[devdaim6]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

You should merge. Other contributors also have to pull and they may face issues like large no. of conflicts if there are too many commits in a single PR.

BARADAR THATS WHAT I SAID THEY WILL PULL FROM DEV BRANCH , AND FROM NOW ON CREATE SEPERATE BRANCH FOR EACH THING like events page will have seperate branch clubs etc, just complete this and then will merge it , it wont cause issue dont worry

[Naveed-SNR]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

You should merge. Other contributors also have to pull and they may face issues like large no. of conflicts if there are too many commits in a single PR.

BARADAR THATS WHAT I SAID THEY WILL PULL FROM DEV BRANCH , AND FROM NOW ON CREATE SEPERATE BRANCH FOR EACH THING like events page will have seperate branch clubs etc, just complete this and then will merge it , it wont cause issue dont worry

We're mostly working on one feature at a time, so the dev branch is enough, no need to create a separate branch for every thing. And convey to others that they have to pull from dev branch, if that's what we're doing.

[devdaim6]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

You should merge. Other contributors also have to pull and they may face issues like large no. of conflicts if there are too many commits in a single PR.

BARADAR THATS WHAT I SAID THEY WILL PULL FROM DEV BRANCH , AND FROM NOW ON CREATE SEPERATE BRANCH FOR EACH THING like events page will have seperate branch clubs etc, just complete this and then will merge it , it wont cause issue dont worry

We're mostly working on one feature at a time, so the dev branch is enough, no need to create a separate branch for every thing. And convey to others that they have to pull from dev branch, if that's what we're doing.

converying doesnt make any diff sometimes we just push new commit and i cant review every single detail in every commit thats why if everyone create seperate branch for seperate stuff that wont cause any issues otherwise i have no issues on working only on dev , but its getting complicated day by day because codebase is filling up , cant review every minute step of every commit change

[Naveed-SNR]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

You should merge. Other contributors also have to pull and they may face issues like large no. of conflicts if there are too many commits in a single PR.

BARADAR THATS WHAT I SAID THEY WILL PULL FROM DEV BRANCH , AND FROM NOW ON CREATE SEPERATE BRANCH FOR EACH THING like events page will have seperate branch clubs etc, just complete this and then will merge it , it wont cause issue dont worry

We're mostly working on one feature at a time, so the dev branch is enough, no need to create a separate branch for every thing. And convey to others that they have to pull from dev branch, if that's what we're doing.

converying doesnt make any diff sometimes we just push new commit and i cant review every single detail in every commit thats why if everyone create seperate branch for seperate stuff that wont cause any issues otherwise i have no issues on working only on dev , but its getting complicated day by day because codebase is filling up , cant review every minute step of every commit change

You still have to inform everyone that they've to pull from dev branch and not main (because most of them don't know dev is ahead of main). As far as different branches go, only I am working on something currently so I'll push to dev. If I or someone else starts working on something else, we'll create a different branch.

[devdaim6]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

You should merge. Other contributors also have to pull and they may face issues like large no. of conflicts if there are too many commits in a single PR.

BARADAR THATS WHAT I SAID THEY WILL PULL FROM DEV BRANCH , AND FROM NOW ON CREATE SEPERATE BRANCH FOR EACH THING like events page will have seperate branch clubs etc, just complete this and then will merge it , it wont cause issue dont worry

We're mostly working on one feature at a time, so the dev branch is enough, no need to create a separate branch for every thing. And convey to others that they have to pull from dev branch, if that's what we're doing.

converying doesnt make any diff sometimes we just push new commit and i cant review every single detail in every commit thats why if everyone create seperate branch for seperate stuff that wont cause any issues otherwise i have no issues on working only on dev , but its getting complicated day by day because codebase is filling up , cant review every minute step of every commit change

You still have to inform everyone that they've to pull from dev branch and not main (because most of them don't know dev is ahead of main). As far as different branches go, only I am working on something currently so I'll push to dev. If I or someone else starts working on something else, we'll create a different branch.

you have tawseef working as well , he did his part on registration part give , now he will create a basic login form : @TAWSEEFSHAMIM create a branch login , route /auth/login -> fields = username or email then password bas thats all and have a forgotpassword? link below that login button bas

[devdaim6]

Issues with the register page section will be fixed later.

fix that then will merge no big deal......no fun of merging many PRs , just complete each step and merge.......and if you have to implement other features better would be create a branch for that push that , and will merge that let it be until its complete , coz preview we have how and what it looks like https://department-of-it-git-dev-devdaims-projects.vercel.app/

You should merge. Other contributors also have to pull and they may face issues like large no. of conflicts if there are too many commits in a single PR.

BARADAR THATS WHAT I SAID THEY WILL PULL FROM DEV BRANCH , AND FROM NOW ON CREATE SEPERATE BRANCH FOR EACH THING like events page will have seperate branch clubs etc, just complete this and then will merge it , it wont cause issue dont worry

We're mostly working on one feature at a time, so the dev branch is enough, no need to create a separate branch for every thing. And convey to others that they have to pull from dev branch, if that's what we're doing.

converying doesnt make any diff sometimes we just push new commit and i cant review every single detail in every commit thats why if everyone create seperate branch for seperate stuff that wont cause any issues otherwise i have no issues on working only on dev , but its getting complicated day by day because codebase is filling up , cant review every minute step of every commit change

You still have to inform everyone that they've to pull from dev branch and not main (because most of them don't know dev is ahead of main). As far as different branches go, only I am working on something currently so I'll push to dev. If I or someone else starts working on something else, we'll create a different branch.

@Naveed-SNR cxe maklaav contact poore fix kaerith beyi kar registration khatam baki wechov patte ye pr karov merge taeth seet

[devdaim6]

NAVEED first thing , dont craete FormData , sending state sedhay as json string in body and second thing when form is submitted without data , errors are displayed but when user changes name email and message state respective errors should get removed on state change

[devdaim6]

[17:19:00.917] Running build in Washington, D.C., USA (East) – iad1 [17:19:01.029] Cloning github.com/devdaim6/department-of-it (Branch: dev, Commit: 15f5744) [17:19:01.350] Cloning completed: 320.99ms [17:19:03.709] Restored build cache [17:19:03.781] Running "vercel build" [17:19:04.250] Vercel CLI 35.1.0 [17:19:04.600] Running "install" command: npm install --legacy-peer-deps... [17:19:06.004] [17:19:06.004] up to date, audited 452 packages in 1s [17:19:06.004] [17:19:06.004] 144 packages are looking for funding [17:19:06.004] run npm fund for details [17:19:06.005] [17:19:06.005] found 0 vulnerabilities [17:19:06.016] Detected Next.js version: 14.2.5 [17:19:06.019] Detected package-lock.json generated by npm 7+ [17:19:06.020] Running "npm run build" [17:19:06.207] [17:19:06.207] > department-of-it@0.1.0 build [17:19:06.207] > next build [17:19:06.207] [17:19:06.882] ▲ Next.js 14.2.5 [17:19:06.883] [17:19:06.960] Creating an optimized production build ... [17:19:20.448] ✓ Compiled successfully [17:19:20.449] Linting and checking validity of types ... [17:19:22.076] [17:19:22.076] Failed to compile. [17:19:22.076] [17:19:22.076] ./app/register/clubs.jsx [17:19:22.076] 71:15 Error: Missing "key" prop for element in iterator react/jsx-key [17:19:22.076] [17:19:22.077] info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules [17:19:22.097] Error: Command "npm run build" exited with 1 [17:19:23.352]

@Naveed-SNR

[Naveed-SNR]

[17:19:00.917] Running build in Washington, D.C., USA (East) – iad1 [17:19:01.029] Cloning github.com/devdaim6/department-of-it (Branch: dev, Commit: 15f5744) [17:19:01.350] Cloning completed: 320.99ms [17:19:03.709] Restored build cache [17:19:03.781] Running "vercel build" [17:19:04.250] Vercel CLI 35.1.0 [17:19:04.600] Running "install" command: npm install --legacy-peer-deps... [17:19:06.004] [17:19:06.004] up to date, audited 452 packages in 1s [17:19:06.004] [17:19:06.004] 144 packages are looking for funding [17:19:06.004] run npm fund for details [17:19:06.005] [17:19:06.005] found 0 vulnerabilities [17:19:06.016] Detected Next.js version: 14.2.5 [17:19:06.019] Detected package-lock.json generated by npm 7+ [17:19:06.020] Running "npm run build" [17:19:06.207] [17:19:06.207] > department-of-it@0.1.0 build [17:19:06.207] > next build [17:19:06.207] [17:19:06.882] ▲ Next.js 14.2.5 [17:19:06.883] [17:19:06.960] Creating an optimized production build ... [17:19:20.448] ✓ Compiled successfully [17:19:20.449] Linting and checking validity of types ... [17:19:22.076] [17:19:22.076] Failed to compile. [17:19:22.076] [17:19:22.076] ./app/register/clubs.jsx [17:19:22.076] 71:15 Error: Missing "key" prop for element in iterator react/jsx-key [17:19:22.076] [17:19:22.077] info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules [17:19:22.097] Error: Command "npm run build" exited with 1 [17:19:23.352]

@Naveed-SNR

Wait yehi thk kr rha hu

[devdaim6]

@Naveed-SNR chuyna cxaer aasan gomut : fullname is not updating ath chuyni onchange chalaney

[devdaim6]

ath chune typey gasan

[Naveed-SNR]

ath chune typey gasan

Wni hy chalan os

[Naveed-SNR]

ath chune typey gasan

Cxe kyazi 4 lati same msg kermicx

[devdaim6]

ath chune typey gasan

Cxe kyazi 4 lati same msg kermicx

[Naveed-SNR]

ath chune typey gasan

Cxe kyazi 4 lati same msg kermicx

GitHub pareshan isko sync issues h

[devdaim6]

wani kar ye issue theek te naev pr kar pat kaerzi kaem events ya clubs kaerzi start banavun mai chu tami hissab tath bakend banavun

[devdaim6]

cluubs rozan static su thavav hardcoded

[devdaim6]

@Naveed-SNR