Giter VIP home page Giter VIP logo

sportrakker's Introduction

Sportrakker

Sportrakker is a prep sports suite that adds cross sport statistical tracking for highschool students, as well as serving as a meet hosting software providing realtime live update of prep sporting events.

Goals of Sportrakker

  1. Create an simple but intuitive way to host prep sporting events
  2. Offer live resutls of prep sporting events
  3. Serve as the one stop shop for all data related to High School prep sports
  4. Use big data to find stadout athleates that might have gone unknoticed by college recruiters

Contribution

  1. Create a new branch off of develop. If you are working on an issue please title the branch issue-<issue#>-<issue title> ie issue-1-react please keep it all in lower case and do not include the '<>' signs.
  2. Commit to your branch until the task is compleated
  3. Submit pull request from develop. All pull requests will be handeled by the Admins.

Workflow

  1. Create a new issue for what you will be working on.
  2. Create a new branch off of develop for your work.
  3. Commit frequently to your branch with descriptive comments. Try to keep each commit to one task.
  4. Once the issue is resolved create a pull request from develop.
  5. After that a admin must give their approval before they will accept the pull and close the issue.

Issue Trackking

ALL new enchancements and bugs WILL be recorded in the Issues section of this repository. Work on this repo should not begin until an issue report is filled out for the task at hand.

  1. Go to the Issues tab and click the "New Issue" button located on the right.
  2. Fill out the title in Title case
  3. Add a detailed description of the issue
  4. Add the appropriate Lables and Milestones to the issue
  5. Assign the issue to the correct user
  6. Submit the issue

Building the App

  1. Install dependencies with npm install
  2. Build the app using ng build
  3. Test the app using ng serve
  4. Go to localhost:4200 to find the running local app running

License

All Rights Reserved
Copyright Šī¸ 2016 Andrew Casner and Jason Cyrus

sportrakker's People

Contributors

andrew-casner avatar

Stargazers

Carl Cortright avatar avatar Dawson Botsford avatar

Watchers

Jason Cyrus avatar James Cloos avatar

sportrakker's Issues

Results Schema

Needed

  1. results.js in ./server/app/models. This will be the schema file defining the json element
  2. results.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Add node_modules to the .gitignore File

The folder containing all of the node packets should be managed by npm at the time of cloning a repo. Cross OS dev can cause huge problems if each module is stored each time. It also cuts down on the size of the project allowing for fasted development.

Add Wiki

The projects Wiki needs to be created and filled out to allow for an easy and quick way to understand each class and how everything fits togeather

Athlete Schema

Needed

  1. athlete.js in ./server/app/models. This will be the schema file defining the json element
  2. athlete.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Grunt Build

Add grunt to build and deploy the project. Grunt or similar software needs to be implemented to build the source code, minify the code, compress images, and handle any other necessary actions to build the project. In the end we should be able to run grunt build and the project should be compiled, built, and deployed.

React

React needs to be included to this project. React is the chosen for its many features for web apps. The combination of its power and ability to scale makes it a perfect fit for this project. The file structure needs to be laid out in a coherent organized way, separating the front end and back end. The .jsx files will need to be compiled with Webpack. For this issue all boilerplate code needs to be created, allowing us to quickly add new react components and integrate them into our front end without any extra work after the component is written. This issue is a high priority and is blocking all front end development.

Trello Integration

Integration with Trello is necessary to provide an organized workflow. GitHub and Trello already have a standard to do this. See this.

Position Schema

Needed

  1. position.js in ./server/app/models. This will be the schema file defining the json element
  2. position.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Staff Schema

Needed

  1. staff.js in ./server/app/models. This will be the schema file defining the json element
  2. staff.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Game Schema

Needed

  1. game.js in ./server/app/models. This will be the schema file defining the json element
  2. game.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Organization Schema

Needed

  1. organization.js in ./server/app/models. This will be the schema file defining the json element
  2. organization.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Angular cli build

We need to implement an angular cli build to start front end of development

Team Schema

Needed

  1. team.js in ./server/app/models. This will be the schema file defining the json element
  2. team.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Rules Schema

Needed

  1. rules.js in ./server/app/models. This will be the schema file defining the json element
  2. rules.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Schema Todos

This is the parent issue for all Schemas that need to be created.
Once an issue is closed please Strikethrought the issue number

Organizational Hierarchy

Event Schema

Needed

  1. event.js in ./server/app/models. This will be the schema file defining the json element
  2. event.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Delete Master Branch

Master branch needs to be removed and default needs to be switched to develop.

Sport Schema

Needed

  1. sport.js in ./server/app/models. This will be the schema file defining the json element
  2. sport.js in ./server/app/routes. This will define all of the routes to get and edit data
  3. The routes need to be added to './server/server.js`
  4. Proper documentation needs to be added to the wiki.
    • Listing and describing all of the api routes
    • Listing and describing all of the objects in the schema
    • Listing the overall design and structure of the schema and how it fits into the scope of the project overall.
    • Any other data the developed believes is necessary such as code gimmicks or bugs.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤ī¸ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.