JoomShaper Language School - Joomla Template

Configuring JoomShaper Language School for a Joomla Language School Website

JoomShaper Language School is best viewed not as a standard visual template, but as a ready-made Joomla setup for an education website: the homepage design, course pages, events, program search, contact header, language switcher, SP LMS modules, and SP Page Builder editing all work here as a single system. In this guide, we will walk through how to prepare the installation, choose between quickstart and the regular template package, and configure the header, menu, module positions, courses, events, footer, responsiveness, and safe customizations.

This guide is intended for a school owner, Joomla administrator, or webmaster who has received the ZIP archive and wants to do more than just enable a polished homepage. The goal is to turn the site into a working project: replace demo data, build a program catalog, configure course inquiries, test the mobile menu, remove unnecessary blocks, and understand why some elements may not appear after installation.

I am not going to rehash the template's marketing copy. Instead, this guide is built around practical use: what to check before installation, where the key settings are located, how Template Styles, Modules, SP LMS, SP Page Builder, and Joomla menus connect to each other, which issues are typical for this kind of setup, and when it makes more sense to choose a different education template or a separate LMS component.

What This Template Is Designed to Do

The main value of JoomShaper Language School is that it already brings together the standard building blocks of a language school website: top navigation, a hero section with a clear call to action, program cards, course search, teacher or benefits sections, events, testimonials, a news area, an admission page, and a footer. If you were building this kind of site from a blank Joomla install, you would have to design the structure, choose a template, configure an LMS component, set up module positions, and style the pages separately. Here, that starting logic is already in place.

The template relies on three important layers. The first layer is the Joomla template itself with Helix Ultimate settings: logo, header, menu, footer, Layout Builder, responsiveness, and custom code. The second layer is the pages and sections built in SP Page Builder Pro inside the quickstart package. The third layer is SP LMS, which handles courses, events, categories, lessons, teachers, reviews, orders, and related modules.

This approach works well if you need more than a simple school brochure site and want a page where visitors can browse programs, find a suitable course, open the details, and contact an administrator. But it also requires careful setup: if you delete a module, fail to assign it to the correct position, or install only the template package without the demo content, the final result will look very different from what you expect.

When the Template Is Especially Useful

JoomShaper Language School is a good fit for websites that need a clear structure around educational programs. That includes a language school, exam prep center, conversational English club, small training center, offline courses with a schedule, or an educational project with events and an admissions page. In these scenarios, flashy animation matters less than a clear flow: program - schedule - level - application - contact.

When the Template May Be More Than You Need

If you only need a lightweight one-page landing page without a course catalog or events, this template may feel too heavy. If the project requires a complex learning platform with progress tracking, user accounts, many lesson types, external service integrations, and deep analytics, you should evaluate SP LMS carefully and compare it with full LMS solutions. If your website already runs on a different architecture and you have a large amount of existing content, installing quickstart on an existing Joomla site is not appropriate: quickstart installs as a separate website, not as an extension on top of your current setup.

Product Map: What a Working Site Is Made Of

To avoid getting lost in the settings, it helps to think of the template not as a one-click install, but as a map of dependencies. The homepage design depends on SP Page Builder demo sections, course and event modules pull data from SP LMS, the header and footer are controlled by Helix Ultimate settings and Joomla modules, and block visibility depends on position and menu assignment.

Joomla as the Foundation

Joomla stores menus, articles, modules, languages, users, access permissions, and system settings. Even if most of the homepage is assembled visually, navigation and module assignment still depend on standard Joomla logic. That is why, after installation, you should not limit yourself to editing the polished blocks in the builder. Check the menus, system languages, access rights, module positions, and cache settings as well.

Helix Ultimate as the Template Framework

Helix Ultimate controls what is usually considered the site's framework: logo, header height, sticky header, predefined header variations, Layout Builder, footer, custom CSS, responsive breakpoints, and part of the technical configuration. In the Language School documentation, the header settings are tied directly to the path Extensions - Site Template Styles - shaper_languageschool - Default - Template Options.

SP Page Builder as the Page Editor

SP Page Builder is used for sections, modules, and ready-made content blocks. In quickstart, it is already installed and configured, so you can edit the existing pages and SP Page Builder modules. The regular template package does not include the builder itself: if you install only the template, you will need to create the pages and modules manually or install the required page builder separately according to your update and licensing rights.

SP LMS as the Learning Layer

