YOOtheme Max - Joomla Template

Guide to Configuring and Using YOOtheme Max for Joomla

YOOtheme Max is not a small standalone template that you can just activate and forget about. In practice, it is a demo package and a set of ready-made solutions built on top of YOOtheme Pro: page layouts, styling, images, menus, modules, and portfolio logic all need to be tied carefully to real Joomla content. This guide explains how to treat Max as a working site foundation rather than a polished gallery screenshot.

This material is intended for a site owner, webmaster, or editor who already understands the basics of the Joomla admin panel and wants to build a manageable portfolio site, designer profile, studio page, or small content-driven project. Below you will find pre-installation prep, an initial validation checklist, YOOtheme Pro setup, work with layouts, modules, and menus, a practical example, problem diagnosis, and a comparison with similar solutions.

The core idea is simple: Max only really shines when you do not copy the demo wholesale, but keep its visual logic - bold color sections, portfolio blocks, clear navigation, and concise case studies - while replacing the demo content with your own structure. Set up the foundation and your validation process first, then move on to decorative details.

What Max Actually Gives You and Why You Need to Understand That Before Setup

The official YOOtheme page describes Max as a package for creative websites, personal pages, and portfolios. What matters inside is not just the color palette or the first hero section. You get ready-made page layouts, style variations, a curated image set, and a demo site you can study as a build example. That changes the approach: you are not starting from an empty template, but deciding which parts of the demo to keep, which to replace, and which pages to rebuild from scratch in the builder.

With YOOtheme Max, it helps to think in three layers. The first layer is visual identity: a bold top section, large typography, portrait imagery, alternating dark and light blocks, and large project previews. The second layer is structure: homepage, portfolio, service pages, blog section, individual case studies, and utility pages. The third layer is YOOtheme Pro mechanics: style settings, builder elements, module positions, template styles, menu assignments, and responsive validation.

If you treat Max as "install the template and the site is done," the result often looks worse than the demo. Demo pages use carefully selected images, short headings, and a clean grid. Once you swap in real copy and photography, the block rhythm can break, the contrast can disappear, the navigation can feel cramped, or the sections can become unnecessarily tall. That is why the rest of the setup should revolve around control: what you change, where it appears, how quickly you can verify it, and how to roll back a questionable step.

Confirmed capabilities you can rely on

According to the official Max page, it belongs to the YOOtheme Pro package lineup for Joomla, includes a set of ready-made page layouts, several style variations, and a demo site available as a full Joomla installation with YOOtheme Pro and demo content. YOOtheme Pro documentation confirms that the builder itself works through a customizer with a settings panel on the left and live preview on the right, while the page builder assembles pages from sections, rows, columns, and elements.

For the user, that means most of the work after installation happens not in template files, but in the Joomla and YOOtheme Pro stack: articles and menus remain part of the CMS, while the site appearance, sections, modules, footer, style, and individual pages are controlled through the builder and settings panels. You should only touch template files when you clearly understand why you need an override or a child theme.

Where Max works best

Max naturally fits sites where visual presentation matters: a designer portfolio, studio site, photographer page, small agency website, illustrator profile, art director portfolio, or a team that sells services through case studies. Its strength is not a catalog with hundreds of cards, but short persuasive pages: who you are, what you do, what work you have done, how to get in touch, and which services can be ordered.

If the site primarily needs to function as a knowledge base, large store, forum, complex client portal, or permissions-heavy platform, Max may only work as the visual shell. In that case, decide up front which functions Joomla or third-party components will handle, and which parts will remain inside the visual builder. Otherwise, it is easy to end up with a beautiful homepage and an awkward day-to-day admin experience.

Who this template may not be right for

Max may be excessive for a site that needs a strict corporate look without bold hero blocks, for a project with a large volume of uniform content, or for a team that is not prepared to maintain a visual builder. It is also not the best choice if editors need to create articles in bulk using the same structure, while every builder screen then requires manual validation.

