JoomShaper Wimble - Joomla Template

JoomShaper Wimble Setup Guide for a Joomla Agency Website

JoomShaper Wimble is best viewed not as just another polished skin, but as a ready-made foundation for an agency website, consulting firm, studio, expert team, or portfolio-driven business. In this guide, we will look at how to approach installation safely, how quickstart differs from the standard template package, which settings to review after your first login to the admin panel, and how to avoid losing important demo blocks when adapting the template for a real project.

This guide does not repeat the short product description from the listing. The practical side matters more here: where to change the logo and menu, how Helix Ultimate, SP Page Builder Pro, module positions, and Wimble pages work together, why demo images may differ from what you expect, how to check responsiveness, and what to do if some modules or buttons do not appear on the site.

We will start with preparation and installation, then build a practical homepage workflow for an agency site, configure the menu and the Contact Us block, review the portfolio and case studies, add a safe CSS tweak, and finish with troubleshooting. This order helps you do more than just enable the template - it helps you build a controlled website that can be updated and maintained over time.

What this template is built to do

Wimble is designed for websites that need to present a company's expertise quickly: services, workflow, portfolio, case studies, team, blog, and contact path. The official template page specifically highlights three homepage variants: consulting business, interactive agency, and portfolio. That matters because setup should begin not with button colors, but with choosing the right demo logic for your project.

If you are building a consulting website, the homepage should guide visitors from a clear value promise to services, numbers, methodology, case studies, and an inquiry. If the project is closer to a studio or agency, a strong visual hero, portfolio, interactive transitions, and a quick path to discussing the project tend to work better. If the site is centered around completed work, it makes more sense to lead with portfolio and case studies, while presenting services as an explanation of what the team actually does.

The main value of Wimble is not any single page, but the set of ready-made business sections working together. The template includes internal layouts for team, services, blog, case studies, portfolio, and questions. In practice, this reduces the risk of ending up with a site that has one striking first screen and empty inner pages.

When Wimble is a good fit

This template makes sense when the site owner wants to start from a ready-made structure and then replace the demo content with their own text, images, and sections. It is especially useful for projects where the design needs to feel modern, but the administrator does not want to build a template from scratch or spend a long time assembling pages from separate extensions.

• An agency website that needs services, portfolio, case studies, and a contact form.
• A consulting team site where methodology, trust, metrics, and expert pages matter.
• A corporate showcase for a small company that needs a blog and several ready-made inner page layouts.
• A web studio project where the client needs to review a demo, approve the structure, and gradually replace the content.

When another approach may be better

Wimble may be too much if you need an ultra-minimal blog, a catalog with hundreds of products, a complex user dashboard, or a site with unusual data logic. The template creates a strong presentation layer, but it does not replace a specialized component for eCommerce, directories, bookings, or a private client portal. In those cases, Wimble can still work as the public-facing front end, but the business logic will need to be built with separate extensions.

Before installation, define one primary goal for the website: generate leads, showcase a portfolio, explain services, or support an expert blog. That decision affects which home variant should be your starting point and which demo sections should be removed first.

What to check before installation

Preparation matters more for a Joomla template than it does for a small extension. The Wimble quickstart package includes not only the template itself, but also a ready-made Joomla demo build with components, modules, Helix Ultimate settings, and SP Page Builder pages. The standard template pack works differently: it adds the visual layer, but it does not automatically bring over demo content, modules, and pages.

First, decide where you will test the template. For quickstart, it is best to use a clean environment: a subdomain, temporary directory, or separate local setup. Installing quickstart over an existing Joomla site through the extension manager is not appropriate, because quickstart is installed as a full website. For an existing site, the standard template package is usually the right choice, followed by manual creation of the needed pages, module positions, and menus.

Pre-installation checklist

• Check the official product page to confirm that the current template version supports your Joomla branch and PHP version.
• Verify your hosting limits for upload_max_filesize, memory_limit, max_execution_time, and cURL availability, because quickstart is heavier than a standard template zip.
• Prepare a separate database or a separate table prefix for the test installation.
• Create a backup of the existing site if you plan to test the template anywhere other than a clean domain.
• Gather your own photos, logos, service copy, and social profile links ahead of time, because some demo images may be replaced with placeholders.
• Decide who will edit the pages: a Joomla administrator, a content manager working in SP Page Builder, or a developer using Helix and CSS.