SP LMS handles the education-specific entities: courses, categories, lessons, quiz questions, results, certificates, teachers, events, reviews, and orders. This is especially important in Language School, because the homepage and blocks like Course Search, SP LMS Courses, and Upcoming Events are supposed to display real academic programs, not placeholder content. If there is no data in SP LMS, or the module is configured for the wrong course type, visitors will see an empty or incomplete block.

What to Check Before Installation

Preparation is not just a formality here. JoomShaper Language School supports two different installation scenarios, and the one you choose affects the entire workflow. Quickstart is for a new website that should match the demo structure. The template package is for an existing site where you want to install only the template and build the content manually.

Quickstart or Template Package

Quickstart includes Joomla, the template, demo content, additional components, modules, and settings. It cannot be installed through the Extensions Manager on an already running Joomla site because it is effectively a full website installation package. This option is convenient for a staging site, a new school, or a project where you want to start with the ready-made demo and replace the content gradually.

The template package is just the template itself. It controls the look and layout, but it does not bring demo pages, components, modules, or ready-made records with it. If you install only that package, the site will not automatically look like the demo. For an experienced administrator, this can be an advantage because no extra data is imported. For a beginner, it is a common source of frustration.

Safe approach: first deploy the quickstart package on a test subdomain or local copy, study the module positions and page structure, and only then transfer that logic to the live site.

Server Settings and Permissions

The official documentation recommends checking the stable Joomla version, PHP and MySQL requirements, file upload size, memory limit, execution time, and cURL availability. This matters especially for quickstart: the installer unpacks a full site with demo data and extensions, so weak limits can cause it to hang during table creation or lead to an incomplete import.

• Make sure the quickstart archive is extracted before uploading it to the server if the package name includes an unzip first note.
• Create a separate database, or at least a separate table prefix, for the test installation.
• Make sure there is no old configuration.php or extra index.html in the installation root.
• After installation, check System - System Information - Folder Permissions to confirm that important folders are writable.
• Record which extensions are included in quickstart right away so you do not delete a module that the homepage depends on.

Content Preparation

Before installation, it helps to prepare not only your logo and colors, but also your course structure. For Language School, the meaningful fields are the real ones: program name, duration, level, schedule, enrollment deadline, description, requirements, and price or course status if you use SP LMS for commercial logic. Demo course cards need to be replaced with actual school data before launch, otherwise the site may look finished but still fail to help visitors choose a course.

Installation and Initial Validation Without Unnecessary Risk

For a new installation, use quickstart the same way you would use a regular Joomla installation. Upload the extracted files to the appropriate site folder, open the domain in a browser, complete the standard installation wizard, enter the database details, and create an administrator account. Do not use an obvious super user name. After the installation completes successfully, remove any leftover installation elements, sign in to the admin panel, and check that the homepage opens without system errors.

First Steps After Quickstart

1. Open the public side of the site and compare the top section with the demo reference: the logo, top bar, menu, hero section, course search button, and Course Programs block should all be in place.
2. Sign in to the admin panel and check System - Manage - Extensions to confirm that the key extensions are active.
3. Open Content - Site Modules or the equivalent module section in your version of the admin panel and find the Language Switcher, Find My Course Button, SP LMS Courses, Find Course Classic, and SP LMS Upcoming Events modules.
4. Check the main menu: Home, Language Programs, Admission, Who We Are, Events, Blog, and Contact should lead to real pages or clearly defined sections.
5. Open the template settings through Site Template Styles and make sure the correct style, shaper_languageschool - Default, is in use.

At this stage, do not rush into deleting all demo data in bulk. First, note which pages, modules, and positions are used on the homepage. Deleting a demo course can break a visible block if the module is configured for a specific category or course type. It is better to replace the content gradually: one course at a time, one event at a time, one block at a time.

If Only the Template Package Is Installed

After you install the regular package through System - Install - Extensions, the template will appear in the list of site templates, but there will be no demo pages. From there, you need to assign the template style, install or connect the required extensions, and create the pages, modules, and positions. This is where many users confuse a template with a ready-made site. The template package gives you the visual framework, but it does not build a course catalog on its own.

Practical conclusion: if you are not sure how to assemble the homepage manually, first set up quickstart on a test site and use it as your configuration map.

Configuring the Header, Menu, and Language Switcher

