YOOtheme Soda - Joomla Template

How to Set Up YOOtheme Soda for a Creative Studio Joomla Site

YOOtheme Soda is more than just a dark visual Joomla template. It is a ready-made YOOtheme Pro layout package for a studio, agency, portfolio, or team site that showcases its work through strong imagery, case studies, and clean navigation. This guide focuses on the practical side rather than the marketing pitch: how to approach the installation, which settings to review first, how to adapt the demo to your own services, where modules can break, and how to tell when the site is actually ready to launch.

The main idea behind Soda is to provide a starting structure for a creative website: a homepage, portfolio, case studies, team pages, careers, contact, and blog. But the template only becomes truly valuable after proper setup. You need to choose the right style, replace the demo content, align the menu with the project structure, check module positions, responsiveness, image loading performance, and editor permissions.

What follows is a working guide: first we determine whether Soda fits the job, then we prepare Joomla, install the package, configure YOOtheme Pro, build the homepage structure, check the result, and troubleshoot common issues. If you already have the template archive, this guide will help you go beyond installation and bring the site into a manageable, production-ready state.

A strong template setup does not start with replacing the logo. It starts with understanding which demo pages to keep, which to remove, and which to turn into real working sections. This matters especially for Soda, because the template looks convincing precisely as a visual agency site. If you leave random demo case studies and empty categories in place, the page quickly turns into a beautiful but confusing storefront.

When Soda Works Better Than a Generic Multipurpose Template

Soda is designed for sites where visual impact matters more than a dense information structure. According to the official YOOtheme page, the package is aimed at VFX, 3D animation, media agencies, galleries, portfolios, and case studies. You can see that immediately in the demo: a dark background, large typography, asymmetric imagery, a categorized portfolio, case study pages, and service blocks. This approach works well when visitors need to quickly grasp the character of the work and move to a specific project.

The template is a good fit for a 3D studio, motion design team, architectural visualization company, VR/AR project, production agency, illustrator portfolio, commercial video studio, or small creative bureau. It can also be adapted for adjacent niches such as product photography, interior design, exhibition installations, industrial design, and video production. The key is having strong visuals and clear case studies. Without them, Soda's visual structure will work against the site instead of for it.

Where the Template Performs Best

The most natural use case is a site with several types of work and dedicated case study pages. The demo Work page shows filtering by areas such as Animation, Architecture, Product, Technology, and Vehicle. For a real project, those can become service or industry categories such as "3D interior visualization," "product animation," "VR presentations," or "motion graphics for advertising." That way, visitors are not just looking at a beautiful gallery. They understand what kinds of problems the team actually solves.

The second strong use case is the homepage as an agency presentation. In the demo, it combines a hero block, a list of focus areas, client logos, and a contact CTA. If you replace the demo images with real work and connect the service list to actual pages or anchors, Soda becomes a full landing page for a creative studio. Do not try to cram everything into the first screen. It is better to keep one strong visual message and guide the user toward the portfolio.

When Another Template Is a Better Choice

Soda may be excessive if the site is primarily meant to be a knowledge resource, a catalog with lots of text-heavy cards, a corporate portal, an online store, or a service with a user account area. The template can technically be adapted for those needs, but the starting structure will require more rework. If you have limited visual assets, no case studies, and need a calm light corporate interface, it makes more sense to consider another YOOtheme package or a more neutral Joomla template.

Another risk is using the demo too literally. Soda looks like the website of an agency called SODA, and if you only swap the logo while leaving the service structure, case study titles, random photos, and placeholder copy untouched, visitors will immediately notice the template feel. That is why, throughout this guide, we treat Soda as a starting layout system rather than a ready-made page that can be published without editorial work.

What the Package Includes and How That Shapes the Rollout Plan

