JoomShaper Empire - Joomla Template

A Practical Guide to Setting Up JoomShaper Empire for a Joomla Real Estate Website

JoomShaper Empire is best understood not as just another template with a polished homepage, but as a ready-made working framework for a real estate website: a visual template, demo structure, Helix3, SP Page Builder Pro, SP Property, search modules, property cards, agent pages, and inquiry forms. This guide explains how to turn the installed package into a manageable website rather than simply swapping out the logo and demo photos.

This article is aimed at a site owner, webmaster, or Joomla editor who needs to understand the implementation flow: what to check before installation, when to use Quickstart, where to configure the header, menu, and typography, how to connect property fields to SP Property modules, how to verify the result on the live front end, and how to quickly identify the cause of common issues.

We will not repeat the promotional copy from the product page. Instead, we will focus on practical work: what decisions to make before the first launch, which settings to handle carefully, how to structure the homepage for a real estate agency, and when Empire is better replaced with a more modern or more specialized solution.

How Empire Differs from a Typical Real Estate Template

Many Joomla real estate templates offer little beyond the visual layer: a few pages, a card grid, a slider, and a contact form. Empire is built differently. In JoomShaper's official materials, it is presented as a template for real estate agencies, developers, rentals, and similar projects, but its real value comes from its integration with the SP Property component. That component handles listings, agents, features, search, maps, viewing requests, and dedicated property pages.

That changes the way you should approach setup. If you treat the template as nothing more than a collection of SP Page Builder sections, it becomes very easy to break the catalog logic: remove the search position, forget to assign a module to the right menu item, leave demo categories without structure, or replace property cards with standard Joomla articles. A better approach is to define the property catalog, agent roles, search filters, and menu structure first, and only then move on to visual customization.

The homepage reference shows Empire's typical mechanics: a large featured property slider at the top, colored property tabs below it, then a search bar, and a Featured Property block. This is not just decorative above-the-fold design. It creates a user journey: notice an appealing property, refine the criteria, open the listing, contact the agent, or submit a viewing request.

The Core Product Stack

Empire relies on four layers working together:

• The Shaper Empire template defines the design, module positions, header, menu, slider, typography, grid, and overall visual rhythm.
• Helix3 handles the core template settings: logo, header, menu, color presets, typography, custom CSS, and part of the responsive behavior.
• SP Page Builder Pro is used for pages, sections, and demo layouts, including the homepage.
• SP Property manages the real estate data itself: properties, categories, agents, features, maps, galleries, search, inquiries, and output modules.

These layers need to be configured together. For example, if the homepage includes a search block, it should not only sit nicely in the property-search position, but also pull real categories, cities, statuses, and features from SP Property. If a property card includes a gallery and a floor plan, uploading a single image in Page Builder is not enough. That data is better stored inside the property record itself so the listing page, search, and module blocks all display consistent information.

The main question to answer before working with Empire: decide whether the site will be a real property catalog or only a presentation-style showcase. For a catalog, SP Property matters more than visual polish. For a showcase, you can simplify the structure, but then some of the template's capabilities will become unnecessary.

Who This Template Is For, and Where It May Be Overkill

Empire works best for websites where properties need to be updated regularly rather than simply presented as a static portfolio: an agency selling apartments, a developer showcasing residential complexes, a company leasing commercial spaces, a cottage community owner maintaining a house catalog, or a content manager adding new listings without manually rebuilding layouts.

Projects like these rely on repeating entities: property, agent, category, status, price, square footage, bedrooms, bathrooms, gallery, map, floor plan, and contact form. SP Property gives you dedicated fields for all of them. That is more practical than building every property card from a standard Joomla article, because the data can be filtered, displayed through modules, linked to an agent, and used on the search page.

When Empire Is a Good Fit

• You need a real estate agency website with property search, categories, and basic filters.
• Dedicated property pages with galleries, maps, descriptions, pricing, property details, and agent contact information matter to the project.
• The team wants to get a demo structure quickly through Quickstart and then replace the demo content with their own listings.
• Editors are comfortable working in Joomla and understand the difference between a component, a module, a menu item, and a template position.
• The project fits Empire's visual logic: a large slider, green accent palette, property cards, and a clean grid.

When You Should Consider Another Solution

The template may be too much if the website is just a single landing page for one property. In that case, it is usually easier to build the page in a modern builder or use a lighter template without catalog features. It may also fall short for projects that need a complex marketplace with agent dashboards, paid submissions, advanced inquiries, internal messaging, complex roles, and automated sync with an external CRM. Some of those scenarios can be built around Joomla, but Empire on its own does not turn a site into a full CRM platform.

Another factor is the framework. Empire is built on Helix3, while newer JoomShaper templates often use Helix Ultimate. That does not make Empire outdated or unusable, because the official page and changelog still show ongoing updates, but before implementation you should verify the stack for the specific project: Joomla version, PHP, SP Page Builder, SP Property, hosting requirements, and the availability of updates for all extensions.

What to Check Before Installing It on a Live Site

The most common mistake when installing a Joomla template is starting on a live site that already has content, menus, modules, and users. With Empire, that is especially risky because Quickstart includes not only the template, but also a full Joomla demo build with components, settings, and sample content. You cannot simply install that package over an existing site like a regular extension.

Before installation, verify not only the compatibility listed on the product page, but also the practical conditions. Quickstart requires a separate directory or subdomain, a separate database, and the ability to go through a standard Joomla installation. A manual install on an existing site requires the template package and its dependent extensions, followed by manual setup of modules and positions.

Minimum Technical Checklist

• Check that your Joomla version, PHP version, and database match the official product page and documentation.
• Make sure the hosting environment has enough upload_max_filesize, memory_limit, and max_execution_time for package installation and demo import.
• Verify that the required PHP extensions for Joomla and the template components are available, including cURL, OpenSSL, image support, and multibyte string handling.
• Create a backup of the files and database if you are working alongside an existing site.
• Create a staging subdomain or local copy so you can reproduce the demo first and understand the module structure.
• Compare the template's extension list with what is already installed on the site to avoid version conflicts.

If you are not sure which package you need, start with a test Quickstart installation. It helps you see which modules and positions the demo uses before you move the structure to the live site.

Quickstart or Manual Installation

Once you choose the installation method, write down which data will be real: property categories, statuses, currency, cities, agents, contact fields, map, and forms. That will save time when you start configuring SP Property.

Quickstart, the Template Package, and the First Verification Run

In the JoomShaper ecosystem, Quickstart is a ready-made copy of the demo site bundled together with Joomla and demo settings. Empire's documentation explicitly points out that this package is installed as a new Joomla build. If you try to upload it through the Extensions Manager on an existing site, you will get an error or end up with an unpredictable result.

In practice, the workflow is straightforward. First, create an empty database, unpack Quickstart, upload the files to a separate directory, and complete the Joomla installation wizard. After installation, log in to the admin panel, remove the installation folder, verify the homepage, and only then start replacing the demo data.

What to Do Immediately After Installation

Front-End Check

1. Open the public side of the site and make sure you see the Empire homepage rather than the default Joomla template.
2. Check the header: logo, menu, phone block, slider, and search bar.
3. Open several property cards and make sure images, price, map, agent, and forms are displayed without empty blocks.
4. Go to the admin panel and locate SP Property in the Components menu.
5. Open the module list and filter positions associated with Empire: property-search, slide, search, gallery, footer1, offcanvas, and others.
6. Clear the Joomla cache and browser cache if you still see the old layout after changes.

At this stage, do not rush to delete all demo properties. It is better to first study which elements are used on the homepage and property pages. Deleting demo content before you understand the structure often leads to an empty slider, missing search, or property cards without images.

If You Are Installing Only the Template on an Existing Site

