JUX Portfolio - Joomla Extension

JUX Portfolio Setup Guide: Portfolio Items, Filters, and Output Checks in Joomla

JUX Portfolio is best understood not as just another image gallery, but as a practical Joomla module for pages where you need to display projects, completed work, case studies, illustrations, videos, or a curated set of visual materials with filtering. This guide walks through how to prepare the site, install the extension, populate portfolio items, choose a grid style, configure the popup view, place the module in the right template position, and verify the result on the public-facing site.

This guide does not repeat the product's short description. The practical logic matters more here: which settings to adjust first, why the module may not appear on the page, how to avoid a broken grid, what to check when scripts conflict, how to use filters without confusing visitors, and when a different tool would be the better choice. If you have already installed JUX Portfolio, you can start with the initial configuration section. If you are only planning to test the extension, begin with preparation and limitations.

This guide is written for Joomla site owners, webmasters, content editors, and developers who want to create a clean portfolio page quickly without building a custom component from scratch. At the same time, the extension requires careful setup: it is displayed as a module and depends on the template position, menu assignment, cache, image sizes, and the state of JavaScript on the page.

What problem this portfolio module solves

The main purpose of JUX Portfolio is to display a set of visual items as a portfolio with clear navigation. In the official documentation, the product is described as a module rather than a full component with separate records, categories, and a full administrative content model. That distinction matters: you configure the portfolio block inside a Joomla module, then publish it in a template position or alongside a specific menu item.

This approach works well when you need a controlled content block on one or several pages: an agency page with case studies, a photo selection, a design showcase, a studio project list, a video gallery, or an "our work" section on the homepage. For those use cases, the module model is simpler than a large component: fewer moving parts, faster initial setup, and easier result validation.

That said, the module format does impose limits. If the site needs a large project database with separate URLs, complex categories, search, editor permissions, routing, and SEO pages for each project, a standalone module may not be enough. In that case, JUX Portfolio works better as a compact showcase rather than the central catalog for all site content.

What visitors see on the site

According to the documentation and the JED page, JUX Portfolio offers several display modes: grid, classical, and text layout. Visitors see cards with images, titles, tags, descriptions, links, or videos. On hover, controls, icons, captions, or color effects may appear. A popup view is used for detail viewing, and tag-based filtering is used to narrow the list.

In practice, that means you are designing more than a gallery - you are shaping a short user journey: first the visitor sees the full grid, then filters the items by topic, opens a card in an enlarged view, follows a link, or starts a video. The quality of the result depends not only on the extension itself, but also on how well the images, tags, captions, and module position are prepared.

How JUX Portfolio differs from a standard gallery

A standard gallery often solves one task only: displaying images in a convenient viewer. A portfolio needs to communicate the structure of the work being shown. That is why tags, card order, captions, hover effects, links, and consistent item height matter here. If those details are filled in randomly, even a visually appealing grid template will end up looking like a pile of unrelated images.

JUX Portfolio is most useful when each card has context: a project title, work type, link to an example, video walkthrough, short description, or tag. If the page only needs to show ten photos with no filtering logic, a simpler gallery may be easier to maintain.

Who JUX Portfolio is for - and when it may be unnecessary

Before installation, it helps to define the role of this block on the site honestly. The extension has a strong use case: compact portfolios and visual showcases that an editor can build inside a module and place in the right position. It does not replace a catalog component, but it works well for visual blocks on landing pages, service pages, or a dedicated "work" page.

Good-fit scenarios

• Studio or freelancer site. You can present projects in a grid, add filters by work type, and guide visitors to a detailed page or external example.
• Local business with visual services. A photo studio, remodeling company, salon, architecture firm, or workshop can show before-and-after sets, work samples, or themed categories.
• Educational or media site. The module works well for visual collections of lessons, videos, materials, student projects, or examples.
• Joomla site homepage. If the template includes a suitable position, the module can be displayed as a standalone visual block between text sections.
• Promo page for a single service line. When you do not need a separate catalog component, the module gives you a quick way to build a showcase and manage it from the admin panel.

