WordPress and Articulate Rise
How to Upload Articulate Rise Packages to WordPress
Articulate Rise makes it straightforward to build polished, responsive eLearning content. Publishing that content on WordPress takes a little more planning: you need to decide whether the package simply needs to display, or whether you need standards-based learner tracking and reporting.
This guide explains the practical options for uploading Articulate Rise packages to WordPress, including manual embedding, tracking platforms, and a modern Gutenberg-friendly workflow for displaying self-contained HTML packages.
Start with the outcome
Choose the Rise export format that fits your workflow
The correct Rise export depends on what WordPress and your learning platform need to do after a learner opens the package. A web export is generally appropriate for presentation. SCORM and xAPI exports are for workflows that need compatible standards tracking.
| Rise export | Best fit | What to know before uploading |
|---|---|---|
| Web | Displaying a self-contained Rise course, guide, or interactive package on a WordPress page. | Does not provide SCORM or xAPI reporting by itself. LearnDash completion must be managed separately. |
| SCORM 1.2 | Traditional LMS workflows that require compatible SCORM tracking. | Needs a SCORM-capable player or LMS integration to record progress, score, or completion. |
| SCORM 2004 | Workflows requiring SCORM 2004 features and a compatible platform. | Compatibility varies by platform, so test the complete learner journey before launch. |
| xAPI | Detailed activity reporting through a Learning Record Store (LRS). | Requires an xAPI-compatible workflow and usually an LRS if you need meaningful reporting. |
Web export
Best for displaying a self-contained Rise package. It does not create SCORM or xAPI reporting by itself, so LearnDash completion must be managed separately.
SCORM 1.2 or SCORM 2004
Best for compatible LMS or player workflows that need standards-based tracking. Test the entire learner journey before launch.
xAPI
Best for detailed activity reporting through an LRS. It needs an xAPI-compatible setup rather than a simple WordPress embed.
Two valid approaches
Decide whether you need presentation or standards tracking
Display a Rise course cleanly on WordPress
Use this route when the package is a course preview, client resource, interactive guide, sales asset, or supplementary lesson. The priority is reliable delivery, responsive presentation, and an easy editor workflow.
Record learner activity, scores, or completion
Use this route when you need SCORM/xAPI data, detailed reports, or standards-based completion logic. It requires a specialist tracking platform and, where applicable, an LRS.
Option one
Upload a web export manually and embed it with an iframe
A manual workflow can work for a small number of web-exported packages. Export the Rise course for web, unzip it, upload the extracted files to a controlled location on your host, then embed its index.html file in a page or lesson.
- Publish the Rise project as a Web package.
- Extract the ZIP file locally.
- Upload the complete extracted folder to a dedicated directory on your server.
- Embed the package’s
index.htmlfile with an iframe. - Test the package on desktop and mobile before sharing it with learners.
src=”https://yourdomain.com/rise-package/index.html”
title=”Interactive Articulate Rise course”
width=”100%”
height=”780″
loading=”lazy”
allowfullscreen>
</iframe>
Option two
Use a specialist platform when tracking is required
If the course must report standards-based data, use a platform designed for that purpose. These tools are not interchangeable with a simple HTML package display plugin; they solve a more complex tracking problem.
GrassBlade xAPI Companion
GrassBlade is designed for xAPI, SCORM, and cmi5 workflows. It is a strong option when detailed tracking and Learning Record Store integration are central to the project.
Tin Canny Reporting for LearnDash
Tin Canny is a LearnDash-focused reporting option for organizations that need to capture and review learning activity from compatible modules.
Option three
Use a package loader for simple WordPress delivery
For web-exported Rise content that needs to display reliably without SCORM or xAPI reporting, a package loader gives site owners a cleaner alternative to manually managing folders and iframe code.
General-purpose HTML package tools
Tools such as eLearningFreak provide a general WordPress route for embedding HTML-based learning packages. Confirm the supported package type, delivery method, and reporting capabilities against your requirements.
Articulate Rise & HTML Loader
Our Articulate Rise & HTML Loader is built for displaying self-contained HTML ZIP packages directly in WordPress, with Gutenberg controls and a focused package-management workflow.
WPGator workflow
Upload Rise web packages with Articulate Rise & HTML Loader
Articulate Rise & HTML Loader is designed for WordPress sites that need a modern way to upload and display self-contained eLearning packages. It is suitable for Articulate Rise web exports and other compatible HTML package types.
Add the ZIP package
Upload a complete web-export ZIP while preserving its internal structure and entry point.
Choose a display mode
Add the package through Gutenberg or a shortcode, then select the presentation that fits the page.
Review attachments
Use the Package Attachments report to see where packages are used and open the relevant post or page for editing.
Delivery choices
Choose a display mode that fits the content
The package can be presented in several ways. The best choice depends on whether it is the main learning experience or a supporting resource inside a broader page, post, or LearnDash lesson.
| Display mode | Best for | Consider before using |
|---|---|---|
| Inline iframe | Embedding an interactive package directly in an article or lesson. | Set an appropriate height and test smaller mobile screens. |
| Lightbox | Focused viewing without permanently expanding the page. | Make the close action and return path obvious to learners. |
| Button launch | Supplementary content, demonstrations, and optional resources. | Use a clear button label so visitors know an interactive package will open. |
| Fullscreen popout | Rise packages that should feel closer to a dedicated course experience. | Provide a clear route back to the lesson or parent page. |
Inline iframe
Best for embedding a package directly in a page or lesson. Test its height carefully on mobile screens.
Lightbox
Best for focused viewing without permanently expanding the page. Make the close action clear.
Button launch
Best for optional resources and demonstrations. Use a label that explains what will open.
Fullscreen popout
Best when the Rise package is the main experience. Give learners a clear route back to the lesson.
Choose the right workflow
Keep package delivery and learner tracking separate when necessary
Choose a standards-focused platform when your project requires SCORM/xAPI reporting, LRS data, scores, or completion logic. Choose Articulate Rise & HTML Loader when you need a clean, WordPress-native way to publish compatible HTML learning packages without that reporting layer.
Get Articulate Rise & HTML Loader