The manual path requires more attention. The template controls the visual layer, but it does not create all pages, modules, and demo relationships for you. After installation, you need to assign Empire as the site style, install or update the required extensions, create SP Property menu items, place modules into the template positions, and configure the pages in SP Page Builder.

If the existing site already uses another template, compare module positions in advance. A module that used to sit in sidebar-right or position-7 may not appear in Empire if that position does not exist or is not used in the current layout. In that case, you need to open the Empire position list and reassign modules manually.

The Template Framework: Logo, Header, Menu, Typography, and Colors

Once the initial verification is done, move on to the framework. In a Joomla template, this is not just cosmetic detail, but the foundation of navigation. A real estate visitor usually arrives with a specific goal: find a property by criteria, check the neighborhood, contact an agent, or compare several offers. That means the header, menu, search, and property cards should support that journey.

Empire uses Helix3, which means the main settings are configured in the template style. That is where you control the logo, sticky header, menu, color presets, typography, custom CSS, and some utility blocks. The Helix3 documentation also shows that the menu has separate Mega Menu and Off Canvas settings, while some advanced options are handled in Joomla's menu manager.

Logo and Phone Block in the Header

In the Empire demo, the logo appears as a bold green vertical mark, while the phone block is visible on the right side of the header. Do not copy that layout mechanically if your agency uses a different conversion path. For a small agency, phone calls may be the main action. For a developer, a link to the sales department or a viewing request page may be more useful. For a rental website, a location filter may matter more.

A practical order of work looks like this: upload a logo at the right size, check the header height before and after scrolling, configure the mobile logo, then open the homepage at tablet and smartphone widths. If the mobile header logo is too tall, the menu and slider will start competing for the first screen. Helix3 includes separate logo and mobile logo settings for exactly this case.

Menu and Off-Canvas

A real estate website menu should not be overly long. A good starting set is: Home, Properties, Rent or Sale, Agents, Blog or News, Contacts. If the catalog is large, it is better to create dedicated sections through filters and SP Property pages rather than adding dozens of items to the header.

In Helix3, you can choose the menu and the menu type. Off Canvas works as a separate mobile layer. It is usually powered by a menu module published in the offcanvas position. If the mobile menu does not open or appears empty, check for a published menu module in the correct position before you start debugging CSS.

Typography and Cyrillic Support

Empire's documentation notes that the demo uses the Google Font Catamaran. For a Russian-language site, that is not enough as a ready-made solution. You need to check Cyrillic support, available weights, and loading speed. If the chosen font handles Russian poorly, headings will look out of place, and some characters may fall back to the system font.

A practical approach is to keep Empire's overall visual logic but choose a font with solid Cyrillic support. Check H2 headings, property cards, pricing, the search button, and form labels. Do not change every size at once. First, make sure the property card and main search are readable, then fine-tune the headings and menu.

Colors and Presets

The official page mentions multiple color presets, and the reference clearly shows the green accent, colored slider tabs, and light property card grid. For a real estate agency, that is a workable scheme: green reads well as an action color, while a neutral background does not compete with property photos. But if the company brand uses a different color, change it through settings and custom CSS rather than editing the template files directly.

Rollback rule: before changing colors or CSS, save the current values or create a copy of custom.css. If your edits make cards, menu, or slider harder to read, revert only the last CSS block instead of reinstalling the entire template.

SP Property as the Catalog Core: Listings, Agents, Filters, and Inquiries

If the framework controls the visual side, SP Property controls the meaning of the real estate website. The official documentation describes the component as a tool for categories, property features, listings, inquiries, and agents. For Empire, it is the core. Without it, the template becomes a polished page with no manageable catalog behind it.

Do not start by adding your first property. Start by designing the data model. A real estate catalog does not handle chaos well. If one property's price is typed into the description, another uses the price field, and a third includes it in the title, search and modules will never display the data predictably. The same applies to square footage, statuses, cities, agents, and galleries.

Prepare Categories and Features

