YOOtheme Woolberry - Joomla Template

A Guide to Setting Up YOOtheme Woolberry for a Joomla Fashion and Product Site

It helps to think of YOOtheme Woolberry not as a standard template you simply enable and forget, but as a ready-made foundation for a visual catalog, fashion brand, content-driven store, or promo site with lots of photography, product cards, curated selections, and related content. In this guide, we will walk through how to approach installation, where to find the core YOOtheme Pro settings, how to preserve the demo structure, and how to connect menus, modules, page templates, and Joomla custom fields.

This material is aimed at a site owner, webmaster, or editor who already understands that a short template description is not enough. After installation, it is important to check not only how the homepage looks, but also how categories, product pages, posts, search, menus, module positions, responsive behavior, and access permissions work. Those are the areas that most often turn a beautiful demo site into a long manual rebuild.

What follows is not a promotional retelling of the product page, but a practical guide: what to check before installation, how to choose between the demo package and installation on an existing site, what to configure in Customizer, how to work with Template Styles, where module positions are useful, how to build a real storefront scenario, and how to troubleshoot common issues.

The core idea is simple: Woolberry really comes to life only when the visual layer, content structure, and display rules work together. If you copy over only the images and leave Joomla content in a messy state without fields, tags, and assignments, the site may look like the demo only on the first screen.

What Woolberry Actually Offers and Where It Fits Best

The official YOOtheme page describes Woolberry as a template for fashion, beauty, and retail-oriented websites built on YOOtheme Pro. For the Joomla version, one clarification matters: the demo presents product logic through content structure, custom fields, categories, tags, page templates, images, video, and related content. That does not mean Joomla automatically gets a full eCommerce system with payments, inventory, and order management. If you specifically need a cart, checkout, customer account area, and order processing, you will need a separate commercial extension or another integration.

Woolberry works especially well for projects where the main goal is to present collections, products, looks, editorial content, and brand pages in a compelling way. The demo includes a homepage with a large hero block, Women, Men, and Kids categories, product pages, curated selections, publication pages, FAQ, search, store locations, careers, and error pages. That gives you more than a single layout - it gives you a set of connected user journeys: a visitor can move from a collection to a product, from a post to related products, and from search to recommendations.

For a Joomla site, Woolberry is particularly appealing if you want to keep the site manageable through the CMS. Content remains in articles, categories, tags, custom fields, and modules, while YOOtheme Pro handles visual templates and the connection between dynamic data and layout elements. That approach is useful when the design needs to feel rich, but the editor does not want to manually duplicate similar blocks across dozens of pages.

Who this template is a good fit for:

• A fashion brand, showroom, clothing designer, or accessories catalog where visual collections matter more than a complex shopping cart.
• A team already using YOOtheme Pro that wants to launch quickly with a ready-made structure of layouts, styles, and demo content.
• An editorial project about style where articles need to connect to products, looks, curated selections, and categories.
• An agency that wants to show a client a polished prototype first and then carefully replace the demo data with real content.

Who Woolberry may not suit without extra work:

• A store that needs full order processing in Joomla immediately after the template is enabled.
• A project with very few images: Woolberry is built around strong visual presentation, and weak media content quickly breaks the effect.
• A site where content managers are not prepared to maintain custom fields, categories, tags, and relationships between items.
• A team that wants to edit template files directly without a child theme or YOOtheme Pro's safer customization mechanisms.

Before installation, decide what you are building: a visual catalog in Joomla, a fashion brand site, or a full online store with orders. Woolberry handles the first two scenarios very well and provides a foundation for the third, but the commerce layer needs to be evaluated separately.

The Demo's Visual Logic: Not Just the Homepage

Woolberry's strength is not a single impressive hero block, but a coordinated page system. The official description highlights ready-made layouts, multiple style variations, and a large image library for the theme. In practice, that means the template should be evaluated as a set of reusable solutions: the header, large imagery, gap-free grids, product cards, hover video, lightbox, sliders, search results, gallery posts, collection pages, and support pages like FAQ or Stores.

