About Feli

People behind the project

Creator: Gian Alingog.

Faculty mentor: Maryam Majedi.

Background

I consider Feli as a reflection of my first year at UCSB because it serves as a testament of my growth across the three quarters I worked on it for.

Last Fall of 2025, I entered, eager to find something to do. That’s when I decided to reach out to Professor Majedi, when I was her student in CMPSC 16 at the time. When I told her I was looking to volunteer my time, she didn’t hesitate to give me the opportunity I needed to put myself to the test. Throughout this quarter, we mostly went over the big picture, quickly iterating over ideas and building demos to try and gauge what would be most useful to the UCSB community. We had some rough ideas for what Feli would become, and there are still some remnants left in the current version, but it’s definitely changed a lot since then.

It wasn’t until Winter that we finally locked in the idea of a task management system geared for the faculty and staff. It was also this stage that really began to test how fast I could learn “new tech,” since features were becoming more complex, and the system to needed to function coherently. I learned how to work around the stack, as they would say nowadays, picking up anything and everything from front-end design, handling auth (somewhat), managing a database and modeling the data, building and interacting with APIs, scripting, infrastructure and optimization, and a bit of CI/CD. By the end of Winter quarter, Feli was looking a lot less like a prototype and more like something I could see people using regularly.

Towards the end of Winter and the start of this Spring, we ramped up the demos and got as much feedback as possible. I had to do lots of iterative sprints, but it taught me to be flexible yet headstrong, whatever that really means. By the time I’m writing this, we’ve added in dozens of quality-of-life features, big and small, and have officially closed off the scope of the project. Feli should now be up and running, ready for public use!

That’s a sentence I thought I’d never be able to say. Looking back, I saw how much I improved, and how much I now better understand computer science as a whole, beyond theory.

Thank you

Thank you to everyone who came to my demos, tried early versions, and took the time to share honest feedback. Your questions and edge cases helped me iterate faster and make the product clearer.

• Krystal Contreras
• Angelina Aguilera
• Adrian Rodriguez
• Maritza Fuljencio
• Roselind Zeng
• Amy Sayer

A very special thank you to Maryam Majedi for being my guiding hand. You made the journey I took all the more meaningful and supported me through it all, even when things got tough. Thank you again for giving me the chance and for looking after me. I could never thank you enough.

Feedback

If you have ideas, bug reports, or feature requests, I’d love to hear them. A quick note could really help a lot, so feel free to fill out the form below.

How to use the platform

Feli has grown into a full task manager for UCSB teams. Here’s a walkthrough of everything it can do, from your first login to running a team as a supervisor.

Getting started

Log in with your UCSB credentials through CAS. Every new account starts out with the student classification, which is upgraded to faculty or staff by an existing staff member if needed. After logging in, you’ll land on your personal dashboard.

Your dashboard

The sidebar is your home base. It links to your dashboard, resources, notifications, teams, your profile, etc.

• Dashboard: a unified table of every task assigned to you, personal and team, with search, sort, and filter by status, priority, or due date.
• Personal tasks: create one-off or recurring self-tasks (weekly, biweekly, or monthly) that only you can see. Track status, log hours, and leave a note when you mark one complete.
• Resources: quick links shared by staff, filtered to what’s relevant to your classification.
• Notifications: assignments, nudges, and completions land her; mark them read individually or all at once.
• Profile: update your name, bio, and avatar, and toggle whether you receive email notifications.

Joining or creating a team

From the Teams page, students can join an existing team using a join code from their supervisor. Faculty and staff can also create a new team, which makes them its first supervisor and gives them a join code to share (regenerate it anytime from team settings).

Using a team as a member

Once you’re in a team, its own dashboard (with its own sidebar) shows your role, team goals, meeting info, and any quick links your supervisor has added.

• View the tasks assigned to you, update their status, log hours, and add a submission note when you finish.
• Check off team goals in the sidebar as you complete them. Everyone can see the team’s overall progress.
• Find meeting times (often a when2meet link) and shared folders or spreadsheets in the sidebar.

Running a team as a supervisor

Supervisors get extra tools for coordinating members:

• Assign tasks to one member, several members, or a whole group at once, including recurring tasks that generate their own instances on a schedule.
• Nudge a member with a reminder notification (and email, if they’ve opted in) if a task is overdue.
• Groups: organize members into groups for bulk assignment and bulk completion notifications, and track each group’s or member’s progress.
• Settings: set team goals, meeting info, and shared links; manage members, including promoting a member to supervisor or the reverse.

Connecting a Google Form

If your team collects requests through a Google Form, Feli can turn each response into a task automatically:

1. In your team’s settings, set up the Google Sheets integration. Feli generates an Apps Script snippet for you.
2. Open your form’s response sheet, go to Extensions → Apps Script, and paste the snippet in.
3. Deploy the script as a web app and copy the resulting URL back into Feli’s settings.
4. From then on, new form submissions become tasks automatically, and completing a task in Feli writes the status back to the sheet.

Faculty & staff tools

Faculty can submit course preferences each quarter: course, textbooks, equipment, teaching hours, preferred time slots, and any accommodations needed. Staff open each quarter for submissions, maintain the course code list, and can view every faculty response. Staff can also manage the global resources list and use the admin panel to promote or demote a user’s classification.