hackmerced/hackmerced

HackMerced's Official Hub for all Hackathon Iterations and Mini Events

Initial page

hackmerced's Issues

Status Component

Acquire status of Participant or Volunteer Applicant

Sponsor List

bug/teampics

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. pull master repo
2. install and run
3. See error

Expected behavior
no error, landing page.

Screenshots
see above

Desktop (please complete the following information):
NA

Smartphone (please complete the following information):
NA
Additional context
misspelled branch name OOPS. LOL

Sign-Up/Apply

Forms for Hackers and Volunteers

npm run start on master branch issue

Module not found: Can't resolve 'react-router-dom' in '/Users/adarian/HackMercedf18/client/src'

Member Components

for HackMerced Team Members with the following user types:

• Admin (mainly for approving and denying applicants, will be for directors)
• General (everyone else on the team)

Components:
Team member: Parent
Admin: Child
General: Child

Build Initial Application Collections

Create the initial documents for the applications:

• Applicants
• Volunteers
• Sponsors
• Judges
• Teams

Explore other requirements / needs for collections, ex:
Do we offer travel reimbursement? If yes, we might need a collection for the people registered to that.

About Us

Title Screen

The scss is not loading properly. Also double check the console when running the app to make sure there are not errors

Volunteer Components

Volunteer Info and Acquires Status of Application from status component

compile error

User Dashboard

• Construct user dashboard and build it to handle different types of users. Aka it should only show info belonging to that user group.

Team Page

Initial Style Design

Complete an initial style guide that falls under the theme of Outdoors for the HackMerced website.

• Cover page

• Application pages

These are the only ones to focus on right now

Contact Us

Timeline

Asana | Build out GitBook documentation structure

Description of Task: https://hackmerced.gitbook.io/hackmerced/ was just created with out admin account and needs to have an initial structure to it so we can move forward and update it as we develop our apps

HackMerced Git Book Structure
Introduction
Getting Started
How to prepare for a hackathon
How to contribute to our projects
FAQ
Who We Are
Contributing
Hackathons
Mini Events
API
Tomoe
Myriagon
Admit

FAQs

Initialise Node Server

Setup the NodeJS server with ExpressJS

• Create the server
• Add Express to it
• Test the server

Typeform data retrieval

Get the data from the typeform, either by connecting with a webhook or with the google forms

UI Page for Sponsor Us on Hub

• Sponsors can go to this page and have a form to fill in name, company, email, and message if they want to sponsor us and like our hackathon

• name

• company

• email

• message

if possible, put a character count on the message

Connect Server - Database

Connect the Node server to the cloud database

• Setup the connection
• Run initial tests with dummy data
• Add data from the server

Checkin

• Automated connection for UC Merced students to register and sign-in

• Schema for HackMerced Team members

• endpoints for get requests to put data on timeline programmtically

• Setup Admin control endpoints. So that Directors can update the collections without having to manually open them.

Navigation Bar

Application Form

Title Screen

User Components

Process specific User Type

• HackMerced Members
  • Admins(Directors): can approve or deny applicants
  • General
• Judges
• Sponsors
• Volunteers
• Hackers

Asana | Asana | Asana | Asana | make sketch of hub

Description of Task: Description of Task: Description of Task: Description of Task:

User Login

Email and Password

Asana | Asana | Asana | make sketch of hub

Description of Task: Description of Task: Description of Task:

Asana | Asana | make sketch of hub

Description of Task: Description of Task:

Refactor Components

Pass values through props

Move around the endpoints

Refactoring of the server structure to have the placeholder, official and live site on the server

• Move the placeholder website from heroku to the server
• Place all three websites under folder (sub-domains) in a /site/ folder on the server
• Have the default route '/' redirects to the placeholder website

Get User Info

Checking service for the validation at door

• Check if the e-mail is in the DB
• Check hacker status
• Retrieve shirt size info, role and registration status for said hacker

Basically making a small web page that can do that. You enter the name or email of the hacker (or scan their QR code if we do one) and it will give you back information so you can give them their starter pack and let them in.

Background

Use FREE Vector Art :)

Asana | Asana | Asana | Asana | Asana | make sketch of hub

Description of Task: Description of Task: Description of Task: Description of Task: Description of Task:

Asana | make sketch of hub

Description of Task:

Participant Components

Participant Info and Acquires Status of Application from status component

Judges Components

Judge Info

Issue test

Dashboard Component

Dashboard for User Info