JoomShaper Affility - Joomla Template

A Guide to Setting Up JoomShaper Affility for an Affiliate Joomla Site

JoomShaper Affility makes the most sense not as a standard “pretty” template, but as a starter framework for a site built around reviews, product roundups, promo blocks, category showcases, and affiliate click-throughs. This guide walks through the full process, from checking the package and installing it to configuring the homepage, menus, modules, cards, ad placements, and the final public-facing result.

This article does not repeat the template’s short product description. The practical logic matters more here: where to use QuickStart, when it is safer to install just the template, which elements are edited through SP Page Builder, where Helix Ultimate comes into play, and why module positions and menu assignments solve more problems than random CSS tweaks.

It also covers affiliate-specific scenarios: how to build a homepage around a primary offer, how to organize reviews and categories, how to keep sidebar blocks visible on article pages, how to test mobile navigation, and what to do if the demo looks different after installation than it did in the screenshot.

What This Template Is Designed to Do

Affility’s main job is to help you launch a Joomla site quickly where visitors see not only articles, but also a commercially useful structure: a featured deal of the day, product roundups, reviews, store categories, banner placements, a subscription form, affiliate pages, and a storefront-style product showcase. This is especially useful when the site needs to guide readers from informational content to a deliberate affiliate click or a product detail page.

In a typical blog, the editor publishes articles first, and commercial elements are often added later through whatever modules happen to be available. In Affility, those elements are already built into the page composition: top navigation, an ad banner, the Deal Of the Day block, a countdown timer, a review feed, editorial picks, sidebar content, and subscription signup. That is why setup should begin not with “what button color should I choose?” but with “what role will each page and module play?”

When the Template Is a Strong Fit

Affility works well for sites where editorial content and commercial click-throughs need to work together. For example, gadget review sites, home product roundups, coupon projects, seasonal deal catalogs, blogs with affiliate recommendations, or small stores that need a strong showcase but not the complex commerce logic of a large marketplace.

• The editor publishes reviews and comparisons, and the template helps surface them in prominent homepage sections.
• The site administrator builds store or product categories and presents them as navigation entry points for readers.
• The marketer places banners, promo strips, and subscription forms without disrupting the overall rhythm of the page.
• The site owner wants to start from the demo structure and gradually replace the content with original material.

When Another Approach Makes More Sense

The template may be unnecessary if you need a minimalist blog without showcases, timers, ad blocks, or store-style logic. It also does not replace a complete affiliate content strategy: if you do not have reviews, categories, legally compliant links, affiliate disclosure, and your own images, polished demo styling alone will not make the project feel credible.

Practical rule of thumb: if the site will have fewer than several ongoing sections for reviews, offers, and categories, Affility may be heavier than you need. But if you are building an editorial storefront with regular roundups, the ready-made structure saves a great deal of time.

What to Check Before Installation

Before installing, it is important to separate Joomla’s technical readiness from the readiness of the project itself. JoomShaper’s official Affility documentation outlines the server requirements for Joomla, QuickStart, and SP Page Builder: working PHP, MySQLi or MariaDB, enough memory, sufficient execution time, cURL, OpenSSL, and functions required to load resources. In practice, that means weak hosting may install the archive successfully, then stall during demo import or while saving large pages.

The second layer is content readiness. Affility is built around images, product cards, banners, reviews, and categories. JoomShaper’s documentation specifically notes that demo photos may not be included in the package because of licensing restrictions. So prepare your own legally usable images in advance, otherwise the site may be installed correctly from a technical standpoint but still look empty or filled with placeholders.

Technical Pre-Launch Checklist

• Make sure the current Affility package is compatible with your Joomla and PHP versions, not just with an outdated description on a third-party site.
• Confirm that upload_max_filesize, memory_limit, and max_execution_time are high enough for a QuickStart installation.
• Check for cURL, OpenSSL, GD, and mb_* support, since components, images, and multilingual strings may depend on them.
• Create a full site backup if you are installing the template on top of an existing Joomla site.
• Decide whether you need QuickStart with demo data or just the template for an existing site.

Content Checklist