If you are bringing Woolberry into an existing Joomla site, do not start with minor edits like changing a button color. First, look at which page types you actually need. For example, a clothing brand usually needs a homepage, collection page, product category, product page, collection article, FAQ, store locations page, and search. If you keep the entire demo structure but fill only two pages, the site will feel unfinished. If you remove too much, you may lose the connections that made Woolberry the right choice in the first place.

Which Demo Blocks Are Worth Keeping as a Foundation

The homepage in the reference demo sets the rhythm: a top header with logo and menu, a large hero for a seasonal collection, two prominent Ready-to-Wear tiles, a latest arrivals block, and then new visual sections. That order works well for a brand with recurring collections: first mood, then entry points into sections, then specific products.

Collection pages benefit from large images and video backgrounds. They communicate not just "what is for sale," but the style, season, color, and mood behind the selection. For a collection article, the connection between text and gallery matters more than a standard Joomla post card. A Woolberry product page is defined by a visual presentation with multiple images, video, and a right-hand information column.

Which Blocks Are Better Removed or Simplified

Not every demo section is needed on every site. If you do not have physical locations, a store map page is unnecessary. If the brand is not hiring, the Careers page can be disabled. If the site is launching first as a catalog, filters, related products, and complex curated selections are better introduced gradually so you do not promise more than the content team can realistically maintain.

Good template setup starts with an editorial plan. Make a list of page types first, and only then decide which layouts to import, which templates to keep, which fields to fill, and where module positions are needed.

What to Check Before Installing on Joomla

YOOtheme Pro can be installed on an existing Joomla site as a template, or you can start with the demo package. Those options solve different problems. Installing the template on an existing site is the right choice if you already have structure, users, menus, content, and working extensions. The demo package is more convenient if you want to see how Woolberry is built internally and use it as a starter kit with demo content.

YOOtheme's official documentation specifically warns that the demo package is a full Joomla installation, not a standard ZIP template for an existing site. That is critical: if you try to install the demo package as an extension, you will waste time and may get lost in the files. For an existing site, you need the YOOtheme Pro template package, while the layout and style can be loaded inside the builder if you have library access.

The Technical Minimum Before First Launch

Check the Joomla version, PHP version, the GD extension, write permissions for the template directories, and the images folder. YOOtheme Pro has system requirements, and file permissions matter for generating style CSS and loading the media library. If the server cannot write to the required directories, some settings may save incorrectly or fail to appear on the front end.

Create a backup before installation and another one after the template is enabled successfully. This is not just a formality. Visual templates often affect menus, modules, article output, fields, and homepage structure. When something "shifts out of place," it is faster to roll back to a checkpoint than to remember which settings were changed in Layout, Style, Templates, and Modules.

The Minimum Content Needed for a Similar Result

Woolberry needs strong imagery. If your product pages are filled with small, compressed photos, hero sections and grids will look worse than the demo, even if the template is installed correctly. Prepare horizontal and vertical images, a consistent photography style, short category names, descriptions, sizes, colors, and relationships between products and articles.

For the Joomla version, custom fields are especially important. The official demo description lists fields for product categories, product type, and posts: images, video, image text color, price, color, size, fit, description, care, features, cross-sell products, excerpt, focal point, galleries, and related products. You do not have to replicate everything exactly, but you do need to understand which fields feed which visual blocks.

Installation and Initial Validation Without Losing the Demo Logic

It is best to split the first launch into two stages: technical installation and visual structure validation. Technically, the Joomla template is installed through the standard extension installer, but YOOtheme Pro adds its own customizer, layout library, style customizer, and its own panels for pages, templates, menus, and modules. That is why after installation it is not enough to set the template as default - you should also open YOOtheme Pro from the Joomla admin panel.

