JoomShaper Velvet - Joomla Template

Guide to Setting Up JoomShaper Velvet for a Joomla Fashion Store

JoomShaper Velvet is best viewed not as a typical visual template, but as a ready-made foundation for a Joomla store: it brings together the storefront design, catalog pages, product detail pages, blog content, menus, module positions, and EasyStore integration. In this guide, we will walk through how to approach the installation, what to check before launch, where to edit the home page, how to fine-tune the storefront without overcomplicating it, and how to tell when the result is actually ready for testing.

This guide is written for a site owner, webmaster, or editor who already has the template archive and wants to turn the demo into a working project. It does not repeat the product card or general marketing claims. Instead, it gives you a practical roadmap: quickstart or installation on an existing site, Helix Ultimate settings, SP Page Builder pages, EasyStore products and categories, module positions, responsive checks, common issue diagnosis, and comparable alternatives.

Special attention is paid to the things that often break the impression in fashion store templates: borrowed demo photos, unprepared categories, unassigned modules, weak product pages, cache conflicts with the visual editor, and unclear mobile navigation. The main goal of setup is not just to install the template, but to build a verifiable chain: a demo page, real products, a clear menu, a working cart, and predictable results on the public-facing site.

What Velvet Actually Provides and Where Its Responsibility Ends

Velvet is built for a fashion store: clothing, accessories, capsule collections, seasonal edits, small brands, and visually driven catalogs. According to JoomShaper's official materials, the template uses Helix Ultimate, SP Page Builder Pro, and EasyStore. That matters because most of the work after installation does not happen in a single section, but across three layers.

The first layer is the template and its styling. It controls the overall framework: the header, navigation, module positions, grid, spacing, typography, responsive behavior, and the overall rhythm of the pages. The second layer is SP Page Builder pages. This is where you typically edit the home page, promo blocks, collection sections, visual storytelling areas, and some store pages. The third layer is EasyStore. It handles products, categories, the storefront, the product page, the cart, checkout settings, and part of the store logic.

The practical takeaway is straightforward: if the text in the hero block is wrong, look for the page in SP Page Builder; if a product is missing from the catalog, check EasyStore; if a module appears in the wrong place, review the positions and menu assignments; if the entire header behaves badly on mobile, start with the Helix and menu settings. The same front-end screen can be assembled from several Joomla systems, so troubleshooting should always follow the layers.

Who This Template Fits Best

Velvet is especially useful when a project needs a ready-made visual stage for a fashion brand, but the team does not want to build every page from scratch. It works well for a small to mid-sized store where large photography, refined typography, collection sections, product cards, a style blog, and clean navigation matter more than a heavy, overloaded interface.

The template is also useful for an agency that needs to spin up a demo quickly for a client, show multiple home page directions, and then replace the demo content with real products. Quickstart is especially convenient for that workflow because it installs as a complete site with preconfigured extensions and demo pages.

Who Should Consider a Different Approach

Velvet may be more than you need if you already have a large, active store with deep order integrations, nonstandard shipping services, complex buyer roles, and critical checkout customizations. In that case, the template should be tested on a copy of the site rather than installed over the live project. It also does not solve inventory management, legal documents, payment gateways, or business workflows by itself - those parts still depend on EasyStore, Joomla, and additional extensions.

If your goal is simply to change the header color on an existing Joomla site, Velvet may be too much. If your goal is to build a visually cohesive fashion storefront with a catalog, product pages, and ready-made layouts, then the template is much closer to the right tool.

What to Check Before Installation: Server, Site, and Demo Content

Before installation, do not start by unpacking the archive into the site root. First decide which scenario you actually need: a new site based on quickstart, or installing the template on an existing Joomla site. These are different paths. JoomShaper's documentation clearly states that quickstart includes the Joomla core and is installed as a new site, not through the extension manager of an existing installation.

For a clean quickstart deployment, check your hosting environment: PHP 8 family support, sufficient memory limit, upload size, execution time, MySQL or MariaDB, and enabled cURL and OpenSSL. You do not need to memorize exact numbers here - they change and should always be verified against the developer's documentation - but the logic stays the same: a quickstart archive is larger than a regular template package, and installing demo data requires more resources than enabling a small extension.

Quickstart Pre-Launch Checklist

• Prepare a separate database, or at least a separate table prefix if you are working in a test environment.
• Check that the root folder does not contain an old configuration.php file that could pull in someone else's settings.
• Make sure there is no extra index.html in the root if it interferes with the Joomla installer.
• Keep access to your file manager or SFTP until the installation is finished, because you may need to remove temporary files and check .htaccess afterward.
• Do not use an obvious Super User name such as admin; it is a basic but important security measure.
• Decide up front which demo photos will be replaced with real brand images, because some demo images may not be included in the package.

For an existing site, the logic is different. Before installing the standalone template package, create a backup of both files and database, check extension compatibility, disable aggressive optimization during setup, and create a test menu item. That lets you assign the new template style only to a test page instead of changing the entire site at once.

Why Demo Photos Should Not Be Treated as Production Content

A fashion store template depends heavily on visuals. But demo photos are usually there to showcase the design, not for commercial reuse. In its template documentation, JoomShaper explains that demo images may be replaced with placeholders because of licensing restrictions. This is especially important for Velvet: the large hero, product cards, and collection sections only look convincing with your own brand photography.

Prepare at least three visual sets: wide hero images, square or vertical product shots, and images for collections and blog content. If you do not yet have your own photography, it is better to use properly licensed stock images temporarily than to leave gray placeholders in place. Checking the demo photos is one of the first signs that the site is ready not just for a client preview, but for real content work.

Installation: Quickstart, Standalone Template Package, and Initial Validation

The fastest way to get something close to the demo look is quickstart. It deploys a Joomla site with the template, components, and demo data. This is a good path for a new project, a demo environment, a store prototype, or moving the design into a separate staging setup. But quickstart cannot be installed over an active site through System or Extensions, because it is not a standard template installation package.

If the site already exists, install the template package and related extensions separately. After installation, open System, then the site templates section, find the Velvet style, and assign it to a test menu item first. This lets you check the header, footer, module positions, and key pages without the risk of suddenly changing the entire live site.

How to Tell Whether Quickstart Installed Correctly

1. Open the front end and confirm that the home page loads with a recognizable Velvet structure: top promo bar, minimal header, large fashion hero, collection blocks, and product cards.
2. Log in to the admin panel at /administrator and verify that Components, SP Page Builder Pro, and EasyStore are available.
3. Open the SP Page Builder page list and find the page assigned as Home in the main menu.
4. Check that EasyStore products and categories are published rather than hidden or left as drafts.
5. Switch to a mobile viewport in the browser and see whether the header, menu, or product grid breaks.

After this check, do not rush into changing everything at once. First create a copy of the home page in SP Page Builder or save the current configuration. That gives you a simple rollback if your first experiment with sections or spacing ruins the composition.

Initial Setup on an Existing Site

On a live site, the safest route is to work through a test path. Create a hidden menu item, assign the Velvet style to it, and place one SP Page Builder page and one set of modules there. This approach shows how the template behaves with real content, while leaving the home page, catalog, and SEO structure untouched until you are confident in the result.

If caching, CSS combining, or JavaScript optimization are active during setup, temporarily disable them or exclude the test page. Otherwise, you may edit SP Page Builder, click Save, and still see the old version on the front end. That is not a Velvet template issue; it is a typical problem on a cached Joomla site.

Checkpoint Before Moving It to the Main Menu Item

Before assigning Velvet to the actual main home page, save a list of the changes you made: which template style was used, which SP Page Builder page was assigned, which modules were published, and which EasyStore categories appear in the blocks. This is not bureaucracy; it is a fast rollback method. If a module disappears after the switch, the header changes, or a product block becomes empty, you will immediately see the difference between the test page and the working page.

Do not switch the entire site to the template in one move if you have not yet tested at least one store page, one product page, and one utility page. For an eCommerce project, a beautiful home page is not enough: a shopper needs to reach the product and cart without friction, and the administrator needs to understand which layer controls each visible block.

Home Page: How to Keep Velvet's Mood While Replacing the Demo with Your Brand

In the documentation, Velvet's home page is described as clean and restrained, and the provided visual reference clearly reflects that: white space, a thin header, large fashion photography, expressive serif typography in the hero, a logo block, and then a product collection. This is not a template built around heavy animation and multiple colorful banners. Its strength lies in pauses, proportions, and large imagery.

You edit the home page through SP Page Builder Pro. In the admin panel, open Components, then SP Page Builder Pro, then Pages, and choose the page assigned in the Main Menu as Home. Depending on the builder version, some tasks are easier in the admin editor, while spacing and section-level visual tuning may be easier in the front-end editor.

What to Change First

Start with the content that directly affects trust in the store. In the hero block, replace the headline, subheading, call to action, and photo. Then review the featured collections block: the cards should link either to EasyStore categories or to prepared collection pages. After that, replace the demo partner logos, if any, with real brands, publications, or remove the block entirely if it does not support trust.

Do not change the typography, grid, background, spacing, and section order all at once. Velvet is built on minimal visual contrast, so rough font replacements or random spacing reductions can quickly turn a refined store into a cramped catalog. Work in iterations: one section, one change, one mobile-width check.

What to Keep from the Original Rhythm

• A large visual first screen, because it sets the brand tone before the visitor even browses the catalog.
• Open white space around blocks, because otherwise the premium fashion rhythm disappears.
• A small number of accent buttons, so the user does not lose the main path into the store.
• Product cards with a clear price, title, and quick visual distinction between items.
• A blog or stories section, if the brand sells not only products, but also style, curated edits, or seasonal advice.

A quick post-edit check for the home page: within a few seconds, the visitor should understand what the brand sells, where to go to shop, and how the current collection differs from a generic list of items.

How Not to Break the Minimalist Style

Velvet has a restrained visual logic: large photos, a limited amount of text, black-and-white contrast, visible serif typography in promo areas, and a calm product grid. If you replace that with dense banners, tiny product cards, and several multicolored buttons, the template may still technically be Velvet, but its strongest quality will be gone. It is better to add one convincing collection story than five identical promo blocks.

A useful technique is to keep a list of "what was removed from the demo." If you removed the logo block, blog, promo strip, or the second collection section, write down why. That helps you avoid leaving visual gaps or bringing back an unnecessary block just because it looked good in the demo. Configuring a visual template is about editing the meaning of the page, not just swapping images.

Template Styles, Helix Layout Builder, and Module Positions

For a Joomla template, the key work often does not happen inside the page text, but in the template style. In Joomla, a template style lets you assign different visual variants to different menu items. That is useful when the home page needs to be visually wide and promo-driven, while the catalog, blog, or utility pages should feel calmer and more readable.

Velvet is built on Helix Ultimate, and Helix documentation describes Layout Builder as the tool for configuring rows, columns, module positions, and responsive behavior. This is especially important for Velvet: the header, off-canvas menu, pre-component blocks, footer, promo strip, and additional positions must not only be published, but also assigned to the correct menu items.

How to Work with Positions Without Creating Chaos

Open the template style and find the layout settings. First document the current positions, then decide which modules should be global and which should appear only on specific pages. In Joomla, a module can be published but still not visible if it is assigned to the wrong menu item, uses the wrong access level, or sits in a position that the current template style does not render.

A practical pattern for Velvet looks like this: the header and primary navigation are global; the promo strip with a discount or service message is global but easy to disable; collection blocks appear only on the home page; filters and categories appear only on store pages; blog modules appear only on article pages. The more precisely modules are assigned by menu item, the fewer random blocks will show up on checkout, product pages, and utility pages.

Settings Worth Checking After Installation

Do not begin by adding new positions if you have not yet understood the existing ones. Helix lets you create and modify positions, but for an initial Velvet setup it is usually more important to assign the built-in areas carefully. New positions make sense only when you have a specific need: for example, placing a seasonal banner between the hero and the collections, or showing a narrow informational module only on the catalog page.

How to Verify Positions Without Guessing

In Joomla, it is useful to enable module position preview and open the page with the ?tp=1 parameter, if that is allowed in the template settings. This shows you the real output areas on the page rather than abstract names from the admin panel. After checking, it is best to disable the mode so visitors do not see the technical grid. This method is especially useful when a module is published in the admin area but seems "lost" on the front end.

If the position exists but the module still does not appear, move on to menu assignment. In Joomla, the same module can be shown on all pages, on no pages, only on selected menu items, or on all except selected ones. So the issue is often resolved not in Helix, but in the module's own assignment tab. For Velvet, this is critical on store pages: extra promo modules should not accidentally appear in the cart or checkout.

EasyStore Inside Velvet: Products, Categories, and Store Pages

Velvet relies on EasyStore as its commerce layer. That means the template's visual polish does not replace a proper product structure. If categories are poorly planned, products have no images, discounts are applied randomly, and checkout has not been tested, a beautiful hero will not save the store. Start your EasyStore setup with a minimal working model: categories, a few test products, a product page, a cart, and checkout.

Categories in EasyStore are created through Components, EasyStore, Categories. The documentation describes the title, alias, description, status, parent category, and category image. For a fashion store, that is not just formality. The category name should make sense to the shopper: not Collection 01, but "Dresses," "Suits," "Accessories," "New Collection," or another piece of real brand language.

Product Page: What to Fill In Before Visual Polishing

When adding a product, EasyStore provides fields for the title, alias, description, images, price, discount, tax settings, status, category, featured flag, inventory, SKU, tags, weight, dimensions, and SEO fields. Not every store needs every field, but the basic product page should be complete enough for Velvet to present the item convincingly.

• The product title should distinguish one model from neighboring cards, not repeat the same generic word.
• Images should have consistent visual quality and similar proportions, otherwise the collection grid will look random.
• The category should be assigned before you test the storefront, or the product may not appear in the correct block.
• Publication status and availability should match the actual test scenario.
• It is worth filling in SEO fields for key products, but without assuming that a template alone will improve rankings.

After creating products, check how they display inside SP Page Builder blocks. EasyStore documentation shows that categories can be rendered on SP Page Builder pages through the corresponding addon. This is convenient in Velvet for the home page: you can show curated selections, seasonal categories, or specific product groups without turning the first screen into a full catalog.

Checkout and Utility Pages

The checkout area in EasyStore is configured separately. The documentation lists settings for guest checkout, guest information storage, address fields, phone number, taxes, coupons, and legal information. A template guide does not need to spell out payment flows in detail, but it does need to verify that Velvet does not visually break the utility pages of the store.

Create a test product, add it to the cart, proceed to checkout, and review the fields on desktop and mobile widths. If a promo module, blog block, or large banner appears on checkout, go back to module menu assignments. The checkout page should feel calm and functional, not compete with the home page for attention.

Minimum Data Set for a Test Product

A test product should not be an empty placeholder. Give it a real title, one primary image, a category, a price, publication status, an SKU or another internal identifier, a short description, and at least one attribute. That way, testing shows not only that the page exists, but also how Velvet handles real text, image proportions, and extra data. If you test the template with a product that has no image or description, you may miss problems that will surface with real content.

Also check both a discounted product and a regular product with no discount. The Velvet reference shows neat discount labels on product cards, so it is important to make sure those elements do not break the grid or cover the image. If the discount styling looks noisy, first look for the setting in EasyStore or in the SP Page Builder block instead of jumping straight to template file edits.

Practical Scenario: Build a Home Storefront for a New Collection

Suppose you need to prepare a home page quickly for the launch of a capsule clothing collection. You have a few photos, five to ten products, a short brand message, and the goal of guiding visitors into the catalog. This is a typical Velvet use case: the template already sets the mood, and your job is to replace the demo content and connect the home page to real EasyStore products.

Goal

Create a home page where the visitor sees the new collection, understands the brand style, can move into the product category, and open a product page without unnecessary steps. The result should feel cohesive on both desktop and mobile.

Preparation

• The template has been installed through quickstart or assigned to a test template style.
• Collection categories have been created in EasyStore, and test products are published.
• The products have images, a price, publication status, and clear titles.
• The home page assigned in the main menu is available in SP Page Builder.
• Joomla cache and external optimization are disabled during active setup or cleared after each change.

Setup Steps

1. Open Components, SP Page Builder Pro, Pages, and select the Home page.
2. Replace the hero headline and photo with content for the new collection. Keep the composition large and avoid adding multiple competing buttons.
3. In the collection block, set the EasyStore categories or links to pages that display the right products.
4. Review the product cards: title, image, price, discount, and Featured state if the block displays featured products.
5. Keep the menu path short: Home, Shop, Categories, Blog, with utility pages placed in a dropdown.
6. Save the page, clear cache, open the front end in a private window, and test the path from the hero to the product.

Verifying the Result

The check should be user-centered, not purely administrative. Open the site like a normal shopper: click the hero button, go to the category, open a product, add it to the cart, return to the home page, and make sure the mobile menu does not cover important elements. If the user gets lost between the collection and the product, the problem is not the template's "beauty," but the connection between the menu, categories, and content blocks.

A Common Detail That Gets in the Way

The most common trap is editing a visual block on the home page and forgetting that it may be displaying EasyStore data or a linked page rather than manually entered cards. In that case, everything on the home page may look correct, but the link leads to an empty category, the product is hidden, the product page is unpublished, or the module is assigned to the wrong menu item. Check not only the block, but also the data source behind it.

How to Present the Result to a Client or Team

After setting up the collection, create a short internal note: which categories are used in the block, which products are marked as featured, where the hero is edited, and which images must not be removed from the media manager. This is especially useful if the site will later be maintained by a content manager. Without that note, teams often change a product in EasyStore but do not understand why it did not appear on the home page, or they edit the hero in the wrong page copy.

For final approval, do not show a static screenshot - show the path: home page, category, product, cart, return to the menu. This kind of walkthrough reveals weak points much faster: a product title that is too long, a weak photo, an extra module on checkout, or an unclear menu item. A practical example is only complete when it can be repeated step by step and verified on the public-facing site.

Practical Ways to Use Velvet Without Inventing Features It Does Not Have

Velvet is not limited to a single "products in a grid" storefront. It can support several real-world scenarios as long as you stay within its confirmed capabilities: SP Page Builder pages, EasyStore, categories, product pages, blog content, modules, and template styles. Below are a few ideas that can be implemented through standard Joomla layers and the extensions already present in the template ecosystem.

Capsule Collection with a Short Purchase Path

Create a separate EasyStore category, add the collection products, place the block on the home page through SP Page Builder, and keep one primary button that takes visitors into the category. This works well for a seasonal launch, a limited edit, or a new accessories line. The check is simple: every product in the block should open correctly, be published, and lead to a working cart.

Brand Storefront with a Style Blog

If the store sells not only products but also a visual identity, use blog pages for content like "how to wear it," "the story behind the collection," or "fabric care." You can feature a few articles on the home page to support trust, but do not overload it with long text. Make sure blog modules do not appear on checkout and do not interfere with product pages.

Catalog Without Aggressive Selling

For brands that accept inquiries manually or want to showcase inventory before fully launching sales, Velvet can be configured as a visual catalog. EasyStore still helps structure products and categories, but some commerce actions can be introduced gradually depending on the store's readiness. This should be phrased carefully: the exact mode depends on your EasyStore configuration and the capabilities you have installed.

Multilingual Storefront

Joomla works well for multilingual sites, but the template does not translate content by itself. For Velvet, that means separate preparation of menus, SP Page Builder pages, categories, products, and text strings. Do not begin by translating the whole site at once. Start with one test language version of the home page, one category, and one product page. That makes it much easier to see which text comes from the builder, which from EasyStore, and which from Joomla language files.

Promo Landing Page for a Limited Sale

Velvet's top promo bar and large hero are a good fit for a short campaign, but that campaign should stay manageable. Create a separate page or section in SP Page Builder, show only the relevant EasyStore category, limit the number of products, and verify that the block can be disabled quickly once the campaign ends. Do not tie a temporary promotion to global elements if it needs to disappear without rebuilding the entire header.

The check here is straightforward: once the section is disabled, the site should not be left with broken links, empty categories, or promo text in the menu. If the campaign affects discount labels, also test products without discounts so the layout does not depend on a single product state.

Safe Improvements: CSS, Localization, and a Clean Rollback

In a store template, small adjustments almost always come up: making product cards more even, refining labels, hiding an extra block on mobile, translating an interface string, or fixing spacing. The key rule is not to edit the Joomla core, extension files, or template files directly if the same task can be solved through settings, custom CSS, a language override, or a page copy.

For a small visual adjustment, use your own section class in SP Page Builder. For example, add vf-product-grid-check as the class for a product block, then place the CSS in a safe location for custom styles in the template style or builder. This kind of snippet does not depend on Velvet's internal classes and is easy to disable by removing one class or one CSS block.

.vf-product-grid-check .sppb-addon {
  min-height: 100%;
}

.vf-product-grid-check img {
  object-fit: cover;
}

.vf-product-grid-check a:focus-visible {
  outline: 2px solid #111111;
  outline-offset: 3px;
}

This adjustment does not change store logic. It helps visually align the block and improve keyboard focus styling, if your specific block uses images and links inside the section. Check the result on a collection page and then on mobile width. If something looks wrong, remove the vf-product-grid-check class from the section or delete the CSS itself. That kind of rollback is much safer than editing template files.

Localization Without Editing Files

If you need to replace a system label, look first for Joomla's built-in language override mechanism or the component's own settings. Do not edit extension language files directly: an update may restore the old text. This is especially relevant in Velvet at the boundary between the template, SP Page Builder, and EasyStore, because a visible phrase may belong not to the template, but to the store component.

When You Should Not Add Code

Do not add JavaScript to change the cart, checkout, or pricing unless you fully understand which component controls that behavior. In a store, such edits are risky: they can break checkout, field validation, or mobile behavior. If you need a nonstandard commerce workflow, it is better to look for a documented EasyStore method or a dedicated extension than to inject a random script.

The same rule applies to editing PHP files in the template. If you need to change the output structure, first check whether the task can be solved through the template style, a module, a language override, an SP Page Builder setting, or a Joomla override created according to CMS conventions. Direct edits to product files are often lost during updates and make maintenance harder. A safe customization should have a clear insertion point, a way to verify the result, and an obvious rollback path.

Validating the Result: Front End, Mobile View, Speed, and SEO

Once the template is configured, review the result as a visitor, an editor, and an administrator. The visitor cares about appearance, navigation, and how understandable the purchase path is. The editor checks how easy it is to replace a block, a product, or a piece of text. The administrator evaluates where the settings live, whether changes can be rolled back, and whether the team has created unnecessary dependencies.

Visitor Path

1. Open the home page in a private window.
2. Follow the main button into the catalog or a category.
3. Open a product and check the images, title, price, availability, and description.
4. Add the product to the cart and proceed to checkout.
5. Return to the home page and confirm that the menu, footer, and utility links behave consistently and predictably.

Editor Path

The editor should understand where to edit the home page, where to edit a product, where to edit a category, and where to hide a module. If those tasks have to be hunted down in random places, create a short internal reference: Home is edited in SP Page Builder, products and categories in EasyStore, the header and positions in the template style, and module visibility in the module settings and menu assignment.

Speed and SEO Without Overpromising

No template can guarantee better search rankings on its own. For Velvet, it is more reasonable to talk about a solid technical foundation: clean structure, a responsive layout, properly sized images, clear headings, completed product meta fields, and no extra blocks on utility pages. Compress images to a sensible size, do not upload massive hero images unless they are truly needed, and make sure product cards have unique descriptions.

If you enable caching, file combining, or optimization, do it after the main setup and then test SP Page Builder, EasyStore, the cart, and the mobile menu. First establish a working path, then optimize it. Otherwise, it becomes difficult to tell what actually broke: the template settings, the cache, minification, or the store data.

What to Record After the Final Check