For an affiliate site, prepare more than just a logo and color palette. You also need categories, initial reviews, affiliate offer terms, copy for the about page, trust elements, custom banners, and original photography. Without them, the demo structure remains a polished shell without a useful path for the reader.

QuickStart, the Template, and an Existing Site

JoomShaper templates usually support two working scenarios. The first is QuickStart, meaning a ready-made Joomla package with the template, demo pages, components, and modules. The second is installing only the template and the required extensions into an existing site. With Affility, that distinction matters even more because the value of the template lies not only in its styling files, but also in its prebuilt page structure.

If the project is new, QuickStart is usually easier. It gives you a working map: where the homepage lives, which modules are published, how the categories are laid out, which pages were built with SP Page Builder, and which positions are used in the header, footer, and sidebar areas. You start with a working system and replace demo content with your own.

If the site is already live, you cannot install QuickStart over it like a normal extension. That package behaves like a brand-new site installation and can overwrite the structure. In that case, the safer option is to deploy QuickStart on a subdomain or locally, study the demo structure, and then transfer only what you actually need: the template, module positions, pages, styles, and content blocks.

When to Choose QuickStart

Choose QuickStart if you are building the site from scratch, want a layout close to the demo, and are prepared to replace the demo materials with your own. It is also the best option for learning how the template works: you can open the admin panel, see which modules control which zones, compare the frontend with the settings, and understand the mechanics without guessing.

When to Install Only the Template

Installing only the template makes sense if the site already has articles, menus, users, components, and an SEO structure in place. In that scenario, do not try to “get the demo in one click.” Instead, carefully reassign the template style, create the necessary modules, test the pages, and gradually replace the old output with the new layout.

A Mini Plan for a Safe Installation

1. Back up both the site files and the database.
2. Deploy QuickStart in a separate test environment if you want to reproduce the demo.
3. Check which extensions are included in your package: current JoomShaper materials mention EasyStore, while older descriptions referred to J2Store.
4. On the production site, install only the packages you actually need and do not import demo data without reviewing it first.
5. After installation, assign the template style to a test menu item and verify the result on a single page.

Initial Setup After Installation

After installation, do not start by replacing every piece of homepage text. First, make sure the template is assigned correctly, the required extensions are active, the homepage loads, the menu points to the right items, and the demo blocks are not tied to missing images or disabled modules.

Affility has several configuration layers. The overall visual presentation is managed through the template style and Helix Ultimate settings. Pages built in the visual editor are edited through SP Page Builder. Joomla modules control individual blocks, positions, and menu assignments. The store or product layer depends on whichever commerce component is included in your build.

Where to Find the Main Settings

• System or the Joomla template area - template styles and Affility settings based on Helix.
• Components - SP Page Builder pages and the store component, if installed.
• Content and Menus - articles, categories, menu items, and the URL-to-page relationships.
• Site Modules - banners, menus, subscription forms, recent content, categories, and the blocks rendered in template positions.

Settings Worth Checking First

Start with the logo, the overall header style, the menu, mobile navigation behavior, the homepage, and the footer. Then move on to more complex areas: product showcases, store categories, deal timers, ad zones, and forms. That order lowers the risk of spending time on card styling only to discover later that a menu item points to the wrong page or a module is rendering in the wrong place.

Homepage: Deal of the Day, Reviews, and Ad Blocks

Affility’s homepage is built as an editorial storefront. The goal is not simply to replace the demo text, but to preserve the user journey: first the reader sees a strong offer, then gets proof of expertise through reviews, and only after that moves into categories, roundups, and additional materials. If you rearrange the blocks without a clear reason, the page may look full but stop guiding the visitor toward action.

The Affility homepage documentation states that the page was built with SP Page Builder Pro and can be edited either from the frontend or the admin editor. Frontend mode is convenient when you want to see the visual result immediately. Admin mode is better when you need to work carefully with the structure of sections, rows, columns, and addons.

How to Configure the Main Deal Block

The main offer block should answer three questions: what is being offered, why it is a good deal, and where the user should go next. For an affiliate site, it is especially important not to rely on empty promises. In the offer card, include a clear product or category name, a concise benefit, the validity period, an image, and a button. If the time limit is unknown, it is better to remove the timer than to display a fake countdown.

