JoomShaper Themis - Joomla Template

Configuring JoomShaper Themis for a Law Firm Website

JoomShaper Themis is a Joomla template built for legal practice websites, but it works best when you treat it not as a finished picture, but as a set of connected layers: the Quickstart demo, Helix Ultimate, SP Page Builder Pro pages, module positions, menus, the appointment form, and separate pages for services, cases, the blog, and contacts. This guide walks through the practical path: what to check before installation, which package to choose, how to adapt the homepage, where to change the inquiry form, how to avoid losing modules, and how to verify the result on a real site.

This material does not repeat the template's short product description. The more important question here is different: how to turn a law-firm demo into a working site with a clear structure, safe configuration, and verifiable results. That is why every section is tied to a real Joomla administrator task: choosing an installation method, setting up the homepage, assigning modules, replacing demo content, checking the mobile menu, connecting the consultation form, and preparing the site for updates.

The guide uses careful wording wherever behavior depends on the Joomla version, the installed extensions, or the specific Themis package. If you have only the standalone template installed, some demo pages and modules will have to be created manually. If you install Quickstart, you will get the demo look much faster, but you still need to replace the demo data, images, contacts, and legal copy with your own.

The core idea behind configuring Themis is not to edit everything in one place. The outer framework is usually controlled by the template and Helix Ultimate, pages are built in SP Page Builder Pro, navigation lives in Joomla menus, and individual content blocks may be modules. When those layers are kept separate, the site is much easier to maintain, update, and troubleshoot.

When Themis Fits a Legal Website, and When Another Approach Makes More Sense

Themis is a strong fit when you need a website for a lawyer, law firm, legal advisory office, practice focused on specific areas of law, or a related corporate project where trust, service structure, and a quick path to inquiry matter. The official materials describe the template as a solution for lawyers, attorneys, advocates, solicitors, and law firms, while also allowing use for business consulting, financial services, and corporate websites. That matters because Themis is not limited to a one-page brochure site, but its visual language is clearly built around legal services.

If the project already has a strong brand system, a complex client portal, CRM integration, a document catalog, a private knowledge base, or a nonstandard intake process, Themis may only serve as a starting shell. You will still need to design additional components and workflows. The template does not replace legal expertise, does not write content for the firm, and does not guarantee leads. What it gives you is structure, pages, and a visual foundation that still needs to be filled with real proof of competence.

For a smaller legal website, Themis is especially useful in three situations. First, when you need to assemble a demo-based structure quickly and then replace the text, images, and contacts. Second, when the editor wants to change sections visually through SP Page Builder Pro instead of editing PHP files. Third, when the site needs several standard sections: practice areas, cases or portfolio, team, blog, pricing, consultation form, contacts, and utility pages.

When might the template not be the right choice? If you need a fully minimalist site without a page builder, if the company deliberately avoids SP Page Builder, if the project is being built on a different template framework, or if maximum lightness without demo components is the priority. In those cases, it makes more sense to consider plain Helix Ultimate, another Joomla template, or a custom build based on Joomla's standard capabilities.

The practical rule is simple: if you need a ready-made legal structure and are comfortable working with Helix Ultimate plus SP Page Builder Pro, Themis saves time. If all you need is an empty framework with full control over every file, the template may be more than you actually need.

What Makes Up the Template's Working Structure

Themis has several layers you need to understand before you start configuring it. The official product page and documentation connect the template with Helix Ultimate and SP Page Builder Pro. Helix Ultimate handles the overall framework: template styles, the layout builder, header, footer, module positions, typography, colors, logo, custom code, and behavior across screen sizes. SP Page Builder Pro handles pages, sections, addons, and visual content editing. Joomla handles menus, articles, modules, languages, access rights, cache, and system settings.

In the Quickstart demo, JoomShaper indicates the use of Joomla core modules and additional extensions: SP Page Builder Pro, SP Simple Portfolio, SP Easy Image Gallery, Articles - Latest, Articles - Categories, Custom HTML, Smart Search, Menu for offcanvas, Breadcrumbs, and Custom. That does not mean every one of those elements is required on your site. But it does explain why, after installing Quickstart, you see a ready-made demo structure, while after installing only the template pack, you do not.

The standalone template is not a demo website. The documentation explicitly separates the Template Pack from the Quickstart Pack: the template controls the look and layout, but it does not include modules, components, or demo content. That is why manual installation works well for an existing site that already has content and menus, but it requires more setup: you need to create pages, assign modules, check positions, and rebuild SP Page Builder pages if you need them.

Quickstart is a complete Joomla website with demo data and settings. It cannot be installed into an existing Joomla site through the extension manager, because it is not a regular extension but a full installation package. This option is best used on a clean test domain, subdomain, or local environment. Once you have reviewed the structure, you can decide whether to migrate the site as a whole, recreate the settings manually, or simply use the demo as a reference.

The most common mistake with templates like this is trying to find every setting in one interface. A page title may live in a menu item, the hero section in SP Page Builder, the logo in template options, and a footer block in a regular module. Once you identify which layer an element belongs to before editing it, configuration becomes predictable.

Preparation Before Installation: What to Check Without Rushing

Before installing Themis, it is worth preparing not just the archive, but the working strategy. For a Joomla template, that matters more than it does for a simple extension: a template affects the appearance of the entire site, module positions, menus, styles, and sometimes component output overrides. If you install Themis on an already live site without a test copy, you may end up with unexpected changes in the header, footer, sidebars, and article pages.

Start with a backup. For an existing site, create a full snapshot of the files and database, or better yet, deploy a copy to a staging address. For a new project, prepare a clean database and a separate folder or subdomain for Quickstart. JoomShaper's documentation emphasizes that Quickstart requires a fresh environment and database because it installs as Joomla itself. This is not the kind of archive you upload through System or Extensions inside an already configured admin panel.

Next, check the server parameters. JoomShaper lists PHP, MySQL, upload file size, memory limit, execution time, cURL availability, and disabled Magic Quotes GPC in its technical requirements. Not all of those settings are visible in the Joomla interface, so some of them may need to be checked in the hosting panel or with support. If the installation freezes, pages save with errors, or SP Page Builder behaves inconsistently, weak server limits are often one of the first causes.

Also decide in advance what to do about demo photos. The Themis documentation warns that images from the live preview may not be included in the package due to licensing, and Quickstart may contain placeholders instead. For a legal website, that is critical: random stock photos of lawyers look unconvincing. It is better to prepare legitimate images of your team, office, documents, consultations, and relevant illustrations ahead of time. If you do not yet have your own photos, use legal stock assets and keep track of the licenses.

• Check whether you need Quickstart or whether the standalone template is enough.
• Create a staging environment if the site is already public.
• Prepare the database, file access, and a backup.
• Check PHP limits, upload size, and cURL availability.
• Gather real legal copy, contacts, photos, and a list of practice areas before editing the demo.

Short version: preparation saves more time than trying to repair the site afterward. Themis gives you many ready-made blocks, and that is exactly why it is best introduced through a test copy and a plan for replacing demo content.

Installation: Quickstart, Template Pack, and the First Check

The package you choose determines the entire setup path that follows. If you want a copy of the demo with its ready-made structure, choose Quickstart and install it as a clean Joomla instance. If the site already exists and you only need the visual template, use the Template Pack. In both cases, do not jump straight into design work after installation. First, make sure the admin panel opens, the template appears in site styles, the Helix Ultimate system plugin is enabled, and the pages and modules are not throwing errors.

Quickstart for a New Site or Test Environment

Quickstart is useful when you want to see the full Themis setup in action: homepage variants, practice pages, consultation booking, portfolio, blog, menu, and footer. Extract the archive, upload the files into a separate folder, create a database, and go through the standard Joomla installer. During setup, use a unique super user name instead of an obvious login. Once installation finishes, sign in to /administrator, check for updates, verify that the required extensions are enabled, and make sure the installation folder has been removed if Joomla did not finish that step automatically.

After installing Quickstart, open the public side of the site and compare it to the expected structure, not to every pixel of the live demo. If you see placeholders instead of photos, that is not necessarily an error. In Themis, that can be a normal licensing-related limitation that you need to solve with your own images. If pages do not open, check the menu, SEF settings, file permissions, and system requirements.

Template Pack for an Existing Site

With a manual template pack installation, you install the template as a Joomla extension, assign the style as the default or to specific menu items, and then configure module positions by hand. This is the safer route for an existing content-filled site, but it does not automatically create Themis pages. If you expected to see the demo reproduced exactly, that will be disappointing, but it is not a package defect. The documentation clearly warns that the template pack does not include components, modules, or demo pages.

The first check after a manual installation should be brief: open the homepage, an article, a blog category, the contact page, and the mobile menu. If some blocks are missing, check the module positions and menu assignments. In Joomla, modules can be published but still not appear on the right page because of the Menu Assignment tab or an unsuitable position.

Do not install Quickstart over a live site. If you want to reuse its settings, install Quickstart alongside it on a test address and use it as a visual and technical reference.

The Homepage: How to Choose Between Default and Classic

Themis includes two homepage variations built with SP Page Builder Pro. Default Home emphasizes a large hero block, contact information, a consultation call to action, practice areas, testimonials, and statistics. Classic Home brings the booking form closer to the first screen, then follows with facts, awards, and the team. The difference is not just visual. These are two different trust-building flows: either tell visitors about the firm and its practice areas first, or give them the inquiry form right away.

Default Home works better when the law firm sells more complex services and the visitor needs to understand the firm's specialization quickly. For example, if the firm handles many practice areas such as family law, immigration, bankruptcy, and corporate contracts, it makes sense to highlight areas of practice, cases, and overall experience first. Classic Home fits a consultation-focused flow, where the visitor already understands the problem and wants to submit an inquiry quickly.

The homepage choice is made through Joomla menus and SP Page Builder pages. Themis documentation shows that the homepages live in the menu, while the pages themselves are created in SP Page Builder Pro. So the sequence is this: first find the relevant page under Components -> SP Page Builder Pro -> Pages, then check the menu item assigned as the homepage. If you change only the builder page but the menu still points to another item, the public result will not change.

How to Adapt the Hero Section Without Breaking the Structure

Start with three things: the headline, the action, and the trust signal. The headline should not say "best lawyers" but should clearly define who the firm serves and what kinds of matters it handles. The button should lead to the consultation form, contacts, or another relevant section. The trust block should not rely on invented numbers, but on real indicators: years of practice, areas of specialization, membership in professional organizations, publications, testimonials, and successful case types, as long as all of that can be shown legally and ethically.

Do not remove sections at random. In SP Page Builder, it is better to duplicate the page or save a copy of the sections first, then replace the text and images. If spacing disappears after editing, the button becomes hard to read, or a section breaks on mobile, check the column settings, background, typography, and responsive options for that specific section. A visual builder speeds up the work, but it does not remove the need to test across screen sizes.

Practice Pages, Case Studies, and the Blog as the Foundation of Trust

A legal website rarely persuades visitors with a hero block alone. People look for proof: what the firm does, what kinds of problems it understands, how it explains complex topics, and whether the consultation can be trusted. Themis gives you several ready-made zones for that: practice areas, service listing, service detail, portfolio, blog variations, testimonials, and pricing layouts. Use them not as decorative sections, but as a system of evidence.

Practice Areas and Services

The practice list in Themis presents areas of legal work and may include quantitative or status elements. If you do not have verified numbers, do not leave the demo figures in place. It is better to replace them with clear categories such as "family disputes," "inheritance matters," "contract work," "immigration issues," or "business protection." Prepare a separate page for each practice area: the client's problem, what the firm does, what documents are usually required, how the consultation works, and when it is better to seek help early.

The official description of the Service Detail Page mentions detailed service information and a tabbed system. That is a strong format for legal topics: tabs can separate "when to contact us," "what to prepare," "how the process works," and "frequently asked questions." But tabs should not hide critical information. On mobile, a visitor may scroll only through the first block, so the core value should appear before the tabs.

Cases and Portfolio

Themis is tied to SP Simple Portfolio for displaying portfolio items or case studies. For a legal website, the word "portfolio" should be used carefully: not every matter can be disclosed publicly, some information is protected by confidentiality, and results cannot be promised. Instead of loud "wins," use anonymized case studies: the starting situation, the type of work, the legal complexity, the process, and the outcome described in acceptable terms. If details cannot be disclosed, build a "typical situations" section without personal data.

The Blog as Support for SEO and Trust

The official Themis description mentions two blog variants: a card based grid layout and a section-wise list view. For a legal website, the blog is useful when it answers client questions instead of simply publishing firm news. Organize materials by practice area, add clear categories, and configure sidebar modules such as popular posts or categories. Themis documentation for Blog View notes that the blog page heading and subheading are set through page settings, while sidebar modules can be configured by position on the page.

