WarpTheme Epic Pro - Joomla Template

WarpTheme Epic Pro Setup Guide for a Joomla Website for a Construction Company

WarpTheme Epic Pro is a Joomla template for corporate and construction websites, but its real value does not come from simply installing it. It comes from assembling the demo layout, menus, module positions, styles, and service pages correctly. In this guide, we will look at how to treat the template as a practical site foundation rather than a ready-made picture that only needs to be uploaded to a server.

This guide is intended for a site owner, Joomla administrator, or developer who needs to launch a polished front end quickly, keep control over the site structure, and avoid breaking template updates. We will also cover Quickstart, the standard template package, Template Options, Helix Ultimate, SP Page Builder, Extra Add-ons, module positions, the mobile menu, styles, performance, and troubleshooting common issues.

This guide does not repeat the product's short description. Instead, it shows which decisions to make before installation, which settings to check immediately after activation, how to build a practical scenario for a construction company website, and how to confirm that the result works properly on the live Joomla front end.

What this template is designed to do

Epic is built for company websites where you need to present expertise, services, portfolio items, trust-building sections, and contact points quickly. The demo clearly reflects a construction and industrial style: a strong hero section, a top contact bar, navigation, service blocks, an about section, benefits, and a portfolio. This is not a generic blank theme. It is a visual starting point for contractor websites, architecture firms, engineering teams, renovation companies, and service businesses that need a clear, professional storefront.

The main strength of WarpTheme Epic Pro is that it brings together several layers of a Joomla website. The first layer is the template itself, including the visual design, header, footer, styles, and positions. The second layer is Helix Ultimate, which handles layout, menu, typography, presets, compression, and additional settings. The third layer is the pages and sections built in SP Page Builder and extended with WarpTheme Extra Add-ons. If you work with only one layer, the site will feel incomplete: the template may be installed, but the home page will still be empty; the pages may be built, but the menus and positions may not behave like the demo; the styles may look polished, but the mobile menu or quick-start workflow may still be unconfigured.

The right implementation logic is this: first choose the installation method, then activate and verify the template style, then configure the overall site shell, and only after that edit the content blocks. If you start replacing homepage text immediately, it is easy to miss system-level settings that control the header, mobile menu, container width, CSS compression, SCSS compilation, and module display.

When Epic is the best fit

This template is especially useful when the site needs to look like a corporate website with a strong hero section, clearly presented services, and a portfolio. It works well for a small company website, a landing page for construction services, a multi-page project catalog, a contractor website with a blog, or a site that needs a basic catalog or HikaShop styling, if that use case is actually part of the project.

For a Joomla administrator, there is another important advantage: Epic is built on standard Joomla tools rather than a locked-down one-page editor. That lowers the risk of the entire site becoming impossible to update without a specific designer. Menus, modules, template styles, and pages remain in familiar Joomla areas: System, Site Template Styles, Menus, Modules, Components, and SP Page Builder.

When another approach makes more sense

Epic may not be the best choice if you need a minimalist blog without a visual builder, a large online store with custom checkout logic, a project with a completely custom design system, or a website where additional extensions and page builders are not allowed. Quickstart is convenient when you want a copy of the demo, but it requires a clean Joomla installation and a separate database. If you already have a live site with content, users, and a complex menu structure, you cannot simply upload Quickstart over it.

There is also an organizational risk: the template gives you many settings, but it does not replace a content plan. You should not expect the demo text and images to turn a construction company site into a finished expert resource. You will still need to replace the services, photos, case studies, contact details, legal information, and forms. Epic speeds up the structural build, but it does not solve the problem of original content creation.

What to check before installation

Before you install anything, decide which package you are using: the standard template package or the Quickstart package. This is the key decision because it affects not only the installation process but also how you will work with the content afterward. The standard package is installed into an existing Joomla site through the extension manager. Quickstart is a complete demo site that is deployed as a new Joomla installation with preconfigured extensions, the template, modules, and demo content.

