JoomShaper Travel Kit - Joomla Template

How to Set Up JoomShaper Travel Kit for a Joomla Travel Website

JoomShaper Travel Kit is best viewed not as a standalone pretty skin, but as a ready-made foundation for a travel website where the design, destination pages, tour cards, booking forms, and modular structure all need to work together. In this guide, we’ll look at how to approach installation safely, what to check before importing the demo, where to find the key settings, and how to turn the demo layout into a working site for a travel agency, hotel, or destination catalog.

This guide does not repeat the template’s short product description. The practical side matters more here: which package to choose, how not to break an existing site, which pages to edit in SP Page Builder Pro, how to review menus and module positions, why demo photos may be missing from the installation package, and which symptoms point to a bad configuration.

Some product details are confirmed by JoomShaper’s official page and the Travel Kit documentation. They state that the template is built on Helix Ultimate and SP Page Builder Pro, includes a QuickStart package for launching the demo site, uses travel-specific pages, and connects booking features through SP Booking. The same sources also describe key limitations: QuickStart cannot be installed on top of an existing Joomla site, and demo photos may be replaced with placeholders because of licensing restrictions.

If you have worked with Joomla templates before, do not skip the sections on menus, modules, and result validation. Travel Kit’s home page design does not depend on a single template file. It relies on a combination of template style, SP Page Builder pages, site modules, menus, Helix positions, and booking components.

What the Travel Kit Template Actually Solves

Travel Kit helps you quickly build a website for a travel business where visitors should do more than just read a service description. They should be able to choose a destination, date, package, or accommodation option. On JoomShaper’s official product page, the template is positioned for travel agencies, tour operators, hotels, resorts, and other businesses that need destination pages, accommodation pages, itinerary pages, and booking features.

What sets it apart from a standard corporate theme is that Travel Kit already gives you a travel-specific page rhythm: a large opening screen with an offer, a search or booking bar, popular destination cards, a discount promo section, an inspiration block, internal pages, and trust-building elements. It does not replace your content strategy, but it gives you a useful structure to build from.

The template only becomes truly valuable once you replace the demo content with real tours, hotels, itineraries, and booking terms. If you leave the demo copy and random images in place, the site may look finished visually, but it will not help users make a decision.

Travel Kit is also useful for administrators because it separates the work into clear areas. The overall site framework, header, footer, grid, and module positions are configured through Helix Ultimate. Page content is edited through SP Page Builder Pro. Booking blocks, if they are included in your version and package, depend on SP Booking and its modules. Joomla handles menus, articles, modules, languages, access permissions, and overall publishing.

When the Template Works Best

Travel Kit works especially well when the site is built around visually choosing a destination. The user sees photos, pricing, trip duration, conditions, and a button that leads to the tour or accommodation page. This setup works well for a small travel agency, a local excursion operator, a hotel with package offers, a resort, a travel blog with commercial tours, or a route catalog.

If the site needs to sell complex custom tours with manual pricing, Travel Kit can still be useful as a showcase, but automated booking should be introduced carefully. First, verify whether the booking component you use supports the fields, categories, statuses, and payment methods you actually need. Not every travel business fits neatly into ready-made package cards.

Which Product Elements Are Confirmed by the Sources

The official Travel Kit page mentions SP Booking integration, ready-made pages, homepage filters, Places and Places Details pages, accommodation pages, travel itineraries, an About page, responsive design, SP Page Builder Pro, and Helix Ultimate. The documentation adds that QuickStart includes Joomla CMS, components, modules, the selected template, the Helix Ultimate plugin, settings, and demo data. This is important: if you install only the template package, you get the visual shell without the demo pages, modules, and content.

Who Travel Kit Is For and When Another Solution May Be Better

This template is a good fit for anyone who wants a quick start with a travel-focused visual style without designing from scratch. It is useful for a site owner who wants a starter homepage structure, destination cards, inspiration sections, and a setup that fits into JoomShaper’s Joomla ecosystem. For an agency or webmaster, it can be a fast way to build a working prototype for a client and later replace the demo content with real tours.

Travel Kit may be less convenient if the project needs a custom booking architecture, deep integration with an external CRM, complex dynamic pricing based on many conditions, or a non-standard cart flow. In that case, the template can still serve as the visual layer, but the business logic will have to be handled through a separate component, integration, or custom development.

It is also worth assessing editorial discipline. SP Page Builder makes visual page editing easier, but it does not remove the need for content structure. If several administrators start changing sections, spacing, colors, and photos at random, the site will quickly lose a consistent style. For a production project, it is better to decide in advance which sections the content manager may edit and which ones remain under the webmaster’s control.

Good Fit

• A travel agency that needs a homepage with destinations, filters, packages, and promo blocks.
• A hotel, guest house, or resort where accommodation and booking pages matter.
• A webmaster who wants to launch a demo site quickly through QuickStart and show the client a working structure.
• A Joomla project that already uses Helix Ultimate or SP Page Builder and has a team that understands how they work.

May Not Be the Best Fit

• A site with an existing complex Joomla structure if QuickStart cannot be installed on a clean environment.
• A project where booking is handled by an external system and requires deep two-way synchronization.
• A team that wants a minimalist site without a page builder and without relying on extra JoomShaper tools.
• A site where long-form expert content and detailed routes matter more than a visual tour showcase.

Before choosing the template, decide what the core of the project really is: a ready-made travel storefront or your own booking system. Travel Kit is strong as a visual and structural foundation, but the business logic still needs to be validated against your real-world use cases.

What to Check Before Installing on Joomla

Preparation matters because Travel Kit has two different installation paths. QuickStart recreates the demo site and is meant for a clean environment. The template package installs on an existing site as a standalone template, but it does not bring in demo pages, modules, or ready-made SP Page Builder layouts. Choosing the wrong path at this stage leads to a common outcome: the template is installed, but the site looks nothing like the demo.

JoomShaper’s documentation lists the server requirements for QuickStart: a current PHP branch, sufficient memory limit, post_max_size, upload_max_filesize, max_execution_time, a supported MySQL or MariaDB version, cURL, OpenSSL, and working file_get_contents. This guide does not lock version numbers into the text as if they were permanent, because they change over time. Before installation, compare the requirements with the developer’s current documentation and your hosting panel.

Environment Checklist

For testing, create a separate subdomain or a local copy. This is especially important if you want to see the demo structure through QuickStart. That package includes Joomla itself and should not be installed over a live site through the extension manager. On a production site, the usual sequence is to back up files and the database, test the installation on a copy, and only then transfer the settings.

1. Make sure you have a separate database or a separate table prefix for the test installation.
2. Compare your PHP limits and required libraries against the Travel Kit documentation.
3. Confirm that you can delete or rename old files such as configuration.php and index.html if you are installing QuickStart into a clean directory.
4. Prepare real destination photos, because demo images may not be included in the package.
5. Draft the menu structure: home, packages, booking, destination pages, blog, contacts, and utility pages.

Image License Check

The documentation explicitly explains that photos from the live demo may not be distributed with the package. This is not an installation error. The developer may use those images for demonstration purposes without granting reuse rights. As a result, QuickStart may show gray placeholders, watermarked images, or image-size blocks instead of real photos.

The best approach is to prepare your own image set before you start configuring the site. For a travel website, this is critical: the exact same card grid can look either professional or random depending on photo quality and consistent cropping.

Installation: QuickStart, the Template Package, and the First Validation Pass

If you want a site that closely matches the Travel Kit demo, use QuickStart on a clean environment. It installs as a brand-new Joomla site and includes the demo data, extensions, template, modules, and settings used by the developer. If you already have a site and cannot wipe its structure, use the template package instead, but be prepared to create pages, modules, and assignments manually.

The QuickStart Scenario

QuickStart is convenient for a new project or prototype. Extract the archive on your local computer, upload the files to a clean directory on the host, create a database, and open the domain in a browser. The Joomla installer will guide you through the standard steps: site name, administrator account, database connection, and installation completion.

After installation, verify three things: the public site opens the homepage, the admin panel is available at the URL ending in /administrator, and the demo menu and modules are published. Then remove the installation directory, enable your baseline security settings, and save a backup of the installed prototype. That backup will be useful if you later make aggressive layout or module changes and need to roll back.

The Template Package Scenario

The template package is lighter and safer for an existing site, but it does not magically generate the demo homepage. JoomShaper’s documentation describes it as a standalone Helix Ultimate template. This package controls the overall visual style and layout, but it does not include ready-made components, modules, or demo content. If you install only the template and then open the site, the result may be almost empty.

In this scenario, the sequence is different: install the template through Joomla’s standard extension manager, make sure the template style appears under Site Template Styles, assign it to the correct menu items, then create or migrate pages into SP Page Builder, publish modules in the proper positions, and review the frontend. This takes longer, but it avoids breaking your existing site structure.

Post-Install Quick Check

• Open the homepage in an incognito window and make sure there is no access error or blank screen.
• Check that the main menu shows the correct items and does not point to demo pages you do not plan to use.
• Go to System - Templates - Site Template Styles and find the Travel Kit style.
• Open Components - SP Page Builder Pro - Pages, if QuickStart is being used, and review the page list.
• Check Content - Site Modules, because some visible blocks may be modules rather than page sections.

Post-Install Setup: Where to Change Pages, Menus, and the Overall Style

After installation, do not start by editing CSS. First, figure out which layer controls the visible element. In Travel Kit, the same screen is assembled from several systems: the template style in Helix Ultimate, SP Page Builder pages, Joomla menus, site modules, and booking component settings. If you edit layers at random, you may fix one block and accidentally break another.

Template Options and the Helix Ultimate Framework

Open System - Templates - Site Template Styles, choose the Travel Kit style, and go to Template Options. The Travel Kit documentation specifically describes the menu settings path through Helix Ultimate: in the sidebar, there is a Menu tab with Menu Builder, Mega Menu, and Off-canvas Menu. The layout tab in the same area is where position grid settings are configured.

Review the settings in this order: logo, header, menu, off-canvas navigation for mobile, layout, footer, typography, and any extra CSS fields available in your version. On a typical site, there is no need to rebuild the grid right away. Replace the logo, menu items, text, and images first, then decide whether the layout really needs to change.

A Safe Approach to Layout Changes

In Helix Ultimate, the layout is built from rows, columns, and module positions. Helix documentation states that the grid follows a 12-column Bootstrap-style approach with separate settings for different screen sizes. For that reason, any change to column width should be checked not only on a wide monitor, but also on tablet and mobile widths.

Do not delete an existing layout row until you know which module or component it outputs. Copy the current settings first or create a backup. If you need to hide a block on mobile, use responsive settings, but remember that hiding something with CSS does not remove it from the HTML. That matters for both performance and accessibility.

SP Page Builder Pro Pages

The Travel Kit documentation says that QuickStart pages are built in SP Page Builder Pro. Go to Components - SP Page Builder Pro - Pages and open the page you need. On the homepage, you will usually edit the hero area, the search or booking bar, the popular destination grid, promo blocks, inspiration sections, and footer sections if they are built as builder content.

SP Page Builder offers both a backend editor and a visual frontend editor. The visual mode is convenient because it lets you review changes directly on the page, but for careful work it is better to save major edits one at a time. Change the hero, save it, clear the cache, and review the frontend. Then move on to the destination cards. This pace feels slower, but it gets you back to a working version much faster if a specific block breaks.

What to Change First

• The first-screen headline and subheadline so they reflect your actual offer rather than a demo tour.
• The hero and card photos, because a travel template depends heavily on visual trust.
• Button links so they lead to real menu items, tour cards, or your inquiry form.
• The section order: for an agency, tours and destinations matter most; for a hotel, accommodation and stay details; for a blog, stories and itineraries.
• The page’s SEO settings in SP Page Builder page settings, if that feature is used in your editor version.