Do not review the blog only visually. Open an article card, a category page, a post with a long headline, a post without an image, and the search page. If sidebar modules do not appear in the article detail view, go back to the Helix Blog Details settings and check the option that disables or enables modules in the detail view.

Appointment Form: How to Make the Consultation Form Work Instead of Looking Like a Demo Block

Appointment Form is one of the most important elements in Themis, because a legal website needs to turn interest into an inquiry. Themis documentation says the form is built with the Form Builder addon in SP Page Builder Pro and is edited through Components -> SP Page Builder Pro -> Pages -> Appointment. That means the form is not a separate Joomla booking component with a calendar in the traditional sense. It is a builder page with a form that needs to be adapted to a real intake workflow.

Do not start with the button color. Start with the fields. For a legal consultation, you usually need the person's name, contact details, the area of concern, a convenient time for communication, and a short description of the situation. Do not ask for too much information at the first step. The more sensitive the information, the more carefully the form should be designed. If the visitor is describing a legal issue, it is worth adding a short note nearby explaining that they should not send unnecessary personal data before an agreement or initial contact is established.

In Form Builder, the email recipient is especially important. SP Page Builder documentation states that Recipient Email is a required field for receiving form responses. Check the address, the email subject, the reply-to address, the required fields, and the field widths. If the form looks great but the emails do not arrive, the visitor will not know the inquiry was lost. That is why after every change you should submit a test request and check not only the inbox, but also spam, the hosting system log, and Joomla mail settings.

How to Test the Form After Configuration

1. Open the Appointment page in SP Page Builder Pro and locate the Form Builder addon.
2. Check the labels, required fields, the service area selector, and the date or time fields if your version uses them.
3. Set a working Recipient Email and a clear email subject.
4. Save the page, clear the Joomla cache and the template cache if it is enabled.
5. Submit a test request from a normal browser, then check whether the email arrived and how the message looks.

To improve lead quality, add microcopy next to the form: how long a response usually takes, what information to prepare, and which issues are better handled by phone right away. This is not a technical Themis setting, but it is exactly what makes the form genuinely useful. A polished-looking form with no clear expectations often produces fewer inquiries than a simple form with clear rules.

Module Positions, Offcanvas, and Menus: Where Blocks Most Often Go Missing

In a Joomla template, module positions are not a minor detail. They determine where menus, breadcrumbs, side blocks, the footer, search, offcanvas, and additional zones above or below the component appear. Themis documentation notes that the main layout module positions are shown in a screenshot, and the Helix Ultimate Layout Builder lets you move positions and change column widths on the Bootstrap grid. It also points out additional positions that may not appear in Layout Builder, but are used to display modules above and below the component area.

If some blocks are not visible after installing Themis, follow the chain: the module is published, the position exists, the module is assigned to the correct menu items, access is allowed for the right user group, and the cache is cleared. Joomla may hide a module not because the template is broken, but because the module settings point to a different menu item or access level.

Offcanvas for the Mobile Menu

Themis documentation for the Mobile Menu says that the items inside the mobile menu come from modules published in the offcanvas position. That is an important practical detail. If the menu is visible on desktop but opens as an empty panel on mobile, do not check SP Page Builder first. Check the menu module: it must be published in offcanvas, assigned to the correct pages, and available to public access. Helix Ultimate also has menu and offcanvas behavior settings that are worth checking after the module is published.

Sidebars in Article Views

The Layout - Module Positions documentation includes a specific warning: to display modules in the right or left sidebar on the Single Article Detail view, you need to change the setting in Helix Options -> Blog -> Details -> Disable Modules: OFF. This is a classic example of a problem that looks like "the module disappeared," when in reality it is being disabled by the article detail setting. For a legal blog, this matters: popular posts, categories, a consultation block, and contact information should remain visible in the article view if users need them.

Detailed Post-Installation Configuration

After installation, do not try to perfect every block immediately. Start with the settings that affect the whole site. That order reduces the risk of carefully tuning one section and then changing the global typography, header, or color scheme and ending up with unpredictable results.

Basic Template Settings

Open the Themis style in the Joomla admin panel through the site templates section. Depending on the interface version, the path may be labeled slightly differently, but the meaning is the same: you need the site template style and template options. Check the logo, favicon, footer text, header parameters, menu, typography, colors, and custom code. Themis documentation describes the template as one that supports background, fonts, colors, and logo settings, so these are the parameters you should lock in before editing pages.

