JoomShaper Gourmand - Joomla Template

How to Configure JoomShaper Gourmand for a Joomla Recipe Website

JoomShaper Gourmand is best understood not as just a nice-looking template, but as a ready-made foundation for a food website: a blog with food reviews, a recipe catalog, an author page, curated content collections, ad zones, and polished inner pages. In this guide, we will look at how to approach the template after installation, when to choose Quickstart versus the regular package, where to find the key settings, and how to verify that the public-facing site actually works the way you intend.

This guide does not repeat the short product description at the top of the page. The practical side matters more here: which pages and modules to replace first, how to avoid breaking the demo structure, how to use SP Page Builder Pro and Helix Ultimate, why recipes in Gourmand are tied to Joomla articles rather than a separate component, and which symptoms usually show that a module, menu, or cache setup is only partially finished.

If you are still deciding whether to use the template, start with the sections on suitable use cases and limitations. If the archive is already installed on a staging domain, jump to the configuration section: it will help you move from demo site to working homepage, recipe pages, sidebar modules, footer, and final checks without taking unnecessary risks with the existing website.

What This Template Actually Solves

Gourmand's main job is to quickly give a Joomla site the structure of a culinary media project. In the official product page and documentation, the template is presented as a solution for a food blog, recipe website, recipe catalog, restaurant reviews, and recipe-related pages. That distinction matters: the template does not replace a full restaurant ordering system, table reservations, or delivery management. It helps you present food-related content in a clean and consistent way, while commercial use cases such as ads, affiliate books, or contact pages work as part of a content-driven site.

Gourmand has two meaningful starting models. The first is Food Blog, where the main screen, post collections, author block, and featured posts guide the reader through your content. The second is Recipe Catalogue, where the emphasis shifts toward recipe categories, lists, individual recipe cards, and an easy path from collection page to recipe. The choice affects more than the visuals: it determines which menu sections, article categories, modules, and Page Builder sections you will need to change first.

The best starting point for most sites is Quickstart on a separate staging domain or subdomain. JoomShaper's documentation specifically notes that Quickstart is a complete Joomla site with demo data, the template, modules, Helix Ultimate, and settings. It cannot be installed over an existing Joomla site through the extension manager. The regular Template Pack is better suited to users who only want to add the visual layer to an existing site and are prepared to build pages, modules, and articles manually.

Which Features Matter Most Here

With Gourmand, the real value is not the generic feature list, but the combinations that actually help you launch a site:

• Two homepage layouts for different kinds of food projects: a blog and a recipe catalog.
• Recipe pages with space for ingredients, cooking steps, images, extra details, and related content.
• Category-based recipe output through Joomla articles and the Articles > Category Blog view.
• Section editing through SP Page Builder Pro, including the homepage, footer module, and visual content blocks.
• Helix Ultimate module positions that let you control the sidebar, footer, content top, and content bottom areas.
• Ready-made pages such as About, Contact, Registration, and 404, which are best replaced with your own content before launch.
• The ability to add clean CSS, meta code, or verification snippets through Helix Ultimate settings without editing core files.

Together, these elements give you more than a design. They provide a working framework. If you only replace the logo and a couple of images, the site may look finished, but it will still be a demo project. Proper setup starts with a content map: which recipe categories you need, what the main menu item should be called, where reviews will live, which monetization blocks actually make sense, which modules should appear on recipe pages, and which sections should be removed to keep the site from feeling overloaded.

Who Gourmand Fits and Who Should Look Elsewhere

JoomShaper Gourmand is a strong fit for a site owner who wants to launch a food project on Joomla and is ready to work with content: publishing recipes, reviews, curated roundups, tips, ingredient-focused articles, or stories from the author or team. The template is especially useful if the visual side needs to look strong from day one: large food photography, clean white space, expressive typography, green accents, article cards, and a polished food-blog presentation.

For a personal food blog, Gourmand is convenient because it does not force you to build a complex recipe database right away. You can start with Joomla article categories, configure the recipe presentation, and add images, ingredients, and steps directly within the page structure. For a studio, chef, or small food business, the template is valuable because of its ready-made author and contact pages, featured posts, and the ability to present a recipe as a compelling story rather than a dry entry.

There are also cases where the template may not be the best choice. If you need an online store with a cart, payments, inventory, and order management, Gourmand does not solve that on its own. If you need a structured recipe database with filters for allergens, calories, cooking time, ratings, and user collections, you will need to extend the site with dedicated extensions or carefully design the article structure. If the team does not want to work with SP Page Builder and prefers a fully code-based template workflow, Helix and Page Builder may feel like unnecessary extra layers.

A practical selection rule: Gourmand is a good choice when you need a visually strong food website with manageable pages, modules, and blog-style content logic. If the core goal is a complex data catalog or full e-commerce, first evaluate which extensions will cover the missing functionality.

How Not to Mistake a Beautiful Demo for a Finished Project

The Gourmand demo looks convincing because of its photography, section rhythm, and thoughtfully prepared content. But after installing Quickstart, you do not get a finished website. You get a training version. It needs to be cleaned up: replace the text, remove unnecessary articles, configure the menu, verify user permissions, enable only the modules you actually need, and update the links. The most common beginner mistake is publishing the demo structure with only minimal changes, planning to replace the content gradually later. In practice, that hurts SEO, confuses visitors, and makes the site harder to maintain.

Before going live, ask yourself three questions. First, which content should be published first: recipes, reviews, articles, or author pages? Second, which homepage blocks support that content specifically? Third, which demo-site elements have nothing to do with your project and should be disabled instead of left in place just because they look good?

What to Check Before Installation

Preparation matters more with a Joomla template than it may seem. Gourmand relies on the Joomla, Helix Ultimate, and SP Page Builder Pro stack, and Quickstart includes not just the template but a complete demo installation. So before you install anything, decide where you will experiment, how you will preserve the current data, and which package you actually need.

A Separate Test Environment

For Quickstart, use an empty directory and a separate database. This can be a subdomain such as dev.example.com, a local environment, or a temporary folder on your hosting account. Do not install Quickstart on top of a live website. If you already have a Joomla site with articles, menus, and users, install the regular template package instead, or create a copy of the site first and test the migration there.

Before doing anything, make a backup of both the files and the database. Even if you are installing only the Template Pack, a mistake in template style assignment, module positions, or caching can temporarily change how the public-facing site looks. The backup is not just a formality. It gives you a fast rollback path if pages turn blank or the menu shifts into the wrong position after enabling the template.

Template Package or Quickstart

The package you choose determines the entire process that follows:

If you are unsure, install Quickstart in a test environment first and study the structure. After that, you can carry those ideas over to the live site: replicate the module positions, copy the homepage logic, configure the recipe categories, and only then enable the template for visitors.

Permissions, Updates, and Compatibility

The official product page lists Gourmand as compatible with current Joomla branches and tied to Helix Ultimate. The changelog shows that the template has been updated alongside Joomla, PHP, SP Page Builder, and Helix Ultimate. That information is useful for planning, but on a real project you should not stop at the template version alone. Check Joomla system information, the PHP version on the server, extension availability, memory limits, folder write permissions, and cache status.

After installation, go to System and check for warnings related to folders, updates, or extensions. If you used Quickstart, remove or replace demo users, verify the super user account, configure the site address, and keep only the extensions you actually need enabled. The fewer unnecessary extensions remain active, the easier it is to maintain both security and performance.

Installation and Initial Validation Without Unnecessary Risk

Installing Gourmand really means choosing between two different workflows. With Quickstart, you install a complete Joomla site as a new setup. With the Template Pack, you add the template to an existing Joomla site and then build the structure manually. Do not mix these workflows: Quickstart should never be installed through the standard extension manager on a live site.

If You Choose Quickstart

Treat it like a normal Joomla installation. Extract the archive into an empty directory, create a separate database, open the domain or subdomain in the browser, and walk through the installer. After installation, check the public homepage, administrator login, menu structure, and presence of demo content. Then make a checkpoint backup of that state right away, so you have a clean restore point before replacing content.

Initial Quickstart validation:

1. Open the homepage as a regular visitor and make sure the header, hero, post blocks, author section, featured posts, and footer are all visible.
2. Go to the admin panel and confirm that SP Page Builder pages open from Components > SP Page Builder Pro > Pages.
3. Open Menus and find the home item marked with the yellow star so you know which homepage variation is being used by default.
4. Check Content > Articles and the recipe categories, because the Recipe page in the documentation is tied to the Articles > Category Blog view.
5. Go to Content > Site Modules and inspect the published modules in the sidebar and footer positions.
6. Clear both Joomla and browser cache, then check the homepage again.

If You Choose the Template Pack

