Branching Scenario: Make using Custom End Scenarios more comfortable

otacke's picture

In Branching Scenario, having an option for custom end scenarios is a great way to give feedback. However, in practice you often have "classes" of custom end scenarios. In other words: You may have 20 nodes that should end in custom end scenarios, but in fact it might be 4 classes of custom end scenarios that are the same for 5 nodes each. Right now, you cannot reuse a custom end scenario, but you will have to create it over and over again as settings of the node that preceeds the custom end scenario.

Suggested solution

  • Add custom end scenario: As an author, in the editor canvas I can drag a "custom end scenario" content item from the side bar to the canvas and drop it as a successor to an existing node or to an existing branching question option (add new or replace existing content just like for any other content) in order to add a custom end scenario.
  • Customize custom end scenario: As an author, in the editor canvas I can open the editor overlay for a custom end scenario just like I can for any other node in order to customize the end scenario (Custom end scenario title, Custom end scenario text, Custom end scenario image).
  • Reuse custom end scenario a): As an author, in the editor canvas I can copy and paste a custom end scenario just like any other node.
  • Reuse custom end scenario b): As an author, in the editor overlay of a node I can select "Jump to existing end scenario" (if applicable) instead of choosing "Custom End Scenario" and then choose from a list of existing custom end scenarios (just like it's done for content nodes).


  • The changes could be implemented by creating a separate "branching end scenario" content type similar to the "branching question" content type. This way, much of the required functionality could be inherited from the existing code (dragging/dropping nodes, editing, copy & paste), but the data structure and/or related functions would very likely need to be changed to be able to not only distinguish between content nodes and branching questions, but also between custom end scenarios. Welcome to the danger zone!
  • In the canvas, end scenario nodes could either get a slightly different styling compared to a regular node (e.g. be slightly red, have a thick border, etc.) or simply look like a regular node with the red flag attached.
  • It might be possible for me to contribute the required code if the user stories and UX can be agreed upon.
Content types: 
Supporter votes Members of the Supporter Network can vote for feature requests. When the supporter network has generated sufficient funding for the top voted feature request it will normally be implemented and released. More about the H5P Supporter Network
Learningbuzz's picture

Branching scenarios are not available in Canada.

BV52's picture

Hi Learningbuzz,

Contents that are available in is not location based. To provide a best possible experience for new users and to ensure that people use only for trying out H5P (we've had more traffic than our server can handle lately, ref also the warnings when you create content, embed content and view the content) we are experimenting with which content types should be available here.

Check the getting started page for information on how you can use all the content types and use H5P for real. We unfortunately are not able to provide free hosting, only free software :) Hopefully you'll consider supporting the H5P Core Team by using