self explanatory.

• Add a transition time to the event sections.
• Make the content of the event sections responsive so that it wraps around a div and displays properly on smaller screens.
• Expand the acronym EIC to its full name.

ISSUE

self explanatory

when user is on route other than '/', clicking on about us NavLink takes him to the home page (hero section). Ideally it should take him to about section of the home page.

The current implementation of the photo gallery cards leads to stretched or distorted images when hovering over them. To avoid this, I propose the following steps:

• Create square versions of each photo without changing its original aspect ratio. Example
• Set the width and height of the image on the cards to match the dimensions in cloudinary.com.
• Adjust all other sizes as needed to match the design (not necessarily the size) in Figma.

The social media buttons on the core team cards are not centered in mobile view, and the content on the cards is overflowing and not properly wrapped inside the div. Refer to the attached screenshot for details.

If a user hasn't provided at least one social media profile link in dashboard and tries to create a blog redirect him to /editprofile. This is required, as blog reader must have atleast one way of contacting the author.

To improve the UI layout, I propose the following changes:

• Create a grid with three columns to align the gallery.
• Decrease the width of the gallery and tab buttons and set it to 80%.
• Set margin auto to the gallery and tab buttons to center them on the page.

To fix this issue, I suggest updating the Testimonial component to add a unique "key" prop for each child element in a list.

react_devtools_backend.js:2655 Warning: Each child in a list should have a unique key prop. Check the render method of Testimonial. See https://reactjs.org/link/warning-keys for more information. at Testimonial (http://localhost:3000/static/js/bundle.js:3945:69) at Home (http://localhost:3000/static/js/bundle.js:10975:51) at RenderedRoute (http://localhost:3000/static/js/bundle.js:309123:5) at Routes (http://localhost:3000/static/js/bundle.js:309545:5) at Scrolling (http://localhost:3000/static/js/bundle.js:10007:77) at Router (http://localhost:3000/static/js/bundle.js:309483:15) at BrowserRouter (http://localhost:3000/static/js/bundle.js:307841:5) at App

Give user the freedom to delete account as well as delete provisional blog (blog that has not been published yet).

explaining a little bit more here. Forgot password button should ideally be disabled after the user clicks on login button. After failed login it should return to its original state. Currently, forgot pwd button does get the not-allowed cursor but it is not getting disabled. So, if a user accidentally clicks the forgot pwd button after initiating the login process, it will lead him to forgot pwd page, potentially leading to corrupt login.

self explanatory

blog should be centered or spaced evenly instead of space-between.

Currently, any user can provide anyone's email to subscribe to the newsletter, which could potentially lead to spam. So, brainstorm and add email verification method

ref: inngest/vite-to-nextjs#1

Use conditional rendering to show "Blog" when no of blog is 1 and "Blogs" when no. of blog>1

As mentioned in the title, no skeletons are displayed during data fetching. Either it shows loading... or loading state is not handled somewhere. Take reference from linkedin website on how to properly handle the loading state and display skeletons giving user an idea of data being fetched from the server.

Add a separate protected route '/logout' that will serve as a confirmation step for users who wish to sign out.

It should have following features:

• Title: Sign out?
• A button with the label Sign out to take confirmation from the user.
• It should be protected route; i.e if user is not logged in and attempts to visit /logout redirect them to home route

Edit profile form should have populated data by default (except password field) so user can do the required changes. Say a user have to edit the About field, he will need to retype the whole about again. If data is populated then, he can do the changes instantly instead of typing the whole stuff again.

When using the Events_red component, we're getting two warnings in the console that need to be fixed.

The first warning says "Each child in a list should have a unique 'key' prop.". We need to ensure that each child element in the Events_red component has a unique key prop.

The second warning says "Invalid DOM property class. Did you mean className?". We need to update the class property to className in the Events_red component.

like this one.

As stated above. upon failed signup, login attempt all input gets cleared leading to bad user experience.

Use react-toastify to handle error notifications more properly.

if a user submits link like this way without https:// it lead to 404 page:

When a user attempts to visit /blogs or /blog or /tags or /tag, redirect them to Blog-section of /resources . Blog-section should come in view port.

Currently contact Us & newsletter have very typical design. Consider improving the same.

big name of the user in dashboard (mobile view) potentially breaks the default layout of edit profile and sign out button

Display 404 page or handle error (no user found) with react-toastify and redirect to resources page after the interval of 5seconds.

also correct the alignment issue in the mobile view