If you are working with an existing site, do not switch every page to the new style at once. Create a copy of the template style, assign it to a test menu item, and check the page in an isolated setup. That approach is especially useful on sites with multiple sections because Joomla allows template styles to be assigned to specific menu items. If the new style breaks only one page, you fix that page locally instead of affecting the whole site.

Basic Sequence

1. Back up the files and the database.
2. Install the YOOtheme Pro template package for Joomla through the standard extension installer.
3. Open System or the Joomla templates section and make sure the template appears in the list of template styles.
4. Create a copy of the style if you do not want to change the whole site right away.
5. Open YOOtheme Pro through the YOOtheme item in the Joomla admin panel.
6. Make sure the left side shows the Layout, Style, Pages, Templates, Menu, Modules, and Settings panels, and that live preview works on the right.
7. Save the initial state without major edits to confirm that the server can write settings properly.

How to Tell the Installation Went Smoothly

Start with the admin side: the customizer opens, the preview is not blank, and when you change a simple setting, the Save and Cancel buttons appear. Then check the public side: the page loads without a white screen, the header is not duplicated, the menu appears where expected, and modules have not disappeared from important areas. After that, switch to different devices using the device preview buttons in the customizer.

If you used the demo package, do not check only the homepage. Open a category page, product page, article, FAQ, and search. If the structure looks correct, then the demo data, fields, templates, and relationships are working together. If the homepage looks like the demo but the inner pages are empty, the issue is usually not the design but the content sources, template assignments, or missing fields.

Post-Installation Setup: Panels, Style, Header, and Responsive Checks

After installation, do not rush to change dozens of parameters. The YOOtheme Pro customizer shows changes in live preview, but several unrelated edits can easily get mixed together. It is better to move from global to specific: site & logo, header, style, pages, templates, modules, settings. That order makes it easier to understand what each setting controls.

The safest way to customize Woolberry is to start with a copy of the template style. In Joomla, open Extensions -> Templates -> Styles, duplicate the YOOtheme style, and assign it to a test menu item. Then make your visual changes inside YOOtheme Pro. If the result does not work, you can restore the old style assignment or delete the copy without touching the live site.

The First Settings Worth Checking

Style Variations and Real Contrast

Woolberry ships with several style variations. The official overview describes a minimal style, sharp edges, fine form styling, outline buttons, a modern sans-serif look, and an accent color, along with additional schemes such as blue, orange, green, red, and darkblue. Do not choose a variation just because the thumbnail looks good. Open the homepage, a product page, a collection page, and the FAQ, then check the contrast over real photography.

For fashion sites, the most common mistake is beautiful light text placed over an image that is also too light. Woolberry includes a field for choosing text color on the image, and that should be used as an editorial tool. If the image is bright, use dark text or add an overlay through section settings. If the background is dynamic, test with several real photos, not just the demo.

Header, Menu, and Mobile View

In the Woolberry reference demo, the header is very clean: logo, section menu, search, and icons. On a real site, it becomes overloaded quickly if you add every category, utility page, and promo link at the top level. With Woolberry, it is better to keep the top level short and move the detailed structure into a dropdown, mega menu, or footer.

Check the mobile header separately. YOOtheme Pro has settings for mobile header, mobile navbar, and dialog/mobile dialog. On a small screen, the goal is not to copy the desktop menu, but to provide fast access to the main sections: new arrivals, women, men, kids, gifts, search, and contact. If the site is multilingual, the language switcher should be tested together with the mobile dialog because it often affects header height.

Settings That Are Better Changed Carefully

Do not change global font sizes, section spacing, container width, navbar behavior, and card styles all at once. In YOOtheme Pro, many parameters are tied to UIkit components and Less variables, so one global change may improve the hero but make the table, form, or product card worse. Work in short iterations: change a parameter, save it, test three page types, and note the result.

If you need to add CSS, use the Settings -> CSS panel or a child theme, not direct edits to the main template files. That way, YOOtheme Pro updates will not overwrite your changes.

