Migration of HeroUI to shadcn/ui

[No767]

Summary

NextUI/HeroUI are known as traditional component libraries, where you install, import, and use them directly. This although is a good solution, spawns a ton of UI component libraries that are tailored to different styles, e.g. Material UI (MUI), Chakra UI, Mantine, and others. They all have a drawback: there is a lack of finite control over styles. This is best summarized by shadcn/ui themselves:

This approach works well until you need to customize a component to fit your design system or require one that isn’t included in the library. Often, you end up wrapping library components, writing workarounds to override styles, or mixing components from different libraries with incompatible APIs.

Point is, by sticking with HeroUI, we end up wrapping styles around components, and attempt to force them to "integrate" with our design. shadcn/ui takes a completely different approach. It literally is the framework to build your own component library. By sticking to shadcn/ui, we can deeply integrate our designs into the components directly, and manipulate our designs to perfectly couple natively with TailwindCSS instead of wrapping everything around the component library. And yes, by doing this, we only actually add and import the components we really need, not 125 of them that we end up only using 10 for the whole entire website.

In addition, this PR implements a completely new home page that utilizes mesh gradients and a simpler design than geometric shapes. Inspirations has been taken from ACM at CSUF, ACM at UCSD, and ACM at UCLA for layout and home pages.

Important

This PR does not complete the front page. It only provides a fully working navbar, and some code for the body, which will be finished in different PRs

Caution

This PR literally breaks every single other branch and PR, as it starts from the ground up. Be aware that you will need to adapt to these new technologies and frameworks

Types of changes

What types of changes does your code introduce to the UC Merced's ACM Chapter Website?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (Updates to README.md, the documentation, etc)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply

• If code changes were made then they have been tested.
• All workflows pass with my new changes
• This PR does not address a duplicate issue or PR

[sonarqubecloud]

Quality Gate passed

Issues
8 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud