You do not need to read or use every resource below. Start by:

1. Choosing one Chicago community or user.
2. Identifying one clear problem or opportunity.
3. Selecting only the tools and data needed for your solution.
4. Creating and testing one core user experience.
5. Preparing your demonstration and Devpost submission.

Mentors and workshops will be available during the Summit to help teams scope, build, troubleshoot, and present their projects.

• Chicago Quantum Exchange — Explore Chicago and the Midwest’s growing quantum ecosystem.
• What Is Quantum Technology—and Why Does It Matter? — A beginner-friendly explanation of quantum technology and its potential uses.
• CQE Education and Training — Explore educational programs, internships, training opportunities, and workforce resources.
• Q-READY — Free career-development resources for undergraduate students, graduate students, and early-career researchers.
• CQE Talent Portal — Search for quantum and quantum-adjacent jobs and internships.
• National Quantum Initiative Resources — Educational materials and introductory quantum resources from the federal National Quantum Initiative.
• NIST: What Is Post-Quantum Cryptography? — A plain-language explanation of how quantum computing may affect cybersecurity.

Remember: Your project does not need to use quantum computing. These resources are here to help you understand the technology, its possible effects, and the opportunities developing around it.

• City of Chicago Data Portal — Public datasets covering transportation, health, buildings, the environment, community services, and more.
• CTA Developer Center — Bus, train, schedule, service-alert, and transportation APIs.
• U.S. Census Bureau Data — Population, housing, income, education, employment, and community data.
• U.S. Census Bureau APIs — Tools for incorporating Census data into websites, applications, and visualizations.

Before using a dataset, review its description, update date, limitations, and licensing or usage requirements.

• Figma — Design interfaces and create interactive prototypes.
• Figma Prototyping Guide — Learn how to connect screens and demonstrate a user journey.
• W3C Accessibility Guidance — Guidance for making digital experiences more accessible.

Non-coded Figma or design prototypes are allowed, but they should clearly demonstrate how the proposed experience would work.

• GitHub Repository Quickstart — Create a repository and organize your project code.
• GitHub Repository Best Practices — Document what your project does, how it works, and how to run it.
• GitHub Pages Quickstart — Publish a basic website directly from a GitHub repository.
• Vercel Getting Started — Deploy a web application and create a public project URL.

Never include passwords, private credentials, access tokens, or API keys in a public repository.

Generative AI tools are allowed but not required. If your team uses AI:

• Identify the tools or models used.
• Explain how AI supported the project.
• Review and understand AI-generated code and content.
• Test outputs for inaccurate, harmful, or biased results.
• Do not enter sensitive personal information into public AI tools.
• Clearly explain important limitations to judges.

For additional guidance, review the NIST AI Risk Management Framework.

Before submitting, confirm that:

• Your Devpost project page is complete.
• Your project or prototype link works.
• Judges have permission to access every submitted link.
• Your demo video plays correctly.
• Your slide deck is accessible.
• Your GitHub repository or project files are available.
• All code, data, models, research, and outside resources are credited.
• No passwords, API keys, or sensitive personal information are included.
• Every team member’s contribution is identified.

Submission deadline: 2:50 p.m. CT on Saturday, November 14, 2026.

Remember: A focused prototype that clearly addresses one user and one problem is stronger than an unfinished project with too many features.