JoomShaper Crafty - Joomla Template

How to Set Up and Use JoomShaper Crafty for a Joomla Workshop Website

JoomShaper Crafty is a Joomla template for a craft workshop website, a ceramics studio, a small handmade goods shop, or any project that needs to combine a storefront, brand story, educational content, and online sales. This guide is not a promotional overview of the template. Instead, it walks through the practical workflow: what to check before installation, how to launch the demo site safely, where to edit the homepage, how to connect the EasyStore storefront with your content, and what to do if modules, styles, or images do not appear after setup.

This material is written for site owners, Joomla administrators, and developers who receive the template and need to turn it into a working project quickly. We will focus on practical JoomShaper Crafty setup: QuickStart, Helix Ultimate, SP Page Builder, EasyStore, module positions, menus, shop pages, workshops, result checks, and the limitations you should understand before launch.

Exact versions, update dates, and technical details are documented in the source and notes files. The article itself intentionally avoids dates because what matters more to the user is the order of operations, the logic behind each check, and a clear understanding of which template elements control the look of the site.

What Crafty Does Better Than a Typical Multipurpose Template

Crafty is best viewed not as an empty shell with an attractive header, but as a ready-made composition for a niche website. The original visual reference makes it clear that the template is built around a calm palette, large photography, a smooth section rhythm, product cards, and soft typography. This is not a generic corporate design where the user has to invent the entire personality of the site from scratch. The atmosphere of a craft workshop is already there: ceramics, natural materials, product cards, a workshop block, a blog, and pages for core information.

The real advantage of a template like this shows up when a project needs to communicate three things at once, quickly: who makes the products, what is available to buy, and which classes or events can be booked. A standard Joomla template often gives you only a header, footer, and a few module positions. Crafty adds ready-made pages and EasyStore integration, so the administrator does not have to build the storefront, product page, blog, and contact pages from the ground up.

But that strength has a downside. The more distinctive the demo design is, the more carefully you need to replace its content. If you leave in someone else's photos, placeholder product names, and demo copy, the site will look like an unfinished mockup. If you swap out all the images too aggressively without respecting the proportions, the template's calm visual rhythm will break. That is why setting up Crafty is not just about installing an archive. It also means carefully adapting the demo blocks to real products, the actual workshop, a real schedule, and real text.

What Kinds of Tasks the Template Covers

Based on the official product page and documentation, Crafty is aimed at crafts, art, ceramics, sculpture, and similar creative niches. In practice, it works well for the following tasks:

• Launching a workshop website with a homepage that includes a strong visual hero section, product blocks, a story about the maker, and links into a collection.
• Building an EasyStore product shop with cards, categories, search, filtering, and product pages.
• Showcasing workshops, class schedules, or bookings through a dedicated page and form.
• Running a blog about the process, materials, product care, and collection stories.
• Quickly preparing supporting pages such as FAQ, terms, and contacts without designing them from scratch.

If your project needs a strict B2B catalog, a complex user account area, multi-vendor marketplace logic, or an unusual ordering flow, Crafty may serve only as a visual base. In that case, you will need to design the extensions, access rights, order flow, and data structure separately. The template helps present a craft-focused website, but it does not replace proper technical planning for a more complex service.

Who JoomShaper Crafty Fits, and When It Makes More Sense to Start Elsewhere

Before installing it, it is worth deciding whether Crafty's logic actually matches your task. That saves time: if the template fits your scenario, you will adapt ready-made blocks; if it does not, you will end up fighting someone else's structure. This matters especially for a craft site, where visual style and content strategy are tied together more closely than in a standard corporate template.

Good Use Cases for Crafty

Crafty is a strong choice when the project already has visual assets: photos of products, the workshop, the process, packaging, people, or the interior. The template is designed for large images and for calm, deliberate presentation of physical objects. If the image quality is weak, the site will lose impact quickly, even if the installation itself is correct.

The second strong use case is a shop with a limited assortment where the story behind each product matters. EasyStore provides the foundation for products, options, orders, shipping, and payments, while the template pages help present the product not as a dry catalog row, but as part of a workshop story. For ceramics, jewelry, home decor, courses, and creator-led collections, that is a natural fit.

The third use case is a site where the shop and educational content work together. For example, a workshop sells finished products and also runs classes. In that case, Crafty makes it possible to keep both directions on one site: the homepage can lead visitors to the storefront, workshop pages, the blog, and contacts.

When the Template May Not Be the Right Fit

Crafty may be too much if the site needs to feel as neutral as possible, technical, or corporate. Its visual identity is fairly pronounced: large artistic photography, a craft-inspired palette, and soft product cards. You can reshape a template like that heavily, but at that point, the reason for choosing Crafty in the first place starts to disappear.

You should also be cautious with projects that need extensive product filtering, complex logistics, integrations with an external warehouse, or multiple seller types. EasyStore covers a standard storefront and core shop operations, but complex commerce always requires a separate review of extensions, integrations, and the actual user journey.

The main check before choosing it: if you can replace the demo products, photos, and text with your own material without changing the overall composition, Crafty will most likely fit. If you need to rework almost every section and the entire page logic, a more neutral framework or another template is usually the better option.

What to Check Before Installation: Server, Joomla, Archive, and Content

Preparation matters more with a Joomla template than it may seem. Errors at this stage often look like "the template does not work," when the real cause is PHP limits, the wrong installation method, caching, missing extensions, or a weak set of source content. With Crafty, you also need to account for its connection to Helix Ultimate, SP Page Builder, and EasyStore, since the demo site depends on several components and modules.

Environment Check

The official Crafty documentation notes that JoomShaper products need the usual Joomla, PHP, and MySQL requirements to be in place, along with upload limits, memory, execution time, and cURL availability. You do not need to expose those values to site visitors, but the administrator should verify them in the hosting panel ahead of time. If the upload limit is too low, a large installation package may fail to upload. If the execution time is too short, QuickStart or a demo import may stop before it finishes.

Minimum Technical Readiness

A practical verification sequence looks like this:

1. Open the Joomla admin panel and review the system information available for your permission level.
2. Compare Joomla and JoomShaper requirements against your hosting settings.
3. Make sure the extension installer can upload archives of the required size.
4. Confirm that the site runs over HTTPS and that you have a backup before installation.
5. On a staging environment, enable module position preview in advance if you plan to move or verify blocks.

If the site is already live, do not install QuickStart over an existing Joomla site. QuickStart is meant to bring up a separate installation with demo data. On an existing site, you would normally use the template package and manually create the pages, modules, and content you actually need.

Content Preparation

Crafty is built around visual trust. So before installation, it is worth preparing not just the technical environment, but also the content itself: collection photos, product names, short material descriptions, prices or price ranges, workshop copy, class terms, contacts, and baseline FAQ answers. Without that information, the demo pages may look filled in, but the site will still be a draft in practice.

Also check image usage rights separately. JoomShaper's template documentation often includes an important note: photos from the live demo may not be included in the package and may be replaced with placeholders. That is normal because of licensing. So do not plan your launch around someone else's demo photography. It is better to gather your own images in advance and adapt them to the proportions of the key blocks.

QuickStart or the Template Package: Which Route to Choose

JoomShaper templates usually support two practical scenarios. The first is QuickStart, which is a ready-to-run Joomla installation with demo content, components, modules, and settings that reproduce the demo. The second is the standalone template package, which installs into an existing site and controls only the visual layer and template parameters. For Crafty, that choice is fundamental.

When to Choose QuickStart

QuickStart is convenient if you are starting a new site and want a structure that matches the demo as closely as possible: homepage, menu, shop, workshop pages, blog, FAQ, contacts, and a set of modules. This route works well both for learning and for rapid prototyping. You can see how the developer connected SP Page Builder, EasyStore, menus, and module positions, then gradually replace the demo content.

Practical Check After Installing the Demo

But QuickStart requires a clean environment and a separate database. It should not be installed inside an existing site that already contains content, orders, or users. In practice, teams often do this: first launch QuickStart on a subdomain or local copy, study the structure, identify the needed modules and pages, and then transfer only the settings they actually understand to the main site.

When to Use the Template Package

The template package is the better choice if Joomla is already running and you need to change the design or add Crafty as the foundation for a new section. In that setup, you will not automatically get the entire demo store and page set. You will need to configure menus, modules, components, and SP Page Builder pages separately. The advantage is that you are not putting the existing site structure at risk.

If the site already has a catalog, a blog, users, and an SEO structure, the template package is usually the safer route. First install the template, create or copy a template style, assign it to a test menu item, check the front end, and only then expand its use gradually. This gives you a clean rollback path: remove the menu assignment or restore the previous default template.

Short version: QuickStart is useful as a learning and starting route, while the template package is the more controlled way to roll Crafty into a live site. Do not mix those scenarios without a backup plan.

Initial Setup After Installation: Menu, Template Style, and Homepage

After installing Crafty, do not rush into changing colors and fonts. First make sure the site is actually displaying the correct template, the menu points to the intended homepage, and the page you want to edit is really built in SP Page Builder. The Crafty documentation notes that the QuickStart homepage is created in SP Page Builder Pro and assigned through the Home item in the main menu. That is an important clue: if you are editing a standard Joomla article and do not see any changes on the homepage, you may be modifying the wrong object.

Initial Verification Sequence

Your first changes should be small and easy to reverse, because at this stage you are testing not the design, but the connection between the menu, the page, the template, and cache.

1. Open the public site and confirm that the Crafty style is loading, not the default Joomla template.
2. In the admin panel, check the menu: the main item should lead to the page responsible for the home screen.
3. Go to Components - SP Page Builder Pro - Pages and find the page connected to the homepage.
4. Open that page in the editor and make one small, safe change, such as temporarily editing draft text in a low-visibility block.
5. Save, clear the Joomla and browser cache, and then check the public page.

This confirms the whole chain: the menu points to the right object, SP Page Builder saves changes, the template renders the page, and cache is not hiding the result. If that chain breaks, all further setup becomes guesswork.

What to Configure in the Template Style

Crafty is built on Helix Ultimate, so part of the global setup happens not inside each page, but in the template settings: header, logo, menu, base typography, footer, custom CSS, layout, and positions. In Joomla, those parameters are usually available under System - Site Template Styles, then the selected template style and its Template Options.

For a typical workshop site, the first pass should cover:

• The logo and site name, so no demo branding remains in the header.
• The main menu, item order, and any unnecessary demo pages.
• The footer, attribution lines, contact details, and links to utility pages.
• Color accents, if the brand already has an approved palette.
• Custom CSS, if you need a small change without editing template files.

Do not start with heavy layout rewrites. First preserve a working baseline, then make targeted changes and check the public page after each pass. The best way to preserve Crafty's demo logic is to change one layer at a time: first menus and pages, then content, then modules, then styles.

Crafty's Homepage: How to Preserve the Demo Rhythm While Replacing It With Your Own Content

Crafty's homepage is one of the main reasons to choose this template. The reference design shows a large first section with a photo of the maker and a product, a product card layered over the visual, a vertical scroll block, then a section about the workshop, product cards, and the storefront. This is not a pile of random blocks. The rhythm builds trust: first atmosphere, then the person or workshop behind it, then the products and the path to purchase.

When replacing the content, it is important not to break that order. If you swap the calm photo for a busy banner, replace short cards with long text, and use images with inconsistent proportions for the products, the template will keep its technical structure but lose its mood. That is why the homepage is best edited as a refinement of an existing composition.

How to Replace the Hero Section

The first screen should quickly explain what the site is selling or presenting. For a workshop, that might be a new collection, a seasonal set of products, a class, or a brand story. In SP Page Builder, find the section that controls the hero area and check three elements: the image, the short text, and the product card or collection link.

A practical approach:

1. Prepare one strong horizontal image featuring a person, a product, or the making process.
2. Replace the demo heading with a short phrase that does not feel stuffed with keywords.
3. Make sure the product card links to a real EasyStore product or a collection page.
4. Open the page at a mobile size and confirm that the face, product, and text are not cropped too aggressively.
5. If a slider is used, keep the number of slides small and make sure each slide serves a clear purpose.

Do not turn the hero area into a catalog of every offer. Its job is to give direction. Detailed products, schedules, and articles are better shown lower on the page, once the user already has context.

The About-the-Workshop Section and Trust

In the reference design, the first screen is followed by a block with soft cards and a central image. That section works well as a trust layer: who makes the products, which materials are used, and why the collection looks the way it does. It is not the place for a long biography. Two or three short paragraphs, the maker's name, a photo, and a link to a fuller page are usually enough.

If the workshop does not have a public-facing person, you can replace the portrait with a photo of the process, the packaging, or the studio. The key thing is not to leave a generic stock image in place. For a craft website, proof of authenticity matters more than decorative perfection.

The Product Block on the Homepage

The High Quality Handcrafts block in the visual reference shows a row of cards with names and prices. On a real site, this area is better used for a specific selection rather than random products: new arrivals, a seasonal collection, gift sets, or the clearest products for a first introduction. If EasyStore and SP Page Builder are connected through the relevant addons, check the product source, sorting, card appearance, and links into the product page.

Result check: after saving the homepage, open it as a regular visitor, click through two product cards and one menu item. If even one of those links goes to a demo page or an empty product, the homepage is not ready to launch yet.

The EasyStore Shop: Products, Filter, Product Page, and Order Flow Validation

Crafty is positioned as a template for a craft shop, and an important part of that logic depends on EasyStore. According to the official sources, EasyStore handles product creation and management, variants, coupons, shipping, payments, orders, analytics, and SP Page Builder integration. In Crafty, that means the visual storefront and the shop logic need to stay aligned. Beautiful cards will not help if the products have no categories, photos, descriptions, or a clear path to checkout.

The Minimum Viable Product Page

For handcrafted goods, the product page should answer the questions buyers usually have before purchasing: what the item is, what material it is made from, what dimensions or options it has, how the texture differs, whether care instructions apply, what the object looks like at scale, and whether a similar custom order can be repeated. The Crafty documentation and product page mention product pages with images, descriptions, materials, and reviews in a clean structure. Use that structure as a base, but do not overload the first screen of the product page with a long story.

A practical minimum for each product:

• A human-readable title without an internal SKU at the beginning.
• Several images of the same item shot with consistent lighting and proportions.
• A short description of its purpose and material.
• A selected category and, if needed, tags or a collection.
• A clear price or a clear way to request details if the item is made to order.
• A tested Add to Cart button or another target action that actually works in your configuration.

Store Filter and Search

The official Crafty product page mentions a shop page with filter and search. That should not be treated as a decorative extra. Filtering only helps when the user has real decision criteria: material, collection, product type, size, color, purpose, availability. If the assortment is small, keep the filter simple or temporarily remove unnecessary parameters so you do not generate empty results.

Test the filter in three states: many products found, one or two products found, and nothing found. The last state is often overlooked. If the page shows only an empty block with no explanation, visitors may assume the shop is broken. It is better to prepare a clear message, a link to collections, or a prompt to contact the workshop.

Checking the Shop Flow

Seeing attractive product cards is not enough for launch. You need to walk the visitor path:

1. Open the shop page from the menu.
2. Find a product through filter or search.
3. Open the product page and check the images, description, material, and related products.
4. Add the product to the cart, if that feature is enabled.
5. Check the cart and checkout flow in test mode without touching live payments.
6. Make sure notifications, statuses, and emails are configured according to the project's rules.

If the shop is currently meant to work only as a catalog without online payment, do not pretend that full checkout exists. It is better to build an honest path like "view product - check availability - get in touch" and remove any elements that imply purchasing when that flow does not actually work.

Workshops, Booking, and the Blog: How to Use the Ready-Made Pages Without Creating Chaos

What makes Crafty interesting is that the shop does not live separately from the content. The official materials mention workshop pages, a booking page, a blog, and a detailed event page. For a craft business, that is a strong combination: the workshop can sell products, explain the process, invite people to classes, and answer common questions without relying on several disconnected templates.

The Workshop Page

A workshop page should explain not only the topic of the class, but also the practical conditions: who it is for, how long it lasts, what the participant takes home, which materials are included, whether experience is required, and how to get in touch or submit a request. If Crafty includes a ready-made block with a schedule and a form, use it as a framework, but replace the demo fields with questions that reflect your actual process.

For small workshops, it is often better to start with a simple inquiry form rather than a complex booking calendar. A more advanced system is only necessary when there is a regular schedule, seat limits, multiple groups, and a real need for automated registration. If classes happen irregularly, a page with a clear description, a contact button, and a straightforward form is usually enough.

The Blog as Part of Sales, Not a Separate Feed

The blog in Crafty can strengthen the shop if you use it for useful material: how to care for ceramics, how glazes differ, how to choose a gift, what happens during a workshop, or how a collection is made. Articles like that help visitors understand the value of the product and reduce repetitive questions.

Do not turn the blog into a news feed just for publishing frequency. For a craft site, five strong pieces tied to products and workshops are better than dozens of short posts with no practical value. You can connect articles to collections from the homepage and product cards, but do it naturally: the article should support decision-making, not just inflate the number of internal links.

Utility Pages

Built-in FAQ, terms, and contact pages are not there just to check a box. They reduce uncertainty before a purchase or a booking. The FAQ should cover delivery, care, returns, custom orders, class duration, participant age, and contact methods. The terms page should reflect the real business, not remain demo text.

Contacts are also worth testing technically: the form should send email, the map or address should be current, the contact buttons should work, and the links in the header and footer should point to the same page. If a visitor reaches the contact page after viewing a product or a workshop, losing them because the form does not work is especially frustrating.

Module Positions and Helix Layout Builder: How Not to Lose Blocks While Editing

With a Joomla template, it is important to understand the difference between a page, a module, and a position. The page controls the main content, the module is displayed in a predefined position, and the template decides where that position physically appears. The Crafty documentation separately shows header and layout module positions, while the Helix Ultimate documentation explains Layout Builder, the 12-column grid, rows, columns, module positions, and responsive rules.

If, after installation, some blocks disappear or shift unexpectedly, do not jump straight into CSS changes. First check whether the module is published, whether it is assigned to the correct menu items, and whether its position exists in the current template style. In Joomla, a module can be enabled but still invisible if it is assigned to a position that the current style does not render, or if the menu rules exclude the current page.

How to Enable Position Preview

Joomla can display module positions through the ?tp=1 parameter if position preview is enabled in the template settings. In practice, this helps you understand where the header, footer, main content area, and extra positions are located. On a production site, it is best to disable that mode again after diagnostics.

What Exactly Needs to Match

1. Open System - Site Templates and the template settings.
2. Enable Preview Module Positions.
3. Open the public page by adding ?tp=1 or &tp=1 to the URL.
4. Compare the visible positions with the modules you want to display.
5. Turn preview back off on the live site after checking.

What to Change in Layout Builder

Helix Layout Builder lets you change rows, columns, the grid, and positions. It is a powerful tool, but also one that is easy to use too aggressively. If you remove a row or assign the component area incorrectly, pages may start rendering in unexpected ways. With Crafty, it is better to duplicate the template style or work on a staging copy first, then change one area at a time and verify the result.

Typical safe changes:

• Hide a secondary column on phones if it gets in the way of viewing products.
• Add a separate position for a promo block or contact module.
• Reorder footer modules without deleting the original positions.
• Adjust the container width for the shop page if the cards feel too cramped.

Changes that are better left until after a backup: replacing the header structure, removing the component area, renaming key positions, or moving the menu into a completely new row. Edits like that can affect not just one page, but the entire site.

Safe Visual Tweaks Without Editing Template Files

The official Helix documentation recommends using the custom CSS field or a separate custom.css file rather than editing the main template files. That is especially useful with Crafty: you can fine-tune cards, spacing, or accents to match the brand without breaking future updates. But custom CSS should stay small and easy to reverse. If a tweak turns into dozens of lines, it is better to move it into a separate file and keep a clear list of changes.

An Example of a Careful CSS Tweak

For example, if you added a custom class called crafty-featured-products to an SP Page Builder section on the homepage and want to soften the product cards slightly without affecting the whole shop, that approach is safer than writing styles against broad selectors like .card, because the change is limited to one specific section.

.crafty-featured-products .sppb-addon {
  border-radius: 6px;
}

.crafty-featured-products img {
  object-fit: cover;
}

.crafty-featured-products .sppb-btn {
  letter-spacing: 0;
}

Where to place it: Template Options - Custom Code - the custom CSS field, or your custom.css file if you already manage styles that way. Before applying it, assign the class only to the section you want to change. After saving, clear cache and check the homepage, the product page, and the mobile view.

Rollback is simple: remove the CSS or remove the crafty-featured-products class from the section. Do not edit Joomla core files, EasyStore, SP Page Builder, or the template itself if the task can be solved through settings and custom styles.

Language and Text Adjustments

If you need to replace a Joomla or extension system phrase, check the built-in language override mechanism first. It is safer than searching for the string in files. This is especially relevant for a Russian-language site built on the template: the shop interface, forms, buttons, and system messages should all sound consistent.

Be careful when translating elements inside the demo design. Product names, menu items, and text blocks should be replaced with real Russian content, but the technical names of admin panel items in instructions are better left exactly as they appear, wrapped in code, so the administrator can match them to the interface.

Practical Example: Launching a Workshop Homepage and the First Collection

Now let us build a realistic scenario. Imagine a workshop that sells a small ceramics collection and also runs clay classes. The goal is to prepare the homepage, a storefront for the first collection, and a clear path to the workshop page. This is not a full store launch with all legal and payment settings in place. It is a safe content-and-technical starting point that is ready to show to a team or a client.

Goal and Preparation

Goal: a visitor lands on the homepage, understands the workshop atmosphere, sees several products, can open a product page, move to the workshop page, and find the contacts. Before starting, the following should already be in place: Crafty installed, a working template style, access to SP Page Builder, EasyStore enabled, at least three products with images, a workshop page, and a contact page.

Setup Steps

A Sequence Without Jumping Between Layers

1. In SP Page Builder, open the page assigned to the Home menu item.
2. Replace the hero section with a photo of the workshop or a product, keeping the composition calm and the heading short.
3. Check the card layered over the hero section: it should lead to a real product or collection.
4. In the workshop/about block, replace the demo portrait or illustration with a real process photo if there is no public-facing portrait.
5. In EasyStore, create the products for the first collection and assign categories, images, and short descriptions.
6. Configure the homepage product block so it displays that collection or those selected products.
7. Update the Workshop menu item, or its equivalent, so it points to the class page with the terms and form.
8. Check the footer: contacts, terms, FAQ, and links should not point to demo pages.

Checking the Result

After saving, open the site as a normal visitor. Follow this path: homepage - product - back to collection - workshop - contacts. At each step, verify that the URL is understandable, the text is no longer demo copy, the images are not critically cropped, the buttons go where they promise, and the contact form works.

One nuance: if changes in SP Page Builder are saved but the public page does not update, clear the Joomla and browser cache first. Then confirm that you edited the page actually assigned to the current menu item. If the site uses separate template styles for different menus, make sure the change was made in the correct style.

Checking Speed, SEO, and Usability After Setup

After the visual setup is done, it is important to test not just how the site looks, but how well it works. A template may look good in the hero section and still underperform because of heavy images, empty meta descriptions, broken links, or a poor mobile experience. That is especially noticeable with Crafty because the design relies on large photography and product cards.

Images and Speed

Large photos should be optimized to a reasonable size. Do not upload camera originals directly into the hero background if they are excessively heavy. Prepare separate versions for the website, check sharpness after compression, and do not forget alternative text. For products, use consistent proportions so the cards do not jump in height.

If, after enabling cache or CSS/JS optimization, some SP Page Builder blocks render incorrectly, temporarily disable the questionable optimization and test the settings one by one. There is no need to turn off all caching forever. Find which file, script, or mode is causing the conflict, then add an exception or choose a softer configuration.

The SEO Foundation for a Craft Website

Crafty by itself does not guarantee search performance. It provides structure and a visual format. SEO quality depends on content, URLs, headings, product cards, internal links, and speed. For the homepage, prepare a clear heading, a short workshop description, links to key categories, and a contact path. For products, write unique descriptions rather than copying the same phrase into every card.

For the blog, choose topics that help the buyer: product care, gift selection, the making process, differences between materials, or preparation for a workshop. Those kinds of articles connect naturally to products and collections. SEO here works through usefulness and structure, not through repeating the template name or stuffing in a list of keywords.

Mobile Review

Helix Layout Builder and SP Page Builder both include responsive settings. Check more than just screen width. Test real actions: opening the menu, browsing product cards, using the filter, clicking the add button, submitting the workshop form, and using the contact form. If phone users have to scroll through an oversized hero section for too long, reduce its height or restructure the block order.

Why Crafty May Display Incorrectly and How to Diagnose the Issue

Most issues that appear after installing a Joomla template look similar: some blocks are missing, the style did not apply, the page still shows demo data, the shop does not display products, or images were replaced by placeholders. The key is not to guess, but to move through the chain methodically: installation - template assignment - menu - module - component - cache - content.

The Homepage Does Not Change After Editing

Symptom: you change text or a block in SP Page Builder, but the public homepage stays the same. Possible causes: you edited the wrong page, the menu item points to a different object, cache is enabled, you are looking at a different template style, or the changes were not saved.

Check: find the Home item in the main menu, open the linked object, then verify the page under Components - SP Page Builder Pro - Pages. After saving, clear cache. If nothing changes, temporarily add an obvious test phrase in a draft area and see whether it appears on the public page.

Modules Do Not Appear in the Expected Position

Symptom: a module is published, but it does not show on the page. Causes: the position is wrong, the module is not assigned to the current menu item, the position is hidden by responsive settings, the current template style does not include that position, or cache is still showing an older result.

What to do: enable position preview with ?tp=1, confirm that the position exists, check the module's menu assignment and publication status. If the position exists only in another template style, either move the module or configure the style that is actually assigned to the page.

QuickStart Does Not Include the Same Photos as the Demo

Symptom: instead of the polished demo photography, you see placeholders or different images. That may not be an error at all, but a licensing limitation. Template developers often do not have the right to distribute every image from the live demo inside the package.

Fix: prepare your own photos with similar proportions and mood. Do not try to "restore" someone else's demo photography as if it were a required part of the product. If some blocks are built around a specific aspect ratio, start by replacing the images in one section and checking the mobile view.

The Shop Is Empty or the Filter Finds No Products

Symptom: the shop page opens, but no products appear, the filter returns empty results, or the cards lead to the wrong place. Causes: the products are not published, categories are missing, the SP Page Builder product block is pulling a different selection, the filter uses parameters the products do not have, or cache is keeping an outdated storefront.

Check: open EasyStore in the admin panel and make sure the products are published and assigned to the required categories. Then review the settings of the product block on the shop page or homepage. If the filter is complex, temporarily reduce it to one simple criterion and confirm that it works.

Styles or Interactive Elements Disappear After Optimization

Symptom: the slider, filter, menu, or part of the sections stop working correctly after enabling compression, file merging, or caching. Causes: an optimization conflict with files from SP Page Builder, EasyStore, the template, or a third-party extension.

Fix: disable optimizations one at a time and test the result. If the problem disappears after turning off a specific mode, do not re-enable it blindly. Add an exception or keep the softer mode. If you cannot identify the cause quickly, roll back the last optimization and continue the launch without it.

When Crafty Is the Right Choice

JoomShaper Crafty is worth using when you need more than just a Joomla template. It works best as a ready visual foundation for a craft shop or workshop website. It is especially effective when the project already has quality photography, a small product collection, a brand story, and classes or events that deserve dedicated pages.

Before launch, run one final check: the server meets the requirements, the installation method was chosen correctly, the homepage is edited in the right place, EasyStore products are published, the menu no longer points to demo pages, modules sit in working positions, images have been replaced with legal and optimized versions, and cache is not hiding changes. After that, you can download the latest version of JoomShaper Crafty and test it on a staging site or move on to updating an already prepared site copy.

If, after testing, you can see that Crafty's structure matches your real scenario, do not rush to tear the design apart. The template's strength is its calm visual rhythm, the way it connects the storefront, workshops, and content, and the ready Joomla ecosystem built around Helix Ultimate, SP Page Builder, and EasyStore. The more carefully you replace the demo content with your own material, the faster the product page turns into a complete working website.