In this part of the specification we'll be looking at the file structure design used in H5P packages.
The file tree structure of the H5P package is designed to enable H5P's extensive re-use of code and the wide flexibility regarding what can be packed as an H5P.
The following is an example of how the structure should look for a Fill in the Blanks task.
. ├── content │ ├── images │ │ └── explain.png │ └── content.json ├── FontAwesome │ ├── ... │ └── library.json ├── H5P.Blanks │ ├── ... │ ├── library.json │ └── semantics.json └── h5p.json
Sat, 08/18/2018 - 12:16
Library directory names
I came across the following which might be worth noting:
The example contains the library
H5P.Blanks, it is worth noting that these library directories need to be in the format "machineName" or "machineName-majorVersion.minorVersion". "h5p-blanks" will not work, even though this is the directory that is cloned from git.
Tue, 08/28/2018 - 09:35
Hi Stefan!The repository
The repository files on github are not intended to be installable copies of the libraries. They often contain build files, etc. that are addressing developers. You can however download the files and use the h5p-cli tool to automatically create an H5P library file from the repository (after building) that can be uploaded.