Frontend - Copy layout from teaser website, basic components

[SheepTester]

Info

set up groundwork for routes on the hackathon portal by copying the layout from the teaser website and creating some components that seem to be common across all routes

Changes

• a1f71d2 copied files from diamondhacks-teaser
• updated navbar for portal
  • the navbar is not sticky on the hackathon portal so the user can focus on the application
  • missing user name
• added Card, Heading, and Button components (which seem to be common across pages) so later PRs don't duplicate code or have to depend on another PR for a component
  • the card neutral grey color clashes with the cool blue grey of the background IMO, we probably want to find a different card color that's bluer

Type of Change

• Patch (non-breaking change/bugfix)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to not work as
  expected)
• Documentation (A change to a README/description)
• Continuous Integration/DevOps Change (Related to deployment steps, continuous integration
  workflows, linting, etc.)
• Other: (Fill In)

If you've selected Patch, Minor, or Major as your change type, make sure to bump the version before merging in package.json!

Testing

I have tested that my changes fully resolve the linked issue ...

• locally.
• on the testing API/testing database.
• with appropriate Postman routes. Screenshots are included below.

Checklist

• I have performed a self-review of my own code.
• I have followed the style guidelines of this project.
• I have appropriately edited the API version in the package.json file.
• My changes produce no new warnings.

Screenshots

Please include a screenshot of your Postman testing passing successfully.

no

mobile screenshots:

[alexzhang1618]

🫡

[alexzhang1618]

Hm, I wonder if we can also just have shrinking for Typography as well, I remember doing this for some other repo

https://github.com/acmucsd/outreach-website/tree/main/src/components/Typography

I think this is more of a consideration when we start making a component library so we can have this be standardized