UCMACM Website v2

[No767]

Introduction

For the last semester, the project has been constantly held back, delayed, and shown many issues due to an aging codebase. Essentially no work was able to be done due to years of technical debt, near zero documentation, broken code, and focusing on the wrong target. This issue aims to bring a comprehensive roadmap of what's expected.

Please note that this is not a complete list, and may change at any time.

Contributing

The first task is to join the UCMACM discord server, and ask me or one of the project leads. Discussions take place under #acm-website, and will be used to help aid in the direction or guidance of the project. In addition, you must also read the onboarding guide if you are starting off for the first time

Once you have discussed your contribution, open a PR. The pull request should target react-rewrite, not any other branches.

Roadmap

Below is a roadmap detailing the parts of the eventual website:

Frontend

• New Figma design based on NextUI
• Rebuild front landing page (Implement components and front page #259)
  • Uses the NextUI library
  • Website Components
    • Navbar
    • Footer
    • Front landing header
    • Better about us
    • SIGs introduction
• Rebuild other pages
  • SIGs (Build SIGs Page #279)
  • Events
• Design web dashboard
• Login page for dashboard
• Project showcase ([feature] Project Showcase #227)

Backend

• Create a utils package to use within the frontend
• Move away from Firebase and use a different service instead for backend storage (Will be Supabase)
• Consider hosting options (Vercel and Supabase)
• Deploy development dbs, staging, internal POP dbs, production db
• Look into cost of hosting Supabase / Infra usage costs