That is not a flaw in the product itself. YOOtheme Max is simply geared toward expressive pages where visual composition matters almost as much as the text. If your project runs on frequent publishing, filters, complex catalogs, and automated listings, think ahead about where to use standard Joomla articles, where to use output templates, and where builder-based pages make sense.

What to Check Before Installing It on a Joomla Site

Preparation is not just a formality. Max is tied to YOOtheme Pro, demo content, media assets, styles, and access permissions. A mistake at this stage often looks like "the template does not match the demo," when the real issue is that the wrong archive was installed, the server does not have enough resources, permissions do not allow CSS to be written, or the editor is working without the required access level.

Start by choosing the right scenario. If you are building a new site and want a structure that stays as close to the demo as possible, use the demo package as a separate Joomla installation. If the site already exists, install the YOOtheme Pro theme package and load the required layout elements inside YOOtheme Pro rather than trying to upload the full demo package over a live CMS.

New site or existing site

For a new project, the demo package is convenient because it immediately shows how the menus, pages, images, and styles are put together. It is excellent training material: after installation, you can open the builder, go through the sections, and see which elements control the hero area, portfolio, services, footer, and individual pages. But the demo package is a full Joomla installation, so it should not be treated like a regular ZIP template for an already live site.

For an existing site, it is safer to create a copy or staging environment, install the template there, assign it to a test menu item, and validate one page first. That way, you do not change the appearance of the entire project at once. In Joomla, it is especially important to remember template style assignment and module assignment: the same template can look different on different menu items, and a module can be published but still fail to appear on the page where you expect it.

Server, permissions, and access

YOOtheme Pro documentation lists the basic server requirements and separately describes installation issues caused by limited PHP resources. In practice, before installing Max, you should check the archive size, `upload_max_filesize` and `post_max_size` limits, script execution time, PHP memory, and GD availability, because YOOtheme Pro works with images and generates derivative files.

The second validation block is file permissions. If the template is installed but settings do not save, CSS does not load, or the site appears unstyled, the reason may be that the web server cannot write the required files into the template or cache directories. YOOtheme documentation recommends standard permission values for directories and files; the exact setup is best confirmed with your hosting provider so you do not grant more access than necessary.

Safe order: create a backup and a test page first, then install the template, open YOOtheme Pro, save one setting, and check whether the CSS appears on the public-facing site.

What source materials to prepare in advance

Max is demanding when it comes to content. It uses large sections and large images, so random low-resolution pictures instantly make the site look unfinished. Before installation, gather your logo, 5 to 8 strong project images, a short description of the author or studio, a service list, 2 to 3 case studies, contact copy, and a menu structure. This speeds up setup because you will be replacing specific blocks instead of trying to invent content inside the builder as you go.

For a portfolio site, it also helps to agree on a case study format in advance. For example: project name, client or project type, scope of work, short description, 2 to 4 images, outcome, and link. That keeps Max pages from falling into mismatched styles, where one case study is oversized, another is empty, and a third is overloaded with photos and no explanation.

Installation and Initial Validation Without Risking the Live Site

How you install Max depends on which archive you have. A standard template package is installed into an existing Joomla site through the regular extension installer. A demo package is installed as a separate Joomla instance and used for a new site or a training environment. The distinction matters: the first option adds a template to your CMS, while the second deploys a ready-made site with demo data.

If you are not sure which archive you have, do not install it on your live site. First extract it locally just to inspect the structure, or check the vendor documentation. Demo packages usually contain a full CMS file set and a separate installation procedure, while a template package is a template archive that Joomla accepts through the installer.

Step-by-step installation on an existing site

For an existing site, the logic is straightforward: upload the ZIP through the Joomla installer, open the list of site templates, find the YOOtheme template style, assign it to a test menu item, and only make it the default after validation. You should not immediately switch the default template style for all pages if the site already contains content, modules, and custom extensions.

1. Create a backup of the site and database.
2. Open the Joomla admin panel and go to extension installation.
3. Upload the template archive, if it is specifically a package for an existing site.
4. Open the list of template styles and assign the YOOtheme style to a separate test menu item.
5. Open the test page on the public-facing site and confirm that the styles, header, and basic layout have loaded.
6. Open YOOtheme Pro through the YOOtheme menu item in the admin panel and make sure live preview works.

The short conclusion of this stage is simple: you do not need to see a perfect Max yet. You need to see a working connection between Joomla, the template style, the builder, and the front-end page. If that works, you can move on to design setup. If it does not, do not carry the problem into the content layer. Resolve installation, permissions, cache, and extension conflicts first.

How to validate the demo package

If you are working with the demo package, create a separate database and a separate site folder. After installation, open the homepage, portfolio pages, services, and blog. Then go into the builder and study how the sections are assembled. This type of environment is useful even if the final site will be installed differently: it shows the real page names, menu structure, block types, and the visual rhythm of Max.

Do not transfer the demo content to a live site wholesale without review. Demo copy and images are there to help you understand the structure, but they should not become the final content. A better approach is to note which sections you actually need and carry over only the logic: hero, 2 to 3 featured projects, services block, contact, footer, and case study page.

Initial validation after activation

After installation, open the site in a regular browser and in incognito mode. Make sure a logged-in user is not seeing elements hidden from guests, and vice versa. Then clear Joomla cache and YOOtheme Pro cache if you have already changed styles or images. If the page still shows the old logo or an old image with the same filename, the issue may not be the template at all, but cached image files.

Check three pages: the homepage, a page without a builder layout, and an individual article or blog page. This helps you understand where the YOOtheme layout is active, where Joomla is rendering a standard component, and where the template style or module position is being applied differently from what you expected.

Detailed Post-Install Setup: From Logo to Style

After the initial validation, do not start with small CSS tweaks. Set up the base system first: logo, header, navigation, style, fonts, images, footer, cache, and editor permissions. If this layer is not in place, any visually polished Max block can behave unpredictably on other pages.

In YOOtheme Pro, most of the work happens through the customizer. The documentation describes it as an interface with a settings panel on the left and a preview on the right. It is important to keep the distinction between theme settings and page layout clear: saving a page layout does not always mean saving global theme settings, and vice versa. So after changing a style, header, or site settings, save the change in the exact place where you edited that parameter.

Logo, layout, and transparent header

Start with the Layout panel and the Site & Logo block. For Max, the header contrast against the first section matters a lot: in the demo, the header feels like part of the hero area rather than a separate heavy panel. If you use a transparent header over a bright or dark image, prepare both a regular and an inverse logo. YOOtheme Pro documentation specifically covers the inverse logo for cases where the header sits on top of a dark background.

Check the logo width, mobile logo, and the version used for the dialog/mobile header. A common mistake is uploading a complex horizontal logo that looks great on desktop but becomes unreadable in the mobile header. With Max, it is better to have a simplified mark or a short text logo than to force a long wordmark into a narrow navigation area.

Header, menu, and the first navigation items

The Max demo uses a short menu: Home, Work, Branding, About, Services, Blog. That is not accidental. In a visual portfolio, the main menu should stay compact because the large hero section already commands attention. If you add too many items, the header starts competing with the first screen and the mobile menu becomes overloaded.

Build the menu around roles: homepage, work, services, about, blog or notes, and contact. If you need a separate catalog, documentation area, or client materials section, it is usually better to move it into a secondary menu, footer, or dialog/offcanvas rather than break the top navigation. For more complex items, YOOtheme Pro supports menu item settings and mega menu configuration through the page builder, but for Max that only makes sense if you truly have service groups or a large portfolio.

Style Customizer and color variations

The official Max page mentions several style variations. Start with the one that is closest to the demo, then change global colors, typography, and components through the Style Customizer. Do not try to replace the entire palette with a CSS snippet: YOOtheme Pro is built on UIkit and Less variables, so adjusting global style parameters usually produces a more stable result than a set of isolated tweaks.

With Max, it is especially important to check text contrast on colored sections. If the hero or portfolio block uses a bold background, the text still needs to remain readable. The documentation on style variables explains that YOOtheme Pro compiles variable changes into CSS, while UIkit components such as cards and buttons inherit the overall style. That means one well-chosen global palette adjustment often improves several blocks at once.