Catalog Structure: Fields, Categories, Tags, and Related Products

One of Woolberry's defining traits is that the demo is built around content structure. That is especially important in Joomla: the products and posts in the demo depend on categories, tags, custom fields, and related articles. If you simply create standard articles with an image and text, many of the template's more striking blocks will have no data to display.

The product side of the demo uses fields for images, price, sale price, video, color, sizes, fit, size & fit, short description, composition & care, icons, features, and cross-sell products. Categories use an intro image, hover video, and text color. Posts use excerpt, focal point, galleries, and related products. This is not a required structure for every project, but it shows how YOOtheme Woolberry turns a standard CMS structure into a visual catalog.

How to Plan Fields Without Creating Chaos

Start with entities. For a small catalog, three types are enough: category, product, and article. The category serves as the entry point into a section, the product provides the detailed item page, and the article carries a collection story or editorial content. Then decide which fields you actually need. For example, clothing typically needs color, size, fit, composition, care, images, and related products. Accessories may depend more on material, dimensions, color, collection, and recommendations.

Do not create fields "just in case." Every field should either appear somewhere in the layout or help filter, group, and connect content. If a field is never displayed and does not take part in any logic, editors will stop filling it in, and the template will start receiving empty data.

Dynamic Content in YOOtheme Pro

YOOtheme Pro can insert Joomla data into builder elements. In the element settings, you choose a content source and then map fields to the title, image, text, link, or other parameters. For repeating sources, a single element can duplicate itself based on the data. That is useful for product lists, related content, categories, and curated selections.

If a source or field has been removed, renamed, or is unavailable on the current page, dynamic content becomes invalid. YOOtheme documentation highlights those cases. For Woolberry, that is an important diagnostic clue: an empty card usually does not mean "the template is broken," but "the layout is waiting for a field that does not exist in this category or article."

Related Products and Editorial Content

The official Woolberry description shows the idea of cross-sell products for the single Product page and related products for posts. In the Joomla version, that logic is built through article relationships and custom fields, including the Regular Labs Articles Field used in the demo package. In practical terms, that means an article about a seasonal collection can lead to products, while a product page can point to similar items.

For editors, this is not automatic magic. You need to decide who is responsible for those relationships: the content manager, merchandiser, or administrator. If the relationships are not maintained, blocks like "related products" and "Shop the Looks" will be empty or random. If they are managed carefully, Woolberry becomes more than a beautiful template - it becomes a navigation system between inspiration, the catalog, and specific product pages.

Template Styles, Layouts, and Menu Item Assignment

In Joomla, a template style is not just a decorative option - it is the way you control which set of template settings applies to specific menu items. YOOtheme Pro documentation recommends duplicating the default style and assigning copies to the pages you need. That is especially useful for Woolberry because different sections may need different header behavior, color schemes, or top-block structures.

For example, the homepage may use a transparent header over a hero image, while the FAQ or Size Guide may need a regular light header. A collection page may use more expressive imagery, while utility pages may need a calmer grid and fewer animations. Instead of building manual CSS exceptions, it is better to create a separate template style and assign it to the appropriate menu item.

How Not to Get Lost in Assignments

Give the copies clear names: Woolberry - Home, Woolberry - Catalog, Woolberry - Editorial, Woolberry - Service Pages. Then open the style in Joomla Template Manager and check Menu Assignment. Alternatively, you can open a specific menu item and choose its template style in the parameters. Both approaches work, but it is important to choose one consistent workflow so you are not hunting for settings in two different places.

After assignment, open the page in a browser while logged out and check the actual result. In the customizer preview, you see the page in an editor context, while the public version may differ because of cache, permissions, published modules, or language segment rules.

Layouts from the Library

