BA Gallery - Joomla Extension

Guide to Setting Up and Using BA Gallery on a Joomla Site

BA Gallery is best treated not as just another decorative photo block, but as a working tool for pages where images need to help visitors choose, compare, and understand the content. This guide covers installation, category logic, image uploads, output through a menu item and a module, result checking, troubleshooting common issues, and situations where a different solution may be a better fit.

This material is written for a Joomla administrator, webmaster, or content editor who already has the extension archive and wants to publish a gallery on the site safely. It does not cover purchasing, payment, or license activation. The focus is strictly on how to prepare the site, configure galleries, avoid overloading the page, and quickly understand why the result may differ from what you expected.

The official BestAddon page describes BA Gallery as a Joomla photo gallery extension with several display options, and the demo shows different output styles: thumbnails, masonry, mosaic, slideshow, carousel, browser, blog, polaroid, hexagon, and album-based layouts. That matters because with a product like this, the quality of the result depends not only on installation, but also on choosing the right layout for the specific content.

The guide is built around a practical sequence: prepare images - create the structure - display the gallery - check the public-facing page - fix any conflicts if they appear. That approach is more useful than simply listing features, because a gallery is almost always tied to the template, cache, menu structure, module positions, and page load speed.

Where BA Gallery Is Actually Useful

BA Gallery works well on Joomla sites where images are the main content rather than incidental illustrations inside text. That could be a studio portfolio, a showcase of completed work, a real estate listing page, an event photo block, a restaurant visual showcase, a product selection without a full store, or a before-and-after project presentation. In those scenarios, the visitor wants to browse a lot of images quickly and open a larger view without jumping through dozens of separate pages.

The extension's strength is that it combines several common gallery tasks: image uploads, grouping through categories, displaying a dedicated gallery page through the menu, and showing a block in a template position through a module. BestAddon documentation shows a workflow that includes the component, category creation, image uploads, a menu item for gallery viewing, and a separate module. This is not just "an image inside an article" - it is a standalone gallery structure inside Joomla.

When a Gallery Matters More Than a Regular Article Image

A regular image inside an article works well when you only need to support one specific piece of text. A gallery is needed when the visitor has to compare a series of visual objects. For example, in a renovation portfolio, a single image rarely answers questions about quality. You need an overview, details, multiple angles, close-ups, and the final result. If you insert all of that as regular article images, the page becomes long and heavy. A gallery helps organize those images into a manageable grid.

With BA Gallery, choosing the display type is especially important. The BestAddon demo page shows several options: thumbnails work well for an even grid, masonry is better for images with different heights, mosaic creates a denser visual showcase, slideshow is useful for sequential viewing, and carousel can work as a secondary block on the homepage or in a sidebar area. The exact same set of photos can look polished or chaotic purely because of the selected layout.

When the Extension May Be Unnecessary

If the site only needs two photos inside a single article, a separate gallery extension may be excessive. Joomla already handles images through articles and the Media Manager, and the template often includes its own image styling. BA Gallery makes sense when you plan to add collections regularly, manage categories, show galleries through menu items, or place them as modules in different parts of the site.

The extension may also be the wrong choice for a complex media catalog with user uploads, public author profiles, image sales, fine-grained per-file permissions, or deep integration with external storage. Official BestAddon sources confirm the core gallery scenarios, but they do not justify promising the features of a full media platform. If that kind of logic is required, it is better to compare BA Gallery with larger gallery components in advance.

What to Check Before Installing the Extension

Preparation matters for practical reasons, not just formality. A gallery adds images, scripts, styles, and a lightbox-style viewer to the page. If you install the extension on an unprepared site, the issue may look like a BA Gallery error when the real cause is an outdated template, a conflicting optimizer, overly heavy photos, or an incorrectly published menu item.

The BestAddon product page lists compatibility with multiple Joomla generations and basic server requirements. It is not a good idea to hard-code specific version claims into an article as if they were permanent facts, because compatibility changes over time. In practice, it is more useful to check three things before installation: whether your Joomla version matches the current extension package, whether the server supports the required PHP version, and whether you can roll changes back quickly if needed.

Minimum Site Preparation

• Create a backup of both files and the database before installing a new extension.
• Make sure you have access to the Joomla admin panel with permissions to install extensions.
• Confirm that package upload installation is not disabled by the server or hosting environment.
• Prepare 10-20 test images that have already been resized to a reasonable web-friendly size.
• Create a draft menu item or test page where you can check the gallery without risking the main section of the site.
• Temporarily disable aggressive JavaScript and CSS bundling in your optimizer if the site already uses those settings.

The last point matters for galleries with effects, lightboxes, and carousels. Joomla and extensions rely on JavaScript and CSS for interactive output. Official Joomla documentation on web asset management explains that dependencies between styles and scripts matter. If an external optimizer changes the loading order, some behavior may break.

Preparing Images Before Upload

One major mistake is uploading original camera files directly into the gallery. Those files can be huge in both size and weight, while the visitor usually needs a fast, sharp web version rather than the original photo. Before uploading, prepare the images in a consistent way: a clear naming pattern, a logical sequence, reasonable compression, consistent color treatment, and no unnecessary duplicates.

For a portfolio, names like kitchen-project-01.jpg, kitchen-project-02.jpg, and kitchen-project-detail.jpg work well. Even on a Russian-language site, it is safer to avoid Cyrillic characters in file names unless you are fully confident in the server and backup setup. You can use normal Russian captions in the page content, but the files themselves are more reliable when stored with Latin characters, numbers, and hyphens.

Pre-installation check: if a test page with regular images already loads slowly, reduce file size and check caching first. BA Gallery should not become a way to hide a problem caused by overly heavy source files.

Installation and the First Check in Joomla

The official BestAddon guide describes manual installation through the Joomla admin panel: go to System, open Install / Extensions, select the Upload Package File tab, upload the archive, and then move on to enabling or configuring it through Joomla pages. If the archive includes a label such as UnzipFirst.zip, you need to extract it locally first and install the actual extension package rather than the outer container.

Screen names may vary slightly across Joomla versions, but the logic stays the same: install the extension through the system section, then locate the installed component or module. The important point is not to rush into placing the gallery on a live page right away. First, make sure installation completed without errors, the extension appears in the list, and the expected management items are present in the admin panel.

Step-by-Step Installation Without Unnecessary Risk

1. Download the installation archive from your account or the source used by your project.
2. If the archive requires extraction first, unzip it on your computer and locate the BA Gallery installation package.
3. Open the Joomla admin panel and go to System - Install / Extensions.
4. On the Upload Package File tab, select the extension ZIP package.
5. Wait for the successful installation message and do not refresh the page while the upload is in progress.
6. Check whether the BA Gallery component and any related modules or plugins included in the package are now available.
7. Create a test category and upload several prepared images.
8. Display the test gallery through a separate menu item or module, but do not publish it in an important section of the site yet.

If the installation is interrupted, do not keep retrying the upload over and over. First check the file size, the server upload limit, permissions for the Joomla temporary folder, and whether the package matches your CMS version. Reinstalling over a partially installed extension can create confusion: the component may already exist while the module or media files did not install correctly.

What You Should Have After Installation

After a successful installation, you should be able to manage galleries through the component and, if the package includes module output, create or configure a module. BestAddon documentation separates the component guide from the module guide. That is a useful distinction: the component handles gallery data, while the module controls where part of that gallery appears on the page.

A quick check is simple: upload a small set of images, create a temporary menu item, open the page in incognito mode, and make sure the grid is visible without logging in. If the public side shows a blank page while the images are visible in the admin panel, the issue is usually not the file upload itself, but category publication, the menu item, access permissions, or a script conflict.

Categories, Images, and Gallery Logic

Galleries have one trait that new administrators often underestimate: order and structure matter just as much as the visual effect. If you dump all images into one large pool, the first pages may look fine, but after a few months editing becomes chaotic. That is why it is better to start working with BA Gallery by defining categories and naming rules.

The official BA Gallery documentation explicitly separates Create a category from Upload images. That is a good signal: define your logical groups first, then fill them with files. In Joomla more broadly, categories are used to group records, and official Joomla documentation describes the category structure as a tree inside a component. Even if the BA Gallery interface is simpler, it still makes more sense to think in categories.

How to Plan Categories Without Creating Future Confusion

For a portfolio, categories can be based on the type of work: "Kitchens," "Bathrooms," "Facades," or "Commercial Interiors." For events, organize them by event or season. For a property catalog, group them by property type or location. The main rule is simple: a category should help both the visitor and the editor, not just mirror an internal folder on someone's computer.

If BA Gallery is used on an agency website, it can be helpful to add not only images but also short captions, if the extension interface supports them. A caption should explain context: what is shown, why the shot matters, and how it differs from nearby images. There is no need to turn captions into marketing slogans. Galleries work better with precise phrases such as "Tile section after installation," "Full room view," "Before lighting adjustment," or "Finished display area."

How to Choose a Layout for the Type of Photography

The BA Gallery demo shows several output formats, and they are not just visual gimmicks. Each format solves a different problem. An even grid works well for cards with the same aspect ratio. Masonry helps when vertical and horizontal images are mixed together. Mosaic gives the page a more editorial look, but it requires more careful image selection. Slideshow is useful when you want to lead the visitor through a fixed sequence. Carousel works as a compact block, but it does not replace a full image archive.

Once you pick a format, be sure to view the page on a narrow screen. Galleries often break not on a large monitor, but on a tablet or mobile browser where the grid becomes too dense, captions disappear, or lightbox controls sit too close to the edge of the screen.

Configuring BA Gallery After Installation

This setup section should answer one practical question: what should you do right after installation so the gallery looks controlled and does not get in the site's way? There is no universal set of perfect values, but there is an order that reduces the risk of mistakes. Start with structure and output, then adjust the visual mode, then performance, and only after that move on to extra effects.

Do not turn every effect on at once. For a gallery, what matters is that the visitor immediately understands what they are looking at: a grid of work, albums, a slideshow, or an image collection inside a module. If you enable complex animation, a dense grid, captions, a lightbox, and auto-scroll all at the same time, the visual effect can overpower the content itself. The best BA Gallery settings are not the maximum number of enabled options, but a clear chain of "category - layout - display location - result check".

Initial Component Settings

Start by creating one test category. Do not move your entire image archive over at once. Upload a few files with different proportions: a horizontal shot, a vertical shot, a square image, and an image with an important detail near the edge. That set will quickly show how the chosen layout crops thumbnails, how readable the captions are, and whether the large-view mode opens comfortably.

Then review the basic image entry fields: title, description, publication, order, and category. If your BA Gallery version includes settings for thumbnail size, number of columns, opening effect, or sorting mode, change them one at a time. After each change, save and refresh the public page while logged out.

Safe Setup Order

1. Create a category with a clear name and make sure it is published.
2. Upload a small test set of images and fill in basic titles.
3. Select one output layout and test it on the site's actual template.
4. Adjust the number of items shown on the page or in the block, if that option is available.
5. Check the lightbox view and navigation between images.
6. Enable extra effects only after the basic output works reliably.

This order makes rollback easier. If the gallery stops opening after you enable an effect, you know the last change caused the problem. If you switch on ten settings at once, you are left guessing.

Menu Item or Module: Which One to Choose

BA Gallery can be used as a standalone gallery page and as a block on an existing page, if the module package is available in your installation. A menu item is better for a full section: a portfolio, project photo gallery, event archive, or work showcase. A module works better as a compact fragment: recent projects on the homepage, a collection in a sidebar, or a short carousel on a service page.

Official Joomla menu documentation explains that a menu item affects more than just the link - it also defines the active page context. That matters for a gallery because the active menu item can determine template styling, module positions, and whether the page is available in the expected way. If you display a gallery without a proper menu item, the site may generate a less usable URL or apply the wrong set of modules.

Module Settings and Page Assignment

If you are using the BA Gallery module, check four areas: publication status, template position, menu assignment, and the selected image source. Joomla modules in general are lightweight extensions displayed around the main page component. Because of that, a gallery module may behave correctly in one position and look odd in another, especially if the template uses different column widths.

For the homepage, a wide position below the intro block or above the footer usually works best. On a service page, you can place the module after the main text to show examples of completed work. A sidebar only makes sense for a very compact mode: a carousel, a short list, or a few thumbnails. If the module outputs a large masonry grid inside a narrow column, the result usually looks overloaded.

How to Roll Back a Questionable Setting

Before changing the module, note the current position, publication state, selected menu items, and gallery source. If the block disappears after the change, restore the previous position and assignment. If administrators can see the gallery but guests cannot, check the access level for the module, category, and menu item. Joomla ACL separates what a user can see from what they can do, so an access issue is not always caused by the extension itself.

Practical Example: A Project Portfolio With a Dedicated Page and a Homepage Block

Let us walk through a scenario that suits BA Gallery well: a studio website wants to show an interior design portfolio. It needs a dedicated "Projects" page where visitors can browse the full collection, plus a small homepage block with recent work. That example covers two important display methods: the component through the menu and the module in a template position.

Goal and Preparation

The goal is to create a clear project gallery where each project includes several images and the visitor can open a large view without leaving the page. Before setup, prepare 12-18 images: 3-4 shots for several projects. Resize the files sensibly, remove duplicates, give them Latin-character names, and choose one consistent visual editing style.

In the Joomla admin panel, create a test menu item or draft section in advance if you do not want to change the live menu right away. Also decide whether the gallery should be available to all visitors or only to a specific group. A standard portfolio usually needs public access, but for private client collections you should test Joomla access levels separately.

Setup Steps

1. In the BA Gallery component, create a category called "Projects" or several categories by work type.
2. Upload the prepared images into the appropriate category.
3. For each image, enter a short title so the editor can easily understand the collection later.
4. Select the masonry or mosaic layout if the photos have mixed proportions, or thumbnails for an even grid.
5. Create a menu item that displays the gallery or a list of galleries, depending on the menu types available in your extension version.
6. Open the public page and check the grid, the large-view mode, navigation, and the page URL.
7. Create a BA Gallery module for the homepage and select the same category or a limited set of images.
8. Assign the module only to the homepage or to the relevant menu items so it does not appear throughout the entire site.

After those steps, you will have a main portfolio page and a compact homepage block. If the module supports limiting the number of items, do not output the entire gallery on the homepage. A few strong shots and a link to the full section are enough. The homepage should spark interest, not replace the archive.

Expected Result and Verification

On the dedicated page, the selected gallery should open with an even grid or the chosen visual mode. Clicking an image should open the larger view if that feature is enabled in the settings. The module on the homepage should occupy a predictable place, should not shift other blocks, and should not appear on pages where it is not needed.

The key nuance in this scenario is mixed photo proportions. If an important part of the image gets cropped in the grid, do not rush to replace the extension. First check the source files, the layout, and the thumbnail settings. For portrait-oriented images, masonry often works better, while project cards tend to look better with pre-prepared images using the same aspect ratio.

How to Check the Result on the Site

Result checking should go beyond "the page opens." A gallery may display while still being too heavy, awkward on mobile, inaccessible to guests, or in conflict with the template. That is why, after configuring BA Gallery, you should run a short manual audit.

Public-Facing Check

• Open the page in a normal browser and in incognito mode to rule out the effects of administrator login.
• Make sure guests can see the images and that no access-denied message appears.
• Click several thumbnails and confirm that the large-view mode opens and closes correctly.
• Check navigation inside the viewer: next image, previous image, close action.
• Open the page on a mobile screen and make sure the interface does not become too small.
• Clear the Joomla cache and any external optimizer cache if the page still shows the old result after changes.

If the site uses a CDN, image optimization, or resource bundling, check the result twice: immediately after saving and again after clearing cache. Sometimes the administrator sees the fresh version while a regular visitor still gets old styles or old JavaScript.

Checking Speed and SEO Cleanliness

The gallery should not turn the page into a collection of heavy files without context. For SEO, what helps is not only the images themselves, but also the surrounding text: the section heading, a short explanation, captions, and a logical page structure. BA Gallery handles the visual output, but the meaning still needs to be framed inside the Joomla article or next to the module.

From a performance standpoint, check the total page weight and the number of images above the fold. If the gallery shows too many thumbnails at once, reduce the number of items, split the collection into albums, or use a separate page instead of a heavy homepage block. A gallery should support decision-making, not slow down the visitor's first look at the page.

Display Scenarios: Full Page, Albums, and Compact Blocks

After the initial setup, it is important to decide how the gallery will live inside the site structure. BA Gallery offers several visual modes, and the documentation separately describes menu-based and module-based use. That creates not one but several editorial scenarios. Problems begin when all of those scenarios are forced into the same configuration: a full gallery is placed in a narrow position, a carousel is used as an archive, or albums are created without clear titles.

A full gallery page is needed where the visitor comes specifically to look at images. A compact module is useful where images support the main text or lead into a full section. Albums are useful when you have several collections and the user needs to choose a topic before viewing specific shots. If you separate those roles in advance, BA Gallery becomes a predictable tool rather than a collection of random visual blocks.

Full Gallery Page

A full page works best when built around one clear purpose: showing a portfolio, an event archive, a property collection, or a visual catalog. Before the gallery, add a short text introduction in the article or on the page so the visitor understands the context. After the gallery, you can add a link to a contact form, service page, or another next step. That way the images are not floating in a vacuum, but become part of the user's path through the site.

For a full page, avoid relying on a very small carousel. Visitors expect an overview, the ability to compare shots quickly, and a large-view mode. If there are many photos, it is better to split them into categories or albums than to force the page to load everything at once. With long collections, group titles and image order become especially important: first the overview, then the details, then the final shot or the strongest example.

Album Structure

Albums make sense when each collection has its own standalone meaning. For example, for an interior design studio, an album might represent a specific project; for a school, a specific event; for a travel site, a destination. The BA Gallery demo shows compact and list-based album views, so before launch it is worth checking which format fits better with the number of collections and the length of their titles.

Do not make albums too small. If each album contains only two images, the visitor ends up constantly clicking in and out, and the structural benefit disappears. On the other hand, it is also a bad idea to dump 80 images into one album with no internal logic. A good album answers the question "what am I looking at right now?" before the user even clicks the first photo.

Compact Module on the Homepage or a Service Page

Module output works best as a showcase. Its job is to display a few strong shots and guide the user into the full section. That means the module should have a limited number of images, a restrained layout, and assignment only to relevant menu items. If the module appears on every page, it quickly turns into visual noise and increases page weight without adding value.

On the homepage, 4-8 images are usually enough. On a service page, 3-6 examples tied specifically to that service are often sufficient. If you use a carousel, check that the controls are visible and that auto-scroll does not interfere with reading the text. If the images themselves are important for making a choice, it is better to send the user to the full gallery than make them wait for slides to rotate.

An Editorial Workflow for the Gallery So the Site Does Not Slowly Fall Apart

A gallery looks good on launch day because the administrator carefully selects the first set of photos. Problems start later: different editors upload files in different sizes, category names become random, old projects remain mixed with new ones, and the homepage gradually gets heavier. That is why it helps to define a lightweight workflow for BA Gallery. This is not bureaucracy - it is simply a way to preserve the quality of the visual section.

You can store that workflow in a regular project document. It is enough to define image sizes, file naming rules, who creates categories, who checks the mobile view, and how many images are allowed on the homepage. For a small site, that fits on one page, but it can save a great deal of time during updates.

Rules for Files and Captions

Set a maximum image width, an acceptable file size, and a naming format. Those rules do not need to be visible to site visitors, but the editor should know what to upload. A good practice is to store the originals separately and upload only prepared web files into BA Gallery. That way the extension does not become a warehouse for heavy source assets.

Captions are also worth standardizing. For a portfolio, use a pattern like "project - angle - detail"; for events, "event - moment - participants"; for a catalog, "item - feature - condition." If a caption adds nothing, it is better to leave it blank than to repeat the same generic phrase everywhere. But for important images, a short caption helps both the visitor and the editor.

Periodic Checks After Updates

After updating Joomla, the template, a caching extension, or BA Gallery itself, open one full gallery page and one module block. Check the grid, the large-view mode, the mobile layout, and the cache behavior. This is especially important after changes related to JavaScript and CSS, because the gallery depends on public-side page behavior, not only on the data saved in the admin panel.

If the problem appears after an update only in one template style or one position, do not assume the extension is completely broken. Compare the page against a different menu item, temporarily change the module position, clear cache, and inspect the browser console. That kind of short control loop helps you quickly identify which layer is causing the issue: the data, the output, the template, or optimization.

When It Is Better to Split the Gallery Across Multiple Pages

As the number of images grows, one large gallery stops being convenient. Visitors have trouble finding the right project, and the page becomes heavy. The split can be based on work type, years, services, objects, or thematic collections. What matters is that the structure makes sense to a person, not just to the site administrator.

For a portfolio, a common structure works well: the homepage shows a few recent or strongest projects, a separate menu item leads into the main section, and inside that section there are categories or albums. For an event site, separate albums by day, area, or activity are often more effective. For a property catalog, split by property type or region. In that approach, BA Gallery becomes part of the site architecture rather than an isolated block of pictures.

Performance, Cache, and Template Compatibility

Any gallery sits at the intersection of several systems: the component stores data, the module displays a block, the template defines the page grid, Joomla loads styles and scripts, and cache layers and optimizers try to speed everything up. When something goes wrong, the user sees one symptom - the gallery looks wrong or does not open. But the actual cause can be anywhere in that stack.

Official Joomla documentation on web assets is useful here: styles and scripts have dependencies, and the CMS should load them in the proper order. If a third-party optimizer bundles or defers files, the lightbox, carousel, or filtering may stop working. That does not mean optimization is forbidden. It means it needs to be enabled gradually.

How to Enable Cache Safely

First, make sure the gallery works reliably without aggressive optimization. Then enable Joomla cache or an external cache layer and check the public page. If new images do not appear after enabling cache, clear the cache and verify that the page is not also being cached at the CDN level. If the large-view mode stops opening after script bundling is turned on, temporarily exclude the gallery page or the extension files from bundling if your optimization tool supports that.

You do not need to disable all site caching forever because of one gallery. It is better to identify the exact setting that breaks behavior: JavaScript bundling, deferred loading, CSS minification, moving scripts to the bottom of the page, or HTML caching for logged-in users. Change one parameter at a time and test the page after each step.

CSS Adjustments Without Editing Extension Files

Sometimes the gallery works correctly, but within a specific template it needs more outer spacing, the grid sits too tightly against the next block, or the captions look denser than the rest of the site. Without confirmed BA Gallery classes, it would be wrong to provide exact CSS for the extension's internal markup. A safer approach is to add your own wrapper around the position or article where the gallery appears and style only that wrapper.

For example, if the gallery sits inside an article or module where you can assign a custom class such as portfolio-gallery-wrap, add CSS to the template's custom stylesheet or the built-in custom styles field if the template provides one:

.portfolio-gallery-wrap {
  margin-top: 32px;
  margin-bottom: 40px;
}

.portfolio-gallery-wrap img {
  max-width: 100%;
  height: auto;
}

This snippet does not interfere with Joomla core, BA Gallery, or the template. It only adds outer spacing and safe image behavior inside your own wrapper. Check the result on the gallery page and on a mobile screen. To roll it back, remove the custom class or the CSS itself. If you need to change BA Gallery's internal elements, inspect the real markup in browser dev tools first and do not rely on random classes copied from someone else's example.

Limitations and Decisions That Are Better to Make Up Front

BA Gallery handles a typical photo gallery task well, but it should not be credited with features that official sources do not confirm. Before launch, it is worth deciding how you will update images, who owns the category structure, how often compatibility should be checked after Joomla updates, and where the extension's practical limits begin.

If the gallery is used in a commercial section, do not rely on it as the only archive of your original assets. Keep original photos separately: in cloud storage, the project's media library, or a backup system. Upload optimized web versions to the site. That way, migration, updates, or an extension switch will not mean losing the source materials.

Access Permissions and Editorial Process

Joomla ACL separates viewing access from action permissions. For BA Gallery, that creates two practical checks: who can see the gallery on the site, and who can manage it in the admin panel. If a content manager only needs to add images, do not give them unnecessary system-level permissions. If the gallery contains private materials, test access as a guest, as a registered user, and as an administrator.

For the editorial process, it helps to agree on simple rules: how categories should be named, how many images can be added to one project, which file sizes are acceptable, who checks the mobile view, and who clears the cache after publication. Those rules may seem ordinary, but they are exactly what determines whether the gallery still looks clean a few months later.

Localization and Captions

If English strings remain in the extension interface or public captions, use Joomla's built-in language override mechanisms when the string is actually translatable. Joomla documentation describes language files and Language Overrides as a safe way to change text without editing core or extension files. That is better than editing PHP files that may be overwritten during updates.

If a specific BA Gallery string cannot be found through language overrides, do not patch the extension files directly unless there is no other choice. Record the issue, check BestAddon documentation, and contact support if needed. For public gallery text, properly filled category names and image captions are often enough.

When BA Gallery Will Be a Good Choice

BA Gallery is a good fit if your Joomla site needs a visual gallery with multiple display modes, a clear category structure, a standalone page through the menu, and the ability to show a compact block through a module. The extension works especially well for portfolios, work showcases, event photo collections, and pages where visitors need to browse a series of images quickly.

Before launch, do more than just install it. Prepare the images, create a test category, choose a layout that matches the real photo proportions, publish the page through a menu item, check module positions, clear cache, and review the result on a mobile screen. If everything works reliably, you can download the latest version of BA Gallery and test the extension on your own site copy.

If the project requires a complex media system, user uploads, advanced access permissions, built-in image processing, or a large open community around the gallery, compare BA Gallery with alternatives before implementation. The right choice here is not the one with the longest feature list, but the one that solves your task without creating unnecessary overhead for the editor, the visitor, or the site.