Quickstart or the standard template pack

The difference between these two packages defines the entire workflow that follows. Quickstart is for when you want a demo site that looks close to what the developer showcases, and then gradually replace the content. The template pack is for an existing site where you only need the template layer. In that case, the demo pages, modules, positions, and menu relationships will have to be recreated manually.

The short version is simple: if you want a fast start with a ready-made page structure, test quickstart separately. If the site is already live and contains important data, do not try to merge quickstart into it like a regular extension.

Installation and initial verification without unnecessary risk

For a new project, the easiest path is to install quickstart on a test environment and confirm that the site loads, the demo pages are accessible, the menu works, and the admin panel shows no critical warnings. After that, you can decide whether to move the structure to the main domain or turn the staging site into the future production site.

If you are using the standard template package, the process is closer to a normal Joomla extension installation: upload the zip, enable the template, assign the style to the required menu items, and create or reassign modules. But do not expect ready-made Services, Portfolio, or Case Study pages to appear automatically. The developer clearly separates the standalone template from quickstart: the standard template controls the presentation layer, not the entire demo site.

Quickstart workflow

1. Extract the quickstart archive locally and upload the files to a clean site directory or subdomain.
2. Create a separate database and user with the required permissions.
3. Open the domain in your browser and run the Joomla installer as you would for a normal CMS installation.
4. Do not use admin as the main administrator username; choose a unique login instead.
5. After installation is complete, remove the installation directory, sign in to /administrator, and review the system information.
6. Check folder permissions under System - System Information - Folder Permissions.
7. Open the public site in both a regular browser window and a private window.

Template pack workflow

1. Back up the site and database.
2. Install the package through System - Extensions - Install.
3. Open System - Site Template Styles and assign the Wimble style to the required menu items.
4. Check whether the extensions your layout depends on are installed: SP Page Builder Pro, Helix Ultimate, and the portfolio component if you are using a portfolio section.
5. Create or reassign modules to the positions used by the layout.
6. Open each important page and compare it to the demo logic: hero, menu, bottom section, content area, side positions, and contact form.

Your first verification should happen before you start editing the design. If you change CSS, menus, and modules immediately, it becomes much harder to tell whether a problem came from the installation or from your own edits.

The settings map after your first login

After installation, do not rush into rewriting every page. First, you need to understand where Joomla ends, where Helix Ultimate begins, and where a specific page is edited through SP Page Builder. In Wimble, these layers work together: Joomla handles menu items, categories, articles, modules, and permissions; Helix controls the template style, positions, menu behavior, header, footer, custom code, and responsiveness; SP Page Builder handles the visual page sections.

A practical order is this: first template style and brand identity, then menu and positions, then the homepage, then inner pages. If you work in reverse, it is easy to end up with a polished section that is attached to the wrong menu item, cannot see the required module, or breaks on mobile.

Template Styles and core brand identity

Open System - Site Template Styles - the Wimble style - Template Options. The interface may look slightly different across versions, but the logic stays the same: start with base parameters, then move through layout, menu, typography, blog, custom code, and similar groups. Do not change every tab at once. Start with the logo, favicon, container width, base colors, and header behavior.

If the site is multilingual, do not limit yourself to a single style. In Joomla, you can use separate template styles for different menu items or languages. That is useful when the Russian and English versions need different logos, contact buttons, or menu sets.

Menu, mega menu, and off-canvas navigation

Wimble uses prominent top navigation: the reference layout shows numbered items, dropdown menus, and a separate Contact Us button. In Helix Ultimate, the menu is controlled not only through the Joomla menu manager, but also through the Menu section in the template settings. That is where you review menu structure, mega menu behavior, dropdown logic, and the mobile off-canvas navigation.

On desktop, make sure the items do not wrap to a second line or clash with the button. On mobile, make sure the correct menu module appears in off-canvas, the items expand properly, and the nesting depth remains understandable. If an item is created as a Menu Heading or Separator, mobile menu expansion can behave differently. For a simple navigation node, a regular link or an item using # is often the safer choice when it fits the site structure.

Modules and positions

Template positions define where blocks appear when they are not part of a specific SP Page Builder page. These can include the menu, footer, sidebar, contact block, additional off-canvas elements, and modules placed above or below the main component. Wimble documentation specifically mentions the Content Top and Content Bottom positions, which can be used above and below the component area even if they are not always visible in the layout builder.

If a module does not appear, do not assume the template is broken. Check four things: position, publication status, menu assignment, and module language. For article pages, also review Helix blog settings: in some cases, whether side modules appear in single article view depends on the Disable Modules parameter.

SP Page Builder and section editing

The homepage, services pages, case studies, and other presentation-heavy sections are easier to edit in SP Page Builder. In quickstart, it is already connected to the demo pages, so duplicate the page or create a backup before you start changing text and images. For clients, it is better to leave a clear set of editable pages and avoid giving access to every global template setting if the task is only content replacement.

A good practice is to replace the text and images first, then review the grid, and only after that change animations, spacing, and colors. That makes it easier to see whether the design can handle real content rather than short demo phrases.

Homepage, portfolio, and case studies: what to adapt first

Wimble's visual style is built on strong contrast: a dark first screen, white typography, a gradient accent, large blocks, cards, and transitions between dark and light sections. It is easy to ruin that character by simply swapping photos while leaving the demo structure in place without any real meaning. That is why homepage customization should follow content logic first.

Hero and the first promise

The first screen should answer what the company does and why the visitor should keep going. In the demo visual, there is a large heading, supporting text, slide-based logic, and a prominent contact button. When replacing the copy, do not try to fit the whole company story into this area. Keep a short promise, one clearly defined audience, and one action: view services, explore case studies, or send an inquiry.

If the hero uses a background photo, check the contrast. White text over a dark image works well only if the image is dark enough. If your photo is lighter than the demo, add an overlay through the SP Page Builder section settings or choose a different image. Do not try to solve this with tiny text or excessive copy.

Services and cards

The demo includes a Services block with cards and arrows. For a real site, do not copy labels like Business Strategy without adapting them. Each card should lead to a clearly defined service: audit, strategy, design, development, support, marketing, implementation, training. If a service is complex, the card should lead to a dedicated page with a description, process, outcome, and contact form.

Case Study and Portfolio

On an agency site, portfolio and case studies play different roles. Portfolio answers the question "what have you done," while Case Study explains "how did you think through it and what path did you take." The official Wimble listing emphasizes the portfolio listing, project details, and the use of the SP Simple Portfolio component for portfolio scenarios. That means setup should focus not only on the visual grid, but also on the card structure: categories, images, descriptions, links, sorting order, and the detail page.

If the company does not yet have a large portfolio, do not leave an empty section in place. It is better to create two or three strong case studies with a detailed explanation of the task, process, and result than to show a grid of random images. For a young studio, you can replace part of the portfolio with a "how we work" section and "typical project types," but do not present demo work as if it were real.

Team, blog, and FAQ

Team, Blog, and FAQ pages should only be enabled when you have actual content for them. The Team section helps when people are genuinely important for trust. A blog is useful if you are ready to publish expert content regularly. FAQ makes sense when visitors keep asking the same questions about timelines, workflow, briefs, support, and outcomes.

In practice, the most common failure with templates like this is leaving every demo section enabled. The site looks large, but visitors see empty copy and repetitive images. It is better to keep fewer sections and make them honest and verifiable.

Configuring the menu, the Contact Us button, and the footer blocks

In Wimble, navigation is part of the template's identity. The top menu in the reference design shows numbered items, dropdown arrows, and a separate outlined Contact Us button. Wimble documentation explains two important details: menu numbers can be hidden with CSS, and the Contact Us button is implemented as an SP Page Builder module in the menu position. Different modules may be used for the homepage and inner pages.

How to edit Contact Us

If you need to change the text, link, or style of the contact button, do not look only at the menu item. Check Content - Site Modules or the modules section in your Joomla version, filter by the menu position, and find the SP Page Builder Module. Open it, go to the Button addon, and change the text, link, color, border, or display conditions.

After saving, open both the homepage and an inner page. If the button changes only on one of them, there is probably a second module assigned to other menu items. That is not an error - it is a way to keep different header states for different parts of the site.

How to remove menu numbers

If numbered menu items do not fit your brand, you can hide them with a small CSS tweak. Wimble documentation provides a selector for the nav-counter element. Add the code in Templates - Wimble - Template Options - Custom Code - Custom CSS or in a separate custom.css file if your team already uses a file-based customization workflow.

#sp-menu span.nav-counter {
  display: none !important;
}

The check is simple: refresh the public site, clear the Joomla cache and browser cache, then compare the desktop and mobile menu. Rollback is simple too: remove the CSS tweak or comment it out. Do not edit the core template files, because those changes may be lost during updates.

The footer area and repeated blocks

In templates like this, the bottom section is often built from modules and SP Page Builder sections. Before editing it, determine whether it is a global module shown across all pages or part of a specific page. If the block appears everywhere, it is usually better to edit it once as a module. If it belongs only on the homepage, keep it inside that page so the same call to action does not clutter the inner sections.

Review module assignment to menu items after every major edit. In Joomla, a block can be published and still remain invisible if it is not assigned to the current menu item, the wrong language is selected, or the position does not exist in the active style.

How to turn the demo structure into working content

After the first successful launch, the most dangerous stage begins: the demo already looks convincing, and it becomes tempting to swap a couple of headings, the logo, and the phone number and call it done. For a template like Wimble, that is not enough. Its strength comes from the way its pages and recurring patterns work together: the hero sets the promise, Services explains the direction of the business, Case Study provides proof, Portfolio shows visual outcomes, Team and Blog build trust, and Contact turns interest into an inquiry.

If you replace only the homepage text but leave the old inner pages untouched, the site will feel fragmented. A visitor may see one service on a card, another in the menu, and a third in a case study, without understanding what the company actually offers. That is why the demo structure should be adapted as an editorial pass, not just a technical block replacement.

Start with a page map, then write the copy

Create a simple map: which menu items stay, which sections lead to dedicated pages, where the contact form will live, what blog topics are needed, and which case studies can be shown publicly. Then decide what to remove. For a small agency, a reasonable starting structure may be shorter than the demo: homepage, services, two or three case studies, team, FAQ, and contact. The blog can remain hidden until there is a real editorial plan.

Do not be afraid to reduce the demo. A ready-made template shows what is possible, not the amount of content you are required to publish. If a section does not help visitors make a decision, it is better to disable it than to publish an empty page filled with generic copy.

How to replace images without losing the style

Wimble uses high-contrast photography, dark surfaces, and bright accent elements. When replacing images, it is important not only to choose the right size, but also to preserve the overall mood. If you put a very light image in the hero, the white headline will lose contrast. If you use unrelated visuals in the service cards, the clean grid will start to feel noisy. Prepare one consistent image set: similar processing style, similar color temperature, consistent cropping logic, and enough empty space for text overlays.

For case studies, use images that show the result of the work or the actual process, not a random office stock shot. For services, abstract but recognizable visual markers often work better: audit, design, development, strategy, support. If you do not have original photography, use only legal stock assets or graphics that are licensed for commercial use. Demo shots from the preview should not be moved to the live site unless you have confirmed usage rights.

How not to break internal links

After replacing the demo content, go through every link manually. A service card should lead to the service page, the hero button to the next key step, the case study to its detail page, and the bottom CTA to a contact page or form. In SP Page Builder, links may live inside a Button addon, Image addon, card block, or custom HTML. In Joomla menus, links are managed separately. Check both layers.

The main sign that the site is ready is an uninterrupted visitor path. If a user reads the hero, opens a service, reviews a case study, and clicks contact, they should never land on a demo page, an empty anchor, or an outdated link. It may sound minor, but those gaps are exactly what most often reveal an unfinished template setup.

Portfolio, case studies, and SP Simple Portfolio

The official Wimble listing notes that the portfolio listing and project detail pages are tied to SP Simple Portfolio. For the end user, that means the portfolio is not necessarily a standard Joomla article or an SP Page Builder section. Before editing, determine where each project is actually stored: in the portfolio component, a Page Builder page, an article, or a module.

For an agency, it is better to think in three layers of proof. The first is a short card in the listing that helps visitors quickly understand the type of work. The second is a detailed case study page with the task, approach, and result. The third is a related call to action where the visitor can order a similar service or discuss a project. If you leave only a gallery of images, the portfolio may look attractive but remain weak as a sales argument.

Categories and filters

If you use portfolio categories, do not create too many filters at the start. Three clear categories usually work better than ten empty ones. For example: Strategy, Design, Development or Branding, Websites, Support. In the Russian version, you can display reader-friendly names, but keep the internal category structure tidy so the editor clearly understands where each new project belongs.

After changing categories, open the public listing and confirm that the filters do not lead to empty results. If a category contains only one weak item, it is usually better to merge it temporarily into a broader group. An empty filter looks like a mistake even when the component is technically working correctly.

Case study page

A strong case study in Wimble can follow a simple pattern: the client's task, the constraints, what the team did, which site or service blocks were involved, and what result can be shown. You do not need to reveal confidential numbers if they cannot be published. It is enough to explain the context and provide visual proof.

A practical check: open the case study detail page on a phone and see whether the heading, image, summary, and next step are visible without excessive scrolling. If visitors see only an oversized image and do not understand what to do next, reduce the first block or bring the CTA higher.

Multilingual setup and editor roles

Joomla is often chosen for projects that need multiple languages, separate user groups, and controlled editing. Wimble does not change that logic. If the site will be multilingual, decide in advance which elements are translated through Joomla language overrides, which use separate menus and modules, and which are embedded inside SP Page Builder pages.

Menus and modules by language

Each language usually needs its own menu items, menu modules, and sometimes its own template styles. If the contact button in the menu position exists as a separate SP Page Builder Module, check its language assignment. Otherwise, the Russian version may show an English CTA or vice versa. The same applies to the off-canvas menu: on a multilingual site, it is safer to explicitly assign the correct menu module to each language.

Access permissions

Not every editor needs access to Template Options. A content manager usually only needs pages, articles, media, and possibly a few specific modules. Helix settings, custom code, positions, and global styles are better left to an administrator or developer. That reduces the risk of someone accidentally hiding a position, changing the global font, or inserting broken JavaScript.

Before handing the site over to a client, create a test editor role and walk through typical tasks: change service copy, replace a case study image, update the FAQ, create a blog post, and review the public page. If a simple task requires the editor to jump through five different areas, prepare a short internal guide tailored specifically to your site.

Practical workflow: building an agency homepage

Now let's apply the template to a concrete task. Suppose you need to prepare a website for a small digital studio: showcase design, development, strategy, three case studies, the team, and a contact form. The goal is to end up with a working homepage, not to endlessly polish the demo.

Goal

Create a homepage where visitors understand within the first few minutes what the studio does, see the service directions, can open case studies, and can quickly move to contact. The Wimble visual style stays intact: a dark first screen, bright accent, large headings, clean cards, and a clear progression from problem to result.

Preparation

• Quickstart is installed on a staging site, or the template pack is assigned to a separate test menu item.
• SP Page Builder is available in the admin panel for page editing.
• The logo, three to five photos or illustrations, a service list, short case study summaries, and a contact link are ready.
• A backup of the page has been created, or a duplicate exists so you can return to the original demo.

Steps

1. Open the homepage in SP Page Builder and replace the hero heading with a specific promise for the studio.
2. Keep one primary call to action: open case studies or get in touch. A second CTA can remain secondary if it does not compete with the first.
3. In the Services block, keep three or four services that are actually offered, and link each card to a dedicated page or form.
4. In the Case Study section, replace demo cards with real projects or honest descriptions of typical engagements if the case studies cannot yet be disclosed publicly.
5. In Portfolio, review the categories and images. If SP Simple Portfolio is used, configure categories so visitors do not see empty filters.
6. Check the Contact Us button in the menu position and replace the link with the contact page, form, or anchor.
7. Open Template Options and review the logo, favicon, mobile logo, off-canvas menu, and footer area.
8. Open the site in a private window to confirm that the SP Page Builder edit button is not visible to a regular visitor.

Result check

Test three visitor paths. First: go from the homepage to a service and then back to contact. Second: open a case study, understand the task, and see the next step. Third: visit from a mobile device, open the off-canvas menu, and get to the form. If any of those paths breaks, the setup is not finished yet.

A common detail that gets in the way

An administrator may see the edit button on the public side, while a regular visitor does not. If you are signed in as a Super User or another role with SP Page Builder editing rights, do not evaluate the public-facing experience only from that session. Check it in private mode or under a non-editing role.

Practical ways to use Wimble in different projects

The same template can be configured very differently if you use its proven strengths: ready-made home variants, services, case studies, portfolio, blog, FAQ, Helix navigation, and visual page editing. The examples below are not an abstract list of niches, but practical structures you can build without inventing new features.

Consulting firm

Use the home variant that emphasizes methodology, metrics, services, and team. The hero should lead to an audit or consultation, the How we work block should explain the stages, and Case Study should show how the company solves client problems. Result check: in one clear flow, the visitor should be able to find a service, see proof of expertise, and understand how to get in touch.

Creative or digital studio

For a studio, portfolio, visual rhythm, and a quick path to project discussions matter more. Keep a bold hero, display a few service cards, make Portfolio the main proof point, and use the blog for expert breakdowns. If you do not have many case studies yet, make each project page more substantial: task, approach, visual solution, result, and the team's role.

Corporate showcase site

For a company selling not a single service but trust and credibility, pages like About, Team, FAQ, and Blog are often more useful. The homepage should be calmer: a short positioning statement, business directions, key numbers, team, and contact. Portfolio can be replaced with implementation case studies or client examples if real project work cannot be shown.

A starter agency site with room to grow

If the project needs to launch quickly, do not enable every demo page at once. Launch the homepage, services, two or three case studies, FAQ, and contact first. Add the blog and an expanded portfolio later, once the content exists. Wimble is strong because it gives you a ready-made section rhythm, but it does not force you to publish every block immediately.

Responsiveness, performance, and safe refinements

Wimble relies on Helix Ultimate and SP Page Builder, so part of the responsive behavior comes from the layout, part from section and addon settings, and part from CSS. Do not start with code if the issue can be solved through column settings, spacing, font size, or device visibility controls.

Responsiveness

Helix layouts use a grid-based system in which rows and columns adapt to screen width. Column settings let you define sizes for different devices and hide blocks for specific breakpoints. It is important to understand that hiding a block through responsive settings usually applies a CSS rule rather than removing it from the HTML. So do not rely on hidden heavy blocks as a performance strategy. If a block is unnecessary for mobile visitors, consider replacing it with a lighter section instead.

Performance

The template itself does not guarantee a fast site. Performance depends on images, fonts, animations, the number of SP Page Builder sections, third-party widgets, caching, and hosting. Start with the basics: optimize your images, do not upload oversized photos into cards, review whether every video and animation is truly needed, enable Joomla's built-in cache, and test the site in multiple browsers. For the final assessment, use external performance tools, but do not chase a score if it breaks the visual experience.

A safe CSS tweak for article headings

Wimble documentation includes examples for reducing heading sizes in blog and single article views. Below is a careful option for situations where long Russian headings appear too large on inner pages. This is a CSS-only tweak, so it does not touch PHP and can be rolled back easily.

.view-article .article-header h1 {
  font-weight: 700;
  font-size: 38px;
  line-height: 1.22;
}

@media only screen and (max-width: 820px) {
  .view-article .article-header h1 {
    font-size: 30px;
    line-height: 1.25;
  }
}

Insert the code into Template Options - Custom Code - Custom CSS or into your custom.css. After saving, open an article with a long heading, check both desktop and mobile view, and clear the cache. To roll it back, remove this snippet. If you already manage typography through Helix, try the built-in settings first and keep CSS as a targeted override.

Custom code without unnecessary risk

Helix Ultimate lets you add CSS, JavaScript, meta tags, and tracking code through the Custom Code section. Use that capability carefully. In the CSS field, add CSS only, not PHP. If analytics code or an iframe breaks, check whether a security extension or editor filter is modifying it. Do not blindly disable protection on a live site: test on a copy first and save the original snippet.

Troubleshooting common issues after setup

Joomla template issues often look similar: "a block is missing," "the change did not save," "the demo does not match the screenshot," or "the mobile menu behaves strangely." But the causes are different. Below are the issues most typical for the combination of Joomla, Wimble, Helix Ultimate, SP Page Builder, and quickstart.

Quickstart will not install through the extension manager

Symptom: you try to upload quickstart like a normal extension, but the installation fails or Joomla reports a package error.

The reason is that quickstart is a full demo site build, not a regular template zip. It includes Joomla, demo data, the template, extensions, and configuration. It must be installed as a new site on a clean environment.

What to check and how to fix it

• Make sure you use quickstart only for a new installation.
• For an existing site, use the template pack and configure modules, menus, and pages manually.
• If the installation stalls, check server limits and folder permissions.
• If the site already contains data, do not continue testing on the live domain without a backup.

The photos from the demo are missing after installation

Symptom: the structure looks similar to the demo, but placeholder images or different visuals appear instead of the original photos.

This is expected for many templates: demo photography may be excluded from the package due to image licensing restrictions. For a real site, it is better to use your own photos, licensed stock assets, or client-provided graphics right away. Do not try to recover the original demo images at any cost if you do not have usage rights.

A module is published but does not appear

Symptom: the module is enabled, the position is selected, but nothing shows on the page.

Check the position, menu assignment, language, access level, and active template style. For some Helix positions, the layout must actually include the required area. If this involves a sidebar in single article view, check the Helix blog settings, because module output in detail view may be disabled there.

The Contact Us button does not change

Symptom: you edit the menu item or the page text, but the header button stays the same.

In Wimble, that button is tied to an SP Page Builder Module in the menu position. Find the module in the module list, open the Button addon, and change the text or link there. If the homepage and inner pages use different modules, update both.

SP Page Builder shows the wrong result or does not save changes

Symptom: the editor opens, but the preview differs from the public page, the change is not visible after saving, or some tools do not work.

Start with safe checks: clear the Joomla cache and browser cache, verify user permissions, open the page in another browser, and temporarily disable conflicting third-party addons on a test copy. If the issue appeared after an SP Page Builder, Helix, or Joomla update, review the changelog and the developer forum before adding CSS or JavaScript workarounds.

The mobile menu does not expand nested items

Symptom: items are visible in the off-canvas menu, but nested levels do not expand or the arrow is missing.

Check the menu item types in the Joomla menu. Some utility types such as Menu Heading and Separator may have limitations in mobile navigation. Also verify that the correct menu is selected for off-canvas, that the required menu modules are published, and that language assignments are not hiding them.

Custom code does not apply or breaks the embed

Symptom: CSS does not take effect, an iframe or tracking code changes after saving, or JavaScript behaves inconsistently.

Check which field you are using for the code. CSS belongs in Custom CSS, while meta tags and external snippets belong in the fields around <head> or <body>, and PHP cannot be placed there. If a security extension filters the embed, test the change on a site copy and do not disable filtering unless you fully understand the consequences.

When JoomShaper Wimble is the right choice

Wimble is worth using when you need more than an empty Joomla base and want a ready-made visual framework for an agency or corporate team: homepage, services, case studies, portfolio, blog, FAQ, menus, and manageable content sections. It is especially useful when the project can begin with quickstart on a staging environment, then replace the demo content, and carefully move the structure into a production site.

If you expect the template to solve content, performance, SEO, and business-logic issues on its own, the result will be weaker. Wimble gives you structure and a visual system, but site quality still depends on your copy, images, visitor paths, mobile checks, and update discipline.

Before launch, walk through one short checklist: the homepage loads quickly, the menu works on desktop and mobile, services lead to meaningful pages, case studies are not empty, the contact button points where it should, and regular visitors do not see editor interface elements. After that check, you can proceed to download JoomShaper Wimble and test it in your own workflow without turning the live site into a sandbox.