ACAD 276: Project Proposal by Mark Hou
Sundays is a community/organization between USC & UCLA, which hosts Pomodoro-style co-working sessions from 2-6pm on Sundays. This is to create a home for creatives & builders of all kinds, whether you a re a designer, developer, content creator, filmmaker, photographer/videographer, and more. However, currently Sundays' website is mainly for information about the organization, but to RSVP for events you need to go to our Luma.
As we are trying to improve our current website already, I thought it would be cool to develop a site specifically for our members, adding special perks (carpools, early signups & awareness of special events, etc.) The membership portal is for those that come frequently, and they can also post demos/links to their projects to get more awareness. This would also be an amazing hub to reach out to other people in Sundays, so you can learn who else in the organization shares your interests.
The primary audience is frequent Sundays attendees, people who use Sunday coworking sessions to make progress on side projects, creative work, startups, or school. For them, the portal can be a nice membership home to search for curated inspiration from other talented attendees, as well as hub for carpools/transporation, communication, and event signups.
The secondary audience is the Hosts (us who run Sundays), as it makes our job easier having one centralized hub for headcounts of events, keeping track of transportation, and also recording recurring attendees for our organizational growth goals.
The main data is entered by the Hosts. Some data includes about upcoming events (date, time, location, capacity). Other information includes the membership profile data (name, email, school, career field, project data), and also separating admins (Hosts) from members (general attendees).
Most of the data will come from members directly creating their profiles, and for the events the data will come from manual inputs by the Hosts when we make the events. Attendance records can also be inputted on the day of each event.
Other usage of data that might be out of the scope of the project, but that could be implemented, would be transportation data (mapping to locations), as well as messages (saving chat histories), as well as posting projects (project board data: name of project, date, content, photos).
Thank you!