Categories in SP Property are not just for admin-side organization. They are part of module output, filtering, and page structure. For an agency, they may include apartments, houses, commercial units, land plots, and rentals. For a developer, they might be residential complexes, construction phases, apartments, offices, and parking. The key is to keep categories distinct and understandable for the visitor.

Features are best set up as reusable values. If many listings have security, parking, a terrace, an elevator, a river view, or finished interiors, create those as structured property features instead of retyping them as free text each time. That way, users can compare listings, and editors do not have to invent different wording for the same feature.

Fill Out Property Records So They Sell and Filter Properly

The basic fields in a property record matter: title, alias, category, status, agent, description, featured image, gallery, coordinates, price, currency, city, address, area, bedrooms, bathrooms, garages, features, video, and floor plans if available. Not every field is mandatory for every project, but leaving important ones empty creates weak property pages.

A strong property page answers the visitor's questions before they submit an inquiry: where the property is located, whether it is for sale or rent, how much it costs, how large it is, who handles viewings, what the photos look like, whether a floor plan is available, and how to contact the agent quickly. That is why, in Empire, one photo and a short description are rarely enough. The gallery, map, and agent block are not decoration, they are part of building trust.

Agents and Viewing Requests

In SP Property, an agent is a separate entity that can be linked to listings. That is useful even for a small company. If the visitor sees a specific specialist, phone number, email address, and contact form, the chance of conversion is higher than with a generic footer contact. For a team with multiple agents, linking properties to people also helps distribute inquiries and keep portfolios current.

Viewing requests and price inquiries should be tested separately. After setup, submit a test inquiry, make sure it appears in the admin panel, and verify that the email is not lost because of Joomla mail settings or hosting issues. If forms work through Ajax, the front-end result may look successful even though the administrator still needs to confirm the record was saved in the component and the email was actually delivered.

Modules, Positions, and Menu Items: How to Output Search, Property Cards, and Catalog Pages

In Joomla, a module does not appear on a page by itself. It needs a position, publication status, menu assignment, and correct parameters. Empire's documentation lists template positions including property-search, gallery, search, slide, feature, slider, position1 - position8, bottom1 - bottom4, offcanvas, pagebuilder, footer1, and others. That list is the map you use to place functional blocks.

For Empire, three module groups matter most: property search, property output, and agent or category output. The SP Property documentation explains that you create these modules through Joomla, find them by the SP Property name, configure their fields, and assign them to template positions.

Property Search

The homepage search should stay simple. The Keyword, Location, Min Size, Bed, and Bath fields from the reference work well above the fold because they do not overwhelm the visitor. Advanced search can remain a separate link or mode if the catalog is large. If the site has only a small number of properties, too many filters make it feel empty.

Configure the search module so the fields reflect real data. If cities or sizes are not filled in for listings, those filters will be useless. If listing statuses are maintained inconsistently, visitors will get confusing results. After each change to the filters, open the public page and run several test queries.

Property Cards on the Homepage

The Featured Property block in the demo is best used as a curated selection rather than a random showcase. In SP Property, you can mark properties as featured and output them through a module. For the homepage, 4 to 6 strong listings are usually enough. A list that is too long pulls attention away from search and contact paths.

Make sure all listings in the selection have images with matching proportions, either a filled-out price or a clear request-price mode, a category, and an assigned agent. If one card looks empty, it weakens the whole grid.

Menu Items for the Catalog

Catalog pages should be created through the Joomla menu manager. The SP Property documentation shows that menu items can lead to the property list, agents, gallery, and other component content types. This matters for routing, SEO-friendly URLs, and module assignments. If you simply place a module on a page without a proper menu item, some module assignments and breadcrumbs may not behave as expected.

A practical starter menu for the site is: Properties, For Sale, For Rent, Agents, Contact. If you also need a blog, keep it separate rather than mixing Joomla articles into the property catalog.

Homepage and Slider: How to Preserve Empire's Visual Rhythm