1. Open the homepage in SP Page Builder.
2. Find the section with the main offer and save a page copy or export if the editor supports it.
3. Replace the product image with your own legally usable asset.
4. Update the title, description, price, or discount only when that information is actually confirmed by the seller’s source.
5. Check the destination button and add whatever attributes match your affiliate link policy.
6. Save the page and open it in guest mode.

How to Avoid Overloading the Page with Ads

The demo clearly shows ad and promo zones, but a real site should not turn into a wall of banners. For an affiliate project, ads work better when they explain a section or help the visitor choose the next page to visit. Use one prominent top banner, one block inside the content feed or after a group of reviews, and one clean subscription block. Use any additional placements only after you have analytics to support them.

A useful test: open the homepage and cover all banner areas with your hand. If the user path is still clear without them, the structure is solid. If the page falls apart, the banners are acting as a crutch for missing navigation and content.

Reviews, Categories, and Store Logic

What makes Affility interesting is that it combines blog-style reviews with storefront-style product presentation. In practice, that means working with two different content types. A review answers the reader’s question and helps them decide. A category or product card helps them move quickly toward a choice. If you blur those roles together, the page becomes harder to understand: the review starts to feel like a catalog, and the catalog starts to read like a stack of short ad notes.

The official product page mentions review pages, product showcases, store categories, and a store landing page. Current JoomShaper materials also reference EasyStore, while older descriptions and parts of the demo context mention J2Store. So when configuring the site, do not name the component from memory. Open the package or the installed site and verify which component is actually present in your build.

How to Structure the Review Layer

For review pages, use a structure where the reader can understand the selection criteria. A strong review should be more than a heading, an image, and a button. It needs setup context, strengths and limitations, who the product is a good fit for, who should consider something else, comparisons with similar options, and an honest conclusion. The template provides attractive presentation zones, but responsibility for the substance still belongs to the editor.

Recommended Review Structure

• State the product or category use case clearly and briefly.
• Show the main characteristics, but do not overload the page with a table that has no conclusions.
• Add a “who it is for” and “who should look elsewhere” section.
• Place the affiliate button after the reasoning, not in place of it.
• Update the content when the link, price, availability, or seller terms change.

How to Build a Product or Store Category

A category should help focus attention. In EasyStore, categories are created through the component’s admin panel and can then be displayed on SP Page Builder pages through the appropriate addons. If your build uses a different store component, the logic is similar: first create categories, then products, then the page that outputs the relevant list.

For Affility, intent-based categories are especially useful, not just product-type categories. Instead of generic sections like “Electronics,” “Home,” or “Sports,” you can build sections such as “Gifts Under a Mid-Range Budget,” “Home Office Tech,” or “Products with Quick Comparisons,” as long as those sections are supported by real site content.

A Content Model for an Affiliate Project

With Affility, it is tempting to fill the homepage with ready-made cards and call the site launched. But for an affiliate project, it matters far more to define in advance which page types will exist in the system and how they connect to each other. The template gives you strong visual placements, but it does not decide for the editor where a review ends, where a category begins, how a roundup differs from a promotional offer, or why the user should trust the conclusion.

A practical model can be built in four layers. The first layer is the homepage, which shows the main user paths. The second is categories for reviews and product directions. The third is individual content pieces: reviews, comparisons, roundups, and guides. The fourth is commercial click-throughs: buttons, banners, cards, stores, and offers. If you do not separate those layers, the site quickly turns into a series of similar-looking blocks where every button promises value, but no section actually explains the choice.

The Review as a Trust Layer

A review should be the most substantial element on the site. It should show selection criteria, product limitations, a personal or editorial conclusion, alternatives, and the situations where the product is not a good fit. In Affility, that kind of content can be surfaced in recent review blocks, editorial picks, and popular article sections. The key is not to reduce every review to a short card with an affiliate button. Users come for an answer, not a banner.

In Joomla terms, that means working carefully with article categories, aliases, meta descriptions, and internal links. If a review belongs to several themes, it is usually better to choose one primary category and create secondary connections through tags, manual links, or “related articles” blocks. That makes URLs easier to control and keeps navigation cleaner.

The Roundup as a Fast Decision Path