The official Soda listing highlights three important groups of assets: ready-made page layouts, style variations, and curated images. That means implementation should not be planned as "install the template and change the colors." It should be planned as selecting a set of pages, a style, and visual content. For a Joomla site, this matters especially because the menu, articles, modules, and template styles all need to line up. Otherwise, users may land on a page without the intended layout, or a module may appear in the wrong place.

According to the official page, Soda includes 12 ready-made layouts. Among them are the homepage, portfolio, several case study pages, About, Careers, Developer Careers, Contact, Index, and Post. That is a strong set for an agency site: you can showcase services, work, the team, job openings, contact information, and a blog. But not every company needs to use all 12. In many cases, it is better to keep 5 or 6 strong pages and remove weak demo sections than to publish a long menu full of half-empty content.

The six style variations listed on the official page are useful for more than color alone. They let you quickly test which tone fits the brand best: a dark studio look, or a lighter version with red, pink, green, dark blue, or blue accents. But you should not switch styles blindly after filling the entire site. First choose 2 or 3 key pages, insert real images, then switch styles and check contrast, buttons, background sections, menu state, and the readability of long headlines.

The curated images in Soda help you quickly assemble a demo-like site, but they have limits. Images do not replace real work. For a studio portfolio, it is better to use your own renders, stills, photo shoots, project previews, and case study covers. Demo images are fine as temporary placeholders during prototyping, but before launch every image should be replaced or removed so the site does not create expectations the team cannot support.

Preparing Joomla Before Installation and the First Admin Decisions

Before installing Soda, it is important to understand what exactly you are installing. The YOOtheme Pro documentation for Joomla separates two scenarios: installing the YOOtheme Pro theme on an existing site, and installing a demo package as a full Joomla setup with demo content. These are not the same thing. The theme archive is installed through Joomla's template mechanism, while the demo package is not meant to be uploaded over an already running site. Choosing the wrong archive type is one of the most frustrating starting mistakes, because users expect to "install a template" and instead get a full-site installation package.

If the site is already live and contains articles, users, menus, multilingual content, or SEO pages, it is safer to deploy Soda on a copy of the site or a staging domain. There you can test YOOtheme Pro, import the required layouts, choose a style, connect the menus, and only then move the result over. If the project is new and you want to study Soda's ready-made structure, the demo package is more convenient because it shows how the pages, modules, images, and navigation are put together.

Minimum Pre-Install Checklist

The checks below should not turn into bureaucracy. They are there to prevent basic problems from surfacing only after the layouts have already been assembled:

• Create a backup of the files and database if you are not working on a clean installation.
• Make sure you have Joomla administrator access and permission to manage templates.
• Confirm whether you are using the theme archive or the demo package, because they are installed differently.
• Check PHP limits for uploading large archives: POST size, upload file size, execution time, and memory.
• Disable aggressive caching during setup so you do not confuse old HTML with the new result.
• Prepare real images for the homepage and portfolio, otherwise visual validation of Soda will be misleading.

If you are not sure which archive you have, do not upload it to the live site. First unpack a copy locally or on a test domain and inspect the structure. A demo package usually behaves like a starter site, not like a standard template for an existing Joomla installation.

Permissions and Editors

The YOOtheme Pro documentation notes that access to the customizer depends on the Edit Templates permission. On a small site that may seem minor, but on a real team you should not give template editing access to every content editor. One administrator or technical editor responsible for page structure is enough. A content manager can still handle articles, images, and text, but not global styles, the header, footer, or template styles.

The rule is simple: the closer a setting is to the site's global appearance, the fewer people should be able to change it without review. This matters especially in Soda, because one bad style choice, one overly long menu item, or one careless section edit can throw off the composition of the homepage and portfolio.

Installation: Theme, Demo Package, and Initial Validation

For an existing site, use the YOOtheme Pro theme installation archive for Joomla. After installation, make the template active in Joomla and open the YOOtheme Pro Website Builder. At this stage, do not start importing everything right away. First confirm that the template opens, the preview works, the admin panel shows no errors, and the public side of the site displays at least a basic page.

If you are working with the Soda demo package, treat it as a learning and starter site. Its main value is that it shows a ready-made combination of pages, images, menus, and styles. According to the official Soda page, the Joomla demo package does not rely on third-party plugins, so the starting dependency stack is simpler: Joomla + YOOtheme Pro + demo content. That does not eliminate the need to check server limits, file permissions, and cache, but it reduces the risk of conflicts with unknown extensions.

Initial Check After Installation

1. Open the public side of the site in a private browser window and confirm that the correct template is active.
2. Log in to YOOtheme Pro and make sure the Layout, Style, Builder, Modules, and Templates panels open correctly.
3. Open the homepage and try editing one safe text block, then click Save Layout.
4. Clear the Joomla cache and browser cache if the result does not change.
5. Restore the test text to confirm that you understand the full edit-and-rollback cycle.

After this check, you already know the essentials: the template is installed, the builder saves changes, the front end responds to edits, and the cache is not blocking basic work. Only now does it make sense to move on to structure and style configuration.

What Not to Do Right Away

Do not begin with code edits, a child theme, or by moving every demo page into the menu. Soda is built on YOOtheme Pro, and most visual tasks should first be handled through the builder, the style customizer, template styles, modules, and menu assignment. Code changes should be reserved for small project-specific improvements that cannot be handled cleanly through settings. This order reduces update risk and makes the site easier to hand off to another administrator.

Appearance Setup: Styles, Header, Menu, and Soda's Visual Rhythm

Detailed Soda configuration starts with choosing a visual mode. The template includes multiple style variations, and YOOtheme Pro lets you change colors, fonts, the header, navbar, dropdown, offcanvas, search, and other layout parts. But setup should not turn into random toggling. A creative site needs sequence: style, logo, header, menu, hero, portfolio, contact CTA.

Choosing a Style Variation

Start with the style that best supports your real images. The dark Soda variant works especially well for bright 3D renders, video stills, and high-contrast portfolios. Lighter variants may be a better fit for architecture, object design, an educational studio, or an agency that needs a less night-like presentation. Test the style not on an empty demo, but on 5 to 7 real images: the homepage, two portfolio cards, one case study, the contact block, and the footer.

Testing Against Real Content

After switching styles, check three states: the hero area, a long case study page, and the contact page. If buttons disappear against the imagery, the headline feels too heavy, or the portfolio filters are hard to read, the style needs adjustment or should be replaced. In YOOtheme Pro, the style customizer affects UIkit variables and components, so one change can alter buttons, cards, links, and navigation across multiple areas at once.

Header and Navbar

The Soda demo uses a minimal top navigation. For a real site, it is better to keep the first menu level to 5 to 7 items. If you put every service, every blog section, and every careers page into the top level, the composition quickly becomes cramped. In YOOtheme Pro for Joomla, the header and navbar include behavior modes such as static and sticky navigation, along with settings for dropdown, dialog, offcanvas, and search. For Soda, a simple navigation is usually enough: Work, Services, Studio, Careers, Contact, Blog.

What to Keep in the Top Menu Level

If the site has a long list of services, use a dropdown or a dedicated Services page instead of overloading the navbar. For the mobile view, check the dialog or offcanvas early. In creative templates, desktop navigation often looks clean, but on smaller screens long items can break the rhythm. In practice, that shows up as an overly tall first screen, cut-off words, or a menu that overlaps the hero area.

Logo and Typography

The logo in Soda should stay simple. A complicated mark next to large typography and a collage of images will compete with the content. If the brand has a long name, test a short text version in the header and the full version in the footer. Change fonts carefully. The official YOOtheme Pro documentation notes that Google Fonts can be stored locally after selection in the style customizer, but they still affect page weight and the site's visual character. Do not load too many font weights unless you actually need them.

A Safe CSS Tweak for Accent Links

If you need to slightly strengthen a portfolio link or a button accent in the services block after choosing a style, do it through a section class and a child theme rather than by editing the template files. In YOOtheme Pro, you can add a custom class to the required section or element, and the child theme documentation confirms support for css/custom.css. The example below is not tied to any hidden API. It only affects elements using your class.

/* templates/yootheme_NAME/css/custom.css */
.soda-portfolio-accent .uk-button,
.soda-portfolio-accent .uk-link {
  letter-spacing: 0.02em;
  text-transform: uppercase;
}

.soda-portfolio-accent .uk-button-primary {
  box-shadow: 0 0 0 1px rgba(0, 210, 190, 0.45);
}

Before pasting it in, add the soda-portfolio-accent class only to the section where the accent is needed. After saving, clear the cache and check the button on the homepage, in the portfolio, and at mobile size. Rolling back is simple: remove the class from the section or delete the CSS from custom.css. Do not use CSS like this as a way to patch every style issue. If half the template is changing, it is better to go back to the style customizer and the layout structure.

Portfolio and Case Study: Turning the Demo Gallery into Clear, Meaningful Work

The most product-specific part of Soda is the portfolio. In the demo, the Work page displays categories and a set of projects. On a real site, this section should answer not "does the grid look impressive?" but "is it clear what kinds of problems this team has already solved?" If the cards look striking but the project titles explain nothing, visitors will not know how to choose a relevant example.

Start by classifying the work. For a 3D studio, that might be Animation, Architecture, Product, Technology, and Vehicle. For a design agency, Branding, Motion, Web, Campaign, and Illustration. For a VR/AR team, Training, Presentation, Simulation, Exhibition, and Product Demo. The important thing is that the category helps visitors get to the right case study faster rather than simply mirroring the studio's internal folder structure.

Project Card

Each card should have three layers of meaning: image, title, and brief context. If the layout does not allow for a longer description on the card itself, add the context on the case study page: the task, the team's role, the visual deliverables, the result, and any technical constraints. In Soda, concise titles and strong covers work best, but the case study page needs to explain the work in more depth.

A practical case study structure:

• A short description of the client task or internal project goal.
• What materials were available at the start: drawings, 3D models, brand guidelines, script, or prototype.
• What the team did: modeling, rendering, animation, post-production, VR scene work.
• Which images or videos show the result.
• How the visitor can move to a related service or contact the team.

Filters and Categories

Filters are only useful when each category has enough work in it. If Technology contains one project and Product contains ten, visitors will treat the filter as decoration. Early on, it is better to keep fewer categories and fill them properly. As the portfolio grows, you can expand the taxonomy.

The test is simple: open Work in a private window, click each category, and see whether the grid still feels convincing. If a category reveals emptiness or a single random project, merge it with a neighboring one. For both SEO and user experience, a clear group of related work is more effective than a long list of precise but half-empty categories.

How to Preserve the Style When Replacing Images

In Soda, the demo images are curated around a consistent mood: dark backgrounds, bright objects, and a technical, cinematic feel. If you replace them with random light photos, the template can lose its character. Before uploading your own work, bring the covers into a consistent rhythm: similar contrast, clean margins, a clear focal point, and no distracting fine detail in the center. That does not mean every project needs identical processing, but the grid should feel cohesive.

A strong portfolio card in Soda should make sense without requiring a long text explanation. The visitor sees the cover, understands the type of work, opens the case study, and gets the details there. If the cover needs too much explanation, it is not a good fit for the main grid.

Modules, Positions, and Menus: The Joomla Logic Without Which the Template Feels Broken

YOOtheme Pro for Joomla is integrated with Joomla's Module Manager, and the documentation covers the Modules panel, module positions, visibility, the builder module, and the behavior of top, bottom, sidebar, dialog, header, and other positions. This is critical for Soda. A visual layout can look empty not because the template is broken, but because a module is unpublished, assigned to the wrong menu item, or placed in a position that is not rendered in the current context.

Pay special attention to the sidebar. The YOOtheme Pro documentation states that the sidebar position is not rendered on pages built with the page builder, because full-width sections are meant to be controlled inside the layout. For Soda, where many pages are built as expressive builder layouts, this is a common reason behind the "I published the module, but it isn't there" problem. The fix is to use a Position element in the builder or a more appropriate position such as top, bottom, dialog, or navbar, depending on the page structure.

How to Check a Module Position

A practical verification workflow looks like this:

1. Open the page where the module is supposed to appear.
2. In YOOtheme Pro, go to the Modules panel and find the required position.
3. Check the gray dot or other visibility indicator if the interface shows whether the module is published on the current page.
4. Hover over the module in the builder sidebar and see whether its representation is highlighted in the preview.
5. If the module is still not visible, check publication status, language, access, menu assignment, and position.

On the Soda homepage, it is best to use modules where they genuinely help: an alternate menu, a contact block, a language switcher, footer sections, a bottom-position CTA, or a builder module for a reusable block. Do not turn every homepage section into a separate Joomla module if it is easier to maintain as a layout inside YOOtheme Pro. At the same time, reusable elements such as the footer or a language switcher should not be copied manually onto every page.

Menus and Multiple Template Styles

The YOOtheme Pro documentation describes the ability to create multiple template styles and assign them to different menu items. For Soda, that is useful if one part of the site needs a different color scheme or content density. For example, the homepage and portfolio can stay dark while the blog or careers pages use a lighter style. But this approach requires discipline. If you create multiple styles without a clear rule, the site will start to feel like a collection of unrelated templates.

Use a separate template style only when there is a clear reason: a different background for the blog, a dedicated landing page, a calmer treatment for the careers page, or a test redesign for one category. After assigning the style, check the menu assignment in Joomla and open the page directly, not only through the menu. Sometimes users land on an article without the expected menu item, and Joomla applies the default style instead, changing the appearance.

Practical Example: Building a Studio Homepage with Soda

Now let's walk through a concrete scenario. Suppose you need to launch a 3D visualization studio site where the homepage should quickly explain the specialization, present the main service areas, lead users into the portfolio, and end with a contact CTA. The goal is not to rewrite the whole template, but to adapt Soda so visitors clearly understand what the team does and where to view the work.

Goal

Create a homepage with a clear hero section, a services list, a featured work block, client logos or trust signals, and a contact CTA. Visually, the page should retain Soda's character: a dark background, large headlines, high-contrast imagery, calm navigation, and an expressive grid.

Preparation

Prepare 6 to 10 work images, a short statement of specialization, a list of services, 3 or 4 portfolio cases, and contact details. If you do not have real client logos, do not invent them. It is better to replace that block with "Selected projects" or "What we do" built around honest, real work.

Setup Steps

1. Open the homepage in YOOtheme Pro and save the original layout to the library so you have a rollback point.
2. Replace the hero headline with a specific specialization, for example, "3D visualization for product launches and digital campaigns".
3. Keep 3 to 5 service areas instead of a long list if the team does not actually cover every demo direction.
4. In the portfolio block, include only projects that have a dedicated case study page or at least a clear and meaningful card.
5. Configure the main menu: Work, Services, Studio, Contact, Blog. Do not place temporary demo pages in the top level.
6. Check the header: logo, spacing, sticky behavior, and the appearance of the dropdown or dialog on mobile.
7. In the footer, replace the address, email, social links, and repeat only the menu items that are actually published.
8. Clear the cache and check the page in a private browser window.

Checking the Result

Four Questions to Ask After Building the Homepage

The homepage is not done when it "looks like the demo." It is done when users can answer four questions: who you are, what kind of work you do, where to see examples, and how to get in touch. Open the page on desktop and phone, scroll through it outside admin mode, and click every link in the hero, services, portfolio, and footer. If any click leads to demo content, a hidden page, or an empty article, go back to the structure.

A quick Soda check: if the page loses contrast after you replace the images, do not rush to change the entire style. First check the image crops, then the section background, and only after that the global colors.

A Common Nuance That Gets in the Way

The Soda demo uses strong visual accents. If your real images are more restrained, the homepage may become less expressive. Do not compensate for that with random animation or extra blocks. It is better to choose 2 or 3 genuinely strong images for the hero area and portfolio and place the rest of the work deeper in the site. That way, the template keeps its character instead of turning into an overloaded gallery.

Practical Ways to Use Soda for Different Creative Sites

The same template can be used in different ways as long as you do not break its visual logic. Soda adapts well to scenarios where there is a visual result, a story behind the work, and a contact CTA. What follows is not a generic list of "where it might be useful," but use cases based on the package's confirmed strengths: ready-made layouts, portfolio, case studies, styles, imagery, and the YOOtheme Pro builder structure.

3D Studio Website

Keep the dark homepage, make Work the central section, and use case studies for detailed project pages. Services can be organized around modeling, rendering, animation, post-production, and VR/AR. The success check is simple: from the homepage, a visitor should be able to reach a relevant case study in two clicks and see not just a picture, but the context behind the work.

Motion Designer or Art Director Portfolio

Simplify the menu and remove corporate sections that do not belong on a personal portfolio. The homepage can lead into selected work, Studio can become About, and Careers can be removed. What matters here is not the number of pages, but the quality of the cards and the consistency of the visual narrative. If there is no blog, do not keep Blog in the menu just because it exists in the demo.

Agency Site with Multiple Service Areas

Use separate pages for services and portfolio, but keep the overall style consistent. For an advertising agency, Work categories might reflect the type of deliverable: campaign, product visual, animation, identity, installation. In this scenario, separate template styles can be useful for special landing pages, but only if the difference helps visitors rather than simply showing off the customizer.

Internal Sales Demo Site

Soda can work well as a fast prototype for presenting services to a client. The demo package shows the structure, and the YOOtheme Pro layout library makes it easy to save and transfer layouts. But before public launch, that prototype must be cleaned of demo content, have its contacts replaced, and have its access permissions checked. A prototype containing someone else's project names should never end up indexed by search engines.

Multilingual Setup, Localization, and Project Adjustments Without Touching the Core

For a creative studio Joomla site, you will often need at least an English version, especially if the portfolio targets international clients. The YOOtheme Pro documentation covers multilingual site support, the language switcher, translation of pages and modules, and language overrides. But it is important not to overestimate automation here. Builder content should be planned as separate language versions, not as fields that can somehow be translated automatically.

If the site is bilingual, build and validate the main language version first. Then translate the pages, menus, and modules. The YOOtheme Pro documentation recommends translating pages at the final stage, because changes to page builder settings may need to be repeated for each version. For Soda, this is practical: first bring the homepage, Work, one case study, and Contact page to a working state, and only then create language copies.

Language Switcher in Navigation

YOOtheme Pro allows you to add a language switcher through a menu item with the #language-switcher link. In Soda, it is better to place the switcher in the navigation or dialog rather than making it a primary element of the hero area. Check how it appears in the desktop header and the mobile dialog. If full language names break the menu, use a shorter format or move it to a separate position.

Language Overrides

Joomla supports language overrides through System and Language Overrides. For YOOtheme Pro, you can search for strings with the TPL_YOOTHEME prefix. This is a safe way to change a label such as "Continue Reading" without editing the template files. In Soda, this approach is useful on blog pages, case studies, and other reusable system elements.

Child Theme as the Right Place for Clean Project Changes

If you need custom CSS, custom JS, a font, a small override, or a dedicated builder element, use a YOOtheme child theme. The documentation emphasizes that the child theme keeps project-specific changes separate from YOOtheme Pro and helps preserve them through updates. For a typical Soda site, css/custom.css, language overrides, and builder settings are usually enough. Leave deeper template file overrides to a developer, because they require a solid understanding of Joomla and YOOtheme Pro structure.

