Skip to content

hratx-blue-ocean/pogchamp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

About Expwnent

Expwnent is a web application for tournament organizers and players to meet and engage in epic battle with the game of their choice. Click HERE to make your first tournament!

This application was built with pride by a team of eight full stack software engineers from the Hack Reactor Austin campus, 51st Cohort (HRATX51).

expwnent.com

Bracket Tournament Demo

   

Swiss Tournament Demo

   

Dev Team

  • Leslie Crunkilton: Architecture Lead -
  • Alec Brock: Design Lead -
  • Grant Harris: Product Lead - Implemented agile workflow via daily stand-ups, Trello ticketing, and Git workflow. Managed overall project and client relations with acceptance testing and production milestone meetings. Created player and organizer dashboards using React, Material UI, and React Router. Implemented tournament logic for swiss-style tournaments (win conditions, tie-break, player cycling).
  • Rose Bram:
  • Emmanuel Garcia: Bracket Developer & Routing API -
  • Daniel Leal:
  • Brandon Bates:
  • Emily White: Prize distribution, player and organizer dashboard, bracket forms.

Client Deliverables

  • Add user stories

Tech Stack

Expwnent was built primarily with ReactJS on the front end and Node/Express/MongoDB on the backend. Other key technologies used are listed below:

Technologies

Frontend React React Router Material UI Formik
Backend Node Express MongoDB
Dev Tools Webpack Babel
APIs Challonge
Authentication Node Crypto

Development

  1. npm install
  2. npm run start
  3. npm run dev
  4. Open http://localhost:3000/ to view app

Workflow

This project was managed using the git workflow:

The team maintains one development branch that is fed by feature branches. Ready to deploy features undergo the following agile process:

  1. Feature branch is rebased to consolidate commit history and ensure only working code is pushed to the dev branch.
  2. Feature branch is pushed to project repo.
  3. A pull request is made with another dev tagged for review.
  4. Developer branch is merged in line with agile methodology.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published