If the site is multilingual, do not copy one style across all languages without checking. In Joomla, a template style can be assigned to specific menu items. That is convenient if the Russian and English versions use different menus, but risky if you edit only one style and forget the second. After changing the logo or footer, open both language versions and verify where the style was actually applied.

SP Page Builder Page Settings

Next, move to the builder pages: the homepage, appointment, contact, service pages, blog landing page, and any other demo pages you plan to keep. On each page, check the title, alias, SEO fields, publication status, categories, and menu connections. If a page exists in SP Page Builder but does not open publicly, the issue is often a missing menu item or the wrong alias. If a page opens, but not the one you edited, check the menu item, because the homepage may be pointing to a different object.

Modules and the Bottom of the Site

The footer on a legal website should contain more than just a copyright notice. It should include contact details, an address, links to practice areas, terms for handling inquiries, a map, or social links if they are actually used. Some of the footer may be managed through Helix settings, and some through modules in footer positions. Helix Ultimate documentation describes the ability to output the copyright notice through footer settings or publish custom modules in footer positions. In practical terms, that means: first identify where a specific piece of text comes from, and only then edit it.

Cache, Responsiveness, and a Safe Rollback

After a series of changes, clear the Joomla cache, browser cache, and the cache of any optimization extensions you have installed. Check the site in a private window. If the result is not what you expected, undo the last change first instead of changing everything at once. In SP Page Builder, it helps to save copies of sections; in Joomla, to document module changes; and for CSS, to keep comments and make small reversible snippets.

Checkpoint Before the Next Edit

After each major change, note three things briefly: which section was changed, where the setting lives, and which public URL was checked. This kind of log is not for reporting. It just helps you quickly see what to revisit if a problem shows up a day later in the menu, the form, or the mobile layout.

Good post-installation setup leaves a clear trail: what was changed, where it was changed, how to verify it, and how to roll it back. That matters especially when the site will be maintained by someone other than the person who launched it.

Practical Scenario: Building the Homepage for a Law Firm

Imagine this task: a law firm has four practice areas, a team of three specialists, several anonymized case studies, a blog, and an initial consultation form. The goal is to build a homepage that does not look like a demo and leads the visitor toward a clear action.

Goal and Preparation

The goal: within the first screen, the visitor understands the firm's specialization, sees the path to a consultation, and can move to the relevant practice area. Before configuration, prepare the hero copy, the list of practice areas, real contact details, photos or legally usable images, short case descriptions, the form recipient address, and the site menu. If you are using Quickstart, create a copy of the homepage in SP Page Builder first so you preserve the original structure.

Configuration Steps

1. Choose the homepage variation: Default to emphasize practice areas and trust, Classic to emphasize the appointment form.
2. In SP Page Builder, replace the hero headline with a specific statement of the firm's positioning and verify the consultation button.
3. In the practice areas block, keep only the real directions and remove unverified demo numbers.
4. Create or edit the service pages so each card leads to useful content instead of an empty demo page.
5. Configure the Appointment Form: fields, required settings, recipient address, email subject, and test submission.
6. Check the menu: homepage, practice areas, case studies, blog, team, contacts, consultation.
7. Check the mobile menu through the module in the offcanvas position.

Verifying the Result

Open the homepage as a regular visitor. Within 10 seconds, it should be obvious what the firm does, where to click for a consultation, and which practice areas are available. Then test the full path: homepage -> practice area -> form -> test inquiry. After that, check the mobile view, because legal inquiries often come from a phone after a search or recommendation.

One nuance: if demo photos, demo names, and demo testimonials are still present in Quickstart, the site may look technically complete but weak in terms of trust. Do not check only the layout. Check the authenticity of every block. In legal topics, this stands out especially clearly: a random team photo or invented statistics reduce trust faster than an empty block would.

Practical Ways to Use Themis Beyond a Standard Brochure Site

Themis does not have to be used only as a "law firm site with a form." Its ready-made pages and the Helix Ultimate + SP Page Builder Pro stack make several realistic scenarios possible. What follows is not a list of imaginary features, but actual ways to use the template's confirmed elements: homepage variations, practice areas, service details, blog layouts, appointment form, portfolio, and built-in pages.

A Site for a Narrow Practice