Do not edit Joomla core files, YOOtheme Pro core files, or demo package files directly. Even if the change seems minor, it can disappear after an update or create a conflict. If the task cannot be solved through settings, first check the child theme, language overrides, and documented extension points.

Final Validation Before Launch

After configuring Soda, you need to verify more than just the look. Launching a creative website depends on the full combination of menus, portfolio, case studies, contact, responsiveness, performance, privacy settings, and editor permissions. If you only review the homepage, it is easy to miss an empty case study, a broken contact method, the wrong template style, or a module visible to admins but hidden from guests.

Front-End Review

• Open the homepage, Work, one case study, Studio/About, Careers or an equivalent section, Contact, and Blog if it is used.
• Check every menu item on desktop and at mobile size.
• Click portfolio cards, filters, buttons, social links, and contact CTAs.
• Make sure demo copy, placeholder phone numbers, and test addresses have been removed.
• Open the site in a private window so you can see the result without administrator permissions.

Performance and Image Review

Soda depends heavily on visual content, so images can easily become the main source of page weight. Do not upload full-resolution original renders to the homepage if they are only displayed as cards in the browser. Use optimized sizes, meaningful alt text, and avoid overloading the hero area with dozens of large files. If the page includes video, maps, external forms, or third-party services, account for privacy settings and user consent.

The YOOtheme Pro privacy documentation states that the theme itself does not store personal data or create tracking cookies, but third-party services such as Google Maps, YouTube, Vimeo, Mailchimp, and similar elements require separate review. This is especially relevant in Soda on the Contact page if you add a map or signup form.

Administration Review

Before handing the site over to the team, create a short internal guideline: who edits text, who uploads images, who edits layouts, and who has access to template styles. Confirm that an editor can update an article or project without breaking the header, footer, or style customizer. On an agency site, this reduces the risk of accidentally ruining the composition after the first round of content edits.

If Soda Does Not Look Like the Demo: Troubleshooting and Fixes

Problems with a Joomla template often look like "the template is broken," but the real cause is usually the archive type, menu assignment, module position, cache, access permissions, server limits, or an overly loose replacement of the visual content. Below is a practical troubleshooting guide specifically for Soda and YOOtheme Pro on Joomla.

The Demo Does Not Appear After Installation

Symptom: the template is active, but the site does not look like the Soda demo. The homepage is empty, there is no portfolio, and the ready-made blocks are missing.

Likely cause: a standard YOOtheme Pro theme was installed on an existing site instead of the full demo package. The documentation clearly separates these scenarios: the demo package is a full Joomla installation with YOOtheme Pro and demo content, while the theme archive is installed into an existing site and is not expected to create all Soda pages automatically.

What to check: the archive type, the active template style, whether layouts were imported, menu items, and published articles.

How to fix it: if you want an exact demo-based starting point, deploy the demo package on a clean test installation. If the site already exists, load the required layouts through YOOtheme Pro and manually connect them to articles and menus.

A Module Is Published but Does Not Show on the Page

Symptom: the module is enabled in Joomla, the position is set, but it does not appear on the Soda page.

Likely cause: the module is assigned to the wrong menu item, hidden by language or access rules, or published in a position that is not rendered on a builder-based page. Check sidebar separately as well. On pages built with the page builder, that position may not render the way you expect.

Quick Troubleshooting Split

What to check: publication status, access, language, menu assignment, position, the Modules panel in YOOtheme Pro, and whether a Position element exists in the layout.

How to fix it: assign the module to the correct menu item, change the position, or add a Position element to the appropriate builder section. If the module is reused across many pages, consider top, bottom, dialog, or a builder module.

The Style Works on One Page but Not on Another

Symptom: the homepage looks like Soda, but a separate page or article opens with a different style.

Likely cause: a different template style is assigned through menu assignment, or the page is loading without the expected menu item. In Joomla, the relationship between template style and menu matters when different appearance variants are in use.