If you are building a site from scratch and want a look close to the demo, Quickstart is usually faster. If the site already exists, the standard template package is the safer choice because Quickstart is not meant to be installed inside an existing Joomla site. WarpTheme documentation calls this out directly: the quick-start package is a full installation, not a standard extension.

Technical environment

The official Epic page lists the current compatibility combinations for Joomla, Helix Ultimate, UIkit, SP Page Builder, and PHP. We are not locking version numbers into the visible article text because they change, but before installation you should verify them in the sources and changelog. In practice, check four things:

• Your Joomla and PHP versions match the package you plan to install.
• The server has the PHP extensions and functions required by Joomla and the WarpTheme documentation, including cURL, OpenSSL, and proper filesystem support.
• The tmp, logs, cache, and template directories are writable where needed for installation, saving settings, and style compilation.
• You have a backup of the site and database before any update, migration, or template switch.

Do not mix Quickstart with an existing website. If you already have a working Joomla site, install the standard template package and manually transfer the ideas you need from the demo. Only deploy Quickstart on a clean environment or a local staging setup.

Site content and structure

Before installation, it helps to sketch a simple site map. For a construction company, that usually means pages such as Home, Services, Projects, About, Blog or News, and Contact. If you plan to publish a work catalog, decide whether it will be built with SP Page Builder, Joomla articles, a dedicated portfolio component, or a product catalog. That decision affects which modules and positions you will need.

You should also prepare real visual assets in advance. The Epic demo uses construction imagery, service cards, and portfolio blocks. If you replace them with random images in different sizes, the template will lose its visual rhythm. It is better to collect a consistent set up front: 1-2 hero images, 6-9 project photos, 3-6 service icons, team or job-site photos, and a logo in both standard and light versions.

Testing mode

Install the template on a site copy or a local staging environment first. This is especially important when migrating from another Helix-based template or enabling CSS/JavaScript compression. A local setup lets you safely test menus, modules, SP Page Builder, the header, mobile settings, language strings, and access permissions. After configuration, keep a record of the changes: which style is assigned by default, which menus are linked, which positions are used, and which additional files were created.

Installation: Quickstart or the standard package

WarpTheme documentation separates installation into two scenarios. The first is installing the Joomla template package through System -> Extensions -> Install. The second is deploying the Quickstart package as a full demo copy of the site. Both approaches work, but they solve different problems.

Standard package scenario

The standard package is the right choice if you already run a site or want to build the structure yourself. After uploading the template archive, install it through the Joomla extension manager. Then open System -> Site Template Styles, select the Epic style, and set it as the default. At this point the site may still not look like the demo, because demo pages, modules, and additional extensions are not created automatically.

1. Install the template archive through the standard Joomla installer.
2. Open the site styles list and assign the template as the default style.
3. Go to Template Options and make sure the settings panels open without errors.
4. Check the front end both as a guest and as a logged-in user if the site includes private areas.
5. Add or verify the required modules in the header, toolbar, footer, bottom, and other positions.

If you use Extra Add-ons in SP Page Builder, WarpTheme documentation specifically points out the need for the UIkit Assets plugin. On a site using the standard package, this is a common missed step: the template is installed and the page loads, but some add-ons do not behave like they do in the demo because the required CSS and JavaScript assets are missing. After installing the plugin, enable System - Extra Addon Assets and make sure the UIkit activation setting does not conflict with the template itself.

Quickstart scenario

Quickstart is the right option when you want a version of the demo site that is as close as possible to the original. It includes Joomla, the template, extensions, demo data, and the settings used in the demo. This package is convenient for a new domain, subdomain, local environment, or temporary test site. It cannot be uploaded through the extension manager of an existing Joomla installation.

Deploying Quickstart is similar to installing Joomla from a prepared package. You will need a clean directory on the server, a new database, and access to the installation wizard. After setup is complete, delete the installation directory, sign in to the admin panel, and immediately replace the demo logins, email addresses, site name, contacts, and service settings.

The main advantage of Quickstart is that it shows exactly how the developer assembled the modules, positions, pages, and styles. That makes it a useful learning resource. Even if the final site will differ from the demo, you can still see which positions are used for the top bar, how the homepage sections are organized, and how the template settings connect to the front-end result.

Initial checks after installation

Do not jump straight into design changes after installation. First, verify the core signs that everything is working properly:

• The template is assigned as the default or assigned to the correct menu items.
• The front end loads without a layout file message and without a blank page.
• The menu appears in the expected position, and submenus are not clipped by the container.
• The mobile header switches at the correct window width.
• SP Page Builder pages open correctly both for editing and on the front end.
• If Extra Add-ons are used, the corresponding system plugin is enabled.

Quick summary: installation is not finished when Joomla shows a successful archive upload message. It is finished when the template style is assigned, Template Options open correctly, the front end renders properly, and you clearly understand which package was used.

Configuring the look and feel through Template Options

After installation, Template Options becomes the main working area. In WarpTheme documentation, it is divided into panels such as Basic, Presets, Layout, Menu, Typography, Blog, Custom Code, and Advanced. The important thing is not to work through every tab in order. Start with the settings that create the biggest visible impact and carry the lowest risk of breaking the site.

Logo, toolbar, and header

In Epic, the top section matters a great deal because the original demo includes a contact bar, logo, navigation, social links, and cart status. Even if your site does not use a store, that top area shapes the first impression. Check the logo, header height, sticky navbar behavior, search placement, and toolbar content. If contact details change frequently, it is better to output them through a module or managed setting rather than hard-coding them into custom HTML that no one remembers to update.

In WarpTheme's Header settings, you will find prepared header layouts. These control how the logo, navbar, and header position relate to one another. For a typical construction company site, start with a simple setup: logo on the left, main menu on the right, and search or secondary actions only when there is a real need for them. More complex header layouts are useful when you have many menu items, second-level navigation, a contact bar, and separate mobile logic.

Presets and the color system

Epic includes ready-made color schemes and support for custom color adjustments. In the demo reference, a warm orange accent is clearly visible, used in buttons, icons, and active elements. That makes sense for construction branding: the accent should help highlight actions, but it should not turn the entire site into a flat orange page.

In Presets, start by selecting the closest base style and then adjust it. If you use Custom Style, change colors gradually: primary accent, link color, button color, and only then background areas. After each change, review the hero section, service cards, portfolio items, contact form, and mobile menu. The documentation also warns about SCSS compilation: if you change a preset or SCSS, make sure compilation completes successfully, and once the site is stable, do not leave unnecessary compilation enabled in production.

Typography and Cyrillic support

The Typography panel lets you manage fonts for the body, navigation, and headings. For a Russian-language website, the key question is Cyrillic support. Not every attractive Google Font includes the glyphs and weights you need. If you choose a font without Cyrillic support, the browser will fall back to another typeface, and your headings will look different from what you planned.

Test the text on several page types: a long paragraph, H2, H3, a button, a menu item, a service card, and a form label. Do not use an overly thin weight for the main body text. On a services website, readability matters more than decorative style. If privacy or speed is a concern, consider system fonts or local font hosting using the approach described in the WarpTheme documentation. That is safer than inserting third-party font scripts in multiple places.

Custom Code and safe small tweaks

WarpTheme documents several ways to add custom CSS and JavaScript. For minor visual adjustments, use custom.css in the template directory or the built-in Custom Css area if you prefer managing code from the admin panel. Do not edit compiled CSS or the main template.css file, because those changes may be lost during recompilation or updates.

To make the CTA button in the hero section stand out a bit more, you can add a small CSS snippet. It does not change Joomla logic and is easy to roll back by removing the lines from custom.css:

.epic-hero-cta .sppb-btn,
.uk-button-primary {
  border-radius: 3px;
  font-weight: 700;
  letter-spacing: 0;
}

.epic-hero-cta .sppb-btn:hover,
.uk-button-primary:hover {
  filter: brightness(0.96);
}

Use this example only after checking the actual classes on your page. If the CTA button is built through SP Page Builder and uses a different class, create your own section or add-on class in the editor and target that in CSS. The safest rollback method is to remove the custom class in SP Page Builder or delete the snippet from custom.css, then clear the Joomla and browser cache.

Modules, positions, and Layout Builder

In a Joomla template, module positions matter just as much as polished page design. WarpTheme documentation explains that templates include a set of available positions, and that Helix Layout Builder lets you connect sections, rows, columns, and module positions. In Epic, this is especially useful for the header, lower content blocks, footer, additional panels, lead forms, contact information, and local promotional blocks.

How to think about positions

A module position is not just a random place where a block gets inserted. It is an agreement between the template and Joomla about which zone of the page can display content. For example, contact info in the top bar, the menu in the header, benefits in the bottom section, or a map and contact details in the footer. If a module is published but the current layout does not output that position, users will never see it.

In Helix Layout Builder, sections are made up of rows and columns. A column can be assigned a module position. So the setup flow looks like this: create or select a position, publish a Joomla module into it, make sure the layout outputs that position, and verify the module's menu-item assignment. If you miss that last step, the module may appear on every page or fail to appear where you need it.

A practical layout for a construction website

For a contractor website, you can distribute the zones like this:

• Toolbar. A short phone number, email, business hours, or a link to a quote request form.
• Header. Main navigation, logo, and search only if there is a real need for it.
• Top or hero zone. The first screen of the page, usually built with SP Page Builder rather than a random module.
• Bottom. Services, benefits, a CTA, or certifications.
• Footer. Address, map, business details, links to key pages, and social profiles.

If you need a new block between the main content and the footer, you can use an existing position or add a new one, but only when there is a clear purpose. The documentation shows how to add a position through templateDetails.xml and assign it in Layout Builder. That is already a developer-level task: save a copy of the file before editing, and remember that template updates may affect standard files.

Menus and mega menu

Epic inherits Helix Menu Builder features such as menu structure control, menu item options, mega menu, and mobile/header/toolbar positions. On a services website, a mega menu is not always necessary. It is useful when you have many categories, such as home construction, renovation, design, engineering systems, portfolio items, and service regions. If you only have a few items, a standard dropdown menu will be easier to understand.

If you enable a mega menu, do not turn it into a directory of every page on the site. Group services by meaning, keep the hierarchy shallow, add one module with quick contact details or a key advantage, and check the dropdown width. The menu documentation includes width and animation settings. A menu that is too wide can conflict with smaller screens, while overly aggressive animation can hurt usability. After saving, test keyboard navigation and behavior at the mobile breakpoint.

Pages, sections, and SP Page Builder

Epic uses SP Page Builder as its visual editing layer. That works well for the homepage, service sections, portfolio pages, testimonials, CTAs, and image blocks. But this approach requires discipline: content sections should remain understandable for editors, should not duplicate system modules, and should not turn into a chaotic collection of add-ons.

What to edit in Page Builder and what to leave in Joomla

SP Page Builder is the right place for pages with unique layouts: the homepage, a service landing page, a project page, or a promo section. Standard Joomla articles are a better fit for news, blog posts, documentation pages, legal content, and any material that should be easy to filter, index, and maintain by editors. This separation reduces the risk of the entire site becoming dependent on manual page-level layout work.

WarpTheme documentation ties Extra Add-ons to SP Page Builder and explains that these add-ons can be used both in the admin area and in front-end editing. If you are working with Quickstart, review which add-ons are used in the demo. Do not immediately replace them with every available element. First update the text, images, and links, then decide which elements are actually necessary.

Homepage sections

For Epic, it makes sense to keep the rhythm of the demo while changing the meaning:

1. Hero section: a clear service promise, service area, and a CTA that leads to a quote request or projects.
2. Service cards: 3-6 service categories with short descriptions and links to dedicated pages.
3. About block: real numbers, certifications, team details, and photos of the site or work process.
4. Portfolio: projects with filtering by job type, if filtering genuinely helps the user.
5. CTA: not an abstract "Buy now," but a clear next step such as an estimate, consultation, or site inspection.

Avoid the trap of leaving the demo content mostly unchanged. Search engines and users respond poorly to pages filled with template lorem ipsum, generic icons, and identical cards. For a construction company, every section should answer a specific question: what do you do, where do you work, what proves your experience, and how can a customer contact you?

Checking the result after editing

After making changes in SP Page Builder, open the page as a guest in a separate window. Check that images do not stretch, buttons lead to real pages, sections do not overlap, text does not break awkwardly at tablet widths, and lazy loading or optimization settings are not hiding important hero content. If CSS/JavaScript compression is enabled, do the check after clearing the cache.

Do not judge only by the editor view. Front-end editing can display administrative elements that a normal visitor never sees. Final validation should be done in public view, ideally in multiple browsers.

Practical example: a construction company homepage

Let's walk through a concrete scenario. The goal is to build a homepage for a company that handles construction and renovation of commercial properties. The page needs to present the company's focus, benefits, selected projects, and a quick path to a lead form. We are assuming the template is already installed, the style is assigned, SP Page Builder is available, and the hero image has already been prepared.

Goal

The homepage should explain within 10-15 seconds that the company provides construction and renovation services, show 3 core services, provide visual proof through project examples, and offer a clear action to take next. For Epic, this fits the demo rhythm well: hero, services, about, portfolio, CTA.

Preparation

Before editing, prepare the following:

• A logo in a format that works well in a light header.
• A hero image without tiny text and with enough darkening or contrast for the headline area.
• Three services with short descriptions and separate pages or anchors.
• At least six project images with consistent visual quality.
• A contact email, phone number, business hours, and address, if they are needed in the toolbar or footer.

Setup steps

1. Open System -> Site Template Styles, select the Epic style, and review Template Options.
2. In Basic -> Header, choose a suitable prepared header layout, upload the logo, and enable sticky behavior only if it does not cover the content.
3. In Presets, choose a color foundation close to the brand. For a construction site, keep one strong accent for buttons and icons.
4. In Menu, make sure the main menu is assigned to the header position and that the mobile menu works through the expected mode.
5. Open the homepage in SP Page Builder. Replace the hero headline, subheadline, CTA, service images, and links.
6. Keep 3-6 service categories in the services block. If there are more, move the details to a dedicated services page.
7. In the portfolio section, use real projects and do not leave demo categories such as illustration or branding if they do not relate to your business.
8. In the footer, publish a contact module, map, or links to key pages, then verify the menu-item assignments.

Verification

Open the homepage on the front end and check the full chain: the logo links to the homepage, the menu opens correctly, the CTA leads to a form or contact details, the services are clickable, the portfolio contains no demo placeholders, and the footer shows real business information. Then reduce the window width and see when the mobile header activates. If the menu appears too early or too late, go back to Basic -> Mobile and adjust the breakpoint.

Important nuance

If you are working with Quickstart, the page may still include demo modules that are not obvious at first glance. Check Content -> Site Modules and filter by positions. A common mistake is updating the page in Page Builder but leaving an old module in the bottom section or footer. As a result, visitors see a mix of the new brand and the old demo structure.

Mobile navigation, performance, and SEO checks

A corporate website template is not really finished until it has been tested for mobile navigation, performance, and basic search visibility. Epic includes Helix features for mobile breakpoints, offcanvas, modal or dropdown menus, compression, SCSS, typography, and blog layout. These settings affect the user experience much more than they may seem to during the design stage.

Mobile menu

In Basic -> Mobile, check the breakpoint, navbar behavior, logo alignment, menu toggle, and mobile menu type. For a service-based website, offcanvas or dropdown is often enough. Modal menus can look impressive, but if the user has many nested items, a full-screen menu requires a very clean structure. Do not bury the main CTA too deeply: the phone number, form, or quote button should be easy to reach.

After setup, open the site at widths close to a phone, tablet, and small laptop. Check that the menu does not duplicate, the logo does not disappear, and the sticky header does not cover the hero section. If mega menu is enabled, make sure the mobile version is not trying to reproduce a complex desktop grid without adaptation.

Compression and cache

In Advanced -> Compression, you can compress and combine the template's CSS and JavaScript. This can help with performance, but it requires caution. The documentation explicitly warns against using template CSS compression together with another optimization extension such as JCH Optimize. If you enable multiple optimizers at the same time, the problems may not appear in the admin area. Instead, the front end may lose styles, the menu may break, modals may stop opening, or script loading order may change.

A safe workflow looks like this: first finalize the design without compression, then enable one optimization layer, clear the Joomla and browser cache, and test the homepage, an inner page, the contact page, and the mobile menu. If everything works, keep that setup. If something breaks, disable the last optimization you enabled and repeat the test. Do not turn on every checkbox at once.

SEO and heading structure

Epic does not guarantee search performance on its own, but it does help you build a clear page structure. Make sure the page has one main H1, real H2 headings for sections, descriptive alt text for images, sensible menu titles, and non-empty meta descriptions. Epic's changelog has included improvements related to metadata, og:image, logo alt text, and SEO behavior, so after updates it is worth reviewing not only the visual layout but also the HTML markup.

For a construction company website, service landing pages matter especially. Do not try to optimize a single homepage for every search query. Create dedicated pages for key services, and use the homepage as a navigation and trust hub. In SP Page Builder, do not leave image-only headings without a text equivalent, and do not hide all important information inside images.

Updates, customization, and safe rollback

Updating a template should not feel like a gamble. WarpTheme documentation on updating explains that Helix Ultimate can be updated through Joomla itself, and that the template package can be updated by installing a newer archive over the existing one without uninstalling it first. But that does not remove the need for backups or for tracking your customizations.

Where to store your changes

Safe places for small adjustments include custom.css, custom.js, custom.scss, Template Options, and standard Joomla overrides when they are truly needed and you understand their scope. Do not modify Joomla core files, extension files, or the template's compiled CSS files. WarpTheme documentation specifically advises against editing template.css and compiled CSS because those changes can be lost during recompilation.

If you need to make a noticeable change to a section, first look for a solution inside SP Page Builder: a custom section class, add-on settings, layout changes, background controls, spacing, or responsive visibility. Only add CSS when that is not enough. For more complex logic, it is usually better to create a dedicated module or override than to paste long JavaScript into Custom Code.

Before updating

• Back up both files and the database.
• Save a list of active template styles and their menu-item assignments.
• Export or copy any important custom CSS, SCSS, or JS snippets.
• Review the changelog, because it may include changes to Helix, UIkit, Quickstart, HikaShop styles, PHP compatibility, and HTML overrides.
• Run the update on a site copy first if the live site is already generating leads.

After updating

Do not check only the homepage. Open second-level menus, a Joomla article page, an SP Page Builder page, the contact form, login/user profile pages, search, the mobile menu, and the footer. Epic's changelog has included fixes for com_users, frontend media editing, HTML overrides, menu icons, profile editing, mod_menu, and other details. That means post-update testing should focus on functional scenarios, not just the hero section.

If styles or layout disappear after an update, clear the cache first and check SCSS compilation. If the issue remains, temporarily disable compression, switch the template style to the default Joomla template for testing, then switch back to Epic and save Template Options again. This sequence helps you determine whether the issue is caused by the template, optimization, menu assignment, or a specific module.

Troubleshooting common issues after installation and setup

Problems with Joomla templates rarely look exactly the same, but Epic and other Helix-based templates do have common risk areas: the wrong package, template style assignment, layout, module positions, Extra Add-ons, file permissions, SCSS, compression, and cache. Below is a practical symptom map.

The template is installed, but the site does not look like the demo

Symptom: installation completes successfully, but the homepage is empty or still looks like the old site.

Cause: the standard template package was installed instead of Quickstart. The standard package does not include demo content, SP Page Builder pages, modules, or images.

What to check: which archive was installed, whether the Epic style is assigned as default, and whether SP Page Builder pages and published modules exist in the required positions.

How to fix it: if you want a demo-like starting point, deploy Quickstart on a clean environment. If the site already exists, rebuild the structure manually: create the homepage, publish modules, and configure the menu and footer.

A layout file message appears

Symptom: the front end or a specific menu item shows an error related to a missing Helix layout file.

Cause: WarpTheme documentation links this issue to special menu items where the template style ID was assigned incorrectly after a template was removed or changed.

What to check: open the affected menu item, inspect the template style field, and compare it with working items.

How to fix it: open the menu item and save it again so Joomla refreshes the style assignment. If the problem is widespread, check the default template assignment and any special menu assignments.

Template settings are not being saved

Symptom: changes in Template Options do not apply, a write error appears, or the settings disappear after refreshing the page.

Cause: a conflict involving file permissions and ownership, hosting restrictions, inaccessible cache/tmp/logs directories, or the inability to write to the template directory.

What to check: directory and file permissions, the web server user, and both Joomla and server error logs. WarpTheme documentation recommends common values of 755 for directories and 644 for files, but your specific environment may require ownership adjustments as well.

How to fix it: restore the correct permissions through the hosting panel or server administrator, then try saving again. Do not apply overly broad permissions across the entire site as a permanent solution.

Extra Add-ons look broken

Symptom: some SP Page Builder elements do not receive styles, animations, or lightbox behavior.

Cause: the UIkit Assets plugin required by WarpTheme for Extra Add-ons in a standard installation is not installed or not enabled.

What to check: the presence of the System - Extra Addon Assets plugin, its status, UIkit Framework settings, and any conflicting optimization tools.

How to fix it: install and enable the plugin, keep UIkit Framework disabled where the template already loads UIkit, then clear the cache and test the page again.

Styles or menus disappear after enabling compression

Symptom: the site was working, but after CSS/JavaScript compression the header, dropdown, modal, or layout broke.

Cause: a conflict between multiple optimization layers or a change in file loading order.

What to check: whether compression is enabled in Template Options and at the same time in a third-party optimization extension. Check the browser console and network errors as well.

How to fix it: keep only one optimizer active. First disable template compression, clear the cache, and test the site. Then re-enable settings one at a time.

The mobile menu does not appear

Symptom: at mobile widths, there is no hamburger menu, or the wrong set of items appears.

Cause: the breakpoint is set incorrectly, the menu is not assigned to the mobile position, the toggle is disabled, or the menu structure is nested too deeply.

What to check: Basic -> Mobile, Menu -> Menu Positions, menu assignment to mobile/header positions, and whether the items are published.

How to fix it: assign the menu to the mobile position, choose an appropriate animation, and test widths around 640, 960, and 1200 pixels as reference points from the documentation.

When WarpTheme Epic Pro is a strong choice

WarpTheme Epic Pro is worth using if you need a Joomla template with a ready-made corporate presentation, construction-oriented visual logic, Helix configuration tools, SP Page Builder pages, and a clear quick-start workflow. It is especially useful for projects where you need to build a homepage, services, portfolio, contact pages, and a responsive header quickly, while still keeping control through standard Joomla mechanisms.

Before launch, check the installation package, template style assignment, menus, modules, mobile navigation, typography, Extra Add-ons, compression, and file permissions. Then replace the demo content with real services, projects, and contact details. If the result is stable on the test environment, you can move on to publishing and download the installation package for further testing on your own site.

The core idea is simple: Epic gives you a strong starting point, but a high-quality website only appears when the template's demo structure becomes your own service structure, real proof of expertise, and a verified Joomla configuration. At that point, the product stops being just a polished shell and becomes a practical foundation for a real company website.