Articulate Rise & HTML Package Loader

Upload a package

Choose the intended storage folder, then drag one ZIP into the upload area. The plugin uploads the archive in chunks, validates it, extracts it into its assigned folder and generates a slug from the package filename.

HTML, CSS, JavaScript, media and other package assets are preserved. A working index.html is required, and archives containing executable PHP files are rejected.

Replace an existing package

Uploading the same package identity replaces the earlier extracted version without changing its slug. Existing blocks and shortcodes continue to target the replacement, and the operation does not consume another free-tier slot.

Delete a package

Deleting removes its package record and extracted files and releases its free-tier slot. Check Package Usage first: blocks and shortcodes already placed in content are not removed automatically.

Appearance settings provide the defaults for new blocks. An individual block can override those defaults without changing existing embeds elsewhere.

Add the block

Edit a page or post, add the HTML Course block, select an uploaded package and choose its display mode. Use the block settings for any per-embed text, size or appearance overrides.

Use with LearnDash

LearnDash is optional. When it is installed, place the same block inside a LearnDash lesson or topic as you would on any other WordPress page. LearnDash controls access and completion; the loader displays the package.

Use Copy Shortcode in the Package Manager or add the basic shortcode manually:

[hcu_course slug="your-package-slug"]

Optional attributes include mode, text, width, height, unit, overlay and theme. Prefer the generated shortcode when possible so the package slug is exact.

Package Usage scans WordPress content for both HTML Course blocks and [hcu_course] shortcodes. Each package lists its detected posts and pages, with direct edit links. Packages without a detected use are identified before deletion.

This is content-reference reporting, not learner activity or SCORM reporting.

Free capacity

The free tier permits two active packages—not two lifetime uploads. Delete an unused package to release its slot, or replace an existing package without using another slot.

Paid licences

Pro enables unlimited active packages on one production site. Agency enables unlimited packages across up to ten production sites. Manage the key under HTML Courses → License.

Deactivation and deletion

Normal plugin deactivation retains settings, package records and uploaded content. Review the plugin’s Data Management options before requesting a comprehensive deletion.

Confirm the file has a .zip extension, contains a working index.html and does not contain PHP files. Re-export the package rather than renaming another archive format.

Upload only one package at a time and wait for the completion message. Check browser developer tools and host security logs for blocked AJAX or chunk requests. A server, proxy or CDN may impose a lower practical limit than the plugin’s 200MB package ceiling.

Open the browser console and check for missing assets, blocked remote dependencies or JavaScript errors. Confirm index.html is at the usable package entry point and that the export can run independently of its authoring service.

Delete and re-upload the package. The loader inserts its narrow silent SCORM API compatibility stub during extraction when the relevant MindSmith package structure is detected.

Deletion removes the package files and record, not the block or shortcode in WordPress content. Edit the page listed in Package Usage and remove or replace the orphaned embed.