Images, crops, and performance

Max depends on strong imagery. In YOOtheme Pro, media fields support sizing, crops, focal point, responsive images, and cached derivative files. If you replace a portrait in the hero area or update project previews, do not upload a random oversized file without controlling dimensions. Choose the right aspect ratio for the block, set the focus point, and make sure the face, object, or cover is not cropped badly on tablet and mobile.

If the site keeps showing the old image after a replacement, check both cache and filename. YOOtheme Pro includes settings related to cache and images; Joomla can also cache the page or modules. After changing key images, always validate the result in a private window and clear cache deliberately so you do not hide the real cause of the issue.

Settings you should not enable without a reason

Do not turn on every effect, script, and external service just because the option exists in the panel. For Max, fast navigation, clear sections, well-prepared images, and restrained animation are enough. Complex parallax effects, external maps, analytics scripts, and heavy embeds should only appear where they actually help the user.

If you use a consent manager, check how YouTube, maps, and third-party scripts behave before the user gives consent. YOOtheme Pro documentation describes placeholders for embedded content when consent has not been granted. This is especially important on service pages and case studies: a block should not look broken just because an external service is still blocked.

Max Page Layouts: How to Keep the Demo Logic While Replacing the Content

Max layouts are valuable because they already show which pages a portfolio site needs. The official page lists ready-made layouts and style variations, and the demo includes Home, Work, Branding, About, Services, and Blog. Instead of creating everything from scratch, use these pages as a map: what the page is supposed to achieve, what the first screen should do, which blocks lead toward contact, and where proof of expertise should appear.

But do not copy every block indiscriminately. Max has a strong rhythm: large intro, then portfolio or text block, then services, clients, and a contact prompt. If your content is shorter, it is better to remove extra sections than to stretch them with filler. If you have more content, add separate case study pages rather than overloading the homepage.

The homepage as a storefront, not your full biography

The Max homepage should answer three questions: who you are, what kind of work you show, and what the visitor should do next. For that, a hero block, 2 to 3 strong projects, a short services block, a list of clients or focus areas, and a clear contact path are enough. If you try to fit every case study, all your experience, and a long personal story onto the homepage, the site loses its pace.

In the builder, it is best to work from top to bottom. First replace the hero text and main image. Then choose 2 to 3 projects that work as proof rather than a random gallery. After that, set up the services block and call to action. Only once that sequence is solid should you move on to colors, spacing, and effects.

Work and Branding as different portfolio entry points

In Max, a work page and a thematic page like Branding can serve different purposes. Work is a good fit for a general project grid, while Branding works better as a destination for visitors who specifically want to see identity work, covers, print materials, or a broader visual system. On a real site, that is useful because you can build a general work archive and separate landing pages for individual services.

The biggest mistake is sending every link to the same page with the same set of cards. If a menu item promises Branding, show branding examples, explain the process, and include case studies related to that theme. If the menu item leads to Work, offer a filterable or clearly structured gallery where visitors can quickly understand the breadth of your experience.

Case Study as a trust-building format

A case study page in Max is not just there for a beautiful image. It should explain the task, the author's role, the process stages, the outcome, and the visual materials. Even if the official demo uses short placeholder-style copy, on a real site it is better to add more substance: what the problem was, what you did, why that style was chosen, which deliverables were included, and how the client uses the final result.

A strong case study does not need to be long. Four to six meaningful blocks are enough: task, context, solution, imagery, outcome, and next step. In the builder, that is easy to assemble with sections, while recurring details can be moved into Joomla components, article fields, or pre-saved layout blocks if you plan to publish many similar case studies.

Blog and posts without losing the visual style

If you use a blog, do not merge it with the portfolio. YOOtheme Pro includes blog and post settings that let you control images, width, navigation, excerpts, and metadata. This matters in Max because a standard Joomla article can look too plain next to a bold homepage. Configure both the overview and the single post layout so that the images, headings, and text width feel related to the rest of the site.

