WordPress courses without LearnDash
Published 4 min read
LearnDash raised its renewal prices significantly in late 2026. The jump is jarring, but it also forces a question that should have been asked earlier: what does this install actually use? A site hosting internal staff training, a small public course library with no graded assessments, or an onboarding sequence for new customers is using the structural quarter of what LearnDash ships.
That structural layer does not require the quiz engine, the certificate builder, the drip-content scheduler, or the payment integrations that sit on top of it. Those features are what the price buys. For a site that never touches them, what remains is a plugin that registers two custom post types, a shortcode that marks lessons complete, and a few rows of user meta.
The features that drive the price
LearnDash has three functional layers. The structural layer is courses as custom post types, lessons as children, enrollment written to user meta, and progress calculated from lesson completions. The assessment layer adds quiz question banks, grading, pass/fail logic, certificates with merge tags, and assignment uploads. The business layer adds drip-content scheduling, group seat licences, Stripe and WooCommerce payment integration, and the reporting infrastructure that makes all of that auditable.
The structural layer exists in nearly every LearnDash install. The assessment and business layers are used selectively; many small sites never configure them. A price that reflects the full stack is a reasonable prompt to audit which layer you actually use. Anyone running a paid course business with assessed modules, completion certificates on file, or company-level enrolment reports should stay exactly where they are.
The enrollment and progress model
When a user clicks Start Course, the plugin writes an enrollment record to user meta, keyed to that course. When they click the completion checkbox next to a lesson inside the [steem_course] shortcode, it writes a per-lesson completion record. Progress is not stored as a figure; it is recalculated on each render by dividing completed lessons by total lessons in the course.
LearnDash uses the same shape internally. Its progress data lives in a serialized array at _sfwd-course_progress on the user object, one entry per enrolled course. The structure maps directly onto a simpler per-lesson model, which matters if you are building a migration path from an existing install.
Moving content from an existing LearnDash install
LearnDash stores courses in the sfwd-courses custom post type and lessons in sfwd-lessons. Both are standard WordPress posts; the text content and featured images migrate without any rewriting. The parent-child relationship does not transfer automatically, because LearnDash associates lessons with courses through a meta key on the lesson rather than WordPress's native post_parent field. A migration script reads that meta key to rebuild the relationship the replacement plugin uses.
Completion records do not migrate. Users who finished courses in LearnDash will show no progress in the replacement plugin. For a staff intranet with a handful of courses and known users, re-marking progress manually is workable. For a site with thousands of enrolled students whose completion dates are on record, that history has value. Losing it is a reason to stay, or at least to export and archive the records before switching.
What you get
Included
- Course and Lesson custom post types with parent-child relationship via post_parent
- Enrollment stored in user meta when a logged-in user clicks Start Course
- Per-lesson completion tracking with a computed progress percentage per course
- [steem_course id=""] shortcode rendering the lesson list with completion checkboxes
- My Courses account page listing enrolled courses with progress percentage
Not included
- Quizzes, graded assessments, and question banks
- Certificates generated on course completion
- Drip content: releasing lessons on a schedule after enrollment
- Group enrollment, seat licences, and company-level progress reporting
- Payment integration or access gating by purchase
LearnDash does the things on the right. This build covers the part most sites use.
Questions
Can a site owner add courses and lessons without developer involvement?
Yes. Course and Lesson appear in the WordPress admin sidebar as standard post types. Adding a course is adding a post; adding a lesson means creating a post and setting its parent to the right course. No shortcode editing or theme changes required for content updates.
Build it in Steem
The button opens the builder with this guide's prompt filled in, so you can change anything before it runs. Nothing is built, and nothing is charged, until you send it.
Read the prompt (121 words)
Build a WordPress plugin that registers two custom post types: Course and Lesson. Lessons belong to a Course via post_parent; their display order follows menu_order. Add a Start Course button on single course pages that logs a logged-in user as enrolled by writing a timestamp to user meta. Add a [steem_course id="123"] shortcode that shows the full lesson list with completion checkboxes; clicking a checkbox marks that lesson done in user meta and recalculates the course progress percentage shown above the list. Add a My Courses page to the user account area listing enrolled courses with their progress percentage. Add an admin screen under a Courses menu showing all courses with an enrollment count and average completion percentage across enrolled users.
Steem