Question: Why is the H5P content stored in a custom table instead of a post type?

[ptrin]

I was looking into the code because I'm curious about the level of effort to extend the plugin to support copying H5P content and storing revisions, and it seems that those features (and others) would be easier to leverage if the H5P content was stored in a custom post type instead of directly in its own table. Is there a reason this approach was used?

[icc]

The answer is simple: The plugin was originally written before the custom post type API was available.

[ptrin]

That makes a lot of sense, I appreciate the quick response :)