Skip to content

Home

Jump to bottom
David Zhu edited this page Apr 3, 2025 · 15 revisions

Welcome to the AUCC wiki! Here, you'll find all the necessary information to get you acquainted with the AUCC project, repository, workflows, and more.

an image of a very endearing fella
The AUCC Project Mascot John "Yoyo" Canoe

New to the project? Get started with the Onboarding Guide

Goals and Scope

Project Overview

This project aims to develop and deploy a dynamic content website for the Auckland University Canoe Club using Next.js and Payload CMS. The focus is on rehauling their existing website, and creating a beautiful new website with effectively structured content, implementing key functional and non-functional requirements over multiple milestones.

Milestone 1 – SEM1 Weeks 4-10 (6 weeks)

  • Scaffold core website functionality:
    • Home
    • Signup
    • Trip Events
    • Trip Reports
    • Gear Hire
  • Set up collections and resources in Payload CMS.
  • Develop initial website designs.
  • Implement web pages with necessary integrations.

Milestone 2 – Intersemester Break - Week 4 (8 weeks)

  • Automate JotForm and Google Workspace signups.
  • Automate membership expiry handling.
  • Address additional frontend requirements as needed:
    • Merchandise
    • Gallery
    • Contact Us
    • Resources and Links

Milestone 3 – SEM2 Weeks 4-10 (6 weeks)

  • Implement non-functional requirements.
  • Develop a live swim tracker feature.

Tech Stack

The AUCC website will mainly be built upon the following technologies:

  • Next.js, a full stack web development framework
  • TailwindCSS, an utility first CSS framework
  • PayloadCMS, headless CMS that streamlines content management

Team Roles

Project Manager

  • Is responsible for overseeing the project for the duration of the year. They communicate the team and clients, create and manage the project alongside the tech lead, and motivate the team.

Tech Lead

  • Responsible for technical leadership, will guide you and your team in making technical decisions, such as choosing the right technology stack, architecture, and design patterns. Furthermore, they are responsible for code reviews and providing feedback to developers, particularly at starting stages.

Developer

  • In charge of pretty much all of the actual tasks and work output for the final solution. You will be working on implementing features, fixing bugs, writing unit tests, performing code reviews, and other relevant work in making a software product.

Designer

  • Responsible for designing the actual website; making the end product look appealing to audiences and integrating the branding requirements of the client.

Clone this wiki locally