Empire's homepage is built around a visual scenario. At the top, the user sees a featured property and colored tabs, then the search bar, then a grid of featured listings. If you rearrange those blocks at random, the template loses its logic. So when editing the homepage, think in terms of the user's journey rather than isolated sections.

The Empire slider has a distinctive detail: lower mini-tabs with colored backgrounds and previews. The HomePage Slider Customization documentation shows safe CSS techniques for disabling the thumbnails, hiding the button, and adjusting the overlay darkness. That is useful if your property photos look too dark or the tabs distract from the main content.

When to Change the Slider

It makes sense to keep the slider if you have 3 to 4 strong listings with high-quality horizontal photos and a clear status. It works as a showcase. But if you do not have solid photography yet, or the image quality is inconsistent, it is better to simplify the first screen for now: show one main property, the search bar, and a short value proposition instead of rotating weak images.

How Not to Break the First Screen

• Do not use a hero photo with too many small details if large text and a button appear on top of it.
• Watch the contrast: an overlay helps the text, but if it is too dark, the interior or building becomes hard to recognize.
• Do not add more properties to the slider than a user can realistically evaluate before moving to search.
• Check the mobile version, because the desktop menu and off-canvas menu behave differently.
• Keep property captions short: type, name, price or unit, and a details button.

If the search block sits directly below the hero section, make sure it remains visible without excessive scrolling. On a real estate website, search is often more important than decorative company text.

Practical Scenario: Launching a Real Estate Agency Homepage

Below is a setup example you can reproduce on a test site after installing Quickstart. It is not tied to a real address or actual prices, but it shows the sequence of work for a typical real estate agency.

Goal

The goal is to create a homepage where the visitor sees a branded header, 3 to 4 strong properties in the top slider, a quick search, a featured listings block, agent contacts, and a clear path to the full catalog page.

Preparation

Before setup, the Empire template, SP Property, SP Page Builder Pro, and the required dependent modules should already be installed. The test site should include at least two property categories, several property features, two agents, and 6 to 8 test listings with photos, price or request-price mode, status, city, and assigned agent fully filled out.

Steps

Start with the Data Structure

1. Open Components - SP Property and create categories such as apartments, houses, and commercial units.
2. Add property features: parking, elevator, security, terrace, renovation, furniture, nearby subway, or another local feature that matters in your market.
3. Create agents and fill in their contact fields, because property cards should point to a real responsible person.
4. Add listings under Properties: title, category, status, price, currency, city, address, featured image, gallery, description, area, bedrooms, bathrooms, and agent.
5. Mark 4 properties as featured if you want them displayed on the homepage.
6. Open the Joomla module list and configure SP Property Search in the property-search position or another position used by the layout.
7. Configure the property output module: choose categories, status, ordering, number of columns, and item limit.
8. Create menu items for the property list and the agent page through Menus - Main Menu - +New, selecting the SP Property type.
9. In SP Page Builder, edit the homepage: replace the text, hero photos, button labels, and links with real menu items.
10. Clear the cache and open the site in a new window while logged out.

Verification

After setup, the visitor should see a homepage without empty demo blocks. Search should return relevant properties. Clicking a property card should open the listing page and show the gallery, map or address data, agent, and contact form. The mobile menu should open correctly and lead to the same key sections.

Important Detail

If a property does not appear on the homepage, do not check only its publication status. Possible causes include: the property is not marked as featured, the module is filtering a different category, the module is assigned to the wrong menu item, the selected position is not rendered in the current template layout, or the cache is still showing the old state.

Practical Use Cases for Different Real Estate Websites

Empire does not have to be used only as a classic apartment sales agency website. Its structure supports several practical scenarios, as long as you do not try to invent features beyond what SP Property and Joomla actually provide.

Agency with a Regular Property Catalog

Here, the main priorities are speed of adding new listings and search quality. Use categories, sale or rental statuses, featured properties on the homepage, and agent pages. The result is easy to verify: the editor adds a new property once, and it appears in the right lists and filters without manually building a card in Page Builder.

Developer Website