The Template Pack installs like a normal extension, but it does not create demo pages, modules, or recipes for you. After installation, open System > Site Templates or the current template management section in your Joomla version, find the Gourmand style, and assign it to the appropriate menu items. If you want to test the template without affecting the whole site, assign it only to a hidden test menu item.

Then build a minimal structure: a homepage, a recipe category, a menu item for that category, one test recipe, one sidebar module, and one footer module. Only after that does it make sense to apply the design to live pages. Otherwise, you will only see an empty shell and may incorrectly assume the template was installed wrong.

Short takeaway: after installation, you should know which package was used, which page is assigned as the homepage, which articles are being displayed as recipes, and which modules control the sidebar and footer. Without that map, the next stage turns into random section editing.

Homepage: How to Choose a Variation and Replace Demo Sections

The homepage is the most visible part of Gourmand. The original reference shows a clean white background, top navigation with a logo, a large hero section with food photography, a high-contrast serif headline, green accents, a Latest Blog and Food Reviews block, an author section, and Featured Posts. That structure works well for a food blog, but it needs to serve your content rather than the demo.

The documentation states that Quickstart includes two homepage variations built in SP Page Builder Pro. You can choose which one becomes the homepage through the menu item marked with the yellow star, and you can edit the page itself through either the backend or frontend editor. In practical terms, that means this: first choose the homepage scenario, then update the sections, then verify the menu, and only after that enable caching.

Choosing Between the Blog and the Catalog

If the site revolves around an author, reviews, stories, tips, and regular publishing, Food Blog is the better starting point. In that setup, the main slider, latest reviews block, featured post cards, and author section matter most. If your primary asset is recipes with categories, cooking times, difficulty levels, and photography, choose Recipe Catalogue or adapt its logic for your own homepage.

Do not try to keep both models on the first screen. Visitors should understand right away what to do next: read the blog, pick a recipe, browse a category, or go to the author page. If the homepage points in too many directions at once, the template may look rich, but the user journey becomes weaker.

What to Change First in SP Page Builder

Open the relevant page in Components > SP Page Builder Pro > Pages or through the frontend editor. Start by changing the major content blocks rather than the small spacing details:

1. Replace the hero headline with a specific promise that reflects the site: the recipe style, cuisine, review format, or author focus.
2. Check the hero image: it should be large enough, legally usable, and optimized for file size.
3. Configure the Latest Blog and Food Reviews list so it pulls real content from the right categories.
4. Replace the author section or disable it if the site is not built around a public chef or author figure.
5. Check the buttons and links: demo buttons should lead to real pages, not placeholders.
6. Save the page and review the public-facing version as a guest.

How to Edit Sections Safely

In SP Page Builder, it is helpful to work through Layers, where you can see the page sections, columns, and elements. If you need to move the Latest Reviews block higher or lower, do it at the section level instead of copying HTML. Before making a major change, use page duplication or export if your version of Page Builder supports it. That gives you a way to restore the original version without rolling back the entire site from backup.

After every major change, check the homepage in three states: standard desktop view, a narrow screen, and guest mode without logging in. That will show you whether images disappeared, text overlaps the cards, the menu shifted out of place, or the administrator bar is appearing where it should not.

Recipes, Categories, and the All Recipes Page

One of Gourmand's strengths is that it does not force you to learn a separate recipe component from the start. JoomShaper's documentation states that the page under the Recipe menu item uses the Articles > Category Blog view and pulls content from the Recipes category. That is standard Joomla logic: articles are grouped into categories, and a menu item displays the selected category in a blog layout.

For a site owner, this creates a simple working model. You create a recipe category, add articles with intro images and full text, create a menu item of type Category Blog, and get a listing page. From there, the template controls the look of the cards, sidebar, and overall page rhythm, while the content itself stays inside standard Joomla articles.

A Recipe Structure Without Unnecessary Complexity

For the initial launch, a simple article structure is enough. At the top: the dish name, an intro photo, and a short description. Then come the ingredients, cooking steps, useful notes, and optionally time or difficulty if that information genuinely helps the reader. If you want to show nutrition data, servings, and related recipes, add those details consistently across all recipes.

Do not overload the first recipe with every possible block. It is better to create one reference article, check it in the list and on the detail page, and then write a short internal editorial guide. That guide should define the photo size, how ingredients are formatted, how long the intro paragraph should be, where internal links go, and which categories to use.

Configuring the Recipe Menu Item

Create or review the menu item for the recipe catalog. In Joomla, that is usually Menus > Main Menu > New, followed by selecting the Articles > Category Blog type and the recipe category. Make sure the menu item is published, the alias is clear, and the display parameters do not conflict with the template's visual logic. If the page is showing too much text, adjust the article intro text and the blog layout settings.

If recipe cards do not appear, do not start by blaming the template. Check the data chain instead: the article is published, it belongs to the correct category, the category itself is published, the menu item points to that category, guest access is allowed, the publication date is not scheduled for later, and the cache has been cleared. That is faster than changing template settings at random.

Sidebar and Supporting Modules on Recipe Pages

On the All Recipes page and on individual recipe pages, the real value often comes from the side blocks: popular tags, categories, search, recent content, an ad banner, or a small author note. In Quickstart, some of those elements may already be published in the correct positions. In the regular Template Pack, you will need to create them manually.

Gourmand's documentation specifically notes that to display modules in the right or left sidebar on an article detail page, the Helix Options > Blog > Details > Disable Modules setting may need to be set to OFF. This is a typical setting that is easy to miss: the recipe list looks fine, but the individual page feels empty on the sides. Always test the detail page itself, not just the catalog.

Module Positions, Footer, and Menu Logic in Joomla

A Joomla template does not live only inside Page Builder. A large part of the final result is assembled from modules, positions, and menu items. Gourmand uses Helix Ultimate, and the documentation for positions explains that Layout Builder lets you move positions, resize columns, add rows, and hide elements on tablet or mobile. That is powerful, but it requires discipline.

The module logic is especially important for the footer, sidebar, mobile menu, and supporting content blocks. Gourmand's documentation states that the footer is built through a single SP Page Builder module in the footer1 position. That means you should not look for the footer only in template files or only in global settings. It also lives in the module list and inside the content of that Page Builder module.

How to Check Module Positions

Joomla can preview module positions if template position preview is enabled. For real validation, use it only temporarily and disable it again on a published site. A safer day-to-day method is to open Content > Site Modules, filter modules by position, and verify their menu assignment.

For every important module, keep three questions in mind:

• Which position it is published in: footer1, sidebar, offcanvas, content top, content bottom, or another template position.
• Which menu items it should appear on: all pages, recipes only, the homepage only, or a hidden test section only.
• Who can see it: all guests, registered users, or only a specific access group.

The Footer as a Separate Editable Block

In Gourmand, the footer is best treated as its own part of the site. Open the module in the footer1 position and check its type and content. If it is an SP Page Builder module, edit the links, text, contact details, social elements, and visual blocks through Page Builder, then verify the result across multiple pages. The footer is global, so any mistake there will repeat everywhere.

Typical footer changes:

• Replace demo navigation with real sections: recipes, blog, about the project, contact, and site policies.
• Remove unnecessary demo social links or replace them with your public profiles.
• Verify contact details and the form, if one is used.
• Trim visual blocks that are not needed on mobile.
• Save and check the footer on the homepage, a recipe page, the contact page, and the 404 page.

Menu and Mobile Navigation

The source image shows a minimal top navigation: Home, About, Book, Blog, Recipe, Pages, Contact. A real site does not have to copy that exact set. What matters is keeping the path clear: homepage, recipes, blog or reviews, author or team, contact. If there are too many items, move some into a dropdown, but do not bury recipes too deeply.

After changing the menu, check the offcanvas or mobile menu. A common situation is that the desktop navigation looks correct, but the mobile menu uses a different module or has not updated because of cache. Open the site on a narrow screen, check the item order, nested expansion behavior, and links back to the homepage.

Practical Ways to Use Gourmand

A strong template proves itself through a clear use case, not through the number of sections. Below are a few working models based on Gourmand's documented strengths: two homepage variations, recipe pages through article categories, Page Builder sections, sidebar modules, footer, and ready-made pages. You do not need to implement everything at once. Pick one main scenario and configure the menu, homepage, and first content pieces around it.

Author-Driven Food Blog

For an author blog, use the homepage variation with a strong hero, latest posts block, author section, and featured posts. The menu should lead to the blog, recipes, author page, and contact. In SP Page Builder, replace the demo copy with the actual voice of the project: what makes it distinct, which recipes you publish, how often reviews appear, and where a reader should start.

Validation is simple: a new visitor should understand within one screen who runs the site and which content is worth opening first. If the hero speaks too vaguely and the cards still show random demo posts, the scenario is not fully configured yet.