The header in Language School is built from several sources: the logo comes from Template Options, social links and contact details are managed through Helix Ultimate, the menu relies on the standard Joomla menu system, and the Find My Course button is a separate module. Because of this layered setup, you cannot configure everything in one place, but you can work through it in a clear sequence.

Logo and Core Identity

Open Extensions - Site Template Styles - shaper_languageschool - Default - Template Options - Basic - Logo. Upload the main logo, check the mobile logo, alt text, and height. For a school, a simple horizontal logo usually works best: an overly tall logo will increase the header height and may throw off the balance of the hero section.

If the site is multilingual, consider using a custom link for the logo. Helix Ultimate lets you configure the logo link, which is useful when different language versions have different landing pages. Test this on the public site, not just in the admin panel: the logo should take users exactly where they expect to go.

Social Links, Phone, and Address

The demo header includes a top bar with social icons, phone, and address. Social links are configured in Template Options - Basic - Social Icons, while contact details are configured in Contact Info. Remove placeholders, disable networks you do not use, and leave only the channels the school actually monitors. Empty links with a # symbol may seem minor, but to users they signal an unfinished site.

The Menu and the Course Search Button

The main menu is edited in Joomla, not in SP Page Builder. Its items should lead to program pages, the admission page, events, blog content, and contact information. The Find My Course button in the top area belongs to the Find My Course Button module, created through SP Page Builder and published in the menu position. If you do not need the button, you can disable it in the module list. If you do need it, make sure the link points to the current course page rather than a demo URL.

Language Switcher

The template includes a Language Switcher. If the site is single-language, you can simply unpublish the Language Switcher module. If the site is multilingual, first configure Joomla languages, content languages, menus for each language, and item associations. Only then should you enable the switcher in the live header. Otherwise, it may display a language choice while sending the user to an untranslated or incorrectly linked page.

Result check: open the homepage, a course page, an event page, and a blog post. The header should behave consistently, the menu should not wrap to a second line for no reason, and the course button should maintain clear contrast.

Courses, Program Search, and SP LMS: What to Configure First

The most product-specific part of JoomShaper Language School is not the hero image, but the educational program catalog. In the demo, it appears as course cards with duration, shift, level, discount, and a call-to-action button. To make this work on a real site, you need to configure data in SP LMS and the output modules, not just replace the text on the homepage.

Minimum Course Structure

Create course categories, then add the courses themselves. For a language school, the typical structure includes the language or track, level, duration, class format, schedule, requirements, description, enrollment deadline, teacher or instructor team, and cost or paid status if you use payment features. Not every field needs to appear on every course card, but the course page data should be complete enough to be useful.

The documentation describes SP LMS as a component for organizing an educational website: it includes courses, categories, lessons, quiz questions, results, certificates, teachers, speakers, events, reviews, and orders. In Language School, that means the template can function not only as a showcase, but also as a learning shell. At the same time, you should not promise users an advanced platform until you have verified the actual capabilities of your SP LMS version and configuration.

Course Modules on the Homepage

The Language School documentation separately lists SP LMS Courses and Classic Courses Layout. These modules can display courses with different visual styles and filter them by type: free, paid, featured, discounted, or popular. In a typical setup, it makes sense to first configure one clean program category, then feature 3 or 4 key courses on the homepage, while keeping the full catalog on a separate page.

What to Check in the Module

• The number of columns should not break the grid on a tablet or narrow laptop.
• The course limit should match the design, not dump every program onto the page at once.
• The course type should be chosen intentionally: featured for a showcase, popular for a site with real traffic history, discounted only if discounts are actually in use.
• Course titles should not be too long, or the cards will lose their visual rhythm.

Course Search

The Find Course Classic module is used in the demo for a polished course search section on the homepage. The documentation points out an important limitation: it indexes course titles. That means a user may get no result if they search for a word found only in the description. You should account for that in the UX: name courses so that the user's main search terms appear in the title or in a clearly labeled category.

For example, a conversational English course is better named Conversational English or another clear localized equivalent on your site than an internal code like Program A2 evening. Search should work in the language your audience uses, not the language of the administrator.

Events, Admission, and Built-In Pages

The template is not limited to a course catalog. Language School includes event logic, a dedicated admission page, Registration, Coming Soon, About, Login, 404, and blog pages. This is useful for a school where course enrollment is tied to open lessons, exam dates, webinars, trial classes, and news updates.

Events and Meetings

