SPIKE: Faster Cross-Chapter Navigation

Description

Need to create a list of stories to enable changing chapters without causing a full page load.

Open items:

  • Analytics impact

  • How to measure "page load" performance and compare initial loads with subsequent navigation

  • When is other work being done that will impact this page (there are navigation improvement plans in the works).

  • How to handle XBlock initialization, particularly w.r.t. asset dependencies and the various XBlocks that have code triggered off of the document.ready()

  • Should course navigation be driven at the XBlock level instead of being hardwired into the LMS?

  • How do we roll this out in a safe way?

Steps to Reproduce

None

Current Behavior

None

Expected Behavior

None

Reason for Variance

None

Release Notes

None

User Impact Summary

None

Status

Assignee

Unassigned

Reporter

David Ormsbee

Labels

Reach

None

Impact

None

Customer

None

Partner Manager

None

URL

None

Contributor Name

None

Groups with Read-Only Access

None

Actual Points

None

Category of Work

None

Stakeholders

None

Epic Link

Priority

Unset
Configure