Add mobileBody and mobileInstruction to the core component schemas. Then, remove them from the schemas of components like Hot Graphic and Narrative. Would require migration scripts.

Does this need raising as a separate issue so it's not forgotten when the PR is merged?

Does this need raising as a separate issue so it's not forgotten when the PR is merged?

@kirsty-hames Great idea. I've created issues for these two plugins.

adaptlearning/adapt-contrib-hotgraphic#308
adaptlearning/adapt-contrib-narrative#302

Should we do the same for component.hbs body? I think Core wise, Media is the only component still using hbs templates.

@kirsty-hames I've added mobileBody to component.hbs. However, it appears that the expectation is for individual plugins to determine whether body or mobileBody would be used (same for instruction and mobileInstruction). This is different from the header.jsx template which determines the appropriate property to use within the template itself.

So, for this to work in Media and other plugins that still use the older template, updates to the Media plugin's JS would be needed. The change in 2b565d8 will help to facilitate this, though.

🎉 This PR is included in version 6.48.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