...
The key challenge in designing a unified Studio Home experience is that each of these user types will have different levels of access and permissions, which will impact which and how many courses/libraries they see. For example, an admin may view and access all the courses in their organization or instance, while a course staff may only view and access all the courses on which they are a staff member. In its current state, there is no consideration given for the different needs that different users may have in viewing and accessing courses (for example, for users with long lists of courses, there are no navigation or search tools to manage content).
What is the secondary purpose of Studio Home?
...
Create a new course
Create a new library
Create a course run or re-run.
Future state: Navigate to global configuration functions (admin panel, taxonomy panel, etc)
These workflows create significant challenges:
...
The primary function of Studio Home–a quick, intuitive way for all users to view and access everything they have permissions to view and access–should be designed to allow users with varying levels of permissions to have a consistent experience in viewing/accessing courses and libraries, regardless of which permissions they have.
There are many enhancements we can make to improve the “view and access” use cases, such as searching for courses/libraries, filtering for courses, etc (and many more we will create in the user story writing process.)
The secondary function of Studio Home–to create something new–should be redesigned such that Studio Home is simply the jumping off point into each distinct “create something new” workflows (create a new course, create a new library, create a course re-run).
The workflows to “create something new” could be wysiwsg solutions and potentially more interactive. (Would you like to create something new? —> What would you like to create? etc etc)
...