* Post Launch Meeting
** Attendees:
   - KC Williams
   - Norm Rasmussen
** Notes:
   - Ideal regular meeting - every week until we are "more finished" and polished.
   - Fridays at 9:30 am EST
   - Is very happy that there's no confirmation email for pre-reg sign ups
   - Two common cases for learners with no course:
   -- Users signing up with their Gmail email
   -- A random person who isn't part of Anthology, finds their academy, might be interested to learn more, works in
      higher ed, and then signs up. <-- This is much smaller of a use case.
   --- This could also be for international clients, students, non-english speakers, or just random person in higher ed.
   -- If someone else types their email in incorrectly, that's a possible use case.
      DONE: Add warning for any personal email addresses entered into field. And make button unclickable.
   - At some point in the future (next FY-July-June) they will have some things published in the catalog.
   -- They are months out from that. Courses aren't developed yet.
   - For the edu users that aren't on the list should:
   -- Sign up as normal and make it past the first screen
   -- Ideally they will not see the Tell us More Screen.
   -- However, it's okay if they fill that out and then land on the /app page with the warning.
   -- They should NOT see an empty catalog.

** Search and Filter Needs:
   - This is priority one. Internally people are asking and external people are complaining.
   - They _need_ search and filtering capability. Right now, it's not really working as they need.
   - UX has asked KC to ask us for strategic advice. They need to look at it not just from how the screens look, but how
     they work too.
   - The original filter screen was removed from the main page cause it was causing confusion.
   - The experience should be that if you filter and then search you will search only WITHIN that filter.
   - Can we not use Ocean Academy to search and then filter?
     DONE: Can we do a "page search" bar that doesn't use Northpass searching? Some library?

** Roles and Content Grouping:
   - They are still thinking through something like an Ocean Academy example of grouping content
   - The roles for using engage will be different than the roles for reach
   - Sysadmin for Engage could be different than Sysadmin for Reach. It may not even be sysadmin - it would be "general
     technology".
   - Student is the "par excellence" where anything goes and all content is mixed.
   - Engage on the other hand has everything planned. They would have 14-15 permutations of different tagging of content.
   - Maybe we lead with a well-organized product.

** Other:
   - Amhit will be doing some people and content mapping. There's a QA doc for him to review. He will be doing clean up.
   - Abishek is on his team but unsure of responsibilities.