When not to start with this module

JUX Portfolio may be the wrong starting point if you are building a large catalog with hundreds of items, separate project pages, complex filtering, connections to Joomla articles, and different permission levels for editors. In those cases, it makes more sense to look at a gallery or catalog component that provides standalone entities and routing.

The module also does not solve image optimization on its own. It can control display size, cropping, and card style, but source files still need to be compressed, named clearly, and checked for load performance. If you upload heavy images without preparation, the portfolio may look fine while the page itself becomes noticeably slower.

Practical check before choosing: if you need one clean showcase with filters and popup viewing, JUX Portfolio is a good fit. If you need a project database with separate URLs and an editorial workflow, evaluate a gallery or catalog component first.

What to prepare before installation

Most portfolio problems do not start during installation, but before it. The extension itself may be fine, yet the result breaks because of unprepared images, the wrong module position, a template conflict, caching, or incorrect menu assignment. Preparation saves time because you decide in advance where the block will appear and what exactly will go into it.

Site and environment check

A Joomla extension is installed through the standard extension manager. Before you begin, make sure you have administrator access, the ability to upload the extension package, and a site backup. For a live site, it is safer to repeat the installation on a copy or staging environment first, especially if the template already uses its own galleries, animations, or script optimization.

• Verify that the administrative user has permission to install extensions and manage modules.
• Create a backup of files and the database using your hosting tool or Joomla backup workflow.
• Decide where the portfolio will appear: the homepage, a services page, a dedicated menu item, or a hidden test page.
• Identify a template position that is suitable for a wide visual block. A narrow sidebar is rarely a good fit for a filterable portfolio.
• Temporarily disable aggressive JavaScript optimization during the initial check if the site uses caching or script-combining extensions.

Preparing images and content data

For a portfolio, image quality is only part of the story - consistency matters just as much. If some cards are vertical, some horizontal, and others uploaded as huge originals, the grid will look messy. JUX Portfolio includes settings for maximum width, height, and cropping. But those settings do not replace basic file preparation.

Before you start filling out the module, prepare a separate folder for the images. Give the files clear names, remove duplicates, resize them to a sensible format for the web, and check thumbnail sharpness. For each item, write down the title, tag, short description, link, or video in advance if those fields are needed. It is better to start with 6 to 12 clean cards than to dump your entire archive into the module without structure.

Tag and filter plan

A portfolio filter is only useful when the tags make sense to visitors. Do not create too many near-duplicate tags. For a studio, labels like "Websites," "Branding," "Interiors," and "Video" make sense. For a remodeling business, "Kitchens," "Bathrooms," "Facades," and "Before & After" work better. For an education site, "Courses," "Projects," "Video," and "Resources" are more intuitive.

Each tag should answer the visitor's question: "What do I want to filter by?" If a tag only makes sense to the editor and says nothing to the audience, it is better not to expose it in the public filter. JUX Portfolio lets you control tag display and the general filter item, so decide in advance which groups actually help users navigate the content.

Installing the module and publishing it for the first time

JUX Portfolio is installed like a standard Joomla extension. In the admin area, open the extension installer, choose package upload, select the archive, and wait for the installation to finish. After that, find the module in the module list, open its settings, enable publication, choose a template position, and assign it to the appropriate menu item.

Do not skip the initial publication on a test page. If you place the new module directly on the homepage, troubleshooting becomes harder: it is no longer clear whether the issue comes from the portfolio settings, the template position, the menu assignment, cache, or the styles of nearby blocks.

Basic installation order

1. Open the Joomla admin panel and go to the extension installation section.
2. Select the package upload tab, usually labeled Upload Package File, and upload the extension ZIP archive.
3. After a successful installation, go to the site module list.
4. Find the JUX Portfolio module or create a new module of the appropriate type if Joomla prompts you to choose from installed modules.
5. Set the status to Published, choose a template position, and save the module.
6. On the menu assignment tab, choose a test page or the specific menu items where the block should appear.
7. Open the public-facing site in incognito mode or another browser and verify that the block appears.