SP LMS Upcoming Events displays upcoming events. On a language school website, those may include intro lessons, speaking clubs, open houses, enrollment consultations, or exam prep workshops. For each event, check the title, date, time, speaker, location, map, or online link if those are used in your version. If an event has already passed, it should not continue to look like an upcoming one.

The changelog shows that older versions included fixes for event maps, expired events, and course data display. That does not mean those issues are necessarily present on your site, but it does show you what to test after updates: dates, maps, course display, cart behavior, or inquiry flows if those features are in use.

The Admission Page

The admission page in this template is more than a polished school description. It should explain the enrollment process clearly: which programs are open, what requirements apply, how to choose a level, where to submit an application, and what happens after the first contact. Replace demo statistics with real data or remove them. Metrics such as student and teacher counts only feel convincing when they reflect reality.

Registration, Coming Soon, and 404

The built-in pages are useful, but they should not be left with demo copy. The registration page should explain what exactly the user is submitting and how the school handles that data. Coming Soon can be useful when launching a new course, but it is not a substitute for the site's offline mode. The 404 page should guide users back to the program catalog, schedule, or contact information rather than simply telling them the address was not found.

Module Positions and Layout Builder Without the Chaos

Joomla templates often break not because of a code issue, but because a module is assigned to the wrong position or menu item. In Language School, this is especially noticeable: the top bar, course button, bottom sections, footer, subscription forms, and course lists all depend on specific positions.

How to Read Positions

The Language School documentation includes a separate diagram called Layout - Default Modules Positions. It shows the main positions used by the current template. Helix Ultimate lets you modify rows, columns, grid sizes, and add positions through Layout Builder. But every change should be tested on the homepage, a course page, an event page, and a blog post.

The setting for side modules in detail article view is especially important. The documentation notes that to display a right or left sidebar in a single article, you should check Helix Options - Blog - Details - Disable Modules. If that option is enabled, a module may be published correctly and still not appear on the detail page.

Bottom Area and Footer

The lower part of the quickstart layout is built from several rows and positions. The footer uses modules in footer1 and footer2, while the copyright area is edited in Template Options - Basic - Footer. If you change the footer structure, do not merge everything into one HTML block: footer navigation is better kept as a menu module, the logo as a separate module or setting, and contact details as a clear standalone block.

Menu Assignment

Every module has a menu assignment. This is often more important than the position itself. A module may be published in the correct position but still fail to appear on a course page if it is assigned only to the homepage. And the reverse is also true: a module may unexpectedly appear in the blog if it is assigned to all pages. On an education website, it is usually practical to split modules into three groups: global modules for the header and footer, homepage modules, and topic-specific modules for courses and events.

Practical Scenario: Rebuilding the School Homepage After the Demo Install

Below is a real-world scenario that works well as a starting point after installing quickstart. The goal is to turn the demo homepage into a functioning language school homepage without breaking the template structure or deleting connected modules too early.

Goal

Create a homepage where visitors see the school logo, a clear hero section, a button leading to courses, 3 or 4 current programs, course search, a short school introduction, an admission block, the nearest upcoming event, and a correct footer with contact details.

Preparation

• Create a backup of the test installation.
• Prepare the text for the hero section, school intro, course cards, and admission section.
• Create at least one course category and several courses in SP LMS.
• Prepare real contact details, address, social links, and a working email address.
• Decide whether you want the language switcher enabled in the first release.

Configuration Steps

1. Replace the logo in Template Options and check its height in desktop and mobile view.
2. Update the contact information and disable any social links you do not use.
3. Open the homepage in SP Page Builder and replace the hero text with a short question or a clear student benefit.
4. Configure the Find My Course Button module so it links to the program catalog page.
5. Add real courses in SP LMS and assign them categories, levels, and schedules.
6. Open the SP LMS Courses or Classic Courses Layout module and limit the output to only the programs you want featured.
7. Check the Find Course Classic module: enter part of a course title and confirm that the search returns a result.
8. Update the admission block: requirements, enrollment steps, contact channel, and realistic benefits.
9. Configure the footer: logo, menu, contacts, copyright, and links to legal pages.
10. Clear the Joomla cache and browser cache, then check the page while logged out of the administrator account.

Result Check

After configuration, open the homepage in a standard browser, in private mode, and at mobile width. Test three actions: the user can navigate to courses, find a course by name, and find a contact method to submit an inquiry. If those three actions work, the homepage is already doing its main job. After that, you can move on to finer visual polishing.

A Common Issue That Gets in the Way

