Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

This meeting was just to welcome back the existing Trends team and give updates on summer progress.

  • New Project Lead (hi)

  • Welcome Back

  • Trends Summer Updates

  • Roadmap

  • Assigning small tasks to start for each division

\uD83D\uDDE3 Discussion topics

Item

Notes

Current plan

  • Try to get new Trends update out in production by October

  • Try to get new Marketing recruits

New trends update (what we did)

  • Revamping the Search, to be more broad or more specific as needed.

    • Which leads to a new search results UI

  • Added more filters/sorting to allow specificity.

  • New Compare page, that can compare different professors/courses.

Designers

  • Reformat the compare page - for Designers

  • Compare page needs to be able to read up to 5 professors - figure a way to view all professors' data better.

  • Also some small components should be cleaned up in Figma for engineers to implement

Product team

  • Start talking to people about how the dashboard looks like and how they work.

    • Are users understanding data available and what the results indicate

  • New user stories

  • Prepare surveys

  • Suggestion - Get surveys at all hands since we have a lot of people there.

  • Different Axis on graphs and data, is it consistent?

Marketing

  • Get more Marketing people and figure out a way to market nebula through campus both online and in person

  • Event Ideas for the semester

    • Ice cream social(Already planned)

    • Halloween Social (Potentially Oct 28th-31st)

    • Christmas Social/ EOY social (Potentially Dec 2nd-6th)

    • Nebula Hack

    • Potluck TBD

Engineering

  • Bugfixes

  • Error Handling

  • Finishing Touches

    • Default sorting - Which sort?

    • Caching? (Complex)

    • Recent Tags - You can see what you search in your last 5 searches.

Analytics

  • Use the Analytics (Vercel or google) to see where most People click from, which features are being interacted with, lag time and user frustrations.

Engineering Workshop

  • Teach and show new recruits how the code base works and how everything connects together

  • Maybe give tasks for new members to document the code and APIs.

  • Maybe make a google doc explaining how the code base works. (Write it over time, because time consuming).

✅ Action items

  •  

⤴ Decisions