What to check: Extensions / Templates / Styles, the Menu Assignment tab, the default style, and the menu item through which the article opens.

How to fix it: assign the required template style to the specific menu item or create an explicit menu item for the article or category. After making the change, clear the cache and open the direct link in a private window.

The Builder Does Not Save Changes or the Customizer Stops Opening

Symptom: changes do not save, the panel freezes, or an error appears after adding custom CSS or Less.

Likely cause: a syntax error in custom CSS or Less, hosting limitations, file permissions, or a caching conflict. The YOOtheme Pro documentation warns that invalid Less can interfere with the style customizer.

What to check: the latest CSS or Less edits, the browser console, the PHP error log, write permissions, PHP limits, the Joomla cache, and any third-party cache.

How to fix it: temporarily remove the last edit, restore the saved layout, disable minification and caching during troubleshooting, and verify server limits. If the problem started after enabling a child theme, disable the child theme under Settings / Advanced and see whether the error disappears.

The Site Feels Heavy and Slow After Replacing the Images

Symptom: the hero area loads slowly, the portfolio lags, and the mobile version opens slowly.

Likely cause: oversized images, too many heavy sections on the homepage, external video or maps, or demo content that was never fully cleaned out.

What to check: image sizes, the number of files in the first screen, lazy loading, third-party services, cache, and cover image formats.

How to fix it: optimize the images, keep only the strongest work on the homepage, move secondary material deeper into the site, and check privacy-enhanced mode for YouTube if video is embedded through YOOtheme Pro elements.

Limitations and Decisions Around Security, SEO, and Maintenance

Soda helps you assemble a visually strong site quickly, but it does not remove responsibility for content, URL structure, metadata, indexing, privacy, or updates. The template does not guarantee search growth on its own. It provides the visual and builder layer, while SEO depends on clear pages, useful headlines, case study copy, performance, images, internal linking, and clean Joomla implementation.

For SEO, case study pages matter most. Do not leave them as image galleries only. Add a short description of the task, the industry, the service type, the result, and internal links to related work. Use unique title and meta description values in Joomla or your SEO extension, but do not fill them with repeated mentions of the template name. Visitors are not searching for "Soda." They are searching for specific services and examples of work.

For security, keep YOOtheme Pro, Joomla, and all extensions updated, but do not update the live site without testing first if you use a child theme, overrides, or custom CSS. Before updating, review the YOOtheme Pro changelog and create a backup. If the site uses third-party services, forms, maps, or video, review the privacy policy and user consent requirements. The official YOOtheme Pro documentation separately covers privacy aspects for Google Fonts, YouTube, Maps, Mailchimp, and other services.

For maintenance, keep a short site map: which pages are built in the builder, which are standard Joomla articles, which modules appear in which positions, and which template styles are assigned to which menus. A map like that can save hours when you need to understand months later why a specific block is not showing or why a page looks different from the homepage.

When YOOtheme Soda Is the Right Choice

YOOtheme Soda is worth using if you want to quickly build an expressive Joomla site for a creative studio, portfolio, or agency and are prepared to replace the demo content with real work. The template works especially well when you have visual case studies, clear service directions, strong imagery, and a team that can maintain the pages inside YOOtheme Pro.

Before making the final decision, check three things: whether the project has enough visual material, whether the dark agency-style presentation fits the brand, and whether the team is ready to work with YOOtheme Pro, Joomla modules, and template styles. If the answer is yes, you can download the latest version of YOOtheme Soda, deploy it in a test environment, and follow the setup process described in this guide.

If the site is primarily meant to be a store, a knowledge resource, a corporate portal, or a lightweight blog without a strong portfolio, it is better to consider another template. Soda is not technically bad for those use cases, but its visual logic will require more rework. The right choice here is not to pick the flashiest demo, but to choose a starting template that already matches the future structure of the site.