Making the frontend responsive for all screen sizes

[PorePranav]

Description:

We need to ensure that the CampusUnify frontend is fully responsive and adjusts well across various devices like mobile phones, tablets, and desktops. This can be done in phases, starting with critical pages and components. The styling should be implemented using Tailwind CSS, focusing on making all layouts flexible and user-friendly on smaller screens.

Tasks:

1. Analyze existing components and layouts for responsiveness issues.
2. Refactor CSS using Tailwind's responsive utilities.
3. Test each phase across various screen sizes (mobile, tablet, and desktop).
4. Ensure no functionality is compromised after implementing responsive design.

Phase Breakdown:

Distribute the work over several phases and PRs so that it would become easy to test and merge the final code.

[PorePranav]

I am closing issues #2 and #3, combining them both into this one

[shreyansh1410]

Assign me this, I'll work on it

[PorePranav]

Assigning to you. As this might be a big refactor, make sure that you open PRs in phases so that it becomes a bit easy for me to review and merge code. Good luck!

[shreyansh1410]

Hi! @PorePranav , when setting it up locally, server is throwing error saying

Uncaught Exception, Shutting Down!
Error: `key_id` is mandatory

What am I supposed to do?

[PorePranav]

Hi! @PorePranav , I'm unable to signin/signup locally, it is giving server error saying

Uncaught Exception, Shutting Down!
Error: `key_id` is mandatory

What am I supposed to do?

Just set up any random key for RAZORPAY_ID_KEY and related fields in config.env file for the server, that would fix it. Thanks!

[shreyansh1410]

The sever has started but now it is throwing this error when I'm trying to signup:

Is this still related to config.env?

[shreyansh1410]

BTW #18 has been solved, should i create a separate pr for it?

[PorePranav]

The sever has started but now it is throwing this error when I'm trying to signup:

Is this still related to config.env?

Make sure that you are setting up VITE_APP_BACKEND_URL approriately in .env for client, the variable should point to the server url, which is http://localhost:3000/api/v1 by default

[PorePranav]

BTW #18 has been solved, should i create a separate pr for it?

No need to create a separate one, you can include it all in one PR

[shreyansh1410]

Thanks

[shreyansh1410]

And what exactly do you mean by opening PR in phases? Sorry if this sounds dumb

[PorePranav]

And what exactly do you mean by opening PR in phases? Sorry if this sounds dumb

No need to apologize, we all learn at some point! I just meant that to commit changes in a phased manner and not to push all changes in a single commit. It just helps me with code review and testing.

[shreyansh1410]

So just make multiple commits instead of one?

[PorePranav]

So just make multiple commits instead of one?

Yes!

[shreyansh1410]

I'm not able to see any events in the events part?

[PorePranav]

I'm not able to see any events in the events part?

Could you please elaborate your issue, please provide me with additional information so that I can assist you better.

[shreyansh1410]

when i click on events, in my local environment, I am not able to see any current events but when I use your deployed link, I am able to see a lot of events

[PorePranav]

when i click on events, in my local environment, I am not able to see any current events but when I use your deployed link, I am able to see a lot of events

You need to create one club account to add events, then only you would be able to list the events

[Anurag-singh-thakur]

@PorePranav can i work for the frontend part for the responsiveness of the project.

[shreyansh1410]

@Anurag-singh-thakur I have already raised the PR, search for another issue