The YOOtheme Pro layout library allows you to load ready-made layouts, insert them above or below an existing layout, or replace the current layout entirely. For Woolberry, that is convenient if you want to take a ready-made home section, collection block, or page card and adapt it. But loading a layout has to match your content structure. If the layout expects products with images, video, and fields, and your Joomla site has only standard articles, the visual result will be incomplete.

Do not replace a working page with a new layout without making a copy. First save the current layout to the library or work on a test page. Then load the Woolberry layout and check all dynamic mappings. If some sources are red or empty, decide what is easier: create the required fields, change the mapping, or choose a less complex layout.

Loading a Layout and Checking the Result

1. Create a test page or test menu item.
2. Open it in Pages or through preview in YOOtheme Pro.
3. Open Library in the page builder and choose a layout that matches the page type.
4. Select the load mode: replace the layout, insert it above, or insert it below.
5. Check dynamic content mappings, images, and links.
6. Save and open the page as a regular visitor.

Short version: template styles control where a visual settings set is applied, while layouts control the internal page structure. If those layers get mixed together, it becomes much harder to understand why one page looks right and another does not.

Menus, Modules, and Positions: Building Woolberry Navigation

With a Joomla template, you cannot ignore modules. YOOtheme Pro integrates Joomla Module Manager into its customizer and shows module positions, published modules, and their connection to the preview. In Woolberry, that matters for the header, mobile menu, top and bottom areas, sidebar, footer, and builder positions.

The official documentation lists positions such as toolbar-left, toolbar-right, logo, navbar, header, dialog, their mobile equivalents, plus sidebar, top, bottom, and builder-1 through builder-6. Empty positions collapse automatically, so a missing module should not leave a blank hole in the layout. But an incorrect menu assignment can create another problem: the block you need simply will not appear on the page.

Main Menu

In the Woolberry reference demo, the top menu is short: New In, Women, Men, Kids, Gifts, About. That order reflects a catalog well, but on a real site it needs to be adapted. Do not put every page in the header. FAQ, terms, contact, shipping, and returns are better placed in the footer or a secondary navigation area.

If you are using a mega menu, first build a simple Joomla menu item structure and only then enhance the dropdown through the builder. A complex mega menu without a stable category structure quickly turns into a visual block that is difficult to maintain.

Module Positions for Useful Blocks

The top position works well for a promo message or seasonal banner above the system output, bottom works for a newsletter signup, shipping benefits, or extra blocks after the content, and sidebar works for utility pages and the blog. The builder-1 through builder-6 positions are useful when you want to insert a module into a builder layout through the Position element.

For Woolberry, a practical setup might look like this: catalog menu in the navbar, search in the header, newsletter in bottom/footer, shipping terms in the footer, language switcher in the toolbar or dialog, and extra links in the footer. Check desktop first, then mobile. A module that works perfectly in a wide header may overload the mobile dialog.

Menu Assignment and Visibility

In Joomla, a module may be published but still not appear on a page because of menu assignment. This is a common source of problems when migrating a template. If a block is not visible, check not only its position but also its assignment tab. For more complex rules, YOOtheme documentation mentions Advanced Module Manager by Regular Labs as an option for advanced assignment logic, but it should be added only if Joomla's built-in rules are not enough.

After any menu or module change, clear the Joomla cache and the browser cache if they are enabled. Then check the page while logged out of the admin area. That lets you see the result as a regular visitor rather than as an editor with extra permissions.

Practical Example: A Homepage for a Fashion Catalog

Let us walk through a scenario that truly fits Woolberry: building a homepage for a fashion catalog in Joomla. The goal is to preserve the visual character of the demo while replacing the random demo structure with a clear brand storefront: first screen, entry points into sections, latest arrivals, a seasonal collection, benefits, and subscription.

Goal

Create a homepage where the visitor immediately understands the brand style, sees the key categories, can move to new products, and gets quick links to useful sections. For the administrator, it matters that cards and curated selections update through fields, categories, and relationships rather than manual duplication of blocks.

Preparation

