Case Study: Designing a Branded LearnDash Course Vault, Then Rebuilding It After a Hack

How I turned a generic LearnDash course into a branded, tile-based course vault with Elementor for a health practitioner, then rebuilt it after a hack wiped the work, and the backup habits that prevent it happening again.

LearnDash Course Vault: Built, Lost, Rebuilt

Table of Contents

A holistic health practitioner came to me with a LearnDash course that worked but looked generic: a plain list of text links behind a password page. Over four orders we turned it into a branded, tile-based course vault built with Elementor, then rebuilt it from scratch after a security incident at her old host wiped the work. This case study covers the brief, the design decisions, the feedback loop that kept a busy client involved without draining her time, what went wrong, and the habits I now insist on so it never happens again.

Project snapshot
  • Client: a holistic gut-health practitioner running a 3-month GI Map healing program
  • Platform: WordPress, LearnDash LMS, Elementor Pro, later moved to SiteGround
  • Work: course vault design, lesson templates, sidebar, recipe cards, full rebuild after data loss
  • Timeline: February to July 2026, 6 orders in total including follow-ups
  • Result: clients use the vault daily and the practitioner left five-star reviews plus a tip

The brief: make a course feel like a premium private vault

The first message was honest and a little anxious. The practitioner had already worked with another developer to set up a LearnDash course for her clients. The course existed, the videos were uploaded, but the main page was a list of module names on a white background. She was launching a three-month GI Map healing program and wanted her paying clients to feel they were stepping into something special, not clicking through a default template.