For a developer, the emphasis is more on presenting residential complexes, layouts, and viewing requests. Categories can be organized around projects or unit types, while property cards can be used for apartments, commercial lots, and parking spaces. In this scenario, the hero slider should showcase key projects rather than random properties.

Commercial Rental Listings

For rentals, the important fields are size, price per period, location, floor, photos, plan, and the contact details of the responsible manager. It is better to keep fewer fields in the filters but fill them consistently. If a visitor is choosing office space by size and district, empty or inconsistent values in listings will do more harm than mediocre design.

Showcase for a Single Complex

If the number of listings is small, Empire can be used as more of a presentation-style showcase: homepage, gallery, several layout types, sales department contacts, and an inquiry form. In that case, some catalog features should be hidden so the interface does not feel empty. The main thing is not to leave demo sections in place if they do not match the real offer.

How to Verify the Result After Setup

Checking Empire should involve more than a designer's eye. You need to walk through both the user journey and the editor workflow. The user searches for a property, opens a listing, reviews photos and the map, and submits an inquiry. The editor adds a property, assigns an agent, changes the status, checks the module, and updates the page.

Public Front End

• Open the homepage and verify that the hero section, search, and featured listings are showing real data.
• Run 3 to 5 search queries with different filters and make sure the results are not empty because of bad data.
• Open a property page and check the gallery, price, property features, map, agent, form, and related blocks.
• Check the mobile menu and first screen on a phone or in a browser emulator.
• Open the page with browser cache disabled or in private browsing mode.

Admin Panel and Editorial Workflow

Create a test property not as a super user or developer, but as a real editor with the same permissions they will have on the live site. That shows whether they actually have access to SP Property, media files, and menu items. If an editor cannot upload an image or select an agent, you want to catch that before launch.

After saving the property, check where it appears: in the full catalog, in the homepage module, in the agent profile, and in search filtered by category and status. If the property is visible in the component but not on the site, the cause is almost always the status, module assignment, module filter, menu item, position, or cache.

Safe Improvements Without Editing the Template Core

Empire has several scenarios where a small adjustment is genuinely useful. The best example is slider tuning. The official documentation provides CSS for hiding the thumbnails, removing an empty button, and reducing the dark overlay. This is safer than editing template files directly because CSS changes can be rolled back easily.

Add adjustments like these through custom CSS in the Helix3 settings or through the custom.css file if your build uses one. Do not modify the original template files unless you have to. Updates can overwrite those changes, and troubleshooting becomes more complicated.

Make the Hero Slider Lighter

If the real estate photos in the hero section look too dark, you can reduce the strength of the overlay layer. The Empire documentation illustrates the general idea with rgba. Below is an example of a subtle lightening adjustment that does not eliminate contrast completely.

#slider.flexslider .slides li::after {
  background: rgba(0, 0, 0, 0.3) !important;
}

Verification: open the homepage and compare the readability of the property title with the visibility of the image. If the white text becomes hard to read, switch back to a darker value such as 0.45. Rollback: remove this block from the custom CSS and clear the cache.

Hide the Lower Slider Thumbnails

If the project uses one strong property in the hero section, or the mini-tabs interfere with the mobile layout, you can hide the lower part of the slider. This changes the visual scenario, so apply it only after checking the homepage carefully.

#slider.flexslider .flex-direction-nav,
.slide_thumb_wrap .flexslider {
  display: none;
}

Do not use CSS as a substitute for proper data setup. If the slider is empty, first check the slide source, images, and publication status of the listings. CSS is for presentation behavior, not for hiding content problems.

Troubleshooting Common Empire Issues

Problems with a Joomla template often look like design failures, but the root cause is usually somewhere in the connection between data, modules, menu items, positions, and cache. Below is a practical map of symptoms that are especially typical for a site built on Empire and SP Property.

Quickstart Does Not Install or Freezes

Symptom: the installation does not finish, the database is not imported, the Joomla wizard freezes, or an error is returned. Possible causes include server limits, an unsupported PHP version, execution time that is too short, a database issue, or an attempt to install Quickstart into a non-clean environment.

