Inspiration
We help run a student organization at our campus named ACM UTSA that hosts various events and hackathons throughout the year. A common pain point we find is that pre-existing scheduling and directory tools do not meet the needs of a student org, with the pace of movement and flow of new officers we see. O is a toolkit that offers various features that help us manage the org and solve these pain points, allowing us to run the organization with more ease and ability to focus on the important things.
What it does
O has 3 main core features at the moment
- Officer Directory
- Meeting Scheduling
- Quick Links
Officer directory is a directory of the officers within the org, with the size of our org it can genuinely be difficult to keep everything in line, and this provides a single source of truth for who is doing what.
Meeting scheduling allows us to schedule meetings with ease, while also working for people who do not keep there calendars very up to date.
Lastly, quick links allow us to make links for us and others that link quickly to key resources.
How we built it
We used React, Next.js, Typescript, next-safe-action, libsql, lucia-auth, and drizzle
Challenges we ran into
We struggled with getting notion authentiaction to work as a single sign on method. Notion works well as SSO for us since every officer has their own unique pre-existing account, but the documentation is somewhat sparse and required work to get working.
Accomplishments that we're proud of
- Implementing in-house authentication
- Modeling complex meeting events in database
- Building a sleek and elegant UI
What we learned
We learned a lot about rolling our own authentication, and made sure to make continuous progress under the deadline.
What's next for O
We want to keep adding new features for the project! Additionally, we are hoping to fully roll this out within our org!
Built With
- and
- drizzle
- libsql
- lucia-auth
- next-safe-action
- next.js
- react
- typescript
Log in or sign up for Devpost to join the conversation.