UI/UX
DESK
Analyse if the HiSports basic CMS can be a start for Desk
Idea : View as person A, B, C impersonate the navigation for admin (show them what the user will see)
PAGE
Look at if we will keep the basic framework HiSports web site / pages ex : https://omahahockey.ca/
MyAccount
Bring HiSports permission and roles in my account
Mapping HiSports vs Spordle structure, who’s gonna work on what…more work on
Division / Category / Gender and such in Spordle ID
Class = AAA, Division U16 = Category = Midget AAA
Validate if API specs of Spordle ID are compatible with HiSports API
Security architecture - authentication
PLAY
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
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
Ability to change from one app to the other (top right)
Scorekeeper login
Need to look into what we can do with iframes to manage auth flow across domains (first-party)
Pagination
Play’s API is fully paginated, SID is working towards it
Rendering on the cell phone
Standardization of the UX, same experience across the
Mostly similar with cards design
How we will manage role, how we will merge
Permission grid
Use pages in HiSports for Spordle Page
Current implementation uses slate as the underlying format. Used in news/events/pages/announcements
Need a discussion HiSports API and ID API’s