Menus and Off-Canvas Navigation

Travel Kit supports both standard navigation and an off-canvas menu. The documentation notes that the mega menu is not enabled by default in the template, but it can be turned on through menu item settings in Menu Builder. This is an important detail: do not expect a ready-made mega menu on the frontend unless you enabled it yourself.

On a travel website, the menu should stay concise. If you put every destination, tour, blog page, company page, and legal page into it, mobile navigation quickly becomes too heavy. A better approach is to keep the top level to 5-7 items and expose detailed pages through submenus, filters, cards, or internal content blocks.

Travel Pages and Booking: How to Connect the Showcase to Real Services

The official Travel Kit product page mentions SP Booking integration, destination pages, accommodation pages, and an improved booking flow. That means the visual side of the template is designed not separately from booking, but as a user journey: see the offer, review the details, choose a date or service, and move into the booking step.

In practice, the first thing to decide is which entities will be central: tours, hotels, rooms, places, transport, packages, or destinations. SP Booking as a standalone component is described by JoomShaper as a solution for rental services, travel agencies, accommodation services, car hire, villa rental, and flight booking. It includes categories, accommodation, rooms, coupons, packages, transports, places, bookings, tags, review, modules, and global settings. But the exact feature set depends on your installed version and license, so check the component panel itself rather than relying only on the demo.

Content Structure for a Travel Agency

For a travel agency, the logical chain is destination - package - detail page - booking. The homepage shows popular destinations and promo blocks. The destination page explains why the place is worth visiting, what season makes sense, which tours are available, and what is included in the package. The package page shows the itinerary, duration, price or price range, terms, images, reviews, and the booking button.

Content Structure for a Hotel or Resort

For a hotel, the focus is different: accommodation, rooms, amenities, policies, location, reviews, and date availability. Here, Travel Kit can be used as a property showcase, but tour cards are better replaced with accommodation categories, special offers, and extra services. If the booking component supports rooms and availability management, configure your accommodation types first and then connect the search module to the homepage.

Structure for a Travel Blog with Commercial Offers

If the site combines a blog with tour sales, do not mix everything into a single grid. Blog content should help users choose a destination, while commercial pages should move them toward an inquiry or booking. In the menu, you can separate Blog, Package List, and Reservation, as shown in the template’s reference structure. That way, users do not confuse inspiration content with service pages.

Test every button in the chain: hero, destination card, detail page, booking form, and the resulting email or admin record. A beautiful screen is not truly configured until the user journey works from beginning to end.

Module Positions, Footer, and Header: What Matters Specifically in a Joomla Template

In a Joomla template, a large part of the outcome depends on module positions. The Travel Kit documentation states that modules can be found under Content - Site Modules, and SP Page Builder modules are available when creating a new module and searching for SP Page Builder. That means a visible block may not be editable on the page where you expect to find it. It may be a module published into a template position.

The Travel Kit documentation for header, layout, and footer describes the predefined header, website layout, footer position, and copyright note. It also explains that the footer position uses a single SP Page Builder module in the footer1 position, while the copyright note can be changed through the module position and feature position. For a site owner, this is practical: the footer can be edited as a separate module without touching every page.

How Not to Lose Track of a Block

If a block disappears, first check module publishing rather than SP Page Builder. In Joomla, a module may be published but assigned to the wrong menu item. The wrong template position may be selected. The access level may allow only logged-in users to see it. Caching may also be enabled, so the old state remains visible after edits.

Validation Path for a Module

1. Open Content - Site Modules and find the module by name or position.
2. Check its publish status, access level, language, and assignment to menu items.
3. Compare its position with the layout in Template Options.
4. If the module was created through SP Page Builder, open its content and confirm that the selected page or builder section is published.
5. Clear the Joomla cache and browser cache, then review the page in incognito mode.

Header and Mobile Navigation

In the original Travel Kit visual reference, the header is transparent and layered over a dark hero image: logo on the left, menu in the center, booking button on the right. It looks polished, but it depends on high-contrast imagery. If you replace the hero with a light photo and no darkening overlay, the white menu will become hard to read. So when replacing hero photos, review not just the image itself, but also the navigation on top of it.

The off-canvas menu should be reviewed separately. The Travel Kit documentation states that it controls the mobile menu, sits on the right by default, and uses left alignment. After changing menu items, open the site on a narrow screen and check the menu button, the item order, and the visibility of the booking button. If a mobile user cannot reach the form or package page, the entire attractive homepage loses its purpose.

Practical Example: A Travel Agency Homepage with Itineraries and an Inquiry Flow

Let’s walk through a scenario that works well for a small travel agency. The goal is to build a homepage where the visitor sees the core offer, chooses a destination, opens a tour card, and moves to either booking or an inquiry. This is not the only Travel Kit use case, but it clearly shows how the template, pages, menus, modules, and validation all connect.

Goal

The homepage should include a hero with a concrete offer, a search or booking block, 6 popular destinations, a seasonal promo block, an inspiration content block, and a prominent booking link. The menu should include Home, Package List, Reservation, Pages, Blog, and Contacts, or their real equivalents.

Preparation

Before configuration, prepare 6 destinations, 1-2 photos for each, a short description, trip duration, a starting price or another clear commercial parameter, booking terms, and the contact path. If real pricing changes quickly, it is better to show a range or an inquiry button, while keeping exact details on the tour page and in the agreement.

Configuration Steps

1. Open the homepage in SP Page Builder Pro and replace the hero copy with a real offer, for example, "Tours across Greece, Italy, and the Alps with custom itinerary planning."
2. Replace the hero background image with your own photo that has enough darkening so the white menu and buttons stay readable.
3. In the popular destination cards, replace the names, trip durations, images, and links with real package pages.
4. Check the booking or search bar: it should point to a working component, inquiry page, or meaningful filter, not a demo URL.
5. In Content - Site Modules, review the modules related to the footer, booking, and additional content blocks.
6. In the menu settings, make sure the Book Online button points to the booking page rather than an old demo page.
7. Clear the cache and open the homepage in three states: desktop, tablet, and mobile.

Validating the Result

On desktop, it should be immediately clear what the site is selling, where to click to choose a tour, and where booking begins. On mobile, the menu should not overlap the hero, the off-canvas panel should open without horizontal scrolling, and the destination cards should remain readable. In the admin area, confirm that a submitted inquiry, booking, or user action is recorded exactly where you expect it to be.

A Common Issue That Gets in the Way

If the site looks worse than the demo after you replace the photos, the problem is not always the template itself. Travel Kit’s original design depends on high-contrast travel imagery, white typography, and a blue accent color. Random bright photos, inconsistent card proportions, and overly long destination names break that rhythm. Prepare images in a consistent style and avoid overloading cards with text.

Practical Use Ideas for Different Travel Projects

Travel Kit can be used more broadly than just a "travel agency with packages." The key is not to invent features that do not exist in your package, but to adapt the confirmed elements: visual pages, destination cards, search or booking, modules, menus, and SP Page Builder blocks. Below are several workable scenarios that can help you decide how to shape the site structure.

Website for a Local Tour Operator

Instead of hotels and resorts, use excursion cards: city walks, one-day routes, family tours, and food-focused programs. The hero should lead to date selection or an inquiry, while the destination cards should lead to specific itineraries. Result validation is simple: the user should be able to get from the homepage to an excursion description and form in two clicks.

Hotel Showcase with Weekend Packages

For a hotel, it makes more sense to focus on accommodation pages, stay conditions, extra services, and seasonal packages. The "popular destinations" block can become "stay packages": romantic weekend, family getaway, spa package, business trip. If booking is handled by SP Booking or another component, make sure the categories and room setup actually match.

Destination Portal with a Blog

If the project is content-driven, use blog pages as the entry point to commercial offers. A destination article should end with a link to relevant packages or an inquiry form. In this setup, it is important not to overload the homepage booking form: users first explore the content, then move into selection.

Seasonal Campaign Promo Site