Check the PHP limits, a fresh database, database user permissions, complete file upload, and the absence of an older Joomla installation in the same directory. If you are installing locally, compare your setup with the Empire documentation. The correct rollback here is not to revert the template, but to clean the directory and database, then retry in a clean environment.

Property Search Returns Nothing

What to Check First

Symptom: the search form is visible, but the results are empty or odd. Check whether the fields used by the module are actually filled in on the listings: category, city, size, bedrooms, bathrooms, status, price. Then check the SP Property Search module settings and the menu item the results are supposed to open.

Fix: fill in the data consistently, temporarily simplify the filter down to 2 or 3 fields, and test each filter separately. If search works after simplification, add the fields back one by one.

The Module Is Published but Not Visible on the Page

Symptom: the module is enabled in the admin panel, but it does not appear on the site. Possible causes: wrong position, module assigned to the wrong menu item, the position is not used in the current layout, the user is viewing a cached page, or the module is limited by access level.

Check the position against the Empire position list, the menu assignment, publication status, language, access level, and module ordering within the position. For visual position checks, use Joomla's built-in position preview tools if that feature is enabled.

A Property Page Opens Without Photos, a Map, or an Agent

Symptom: the property list looks fine, but the detail page is empty or incomplete. Check the property record: featured image, gallery, coordinates, city, agent, publication status, language, and access. If the map does not appear, check the coordinates and map settings inside the component.

Fix: fill in one property with a minimal but complete data set and compare it with a demo property from Quickstart. Do not copy only the visual HTML from the demo. The data needs to live in the SP Property fields.

Nothing Changes on the Site After Edits

Symptom: everything is saved in the admin panel, but the public page still shows the old version. Clear the Joomla cache through System - Clear Cache, reset the browser cache, and check hosting or CDN cache if those are in use. If CSS/JS optimization is enabled, disable it temporarily while troubleshooting.

The Mobile Menu Is Empty

Symptom: the menu icon is there, but no items appear inside it. In Helix3, off-canvas may use a separate menu module in the offcanvas position. Create or verify that menu module, assign it to all pages, disable the title, and make sure it is using the correct menu item set.

The Layout Breaks After an Update

Symptom: after updating Joomla, the template, or extensions, styles disappear, cards break, or module behavior changes. Check the Empire, SP Property, SP Page Builder, and Helix3 changelogs, then compare your custom CSS changes. If the issue appeared after a specific update, roll back to the backup of your test environment and repeat the update step by step.

The Official Video as a Quick Overview of the Visual Logic

The JoomShaper page for Empire includes a Watch Video button that links to a video about this template. The video is useful not as a substitute for setup, but as a fast visual reference: how the demo looks, how the slider, search, property cards, and overall real estate site style are perceived. After watching it, it becomes easier to decide which blocks you want to keep and which ones you can simplify for your project.

Use the video together with a test Quickstart install: first review the visual scenario, then open the admin panel and identify which modules, menu items, and SP Property records are producing that result.

When JoomShaper Empire Is the Right Choice

Empire makes sense if you need more than just an attractive layout. It is a manageable Joomla real estate website structure with listings, agents, search, property cards, galleries, a map, inquiries, and a clear homepage. The template's strength is the ready-made combination of design and SP Property. Its weak point is that you need to work carefully through modules, positions, Quickstart, and its dependency on several extensions.

Before launch, go through a test cycle: install Quickstart, study the demo, replace a few listings, check search, the mobile menu, the property page, and the inquiry flow. If the structure fits, you can download the ZIP archive, deploy it in a test environment, and move it to the live site only after final verification.

If the project requires a newer framework, a complex listings portal, or highly customized CRM logic, review alternatives before implementation. But if the goal is to build a clear, workable real estate catalog on a proven Joomla structure, Empire remains a practical option as long as you configure it carefully and keep updates under regular review.