JoomShaper Maxora - Joomla Template

How to Set Up JoomShaper Maxora for a Joomla Agency Website

It makes more sense to look at JoomShaper Maxora not as a finished pretty page, but as a working kit for building an agency website: a quickstart with a demo structure, a standalone Helix Ultimate template, SP Page Builder Pro pages, menus, module positions, and portfolio content. In this guide, we will walk through how to approach the installation safely, what to check after launch, where to change the visual design, and how to preserve the demo logic when replacing the content.

This guide assumes you have already read the short product description higher up on the page. What follows is the practical part: how the quickstart differs from the regular template package, how to configure the template style, where pages are edited, how to publish modules in the right positions, how to test the mobile menu, and which issues most often prevent you from seeing the expected result.

Maxora is built around Joomla, Helix Ultimate, SP Page Builder Pro, and SP Simple Portfolio, so this is not about a single install button - it is about how several layers work together. First, you need to understand which layer controls which result on the site: the template defines the overall framework, Helix manages the header, layout, footer, menu, and custom code, SP Page Builder handles page editing, and Joomla modules render individual blocks in their assigned positions.

What the Template Is Good For and Where It Works Best

Maxora is designed for websites that need to showcase team expertise, services, case studies, a blog, and a contact funnel. The official page makes it clear that the template targets digital marketing, branding, web design, and consulting sites, and the package includes several homepage variations, plus service, team, portfolio, blog, and contact pages. This is not a universal product catalog or a complex portal - it is a strong starting point for a presentation-focused agency website.

The practical value of the template is that it already connects visual sections with common agency goals. At the top of the demo, you can see a bold hero, navigation, a trust-building block, service cards, and high-contrast CTAs. That rhythm works well for a page that needs to quickly explain the business direction, show specialization, and guide the visitor toward an inquiry or portfolio view.

When Maxora Saves Time

The template is especially useful when you do not want to build the site from scratch, but from a ready-made structure. The quickstart installs a demo website with Joomla, the template, Helix settings, SP Page Builder Pro, and demo data. That helps you see which pages, modules, and positions are already connected. From there, the site owner can replace the demo content with real services, case studies, team copy, and contact details.

If the site has already been running for a long time and contains a large amount of custom content, the quickstart is not suitable for installing into the current Joomla instance. In that case, the standalone template package is the better fit, but you need to understand the limitation: it does not include the demo modules, pages, or ready-made structure. You will need to rebuild those manually.

When the Template May Be More Than You Need

Maxora may be excessive for a small one-page brochure site that does not need a portfolio, service pages, team pages, or a blog. It also does not replace a specialized component for eCommerce, booking, an LMS, or a member portal. Those features can be integrated into Joomla separately, but the template itself is primarily focused on the visual and presentation layer.

The main decision rule is simple: if you need an agency website with multiple landing pages, a portfolio, and a polished menu, Maxora gives you a strong starting point. If you need a complex functional service, the template will only handle the front-end layer, while the core business logic will still require separate extensions.

Who Maxora Fits Best - and Who Should Choose a Different Route

Maxora has a clear strength: a ready-made design system for an agency website. The black background, bright blue accent, oversized headings, geometric patterns, and image-based sections create a distinct visual identity. That works well for a branding studio, marketing team, web agency, consultancy, service portfolio, or a small business that needs a modern presentation site without building a custom template from scratch.

For a content editor, the template is convenient because the main quickstart pages are built in SP Page Builder. That means much of the structure can be changed through a visual editor without touching PHP files. But that also creates a dependency: if your team deliberately does not want to use a page builder, it is better to estimate in advance how much work would need to be moved into standard Joomla articles.

Good-Fit Scenarios

• An agency wants to launch a site quickly with ready-made service, team, portfolio, blog, and contact pages.
• A webmaster needs to show a client a working prototype first, then gradually replace the demo text and images.
• The team already uses Helix Ultimate or SP Page Builder and understands the logic of template styles, modules, and menus.
• The site is being built from scratch on a separate staging domain or subdomain, where the quickstart can be installed safely.

Questionable Scenarios

• You need to install the demo site on top of an existing Joomla site without migrating content. The quickstart is not built for that.
• You need a fully custom design system with no visible connection to the Maxora demo.
• The site must run without SP Page Builder, and every page has to be a standard Joomla Article.
• The hosting environment does not meet the PHP, memory, upload size, execution time, or database requirements.

Practical takeaway: Maxora is worth choosing when the visual direction of the demo already fits your goals and you are comfortable working with the Joomla, Helix Ultimate, SP Page Builder, and module position stack.

Installation Packages: quickstart, template package, and the Right Working Strategy

The Maxora documentation clearly separates the quickstart and the template package. These are fundamentally different options. The quickstart is a full demo website: it already includes Joomla, the template, components, modules, Helix Ultimate settings, and demo data. The template package is only a standalone Helix Ultimate template that controls the look and layout, but does not include ready-made pages, modules, or demo content.

The most common mistake with Joomla templates is trying to install the quickstart through System and the extension manager on an existing website. JoomShaper's documentation explicitly warns that the quickstart includes the Joomla core and is meant for a fresh installation. If you already have a live site, deploy the quickstart separately: on a staging domain, subdomain, local environment, or in a separate folder and database.

How to Choose the Right Package

For most users, the best path is this: install the quickstart in a staging environment, study the demo structure, and then decide whether to migrate the whole site or carefully recreate only the parts you need in your production Joomla setup. Do not start on a live site without a backup and a clear rollback plan, because the template affects the visual design, modules, menus, CSS, and builder pages.

What to Check Before Installation - and Why It Affects the Outcome

Preparation is not just a formality. If the server does not meet the requirements, the quickstart may fail during installation, a large package may not upload, and SP Page Builder or media files may save unreliably. The Maxora documentation lists requirements for PHP, memory, upload sizes, execution time, MySQL or MariaDB, cURL, OpenSSL, and the file_get_contents() function. Depending on the version, SP Page Builder may require even stricter settings.

Basic Hosting Check

Before installation, open your hosting panel and review the PHP settings. For the quickstart, the most important values are memory_limit, post_max_size, upload_max_filesize, and max_execution_time. If the archive is large, a small upload limit will trigger an error before Joomla even begins installation. If the execution time is too short, the installer may fail while extracting files or creating database tables.

Also check the database. It is best to deploy the quickstart into a new database, or into an existing one with a new prefix only if you fully understand the risk. In day-to-day practice, it is simpler and safer to create a separate database for the staging installation than to untangle later which tables belong to the demo.

Backup and Staging Environment

If you are installing only the template package on an existing site, back up both the files and the database. The template may add its own component view overrides, and the template style settings may change how pages are rendered. The backup needs to be restorable in practice: downloading a single archive is not enough if you do not know how to restore it.

What to Prepare on the Content Side

Maxora is visually strong because of its large headings, high-contrast sections, and imagery. Before replacing the demo, it helps to gather the following: a list of services, short descriptions, 3-6 case studies, team photos or neutral branded visuals, contact information, links to social profiles, and CTA copy. Without that, the site often keeps the demo rhythm but loses its meaning.

Pre-launch check: if you cannot name the new database, the install path, the rollback method, and the list of pages you will change first, it is better to move the installation to a staging environment.

Installation and the First Checks After Launch

For a new site, the quickstart installation looks similar to a standard Joomla installation. You extract the package, upload the files to the chosen folder, create the database, open the domain or subdomain in a browser, and complete the installation wizard. After a successful install, remove or rename the extra installation files as instructed, log into the admin panel, and open the public-facing site.

One important security detail: do not use admin as the super user name during installation. This is a basic recommendation from both JoomShaper and Joomla documentation, but people often skip it in staging and then move the site into production without fixing it.

Initial quickstart check

1. Open the homepage and compare the top section to the demo: logo, menu, hero, CTA, and service block.
2. Go to the admin panel at /administrator and confirm that login works.
3. Open Components - SP Page Builder Pro - Pages and make sure the quickstart pages appear in the list.
4. Open System - Templates - Site Template Styles and locate the Maxora style.
5. Check Content - Site Modules to see the modules assigned to the template positions.
6. Clear the Joomla cache if the front end still shows the old look after you change settings.

If You Installed Only the Template Package

After a standalone installation, do not expect a full copy of the demo. The admin panel will show the template and template style, but the SP Page Builder pages, footer modules, portfolio data, and menus need to be created or migrated separately. That is normal behavior, not an installation error. This approach works well for an experienced administrator who wants to preserve the current site and gradually bring in Maxora's visual design.

To stay organized, create a simple mapping table: which page should become the homepage, which menu item points to it, which modules belong in the header, footer, top bar, and other positions, which pages will be built in SP Page Builder, and which ones will remain standard Joomla Articles.

Configuring the Template Style, Header, Layout, and Footer in Helix Ultimate

After installation, the main control center for the site's framework is the template style. The Maxora documentation gives the menu path as System - Templates - Site Template Styles - select maxora default - Template Options. Inside Helix Ultimate, you are not working with a single page, but with rendering rules: header, layout, footer, typography, menu, custom code, and responsive behavior.

Header and predefined header

The Maxora documentation notes that the template uses a Minimal Layout header, and that Helix lets you enable a predefined header and switch to another option. In practice, do not make major header changes right away. First, check the logo, main menu, contact button, mobile/off-canvas behavior, and top bar if you need one. Then decide whether you actually need to build a custom header through the layout builder.

If you change the header, do not test only on desktop. Open the site at a narrow browser width and make sure the off-canvas menu opens properly, the menu items are readable, the CTA does not overlap the logo, and the header height does not eat up the first screen. This matters even more in Maxora, where the hero depends on bold typography and strong contrast.

Layout Builder and module positions

Helix Layout Builder works with rows and columns on a 12-column Bootstrap grid. The documentation explains that rows, columns, module positions, responsive options, and grid breakpoints can all be changed without editing code. That gives you flexibility, but it also requires discipline. If you remove a position, the module may still be published in Joomla but stop appearing on the site.

Before making serious layout changes, create a copy of the template style or at least document the current structure: which positions are used in the header, which are used in the footer, where the component area sits, and where the extra rows are. If something disappears, first check whether the position still exists in the layout, then review the module status and menu assignment.

Footer and copyright

In Maxora, the bottom area uses SP Page Builder modules in positions footer1 and footer2. That means part of the footer content may be edited not only in the template options, but also through modules. The copyright note is enabled and disabled in Helix under Basic - Footer. If the bottom area is not changing, check both levels: the footer settings in Helix and the specific Joomla modules.

Pages, Sections, and Content in SP Page Builder Pro

The Maxora quickstart includes several ready-made homepages and other pages that can be edited in SP Page Builder Pro. JoomShaper's documentation gives the path as Components - SP Page Builder Pro - Pages, then choose the page you need. For an editor, this is the key section, because this is where you change the hero sections, services, benefits, team, portfolio, forms, and part of the internal page content.

How to Edit Without Breaking the Visual Rhythm

Do not start by deleting every section. In Maxora, the visual rhythm comes from alternating dark and light blocks, the blue accent, large headings, cards, and imagery. It is better to replace the text and images inside the existing sections first, then remove any blocks you do not need, and only after that rebuild the layout. That order preserves the proportions and helps you get to a polished result faster.

A useful working habit: before editing an important page, export it using SP Page Builder if that option is available in your version. The SP Page Builder documentation describes export as a way to reuse pages, modules, or article content, but make sure the new site includes the same add-ons and the required images.

Page Settings and the SEO Layer

SP Page Builder pages include settings for title, status, language, access level, page CSS, and SEO. Do not use those settings as a substitute for a clear content structure. Title and metadata help with the search snippet, but the real value of the page still needs to be in understandable sections, headings, and copy. If the site is multilingual, configure the Joomla languages first and only then assign languages to builder pages.

How to Verify That a Page Saved Correctly

After editing, save the page, open the front end in a new tab, and refresh the cache. If the changes are not visible, check the page status, the menu item, the Joomla cache, and any full page cache. The SP Page Builder documentation explains that Joomla Page Cache can keep serving old HTML and inline CSS until the cache is cleared or expires.

