UI/UX

Owned by André Larouche (Deactivated)
Last updated: Mar 08, 2022
2 min read

DESK

  1. Analyse if the HiSports basic CMS can be a start for Desk

  2. Idea : View as person A, B, C impersonate the navigation for admin (show them what the user will see)

 

 

PAGE

  1. Look at if we will keep the basic framework HiSports web site / pages ex : https://omahahockey.ca/

 


MyAccount

  1. Bring HiSports permission and roles in my account

  2. Mapping HiSports vs Spordle structure, who’s gonna work on what…more work on

  3. Division / Category / Gender and such in Spordle ID

  4. Class = AAA, Division U16 = Category = Midget AAA

  5. Validate if API specs of Spordle ID are compatible with HiSports API

  6. Security architecture - authentication

 

PLAY

  1. re skinning HiSports

    • Header/sidebar are straightforward to implement (e.g., minimal dependency on react-admin)

    • MUI is very customizable, so we can come up with a comparable theme without too many differences

  2. Organisation change, and show on which organisation you are

    • Need to update the tenant entity to include a logo, include that on the current user API so we can show Hockey Canada in the header

  3. Ability to change from one app to the other (top right)

  4. Scorekeeper login

    • Need to look into what we can do with iframes to manage auth flow across domains (first-party)

  5. Pagination

    • Play’s API is fully paginated, SID is working towards it

  6. Rendering on the cell phone

  7. Standardization of the UX, same experience across the

    • Mostly similar with cards design

  8. How we will manage role, how we will merge

  9. Permission grid

  10. Use pages in HiSports for Spordle Page

    • Current implementation uses slate as the underlying format. Used in news/events/pages/announcements

  11. Need a discussion HiSports API and ID API’s