Do not turn the blog into a warehouse for news updates. It is more effective to publish material that reinforces the portfolio: a process breakdown, a note about a project challenge, an explanation of your approach, or a curated set of solutions. That way, Blog becomes not just an obligatory section, but a way to demonstrate professional thinking.

Modules, Positions, and Menus: The Joomla Layer You Cannot Ignore

YOOtheme Max looks like a visual builder, but it runs inside Joomla. That means modules, positions, and menu assignment remain critical. YOOtheme Pro documentation describes the integration of Joomla Module Manager into YOOtheme Pro: modules can be added, edited, and viewed by position, and some positions collapse automatically when they have no output.

That is convenient, but it requires discipline. If a module is published on the wrong page, if a position is not used by the builder layout, or if the template style is assigned to only part of the menu, the front-end result will differ from what you expected. In Max, where the header, footer, portfolio, and call to action are visually tied together, those mistakes are immediately noticeable.

Which positions to check first

Start with the header positions: `logo`, `navbar`, `header`, `dialog`, as well as their mobile counterparts. Then check `top`, `bottom`, `sidebar`, and builder positions. YOOtheme Pro documentation describes `builder-1` through `builder-6` as positions that are rendered through a Position element inside the page builder, not on their own. If you publish a module in one of those positions but do not add a Position element to the layout, the module may not appear where you expect it.

For Max, you will most often need menus, contact details, social links, a short CTA, and footer blocks. Do not publish every module on every page. Use menu assignment and validate each key page: homepage, portfolio, service, case study, blog, and contact.

Menus and template style assignment

YOOtheme Pro allows you to create multiple template styles and assign them to different menu items. That is useful if the Max homepage needs to be bold and full-screen while the blog should feel calmer and more text-focused. But each additional template style creates another maintenance point. If you duplicate a style, change the colors, and forget to assign it to the right menu item, the result can look random.

Keep the structure clear: one main style for most pages, and a separate style only for a special landing page or experimental page. After any change, open the Joomla menu item and check the template style field, then open the style itself and review its Menu Assignment. That will quickly show you why a page is using the wrong appearance.

Multilingual setup and language switcher

If the site uses multiple languages, do not start translation by copying every builder layout. YOOtheme Pro documentation recommends setting up languages first, translating articles, menus, and modules, and only translating pages as the final step. For the language switcher, you can create a menu item with the URL `#language-switcher`, and for more complex multilingual menus, it is often better to use menu modules in the appropriate positions.

With Max, this matters even more because the navigation is intentionally short. The Russian, English, and other language versions of the menu can have very different word lengths, and the header may behave differently as a result. Check the desktop, tablet, and mobile previews, and replace long menu labels with shorter wording if they disrupt the rhythm.

Practical Ways to Use Max on Different Types of Sites

Max is not limited to a personal portfolio, but it also should not be stretched to fit every kind of project without adaptation. Below are a few realistic scenarios where the template and YOOtheme Pro can help you build a clear structure quickly. These ideas are based on confirmed building blocks: ready-made layouts, style variations, the builder, modules, pages, the blog, and the demo package.

Personal portfolio for a specialist

For a designer, photographer, or art director, Max works well as a profile site backed by visible proof of experience. Use the homepage as a short introduction, Work as an archive of your best projects, Case Study as a detailed breakdown of 2 to 3 selected projects, and Blog as a place for notes on your process. The expected result is that a visitor understands the author's style within a minute and sees exactly where to reach out.

The validation is simple: ask someone unfamiliar with your site to open the homepage and tell you your specialization, your strongest project, and the next step they should take. If they cannot do that without scrolling down to the footer, the hero and first cards need to be rewritten.

Small studio or agency

For a studio, Max can be expanded into a more team-oriented site: About introduces the people and the approach, Services explains the offerings, Work leads into projects, and Blog demonstrates expertise. In this scenario, the footer and contact block matter especially because a visitor may arrive not only from the homepage, but also from an individual case study or article.

The main risk in an agency setup is overloading the menu with services. It is usually better to keep the top navigation short and present detailed services inside the Services page with cards and anchors. If you have many services, use separate pages and careful internal linking instead of building one long screen with dozens of blocks.