If the firm focuses on one area, such as family disputes or immigration matters, do not spread the homepage across ten services. Use practice areas as a map of sub-tasks: consultation, documents, negotiations, court, and post-decision support. Publish blog materials around common questions, and tie the consultation form to specific types of requests. The result is easy to test: the visitor should not have to guess whether the firm handles their issue.

A Legal Department or Business Consulting Website

For a B2B scenario, Themis can be adapted for contract work, compliance, transaction support, and ongoing legal service. In that case, pricing layouts are better used not as "prices," but as service packages or support levels, if that matches your practice. The key is not to promise a fixed result or turn legal services into a retail store. Packages should explain the scope of work, the communication format, and the limits of responsibility.

A Knowledge Base Entered Through the Blog

The two blog variants make it possible to build not just a news feed, but an entry point into reference materials. Use categories by area of law, show popular articles in the sidebar, and add internal links to the consultation form. This scenario is useful if the site gets search traffic for specific questions. The result check is simple: an article should lead to a relevant service, not to a generic "contacts" page with no context.

A Portfolio of Anonymized Cases

Themis combined with SP Simple Portfolio works well for case studies if you preserve confidentiality. Each card can show the type of situation, the complexity, the approach, and the acceptable outcome. If details cannot be disclosed, make the case more educational: "how work on this type of matter is usually structured." That format supports trust without violating client privacy.

Safe Enhancements: CSS, Translations, and Small Changes Without Update Risk

JoomShaper notes that Helix Ultimate and SP Page Builder provide visual controls for many CSS properties, but sometimes you still need custom CSS, JavaScript, meta tags, tracking, or verification code through dedicated fields in the template settings. In Themis, this is the safest path for small changes: you are not editing Joomla core, template files, or extension files directly, but adding a small reversible layer.

A CSS Class for a Note Next to the Consultation Form

If you need to highlight a short notice or response expectation next to the Appointment Form, add a separate text block in SP Page Builder and assign it a custom CSS class such as themis-appointment-note. Then add the CSS through the custom code area in the template settings or through the template's recommended custom CSS mechanism. A snippet like this does not depend on Themis internal classes and is easy to remove.

.themis-appointment-note {
  border-left: 4px solid #c59a4a;
  background: rgba(197, 154, 74, 0.08);
  padding: 16px 18px;
  margin-top: 18px;
  font-size: 15px;
  line-height: 1.6;
}

.themis-appointment-note strong {
  color: #2f3546;
}

Verification: open the appointment page, make sure the block does not break the grid on mobile, then clear the cache. Rollback: remove the CSS and take the custom class off the block. This is a small visual change, not an intervention in the form logic.

Translating Template Strings

Themis documentation on Template Translation explains how the template language files work and reminds you that some phrases may come from other components, including SP Page Builder. On a production site, it is better not to edit the English source file as your only source of truth. Use language files with the proper prefix or Joomla language overrides when you need to replace a specific string. Save files in UTF-8 without BOM and check quotation marks in the values.

If a translation does not apply, first check where the string comes from: the template, Joomla core, SP Page Builder, SP Simple Portfolio, or another extension. That is faster than searching through every file. After changing the language, clear the cache and check the page on the public side.

When You Should Not Add Code

Do not add JavaScript for critical form logic unless you understand exactly how it affects submission. Do not edit `template.css` or component files directly if the change may disappear on update. Do not hide form errors with CSS. If an error message looks ugly, first find out why the form is not submitting, and only then improve its appearance.

Checking the Result Before Publishing

Once everything looks finished visually, review the site as an editor, an administrator, and a regular visitor. Themis gives you ready-made pages, but site readiness is defined not by the presence of attractive blocks, but by how well they work together. Start with navigation: homepage, practice areas, service page, case study, blog, article, consultation form, contacts, search, and the mobile menu.

Check the content. Remove demo names, demo numbers, third-party photos, empty links, Latin placeholder text, nonexistent practice areas, and unverified testimonials. Pay special attention to legal claims. You cannot promise guaranteed results or use wording that misleads the visitor. If you mention experience, memberships, certifications, or publications, they must be backed by real information.

Check the form. Submit a request with valid data, with empty required fields, with a long message, and from a mobile device. Review what the user sees after submission. If the email arrives without a clear subject, without contact details, or with unreadable formatting, go back to Form Builder and the mail settings.

