Skip to content

#3 ‐ Requirements

Jump to bottom
TrissyG edited this page Jun 28, 2024 · 1 revision

Motivation

The Web Development & Consulting Club would be remiss to exist without its own website...

This website's purpose is to publicly showcase WDCC's unique offerings and its value to home universities, industry sponsors, and the community at large.

Prior to the initialisation of this repository, the last update to the WDCC Website occurred in 2021. This iteration is built with a unique tech stack and provides administrative ease of maintenance through an integrated Strapi Content Management System.

Related Applications

University Tech Clubs/Societies

Australian University Societies

NZ University Societies

Requirements

Requirements have been converted to GitHub Issues for task-tracking. They have been ordered/prioritized according to the MoSCoW prioritisation method.

Unsorted

  • navbar: the website has a navbar that contains all main pages and links
  • footer: the website displays a call-to-action and organisation's details at the end of the scroll
  • [home] hero: home page has an attention-grabbing hero with a call to action
  • [home] sponsors: home page displays our sponsors of each level
  • [home] about-us: home page tells visitors about WDCC's value proposition
  • [home] events: home page displays a summary of our upcoming events
  • [home] projects: home page displays a featured project section
  • [about] statement: about page has an appropriate mission statement
  • [about] team: about page displays the current executive team of WDCC
  • [events] summary: events page contains a profile of the events we run
  • [events] event-card: each event has its key details shown and a link to further info
  • [events] event-list: events are shown in a filterable list
  • [event-details] summary: the page has a visible full description of the event
  • [event-details] assets: details page contains additional resources about the event
  • [projects] project-card: each project has its key details shown and a link to further info
  • [projects] project-list: current projects are shown in a list
  • [projects-details] background: summary of an individual project is displayed
  • [projects-details] team: the team most recently developing the individual project is shown
  • [projects-details] requirements: the main requirements from the client are shown on the page
  • [projects-details] testimony: a team statement from the developers and/or the client is included
  • [projects-details] gallery: an image gallery for the app and its developers/clients is rendered on the page
  • [blog] article-card: each article has its key details shown and a link to further info
  • [blog] article-list: posted articles are shown in a list
  • [blog] article-search: posted articles can be browsed through

MVP (must-have)

  • website: the app is a functional website
  • deployment: a stable production version of the website is deployed and publicly accessible

MVP+ (should-have)

  • X: [description]

MLP (could-have)

  • Y: [description]

Stretch (would-have)

  • Z: [description]
Clone this wiki locally