Menu, mega menu, and off-canvas: navigation without surprises

Navigation in Maxora depends on Helix menu settings and Joomla's standard menu system. In Template Options under the Menu tab, you get access to Menu Builder, Mega Menu, and Off-canvas Menu. These solve three different problems: item structure, an expanded dropdown layer, and the mobile menu.

Menu Builder

Menu Builder shows your menu items, including subitems, and lets you manage their additional settings. But the actual meaning of each item still comes from the Joomla menu item: its type, alias, linked page, access level, language, and template style assignment. If a menu item goes to the wrong place, look at the Joomla menu item first, not only at Helix.

Mega Menu

A mega menu is useful when an agency has many services, case studies, or focus areas. Do not turn it into a storage room for every link on the site. A good Maxora structure is 3-5 main groups, short labels, and a clear hierarchy. If the menu becomes too long on mobile, some links are better moved to an internal services page or the footer.

Off-canvas Menu

The Maxora documentation notes that the off-canvas menu controls the appearance and content of the mobile menu, and that by default it is placed on the right with left-aligned content. After configuring it, make sure to test opening behavior on a mobile width, scrolling, nested items, the close button, and CTA visibility. You cannot validate a mobile menu only by looking at it in desktop mode, because the real problems usually show up in width, height, and touch interaction.

Maxora Module Positions and the Common Top Bar Trap

Joomla modules are rendered in positions defined by the template. The official Joomla documentation explains that modules are assigned to positions and can be displayed based on menus and access levels. In Maxora, this is especially important for the header, top bar, footer, and blocks built as SP Page Builder modules.

There is a well-known Maxora support case in the JoomShaper forum: a user created a module for the top bar, but it did not appear. Support clarified that the available positions for the top bar are Top 1 and Top 2. That is a good example of why you should not guess a position name based on the area label. You need to check the documentation, the layout builder, the position list, and the specific support answer if the question is about a template area.

How to Check a Module That Does Not Appear

1. Open Content - Site Modules and confirm that the module is published.
2. Check the Position field: for the Maxora top bar, use the confirmed positions Top 1 or Top 2 if your goal is specifically the top strip.
3. Open the Menu Assignment tab and make sure the module is assigned to the correct pages.
4. Check Access so the module is not hidden from guests.
5. Clear the cache and test the site as a guest.

If the module is published, the position is correct, and the menu assignment is correct, but the block is still missing, go back to Helix Layout Builder. The relevant row or column may be hidden for the current screen width, removed from the layout, or overridden by custom CSS.

Practical Scenario: Build the Agency Homepage from the Demo

This example fits a new agency site where the quickstart is already installed on a staging domain. The goal is to create a working homepage that keeps Maxora's visual strength while showing real services, team information, and a clear path to inquiry.

Goal

You need to configure the homepage so that within the first screen, a visitor understands the agency's specialization, sees the main services, can move to the portfolio, and finds a contact path. We are not rebuilding everything from scratch - we are replacing the demo messaging with real content.

Preparation

• The quickstart is installed in a staging environment, and both the site and admin panel open correctly.
• The hero copy, 4-6 services, short value points, 3-4 case studies, and contact details are prepared.
• You know which Maxora homepage variation will serve as the base.
• You have a backup or an SP Page Builder page export from before editing.

Steps

1. Open Components - SP Page Builder Pro - Pages and select the page assigned as the homepage.
2. Replace the hero headline with a specific promise, but keep the line length close to the demo so the oversized typography does not break the grid.
3. Update the CTA: one button should lead to contact, and the second can lead to the portfolio or services if that section is part of your structure.
4. In the services block, replace the cards with real offerings: strategy, web development, advertising, analytics, support, or other verified company services.
5. Update the portfolio or case study section through SP Simple Portfolio or the related pages, if the portfolio is part of your build.
6. Check the menu: home, services, team, portfolio, blog, contact. Remove extra demo items if those pages do not exist yet.
7. Configure the footer modules footer1 and footer2: contact details, a short description, links, and legal information.
8. Clear the Joomla cache and open the site as a guest.

Verification

After saving, open the homepage on desktop, tablet-width, and mobile-width screens. Make sure the hero does not cut off key wording, the CTA is visible without scrolling, the off-canvas menu opens correctly, the service cards do not collapse into each other, and the footer no longer shows demo contact details. Then walk through the user path: home - service - portfolio - contact.

Important detail

If you still see the old text after editing, do not rewrite the page again right away. First clear the Joomla cache, then confirm that you edited the correct page, that a different homepage is not assigned through a menu item, and that full page cache is not enabled. In practice, cache and menu assignment are what most often create the impression that SP Page Builder "did not save" the changes.

Practical Ways to Use It for Different Types of Agency Sites

Maxora does not need to be used as just one homepage layout. Its sections can be adapted to different agency models as long as you stay grounded in the verified building blocks: ready-made home variations, service pages, team pages, portfolio, blog, contact page, SP Page Builder, and Joomla's module system.

Marketing agency

For a marketing agency, the homepage works best when built around services and results. The hero explains the specialization, the services block leads to service pages, the portfolio shows case studies, the blog supports content marketing, and the contact page captures leads. The success check is simple: a new visitor should understand what the agency does and where to click to get in touch within 30-40 seconds.

Web studio or product team

For a web studio, process and portfolio matter more. Use the service cards as stages of work: audit, design, development, launch, support. The team page helps explain roles, and the portfolio shows real projects. If you do not have many case studies yet, it is better to present 2-3 strong, detailed projects than to leave a lot of demo cards with no substance behind them.

Consulting or B2B services

For consulting, a calmer structure works better: hero, areas of expertise, trust block, team, articles, and contact. A mega menu can help group the focus areas, but it should not be overloaded. In this scenario, separate service landing pages built in SP Page Builder and a blog used as an expert knowledge base are especially valuable.

Local agency with a short path to contact

If the site is for a local business, do not hide the contact options. Set up a prominent Contact menu item, then verify the footer, map, form, and phone number. On mobile, make sure the off-canvas menu does not slow down access to contact information, and that the hero button points to the correct section.

Result Check: What to Open After Every Change

After configuring the template, it is not enough to ask whether it "looks good." You need to confirm that Joomla is using the correct menu item, modules appear in the right positions, cache is not serving an old version, and responsive behavior is not hiding critical blocks.

Front-end check

• Open the site in guest mode or a private window so you do not see admin-specific states.
• Check the homepage, a service page, the portfolio, the blog, and the contact page.
• On each page, make sure the active menu item is highlighted correctly.
• Test desktop, tablet, and mobile widths. Helix responsive settings can hide rows or columns through CSS.
• After clearing the cache, open the direct page path if SP Page Builder changes are still not visible.

Admin panel check

In the admin panel, review three areas: template style, SP Page Builder pages, and modules. The template style controls the framework, pages control builder content, and modules control separate blocks in positions. If you look for the problem in only one place, it is easy to miss that the real cause lives on the adjacent layer.

Speed and cache check

Joomla supports multiple cache layers: page cache, view cache, and module cache. That matters on an SP Page Builder site because the rendered HTML and inline CSS can remain inside the fully cached output. After making changes, first verify the result without aggressive caching, and only then enable performance modes and exclusions. Do not turn everything on at once before you know the content and menus are working correctly.

How to Move Structure from a Staging Quickstart to the Live Site

Many administrators install the Maxora quickstart in a staging area and then try to "pull over" the parts they like into an existing site. That is a valid strategy if you do not turn it into blind file copying. The quickstart should be used as living documentation: review which pages are built in SP Page Builder, which modules are placed in the header and footer, which menu items point to the needed pages, which positions are used in the layout, and which settings are applied in the template style.

For a real migration, it is better not to think in terms of "copy everything," but in terms of the desired result path. For example, if you want to move the services section from the homepage, first find the page in SP Page Builder Pro, then identify the section, export or recreate it on the live site, and verify the images and styles. After that, open the menu item that points to the services page and make sure it uses the correct template style. If the section depends on a module, check the module separately.

Migration map

Before migrating anything, create a short map. In the first column, list the demo element: homepage, services block, portfolio section, footer, top bar, contact page. In the second, specify where it is controlled: SP Page Builder page, Joomla module, Helix template options, SP Simple Portfolio, or menu item. In the third, write what needs to be created on the live site. That map usually takes less time than hunting for a missing block after import.

Pay especially close attention to the footer. In Maxora, the bottom area may look like a standard part of the template, but the documentation points to SP Page Builder modules in positions footer1 and footer2. If you move only the template style and do not move those modules, the footer will not match the demo. The same rule applies to the top bar, contact blocks, and any sections that do not live inside the main page but inside Joomla modules.

Post-migration check

After each migrated element, check three states. First - the element appears on the correct page. Second - it does not appear where it should not. Third - it does not break the mobile layout. In Joomla, that matters more than it may seem: module assignment can place a block on every page, access can hide it from guests, and responsive options in Helix can hide a row at specific widths.

If you are migrating an SP Page Builder page, verify not only the appearance but also the service settings: title, status, language, access, SEO fields, page CSS, and menu item. A page can exist in the list but still not open on the public side if it has no correct menu item or is not published. On an agency website, this often shows up as "it works only through the direct admin link," while a visitor cannot reach it through the menu.

Multilingual Setup, SEO, and Editorial Discipline After Launch

Maxora can be used as the foundation for a multilingual site, but the template itself does not configure the language architecture for you. In Joomla, you first create the languages, content languages, language-specific menus, page associations, and the language switcher. Only after that does it make sense to assign a language to SP Page Builder pages and check which menu item becomes active for each page version.

Multilingual pages in SP Page Builder

SP Page Builder page settings include a page language field, but that field works correctly only when Joomla's language system is already set up. If you assign a language at the page level without proper menus and associations, the user may end up on the wrong-language page, the wrong template style, or an empty route. In Maxora, this is especially visible in the header and off-canvas menu: the menu may look polished, but still point to the wrong language branch.

The practical order is this: first create the language menus and home items, then duplicate or adapt the SP Page Builder pages, then assign a language to each page, then test the header, footer, contact links, and portfolio links in guest mode. If the site is still single-language, do not introduce language complexity early just for possible future growth. First build a stable structure in one language.

SEO checks without promising growth

The official Maxora page talks about ready-made pages, responsive design, and visual structure, but that should not be turned into a promise of automatic SEO results. The template helps present content well, while search visibility depends on page structure, speed, metadata, internal linking, content quality, correct headings, and the technical condition of the site.

After launch, check each important page for the following: one clear primary heading in the site's content area, a unique title, a description, a correct alias, working canonical logic from Joomla or the SEO extension you use, indexability, no leftover demo text, and a clear path from the menu. For SP Page Builder pages, separately review the page settings and the public HTML after clearing the cache.

Editorial discipline

Maxora looks convincing as long as its rhythm stays intact: short headings, strong visuals, clear cards, and sections that do not run too long. If an editor starts dropping large walls of text directly into service cards, the design quickly loses its clarity. For a longer explanation, it is better to create a separate service page or blog article, and keep only a concise summary and link on the homepage.

Do not review only the desktop layout. Large phrases that look great in the hero on a wide screen can become too heavy on mobile. If a heading wraps into five lines, shorten it or change the section structure. That is not a flaw in the template - it is a normal editorial task when working with large-scale typography.

Safe Improvements Without Editing the Template Core

Helix Ultimate provides built-in ways to add custom CSS, custom JS, and metadata through template options or separate files. The documentation recommends not editing template.css or other template core files directly, because those changes may be overwritten by the template engine or by an update. For small tweaks, use Custom CSS, and for longer changes use a custom.css or override.css file inside the template folder.

Example: clean top bar styling

The JoomShaper support forum for Maxora shows a real task: changing the top bar background and the look of social links. That can be done with a CSS adjustment if the top bar is already part of your structure and the module is published in the correct position. Add the code in Template Options - Custom Code - Custom CSS or in a separate custom.css file if the changes start growing.

#sp-top-bar {
  background: #000000;
}

#sp-top-bar a {
  color: #ffffff;
  font-size: 18px;
}

After saving, clear the cache and check the top strip on desktop and mobile. If the result does not work, remove those lines and clear the cache again. Do not add custom PHP to template options: the Helix documentation explicitly warns that this is not the place for PHP code.

When It Is Better Not to Add Code

If the task can be solved through Helix settings, SP Page Builder, or a Joomla module, start there. CSS is for small visual refinements, not for patching a broken structure. If you find yourself writing dozens of lines just to bring back a missing block, the real issue is probably the position, menu assignment, responsive visibility, or a deleted layout row.

Common Maxora Issues and How to Diagnose Them

Problems with Maxora usually appear at the intersection of several layers: the quickstart, the template package, Helix settings, SP Page Builder, modules, menu assignment, and cache. The best approach is to troubleshoot from simple to complex, while tracking exactly where the expected result disappears.

The quickstart will not install through the extension manager

Symptom: the user uploads the quickstart like a standard Joomla extension, but the installation fails or behaves unpredictably.

The reason is the package purpose. The quickstart includes the Joomla core and is meant for a fresh installation, not for the Extension Manager inside an existing site. The fix is to deploy the quickstart in a clean location with a new database, just like a normal Joomla installation. If you need to keep the existing site, use the template package and configure it manually.

The module is published but does not appear on the site

Symptom: the module is published in the admin panel, but it does not show on the public-facing site.

Check the position, access, menu assignment, and layout. For the Maxora top bar, support pointed to positions Top 1 and Top 2. If the module is placed elsewhere, it may never reach the intended area. If the position is correct, check whether the layout row is hidden at the current breakpoint.

SP Page Builder changes are not visible after saving

Symptom: the editor saved the page, but the visitor still sees the old text or old design.

First check whether you edited the correct page and which menu item is assigned as the homepage. Then clear the Joomla cache. If System - Page Cache is enabled, it may keep serving pre-rendered HTML and inline CSS. During setup, it is usually better to work with predictable caching and avoid aggressive modes until the result has been verified.

The off-canvas menu looks different on mobile

Symptom: the mobile menu opens, but the items are awkward, too long, or some links are not visible.

Open Template Options - Menu - Off-canvas Menu and check the placement, alignment, and item set. Then review the Joomla menu items themselves: extra demo items, nesting, language, access, and assignment. If the menu is too long, move some links to a services page or the footer.

Icons or styles do not look like the demo

Symptom: individual icon font elements, cards, or styles look visibly different from the demo.

Check whether the required quickstart extensions are installed, whether media files were removed, whether cache is still serving old CSS files, and whether the asset path is broken. In one Maxora support case, the user was advised to check the path media/com_sppagebuilder/assets/iconfont/icomoon/style.css. Do not edit random files blindly - first confirm that the path exists and loads in the browser.

A required block disappeared after adding custom CSS

Symptom: after a visual change to the top bar, menu, or hero, part of the block disappears or becomes unreadable.

Disable the latest CSS change, clear the cache, and check the result. If everything comes back, the problem is in the selector or in a rule that is too broad. In Maxora, use precise selectors and avoid global rules for all links, all buttons, or all sections when you only want to change the top strip or one specific block.

When Maxora Is the Right Choice for Your Website

Maxora is worth using if you need a modern Joomla template for an agency website and you are ready to work with its real architecture: quickstart for a fresh install, template package for manual rollout, Helix Ultimate for the site framework, SP Page Builder Pro for pages, Joomla modules for positions, and menu assignment for routing. That approach requires care, but it gives you a clear structure instead of a chaotic mix of random blocks.

Before moving anything to the live domain, walk through the full final path: homepage, services, portfolio, team, blog, contacts, mobile menu, footer, cache, forms, and 404/system pages if they are part of the site. If everything opens correctly for a guest, modules appear on the right pages, and the demo content has been replaced, you can move on to final testing.

When you are ready to test the template in your own environment, you can download JoomShaper Maxora and deploy it on a staging domain first. That order is safer than changing the look of a live site right away: you will see the quickstart structure, understand which pages and modules you actually need, and only then decide how to migrate it.