• Create or verify the Women, Men, Kids, and seasonal collection categories.
• Prepare images of consistent quality for the hero, categories, and product cards.
• Fill in the product fields: title, images, price, color, size, short description, and related products if used.
• Create a menu item for the homepage and assign the correct template style to it.
• Make sure the customizer opens with live preview of that exact page.

Setup Steps

1. Open the homepage in YOOtheme Pro and load a suitable Woolberry layout from the library, or use the demo page as a starting point.
2. In the hero block, replace the image, the short seasonal label, and the category links. Keep on-site text brief because the visual layer matters more here than a long description.
3. Set up two or three large category tiles. For each one, check the image, link, text color, and behavior on mobile.
4. For the latest arrivals block, use a dynamic content source that outputs the required items or products. Make sure the cards pull the image, title, and price from the fields.
5. Add a seasonal collection block or an editorial block linking to an article if the brand has content around looks and curated selections.
6. At the bottom of the page, place modules for shipping, returns, subscription, and important links. It is better to output them through positions or the footer builder rather than placing them manually on every page.
7. Save the layout, clear cache, and check the page in desktop, tablet, and phone preview.

Validation

Open the homepage as a guest. Make sure the hero is not covered by the header, the category tiles point to the correct pages, the product cards are not empty, images are not stretched, and text over photos remains readable. Then follow every key link: category, product page, article, FAQ, and search. If a user can move through that path without hitting empty pages, the setup can be considered functional.

A Detail That Often Causes Problems

If the latest products block is empty, do not rush to change the layout. First check the content source and fields. The source may be set to a different category, the item may be unpublished, the image field may be empty, or the template may be expecting a related object that does not exist. In YOOtheme Pro, those issues are best traced through dynamic content status and mapping inside the element.

Practical Ways to Use Woolberry on Different Sites

Woolberry can be used more broadly than just a "clothing store." But each use case should stay tied to confirmed capabilities: layouts, style variations, images, video, custom fields, related content, template styles, modules, and dynamic content. Below are a few scenarios that do not rely on invented features and follow the real logic of the template.

A Visual Catalog Without a Complex Cart

If the brand currently sells through physical stores, messaging apps, or an external platform, the Joomla site can function as a catalog. Use product pages as detailed item pages, and point buttons to contact, an inquiry form, or an external channel. The outcome is easy to validate: a visitor should be able to find a category, open a product, see sizes, composition, images, and a clear next step.

An Editorial Magazine with Products Inside Articles

For a content-driven brand, Woolberry makes it possible to connect posts to products. An article about a seasonal collection can include a gallery, the story behind the look, and related products at the bottom. Here, the important part is not the cart but the path from inspiration to curated selection to product page. Make sure related products are filled manually or through a clear source rule.

A Landing Page for a Collection or Capsule Drop

For a collection launch, you can create a separate menu item, assign it a separate template style, and load a layout with a large hero, video, product grid, and FAQ block. That is more practical than reworking the entire site for a single campaign. Once the campaign is over, the style assignment can be disabled while keeping the page as a collection archive.

A Showroom Site with Addresses and Consultations

If sales happen through a showroom, use Woolberry's visual side for the catalog and a dedicated Stores or Location page for addresses. Modules in bottom and footer can display fitting terms, returns, and contact details. Do not check only how attractive the page looks - check whether contact information is easy to reach on mobile.

These scenarios can be combined. The key is not to do everything at once. Start with one user journey and make sure it leads to a clear outcome, then add filters, related products, posts, extra styles, and module blocks.

Result Review: Speed, SEO, Accessibility, and Editorial Stability

After configuring Woolberry, it is important to check more than whether "the design looks good." A template may look impressive, but the real site still needs to load quickly, be indexed correctly, work well on mobile devices, and remain stable when new content is added. It is best to review it in four directions.

Front End and Responsive Behavior

