Inspiration
School can be confusing when you need help but don't know where to go, who to ask, or what resource is right for you. Information is often spread across different places, and students can end up spending more time searching for support than actually getting it.
That inspired us to build SchoolBridge.
We wanted to create more than another school information website. We wanted to build a tool that could help students go from “I need help” to “here’s what I should do next.” The name SchoolBridge represents exactly that idea: creating a bridge between students and the resources, opportunities, and support available to them.
What it does
SchoolBridge helps students describe what they need and guides them toward relevant resources.
Instead of making students search through large lists of information, the experience is designed around a guided triage flow that can narrow down what a student is looking for. Results can then be ranked based on the student's needs, with explanations showing why a resource is a good match.
We also wanted the experience to be welcoming and usable for as many students as possible, so accessibility, plain-language guidance, keyboard navigation, and privacy considerations became important parts of the project.
How we built it
We built SchoolBridge as a modern web application using React, TypeScript, Tailwind CSS, and TanStack Start.
We focused on building the experience around a simple flow:
Student need → Guided questions → Relevant matches → Clear next step
Rather than overwhelming users with information, we designed the interface to progressively guide them toward useful results.
Challenges we ran into
One of our biggest challenges was figuring out how to take a problem as broad as “help students find support” and turn it into a simple user experience.
We had to think carefully about which questions mattered, how to organize potential resources, and how to explain recommendations without making the interface feel complicated.
We also had to balance personalization with privacy and accessibility. A feature isn't useful if students can't understand it or don't feel comfortable using it.
Accomplishments that we're proud of
One of the accomplishments we're most proud of is turning our idea for SchoolBridge into a working platform within the limited time of the hackathon.
We are especially proud of the way we focused on the student experience. Rather than simply creating a database of school resources, we designed SchoolBridge around how a student would actually use it — starting with a need and being guided toward a useful next step.
We're also proud that we were able to build a clean, accessible interface while working with technologies like React, TypeScript, Tailwind CSS, and TanStack Start. Bringing all of these pieces together while continuing to improve the project throughout the hackathon was a major learning experience for our team.
Most importantly, we're proud that SchoolBridge became more than an idea. We built something that addresses a real problem students face and created a foundation that we can continue improving beyond the hackathon.
What we learned
Building SchoolBridge taught us that good software isn't only about writing code. It's about understanding the person using it.
We learned more about building with React and TypeScript, structuring a larger web application, designing user flows, and thinking about accessibility from the beginning instead of treating it as an afterthought.
Most importantly, we learned that a strong project starts with a real problem. Every feature we added came back to one question:
Does this make it easier for a student to get where they need to go?
That question shaped SchoolBridge from the beginning.
What's next for SchoolBridge
While developing SchoolBridge, we made a conscious decision to prioritize the student experience first. With the time we had, we wanted to make sure that students could easily explain what they needed and find relevant support.
Because of that focus, one area we didn't develop as much was the process of creating and adding resources to SchoolBridge. We realized that helping students find resources and helping schools, organizations, or other users create and manage those resources are really two separate problems.
We think resource creation deserves its own thoughtful system rather than something we quickly add at the end. In the future, we would like to build a dedicated resource-management workflow that makes it easy to create, verify, organize, and update resources while keeping the same simple experience for students.
For this hackathon, we focused on what we believed was most important at the time: making SchoolBridge useful and intuitive for the student who needs help. Now we have a strong foundation to build the resource side of the platform on top of it.
Log in or sign up for Devpost to join the conversation.