For a seasonal campaign, Travel Kit can be used as a landing page: one hero, several offer cards, a promo block, an FAQ, and an inquiry form. But do not delete the internal pages right away. It is better to hide unnecessary menu items, keep the structure in the admin area, and return to it after the campaign ends.

Checking Quality, Performance, and SEO After Setup

After the visual setup is done, do not limit the review to whether the site "looks good." For a travel website, loading speed, indexability, accessible buttons, correct links, and a clear path to booking all matter. SP Page Builder page settings include page-level SEO options, including basic fields such as title, meta description, and robots. Joomla still provides its standard menu, article, global configuration, and SEO extension settings as well, if those are used on the site.

Functional Validation

Start with the user journey. Open the homepage as a new visitor, choose a destination, go to the detail page, click the booking button, and submit a test form or go as far as is safe for your site. If real payments are involved, test only in the payment provider’s test mode and do not run live charges just for technical validation.

Visual Validation

Check the contrast of the header over the hero image, the height of the cards, line wrapping in long destination names, the position of the booking button, the footer, and the mobile menu. In Travel Kit, some sections rely on large photos, so responsive quality often depends on cropping. If a face, building, or another important subject gets cut off on mobile, choose a different image or adjust the background position in the editor.

SEO Review

Every important commercial page should have a clear title, a unique description, and a URL that does not look like a demo page. If the page was created in SP Page Builder, check its page settings. If the page is output through a Joomla menu item or a booking component, check the settings of the corresponding menu item. Do not leave demo names such as London, Seoul, or Singapore if they have nothing to do with your business.

Performance

The main risk with a travel template is heavy imagery. The demo structure may look impressive, but real photos still need optimization: reasonable dimensions, a modern format, proper compression, and clear alt text. Do not upload a camera original into the hero section. Prepare a web-ready version first, then review speed and image quality across different screens.

A good result check sounds like this: the user sees the offer, understands the terms, moves to the right tour, opens the booking flow, and the administrator sees the inquiry or record in the correct place.

Safe Improvements Without Editing the Template Core

With Travel Kit, it is better to avoid direct edits to template files unless you manage the project like a developer with version control. Updates may overwrite changes, and even a small PHP or layout-file edit can unexpectedly affect multiple pages. It is safer to use Helix settings, SP Page Builder, Joomla language overrides, template overrides, and small CSS adjustments in the intended areas.

Localizing Labels Through Joomla Language Overrides

If you need to change a system string, button, or label, first look for it as a language constant. Joomla supports language overrides through the admin panel, and the official documentation explains that overrides let you change translations without editing the original language files. That is safer than modifying component or template files directly.

1. Open System - Language Overrides.
2. Select the Site area if the string is visible to visitors.
3. Find the required text or language constant.
4. Create the override and save the new English text.
5. Clear the cache and check the page where the string appears.

A Small CSS Fix for Hero Readability

If the navigation becomes hard to read after replacing the photo, you can add a light darkening overlay to the hero section through the page settings or custom CSS, as long as the specific block has a stable class. Do not use this snippet blindly. First, open the browser inspector and replace the selector with the real class used by your hero block.

/* Insert only into the page or template Custom CSS field.
   Replace .travelkit-hero with the real class of your hero block. */
.travelkit-hero::before {
  content: "";
  position: absolute;
  inset: 0;
  background: rgba(0, 0, 0, 0.35);
  pointer-events: none;
}

Check the result on both desktop and mobile. If the overlay blocks buttons or text, roll back the CSS and configure the overlay through SP Page Builder’s built-in settings. This tweak relies on standard CSS logic and does not require editing the Joomla, template, or component core.

Template Overrides Only for Intentional Changes

Joomla supports template overrides, but this is a tool for a developer or a careful webmaster. Use it when the default output of a module or component does not fit and CSS is no longer enough. Before creating an override, make a backup, generate the change through the template interface, leave a note in the project documentation, and test updates on a staging copy.

Why Travel Kit Does Not Look Like the Demo and How to Diagnose It

