Online learning · Website design and development
ImagineIF Institute
The brief
ImagineIF Institute needed an online learning platform. My contribution covered the website design and the learning platform described in the portfolio, bringing together lessons, subscriptions, payments, cohorts, access, and analytics. The audience includes individual learners and company owners using the platform for learning. The task was to make the public website and the learning experience work as parts of one connected service.
An online learning platform needs to communicate what is available before a visitor enrols and then support the practical steps that follow: payment, access to learning material, and ongoing use. The project combines those needs in a WordPress environment. The details below describe the documented platform and the responsibilities provided for this case study, without attributing an unverified change in enrolments or revenue to the work.
Constraints and approach
The platform has several connected concerns. Course delivery must coexist with a front-end website, subscriptions, payment processing, and the distinction between individual learners and group cohorts. Each of these parts serves a different purpose, but they need to form a coherent journey for the people using the site and the team administering it.
The project record identifies Divi for the front end, Masteriyo LMS for course delivery, and WooCommerce with Stripe for subscriptions and payments. Google Analytics 4 and Google Search Console were set up to provide visibility into performance. The notes do not establish specific technical incidents or business targets, so those are not presented as historical facts here.
What was built
The website and learning platform connect public-facing content with the learning experience. Divi provides the front-end page-building environment, while Masteriyo handles course delivery. WooCommerce supports subscriptions and works with Stripe for payment. The documented setup covers both solo learners and group cohorts, bringing payment and structured course access into the same broader platform.
The work also included setting up Google Analytics 4 and Google Search Console from scratch. These tools provide a foundation for understanding how the website performs and how visitors find it. Setting up measurement is different from claiming a measured improvement: the available project description establishes the configuration, but it does not provide verified before-and-after results.
Technical decisions
The documented technology choices divide the platform by function. WordPress is the website foundation, Divi supports front-end presentation, Masteriyo supplies learning-management features, and WooCommerce and Stripe handle the commerce and payment side. This structure connects established tools instead of describing the learning site as a collection of unrelated pages.
The distinction between an individual learner and a group cohort is important to the way the platform is described. Both need a route to learning material, while the commercial and administrative context can differ. The existing notes confirm support for both, but do not describe every access rule or administrative workflow. Those specifics should be verified before adding a more detailed account. The same applies to any claims about custom code, migration, or third-party integrations beyond the documented stack.
The learning journey
The public website and the learning platform serve different moments in the same journey. Before enrolment, a visitor needs to understand what the institute offers. After enrolment, the learner needs access to the relevant material. The documented project connects those concerns through the WordPress website, Masteriyo course delivery, and the WooCommerce and Stripe payment setup.
The project information describes both individual learners and group cohorts, including company owners using the platform for learning. These audiences can enter the same broad learning environment in different contexts. The available notes do not establish every group-management rule, so this study does not claim a particular invitation, reporting, or administration feature that has not been documented.
Subscriptions and payments are part of the experience as well as the technology stack. WooCommerce manages subscriptions through Stripe in the documented setup. This is a description of the integration, not a claim about the number of subscribers, payment success rate, or revenue. Those results would require confirmed reporting and a defined period.
Finally, the setup of Google Analytics 4 and Google Search Console created a way to observe the site’s performance and search presence. Measurement can inform future decisions, but installing measurement does not by itself prove an improvement. Any future performance claim should be accompanied by its source, dates, and comparison.
Result and reflection
The result described in the portfolio is a connected learning platform covering lessons, subscriptions, payments, cohorts, access, and analytics. The work brings the marketing site and learning operations into the same project, so the experience can be understood from the first visit through course access.
No confirmed figures for learner growth, course completion, conversion, revenue, or time saved were supplied. The project should be evaluated on its documented components until those results are available. The existing portfolio screenshot is included as a visual reference, subject to confirmation that it may be reused in this case study. The live link lets a reader explore the public site; the current site may differ from the implementation captured in the screenshot.
Project image