If the course cards do not update after you change the data, check not only SP LMS but also the output module: selected course type, limit, category, menu assignment, and publication status. If search does not find the course, check the course title, because the demo search logic is based on titles.

Practical Use Cases for Different Educational Scenarios

This section is not here for abstract inspiration. It shows how the template's confirmed building blocks can be applied to different education workflows. Every example is based on real components: courses, events, admission, blog, search, SP Page Builder sections, and module positions.

Offline School Website With Group Enrollment

Use the course cards as a showcase for groups: language, level, session, duration, and start date. In the hero section, focus on helping users choose a program, and keep Find Course Classic on the homepage. The validation is simple: a prospective student should be able to understand within a minute whether the right level exists and where to click to enroll.

Conversational Practice Club

For a club format, events and the schedule matter more than a long catalog. Move Upcoming Events closer to the first screen, and keep courses as a secondary block. The admission page can be repurposed into a participation rules page: meeting format, group size, level requirements, and the coordinator's contact details. Make sure past events do not still look active.

Exam Prep Center

Here, the focus should be on prep programs, enrollment deadlines, and pages with requirements. The blog can be used for exam-related content, and the admission page can explain the registration process. Do not overload the homepage with events if the main goal is to help users quickly choose a prep course and contact the administrator.

Multilingual School Website

Language School is visually well suited to a language-focused project, but technically, multilingual support is still a Joomla task. Configure content languages, menus, page associations, and Language Switcher before placing the switcher in the header. For SP Page Builder pages, check language assignment, and for SP LMS, verify whether course and category titles are translated if your configuration supports that.

Safe Improvements for Design and Localization

The Helix Ultimate documentation recommends using Template Options, the custom CSS field, or a separate custom.css file instead of editing the main template CSS files. That is the right approach for Language School: updates can overwrite template.css, while small edits in custom.css are easier to disable and test.

CSS for a Cleaner Course Button

If the Find My Course button feels too dominant or does not fit your menu width, first try the module and template settings. If you need a small visual adjustment, add CSS through Template Options - Custom Code - Custom CSS or through a separate custom.css if the change is more than a few lines. The classes on your site may differ, so inspect them in the browser before applying the snippet.

.sp-menu-item .find-course,
.find-course-button {
  letter-spacing: 0;
  min-width: 150px;
  text-align: center;
}

@media (max-width: 767px) {
  .find-course-button {
    width: 100%;
    margin-top: 12px;
  }
}

After saving, check desktop, tablet, and mobile view. If the button looks worse or the class does not match, remove the snippet. Do not edit template.css directly: after a template update, that change may disappear and become harder to track down.

Language Overrides Instead of Editing Files

If you need to replace a static system label, use Joomla's standard language overrides instead of editing extension files. This is especially important in a template with courses and a language switcher: the text may come from a module, an SP Page Builder section, a Joomla language string, or an SP LMS setting. First identify where the string comes from, then change it in the safest way available.

Custom Code Without PHP

Helix Ultimate lets you insert code before the closing head, after body, and before the closing body, but the documentation warns against using PHP inside template options. For Language School, that means verification meta tags, CSS, analytics, and lightweight JS are acceptable if you understand the impact, but course logic, payments, and form behavior should not be patched with random code inside the template.

Validating the Site After Configuration

Validation should not stop at "the page opens." It should follow user scenarios. A language school website has several key paths: find a course, understand the schedule, open the details, review enrollment terms, contact the administrator, view an event, read a news post, and switch language if the site is multilingual.

Frontend Validation

• The homepage opens without visible demo placeholders or broken images.
• The hero section answers the visitor's question instead of simply repeating the school name.
• Find My Course leads to the current catalog or an anchor with the search interface.
• Course Search finds a course by title and does not imply description-based search if that is not configured.
• Course cards display useful parameters: level, duration, schedule, or another key selection criterion.
• The admission page explains the enrollment process and does not contain demo statistics.
• Events do not show outdated dates as if they were upcoming.
• The footer includes working contacts, menu links, and legal pages.

Administrative Validation

In the admin panel, check the module list, Template Styles, SP LMS data, menus, and access permissions. If editors will be working on the site, do not give them more permissions than necessary. For a content manager, access to courses, events, articles, and some SP Page Builder pages is often enough. Layout Builder and custom code are better left to an administrator or developer.

Speed and Responsiveness

