jmu-football-tracker

Football Updates Tracker

A web application that tracks and displays football team updates, including commitments, transfers, visits, and offers. I’ve made mine for the James Madison University Football team, but it can be easily adjusted for whichever you’re a fan of. The application features a responsive design with dark/light theme support and administrative capabilities for managing player data.

Features

• Real-time Updates: Track latest player commitments, transfers, visits, and offers
• Filtering System: Filter updates by category (All, Transfer Portal, HS Commitment, Visit, Offer)
• Responsive Design: Optimized for both desktop and mobile devices
• Theme Support: Toggle between light and dark themes
• Admin Panel: Secure admin interface for managing player data
• Player Cards: Detailed player information including:
  • Player image and basic information
  • Physical attributes (height, weight)
  • Recruit and college grades
  • Previous and destination schools
  • Social media links (X/Twitter)
  • Custom descriptions

Technology Stack

• Frontend:
  • HTML5
  • CSS3 (with responsive design)
  • JavaScript (Vanilla)
• Backend:
  • Node.js
  • Express.js
  • MongoDB (with Mongoose)
• Deployment:
  • Heroku
  • MongoDB Atlas

Prerequisites

• Node.js (v12 or higher)
• MongoDB
• npm or yarn package manager

Installation

1. Clone the repository:

   git clone [repository-url]
   cd jmu-football-tracker
   

2. Install dependencies:

   npm install
   

3. Create a .env file in the root directory with the following variables:

   MONGODB_URI=your_mongodb_connection_string
   ADMIN_TOKEN=your_admin_password
   PORT=3000
   

4. Start the development server:

   npm start
   

5. Access the application at http://localhost:3000

Environment Variables

This project uses environment variables for configuration. Create a .env file in the root directory with the following variables:

MONGODB_URI=your_mongodb_connection_string
ADMIN_TOKEN=your_admin_password
PORT=3000

Important notes about environment variables:

• Never commit the .env file to version control
• Make sure to set up these variables in your deployment environment

Project Structure

jmu-football-tracker/
├── node_modules/      # Dependencies directory
├── .env              # Environment variables (not in version control)
├── .gitattributes    # Git attributes configuration
├── .gitignore        # Git ignore configuration
├── index.html        # Main HTML file
├── package-lock.json # Dependency lock file
├── package.json      # Project configuration and dependencies
├── server.js         # Express server configuration
└── styles.css        # Application styles

API Endpoints

• GET /api/players: Fetch all players
• POST /api/players: Add a new player (requires admin authentication)
• DELETE /api/players/:id: Delete a player (requires admin authentication)

Security

• Environment variables used for sensitive data
• .env file excluded from version control
• Admin authentication required for data modification
• CORS enabled for API security
• No sensitive information exposed in frontend code

Deployment

Heroku Deployment

1. Create a new Heroku application
2. Connect your GitHub repository
3. Configure environment variables in Heroku:
   • Go to Settings → Config Vars
   • Add your MONGODB_URI and ADMIN_TOKEN
4. Deploy your application

MongoDB Atlas Setup

1. Create a MongoDB Atlas account
2. Set up a new cluster
3. Create a database user
4. Configure network access
5. Get your connection string and add it to your environment variables

Contributing

1. Fork the repository
2. Create your feature branch (git checkout -b feature/AmazingFeature)
3. Commit your changes (git commit -m 'Add some AmazingFeature')
4. Push to the branch (git push origin feature/AmazingFeature)
5. Open a Pull Request

License

This project is licensed under the ISC License.

Acknowledgments

• Created by Owen Perry
• Built for James Madison University football community
• Not officially affiliated with JMU Athletics

Disclaimer

This site is not affiliated with, endorsed by, or connected to James Madison University or its Athletics Department. All information provided is publicly available and for informational purposes only.