Promo page for a product or event

Max can also work for a promo page if the product is visually driven: an exhibition, album, course, design series, or media project. In that case, the main focus shifts to the hero, a few proof-oriented sections, a gallery, a program description, and contact. The builder makes this kind of page faster to assemble than writing a separate template.

But there is a limitation: if the product requires a shopping cart, booking flow, user account area, or a complex catalog, Max only covers the presentation layer. The functional layer should be handled by a specialized Joomla component, and you then need to validate how its output fits inside the template style.

Content site with visually distinct categories

For a small magazine or blog, Max can provide a bold homepage and attractive category pages, but high-volume content is still better managed through Joomla articles and output templates. The key here is not to build every article manually in the builder if the editorial team will be publishing frequently. Use the builder for key landing pages, and use blog and post settings for regular publishing.

A quick validation step is to create one regular article without a manual layout and see whether it looks acceptable next to the homepage. If it does not, configure the post layout, width, images, and metadata before you start the editorial workflow.

Practical Example: Build a Portfolio Homepage and Validate the Result

Now let us turn the setup into a concrete scenario. The goal is to create a homepage for a specialist portfolio: a bold first screen, 2 to 3 featured projects, a short services block, a contact transition, and a clean footer. This is a typical Max use case because the demo is already built around similar logic.

Goal and preparation

We need a site where the visitor immediately sees the author's specialization, a few real projects, and a clear path to contact. Before you begin, prepare the logo, hero image, a short personal statement, project images, case study titles, a list of services, and a contact email. If you have a staging environment, build the example there.

Check that YOOtheme Pro opens correctly, that the template style is assigned to the test homepage, and that the selected style variation is reasonably close to the original Max look. If you are working with the demo package, save a copy of the original layout in the layout library or duplicate the page so you have something to return to.

Setup steps

Order of actions in the builder

1. Open the homepage in YOOtheme Pro and replace the hero text with a short statement about your specialization.
2. Upload the hero image and check the focal point so the important area is not cropped on different screen sizes.
3. Keep 2 to 3 project blocks and remove extra demo sections if you do not yet have content for them.
4. For each project, specify the title, area of work, and a link to a separate case study or portfolio page.
5. Use short wording in the services block, and move the details to the Services page.
6. Check the footer: contact details, social links, legal links, and, if needed, a link to consent settings through `#consent-settings`.
7. Save the layout, then save the theme settings if you changed global parameters.

At this stage, you do not need every pixel to be perfect. What matters is getting a working structure where every link leads to a real page, the images do not break the proportions, and the top navigation remains short and clear.

Validating the result

What should be visible on the site

Open the page in desktop preview, tablet preview, and mobile preview. Then check it as a guest. Look not only at how it looks, but also at how it behaves: is the main copy visible, is the hero hidden by the header, have any modules disappeared, are old cached images still showing, and does the contact link work correctly?

A good Max result is when a visitor understands the specialization before the first click, sees real work in the first sections, and can move to contact without hunting through the whole site.

If something goes wrong, roll back in a targeted way. Do not delete the entire layout. Restore the previous image, disable the last section, reset one changed style parameter, or clear cache. That will help you find the real cause much faster than rebuilding the page from scratch.

Checking Speed, SEO, and Usability After Setup

Max does not guarantee a fast site or strong rankings on its own. It provides the visual foundation, while the actual result depends on image sizes, heading structure, content quality, cache, external scripts, hosting quality, and how you use the builder. That is why you need a separate validation pass after setup.

Speed and images

Check the weight of the homepage, especially the hero image. YOOtheme Pro can generate responsive images and use lazy loading, but the source images still need to be reasonably sized. If your portfolio blocks are loading massive files, the user will see the beautiful design too late.

Under Advanced settings, there are options for next-gen images, image URLs, and cache. Do not enable them blindly on a live site without testing: first confirm that the server supports the required formats and that cache behavior does not break. After enabling them, open several pages and make sure the images load correctly and old URLs do not conflict with page cache.

