H5P Content Type Scaffolder

Create a modern H5P content type starting from established boilerplates, with a minimal build pipeline and editor semantics.

How It Works

1. Choose package intent: library-install (default) or content-import (advanced).
2. Collect metadata (title, machine name, version, author, license).
3. Generate a boilerplate (default: SNORDIAN) that aligns with current H5P best practices.
4. Provide starter library.json, semantics.json, and JS/CSS entrypoints.
5. Outline build and packaging steps using h5p-cli.

Concepts

• Content types are runnable libraries under H5P.* (runnable: 1).
• Editor widgets are non-runnable libraries under H5PEditor.* (runnable: 0).
• semantics.json defines the editor form schema and validation rules.
• Non-runnable dependency libraries (often H5P.* or H5PApi.*) are used as shared building blocks.