Her goals, once we talked them through, were clear:

  • A vault landing page with visual tiles for each module instead of text links.
  • Branding that matched her existing palette, including a soft grey background (#f7f7f7) and her signature blue.
  • Lesson pages that looked consistent, with the video first, then written content and downloadable handouts.
  • A sidebar promoting her children’s book, her supplement dispensary and a lab ordering link.
  • A special recipe module where clients scroll through colourful meal-plan cards and download PDFs.
  • Password protection so only enrolled clients could get in.

She also had a deadline. She had started the project in early January and hoped to launch by mid February. When she reached me, that left about two weeks.

First decision: keep LearnDash, design with Elementor

A common instinct is to rip everything out and start again with a different LMS. That would have cost her time she did not have. LearnDash was already handling enrolment, progress and access, and it does that job well. What it does not do out of the box is look like a boutique product. So the plan was simple: keep LearnDash as the engine, and use Elementor Pro templates for everything the client sees.

On our first video call I showed her how the pieces would connect: an Elementor-designed vault page with tiles that link to each LearnDash lesson, and a single lesson template applied to every module so changes happen in one place. I also recommended which Elementor plan to buy and why, but asked her not to purchase anything until we had agreed the scope. That small step builds trust. Clients have usually been burned by someone who sold them tools they did not need.

The feedback loop that made two weeks possible

She was running a practice and seeing patients back to back. Long email chains would have stalled everything. So we set up a rhythm that respected her time:

  • Short video calls, often 10 to 15 minutes, booked around her clinic hours. Some were at 6:30 in the morning her time; I adjusted my day so she did not have to adjust hers.
  • One shared folder for handouts and images. She had never shared a Google Drive folder before, so I walked her through setting it to view-only for anyone with the link.
  • A transparent time log. Every few days I shared a Clockify link showing exactly what each hour went into. For an hourly-style project this removes the uncomfortable money conversation.
  • Small, checkable milestones. Three tiles first, then the full grid, then the sidebar, then lessons. She could approve or redirect after each step.

When she asked for a rough total cost so she could plan, I gave her a breakdown: about five hours to finish the landing page, three to four hours for the lesson layout, and time for the template itself. Clear numbers early prevent surprises later.

Challenge 1: tiles that tell people where to click

The tiles had to work on a laptop and on a phone. Long module names broke the grid, so I set a writing rule: each tile description between 17 and 20 words, which fits two lines on desktop and three on mobile. I drafted the first three tiles, she approved the tone, and I wrote the rest from her course content.

There was one confusing moment. I noticed the tile titles did not match the module names in the course. The modules were simply named Module 1, Module 2 and so on, while the real lesson titles lived inside the first item of each module. Once I found that, the mapping was easy, but it is a good example of why I always ask before assuming. A quick message saved an hour of rework.

She also commissioned static images from another designer. They came out more floral than she wanted, and she decided to go with good and done over perfect and unfinished. I made sure the layout supported those images well rather than fighting them.

Challenge 2: lesson pages, materials and the recipe module

Inside each module the order mattered: video at the top, a short written introduction, then the materials. Old handouts were mixed in with new ones, and some charts were too blurry to read on screen. We agreed to move every handout into a single materials section per module as a PDF download, which made them easier to find and easier to update later.

The recipe module was the fun part. She wanted it to feel colourful and scrollable, like a menu. I designed a card for each meal plan and recipe bundle using her images, with each card linking straight to its PDF. On the sidebar I added boxes for her book on Amazon, her supplement dispensary and the lab ordering page, each with a clear label so clients would know exactly what they were clicking.

At one point a module would not load for her even though it worked for me. A short screen-share showed the cause: her browser was holding an old cached version. Clearing the cache fixed it. I mention this because it happens on almost every project and it is easy to panic about.

Going live: connecting the course to payments

When the design was done she asked a very reasonable question: so how do people actually get in? She had expected a password box to appear somewhere on her main website. We talked through the options: selling through WooCommerce, using the course link after a Stripe payment, or adding a clear menu item to the vault with a password page. Knowing the course link could be used anywhere gave her flexibility. We delivered, and a few weeks later she wrote back to say her clients were loving the vault.

“Tanvir was absolutely incredible to work with. He walked me through every single step of the process with so much patience and clarity, and truly made the entire experience feel easy and supported. This has been one of the best Fiverr experiences I've had.”

Health practitioner, LearnDash course vault, first build

Then the site was hacked, and the vault disappeared

In March she messaged me in distress. Her About page had been injected with gambling spam. The hosting company cleaned it up, but in the process the vault reset to an old, broken state. Worse, the backups they restored also contained the malicious code, and the vault design was not in any clean backup. The work was effectively gone.

This was the hardest part of the project, and not for technical reasons. She had paid for the work once and was understandably upset at the idea of paying again. Her host was a design agency that did not offer hosting panel access, did not work with Elementor and was not sure what had happened. She was stuck in the middle, relaying messages between people who did not speak the same technical language.

Here is what I did:

  • Explained in plain words what had happened: the clean backups predated our work and the newer ones were infected, so there was nothing safe to roll back to.
  • Wrote a polite message she could send to her host asking for control panel access and manual backups, so she would not depend on anyone else to protect her own site.
  • Contacted the host’s support directly, with her permission, to compare notes. That conversation confirmed the theory and ended the guessing.
  • Did not charge for the hours spent writing messages and investigating. She offered to pay; I told her I would only charge for real website work. Charging her for a problem she did not cause would have been wrong.
  • Recommended security basics: a strong unique password, a security plugin, removing old admin users and keeping daily off-site backups.

Two page builders on one page: the hidden cause of the mess

While we waited, another question came up. Her site used Divi for most pages and Elementor for the vault. A different designer suggested the two builders were conflicting. They can conflict if both are used on the same page, which can happen by accident when someone opens a page in the wrong editor and saves it. We had only used Elementor on the vault, but the old pages being in Divi made every fix harder.

She made a sensible decision: move the whole site to a company that works only with Elementor, host it on SiteGround with daily backups, and convert the remaining Divi pages over time. I supported that plan and waited until the migration was confirmed before touching anything, because rebuilding on unstable ground would have repeated the same risk.

The rebuild: faster, cleaner and template-first

In April, with the site on new hosting, I rebuilt the vault. The second time was quicker for one reason: there was no feedback loop needed for decisions already made. I estimated about 10 to 12 hours and broke it into two orders.

  • Rebuilt the vault landing page with visual tiles, matching a screen recording she had kept of the original.
  • Rebuilt the single lesson template and reconnected every lesson to it.
  • Re-uploaded all PDF handouts because the old file links were dead after the migration.
  • Rebuilt the recipe module cards and the sidebar boxes.
  • Saved everything as Elementor templates in the theme builder, so a future problem would cost minutes, not days.

Afterwards I showed her where global colours and typography live in Elementor’s site settings. She wanted to change the bold heading colour to her brand blue, and once she knew where it was she did it herself. Teaching clients to make small changes is one of the most valuable things a developer can do, and it saves them money on every future edit.

“Working with Tanvir again has been a great experience. I would highly recommend him.”

Health practitioner, rebuild order

One more twist: a migration broke the password box

In July her new web team finally removed Divi from the site entirely. Afterwards, the password field on the vault disappeared. On a call I traced it to a missing database table after the migration. I restored the password protection, tested it from several devices with the cache cleared, and recorded a short video explaining where to change the vault password herself in the course settings. She was rushing to a class, so a recording she could watch later worked better than another meeting.

What I learned, and what you can take from it

  • Own your hosting access. If you cannot log into your hosting panel or download a backup yourself, you do not fully own your website.
  • Take a manual backup the day a big piece of work is finished. Daily automatic backups are good; a named backup after a milestone is better.
  • Save designs as templates. A template can be re-imported in minutes after any accident.
  • Use one page builder. Mixing builders across a site makes every fix slower and riskier.
  • Keep the feedback loop short. Ten-minute calls and visible time logs beat long email threads, especially for busy professionals.
  • Be fair when things go wrong. I did not bill for investigation time on a problem the client did not cause. That honesty is why she came back three more times.

Need a course site that feels premium?

If you run courses, coaching programs or memberships on WordPress, I can help you turn a default LearnDash setup into something your clients are proud to log into, and set it up so it survives updates, migrations and accidents. I work in small, visible milestones with short calls and shared time logs, so you always know where your money is going.

Work with meWordPress, LearnDash and Elementor expert help

Course design, LearnDash setup, fixes and rebuilds, delivered with clear milestones and a shared time log.

View the Fiverr gig →

Not sure which service fits? Send me a short brief and I will reply within 24 hours with a plan and a fixed price.

Frequently asked questions

Can LearnDash courses be designed with Elementor?

Yes. LearnDash handles enrolment, access and progress, while Elementor Pro templates control how the course pages and lessons look. That combination keeps the engine stable and the design flexible.

How long does a LearnDash course vault redesign take?

In this project the first build took roughly two weeks of part-time work across several short milestones. The rebuild took about 10 to 12 hours because the design decisions were already made.

How do I protect my course pages from being lost?

Keep your own hosting access, run daily off-site backups, take a manual backup after big changes and save your Elementor designs as templates.

Is it a problem to use Divi and Elementor on the same site?

It works if each page uses only one builder, but it makes maintenance harder. Opening a page in the wrong builder and saving can break it. Most sites are easier to manage with one builder.

Free toolTry the Website Cost Calculator

Free, no sign-up, works on any device.

Open the free tool →
Written by Tanvir H

WordPress and Elementor web designer at Tanvir WebXprt, Bangladesh, with 7+ years of experience and 650+ projects. Tanvir builds the free tools on this site and writes practical guides for creators, learners and small businesses.

Learn more

Guides for this tool

Built by Tanvir WebXprt

Want a tool, website or app like this for your business?

Every free tool on this site is designed and coded by Tanvir H, a Bangladesh-based WordPress and Elementor web designer with 7+ years of experience and 650+ projects for clients worldwide. Fast, mobile-first, search-optimised websites that turn visitors into customers.

Website developmentWordPress, Elementor & e-commerce sitesfrom $899
Creative designWeb, graphic & brand identityfrom $220
SEO & paid adsRank on Google, run Meta & Google Adsfrom $300
Speed & fixesCore Web Vitals, bugs and upgradesCustom quote
  • 650+ projects
  • 7+ years
  • 4.9★ rating
  • Govt. registered freelancer

Contents

Was this helpful? Spread the word and share with your network!
Facebook
Pinterest
LinkedIn
Reddit
VK
X
Telegram
Threads
Tumblr
Email
WhatsApp
Pocket

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Article