WarpTheme Agency Pro - Joomla Template

WarpTheme Agency Pro Setup Guide for a Joomla Agency or Portfolio Website

WarpTheme Agency Pro is best understood not as a single attractive landing screen, but as a ready-made combination of a Joomla template, Helix Ultimate, SP Page Builder, demo content, module positions, and visual settings. In this guide, we will walk through how to approach installation, when to use quickstart, which panels to open after enabling the template, and how to turn the demo into a working site for a studio, photographer, freelancer, or small creative team.

This guide is intended for a site owner or Joomla administrator who already understands the basic CMS workflow but does not want to dig through settings blindly. It covers preparation, installation, an initial review, header and menu setup, portfolio sections, responsive behavior, safe customizations, troubleshooting, and a comparison with similar solutions.

Special attention is given to the things that most often ruin the impression of a Joomla template: installing quickstart over an existing site, assigning the wrong template style to a menu item, leaving the resource plugin disabled for Extra Add-ons, choosing a font that does not support Cyrillic, applying overly aggressive CSS/JS compression, and creating mismatches between template settings and SP Page Builder pages.

What This Template Actually Gives You and Where It Works Best

Agency was designed as a portfolio template for visually driven services: design studios, art direction teams, photographers, small agencies, freelancers, brand teams, and similar projects where the hero section and project gallery matter more than a long catalog. The official page makes it clear that the template is built on Helix Ultimate, supports SP Page Builder, includes Extra Add-ons, and comes with a demo package that can be deployed as a ready-to-use site.

The practical value of the template is that it covers three layers of the job at once. The first layer is appearance: a high-contrast hero, a clean portfolio grid, bold typography, and a visually strong presentation of work. The second layer is control: Template Options in Helix let you adjust core header settings, layout, menu, typography, presets, custom code, and advanced options. The third layer is page building: SP Page Builder and additional elements help you edit sections without hand-coding every block.

That is especially useful for an agency site because the standard structure rarely consists of Joomla articles alone. You usually need a hero section, a work showcase, service pages, a gallery, a contact section, and sometimes a blog or store element. Agency gives you the foundation, but the final site quality depends on how carefully you replace the demo content, assign menus, check module positions, and avoid breaking responsive settings.

A strong use case for WarpTheme Agency Pro is a new website or redesign where you can deploy quickstart on a clean setup, study the demo, and then replace the materials. It is harder to use the template on an older site with a large number of extensions. In that case, it is usually better to install the standard template package, enable it on a test menu item, and move sections over gradually.

Who This Template Is a Good Fit For

This template is especially useful if you need a site with a strong visual identity but do not want to build a custom Joomla template from scratch. It works well for people who are ready to edit pages in SP Page Builder, change styles through Template Options, and use Joomla's module system for menus, contact details, supporting blocks, and utility pages.

• Design studios get a homepage centered on visual work and brand style.
• Photographers and art directors can use the portfolio grid as a project catalog.
• Small agencies can build service pages, case studies, and a contact flow without relying on a separate website builder outside Joomla.
• Joomla administrators get a familiar setup: template style, menus, modules, articles, components, and extensions.

When Another Solution Is the Better Choice

Agency is not a good choice just because the demo looks impressive. If you need a store with a large catalog, a user account area, complex filters, a real estate directory, a learning platform, or a site with non-standard business logic, the template may serve only as the visual layer while the real problem still has to be solved with components. In that case, check in advance how the required component looks inside Helix, whether ready-made overrides exist, and whether it conflicts with UIkit, Bootstrap, caching, or minification.

The template can also be more than you need if you are building a simple blog or a two-page brochure site. Agency includes a wide set of options for the header, menu, layout, portfolio, and page builder sections. That is great for a project with a strong visual structure, but it can slow down launch if you do not actually need those capabilities.

Preparation Before Installation: Quickstart or the Standard Template Package

The most important decision before installation is choosing the right package type. WarpTheme provides a standard template package and a quickstart package. These are not two versions of the same ZIP archive - they are two different ways to begin. The standard package is installed into an existing Joomla site through System -> Extensions -> Install. Quickstart is a full demo site that includes Joomla, the template, extensions, and sample data.

Quickstart cannot be installed inside an already running Joomla site. It is meant for a clean environment: a separate folder, a separate database, and then either a normal Joomla installation process or a demo package restore. This is convenient if you want a site that closely matches the demo and then plan to replace the content, images, menus, and text step by step.

If the site already exists, it is safer to install the standard template package, create a test template style, assign it to a hidden menu item or a copy of a page, review the result, and only then make it primary. That approach is slower, but it avoids mixing demo data into production content and does not require moving your existing extensions into a new quickstart setup.

What to Check Before Installation

Do not start by uploading the archive straight to the live site. Run a short technical check first. It takes less time than troubleshooting a white screen, a broken grid, or an inaccessible admin panel afterward.

• Check Joomla and PHP version compatibility against the official template page and WarpTheme requirements.
• Create a backup of the files and database if you are working with an existing site.
• Make sure you have access to File Manager or FTP/SFTP in case of a permissions issue.
• Confirm that the chosen installation method matches the task: quickstart for a new site, the standard template package for an existing one.
• On a staging copy, disable aggressive minification from third-party cache plugins so you can first see the template's clean behavior.
• Prepare real portfolio images in a consistent format: matching dimensions, file weight, alt text, and project names.

If the goal is to get a site that looks as close as possible to the demo, quickstart is almost always faster. If the goal is to carefully refresh the look of an older Joomla site, start with the standard template package and assign it to a separate test menu item.

What to Preserve Before Redesigning an Existing Site

For a working site, do not save only the database and files. Also export or document your current template styles, the list of module positions, module-to-menu assignments, custom CSS/JS adjustments, cache settings, language overrides, and the list of extensions that output content on the homepage. These are the details most likely to get lost when switching templates.

If the current homepage is built from modules, create a table in advance with the module, position, display order, assigned pages, and page role. After enabling Agency, you will be able to recreate that structure in Layout Builder or replace part of the modules with SP Page Builder sections.

Installation and the First Review in Joomla

The standard template installation goes through the Joomla admin panel. Open System -> Extensions -> Install, select the template package ZIP file, and run Upload & Install. After installation, open System -> Site Template Styles, select the Agency style, and assign it either as the default or only to a test menu item.

Do not rush into changing all settings right away. First, make sure Joomla sees the template, the admin panel opens Template Options, the public site does not throw errors, and the core CSS/JS files load without conflicts. If you are redesigning an existing site, assign the template to a separate menu item, such as a hidden test page. That lets you see the real result without breaking the homepage.

Review After Installing the Standard Template Package

After uploading the standard package, run this short verification path:

1. Open System -> Site Template Styles and confirm that the style appears in the list.
2. Select the style and click Template Options to open the Helix panels.
3. Check that the panel includes the sections Basic, Presets, Layout, Menu, Typography, Blog, Custom Code, and Advanced.
4. Assign the template to a test menu item and open the page in incognito mode.
5. Check the browser console only for obvious CSS/JS loading errors, not every warning.
6. Save Template Options without changing anything and refresh the page to make sure write permissions are not blocking saves.

If the site looks too empty, that is not necessarily an error. The standard template package does not bring in demo articles, modules, or pages. It gives you the visual layer and settings, while the content must be built separately. That is normal behavior and the main reason quickstart is often better for new projects.

Review After Installing Quickstart

Quickstart is deployed as a separate Joomla build. After extracting and installing it, open both the public site and the admin panel. First, verify that the demo really matches the expected look: header, menu, hero, portfolio grid, inner pages, contact section, and responsive states. Then check which components and plugins were installed with the demo so you understand exactly what each block is built with.

Quickstart is useful for learning: you can open a demo page, find the matching item in SP Page Builder or the module list, inspect the settings, and repeat the same logic on your own page. But it also carries a risk: demo content is easy to leave in a production site by accident. After replacing text and images, review all menu items, hidden pages, metadata, contact details, email addresses, social links, and the footer.

Template Options Panels: What to Open First

Most Agency configuration happens through Helix Ultimate Template Options. This is not a single page full of random toggles, but a set of panels, each responsible for a separate layer: basic structure, presets, layout, menu, typography, blog, custom code, and advanced settings. To avoid getting lost, it is better to configure the template based on the site's working logic rather than simply moving top to bottom.

Start with identity: logo, header, contact details, social icons, and the base preset. Then review the layout: where the main body appears, which positions are needed for modules, and how the sections are arranged. After that, move on to the menu, typography, and SP Page Builder pages. Leave optimization, custom CSS, and extra scripts for the end.

Core Settings and the Header

In the Basic section, review the logo, header, toolbar, mobile settings, page title, body, footer, contact info, coming soon page, and error page. For an agency website, the logo and header matter most. In the Agency demo, the header feels light: logo on the left, menu items on the right, and an accent color used only on the active item. If you upload a heavy logo, add too many menu items, or enable unnecessary toolbar elements, the top section will lose the mood of the reference design.

Keep the header short. For the first launch, menu items such as "Home," "About," "Services," "Portfolio," "Blog," and "Contact" are enough. If you have more sections, use a dropdown or mega menu instead of stretching the horizontal menu across two lines. Also check the mobile navigation separately: Helix offers multiple mobile menu options and breakpoints, so it is important to review the result somewhere other than desktop alone.

Presets and the Color System

The Presets section controls the color foundation. WarpTheme notes that presets let you quickly switch between ready-made palettes and then refine the styling. For Agency, the goal is not simply to choose a "nice" color, but to preserve the character of the demo: black-and-white visual presentation, a large hero image, restrained accents, and clean portfolio cards.

If the site is in Russian, check the chosen color not only on the homepage but also in Joomla system areas: the contact form, messages, pagination, search results, blog pages, and login screens. A common mistake is choosing an accent only for the hero and then ending up with buttons or links that are hard to read on inner pages.

Typography and Cyrillic Support

In Typography, you can configure fonts for the body, navigation, headings, and specific selectors. WarpTheme documentation specifically warns that not all Google Fonts include the national character sets you may need. For a Russian-language site, this is critical: if the selected display font does not support Cyrillic, the browser will fall back to another font, and the entire visual character of the homepage will change.

Before publishing the Russian version, check Cyrillic in headings, menus, buttons, and portfolio cards. If the font breaks characters or looks radically different from the Latin version, choose a family with Cyrillic support or use a system font for the body while keeping the decorative accent only where it does not interfere with readability.

Advanced: When to Enable Optimization

The Advanced section includes compression, lazy loading, Font Awesome, the Google Fonts list, analytics, settings import/export, and other technical options. These settings are useful, but they should not be enabled before the base build is finished. First get the correct visual result without optimization, then enable features one at a time and test the result.

If turning on compression breaks animation, the menu dropdown, or the gallery, temporarily disable compression and check for a conflict. This matters even more for Agency, where UIkit, SP Page Builder, and Extra Add-ons may all be involved. Not every visual element handles bundled and minified files equally well.

Layout Builder and Module Positions: How Not to Lose the Page Structure

Agency is built around the Helix workflow, where Layout Builder connects template sections to Joomla module positions. WarpTheme documentation describes Layout Builder as a 12-column Bootstrap structure where you can add sections, choose a grid, and assign positions. This is a key area for any administrator moving a site from another template or trying to display extra blocks around the main body.

The point of Layout Builder is not to drag blocks around every time for appearance alone. It is there so you can understand where Joomla will output modules, the main body, breadcrumbs, the footer, top panels, and extra sections. If that map does not match your module assignments, the site can look "empty" even when the modules are published.

How to Work with Positions Without Creating Chaos

Start from the current page structure. For the Agency homepage, the most important areas are usually the header, the hero/page builder area, the portfolio/content area, the footer, and contact blocks. If you are using quickstart, part of that structure is already assembled. If you are installing the standard template package on an existing site, you need to map the old positions to the new ones.

A practical order looks like this:

1. Open the Joomla module list and filter to published modules.
2. Write down their positions and menu assignments.
3. Open Template Options -> Layout and find which positions are actually rendered in the current style.
4. Assign one test module to the target position first.
5. Check the page, and only then move the remaining modules.

Do not move everything at once. If something disappears after a bulk move, it becomes difficult to tell whether the cause is the layout, menu assignment, cache, ACL, language settings, module publishing state, or the template style.

A New Module Position

WarpTheme documentation shows that new positions can be added through templateDetails.xml and then assigned in Layout Builder. This is already a technical customization, so it should not be done for every minor block. Still, it is useful when the design needs a separate utility layer, such as a partner block between the portfolio and contact sections, a dedicated CTA panel before the footer, or a standalone notice area.

The safe approach is this: first check whether an existing position will work. If it will not, create a new position on a staging copy, add it to the layout, assign one test module, and verify the result. After a template update, always review that file because direct edits to template files may be overwritten. For simple visual tweaks, it is better to use custom.css than to modify compiled CSS.

Menu Assignment and Multiple Style Variants

Joomla lets you assign different template styles to different menu items. That is useful if the Agency homepage should have a high-contrast hero while inner pages need a calmer header and a different page title. But it is also easy to create an error here: a menu item may still point to an old or deleted template style. When that happens, Helix may report a problem with the default layout.

If you use multiple style variants, manage them as a deliberate set of profiles: Agency - Home, Agency - Inner, Agency - Landing. Do not create dozens of copies without assignments. Before updating the template, export the settings if you use import/export, and document which menu items depend on which style.

Header, Menu, and Portfolio: A Practical Flow for a Creative Agency Site

Agency's strength is its visual homepage. The attached reference makes that clear: minimal navigation at the top, then a large monochrome hero with the phrase "Design & Art Direction.", followed by an "Our Creative Portfolio" block and a project grid. If you replace that with a random set of sections, the template loses its point. That is why the homepage should be configured around the user journey, not around a list of available elements.

Goal of the Practical Example

Let us build a typical homepage for a creative studio: a hero section with clear positioning, a simple menu, a portfolio of six projects, a short services block, and a contact transition. This is a good demonstration scenario for Agency because it uses exactly the elements people choose the template for: a strong visual presentation, a portfolio grid, and clean navigation.

Preparation

You need Agency installed, access to Template Options, a working SP Page Builder setup, the required Extra Add-ons enabled, prepared project images, and a page list. If the site was created through quickstart, use the demo as a learning base: find the homepage, make a copy, and edit the copy. If the site already exists, create a new page and assign it to a test menu item.

Steps for Setting Up the Homepage

1. In Menus, create or verify menu items for the homepage, portfolio, services, team/about page, and contact page.
2. In Template Options -> Basic -> Header, keep the header compact and check the logo on both dark and light backgrounds.
3. In Template Options -> Presets, choose a base palette and do not change every color at once. First check link and button accents.
4. In SP Page Builder, open the homepage, replace the hero text with the studio's real positioning, and upload your own image.
5. In the portfolio section, replace the demo cards with real projects while keeping image proportions consistent.
6. Add a short services block below the portfolio, but do not overload the homepage with long descriptions. Detailed information is better placed on separate pages.
7. Check the mobile view using both preview controls and a real browser: the hero, menu, project grid, and footer should remain readable without horizontal scrolling.

Result Check

The result is working if a visitor can understand within a few seconds who you are, what work they can review, and where to click next. On desktop, there should not be empty visual gaps between the hero and the portfolio. On mobile, the menu should open predictably, large text should not spill out of bounds, and the portfolio cards should keep their order.

Do not review only the attractive hero section. For Agency, the full chain matters: the hero grabs attention, the menu explains the structure, the portfolio proves competence, and the contact block gives the next step.

SP Page Builder and Extra Add-ons: How to Edit the Demo Without Losing Its Logic

The official Agency page and WarpTheme documentation tie the template to SP Page Builder and Extra Add-ons. That means many of the demo's expressive blocks may be built not with standard Joomla articles, but with page builder sections. If an administrator looks for the hero or portfolio only in the module list, they may conclude that the content is "hidden." In practice, you need to inspect the page in SP Page Builder and see which sections and elements are actually being used.

Extra Add-ons expand the set of elements available in SP Page Builder, but some features require the UIkit Assets resource plugin. WarpTheme documentation says this plugin should be installed and enabled if you are starting from the standard template package or using the template on an existing site. At the same time, for WarpTheme templates the Enable UIkit Framework setting is recommended to stay disabled because the template already includes UIkit.

How to Edit Demo Sections

Work with sections as logical blocks. Do not delete everything just to start from a blank page until you understand how the page is built. Open a section, inspect its row/column structure, background, spacing, responsive settings, and the add-ons it uses. Then replace content one layer at a time: text, image, link, order, spacing.

Image consistency matters especially in the portfolio. If one image is horizontal, another vertical, and a third too small, the grid will feel random. Prepare the images in advance and compress them to a sensible size. Agency's visual style depends on cleanliness, so poorly processed images damage the template more than a slightly imperfect button color.

What to Do If Extra Add-ons Do Not Appear

If part of SP Page Builder stops working after installing the standard template package, check dependencies before you check the page itself. Make sure the required Extra Add-ons package is installed, System - Extra Addon Assets is enabled, and the Joomla cache has been cleared. Then reopen the page in edit mode and verify that the needed elements appear in the add-ons panel.

If you are using quickstart, dependencies are usually already installed and configured. But after updates or after moving the site to a different server, the plugin may be disabled, files may have incorrect permissions, and the cache may still serve an old CSS/JS version. That is why troubleshooting should always start with the basics: plugin publish state, file permissions, cache clearing, and the browser console.

Where the Line Is Between the Page Builder and Joomla Modules

On the homepage, it makes sense to build large visual blocks with SP Page Builder. But utility elements are better left in Joomla modules: menu, language switcher, breadcrumbs, login, footer menu, contact details, and search. That keeps the site manageable: the editor updates the page, the administrator controls system areas, and the template style controls the overall framework.

If everything is moved into a single page builder page, the site may become attractive but less predictable. For example, the footer may have to be copied across pages, language versions become harder to maintain, and switching template styles may not produce the expected effect. For Agency, a mixed model works best: visual sections in SP Page Builder, navigation and reusable areas through Joomla and Helix.

Responsive Behavior, Performance, and SEO Review After Setup

A visual template should not be considered configured until the public side of the site has been reviewed. For Agency, this matters even more because of the large hero, portfolio grid, work images, mobile menu, and possible animations. A desktop issue may be barely noticeable, while on mobile it can completely ruin the top section.

Responsive Behavior

Do not settle for an abstract "the mobile version exists." Check specific elements. Open the homepage, portfolio, service page, blog article, and contact page. Make sure the menu opens correctly, the hero text does not cover an important part of the image, buttons are large enough, the portfolio grid does not create horizontal scrolling, and the footer does not turn into a long chaotic list.

Template Options and SP Page Builder include preview and responsive controls, but the final review still has to happen in a browser. The editor may show one width, a real phone another, and cache or compressed files may introduce a third behavior entirely.

Performance

Agency may look lightweight, but portfolio sites often suffer from heavy images. Do not start optimization by turning on every compression toggle. First reduce image weight, check hero and portfolio dimensions, remove unneeded demo sections, and disable extensions you do not use. Then enable lazy loading, CSS/JS compression, or third-party caching one by one.

If optimization breaks dropdown menus, the gallery, animations, or front-end editing in SP Page Builder, return to the last working configuration. It is better to isolate the problem than to leave the site in a "mostly works" state.

SEO and Small Technical Details

The template itself does not replace basic Joomla SEO setup. Check SEF URLs, page metadata, image alt text, headings, the Open Graph image, the error page, robots.txt, and the sitemap through your chosen extensions or Joomla's built-in tools. On a portfolio site, meaningful project pages matter especially: each project should have its own context, not just an image inside a grid.

For the Russian version, review the title and description not only on the homepage, but also on portfolio, services, and contact pages. If the demo content was in English, it may still remain in metadata, alt text, module titles, the footer, or hidden fields. That is not a template bug, but it is a common launch mistake.

Inner Pages, Blog, and Utility Screens

The Agency homepage usually gets more attention than everything else. That makes sense: the hero and portfolio create the first impression. But a real agency website does not live on the homepage alone. Users open service pages, view projects, read short articles, submit a contact form, land on an error page, or look for information through search. If those areas look like plain default Joomla without the same visual logic, the site feels unfinished.

That is why, after setting up the hero and portfolio, you should review the inner templates. In Agency, Helix controls the outer layer, while content may come from Joomla articles, SP Page Builder, the contact component, third-party forms, blog categories, and modules. The administrator's job is not to make every page look identical, but to preserve a consistent rhythm: the header, spacing, headings, buttons, cards, footer, and menu behavior should all feel recognizably connected.

Service Page

For a service page, do not recreate the homepage in miniature. Keep the structure simpler: a short opening block with the service name, two or three paragraphs explaining the task, a list of what is included, an example result, a question block, and a contact transition. If the page is built in SP Page Builder, do not use too many different add-ons. A few stable patterns are enough: a text block, an image, a benefits list, step cards, and a CTA.

Check the service page like a user would. They did not come to admire the template - they came to decide whether your team fits the job. The headline should be specific, the portfolio link should sit near the explanation, and the contact transition should come after the value is clear. If the page looks impressive but does not answer real questions, the template will not save conversions.

Project or Case Study Page

A portfolio card on the homepage is only the entry point. For a strong result, every important project should have its own page: the task, the team's role, visual materials, phases, outcome, and a contact link. In Joomla, that page can be built as an article, an SP Page Builder page, or a combination of an article and modules. Choose the option that will be easiest for the editor to maintain.

If you have many projects, do not turn every page into a unique design. Create a repeatable structure and use it as a template. For example: project hero, short context, gallery, three or four key facts, final result, and related projects. That saves time and makes it easier for users to compare work. Inside Agency, this approach is especially appropriate because the base visual concept already relies on a clean portfolio grid.

Blog and Joomla Articles

The Blog section in Template Options controls blog- and article-related layout settings. For an agency, the blog does not have to be a news feed. It can work as a section for project breakdowns, process notes, answers to common client questions, and technical articles. The key is not to leave default demo headings, unnecessary metadata, or images in the wrong size.

Check the category blog view, single article view, pagination, intro/full article images, date, author, tags, and "Read more" buttons if they are used. If the blog contains Russian text, review long-word wrapping, line height, and font size. The oversized hero typography from the homepage does not always work for long-form reading. For articles, a calmer rhythm, a sensible text column width, and strong link contrast matter more.

Contacts, Forms, and System Pages

The contact page often breaks the visual consistency: the form comes from a component, the map from a module, the address from custom HTML, and the button looks different from the one on the homepage. Bring the form into the template style: check the fields, spacing, labels, error messages, success state, and mobile behavior. If you are using a third-party form builder, check its CSS compatibility with UIkit and Bootstrap.

Do not forget utility pages: error, offline/coming soon, login, user profile, and search results. The official Agency changelog includes fixes related to user profile, media editing, search, contact handling, and override logic, so these areas should not be ignored. They rarely appear in the demo, but they are exactly where users notice how carefully a site has been put together.

Final Review Path Before Launch

Before the final launch, go through the site like a visitor, not an administrator. Open the homepage, move into the portfolio, open a project, return through the menu, visit a service page, submit a test form, open a blog article, check search, and view the error page. Repeat that path at mobile width. If the user loses context at any point, go back to the template style, layout, menu, or the specific page.

A well-configured Agency setup is not just one attractive screen, but a connected chain of pages. That is why it makes sense to configure the overall framework in Template Options first, then build the homepage, then bring the inner pages into the same rhythm, and only after that enable final optimization.

Safe Improvements Without Editing the Template Core

WarpTheme documentation outlines several safe paths for custom work: Custom Code, the custom.css file, custom.js, and custom.scss. The main principle is simple: do not edit compiled CSS or the main template files if the change could be lost during an update. For small visual tweaks, use custom CSS. For more substantial work, use a staging copy and keep changes under control.

A Small CSS Tweak for Portfolio Cards

If portfolio images look uneven because of different proportions, preparing the images properly is still the best first step. But sometimes you need to smooth out the visual rhythm of the cards without changing the source files. This CSS can be added to templates/template_name/css/custom.css or to the custom CSS field if that is part of your workflow.

.agency-portfolio-grid img {
  aspect-ratio: 1 / 1;
  object-fit: cover;
}

.agency-portfolio-grid .portfolio-title {
  min-height: 2.4em;
}

This example does not depend on a private template API and illustrates a safe idea: normalize the image and caption height at the CSS level. Before using it, replace the selectors with the real classes from your portfolio section. Do not paste the code blindly if those classes do not exist. The review is straightforward: clear the cache, open the homepage, compare the portfolio on desktop and mobile, then remove the CSS if needed and confirm that the original appearance returns.

Local Fonts Instead of External Requests

If the project requires avoiding external Google Fonts requests or the selected font handles Cyrillic poorly, use a local font workflow instead. WarpTheme documentation describes adding files to the TEMPLATE_DIR/fonts folder and connecting them through custom.scss. That is a cleaner approach than dropping third-party CSS links into the head without control.

A practical order is this: choose a font with Cyrillic support, download a webfont kit from a reliable source, place the files in templates/template_name/fonts, connect them in custom.scss, and then assign the font-family to the body or headings. After that, check Russian headings, Latin text in the logo, navigation, the contact form, and Joomla system messages.

Import and Export of Settings

Before making serious changes in Template Options, use the settings export feature if it is available in your version. The documentation notes that export saves the settings structure to JSON, but not the actual images - only their links. That matters: export can help you roll back the layout, presets, and part of the configuration, but it does not replace a full backup of files and the database.

The best order for safe changes is to create a backup, export the template settings, apply one group of changes, verify the result, and only then move to the next group. That way, you can tell which setting produced the effect or caused the problem.

Troubleshooting Common Problems After Installation and Editing

Problems with a Joomla template rarely show up as one obvious error. More often, the user sees "it does not look like the demo," "it will not save," "blocks disappeared," "the menu broke," or "the page turned blank." For Agency, troubleshooting is easiest when you follow the chain: installation type, template style, layout, modules, SP Page Builder, Extra Add-ons, cache, and file permissions.

The Site Does Not Look Like the Demo After Installation

Symptom: the template is installed, but the homepage is empty or looks like a standard Joomla site without the portfolio and hero.

Cause: the standard template package was installed instead of quickstart. The standard package does not include demo pages, modules, content, or preconfigured extensions.

What to check: which archive was installed, whether demo pages exist in SP Page Builder, which modules are published, and whether Agency is assigned as the template style for the correct menu item.

How to fix it: for a new site, deploy quickstart on a clean setup. For an existing site, build the homepage manually in SP Page Builder and assign the required modules to the template positions.

"Default Layout file is not exists" Error

Symptom: Helix reports that the default layout file does not exist or the page does not render correctly.

Cause: WarpTheme documentation links this error to special menu items with an incorrect template style ID after a template was removed or changed.

What to check: open the affected menu item, review the details tab and its template style assignment. Check whether the item still points to an old style.

How to fix it: open the menu item and save it again so Joomla refreshes the template style ID. If multiple Agency style variants are used, explicitly assign the correct one.

Extra Add-ons or Some Effects Do Not Work

Symptom: the element exists in SP Page Builder, but does not display on the site the way it does in the demo, or the gallery, counter, lightbox, or visual effect does not work.

Cause: the resource plugin is not installed or enabled, the cache is serving old files, minification is conflicting, or the element was removed from the page.

What to check: the presence of Extra Add-ons, the status of System - Extra Addon Assets, UIkit assets settings, Joomla cache, third-party optimization, and the browser console.

How to fix it: enable the required plugin, clear the cache, temporarily disable CSS/JS compression, and check the element again. For a WarpTheme template, do not enable extra UIkit loading if the template already includes it.

Settings Will Not Save

Symptom: Template Options opens, but after saving the settings revert or a write error appears.

Cause: file or directory permissions may be wrong. WarpTheme recommends following the standard scheme: directories with 755 permissions and files with 644, unless your hosting environment requires a different secure mode.

What to check: permissions on the template folder, Joomla's ability to write configuration files, file ownership after migration, and messages in the admin panel.

How to fix it: reset permissions to safe values through the hosting panel or your server administrator. Do not use overly broad permissions such as 777 as a permanent solution.

Cyrillic Looks Worse Than the English Text

Symptom: Russian headings appear in a different font, break line height, or look visually weaker than the demo.

Cause: the selected Google Font may not support Cyrillic, or the needed subset is not enabled.

What to check: Typography settings, Cyrillic support in the selected font, and how the menu, buttons, hero, and portfolio are rendered.

How to fix it: choose a font with Cyrillic support, use a system font, or connect a local font through the documented custom font workflow.

The Header or Gallery Breaks After Optimization

Symptom: after enabling compression, the dropdown stops opening, animations disappear, or the portfolio looks different.

Cause: a conflict between CSS/JS bundling or minification and UIkit, SP Page Builder, Extra Add-ons, or a third-party cache tool.

What to check: the last enabled setting, the browser console, file loading order, and exclusions in the cache plugin.

How to fix it: disable the problematic optimization, clear the cache, and enable settings one by one. If a compromise is needed, exclude the conflicting file from bundling if your tool supports that.

When WarpTheme Agency Pro Is the Right Choice

WarpTheme Agency Pro is a strong choice if you need a visual Joomla site for an agency, portfolio, or creative project rather than just another generic theme. The template works best when you preserve its core strengths: a large hero section, a clean header, a portfolio grid, clean typography, controlled color presets, and a clear page structure.

Before launch, run a final review: the correct installation type is chosen, demo content has been replaced, the menu is assigned, modules are published in the right positions, SP Page Builder opens the pages, Extra Add-ons work, Cyrillic is readable, images are optimized, the mobile menu has been tested, and compression is not breaking scripts. After that, you can move on to testing on the live domain and get the Joomla version if you have not downloaded the archive yet.

If the project requires a complex catalog, a non-standard component, or deep custom development, start with a staging copy and check compatibility before redesigning. If the goal is to build an expressive studio or portfolio site in Joomla quickly while leaving the administrator with understandable settings, Agency is a logical option.