The Q is a pickleball queue application developed exclusively for players in the Phoenix area. Built with SvelteKit, Supabase, and TailwindCSS, The Q offers an intuitive interface to organize and manage your games. Currently, the project is in its beta phase, and while most features are fully functional, users may experience a few bugs.
We're working hard to bring you the following features. They are currently a work in progress:
-
Pickleball Queue Management: We're developing an intuitive system to manage your pickleball queue with ease. Quick actions such as "Start Game" and "Quick Join" are in the works to allow for efficient game management.
-
Reporting Mechanism: To maintain a healthy and fair community, we're setting up a reporting action feature. This feature will allow users to report if other games are not taking the court in a timely manner, or if certain players are abusing the system. Offending parties can then be removed to ensure a positive experience for all users.
-
About Page: An "About" page is being prepared to provide users with more information about our application and the team behind it.
-
FAQ Page: We're putting together an FAQ section to answer common questions and help users get the most out of our application.
-
Contact Page: We're designing a "Contact" page to make it easier for users to get in touch with us for support or feedback.
- Clone the repository:
git clone https://github.com/jjbowman2/the-q.git - Change into the project directory:
cd the-q - Install the dependencies:
pnpm install - Start the server:
pnpm run dev
We welcome any contributions that can help us improve The Q! Please feel free to fork the repository and create a pull request with your changes.
Before submitting your changes, ensure to test them thoroughly. Changes that break existing functionality or introduce new bugs will not be accepted.
If you encounter any bugs or issues while using The Q, please open an issue on GitHub. When reporting a bug, try to include as much detail as possible, such as the actions you were taking when the bug occurred, any error messages, and the device and browser you were using.