What was that thing again? An H5P architecture overview

When talking about H5P, one can easily get lost in terminology – in particular if one has not used H5P before. This brief description of H5P’s architecture is supposed to help to deepen the understanding of H5P. The description is directed at developers in particular who want to understand what they are dealing with. Hopefully,…

How can I let H5P content types store the state actively?

The core of H5P takes care of storing contents’ state automatically if the resume feature is activated in the H5P integration settings. State is stored in regular intervals and based on some content type events and browser events. However, there may be a good reason why you don’t want to wait for H5P core to…

How can I implement support for resuming in an H5P content type?

Implementing H5P’s resume (or “save content state”) feature is pretty simple for developers. Whenever the core of H5P wants to store the current state of a content type instance, it will try to call a function named getCurrentState and expects the function to return anything serializable that you might want to store. When the user…