[Product Pull Request] Add toggle to allow redirecting to courseware after enrollment

jmakowski1123 commented 1 year ago

Abstract

For Contributing Author:

This is the Primary Product Ticket for the following community contribution: Add a toggle to allow redirecting to courseware after enrollment

Checklist prior to undergoing Product Review:

The following information is required in order for Product Managers to be able to review your pull request:

[ ] Explanation of the problem being solved
[ ] Description of how users will be impacted, and which users will be impacted
[ ] Screenshots or video showing the functionality or fix, before and after
[ ] Reproduction steps and/or testing steps

Only if necessary:

[ ] If necessary, links to corresponding configuration changes
[ ] If necessary, links to corresponding enablement changes, particularly waffle/toggle status details

Related PRs

[ ] https://github.com/openedx/edx-platform/pull/31715

For Product Manager doing the review:

What criteria should be analyzed from Product to approve a PR?

The problem being solved by the feature or fix is clear.
There is clarity on how the change or fix will impact the end user.
It is clear that the change will not negatively impact users or other areas of the platform.
The change is implemented comprehensively.
Any changes to UI use the current, standard Paragon Design System: https://paragon-openedx.netlify.app/

github-actions[bot] commented 1 year ago

Thanks for your submission, @openedx/open-edx-project-managers will review shortly.

jmakowski1123 commented 1 year ago

Info from PR:

Description

This change adds a new waffle switch to redirect a student to courseware after enrolment instead of the dashboard.

Supporting information

NA

Testing instructions

With a new toggle disabled, enrol a student into a course. They will be redirected to the dashboard after enrolment.
With a new toggle enabled, enrol a student into a course. They will be redirected to the course after enrolment.

Deadline

"None"

Other information

Private-ref: BB-7071

ProductRyan commented 1 year ago

@xitij2000 I am curious what the goal of this work is... what is the use case and how does bypassing the dashboard create value for you?

xitij2000 commented 1 year ago

This is a customisation that we are carrying for a client due to their requirements. We generally prefer to ensure that any customisations are upstreamed and available to the wider community.

In this case creating a hook/filter based system for this seemed like an overkill, so we went for a simpler config based approach, but are open to different approaches that maintain our clients preferred experience.

ProductRyan commented 1 year ago

@xitij2000 can you illuminate your client's use case? what's the reason that they want to bypass the dashboard? do their learners only ever access a single course?

The reason that I ask is that most navigation paths begin with the dashboard and the ramifications for skipping that page in the user's journey may have unintended consequences - I want to make sure we don't add complexity that could get a learner lost.

xitij2000 commented 1 year ago

@xitij2000 can you illuminate your client's use case? what's the reason that they want to bypass the dashboard? do their learners only ever access a single course?

The reason that I ask is that most navigation paths begin with the dashboard and the ramifications for skipping that page in the user's journey may have unintended consequences - I want to make sure we don't add complexity that could get a learner lost.

I think with this change the dashboard is still available and as prominent, it is only skipped in one situation, which is when a user enrols in a course, they are taken to that course immediately instead of to the dashboard first.

On login from the home page, users will still see their dashboard first, so other courses will still be as accessible as before.

DeanJayMathew commented 1 year ago

This would be a lovely toggle. We would use it for all our Open edX sites if it works as planned.

On Thu, 30 Mar 2023, 18:15 Kshitij Sobti, @.***> wrote:

@xitij2000 https://github.com/xitij2000 can you illuminate your client's use case? what's the reason that they want to bypass the dashboard? do their learners only ever access a single course?

The reason that I ask is that most navigation paths begin with the dashboard and the ramifications for skipping that page in the user's journey may have unintended consequences - I want to make sure we don't add complexity that could get a learner lost.

I think with this change the dashboard is still available and as prominent, it is only skipped in one situation, which is when a user enrols in a course, they are taken to that course immediately instead of to the dashboard first.

On login from the home page, users will still see their dashboard first, so other courses will still be as accessible as before.

— Reply to this email directly, view it on GitHub https://github.com/openedx/platform-roadmap/issues/242#issuecomment-1490122265, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACMGDWY5PEU7EXENXLSOSKDW6VTM3ANCNFSM6AAAAAAVO7UY3Y . You are receiving this because you are subscribed to this thread.Message ID: @.***>