Open the homepage, category page, product page, article, FAQ, and search. Check desktop, tablet, phone portrait, and phone landscape. YOOtheme Pro device preview lets you switch sizes, but the final check should still happen in a browser. Pay attention to the header, mobile dialog, hero height, image cropping, button visibility, and text readability over photos.

SEO Structure

Do not add random headings in the builder just for visual size. The page should have a clear hierarchy, and visual elements should not break the meaning. For product pages and collections, check the title, intro text, links, image alt text, breadcrumbs, and whether the pages are reachable through menus or internal links. Woolberry helps present content, but SEO quality still depends on the Joomla structure, the copy itself, and how you use headings inside the layout.

Speed and Media Content

Woolberry uses a lot of images and video. That is one of its strengths, but it also creates a risk of heavy pages. Upload images at sensible sizes, use on-site optimization, do not embed video where an image is enough, and verify lazy loading. If a few video heroes and sliders make the page heavy, simplify the first screen and move part of the animation lower on the page.

Editorial Stability

Create a test product and a test article with a minimal set of fields. If the layout handles incomplete data without showing empty, unattractive blocks, the structure is stable. If a card falls apart because one image or a related products field is missing, you need to add display conditions, fallback text, or an editorial rule that says "these fields are required."

A working Woolberry site is validated through a user journey, not a screenshot: homepage - category - product page - related content - search - mobile view - edit again.

Safe Enhancements Without Editing the Core Template

After setup, you may want to adapt Woolberry slightly for a specific project: improve caption readability, add a subtle utility note, or fix spacing in one particular block. Do that through YOOtheme Pro settings, a child theme, or custom CSS - not by editing the core template files. YOOtheme Pro documentation for Joomla confirms that custom CSS can be added through Settings -> CSS, and for more durable changes you can use a child theme with css/custom.css and js/custom.js.

A Small CSS Snippet for a Controlled Note

Below is an example of a safe customization. It does not depend on hidden Woolberry classes. You add the CSS class wb-product-note yourself to the required Text or Panel element in the YOOtheme Pro element's Advanced settings, and then add the CSS in Settings -> CSS or in the child theme file templates/yootheme_NAME/css/custom.css.

.wb-product-note {
  max-width: 42rem;
  font-size: 0.95rem;
  line-height: 1.6;
  color: #222;
}

.wb-product-note a {
  text-decoration-thickness: 1px;
  text-underline-offset: 0.18em;
}

The purpose of this snippet is to make an editorial note or explanation next to a product selection more readable without interfering with YOOtheme Pro system classes. Validation is simple: assign the class to one element, save, clear cache, open the page, and make sure only that block changed. Rolling back is just as simple - remove the class from the element or delete the CSS.

When a Child Theme Is the Better Option

If the change is needed for one project and includes only CSS or a small amount of JS, a child theme is more practical than direct template edits. If the customization needs to move between client sites, YOOtheme recommends considering a starter plugin. For a typical Woolberry site, a child theme, template style, and customizer settings are usually enough.

Do not edit the main YOOtheme Pro files for a minor visual adjustment. A template update may overwrite the changes, and troubleshooting becomes harder. External CSS, an element class, and a child theme give you control and a clean rollback path.

Why Woolberry May Not Look Like the Demo and How to Fix It

Problems with a Joomla template often look like "the design is broken," while the real cause sits in another layer: a field is missing, a module is not assigned to a menu item, the template style is applied in the wrong place, cache is showing an old version, the user lacks permissions, or the layout is expecting data from the demo structure. Below is a practical troubleshooting guide specifically for Woolberry and YOOtheme Pro.

The Homepage Is Empty or Looks Very Different from the Reference

Symptom: the header is there, but below it Joomla outputs a regular article or an empty block instead of a complex page. A likely cause is that the required layout was not loaded, the page is opened through the wrong menu item, the template style is assigned to a different menu item, or the page builder layout was not saved.