Recipe Catalog with Categories

For a catalog, the recipe category, filtering logic, and cards matter more. Create categories by dish type, cuisine, difficulty, or cooking time. Configure the Recipe item as a category blog and verify that the cards show intro images and clear titles. The sidebar can be used for categories, popular tags, and search.

In this scenario, the homepage should lead visitors toward categories rather than only recent posts. Keep author and ad blocks lower on the page so they do not distract from the main task, which is finding a recipe.

Chef, Studio, or Small Food Business Website

If the site represents a chef, studio, or small team, use Gourmand's visual strength to build trust: homepage, About page, contact, posts, recipes, and possibly a dedicated book or collection page. In the hero area, avoid a vague slogan and use clear positioning instead: signature cuisine, workshops, seasonal recipes, or local reviews.

This is where it becomes especially important not to promise features that do not exist. If event registration, payments, or bookings are not implemented through a separate extension, do not imply that the template supports them on its own. Use a contact form, a link to an external booking page, or a simple CTA if that matches the project.

Content Project with Affiliate Material

The official product page mentions ad placements and pages for recipe books. That makes the template suitable for a site that publishes book reviews, ingredient roundups, or affiliate recommendations. Use that carefully: ad blocks should not obscure the recipe, and affiliate links should be clear to the reader. Always check the mobile view, because side banners and long cards often hurt usability on narrow screens.

In this scenario, it helps to set an editorial rule: every affiliate block should be tied to a specific recipe or curated roundup, not placed on every page indiscriminately. That way, monetization supports the content instead of feeling like something pasted in from the outside.

Safe Enhancements, Performance, and Clean CSS

After the initial setup, you will almost certainly want to fine-tune small things: button color, card spacing, link styling, image behavior, or extra meta code. Gourmand provides a sensible path for that through Helix Ultimate and SP Page Builder. Gourmand's documentation states that custom CSS, JavaScript, meta tags, stats, and verification code can be added through template settings fields, but custom PHP should not be used inside the template options.

For most projects, three directions are enough: enable reasonable Page Builder optimization, keep images at a sensible file size, and add targeted CSS only on top of existing classes. Do not start by editing template files if the task can be handled through settings or a small custom CSS addition. That approach makes updates and rollbacks much easier.

SP Page Builder Settings Worth Checking

In Components > SP Page Builder Pro > Settings, review the global settings. The documentation describes Lazy Load, Production Mode, Color Library, Typography, and other sections. For a food website, images matter especially: if the photography is heavy, even a beautiful homepage will be slow. Lazy Load can help with deferred loading, while Production Mode outputs generated CSS into a separate file.

Enable optimizations gradually. First test the site without aggressive compressors, then turn on one setting, clear the cache, and check the homepage, recipe page, mobile menu, and contact form. If an animation disappears, the slider breaks, or styles stop applying after compression is enabled, roll back the last setting and look for a conflict with an external optimization plugin.

A Small CSS Tweak for Recipe Cards

Below is an example of a safe tweak: it does not depend on a hidden API and does not modify PHP. Use it only after checking the classes in your browser inspector. If your build uses different classes, adapt the selectors. The right place for it is the custom CSS field in Helix Ultimate or a separate trusted module or plugin for custom CSS.

/* Gourmand: gently align recipe cards in the list */
.gourmand-recipe-card,
.blog .article-list .article {
  border-radius: 6px;
  overflow: hidden;
}

.gourmand-recipe-card img,
.blog .article-list .article img {
  width: 100%;
  height: auto;
  display: block;
}

.gourmand-recipe-card .article-title,
.blog .article-list .article .article-header {
  line-height: 1.35;
}

After inserting it, clear the cache, open the recipe page, and check the cards on desktop and mobile. If the wrong elements changed, remove the CSS and go back to the original state. Do not paste CSS blindly from someone else's example without verifying the actual classes on your page. Even a safe tweak can affect a different article list if the selector is too broad.

Localization and Language Details

Gourmand is described as translation-ready, but translating a site is not just about replacing the hero text. Check the menu items, articles, modules, Page Builder sections, system form messages, footer, 404 page, and email addresses. For Joomla system strings, use built-in language overrides instead of editing extension files. That way, the translation survives updates.

If you plan to build a multilingual site, configure Joomla languages, menus, and the language switcher first, and only then duplicate Page Builder pages. Otherwise, it is very easy to end up with a nicely translated homepage and broken links to recipe pages in the other language version.

Practical Example: Launching the Homepage and the First Recipe

Let us walk through a realistic scenario. The goal is to launch a test version of the site with a food-blog-style homepage, one recipe, a catalog page, and sidebar modules. The point is not to build a full portal, but to get a verifiable minimum result: a visitor opens the homepage, sees a clear hero section, goes to recipes, opens a recipe detail page, and sees the side blocks in place.

Goal

Build a working path: Home -> Recipe -> recipe detail page. The homepage should use real text and images, the recipe page should pull articles from the correct category, and the detail page should retain the sidebar if one is planned.

Preparation

Assume Quickstart is already installed on a staging domain. Create a backup, log in as Super User, and confirm access to Components > SP Page Builder Pro > Pages, Content > Articles, Content > Categories, Content > Site Modules, and Menus > Main Menu. Prepare one dish photo, the recipe text, an ingredient list, and a short site description.

Steps

1. Open the homepage in SP Page Builder and replace the hero headline with a specific site theme, such as home dinners, seasonal dishes, or signature recipes.
2. Replace the hero image with your own version optimized for size and weight, then save the page.
3. Create the Recipes category or use the existing demo category after removing unnecessary demo articles.
4. Create the first recipe article: title, intro text, image, ingredients, cooking steps, and a short serving tip.
5. Open the Recipe menu item and make sure it points to Articles > Category Blog for the correct category.
6. Create or edit the sidebar module: recipe categories, popular tags, or recent articles. Assign it only to recipe pages.
7. If the sidebar does not appear on the recipe detail page, check Helix Options > Blog > Details > Disable Modules and the module state.
8. Clear the Joomla cache, open the site in a private window, and walk through the path as a regular visitor.

Validation

The homepage should show your text, your photo, and a correct link to the recipe section. The catalog should display article cards from the selected category. The recipe detail page should show the full text, image, and intended sidebar. On mobile, the menu should expand properly, cards should not overlap, and the hero headline should remain readable.

A Common Nuance

If you still see the old hero section or old cards after saving, clear the Joomla cache and the browser cache first. If that does not help, check whether you edited the second homepage variation rather than the one assigned as the home menu item. Gourmand has two starting models, and confusing the two is a very normal mistake when you first start working with the template.

Checking the Result Before Publishing

Before publishing, do not stop at a visual glance over the homepage. You need to validate the entire user path. A Gourmand-based site can look polished on the first screen while still containing empty demo pages, broken links, an outdated footer, hidden sidebar modules, or overly heavy photos. Build a short checklist and run through it before every major update.

Public-Facing Side

• The homepage shows real text, real images, and real links rather than demo placeholders.
• The Recipe item leads to the correct category and shows published recipes.
• The recipe detail page contains the full structure: photo, ingredients, steps, notes, and related content where needed.
• The footer contains real contact details, links, and legal pages.
• The Contact page either submits the form correctly or shows a valid contact method.
• The 404 page does not look like an abandoned demo page.

Admin Panel and Ongoing Maintenance

• Demo users do not have unnecessary access, and the super user account is protected with a proper username and password.
• Unneeded demo articles have been unpublished or removed after backup.
• Modules are assigned only to the correct menu items.
• The cache has been cleared after changes to Page Builder pages, modules, and the template style.
• Updates for Joomla, the template, Helix Ultimate, and SP Page Builder are first planned and tested on a staging copy.

Performance and SEO Without Unrealistic Promises

The template alone does not guarantee search traffic growth. It gives you structure, visual presentation, and a technical foundation, but the outcome depends on the quality of your recipes, images, headlines, internal linking, performance, and correct indexing. For SEO, check readable aliases, unique title and meta description values for important pages, alt text on recipe images, menu canonical consistency, and the absence of duplicate demo content.

For performance, start with images. A food site can easily become overloaded with photography. Use sensible dimensions, compression, lazy loading, and check the page after every optimization step. If you enable external minification plugins, do it one at a time and test the slider, menu, Page Builder sections, and forms.

Typical Gourmand Issues and How to Diagnose Them

Most problems after installing a Joomla template look like design issues, but the real cause is often the installation package, menu assignment, modules, cache, or the Page Builder page itself. This is not a generic list of all Joomla errors. It is a practical troubleshooting map specifically for Gourmand and its combination with Helix Ultimate and SP Page Builder.

After Installation, You See an Empty Template Without Demo Pages

Symptom: the template is enabled, but there is no demo-style homepage, no recipe sections, the footer looks different, and the content is empty. A likely cause is that you installed the Template Pack instead of Quickstart. The standard template package does not include demo content, modules, components, or ready-made SP Page Builder pages.

Check which archive was used. If you need the training-style demo site, install Quickstart in a clean test environment. If you intentionally installed the Template Pack on an existing site, create the required pages, modules, and categories manually. A rollback is worth considering if the template was enabled on a live site without testing and disrupted the public navigation.

You Are Editing the Wrong Homepage

Symptom: you change the hero block in SP Page Builder, but the site still shows the old version. A likely cause is that a different page variation is assigned as the homepage in the menu. Gourmand includes two homepage models, and it is easy to open the wrong one.

Check Menus > Main Menu and the yellow star marking the home item. Then open the linked Page Builder page and edit that one specifically. After saving, clear the cache and test the site in a private window. If nothing changes, temporarily add a test phrase to the hero so you can confirm you are editing the correct object.

Recipes Do Not Appear in the Catalog

Symptom: the Recipe page opens, but the cards are empty or the wrong articles are shown. A likely cause is that the menu item points to the wrong category, the articles are unpublished, they have the wrong access permissions, or the category itself is unpublished.

Check the recipe category, article status, publication dates, and menu item type. For the basic scenario, you need Articles > Category Blog. If the site uses multiple languages, also verify the language assignment for the category, article, and menu item. The fix is usually safe: adjust the menu item and clear the cache.

The Sidebar Does Not Show on the Recipe Detail Page

Symptom: the side blocks appear on the recipe list page, but disappear on the individual recipe page. A likely cause is that the Helix setting for blog details disables modules, or the module itself is assigned only to the catalog menu item and not to the detail page.

Check Helix Options > Blog > Details > Disable Modules and the module's menu assignment. Enable the module on a test page first. If the sidebar comes back, narrow the assignment to the intended section. If enabling it breaks the mobile layout, it may be better to leave it on desktop only for now or simplify the content.

The Footer Does Not Change After Editing

Symptom: you change text in one place, but the public footer stays the same. A likely cause is that the footer is assembled somewhere other than where you are editing it. Gourmand documentation points to an SP Page Builder module in the footer1 position.

Find the published module in Content > Site Modules, verify the footer1 position, open its content, and edit it through Page Builder if that is how the module is built. After saving, check several pages. If the footer changes only on one page, verify the module's menu assignment.

Styles or the Slider Broke After Optimization

Symptom: after enabling cache, production mode, or external minification, the layout shifts, the slider stops working, or some animations disappear. A likely cause is a conflict between the optimizer and CSS or JS generated by Page Builder or the template.

Disable the most recently enabled optimization, clear the cache, and test again. Enable settings one by one. If an external compressor breaks the page, keep the built-in SP Page Builder and Helix settings and disable the conflicting mode. Any optimization that makes the core user path worse should be rolled back.

Demo Photos Are Missing or Look Different

Symptom: after installing Quickstart, the site looks similar to the demo, but some images are missing or replaced. In JoomShaper documentation for Quickstart packages, there is sometimes a warning that the demo may not include all photos. This is not a template error, but a limitation of the demo content.

Prepare your own image set and replace the images in Page Builder pages, articles, and modules. If a block depends on a photo, insert a temporary legal placeholder first and replace it with the final image later. Do not try to restore someone else's demo photos from questionable mirrors.

When JoomShaper Gourmand Is the Right Choice

JoomShaper Gourmand is worth using if you want to launch a Joomla food blog, recipe catalog, chef website, or food media project with strong visual presentation and ready-made page logic. Its main value is the combination of demo structure, Helix Ultimate, SP Page Builder Pro, module positions, and a visual style that works especially well for food photography and editorial collections.

Before a production launch, verify the installation package, homepage variation, recipe categories, Page Builder pages, footer module, sidebar, and mobile menu. After that, you can download the JoomShaper Gourmand archive, deploy it in a safe environment, and follow the practical workflow from this guide. That approach is far better than enabling the template on a live site immediately and only starting to troubleshoot after publication.

If your goal is a polished recipe-focused content site, Gourmand gives you a strong start. If the project goes beyond content and requires reservations, orders, subscriptions, or a complex recipe database, use the template as the visual foundation and choose the extensions for the missing business logic in advance.