A roundup differs from a review because its purpose is to narrow the choice quickly. For example, not “a review of one vacuum cleaner,” but “what to choose for a small apartment.” In Affility, pages like that work especially well next to showcase-style blocks: the homepage can feature the roundup card, the article itself can present several options, and the ending can link to a category or store page. A roundup should shorten the path to a decision, not disguise an ad list as expert content.

The Offer as a Time-Sensitive Element

Blocks with a timer, discount, or bold call-to-action require discipline. If the offer is time-sensitive, it needs an owner: someone who checks the link, someone who removes the block, someone who updates the text. For static affiliate recommendations, it is usually better not to use a countdown. A broken timer or expired price does more damage than a simple “view offer details” button.

The Category as Navigation, Not Storage

A product or review category should explain what the user will find there. Add a short introduction, three to five key paths, and clear cards. If the category is output through a store component, confirm that the products have images, short descriptions, correct aliases, and published status. If the category is output through articles, check that the module or addon is pulling content from the right source.

Internal Linking Without Chaos

For an affiliate site, a simple linking model works well: the homepage leads to categories, categories lead to reviews and roundups, reviews lead to offers and related materials, and commercial blocks do not interrupt the editorial path. Do not place ten identical buttons on one page. One strong contextual click-through after the reasoning, plus several navigational links to related content, is usually enough.

Checking internal linking takes less time than fixing it later. Open one new review, click every internal link in it, return to the category, then repeat the same path from the mobile menu. If the user ends up at a dead end, the site may be visually configured, but the navigation still is not ready.

Menus, Off-Canvas Navigation, and Module Positions

In Joomla, the template defines positions, and modules are rendered into those positions and assigned to menu items. With Affility, this is critical: the main menu, mobile off-canvas menu, sidebar blocks, banners, footer, subscription area, and supporting zones should not operate independently of one another. If a module is missing on the frontend, the problem is often not the template itself, but the position, publication status, access level, or menu assignment.

The official Affility documentation on module positions notes that the layout can be changed through the Layout Builder in Helix Ultimate, and that sidebar modules on article detail pages may require article blog settings to allow module output. It also mentions the Content Top and Content Bottom positions, which can render above and below the component area even if they do not look like a standard part of the grid.

Configuring the Main Menu

Start by checking the user paths, not the styling. The menu should contain clear sections: home, reviews, best roundups, offers, store categories, the store or showcase, the affiliate disclosure page, and contacts. Remove demo items that you will not actually fill. An empty item inside a polished mega menu is worse than a simple, honest menu structure.

Off-Canvas Menu for Mobile Users

The off-canvas menu is useful when the full structure will not fit on a mobile screen. But it should repeat the important user paths, not become a separate menu with different logic. Make sure the mobile item leads to the same destination as the desktop item, and that nested categories expand in a predictable way.

Module Positions and Page Assignment

For an ad block, subscription form, review category list, or sidebar article list, create a module, choose a position, and configure Menu Assignment. If a module is needed only on review pages, do not publish it site-wide. If a block should appear on articles but not on the homepage, assign it only to the relevant menu items or create a hidden menu item for the output type you need.

1. Open the site modules list and filter by the required type.
2. Check the publication status, position, order, and access level.
3. Open the menu assignment tab and select only the pages where the module is actually needed.
4. Save the module and clear the cache if caching is enabled.
5. Test the page as a guest and as a logged-in user if the module depends on access permissions.

Multilingual Setup, Access Rights, and Editorial Control

Affility is often used on sites where visitors come from different channels: search, social media, affiliate campaigns, or email. If the site will be multilingual or partially restricted for partners, do not postpone that setup until the end. In Joomla, language, menu item, module, and article are more tightly connected than they may appear. Translating only the homepage text is not enough: you also need to verify menus, categories, modules, forms, buttons, and URLs.

Multilingual Pages

For each language, create separate menu items and articles, not just a copied text block in the visual editor. If a subscription module or banner is published for all languages but contains text in only one language, the user ends up seeing a mixed-language page. In Joomla, use language-specific module versions, language overrides, and article associations where your workflow requires them.

Be especially careful with commercial buttons. An affiliate program may direct users to different regional pages, and a link that works for one language version may not fit another. If regional links are not confirmed, it is better to keep a general destination and explain that in the text than to quietly send users to the wrong page.