Check which menu item is set as the homepage, which template style is attached to it, and whether the same menu item is open in the YOOtheme Pro preview. Then open Pages and make sure the layout is actually assigned to the current page. If you worked with the demo package, compare the structure to the demo. If you worked with an existing site, check whether old article content is being displayed instead of the builder layout.

Product Cards Are Empty or Missing Images

Symptom: the grid is there, but the cards have no photos, price, or description. The cause is often dynamic content mapping: the layout is expecting the Images, Price, or another field, but in your Joomla site that field was never created, was left empty, or uses a different name. The item may also be unpublished or placed in a different category.

Open the grid or panel slider element and check the content source and field mapping. If the source is red or the field is missing, either create the required field or remap it to an existing one. Do not hide the problem with CSS: an empty source needs to be fixed at the data level.

A Module Does Not Appear in the Required Area

Symptom: the module is published, but it does not appear on the page. Check the position, status, access level, language, and menu assignment. In the YOOtheme Pro Modules panel, you can see positions and modules, but final behavior still depends on Joomla. If the module should appear on only one page, make sure it is assigned to the exact menu item the visitor is opening.

Nothing Changed After Editing the Style

Symptom: you changed a color or font, clicked Save, but the public site still shows the old appearance. Check the Joomla cache, browser cache, system cache, CDN, and also which template style is assigned to the page. Sometimes the setting is saved in one copy of the template style while visitors are seeing another one.

The Mobile Menu Became Too Long

Symptom: on a phone, the menu fills the screen and gets in the way of search or important links. The cause is that the desktop structure was copied into the mobile dialog without simplifying it. Split the navigation: keep the core categories in the mobile navbar/dialog, move utility pages to the footer, and output extra links through a separate module.

Video and Sliders Hurt Performance

Symptom: the first screen loads slowly, especially on mobile internet. Check image weight, the number of videos, lazy loading, autoplay, and the position of heavy blocks. For the first screen, one strong image is often enough. Video, hover effects, and extra sliders are better placed lower on the page where they do not delay the first impression.

When It Is Better to Roll Back a Setting

Roll back a change if it breaks several page types, makes the mobile header worse, reduces text contrast, or causes dynamic content to display empty blocks. For a template style, it is enough to restore the old menu item assignment. For CSS, remove the class or the snippet. For a layout, reload the saved copy from the library or restore the backup.

Official Woolberry Video Walkthrough and What to Watch For

YOOtheme has a dedicated presentation video for Woolberry. It is useful not as a substitute for setup, but as visual confirmation of the template's logic: which page layouts are included, how the product index, categories, product page, blog templates, live search, product filters, mega menu, video, lightbox, and style variations are built. For the Joomla version, watch it as an overview of the visual and structural concept, not as a tutorial for enabling a full shopping cart in Joomla.

When watching, keep your site plan next to you. Note which pages you will actually use: home, category, product, post, FAQ, search, stores. Separately, write down which blocks require content discipline: images, video, fields, related products, categories, tags, and text over photos.

When YOOtheme Woolberry Is the Right Choice

YOOtheme Woolberry is worth using if you need a visually strong Joomla template for fashion, with ready-made page layouts, style variations, demo structure, dynamic content, and the ability to manage pages through YOOtheme Pro. It is especially effective when the site should be more than a storefront - when it needs to function as a connected system of collections, product pages, editorial stories, search, FAQ, stores, related products, and polished transitions between sections.

Before launch, make sure the team is ready to maintain the content structure: images, fields, categories, tags, relationships, and module assignments. If all of that is in place, the template will provide a fast start and a clear visual language. If not, it is better to simplify the structure, start smaller, or choose a more neutral foundation.

Once the backup, test template style, content fields, images, and page plan are ready, you can download YOOtheme Woolberry, deploy it in a safe environment, and validate it against this guide. Do not publish the site right after the first attractive screen: walk through the site as a visitor, editor, and administrator first, then move the result to the live page.