Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Any fixes of the summary plugin requires plugin publish & will work only for the contents creating after plugin publish. Older contents need to edit & republish to get fixes of the summary plugin.

  • This is the core plugin changes(Stage plugin), any issues will have a huge impact on other contents as well.

  • If the user explicitly adding this plugin to the last stage, then he will see 2 stages with the summary plugin. Which he doesn’t have any info why it is showing twice.

  • We should know how many contents created with this plugin(using telemetry). So that any update of the plugin can be updated to all the contents.

Note:

Existing contents have to fix(remove the last slide). Else edit/copy of any existing will be having duplicate slides of the summary plugin.

...

  • Any fixes of the content requires course republish as well. Also user has to update the course to get latest changes of the course(self-assess content).

Solution 2:

Handling on consumption side as an end-page plugin(merging summary plugin & end page)

...

  • We do not need to change content editor code for a new content type, just a plugin change will suffice this requirement.

  • Existing content will work as it is [ if content-type is a resource, not self assess ] just that while editing it will show one last slide as the summary pluginSelf-assessment creation flow will get reduces, the user need not to add summary slide explicitly

  • Any edition in the future on the assessment parameter will get handled by the assessment end-page plugin.

  • Any fixes of the self-assess content doesn’t requires course/content republish. It will work for all old & new contents in the updated/new version of the app(which has summary plugin fixes)

Cons:

  • For old content migration, we will have to remove the summary plugin from existing content [ Migration task size will be a function of total content ]

  • Any fixes of summary plugin will be available only in the updated version of the app. Because summary plugin is the core plugin of the content-player.

We can look for hardcode push option to push summary plugin changes directly wihtout app update.

...

Note:

Existing contents have to fix(remove the last slide). Else edit/copy of any existing will be having duplicate slides of the summary plugin.

Solution: Manually fix the content body(because of limited contents <10) or write patch script on editor to handle these contents.