Editor Permissions

In an affiliate project, one person may write reviews, another may update banners, and a third may verify links. Do not give everyone full Super User access unless there is a real need. The safest practical approach is to split responsibilities: the content editor handles articles, the template administrator manages SP Page Builder and modules, and the technical specialist takes care of updates, backups, and integrations.

If editors work in SP Page Builder frontend mode, explain in advance which sections they can edit and which ones are better left alone. For example, review cards and text blocks can be updated regularly, while the header, navigation, positions, and global styles are better changed only after testing. One accidental edit to a global section can affect more pages than the editor view suggests.

Affiliate Link Control

Add routine link checks to the workflow. For the main offer, roundups, and store categories, a simple spreadsheet is enough: site page, link, owner, date last checked, and status. Those technical dates do not need to appear in the article itself, but they are valuable in the editorial process because they help prevent outdated offers from staying on the homepage.

Safe Publishing of Changes

Before making a major homepage edit, create a page copy or take a backup snapshot. After the change, test the page as a guest first, then as a logged-in user. If caching is enabled, clear it after structural changes, but do not use cache clearing as a universal fix for every issue. If a change breaks the layout, roll back the last section, not the entire template.

Practical Example: Building the Homepage of an Affiliate Site

Below is a concrete scenario you can reproduce on a test copy. The goal is to turn the Affility demo homepage into a working page for a site focused on home appliance and household product reviews. The example does not rely on imaginary features. It is built around the homepage, the visual editor, categories, modules, menus, and showcase blocks.

Goal

The goal is to create a homepage where a new visitor sees a featured offer first, then the latest reviews, then several themed roundups, a subscription block, and a sidebar with popular content. The page should make sense on both desktop and mobile, and every button should lead to a real destination.

Preparation

• The Affility template is installed, or QuickStart has been deployed on a test copy.
• You already have at least several Joomla articles assigned to review categories.
• Images for the featured offer and content cards have been prepared.
• The store component has been verified if you are using a product showcase.
• Menu items exist for the homepage, reviews, offers, and categories.

Setup Steps

1. Open the homepage in SP Page Builder and rename it to the project’s working title.
2. In the main deal block, replace the product, image, short description, and button link.
3. In the reviews block, select an article category that already contains published content.
4. In the showcase block, choose the product or store categories that should serve as the main navigation paths.
5. Insert an ad banner in only one top or middle zone so it does not overpower the review blocks.
6. Check the subscription form: it should have clear wording, a valid handler, and should not look like a decorative element.
7. Configure the mobile menu and confirm that all core sections are accessible without horizontal scrolling.
8. Clear the cache and open the page in guest mode.

Verification

After saving, test four user paths. The first is from the featured offer to the product card or affiliate destination. The second is from a review to its related category. The third is from the menu to the offers page. The fourth is from the mobile off-canvas menu to those same sections. If even one path leads to a demo page, an empty category, or an error page, the homepage is not ready yet.

A Detail People Often Miss

Not every homepage block should be dynamic. In some cases, it is better to leave certain sections manually curated in SP Page Builder, especially for editorial roundups. But content that needs regular updates should usually be driven by categories or addons. Otherwise, the editor ends up manually replacing the same block after every new publication.

Checking the Final Result on the Site

Testing Affility should go beyond a visual check. A polished first screen does not prove that the site actually works correctly. You need to walk through the user path, verify modules, mobile navigation, images, links, cache behavior, forms, and how easily the page is understood. Pay special attention to pages that were not visible on the demo’s first screen: article detail pages, product categories, offer pages, search, affiliate signup, and the footer.

What to Check on the Frontend

• The header, logo, search, language switcher, and login display as intended.
• The main menu and off-canvas menu lead to the same up-to-date sections.
• The featured offer block does not show an outdated timer or demo pricing.
• Reviews are pulled from the correct categories, and cards do not repeat the same text.
• Sidebar modules appear on detail pages if that is where they are meant to be shown.
• All images have been replaced with approved assets, and placeholders are gone.
• The subscription form and affiliate page both offer a clear next step.

What to Check in the Admin Panel

In the admin panel, verify the template style assignment, the module list, menu items, article categories, SP Page Builder pages, and the store component settings. If the site uses multiple languages, make sure menu items, modules, and content exist for each language, not just the primary one.

SEO and Usability Without False Promises

Affility gives you a convenient content structure, but it does not guarantee search growth. SEO depends on review quality, speed, internal linking, clean URLs, proper headings, and the trustworthiness of the content. On an affiliate site especially, users need to see not just a button, but a useful explanation of why a particular choice makes sense.

Checking Perceived Page Speed

Affiliate templates often include a heavy visual layer: large images, banners, sliders, cards, icons, video, and third-party scripts. Even if the technical performance is acceptable, the page can still feel overloaded. Check the first screen while logged out, then scroll to the reviews and subscription sections. If the user sees three competing calls to action in a row, one of them should be removed or pushed lower.

Optimization starts with simple things: compressed images, a sensible number of cards, unused demo sections disabled, careful video loading, and no random third-party scripts. Do not add analytics, advertising, or widget code until you have tested the base page. Otherwise, it becomes difficult to tell what is actually slowing down or breaking the output.

Trust Check

An affiliate site should explain why its recommendations are worth trusting. That means the homepage and review pages need more than buttons. They also need a transparent selection logic: criteria, limitations, freshness tracking within the editorial workflow, an author or editorial policy, and a clear about page. Affility includes pages that can be adapted for team and affiliate information. Use them as real reference points, not as formal demo fillers.

Safe Improvements Without Editing Core Files

With Affility, it is better to start with Helix and SP Page Builder settings instead of editing template files directly. Helix documentation recommends using custom code fields or separate files such as custom.css, because changes made to base CSS files can be lost during updates. That is a standard safe practice for templates: override the appearance on top of the framework instead of modifying the core styling itself.

A Small CSS Tweak for a Cleaner Promo Block

If the top banner or deal block feels too aggressive, you can add a softer visual boundary. Insert code only in the location intended by the template or by Helix, such as custom CSS, and test it on a staging copy first.

.affility-deal-check {
  border-radius: 6px;
  box-shadow: 0 8px 24px rgba(28, 23, 68, 0.08);
}

.affility-deal-check .sppb-btn {
  min-height: 44px;
  letter-spacing: 0;
}

This example does not rely on hidden APIs or modify core files. It demonstrates the principle: add your own class to the relevant section in the editor, then style only that section. Rolling it back is simple: remove the class or the CSS rule. If you do not assign the class in SP Page Builder, the rule will not affect the site.

Language and Text Adjustments

If you need to replace a system string, label, or interface text, use Joomla language overrides first instead of searching template files for the string. That approach is easier to maintain after updates and safer on a multilingual site.

When Not to Add Code

Do not add JavaScript just to animate buttons if it interferes with forms, the cart, search, or the mobile menu. Do not hide important elements through CSS if they can be disabled in the module or template style settings. Configuration through the interface is always preferable to code edits when it gives you the same result.

Diagnosing Common Affility Issues

Most issues that appear after installing the template are not caused by a single “breakage,” but by a mismatch between the demo structure, the actual modules, menus, cache, and access permissions. It is best to troubleshoot from symptom to cause: what is visible on the site, which element is supposed to render it, where that element is configured, and why Joomla might not be showing it.

The demo installed, but the images do not match the preview

Symptom: instead of polished photos, you see placeholders, empty spaces, or different images. Possible cause: demo photography may not be included in the package because of licensing restrictions. Check JoomShaper’s documentation about demo images and replace them with your own assets. Fix: upload legal images to the media manager, then update the SP Page Builder sections, cards, banners, and categories. Rollback: restore the previous page version or recover the media from backup.

A sidebar module is missing on an article detail page

Symptom: the module exists in the module list, but it does not appear on the article page. Possible causes include the wrong position, publication status, access level, menu assignment, or Helix blog detail settings. Check the position, Menu Assignment, access level, and the setting that enables module output on detail pages. Fix: assign the module to the correct menu items, enable sidebar modules on detail pages, and clear the cache. Rollback: restore the previous menu assignment or disable the module.

The homepage does not save changes

Symptom: the editor shows the changes, but the site still displays the old block. Possible causes include Joomla cache, template cache, browser cache, editing the wrong page, or an editor permission conflict. Check which menu item is assigned as the homepage, open the correct page in SP Page Builder, save a small test edit, and clear the cache. If the issue persists, verify user permissions and review the error logs.

The mobile menu shows the wrong items

Symptom: the desktop menu is correct, but the off-canvas menu shows outdated or incomplete items. Possible cause: a different menu module, a separate position, or a demo module that was never updated. Check the module published in the off-canvas position, its source menu, and its access level. Fix: assign the same set of key sections, or deliberately create a separate short mobile menu.

The layout breaks after enabling ad code or custom code

Symptom: part of the page disappears, blocks overlap, or the editor shows strange output. Possible causes include invalid HTML, a script placed in the wrong location, or a conflict with a security component or cache. Check the most recently added code, disable it temporarily, clear the cache, and inspect the browser console. Fix: place code only in the Helix areas intended for it, keep the snippet minimal, and avoid interfering with forms, the cart, or menus.

A product or review category is empty

Symptom: the page opens, but no list of products or articles is displayed. Possible causes include unpublished items, items assigned to a different category, the wrong source selected in an SP Page Builder addon, or a menu item that points to an empty category. Check the publication status, category, language, access level, and output block settings. Fix: publish a test item, assign the category, and check the page again as a guest.

Practical Ways to Use It

Affility does not have to be limited to a “best products of the month” site. It can support several practical scenarios if you stay within the features provided by the template, Joomla, SP Page Builder, and the store layer. The key is to connect content, user flow, and verification in each scenario.

Niche Review Site

Use the homepage as the entry point to recent reviews, best roundups, and categories. The deal block works well for one strong featured offer, but it should not replace editorial expertise. The result is easy to test: the user should be able to get from the homepage to the relevant review and back to the category in two clicks.

Coupon or Seasonal Campaign Site

Use offer pages, timers, and banner zones for temporary promotions. One important detail: do not leave expired offers in prominent positions. If expiration is not managed automatically, keep an editorial calendar for link reviews.

Affiliate Store Directory

Group stores by category and present them as a navigational showcase. For each store, add a short description, the product type, the click-through conditions, and several content pieces that explain why readers may want to look there. Do not turn a store page into a pile of buttons with no context.

A Lightweight Showcase Backed by Content

If EasyStore or another verified component is installed, use product categories as the structural layer and reviews as the trust layer. Visitors should be able to see a product card, but also have a link to a review, comparison, or roundup. That keeps the showcase from feeling like an empty sales grid.

The core rule for every scenario: do not add a new section just because the template has space for it. Every block should lead to the next clear action: read a review, compare options, open a category, check the terms, or subscribe for updates.

Similar Solutions and When They Make More Sense

Template Video and How to Use It

JoomShaper provides a video specifically related to Affility. Use it as a quick visual overview of the design and the key sections, not as a substitute for the actual setup process. After watching, open your own test copy and walk through the same areas: the top menu, the main deal block, the review sections, offers, the store layer, and the built-in pages.

The video supports the intent of “what Affility looks like and which blocks you should verify after installation.” It is especially useful before editing the homepage, because it helps you understand which sections are essential and which ones can be removed without weakening the purpose of the site.

When JoomShaper Affility Is the Right Choice

Affility is worth using if you need a Joomla template for an affiliate or review-driven project where content, showcase sections, categories, and promo blocks should work as one system. Its strength is not a single button or one attractive hero block, but the built-in page logic: the user sees an offer, then reviews, then categories and additional paths.

Before launch, check the server requirements, package contents, demo structure, your own images, menus, module positions, and the store component. After setup, make sure to walk through the site like a regular visitor: homepage, review, category, offer, mobile menu, form, and affiliate link. If everything opens cleanly without demo placeholders or excessive banners, you can move on to publishing and get the JoomShaper Affility package for a test installation or to update your local copy.

The best result will not come from the person who replaces the logo the fastest, but from the one who carefully maps the template structure to real categories, reviews, and commercial click-throughs. That is when Affility stops being just a design and becomes a working knowledge base and navigation system for an affiliate site.