The template is visually rich: images, sections, modules, page builder content. Do not enable a preloader as a way to "speed up" the site: it can only hide delay, not solve the problem. Optimize images, remove unused sections, review Joomla cache settings, and test CSS/JS compression carefully if you use additional optimization tools. After any optimization, retest course search, menu behavior, events, and forms.

Troubleshooting: What to Do If the Template Does Not Look Like the Demo

Problems with JoomShaper Language School usually appear at the boundary between several layers: quickstart did not install completely, a module was published in the wrong place, SP LMS has no data, a page builder page was changed, cache is showing an old version, or the template options differ from the demo. Below is a practical symptom map.

Quickstart Hangs or Fails to Complete Installation

Symptom: the installation stops during table creation, hangs for a long time, or never reaches the final confirmation. Possible causes include weak PHP limits, unsuitable database settings, incomplete file upload, or a conflict in the local server environment.

Check the requirements, memory limit, execution time, upload size, cURL availability, and folder permissions. If the installation is running in a local environment, adjust PHP settings and restart the server. Only use questionable SQL engine changes as temporary troubleshooting measures if they are documented and you fully understand what you are doing. On a live site, it is better to contact your hosting provider than to modify installation files blindly.

The Homepage Does Not Match the Demo

Most often, the regular template package was installed instead of quickstart, or the demo page was not assigned as the homepage. Check which package you installed, which menu item is marked as the homepage, whether the homepage modules are published, and whether the correct template style is active. If you used the template package, this behavior is expected: the demo content has to be built manually.

Courses Are Not Displayed or Search Returns Nothing

Check whether published courses exist in SP LMS and whether the categories, course type, and limit are selected correctly in the module. For search, keep the title-based limitation in mind. If a user searches for "evening group" and that phrase is not in the course title, the module may not return the expected result. The fix is to rename the course more clearly, configure categories, or adjust the search hint text.

The Language Disappeared or an Extra Switcher Appeared

If the site is single-language, unpublish the Language Switcher. If the site is multilingual, check the installed languages, content languages, language plugins, menus for each language, and page associations. Do not disable language plugins on a multilingual site just to remove the language code from the URL until you understand the consequences.

Sidebar Modules Are Not Visible on Article Pages

Check not only the position and menu assignment, but also the Helix Options setting for detail view, where module disabling can affect single articles. If a module is visible in category view but disappears in detail view, that strongly suggests the problem is not publication status, but the template's output logic.

Part of the Page Broke After Adding Custom CSS

Remove the latest change from Custom CSS or temporarily disable custom.css. If everything returns to normal, the issue is in the selector or media condition. Do not stack more rules on top of the old ones in hopes of "overriding" the conflict. First identify the exact selector, then make a small change and test it on several pages.

Who JoomShaper Language School Is For, and When It Makes Sense to Wait

This template is a strong option if you need a quickly deployable language school website with courses, events, an admission page, a blog, and a visually ready homepage. It is especially useful for projects where the administrator is comfortable working in Joomla and the editor needs a convenient visual way to update pages and content blocks.

It makes sense to pause if you have not yet decided whether you need the LMS layer, have not prepared the course structure, are unsure whether the site will be multilingual, or plan to migrate a large existing website without a staging environment. In those cases, deploy the demo first, map the modules, and estimate the scope of the migration.

Before you download JoomShaper Language School, check three things: whether the quickstart scenario fits your needs, whether SP LMS covers your educational workflow, and whether you have someone who can maintain the modules, menus, Template Styles, and SP Page Builder setup after launch. It is better to start the download after that review, not before.

When JoomShaper Language School Is the Right Choice

JoomShaper Language School makes sense if you want to quickly launch a language school website with a ready-made visual rhythm, program catalog, course search, events, an admission page, and a clear Joomla architecture. Its strength is that the design and education-related blocks are already connected rather than provided as isolated pieces.

The best results come when you install quickstart on a staging site, study the structure, replace demo data with real courses, carefully configure the header and footer, test modules across different pages, and only then move the solution into production. In that setup, the template becomes not just a "pretty page," but a working reference and learning shell for the school.

If that is exactly the scenario you need, move to the download step after the content is prepared and the test installation is complete. If the project requires a different LMS model or a fully custom design, use this guide as a comparison checklist and choose the solution based on real requirements, not on the first impression of the demo.

Video for Configuring JoomShaper Language School

This video complements the guide: a product-specific walkthrough. Open it after the basic setup to compare the interface and the sequence of actions.