Why the module may not appear right away

In Joomla, a module depends on several conditions at once. It must be published, have an accessible access level, be placed in an existing template position, and be assigned to the current menu item. If even one of those conditions is missing, the page may show nothing at all even though the installation succeeded.

Do not check only the JUX Portfolio settings. Open the module list, confirm that the position exists in the current template, then verify the Menu Assignment tab. For quick troubleshooting, it is useful to create a separate test menu item and assign the module only there. That removes the influence of the homepage, cache, and neighboring modules.

Quick takeaway: a successful installation does not guarantee a visible result. For any Joomla module, publication, position, access, and menu assignment are mandatory. Check those four items first.

Initial JUX Portfolio configuration after installation

After installation, the main working screen is the module configuration page. In the official JUX Portfolio documentation, the settings are grouped into portfolio items, display settings, popup settings, hover effects, and additional parameters. It is better not to move through them mechanically from top to bottom, but to follow the logic of the result: first the card data, then the visual layout, then the viewing behavior, and finally the technical settings.

Portfolio cards and their content

In the portfolio items section, you define the data that the grid is built from. For each item, the important fields are usually the image, title, tag, media type, link, video ID, and description. If a field is not needed for a specific project, do not fill it with placeholder text. For example, a simple photo gallery only needs an image, title, and tag. Studio case studies benefit from a project link. A video collection depends more on setting the media type and video ID correctly.

Try to keep the cards consistent in informational weight. If one card contains a long description and another only a title, the text-based view can become uneven. If some items link out to external pages while others only open in a popup, users may not understand the pattern. A visual grid works best when the rules are consistent across all cards.

How to choose tags

In JUX Portfolio, tags drive filtering, so they should be written as public-facing categories rather than internal notes. Do not use administrative labels like "old," "archive," or "review." Instead, create a category set that makes sense to the visitor. If an item belongs to two themes, check how your version of the extension and the documentation handle that case correctly, and do not rely on an unverified format.

Links and video

If a card should lead to a separate page, enter the link carefully and test it after publication. If you are using video, the documentation mentions support for YouTube and Vimeo. There is no need to paste arbitrary page code for a video. In most cases, the extension expects an identifier or link that it can render inside the popup. If the video does not open, check not only the card settings, but also the popup settings and any script blocking on the page.

How many cards to keep in one module

The module format works best for a compact showcase, so avoid turning a single JUX Portfolio instance into a giant archive of everything you have ever produced. For an initial launch, it is better to start with a limited set of your strongest materials: for example, 9 to 18 cards for a studio page or 6 to 12 cards for a homepage block. That volume is easier to review, faster to load, and simpler for editors to maintain.

If you have more work to display, split it by purpose. One module can show featured case studies on the homepage, another can power a dedicated service page selection, and a third can display videos or learning materials. That works better than an endless list in a single module: each page keeps its own context, and users are not forced to filter through irrelevant items.

If the module contains many cards, decide in advance what will happen to outdated work. A portfolio loses value quickly when it keeps stale images, broken links, and tags that no longer match the services you offer. An editorial maintenance routine matters more here than a polished hover effect: assign someone to review links, refresh images, and remove weak items on a regular schedule.

Display settings

The display section determines how the portfolio actually looks on the page. The key settings here include the layout type, site style, number of items, spacing, maximum dimensions, crop mode, filter position, the general filter label, and whether to show the title, tag, description, and supporting elements. Do not enable everything at once. First get to a clean grid, then add captions and effects.

After every meaningful change, save the module and refresh the page without cache. If filters and effects are enabled, test not only the first screen but also behavior after clicking, hovering, and opening the popup. Proper JUX Portfolio setup is not about one isolated setting - it is the combination of card data, layout, image sizes, filtering, and viewing behavior.

Layouts, filters, and lightbox: how to build a clear showcase

The distinct value of JUX Portfolio becomes clear in the combination of layout, filtering, and popup viewing. The documentation lists grid, classical, and text layout options. These are not just visual styles. Each one fits different tasks and different levels of information density.

When to choose a grid

A grid works best when the image is the main thing that matters. It is a strong fit for photography, design work, studio portfolios, visual case studies, or product collections without long descriptions. In a grid, consistent thumbnail proportions and clean tags are especially important. If the images vary in size, enable cropping or prepare the files in matching aspect ratios ahead of time.

Do not overload a grid card with long text. A title and short tag are often enough. Details are better shown in the popup view or on a separate page if the card links out.

When the classical view is useful

The classical view works better for projects where the caption matters almost as much as the image. For example, an agency case study may need a project title, category, and short description. This approach helps the visitor understand the context without opening every card. The tradeoff is obvious: the text takes up space, and the grid becomes less compact.

The text layout for collections and links

The text layout is worth considering when the visual part is secondary or when the portfolio behaves more like a curated content list. For example, you might use it to display a series of videos, student work, or links to projects. The key is not to treat it as a replacement for a full catalog. If every item needs its own long text, metadata, and URL, Joomla articles or a catalog component may be the better fit.

Filtering as navigation, not decoration

A filter should shorten the path to the right item. If the page only contains six cards, a filter may do more harm than good by complicating the interface. If there are many cards and they clearly fall into groups, filtering helps. In the settings, check the label for the general filter item, such as All, the filter position, and the behavior after a click. For a localized site, you can use clear text in visible labels if the setting allows it. If a string cannot be translated through the settings, use Joomla's built-in language overrides only after verifying the constant, rather than editing the extension files.

Lightbox and popup viewing

A popup is useful when visitors need to examine an image, start a video, or view extra information without leaving the page. Check that the popup opens correctly with keyboard and mouse, closes properly, does not appear underneath the site header, and does not conflict with other galleries. On sites that use multiple extensions with their own viewer libraries, popup conflicts are one of the first things worth testing.

Placing the module in Joomla: positions, menus, and access

JUX Portfolio is rendered as a module, which means half of the setup has nothing to do with the extension itself and everything to do with Joomla mechanics. Even a perfectly configured portfolio will not appear on the site if the module is in the wrong position or not assigned to the right menu item. For editors, this is often the least intuitive part: the module settings look complete, but the public page stays empty.

Template position

The position determines where the module appears inside the template. A portfolio usually needs a wide area: above the content, below the content, inside a dedicated homepage block, or in a position created specifically for visual sections. Do not choose a sidebar position if the portfolio needs to show three or four card columns. A narrow container will almost always damage the layout.

If you do not know the template position names, check the template documentation or enable the standard Joomla position preview if it is available in your setup. Another option is to temporarily publish a simple HTML module in the expected position and confirm that it appears where you need it.

Menu assignment

The Menu Assignment tab controls which pages display the module. For testing, choose a single menu item. After verification, you can expand the assignment to other pages. If the portfolio is only needed on the homepage, do not publish it on every page: that adds unnecessary page weight, may annoy visitors, and makes conflict diagnosis harder.

If the site has many pages, it helps to keep a simple assignment map: where each module instance is used, which tags are active in it, which template position is selected, and who is responsible for updating the cards. That becomes especially important for agencies and editorial teams where one administrator creates the module and someone else later has to figure out why the portfolio appeared on the wrong page.

Do not use the "show on all pages" mode as a shortcut. For a visual module, that is rarely justified. A portfolio with images and scripts should support the meaning of a specific page. If the same block appears on the blog, contact page, privacy policy, and service pages, it turns into noise and makes optimization harder.

Access level

The access setting determines who can see the module. For a public portfolio, the Public level is usually correct. If you are testing the block for administrators only, you can temporarily choose restricted access, but then make sure to check the page in a browser where you are not logged in. Otherwise, it is easy to mistake "the module works for the administrator" for a real public launch.

Cache and module order

Joomla and the template may cache module output. During setup, it is usually best to clear cache after changes or temporarily disable caching for this specific module if that setting is available. Also check the module order within the position. If the same position already contains a slider, form, or large HTML block, the portfolio may appear lower on the page than expected.

Fast troubleshooting rule: if JUX Portfolio is not visible on the page, first check publication, position, menu assignment, and access. Only then move on to JavaScript, the template, and the portfolio settings themselves.

Practical scenario: a portfolio page for a small studio

Below is a concrete scenario you can reproduce on a test page. Imagine a studio with 12 pieces of work: websites, brand identity, illustrations, and video. The goal is to build a "Portfolio" page where visitors can filter the work by type, open an image in an enlarged view, and follow through to a detailed project page when one exists.

Goal

Create a clean portfolio module in a wide template position, with category filters, consistent thumbnails, clear titles, and popup viewing. In this scenario, JUX Portfolio does not replace all site content. It serves as a showcase that directs visitors to the best work.

Preparation

Create a test menu item called "Portfolio" or a hidden page if you do not want visitors to see the block right away. Prepare images with consistent quality. For each project, define the title, tag, short description, and link to the project page. Decide in advance which tags will be public: "Websites," "Branding," "Illustrations," and "Video."

Setup steps

1. Open the JUX Portfolio module and give it a clear administrative title so you can distinguish it from other modules.
2. Add the first portfolio item: image, project title, tag, and description. If there is a separate project page, add the link.
3. Repeat the process for the remaining items, keeping the data structure consistent.
4. Select the grid display type, enable the filter, and define the general filter item if the audience needs it.
5. Set the maximum thumbnail dimensions and crop mode so the grid looks even.
6. Enable the title and tag display, and keep long descriptions for the popup or separate project page.
7. Configure popup viewing and make sure images open without sending the user to an empty page.
8. Publish the module in a wide template position and assign it only to the test menu item.
9. Clear cache, open the page in a new window, and check the filters, popup, links, and responsive behavior.

Expected result

A clean grid of work appears on the page. The filters show clear categories, the card heights stay consistent, images open in an enlarged view, and links go where users expect them to go. On mobile, the cards reflow without horizontal scrolling.

A common issue that gets in the way

If the filter works after saving but the grid looks uneven, the filter is often not the problem. Check the source image proportions, crop mode, maximum height, spacing, and the width of the template position. If the module sits inside a container with limited width, even correct JUX Portfolio settings will not produce a broad showcase.

Practical use ideas for different Joomla sites

JUX Portfolio does not have to be limited to an "Our Work" page. The module works well for many kinds of visual blocks as long as each card has a clear purpose and does not turn into a random image. Below are several scenarios that show how filters, links, video, and different layouts can be used effectively without inventing features beyond the documentation.

Case study block on a service page

On a specific service page, you can display only the relevant projects. For example, on a "Web Design" page, show work tagged "Corporate Websites," "Catalogs," and "Landing Pages." In that setup, the filter may be very short or not needed at all, while the project title and link to a full description become more important.

The check is simple: the visitor should understand that this is not a general gallery, but proof of experience for a specific service. If the cards are too mixed, it is better to create a separate module for that page than to reuse one shared set across all sections.

Video collection or media library

If the cards use YouTube or Vimeo videos, the module can become a visual video collection. This works well for lessons, reviews, events, or work demonstrations. In this scenario, do not overload the card with description text: a clear title, topic tag, and reliable video popup behavior matter more.

A before-and-after showcase

For remodeling, design, medical, or cosmetic sites, a portfolio is often built around visible results. JUX Portfolio can be used as a before-and-after showcase, but this use case depends heavily on consistent image proportions and honest captions. Do not mix results, process shots, and promo banners in the same grid. The user should be able to compare the work quickly and open the right card without friction.

Student projects and curated resource sets

On an education site, the module can display student projects, assignment examples, lesson collections, or visual study materials. Tags help separate topics, and links point to the underlying content. If each item requires a lot of text, the text or classical layout may be a better choice so visitors do not have to guess the meaning from a single image.

How to verify the result after setup

Once the portfolio is published, it needs to be tested as a user interface, not just as an administrative configuration. Everything may look saved correctly in the admin panel, while the live site introduces a different set of conditions: the template, responsive behavior, cache, load speed, script conflicts, access permissions, third-party extensions, and browser restrictions.

Testing on the public-facing site

Open the page in a browser where you are not logged in. Confirm that the block appears on the correct page and does not appear where it should not. Click every filter. Open several cards in the popup. Follow the links. If there is video, play it and close the popup. Then reduce the browser width or open the page on a mobile device.

• Filters should show the expected cards, not an empty area.
• Thumbnails should not stretch, squash, or overlap the captions.
• The popup should close without reloading the page.
• Card links should lead to the correct pages or external resources.
• The module should not appear on pages where it was not assigned.
• There should be no horizontal scrolling on mobile because of the grid.

Content review before launch

A technically functioning module still does not guarantee a useful portfolio. Before opening the page to visitors, read through the cards as a normal user would. The title should explain what the work is. The tag should help with filtering. The description should add context rather than repeating the title. The link should lead to a page where the user actually gets the next part of the story.

It helps to review the cards in three modes. First, the overall view without filtering, where you evaluate visual rhythm and the strength of the first items. Second, the view for each tag, where you can see whether any groups are empty or too weak. Third, the view of individual cards through the popup or link. If users encounter duplicates, blurry images, or interchangeable captions at any stage, fix that before launch.

For commercial sites, add one more check: does the portfolio reflect the services the business currently provides? Sometimes old case studies remain on the page even though they no longer match the company's focus. Visually they may still look good, but they lead the audience in the wrong direction. A portfolio should support the client's current decision-making, not simply preserve an archive of past work.

Verification after a template change or update

The portfolio should be retested after a template update, a change in the caching extension, new optimization settings, or major Joomla updates. Even if JUX Portfolio itself did not change, the environment around it may have. Pay especially close attention to the popup, filters, card heights, and the mobile grid.

Create a short checklist for the site administrator: open the page, click every filter, open a card, test one link, play one video, check the mobile width, and clear cache after saving changes. That takes only a few minutes, but it catches most visible problems before visitors do.

Page weight and load speed check

A portfolio almost always adds images, which means it affects page weight. The extension can control display behavior, but it cannot magically make source files lightweight. Check image sizes before upload, use compression, and avoid showing too many cards in the first screen. If the settings include an offset or item limit, use those features intentionally: show the strongest work first rather than the entire archive.

SEO and accessibility without overpromising

Do not expect the module to improve rankings automatically. Search value depends on the page content, speed, accessibility, text context, and link structure. For a portfolio, it matters that the surrounding page contains useful text, the images have meaningful names, and the links lead to worthwhile destinations. If the cards only open inside a popup, do not treat them as a substitute for full project pages.

For accessibility, check whether the page still makes sense without interacting with every effect. Hover captions may work well on desktop, but touch devices behave differently. If important information only appears on hover, repeat it in a visible caption or in nearby text. That is not only better for users, but also reduces the risk that the key meaning of the portfolio is hidden behind a decorative effect.

If the cards link to separate project pages, review the anchor text and surrounding context. A generic link like "Learn more" is acceptable, but the project name or description should be nearby so the user understands where the link goes. For external links, make sure they do not send visitors to an outdated domain or a closed staging address.

Result check: if a visitor can pick a tag, open a project, understand the caption, and continue without visual breakage, the basic configuration is correct. If you have to explain where to click, the interface should be simplified.

Template compatibility, cache, and safe enhancements

JUX Portfolio runs inside a specific site environment, so compatibility depends on the template, installed extensions, and optimization settings. Older JoomlaUX support discussions mention issues related to JavaScript, noConflict mode, mobile responsiveness, and saving large module datasets. Those sources should not be read as a list of current defects, but they are useful for understanding likely troubleshooting directions.

Script conflicts

If the filter, hover effects, or popup do not respond, check the browser console. The problem often appears there as a JavaScript error. For testing, temporarily disable script merging and deferred loading in the optimization extension, clear cache, and test the page again. If the portfolio works after that, configure exclusions for the gallery scripts or use a gentler optimization profile for that page.

Do not edit the extension files directly. That kind of fix disappears after updates and may break the site later. It is safer to rely on cache settings, module loading order, optimization exclusions, or developer assistance if the issue reproduces even with a clean template.

Template and container width

If the cards overflow the page boundaries, the cause may be the template position. A multi-column portfolio needs a wide container. Check whether the module has been placed inside a sidebar, tab, accordion, or any block with hidden width. Some templates recalculate the grid only after visible content loads, so a portfolio placed inside a hidden tab may end up with incorrect dimensions.

Localization and language strings

If some public-facing labels appear in English, check the module settings first. If the needed word cannot be set there, use Joomla's built-in language override system. Do not edit the extension language files directly unless you have confirmed that an override is impossible. File edits inside the extension folder can be lost after an update.

Custom CSS without risking updates

The JUX Portfolio documentation mentions a custom CSS field. That is safer than editing the extension files directly, but it still requires care. Use it for small visual adjustments: spacing, caption color, card size, or hover state. Before adding CSS, open the browser developer tools and inspect the actual classes used by your version of the module and template.

If the exact selectors are not confirmed on your site, do not copy someone else's CSS blindly. First assign the module a unique class suffix through the Joomla parameters, then scope the change to that container. This keeps the adjustment limited to one portfolio block and avoids affecting other modules.

/* Example of the general approach, not a universal selector for every site.
   First assign the module its own class suffix and verify the actual classes in the browser inspector. */
.portfolio-projects img {
  border-radius: 6px;
}

.portfolio-projects a:focus {
  outline: 2px solid #2b7cff;
  outline-offset: 3px;
}

Verification after this kind of change is straightforward: open the portfolio page, make sure only the intended module changed, confirm that the filters and popup still work, and check that keyboard focus remains visible. To roll back, remove the CSS from the field or from the template file where you placed it.

How to avoid breaking maintainability during tweaks

Every change should be reversible. Record where you changed CSS, which class suffix you used, and which module instance it applies to. If another administrator notices an odd spacing or color issue months later, they should be able to find the source without searching through the entire template.

Do not mix rules for different modules and different pages inside one custom CSS field. If the homepage portfolio and the services-page portfolio need different styling, give them different class suffixes and separate short rules. This takes a little longer during setup, but it makes rollback easier and reduces the risk of accidentally changing every gallery on the site.

If you need a major markup change, do not try to force it through dozens of CSS exceptions. Check first whether the required mode already exists in JUX Portfolio or the template. If not, evaluate an alternative extension or a careful template-level customization. CSS should polish the result, not replace the extension's architecture.

Why the portfolio may not work as expected - and how to diagnose it

Troubleshooting is best approached from simple to complex. First rule out Joomla settings, then the card data, then the template, cache, and scripts. Do not start by reinstalling the extension: more often than not, the issue is in module publication, position, menu assignment, or a conflict on a specific page.

The module does not appear on the page

Symptom: installation completed successfully, the module is saved, but no portfolio appears on the public page.

Possible causes: the module is unpublished, a nonexistent position was selected, the menu assignment is incorrect, the access level is restricted, cache is enabled, or you are checking the wrong menu item.

What to check: the Published status, the template position, the Menu Assignment tab, the Access level, cache clearing, and the page view while logged out.

How to fix it: assign the module to a single test menu item, choose a confirmed wide position, set public access, and clear the cache. If the module appears, expand the configuration to the needed pages step by step.

The grid looks uneven or the images crop badly

Symptom: cards have different heights, images look stretched, captions overlap, or the block feels chaotic.

Possible causes: different source image proportions, an unsuitable crop mode, descriptions that are too long, a narrow template position, excessive spacing, or a CSS conflict.

What to check: source image dimensions, maximum width and height settings, crop/resize mode, the amount of text shown on each card, and the container width.

How to fix it: prepare images with similar aspect ratios, limit description length, use consistent thumbnail dimensions, and move the module to a wide position. If you add CSS, scope it with the module class suffix.

The filter returns an empty result

Symptom: when you click a tag, the cards disappear or only an empty area remains.

Possible causes: tags are filled in inconsistently, extra spaces are present, the same tag is spelled in multiple ways, the filter includes an item with no matching cards, or the filter script conflicts with optimization settings.

What to check: consistent tag spelling, whether each filter has matching cards, filter behavior after clearing cache, and whether disabling JavaScript merging during testing changes the result.

How to fix it: standardize the tag set, remove unnecessary groups, clear cache, and test on a clean page. If the filter works when script optimization is disabled, configure an exclusion in the caching extension.

The popup or video does not open

Symptom: nothing happens on click, an empty window appears, or the video does not start.

Possible causes: the media type is wrong, the video ID is entered incorrectly, popup viewing is disabled, another lightbox library on the page is conflicting, or the browser is blocking embedded content.

What to check: popup settings, the media type on the card, the video link or identifier, the browser console, and whether other galleries are present on the page.

How to fix it: test one image card and one video card separately first. If a single card works, add the rest back gradually. If even one item fails, look for the issue in the popup configuration or a script conflict.

Some data disappears after saving

Symptom: you added many items and saved the module, but some entries were not preserved or the form behaves unpredictably.

Possible causes: too much data in the module settings, server-side limits, a save timeout, or an admin form conflict. Older support discussions mention similar symptoms when many items were involved.

What to check: whether the problem repeats with a small number of items, whether the module saves properly on a test site, whether server logs show errors, and whether the module configuration has become unreasonably large.

How to fix it: split the portfolio into multiple modules by page or category, reduce the number of cards in one block, and review server limits with the hosting administrator. If the issue is consistently reproducible, contact the developer with exact reproduction steps.

Horizontal scrolling appears on mobile

Symptom: the page extends beyond the screen, the cards do not reflow, or the filter spills out of the container.

Possible causes: the minimum card width is too large, the template CSS uses fixed dimensions, filter captions are too long, the position is unsuitable, or the responsive grid is conflicting with surrounding styles.

What to check: container width, tag name length, card size settings, custom CSS, and neighboring modules.

How to fix it: shorten filter labels, reduce spacing, review the template's mobile behavior, and temporarily disable your custom CSS. If the problem disappears without those tweaks, add them back one at a time.

When JUX Portfolio is the right choice

JUX Portfolio is a strong option when you need a manageable Joomla module for a visual showcase: a work portfolio, project selection, video gallery, before-and-after block, or compact media collection with filters. It is especially convenient when the result needs to live in a specific template position and does not require a separate catalog architecture.

Before publishing, run one final short check: the module is published, the position exists, the menu assignment is correct, the cards are filled out consistently, the images are prepared, the filters make sense, the popup opens, cache is not breaking the scripts, and the mobile version does not create horizontal scrolling. If those items are covered, you can move on to real-world testing on your site.

If this guide makes it clear where the block will go, which items belong in it, and how you will verify the result, the next step is simple - download the JUX Portfolio archive and test the module on a site copy or a separate test page.

Do not try to solve every visual content task with one module. Use it where simple publishing, a clear grid, tags, popup viewing, and quick result control matter most. For a large media catalog, choose a component; for ordinary photo insertion, use a lightweight gallery; and for a filterable work page, JUX Portfolio may be exactly the tool that keeps the site simple instead of making it more complex than necessary.