Most Joomla template problems are caused not by a "broken template," but by editing the wrong configuration layer. With Travel Kit, people most often confuse QuickStart with the template package, an SP Page Builder page with a module, menu assignment with template style, and demo photos with real images. It is better to diagnose from symptom to cause rather than changing everything at once.

After Installation, the Site Is Empty or Does Not Resemble the Demo

Symptom: the template is installed, but there is no homepage with travel blocks, destination cards, and a booking bar. A likely cause is that the template package was installed instead of QuickStart. JoomShaper’s documentation clearly separates these packages: the template package does not include demo content, modules, or SP Page Builder pages.

What to check: the page list in SP Page Builder, published site modules, the template style assignment, and the presence of the demo menu. How to fix it: if you want an exact demo-based starting point, install QuickStart on a clean test environment. If the site already exists, build the structure manually and transfer only the sections you actually need.

QuickStart Does Not Install Through the Extension Manager

Symptom: Joomla reports an error when installing the archive, or the package does not appear as a normal template. The reason is that QuickStart contains Joomla CMS and installs as a new site rather than as an extension. This is described in the Travel Kit documentation.

What to check: the archive name, the extracted contents, the presence of Joomla files, whether the directory is clean, and the database. How to fix it: install QuickStart through the browser-based installer on a clean environment. If you need a template for an existing site, use the separate template package.

Gray Placeholders Appear Instead of Photos

Symptom: after installation, gray blocks, watermarks, or image-size placeholders appear where attractive travel photos should be. A likely cause is that the demo photos are not included in the package because of licensing restrictions. JoomShaper addresses this explicitly in the documentation.

What to check: media folders, image settings in SP Page Builder, package cards, and modules. How to fix it: upload your own properly licensed images, keep the proportions consistent, and update the alt text. There is no need to roll back the setup, because this is expected package behavior rather than a malfunction.

The Mobile Menu Does Not Behave as Expected

Symptom: the off-canvas panel opens, but the items are wrong, the booking button is missing, or the submenu is awkward to use. The cause may be Menu Builder settings, off-canvas alignment, menu assignment, or an overly complex menu structure.

What to check: the Menu tab in Template Options, Joomla menu items, published menu modules, the mobile viewport, and the cache. How to fix it: simplify the top-level menu, confirm the off-canvas menu is on the right, do not enable the mega menu unless you actually need it, clear the cache, and test again.

Changes in SP Page Builder Are Not Visible on the Site

Symptom: the administrator changes a block, but visitors still see the old version. The reason may be Joomla cache, browser cache, the wrong page, a different template style, an SP Page Builder module instead of a page, or access settings.

What to check: the page URL, menu item, publish status, access level, language, cache, and whether there are similar duplicate pages. How to fix it: save changes one block at a time, clear the cache, open the page in incognito mode, and confirm exactly which object is being rendered.

The Footer Does Not Change from the Homepage Editor

Symptom: the footer is visible on every page, but it is not part of the homepage content. A likely cause is that the footer is separated into its own module or template position. The Travel Kit documentation points to an SP Page Builder module in the footer position.

What to check: Content - Site Modules, the footer1 position, assignment settings, and the module content. How to fix it: edit the footer as a module rather than as a section on each page. If you do not like the result, restore the previous module content from a backup.

When JoomShaper Travel Kit Is the Right Choice

Travel Kit is worth using if you need a Joomla template with a travel-oriented visual style, a clear demo structure, and a combination of Helix Ultimate, SP Page Builder Pro, and, when needed, SP Booking. It is especially well suited to projects where destinations, packages, accommodation, inspiration blocks, and a fast start on a clean environment all matter.

Before launch, make three final checks: the correct installation path, fully replaced demo data, and a complete user journey from the homepage to booking or inquiry. If all three are in place, you can move on to testing with real content and download the installation file for further work with the template.

Do not treat the template as a complete business process. Its job is to provide structure and interface. Your job is to fill the pages with real offers, verify the modules, configure the menus, prepare the images, test the forms, and avoid promising users anything your actual site build does not support.