Page-level SEO structure

Do not check only the metadata. Review the structure of the page itself. Max uses large visual sections, so it is easy to end up with a beautiful hero that lacks clear textual meaning. The homepage needs a clear H1, internal pages need headings that explain the service or case study, and images should have proper alt text in Joomla or in the builder fields.

For a portfolio site, it is useful to create separate case study pages with their own headings and descriptions. A general grid of work looks good, but both search engines and users often need a specific breakdown: what was done, for whom, what the outcome was, and which materials are shown. Do not promise ranking growth just because of the template. It creates structure, but it does not replace content.

Editor usability

If multiple people will use the site, configure roles and permissions. YOOtheme Pro documentation specifically calls out the `Edit Templates` permission: users who can access the customizer can change much more than ordinary content. For editors who only need to update text and images, it is better to prepare a clear workflow: which articles they edit, which modules they can touch, and which builder pages require approval.

If an editor accidentally changes a global style or template, the issue affects the entire site. For that reason, a team should keep a short internal checklist: where to update the logo, where to update the portfolio, where to update services, what should never be changed without a test copy, how to validate the result, and who to notify if something goes wrong.

Safe Improvements Without Editing the Template Core

YOOtheme Pro offers several safe paths for minor customization: CSS in settings, CSS on a specific element through the Advanced tab, template styles, language overrides, and a child theme for more serious work. For Max, targeted CSS tweaks and language overrides are usually enough. There is no need to edit Joomla core files, YOOtheme Pro core files, or the template itself.

Subtle hover effect for project cards

If the project cards feel too flat after you replace the images, add the class `max-project-card` to the required element or panel in the Advanced tab. Then paste the CSS into that element's specific field or into YOOtheme Pro global CSS if the effect should be reused across several cards. The safe approach here is easy to justify: YOOtheme Pro documentation describes the Advanced tab, the Classes field, and Custom CSS for an element, as well as global CSS in Settings.

/* YOOtheme Max: subtle emphasis for project cards */
.max-project-card {
    transition: transform .18s ease, box-shadow .18s ease;
    box-shadow: 0 10px 30px rgba(0, 0, 0, .12);
}

.max-project-card:hover {
    transform: translateY(-2px);
    box-shadow: 0 18px 44px rgba(0, 0, 0, .18);
}

Validation: open the portfolio page, hover over the card, and make sure the text does not jump, the link remains accessible, and the mobile layout does not depend on hover. Rollback: remove the class from the element or delete the CSS snippet. This kind of snippet does not alter the core and does not interfere with Joomla data.

Language overrides instead of manually hunting through files

If you need to replace an interface string in the template, use Joomla language overrides. YOOtheme Pro documentation notes that YOOtheme strings can be searched by the `TPL_YOOTHEME` constants, while Joomla stores overrides separately. That is safer than editing the template language files, which may be replaced during an update.

The workflow is simple: find the string, create an override for the required language, validate the public-facing site, and record the change in the project documentation. If the string does not change, check whether it is actually coming from custom builder content rather than a language file.

When you actually need a child theme

A child theme is needed when you add system files, overrides, new elements, or more substantial development work. For ordinary Max adaptation - logo, colors, spacing, cards, text, menus, modules - it is often unnecessary. Start with the built-in YOOtheme Pro and Joomla settings. If the change begins to affect PHP templates or repeating system blocks, then move it into a child theme and document exactly what was changed.

Why Max May Not Look Like the Demo and How to Diagnose It

Most YOOtheme Max issues look like visual breakage, but the underlying cause usually lives in one of five places: the wrong archive was installed, the template style is assigned incorrectly, a module is published on the wrong page, CSS could not be written because of permissions, or cache is showing an old version. Below is a practical diagnostic workflow without panic and without deleting the template outright.

The site does not look like the demo after installation

Symptom: the template is active, but there is no ready-made homepage, no portfolio blocks, and no demo structure. A likely reason is that only the theme package was installed on an existing site rather than the demo package as a full installation. This is normal behavior: a regular package does not automatically turn an existing site into the demo.

