pec-css / website Goto Github PK

• you know the drill : figma -> code

• user Image tag
• vercel cdn
• ssr for images

• ofc u know what to do

• all details of any user based on email/sid

Stitch the history and events API on the given page (ofc it is also paginated)

Do this after Create event fully done and deployed

Login page as discussed and described in design doc.

Reference doc

• One of the biggest components
• full blown calendar
• fetch from server

Maybe : Include flow for registeration into events

• https://www.pecacm.com/dashboard/events
• Similar components as https://www.pecacm.com/events
• Just some extra options like, "create event" button on top right
• and event details page when clicked on any event

Fix the leaderboard on homepage and leaderboard page (after logging in)

• consume the leaderboard api
• display users in a list
• show only those users who have xp > 0

When api call fails, it crashes the website.

On 400 BAD Request, it is fine, but on other responses, it crashes. It should be fixed.

• this is a bigger task
• Create a page (component) to accommodate all the branches, as shown in figma
• Static data from webiste
• Events and highlights from API

• Navbar
• Footer
• Landing page acc to Figma

Fetch data from google sheet

• branch wise filter
• pick top 3

Socials will update the google sheet using google forms

Protect the user specific routes and also redirect register and login routes when already logged in

• Current Scrollbar is the default scrollbar
  • 
• Update it. Make the corner smooth like shown below:
  • 

• make page with the team members
• core members are well

Do something please. Similar to PEC-CSS/acm-website-backend#67 but this one for frontend docker compose containers

Inside the dashboard events page, when user click on any event. A page containing all details of event should open up.

If that event is already "ended" (a flag), the show the details.

Otherwise, display a form with the end event api details and call a POST API.

Bring it to number 1 on google searches pls, following has been done

• google verification code added on domain TXT field
• meta data (best we could do)
• all assets in public folder
• sitemap.xml uploaded on domain side
• robots.txt file

Fix it by saving cards once in redux.

• when clicked on any event, a pop up showing its info should be shown

When page is in changing state, the loader appears on top as it should, but it should not shift the layout. Rather it should be on top on content.

Change the authentication flow from Cookies to NextAuth

Make a dialog pop up to create new events

• this should be visible to users who have role >= EB
• Location of this pop up will the events page inside the dashboard
• Button at top right of page to open this dialog
• API to be consumed api

https://www.figma.com/file/3gIFJPocYEFVCh24fPuZ99/ACM?type=design&node-id=0-1&mode=design&t=DHHDWxWaL6UmANak-0

• Opened through link sent in email
• Page will make api call to the verify endpoint
• Show success or failure based on response

register page as discussed and described in design document.

• Find all images in assets. Convert it into png using any editor (online or offline)
• Fix the image extension in code (wherever it is used).
• Mainly problem is in constants/team.ts where photos of core members are added.
• Do not change the name of file, change extensions only. Keep both old jpg as well the new png in the assets.

• login
• register
• verify

Maintain User context

Attach these three apis to backend

• hexagonal divs
• animation if possible

• generic card for Trending
• data will come from backend
• dynamic props

• page with all branches listed
• clicking on one take to the specific branch page

• make backend connection using docker compose
• link backend, db all in one file
• expose and consume :8080
• DockerHub?

• add logos
• descriptions (meta)
• social links
• some seo practices

Make leaderboard page, with proper pagination linked with backend

• assets
• colors
• theme
• content

Relate to branch

Will hv to decide how we need to do this, like hv a button or something else, and where exactly to keep the button

• in every page inside dashboard, there is hydration issue coming on refresh :weird: