JoomShaper Anobiz - Joomla Template

A Practical Guide to JoomShaper Anobiz for an Agency or Portfolio Website

JoomShaper Anobiz is best viewed not as a "pretty skin," but as a ready-made foundation for a Joomla site where the visual style, homepage structure, menu, portfolio, and service sections need to come together quickly as a clear company presentation. This guide walks through a practical workflow: how to prepare the site, choose the right installation method, turn the demo structure into a real brand experience, configure the header, modules, and SP Page Builder pages, verify the result, and calmly troubleshoot common issues.

This article does not repeat the template's short description. The practical side matters more here: what to check before installation, how not to confuse the quickstart with the standard template package, where to find the key Helix Ultimate settings, how to work with module positions, and when to change sections through SP Page Builder rather than template files.

Visual decisions matter especially with Anobiz. The official preview shows a light minimalist style, generous spacing, large typography, a horizontal menu, blue accent buttons, and portfolio sections built around bold creative imagery. That means setup should go beyond a technical checklist. You need to preserve the rhythm of the demo while replacing the abstract text, images, and cards with real projects, services, and proof of expertise.

The main goal of the setup is to end up with more than just an installed template. You want a manageable Joomla page where the site owner understands which blocks are edited in the template, which are handled in SP Page Builder, which come from modules, and which depend on the menu and the assigned template style.

When Anobiz Works Better Than a Typical Corporate Template

Anobiz is aimed at agencies, design studios, small creative teams, product consultancies, and specialists who need to showcase expertise through projects, services, visual style, and a clear site journey rather than a product catalog. This kind of template is especially useful when the hero section needs to communicate positioning quickly, followed by case studies, workflow principles, services, portfolio items, and trust elements.

In a typical corporate template, sections like "About Us," "Our Advantages," "Team," and "Contact" often dominate. For an agency site, that is not enough. Visitors want to see what problems the team solves, what the work looks like, how modern the projects feel, and how quickly they can move toward contact. That is exactly what the Anobiz preview shows: a large headline, a short supporting line, a prominent button, a decorative strip of project visuals, a large media block, and a featured work section.

If the site is being built for a studio that sells design, development, branding, marketing services, or creative support, Anobiz gives you the right starting composition. The key is not to break it immediately. Start by replacing the content layer by layer: logo, menu, hero copy, project images, work cards, services, CTAs, and contact forms. Only after that should you fine-tune the palette, typography, and additional module positions.

Who this template may not be right for

Anobiz is less convenient for sites that need a complex catalog, booking, a user account area, an LMS, a forum, or a large news portal. Joomla extensions can add that functionality, but the template itself should not be forced into being a container for every possible use case. If the site's core value is data tables, filters, orders, statuses, or long reference directories, it is better to choose a solution where that logic is already built into the page structure.

It is also worth being cautious if the team is not ready to prepare strong project visuals. Anobiz's light design with large visual areas does a poor job of hiding weak imagery. On a template like this, empty stock photos and random icons quickly make the site feel like an unfinished demo page. Before installation, gather at least a basic set of real materials: 5-8 project images, 3-5 service descriptions, a short positioning statement, and a contact scenario.

What to Check Before Installing on Joomla

Preparation saves more time than trying to fix a site after it is already broken. With Anobiz, there are two main paths: install the quickstart as an almost complete copy of the demo on a clean site, or add the standard template package to an existing Joomla installation. These scenarios should not be mixed. Quickstart, like other JoomShaper quickstart packages, is installed as a separate Joomla build and is not meant to be uploaded through the extension manager on an existing site.

If you are starting a new project, using a staging domain, or working with a local copy, quickstart usually gives the clearest result: you see the demo structure, pages, modules, and styles working together. If the site already has content and is live in production, it is safer to install the standard template, create a separate template style, assign it to a test menu item, and migrate the needed elements gradually.

Minimum checklist before you start

• Make sure your hosting environment meets the requirements for your Joomla version and JoomShaper extensions.
• Create a backup of the files and database if the site already exists.
• Create a separate database and a separate folder if you are installing the quickstart.
• Check which packages are included in the product archive: template, quickstart, SP Page Builder Pro, or additional extensions.
• Prepare a logo in both standard and compact versions, project images, and hero copy.
• Decide whether the site will be single-language or multilingual, because that affects menus, template style assignments, and logo links.

At this stage, there is no need to enable caching, CSS/JS compression, or third-party optimization right away. The first priority is getting the design to display correctly without extra layers in the way. Cache and minification are most useful at the end, once you know the menu, styles, images, and modules are already working properly.

Practical rule: if you want a result that looks like the demo, start with the quickstart on a clean installation. If you already have a working site, do not install quickstart over it - use the template package and a test menu assignment instead.

Installation: Quickstart or Template Package

The difference between the installation options is fundamental. Quickstart includes a Joomla build with demo data, the template, dependencies, and a preconfigured structure. A standard template package adds the visual layer and template settings, but it does not necessarily create the same homepage, modules, or content. This difference is exactly why users often think the template "installed without the demo" or "doesn't look like the preview." In reality, they chose a different installation path.

Scenario for a new site

For a new site, it is easiest to deploy the quickstart in a separate folder or on a temporary subdomain. After uploading the files, open the domain in a browser and go through the standard Joomla installer. When entering admin details, avoid an obvious username like admin, and after installation, check the frontend, the admin panel, and the presence of the demo pages.

After the first login, do not rush to delete the demo blocks. First, map the structure: which pages control the homepage, which modules are published in the header and footer, which menus are used, and which template style is assigned by default. That gives you control over the system. If you immediately delete half of the demo content, it becomes much harder to understand which element was responsible for a specific section.

Scenario for an existing site

On an existing site, install the package through System - Install - Extensions or the equivalent installation area in your Joomla version. After a successful install, open System - Site Templates - Styles, create a copy of the Anobiz style, and assign it not to the entire site but to a separate test menu item.

This approach reduces risk. You can see how Anobiz behaves with your menu, content, modules, and third-party extensions without changing the public site as a whole. If everything looks correct, expand the style assignment gradually. If you find a conflict, rollback takes only a few minutes: restore the previous template style for the test menu item or remove the assignment.

Initial check after installation

1. Open the homepage as a guest, not only from the admin panel.
2. Make sure the main menu item points to the correct page.
3. Open the page in a private browser window to rule out any effect from a logged-in session.
4. Check the browser console for obvious CSS, JS, and image loading errors.
5. Disable third-party minification if the design looks different from the demo after installation.

Basic Style Setup: Logo, Header, Colors, and Typography

After installation, configuring Anobiz should not begin with editing every block on the homepage. Start with the base template style instead. In JoomShaper templates, this part is usually tied to Helix Ultimate: logo, favicon, header, sticky header, body/layout, footer, social icons, typography, presets, and custom code. Not every item will necessarily look identical in every package, but the logic stays the same: global settings first, then pages and modules.

Logo and favicon

In Helix Ultimate, the logo can be an image or text. For Anobiz, a clean horizontal logo without tiny details works best, because the header in the demo feels light and is not designed for a heavy emblem. Prepare the main logo, a mobile version, and a retina file if needed. If the brand has a complex mark, test it against the header background and in the sticky state.

The logo alt field should not be left empty. Use a clear option like Company Name logo or a Russian-language equivalent if the site is entirely in Russian. That will not create a dramatic SEO effect on its own, but it improves accessibility and helps search engines understand the image.

Header and menu

In the Anobiz preview, the header is minimalist: logo on the left, menu centered, and a short CTA button on the right. Keep that clarity. Do not add 10-12 items to the top menu. For an agency site, sections like "Services," "Work," "About," "Process," "Contact," and one action item are usually enough. If you need to show many directions, use a mega menu carefully, but do not turn it into a catalog of everything on the site.

Do not check only the desktop version. In the mobile menu, clear labels and the order of items matter even more. If a visitor opens the site on a phone after a referral or an ad, they should quickly see your work, services, and contact path. A complicated multi-level menu in an agency template often creates more friction than value.

Colors and presets

Helix Ultimate supports color presets and custom styling. For Anobiz, the right starting point is a light palette, plenty of breathing room, black and gray text, and a clear blue accent. If you replace the main accent with your brand color, test it in three places: the CTA button, active menu items, and smaller markers inside sections. The color needs to work not only in the hero section, but also in lists, links, hover states, and cards.

Do not try to repaint the entire site with one random CSS selector. Start with the preset and style settings. CSS should be used for targeted adjustments when the built-in option does not cover the task or when you need to fine-tune a specific block.

Typography

In Anobiz, large-scale typography is part of the template's personality. If you replace the fonts with something too decorative or too narrow, the template loses its clean agency feel. In the typography settings, review the body text, headings, navigation, line height, and responsive sizes. For a Russian-language site, also make sure the chosen font supports Cyrillic. If Cyrillic is rendered with a different fallback font, the design will look uneven.

The most common typography mistake is reducing the homepage headings while leaving the original spacing in place. The result is a section that feels empty. Change the font size, line height, and vertical spacing together, then check the real screen instead of relying only on the settings form.

The Homepage in SP Page Builder: What to Change First

The Anobiz homepage is built around a presentation-driven logic: hero section, visual strip of work, idea or positioning block, large media section, featured work, services, and the sections that follow. Even if the specific pages in your package differ, that rhythm is visible in the preview and should guide your editing. The typical beginner mistake is opening the page in SP Page Builder and changing everything at once. It is much better to move from meaning to blocks.

Hero section

The hero section should answer three questions: who you are, what problem you solve, and where the visitor should click next. Anobiz already gives you a composition with a large heading and CTA. Replace the heading not with a generic slogan, but with a concrete promise. For example, a design studio might talk about websites, branding, and interfaces, while a marketing agency might focus on campaigns, landing pages, and analytics. The supporting paragraph should be shorter than the heading and should not restate it in different words.

The CTA button should lead to a real action: a brief, contact page, portfolio, or inquiry form. If you do not have a form yet, point it to the contact section. Do not leave the button with demo copy. Visually it can stay small, but functionally it is one of the main paths on the page.

Project images

The Anobiz preview shows a horizontal sequence of vivid images. This is one of the template's strengths, but it requires discipline. Choose visuals with the same quality level and a similar visual weight. If you place a dark interface screenshot, a light mockup, a random office photo, and an icon next to each other, the section falls apart. It is better to use 5-6 projects in a consistent format: case study covers, interface details, brand visuals, or project imagery.

Fill in the alt text for each image. If it is a case study, the alt text can include the project name and the type of work. If it is a decorative abstract visual, ask whether it belongs there at all. In an agency portfolio, images should prove expertise, not just fill space in a card.

Featured work and project cards

The featured work section is best used not as a list of your entire portfolio, but as a showcase of 4-6 strong projects. Each one needs a short context: what was done, for whom, and what result is visible. If the template's card opens a detail page, prepare that page in advance. If no detail page exists, a "View Details" button or its localized equivalent will lead nowhere and reduce trust.

Services and process

The services section should not become a long catalog. For Anobiz, 3-5 directions with a short explanation and a link to more detail usually work best. If you offer more services, group them into clear categories. For example: strategy, design, development, support. For the process section, avoid generic wording and use the real stages a client goes through: brief, audit, concept, production, launch, and support.

Menus, Module Positions, and Template Style Assignments

A Joomla template does not live only inside the visual editor. The menu defines the site paths, the template style controls where the design is applied, and modules output content into positions. With Anobiz, this matters especially: the header, footer, CTA, social links, extra blocks, and sometimes parts of the page may depend on modules and positions.

Helix Ultimate Layout Manager works with a 12-column logic and module positions. That means you can change row structure, assign positions, and control display across devices. But any layout changes should come only after you understand the current scheme. Otherwise, it is easy to remove a position that contained an important module and then spend a long time trying to figure out why a block disappeared.

How to check positions

Start in the Joomla admin panel: open the modules, filter by template or position, and review which elements are published for the homepage and inner pages. Then open the Anobiz template style and its layout settings. Your task is to connect the visible block on the site to its actual source: an SP Page Builder page, Joomla Article, Custom module, menu module, footer position, or a template setting.

If a block appears on every page, it is most likely published as a module or built into the template. If it appears only on the homepage, it may live inside an SP Page Builder page. If it disappears on just one page, check the menu assignment and the template style assignment.

Mega menu without overload

Helix Menu Builder lets you create more advanced submenus, add columns, modules, and menu items. For Anobiz, that is useful if the agency has several service categories or separate types of work. But a mega menu should help visitors choose, not expose the entire site structure. A strong pattern is 2-3 columns, short labels, and one highlighted block or link to a brief.

After setting up the mega menu, test keyboard navigation, tablet behavior, and the off-canvas menu. If mobile users see an overly long list, simplify the structure. Agency sites often benefit more from clarity than from deep navigation.

Responsiveness, Speed, and Project Images

Visual portfolio templates often break because of the content, not because of the template itself. In Anobiz, large images and generous spacing require careful file preparation. If you upload heavy unoptimized images, the hero section becomes slow. If you upload images that are too small, project cards will look blurry on large screens.

Image sizes and quality

Prepare separate images for the hero section, project cards, internal case studies, and background sections. Do not use one oversized file everywhere. For portfolio cards, it is enough to use an image that looks sharp in that specific block. A large hero needs a wider file, but it should still be compressed. WEBP and properly prepared JPG files usually give a good balance between quality and file weight.

After replacing the images, check the site in three states: wide screen, tablet width, and phone. On mobile especially, make sure faces, interfaces, and key parts of the visuals are not cropped awkwardly. If a block uses a background-image, review the background position settings. If it uses a standard img, check the proportions and crop.

Cache and optimization

Joomla cache, server-side cache, CDNs, and optimization plugins are best enabled after the base setup is complete. If you enable everything at once, troubleshooting becomes harder: it is no longer clear whether the template failed to save a setting, the browser is holding old CSS, or the optimizer merged files badly. First verify the site without aggressive optimization, then turn improvements on one by one.

Verifying the result matters more than having a checkbox enabled. After any optimization change, open the site in a private window and test the hero section, menu, portfolio, forms, mobile menu, and internal pages. If only one section breaks, temporarily exclude its script or CSS from minification if your optimizer allows those exclusions.

Practical Scenario: Building a Studio Homepage with Anobiz

Below is an example setup scenario without tying it to a specific license or purchase. Let us say you need to launch a website for a small studio that offers branding, websites, and interface design. The goal is to build a homepage where visitors immediately see the positioning, examples of work, services, process, and a quick path to contact.

Goal

Create a homepage where the hero section explains the specialization, followed by 5 strong projects, then a clear breakdown of services, and a path to submit an inquiry. The page should stay close to the visual rhythm of the Anobiz demo, but with a real brand, Russian-language copy, and working links.

Preparation

• A logo in SVG or PNG with a transparent background.
• 5-6 project images in a consistent style.
• A short hero heading and supporting paragraph.
• A service list with clear names.
• A contact page or inquiry form.
• A site backup before editing, if this is not a clean staging environment.

Setup steps

1. Create or open the Anobiz template style and assign it to a test menu item.
2. Replace the logo, favicon, and base CTA in the header.
3. Open the homepage in SP Page Builder and rename the sections with clear working labels if the interface allows it.
4. Replace the hero heading, short description, and button link.
5. Replace the images in the horizontal strip and featured work section with real projects.
6. Keep only the demo blocks that support your scenario. Extra sections are best hidden or removed after backing up the page.
7. Set up the menu so the items lead to work, services, process, and contact.
8. Check the mobile menu, spacing, section order, and CTA appearance.

Verification

Open the public site as a normal visitor. Make sure the hero section no longer looks like a demo, the button points to the right place, the images are not blurry, the project cards open or lead to the correct pages, and the header does not overlap the content while scrolling. Then log out and repeat the check in a private browser window.

Important nuance

If you do not see your changes after saving the page, do not jump straight into editing template files. First clear the Joomla and browser cache, make sure you edited the correct page, confirm that the right template style is assigned to the current menu item, and only then look for a cache or optimization conflict.

Safe Improvements Without Editing the Template Core

For Anobiz, safe custom work is best handled through Helix settings, SP Page Builder, modules, Joomla language overrides, and small custom CSS adjustments. There is no need to edit Joomla core files, template core files, or extension files. Those changes are hard to update, easy to lose during an update, and difficult to troubleshoot.

Soft CTA button refinement

If the CTA in the header or hero is not prominent enough after replacing the brand colors, you can add a CSS class to a specific button in SP Page Builder, or to a row/block if the editor lets you assign a custom class. For example, use the class agency-cta-soft and add the CSS through the Helix custom code area or the standard custom CSS location.

.agency-cta-soft {
  border-radius: 999px;
  box-shadow: 0 12px 30px rgba(0, 94, 255, 0.18);
  transition: transform 0.2s ease, box-shadow 0.2s ease;
}

.agency-cta-soft:hover,
.agency-cta-soft:focus {
  transform: translateY(-1px);
  box-shadow: 0 16px 36px rgba(0, 94, 255, 0.24);
}

This adjustment does not depend on Anobiz's internal files and is easy to roll back: remove the class from the button or remove the CSS. After applying it, test the button on mobile and make sure the focus state is visible during keyboard navigation.

Language overrides instead of file edits

If an English string is still left in the template or extensions, look for it in Joomla language overrides first. That is safer than changing PHP or template files. An override can be disabled or corrected without risking future updates. This approach is especially convenient for buttons, short messages, and system labels.

Template override only for a stable use case

A template override is needed when you want to change the output structure of a Joomla component or module. It is not necessary for ordinary changes to color, text, spacing, or section order. If you do create an override, document exactly what was changed and recheck it after updates. For Anobiz, most visual tasks should be handled through template settings, SP Page Builder, and CSS.

How to Review the Finished Site Before Launch

Pre-launch review should be a separate stage. Site owners often stop when the page "kind of looks like the demo." For a real website, that is not enough. You need to verify paths, forms, images, responsiveness, SEO basics, accessibility, and cache behavior.

Paths and menus

Go through every menu item in the header and footer. Make sure there are no links to demo pages, empty anchors, or old URLs. If the site uses one-page anchor navigation, verify that scrolling lands on the correct section and the header does not cover the heading.

Content and SEO basics

For the homepage, check the title, description, canonical URL, readable URLs, and image alt text. Do not try to stuff every block with keywords. For an agency site, clear positioning, service descriptions, understandable case studies, and clean headings matter more. Internal project pages should have their own headings and descriptions rather than repeating the same text.

Forms and the contact path

If the CTA leads to a form, submit a test inquiry. Check where the email is delivered, whether a success message appears, whether the message lands in spam, and whether the validation error text is clear when a field is left empty. If there is no form, test the phone number, email, messengers, and map. Agency sites often lose leads because of small contact mistakes.

Responsiveness and visual consistency

Do not test only phone width. Intermediate screen sizes matter too. Sometimes a layout looks fine on desktop and phone but breaks on a tablet. In Anobiz, with its large spacing and oversized visuals, it is especially important to make sure headings do not wrap awkwardly, project cards do not become too narrow, and the menu does not clash with the CTA.

Content Map for Case Studies, Services, and Trust Sections

Anobiz only feels convincing when its visual structure is filled with real proof. For an agency site, this is not a secondary task. If you replace demo blocks with generic copy, the visitor sees a beautiful layout but still does not understand why they should contact you specifically. That is why it is useful to build a content map before launch: which projects appear on the homepage, which services get separate pages, which trust elements prove experience, and where the contact path lives.

The map is also important because it keeps SP Page Builder from filling up with random sections. Without a plan, site owners often add an "Advantages" block, then a "Why Us" section, then another service list and several repetitive CTAs. The result is a strong opening screen followed by a page that falls apart. With Anobiz, a different approach works better: fewer sections, but each one answers a specific user question.

Case studies: what to show on the homepage

You do not need to place a full archive of work on the homepage. Choose a few projects that demonstrate different kinds of work: branding, website design, interface design, campaigns, support, or a full launch. Each project should have a short meaningful label. Not "Project 01," but "Service Redesign," "Product Launch Landing Page," "Studio Brand Identity," or "B2B Team Portal." Copy like this helps visitors read not just the image, but the direction of your work.

If an Anobiz project card leads to a detail page, do not leave it empty. A case study page can be short, but it should still explain the task, your role, the key decisions, and the result. For an agency, an honest structure matters more than big promises. Even if you do not have numeric outcomes, you can still show the original problem, the work stages, design fragments, the final page, and what the project taught the team.

Services: grouping instead of a long list

If the studio offers many services, do not move them onto the homepage as one long list. Break them into 3-4 directions and add short descriptions. For example: "Strategy," "Design," "Development," and "Support." You can expand the details on internal pages, but the homepage should offer choice without overload. Anobiz, with its wide spacing and visual blocks, supports that well: one strong service card works better than ten small items.

Add an action to each service: go to the page, view a sample project, send an inquiry, or open a brief. If the services block ends with text only, users do not know what to do next. Connect services to the portfolio: after describing a direction, show 1-2 projects that prove expertise in that specific area.

Trust without logo overload

Agency templates often include rows of client logos, counters, and testimonials. That is useful if the data is real. If you do not have logos or cannot disclose client names, use other proof instead: your process, typical project types, screenshots of results, short testimonials without theatrical language, links to published work, certifications, or a team summary. Do not create fake logos just to fill a demo block.

A trust section should be verifiable. If you say "50+ projects," be ready with a page or at least a portfolio that makes that believable. If you claim a specialization, show a case study in that area. If you promise a fast launch, explain what makes that possible: reusable components, a polished process, a template-based structure, or experience in a specific niche.

Contact path

In Anobiz, a CTA may appear in the header, hero section, after the projects, and closer to the footer. Those buttons do not all need to mean the same thing. The first can lead to the portfolio, the middle one to a brief, and the lower one to contact. The main thing is that they do not contradict one another or lead to empty pages. If the inquiry form is complex, place an alternative nearby: email, messenger, or a short note on what to include in the first message.

After setting up the contact path, submit a test inquiry from a normal user email account. Check not only delivery, but also the content of the message: is it clear which page it came from, and does it include the name, contact details, subject, and message? If the email arrives without context, the manager will waste time clarifying details.

Multilingual Setup, Access Permissions, and a Staging Copy of the Site

Not every Anobiz site needs multilingual support, but agencies often do: a Russian version for local clients, an English version for an international portfolio, and sometimes separate pages for partners. Joomla supports multilingual sites, but it is not a one-click translation switch. You need content languages, menus, module assignments, article associations, and a careful review of template styles.

How not to get lost in language menus

If the site is multilingual, create separate menus for each language and decide in advance which pages truly need translation. For the Anobiz homepage, separate versions are usually necessary: hero copy, services, case studies, and CTAs should sound natural in each language. Do not machine-translate every block without editing. The template's large typography makes awkward wording obvious right away.

A template style can be assigned to different menu items. That is useful when the Russian and English versions share one visual style but use different menus, modules, and contact blocks. Check the logo, logo link, menu, footer, and inquiry form for each language separately. An error in one language menu may not show up on the other version of the site.

Access permissions for editors

If the site will be maintained by more than one administrator, configure the roles in advance. An editor who changes text and case studies does not always need access to system settings, extension installation, or template files. The fewer unnecessary permissions there are, the lower the risk of accidentally breaking the template style or deleting a module position. For a team, it is useful to split responsibilities: who edits SP Page Builder pages, who publishes content, who changes menus, and who handles updates.

After setting permissions, do a test login using the editor role. Make sure that person can open the necessary pages, save changes, upload an image, and does not see critical system sections. This matters especially when the site is being handed off to a client. A good template will not save the project if the client accidentally gets access to settings they should never change.

Why you need a staging copy

A staging copy of the site is essential for testing updates and major changes before touching the public version. For Anobiz, it is especially useful because the template depends on Joomla, Helix, SP Page Builder, modules, menus, and your custom CSS. Updating one layer can affect another. On a staging copy, you can test a new version, spot a conflict, fix CSS, or roll back without putting pressure on the live site.

The minimum discipline is simple: before updating, make a copy, update it, check the homepage, portfolio, menu, forms, mobile view, cache, and custom CSS changes. If everything works, repeat the update on the live site. If not, do not carry the problem into production. Updates should be a controlled process, not an experiment on a live website.

Documentation for the site owner

After setup is complete, leave a short internal guide. It only needs to explain where the homepage is edited, which modules control the header and footer, where the project images are stored, how to replace the CTA, how to clear the cache, which CSS changes were added, and what should not be touched without a developer. A guide like this saves support hours and reduces the chance that no one will remember how the site works a few months later.

For Anobiz, this documentation is especially useful because of the template's mixed structure: some parts are visible in SP Page Builder, some live in the Helix template style, some in Joomla menus/modules, and some in custom CSS. When those layers are clearly labeled, the site stays manageable after it is handed off to a client or editor.

Common Problems When Setting Up Anobiz and How to Diagnose Them

Most issues with JoomShaper Joomla templates come down to the wrong installation scenario, cache, template style assignment, optimization conflicts, missing modules, or editing the wrong page. Below is a practical diagnostic checklist worth going through before contacting support.

The site does not look like the demo

Symptom: the template is installed, but the homepage is empty, looks different, or shows old content. A likely reason is that the standard template package was installed instead of the quickstart, or the template style is not assigned to the correct menu item.

Check which archive was installed. If it was the standard template package, the demo structure is not supposed to appear automatically. Open the list of template styles, check the menu assignment, and make sure the homepage is actually using the Anobiz style. If you need a result that looks like the demo, deploy the quickstart on a clean environment and migrate content deliberately.

Changes in SP Page Builder do not appear on the site

Symptom: the text is changed in the editor, but the public page still shows the old version. First clear the Joomla cache, the SP Page Builder cache if it is enabled, and the browser cache. Then make sure you edited the page that is actually tied to the current menu item.

If an optimizer or CDN is in use, disable it temporarily. Then make a small test change, such as one word in a place hidden from users, save it, and check in a private window. If the change appears, the problem was cache-related. If not, look for another content source: a module, a different page, or another menu item.

A block disappeared from the header or footer

Symptom: the logo is still there, but the CTA, social links, footer, or part of the menu is gone. Check module publishing, positions, access levels, and menu assignment. In Joomla, a module can be published but still not appear on the current page because of its menu assignment or the wrong position.

If you changed the layout in Helix, make sure you did not remove the row or column that contained the needed position. Do not create a new position with a similar name at random. First restore the original scheme or compare it with a quickstart or staging copy.

The mobile menu behaves strangely

Symptom: items do not open, the menu covers the screen, anchors go to the wrong place, or the CTA appears twice. Check the Off-canvas settings in Helix Menu, the Joomla menu structure, and any third-party optimization scripts. If JavaScript minification is enabled, disable it temporarily and test again.

Use short menu item labels for long navigation paths, and move the detail into the pages themselves. If a mega menu is enabled on desktop, check how those same items behave in the mobile structure. Not every desktop solution translates well into off-canvas navigation.

Images look blurry or too heavy

Symptom: the portfolio looks weaker than the demo, images load slowly, or they are cropped badly. Check the original dimensions, format, compression, and how the image is being rendered. If the block uses a background, adjust the background position and size. If it is a regular image, prepare the file for the block's real aspect ratio.

Do not upload huge images "just in case." Optimize copies for specific placements and check the visual quality on a wide screen. For a portfolio, fewer projects in better quality are usually the smarter choice.

Template settings do not save

Symptom: after clicking Save, the settings revert or an error appears. Check administrator permissions, server limits, console errors, conflicts with system plugins, and whether the components are up to date. If the issue happens only in one browser, clear the cache or try a different browser. If no template style can be saved at all, it is time to check the server logs and contact support with specific reproduction steps.

When JoomShaper Anobiz Is the Right Choice

JoomShaper Anobiz is a strong choice if you need a Joomla template for an agency, portfolio, design studio, or creative team, and you are ready to work with the visual structure rather than simply swapping the logo. Its strength lies in its modern light style, emphasis on project work, large typography, and integration with familiar JoomShaper tools.

Before publishing, make sure you chose the correct installation scenario, replaced the demo content, configured the template style, checked the menus and modules, optimized the images, and completed a mobile review. If you need a starter file for a test installation, you can go to the JoomShaper Anobiz download and deploy it on a separate environment first without touching the live site.

The main readiness test is simple: within a few seconds, the visitor should understand what your team does, see examples of your work, move quickly to the services, and send an inquiry without friction. If Anobiz helps you build that path, the template is the right fit. If the site still feels like a beautiful demo page without real substance after setup, return to the structure, the copy, and the case studies - that is what turns a template into a working tool.

Final Review Before Moving Anobiz to the Live Site

Before launch, JoomShaper Anobiz deserves one separate final review pass because the template has many visual dependencies: header, hero block, work cards, service sections, menus, modules, and pages built through SP Page Builder. The typical mistake does not look like a full site failure, but like a small mismatch: a button points to the wrong place, a section was not added to the menu, an image was compressed incorrectly, mobile spacing became too large, or a module appears on only one page.

Start by opening the homepage as a normal visitor, not from editing mode. Check the hero section, call-to-action button, navigation, work block, services section, and contact path. If Anobiz is being used for a studio, agency, or portfolio team, it is especially important that the first scroll immediately shows the specialization, examples of work, and the next step for the client. The template's polished demo rhythm is easy to damage if you replace images without keeping consistent sizes or leave headings too long.

1. Make sure the correct template style is active and assigned to the menu items where the Anobiz design should appear.
2. Open SP Page Builder and confirm that the homepage contains only the current sections, without demo blocks the project does not need.
3. Check the mobile width: the menu, button, hero text, work cards, and contact elements should remain readable without horizontal scrolling.
4. Clear the Joomla cache and optimization cache, then repeat the test in a private browser window.
5. Test forms, links, anchors, and the path to download or testing through the JoomShaper Anobiz download block.

If some changes still do not appear after the review, do not start changing CSS right away. More often, the cause sits at the cache level, a wrong menu item, a duplicate template style, or a page that was edited in the wrong SP Page Builder instance. For a working site, it is useful to write down a short map: which menu item controls the homepage, where the editable page lives, which modules are displayed in the header and footer, and which images are used in the portfolio. A map like this saves time during the next update and helps preserve the logic of Anobiz after the demo content has been replaced.

The final criterion is simple: the template should no longer look like an installed demo, but like the finished structure of a real project. If, within the first few seconds, a visitor understands who you are, what work they can view, which services they can request, and where to click next, then the base setup has been done correctly. After that, you can move on to targeted optimization for speed, SEO metadata, structured data, images, and internal links.