Check the technical side: responsiveness, first-screen speed, image sizes, alt text, page access without authorization, the 404 page, the sitemap, robots settings, and basic SEO fields. The template does not guarantee good performance on its own. Speed depends on images, caching, hosting, the number of extensions, third-party scripts, and content quality. In Themis, it is especially important to compress real team and office photos, because legal websites often use large imagery.

If Themis Is Not Working the Way You Expected

It is better to troubleshoot Themis around the specific symptom, not around the vague phrase "the template is broken." In a Joomla template, the same visible issue can come from different causes: a template style setting, a menu item, a module position, an SP Page Builder page, cache, or server limits. Below is a practical map of problems that are typical for a template of this type.

There Is No Demo Site After Installation

Symptom: the template is installed, but the homepage does not look like the demo. Possible cause: you installed the Template Pack instead of Quickstart. The Template Pack does not include demo content, pages, modules, or components. Check which archive you installed. If you need the actual demo site, install Quickstart on a clean environment. If the site already exists, use Quickstart only as a reference and build the necessary pages manually.

Placeholders Appear Instead of Photos on the Pages

Symptom: instead of images of lawyers, the office, or section visuals, you see placeholder blocks. The documentation confirms a possible cause: live preview photos may not be included in the package because of licensing. The fix is to replace them with your own images or legal stock photography. Do not try to hunt down the "original" demo photos if the rights were not transferred. No rollback is needed: this is not a configuration error, but a normal part of adaptation.

The Mobile Menu Is Empty

Symptom: the menu button opens the offcanvas panel, but there are no items inside. Check whether a menu module exists in the offcanvas position, whether it is published, what access it has, which menu it uses, and which pages it is assigned to. If the menu appears on desktop, that does not guarantee it will render in offcanvas. After making changes, clear the cache and check again at mobile width.

The Sidebar Does Not Appear in the Article Detail View

Symptom: the module is visible in the blog list, but disappears in the article page. Themis documentation points to the setting Helix Options -> Blog -> Details -> Disable Modules: OFF. Also check the module position and the Menu Assignment tab. If enabling modules makes the page feel overloaded, it is better to show only relevant blocks: categories, popular posts, contact information, or a consultation block.

The Consultation Form Does Not Send Email

Symptom: the visitor sees the form, but the inquiry never arrives. Check the Recipient Email in the Form Builder addon, the required fields, Joomla mail settings, hosting restrictions, and the spam folder. If the form sends email but it is hard to read, configure the email subject and body in Form Builder. If the problem appeared after custom JavaScript was added, disable it temporarily and run the test again.

A Change Saved in SP Page Builder Is Not Visible on the Site

Symptom: the section is changed in the editor, but the public page still shows the old version. Check whether you edited the page that the menu item actually points to. Then clear the Joomla cache, template cache, browser cache, and the cache of any optimization extensions. If multilingual mode is enabled, check the menu item for the relevant language.

Video About Themis: What to Watch Before Configuring the Demo

The official Themis documentation includes a video overview of the template on YouTube. It is best viewed not as a promo clip, but as a visual map: which pages and sections are expected in the demo, where the consultation form is, how the legal style looks, which blocks you may want to keep, and which ones are better replaced for your firm. The video supports the main point of this guide about choosing a homepage variation, understanding page structure, and checking the result after installing Quickstart.

After watching it, it is useful to open your own test site and walk through the same zones: homepage, practice areas, appointment, portfolio, blog, menu, and footer. If something is missing in your Quickstart, first check page and module publishing before you start reinstalling.

When It Makes Sense to Move on to Downloading and Testing

Move on to installing Themis when you understand which package you need, are ready to work with Helix Ultimate and SP Page Builder Pro, have prepared a staging environment, and have gathered the basic content for the legal website. For a new project, start with Quickstart on a separate environment so you can see all pages and settings. For an existing site, start with the template pack on a site copy and map the module positions in advance.

Before going live, check not just the visual appearance, but the user path: searching for a problem, opening a practice area, reading a case study or article, submitting the form, receiving the email, using the mobile menu, and finding contact details. If that path works, Themis becomes more than just a good-looking template - it becomes a clear foundation for a legal website.

When you are ready for a test installation, you can get the Joomla version and deploy it in a safe environment first. Do not delete the staging copy after launch: it will still be useful for testing updates, new sections, and CSS changes without risking the public site.