# HackUTD Docs - [Introduction](https://docs.hackutd.co/index.md): The centralized home for HackUTD's open source documentation - [Overview](https://docs.hackutd.co/jury/overview.md): A modern hackathon judging platform - [Using Jury](https://docs.hackutd.co/jury/usage/introduction.md): Instructions on how to use Jury - [Deploying for your hackathon](https://docs.hackutd.co/jury/usage/deploy.md): Step-by-step instructions for how to deploy Jury for your Hackathon - [Physical judging setup](https://docs.hackutd.co/jury/usage/judging-setup.md): How to set up the physical judging space to use Jury - [Judging overview](https://docs.hackutd.co/jury/usage/overview.md): A quick walkthrough of the judging process through an admin and judge point of view. - [Using the admin interface](https://docs.hackutd.co/jury/usage/admin/introduction.md): Guide on how to use the admin (organizer) side of Jury - [Configuration and settings](https://docs.hackutd.co/jury/usage/admin/configuration.md): How to configure your Jury instance once set up - [Adding projects](https://docs.hackutd.co/jury/usage/admin/add-projects.md): How to import projects into Jury - [Adding judges](https://docs.hackutd.co/jury/usage/admin/add-judges.md): How to add judges to Jury - [Score aggregation](https://docs.hackutd.co/jury/usage/admin/scoring.md): How rankings are collected from judges and scores are aggregated. - [Judging tracks (challenges)](https://docs.hackutd.co/jury/usage/admin/tracks.md): How to judge tracks/challenges with Jury - [Judging with multiple groups](https://docs.hackutd.co/jury/usage/admin/groups.md): How to judge if you have multiple judging areas - [Admin dashboard](https://docs.hackutd.co/jury/usage/admin/dashboard.md): Using the admin dashboard - [Judge interface](https://docs.hackutd.co/jury/usage/judge.md): How to use Jury to judge and rank projects as a judge - [Project expo](https://docs.hackutd.co/jury/usage/expo.md): Details about the Project Expo page - [Tips and contingencies](https://docs.hackutd.co/jury/usage/tips.md): Tips for best ways to use Jury and possible Contingencies that can occur related to Jury - [Contributing](https://docs.hackutd.co/jury/contributing.md): How to set up the Jury development environment and contribute - [Technical details](https://docs.hackutd.co/jury/details/overview.md): The nitty-gritty details behind how Jury and its algorithm works! - [Jury core development principles](https://docs.hackutd.co/jury/details/principles.md): Jury core development principles - [Frontend](https://docs.hackutd.co/jury/details/frontend/introduction.md): The frontend. - [Routing (specifically React Routing)](https://docs.hackutd.co/jury/details/frontend/routing.md): How routing works on the frontend application. - [Components](https://docs.hackutd.co/jury/details/frontend/components.md): The component system and how to organize the frontend. - [Styling](https://docs.hackutd.co/jury/details/frontend/styling.md): How to style frontend components with Tailwind. - [Calling backend API](https://docs.hackutd.co/jury/details/frontend/api.md): How to call the backend API from the frontend - [Zustand store](https://docs.hackutd.co/jury/details/frontend/store.md): How to use the global store - [Backend](https://docs.hackutd.co/jury/details/backend/introduction.md): The backend. - [File structure](https://docs.hackutd.co/jury/details/backend/structure.md): How the backend code files are structured - [API](https://docs.hackutd.co/jury/details/backend/api.md): The private API that the frontend calls - [MongoDB database](https://docs.hackutd.co/jury/details/backend/database.md): How Jury interacts and stores data in MongoDB - [Logging](https://docs.hackutd.co/jury/details/backend/logging.md): How to log requests and changes to the global audit log - [Development notes](https://docs.hackutd.co/jury/details/development/introduction.md): Specifics on how to develop Jury and its deployment process. - [Github](https://docs.hackutd.co/jury/details/development/github.md): How the Github repo works and is managed - [Documentation](https://docs.hackutd.co/jury/details/development/docs.md): Docs about the docs - [Public API](https://docs.hackutd.co/jury/reference/public-api.md): The Jury public API - [Internal API](https://docs.hackutd.co/jury/reference/internal-api.md): Reference for every route in the Jury backend API - [Environmental variables](https://docs.hackutd.co/jury/reference/envs.md): The environmental variables you need to define when deploying locally - [Overview](https://docs.hackutd.co/harp/overview.md): One platform for the full hackathon lifecycle - [Why Harp?](https://docs.hackutd.co/harp/why-harp.md): What Harp replaces and the ideas behind it - [Hacker experience](https://docs.hackutd.co/harp/features/hackers.md): What participants see and do in the portal - [Applications & review](https://docs.hackutd.co/harp/features/applications.md): From configurable forms to bulk decisions - [Event-day operations](https://docs.hackutd.co/harp/features/event-day.md): Check-ins, meals, scans, and live updates at scale - [Content & public site](https://docs.hackutd.co/harp/features/public-content.md): Manage public content once, publish it everywhere - [Administration & reset](https://docs.hackutd.co/harp/features/administration.md): Roles, runtime settings, and the annual reset - [Architecture](https://docs.hackutd.co/harp/architecture.md): The three services and how they fit together - [Adoption guide](https://docs.hackutd.co/harp/adoption/guide.md): Run Harp for your own hackathon - [Forking & staying upstream](https://docs.hackutd.co/harp/adoption/forking.md): Keep your fork small so upstream merges stay clean - [The marketing site](https://docs.hackutd.co/harp/adoption/marketing-site.md): A redesign-every-year template on top of Harp's public API - [Local development](https://docs.hackutd.co/harp/deployment/local.md): Run the full Harp stack on your machine - [Production deployment](https://docs.hackutd.co/harp/deployment/production.md): Deploy Harp to Google Cloud, step by step - [Environment variables](https://docs.hackutd.co/harp/deployment/environment.md): Every variable the Go service reads - [Public content API](https://docs.hackutd.co/harp/reference/public-api.md): The /v1/public endpoints that power the marketing site - [Migrations for forks](https://docs.hackutd.co/harp/reference/migrations.md): Why migration numbering is load-bearing and how forks avoid breaking it - [Contributing](https://docs.hackutd.co/harp/contributing.md): Work on Harp itself This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.