What to check: the archive type, presence of demo content, template style, menu item assignment, and whether the page has a layout. How to fix it: either work with the demo package on a fresh test environment, or load the required layouts from YOOtheme Pro and replace the content manually. The only thing you should roll back is the template style assignment if the issue affected live pages.

Settings do not save or the site loads without CSS

Symptom: changes in the customizer do not apply, the site looks unstyled, or everything reverts after saving. A likely cause is file permission issues in the template, CSS, or cache directory. YOOtheme Pro documentation directly connects failed configuration saves and missing CSS with file permission problems.

What to check: directory and file permissions, file ownership on the server, the PHP error log, and whether the template and cache folders are writable. How to fix it: coordinate the permissions with your host, use safe values for directories and files, then save the setting again and clear cache. Rollback: restore the previous permissions if the change creates new access restrictions or server errors.

A module is published but not visible

Symptom: the module exists in Joomla, is enabled, and is assigned to the page, but it does not appear on the public-facing site. A likely cause is the wrong position, menu assignment, device visibility rule, a builder page missing the required Position element, or a `sidebar` position that does not render on pages built with full-width builder sections.

What to check: the module position, the page template style, menu assignment, published state, visibility settings, and whether the layout contains a Position element. How to fix it: move the module to a real position such as `top`, `bottom`, `navbar`, or `dialog`, or add a Position element for the builder position. Rollback: restore the previous position and menu assignment.

The builder says it is unavailable on the page

Symptom: YOOtheme Pro does not open the builder for a specific page or shows a message that it is unavailable. According to the documentation, possible causes include an expired Joomla session, conflicts with certain security extensions, email-to-image conversion, certain third-party component settings, or Cloudflare RocketLoader.

What to check: logging into the admin panel again, testing in another browser, conflicting system plugins, the browser console, and disabling a questionable script acceleration feature in a test environment. How to fix it: refresh the session first, then temporarily disable only the suspected extensions on staging. If the issue disappears after disabling one, look for a compatibility setting rather than leaving the extension off without analysis.

Animations or interactive elements stop working

Symptom: a dropdown, offcanvas panel, slideshow, smooth scroll, or another interactive Max block works on some pages and breaks on others. A likely cause is a JavaScript error introduced by a third-party extension, optimization setting, or script conflict. YOOtheme Pro documentation recommends checking the browser console and identifying the file that triggers the error.

What to check: the browser console, temporarily disabling script minification or merging in a test environment, comparing a broken page with a working one, and reviewing recently added extensions. How to fix it: temporarily disable the conflicting script or optimization setting, clear cache, and check the page again. Roll back acceleration settings if they break navigation or builder elements.

The old image still appears after replacing it

Symptom: you replaced the file, but the site still shows the previous version. Possible reasons include the same filename being reused, cached YOOtheme images, Joomla cache, or browser cache. What to check: the filename, cache clearing, a private window, `media/yootheme/cache` through a safe file management tool, and the Image URLs settings.

How to fix it: upload the file under a new name, resave the element, clear cache, and validate the page while logged out. If the issue continues, do not delete the entire media library. Find the specific cached file or regenerate the image through the settings.

When YOOtheme Max Is the Right Choice

YOOtheme Max is a strong choice if you need an expressive Joomla site with a portfolio, services, case studies, and a clear visual presentation. It works especially well when you are prepared to treat the demo like a system: keep the section rhythm, replace the images with quality assets, adjust the style variation, validate the modules, and stay focused on real content.

Before launch, run through one final checklist: the template style is assigned correctly, the homepage and key pages have been checked as a guest, the images do not break the mobile layout, the modules are visible on the right menu items, editors have appropriate permissions, cache has been cleared after major changes, and the contact path works. If all of that is in place, you can download YOOtheme Max and safely move on to testing the archive on your own site copy.

Do not aim to make the site an exact copy of the demo. It is better to preserve Max's strongest qualities - a bold first screen, confident color, short navigation, clear case studies, and clean service pages - and remove anything that does not help your visitor. That is when the template stops being decoration and becomes a practical site foundation.