Save a short technical sheet: the active template style, the SP Page Builder home page, the main EasyStore categories, the list of modules in the header and footer, enabled optimizations, the location of custom CSS, and who is responsible for images. This helps not only with maintenance, but also with updates. If product cards change after an update or a module disappears, you will be able to compare the current state with the original map instead of relying on memory.

For a small store, this sheet may only take a few lines, but it can save hours of troubleshooting. It is especially useful when the site is handed off from the developer to the brand owner or editor. Velvet remains a practical tool only when the team understands which parts of the site are edited in Joomla, which in SP Page Builder, and which in EasyStore.

If Velvet Does Not Look Like the Demo: Symptom-Based Troubleshooting

Troubleshooting works best when you start from the visible symptom rather than the vague idea that "the template is not working." Velvet has multiple layers, so the same front-end issue can have different causes. Below is a practical map to start with.

The Home Page Opens but Does Not Resemble the Demo

Symptom: the structure is different, the expected sections are missing, buttons lead to the wrong places, or product cards are empty. Possible causes: the standalone template package was installed instead of quickstart, the home page is not assigned in the main menu, the wrong SP Page Builder page is being used, demo images were replaced with placeholders, or EasyStore data is unpublished.

What to check: the Home menu item, the SP Page Builder page list, product and category publication, and the presence of real images. Fix: assign the correct page, verify the category connections, and replace demo content. If the site is already active, do not try to recreate the demo over the live site - use a test copy.

A Module Is Published but Not Visible on the Page

Symptom: the module is enabled in the admin area but does not appear on the front end. Possible causes: the position is not rendered by the current template style, the module is assigned to the wrong menu item, the access level does not match the user, or cache is showing the old state.

What to check: the module position, the menu assignment tab, access, the selected template style, and cache clearing. Fix: assign the module to the correct menu item, use a position that actually exists in the layout, or create a test position through Helix only after checking the existing ones.

Product Cards Do Not Appear in a Collection Block

Symptom: the block exists on the home page, but the products are empty or incorrect. Possible causes: the product is unpublished, no category is assigned, the SP Page Builder block points to a different category, the image is missing, or the filter is set to show only featured products.

What to check: the product status, category, Featured state, addon settings, and cache. Fix: publish the product, assign the category, and verify the block's data source. If the block was copied from the demo, pay especially close attention to where it pulls products from.

After Saving Changes, the Old Version Is Still Visible

Symptom: everything is saved in the editor, but the front end does not change. Possible causes: Joomla cache, hosting cache, browser cache, a CSS/JS optimizer, or a CDN. What to check: a private window, clearing Joomla cache, and temporarily disabling the external optimizer during setup. Fix: first confirm that the data was actually saved in SP Page Builder or EasyStore, then clear caches one by one.

The Mobile Menu or Product Grid Breaks

Symptom: the header wraps, product cards become too narrow, the cart button overlaps text, or the off-canvas menu feels awkward. Possible causes: menu items are too long, extra modules are placed in the header, layout breakpoints are wrong, or heavy images were added without responsive preparation.

What to check: menu length, header settings, off-canvas position, column grid, and image sizes. Fix: simplify the menu, move secondary links into a dropdown item, review Helix responsive settings, and do not try to solve everything by shrinking the font.

When JoomShaper Velvet Is the Right Choice

Velvet is worth using if you need a Joomla template for a fashion store with a strong visual home page, ready-made layouts, an SP Page Builder, Helix Ultimate, and EasyStore stack, and a clear path from demo to a working storefront. It works especially well where products are sold through mood and styling: clothing, accessories, seasonal edits, visual collections, and brand storytelling.

Before launch, check the server requirements, choose the correct installation method, replace the demo photos, set up categories and products, assign modules by menu item, and test the mobile header, cart, and checkout. After that, you can download the ZIP archive or open the archive from the product page and deploy it in a test environment.

A good setup outcome is not an exact copy of the demo, but a working store where Velvet's style supports the brand, products are easy to find, the user journey does not break, and the administrator knows where each layer of the site is managed. Once that path has been confirmed on a test page, the template can be moved closer to real launch.