JoomShaper Fortune - Joomla Template

Guide to Setting Up JoomShaper Fortune for an Elder Care Website

JoomShaper Fortune is a Joomla template best viewed not as an empty shell, but as a ready-made foundation for a care center, retirement home, charity initiative, or senior support service website. In this guide, we will walk through how to approach installation, how to choose between Quickstart and the standalone template, which demo sections actually matter, and where to edit the header, homepage, module positions, footer, and custom styles.

This article does not repeat the product's short description. The focus here is on practical implementation: how to deploy the template safely, how to replace demo data with real content, how to connect pages to menus, how to check the result on the front end, and what to do if images, modules, or the expected layout do not appear after installation.

Special attention is given to Joomla-specific details: template styles, module positions, menu item assignments, the Quickstart package, Helix Ultimate, and SP Page Builder Pro. This approach helps you do more than just preview a polished demo page - it helps you turn Fortune into a manageable website that an editor, administrator, or small team can actually maintain.

What This Template Is Designed to Solve

Fortune makes sense when a website needs to explain a service, build trust, and lead visitors toward action at the same time. A standard corporate site can get by with a services page and contact details, but that is not enough for senior care. Visitors need to see who provides the care, what programs are available, how events are organized, where stories are published, how donations are used, and how to reach the organization without unnecessary friction.

The official JoomShaper product page presents Fortune as a template for care institutions, retirement homes, and charity or social initiatives. It includes two homepage variations: Senior Care for a service-based organization and Old Age Home for a nonprofit scenario. That distinction matters. The first layout is a better fit for an agency or center that sells care services, while the second works better for an organization where donations, events, statistics, and social impact matter more.

The template becomes truly useful only after demo content has been replaced with real materials: team photos, service descriptions, clear campaign pages, local contact details, event schedules, and authentic stories. If you leave Fortune as a collection of attractive blocks, it quickly starts to look like any other demo theme. If you configure it intentionally, the template becomes a site structure where every block helps a visitor make a decision.

When Fortune Is an Especially Good Fit

The template works well when the site is built around trust, regular communication, and several content types. For example, an organization may need a services page, caregiver and volunteer profiles, event listings, donation collection, a gallery, and a blog with guidance for families. All of that aligns with what is described on the product page: services, teams, events, donation and fundraising pages, Memory Wall, Gallery, Blog, and built-in contact pages.

Fortune is also convenient if you need a working structure quickly on a test domain. The Quickstart package deploys a full site with Joomla, the template, demo data, Helix Ultimate, and SP Page Builder Pro. It is not just a theme with no content - it is a working reference build that lets you see which modules, positions, and pages the developer actually uses.

When It Makes More Sense to Choose Another Path

Fortune may be overkill if you need a minimalist two-page site with no events, blog, gallery, fundraising sections, or complex header. It is also not the best choice for a project where the entire design must be fully custom from scratch and the team does not want to rely on page builder editing. In that case, it is often simpler to start with base Helix Ultimate, YOOtheme Pro, or a custom template and build only the blocks you actually need.

One more important point: Quickstart cannot be installed over an existing site through the extension manager. If you already have a working Joomla site with content, Fortune needs to be introduced more carefully: install the Template Pack, move or create pages, configure modules, verify positions, and only then switch the default style. For an existing site, that path takes longer, but it reduces the risk of damaging the current structure.

What to Check Before Installation

Before installing the template, you need to think through not only technical issues, but editorial ones as well. Fortune gives you ready-made visual sections, but you cannot launch a high-quality senior care website without real photos, clearly described services, up-to-date contact details, and verified legal wording. JoomShaper documentation specifically notes that demo images may not be included in the package due to licensing restrictions, so it is best to prepare your image replacement plan in advance.

The technical review starts with your Joomla version, PHP version, database setup, upload limits, and execution time. Fortune documentation recommends checking server requirements before installing Quickstart and keeping in mind that the package includes not only the template, but also the CMS, demo data, extensions, and their settings. If the server is weak, installation may stall during table creation or finish with incomplete data.

Minimum Preparation Checklist

It is best to go through this checklist before uploading the archive to the server. It does not replace your hosting documentation, but it helps catch common issues early.

• Create a separate staging site or subdomain if you plan to explore Quickstart.
• Prepare a new database and a separate database user so demo data does not get mixed with your live site.
• Check PHP limits: memory size, maximum upload size, and maximum execution time.
• Gather real photos, your logo, contact details, address, phone number, email, and service copy.
• Decide which homepage variation you need: service-oriented Senior Care or nonprofit Old Age Home.
• Prepare a list of pages that should appear in the main menu: services, events, memory, blog, contacts, donations.
• Decide who will edit pages in SP Page Builder and who will be responsible for Joomla modules.

Test Fortune on a copy of the site or on a staging domain first. For a new website, this saves time. For an existing one, it protects your live menus, modules, and content from accidental overwrite.

Why Photos and Demo Data Should Not Be Treated as Production Content

Fortune's visual style is built around trust-based photography of seniors, staff, events, and charitable content. But demo images are meant to showcase the design, not to be used commercially. If you see gray placeholders or different images after Quickstart installation, that is not a template bug. It is an expected result of demo asset licensing.

In practical terms, this means you should replace the hero image, event cards, team photos, gallery content, and Memory Wall materials before launch. For a site like this, it is especially important not to use random stock visuals. Use your own photos, licensed stock images, or media with clear usage rights. On a care website, trust is shaped not only by the text, but by how honest and appropriate the visuals feel.

Quickstart or Template Pack: Which Option to Choose

Fortune has two different installation scenarios, and they should not be confused. Quickstart is a full copy of the demo site with Joomla, the template, components, modules, demo pages, and settings. Template Pack is the standalone template for an existing Joomla installation, without ready-made content and without automatic creation of all pages. JoomShaper documentation states this directly: Quickstart is meant for a new site or a test environment, while Template Pack is for an existing site.

The most common mistake is trying to install Quickstart through the Joomla extension manager. That does not work, because Quickstart already includes Joomla. It must be installed like a new site: extract the archive, upload the files to the server, create a database, open the domain in a browser, and go through the installer.

When to Install Quickstart

Quickstart is convenient when you are starting from a clean environment and want a site that looks as close to the demo as possible. This is especially useful for Fortune because the template is tied not only to appearance, but also to a specific page set: homepage variations, donation pages, fundraising campaigns, events, Memory Wall, gallery, blog, contacts, and utility pages. After installation, you can open the admin panel and study which pages are built in SP Page Builder, which modules are published in which positions, and which menu items are set as primary.

For beginners, Quickstart is often helpful even if the final site will be built differently. You can deploy it locally or on a subdomain, inspect how the blocks are structured, and then recreate the parts you need on the live site. This avoids blind configuration, where the administrator sees only an empty template and has no idea which modules should appear in the header, footer, or side areas.

Practical Quickstart Installation Order

1. Extract the Quickstart archive locally so you upload the already unpacked files and folders to the server.
2. Create a separate database and a user with the required privileges.
3. Upload the files to the root folder of the domain, subdomain, or test directory.
4. Remove any extra index.html file from the root if your hosting created it automatically.
5. Open the domain in a browser and go through the standard Joomla installer.
6. Do not use admin as the name of the primary administrator.
7. After installation, check the front end, admin panel, main menu, and homepage.
8. Rename htaccess.txt to .htaccess if you use that URL setting and your server supports it.

After installation, do not rush to delete the demo pages. First, create your own map of the site: which pages control the homepage, which modules are used in the header and footer, and which content appears in events, the gallery, and the blog. Then start replacing the demo content step by step.

When to Install Template Pack

Template Pack is the right choice if the site already has content, menus, users, and an existing structure. It installs like a regular Joomla extension, but it does not create a complete Fortune demo page. So after installation, you will see the template, but you will not see the full demo site automatically. You will need to assign the template style manually, configure menus, create pages or recreate them in SP Page Builder, publish modules into positions, and verify the output.

For an existing site, this is the safer path. You are not replacing all content with a demo build - you are introducing the new design gradually. But there is a cost: you need to understand module positions and menu item assignments. If your team is not familiar with Joomla modules, deploy Quickstart separately first and use it as a reference.

Homepage, Header, and Footer Without Random Edits

Fortune's homepage should not be configured by guesswork. The documentation states that the homepage variations are built in SP Page Builder Pro, and the active homepage is selected through Menus and Main Menu: the required menu item is marked as the homepage using the toggle in the Home column. This is standard Joomla logic, and it matters more than any attempt to edit URLs manually.

The header in Fortune pulls from several sources. Contact details such as phone, email, and address are configured in the template settings under System - Site Template Styles - Fortune - Template Options - Basic - Contact Info. The tagline in the top bar is implemented as the custom module Our Tagline, published in the top1 position. That means part of the header is edited in template options, while another part is managed through modules.

How to Choose a Homepage Variation

Fortune has two homepage models. Senior Care is designed for a service-focused organization: a hero section with a call to action, services, team-driven visuals, trust-building blocks, and contact elements. Old Age Home is closer to a nonprofit structure: donations, statistics, events, teams, and social mission. The choice should not depend only on which screen looks better.

Ask yourself three questions. First: should the visitor request a service or support an initiative? Second: is the main user path built around contacts, a form, events, or donation pages? Third: who will update the site most often - a service manager, an events editor, or a fundraising coordinator? The answers will help you choose the right homepage menu item and avoid mixing two scenarios without a reason.

What to Check After Assigning Home

• Open the front end while logged out and verify that the root URL points to the correct variation.
• Clear the Joomla cache and browser cache if you still see the old homepage.
• Check that the active menu item is highlighted correctly in the header.
• Review the menu item metadata if you use different SEO settings for the two homepage variations.

Header: Contacts, Tagline, and Menu

Fortune's header makes an impression in the very first screen: the top bar, contact details, logo, main menu, and login button establish trust before the visitor even reads about your services. So do not leave the demo phone number, email, or address in place. Replace them in Contact Info, then find the Our Tagline module and decide whether you need a tagline at all.

If the tagline does not fit the organization, it is better to disable the module than to leave a generic phrase. If you do need one, keep it short. The top bar should not compete with the main menu. For a care organization, a simple line about access to support, consultation hours, or a key contact point is enough.

Footer: Five Positions and Social Links

Fortune documentation describes the footer area as a set of five module positions: bottom1, bottom2, bottom3, bottom4, and bottom5. In the demo, they are used for the logo, menus, additional menus, and a block with a heading or subscription form. Social links are managed through Template Options - Basic - Social Icons.

For a real site, the footer works best as a reference hub: a short description of the organization, services, useful pages, legal materials, contact details, and a clean subscription form if you actually use one. If there is no newsletter, do not leave an empty form in place. A blank or non-working opt-in is worse than a simple contact block.

Module Positions and SP Page Builder: How Not to Lose Blocks

In Joomla, the template defines where modules can be displayed. Fortune uses positions that can be rearranged through Layout Builder in Helix Ultimate. Fortune documentation specifically notes that Layout Builder lets you move positions, change column widths, and hide elements on different devices. In practice, that means the page layout depends not only on the article or SP Page Builder page, but also on which modules are published, which position they use, and which menu items they are assigned to.

If a sidebar, menu, breadcrumb trail, or below-content block disappears after installation, the problem is often not the template itself. You need to check module publishing, position assignment, menu assignment, and Helix display settings. Fortune also includes additional Content Top and Content Bottom positions that do not appear in Layout Builder but can be used to display modules above and below the component area.

Where the Template Ends and the Page Begins

It is important to distinguish three layers. The first layer is the Fortune template style and its options in Helix Ultimate. It controls the header, footer, layout, base typography, social icons, custom code, and some global parameters. The second layer is Joomla modules, displayed in positions such as top1, bottom1, or other available areas. The third layer is the pages built in SP Page Builder Pro, where the homepage sections, service blocks, cards, images, and more complex layouts live.

When you edit text inside an SP Page Builder page, that does not necessarily change the menu or footer. When you edit a module in the bottom3 position, that does not necessarily change the page content. When you change a menu item, it may affect both the homepage and the set of visible modules. That kind of multi-layer structure is normal in Joomla, but you need to keep it in mind.

How to Check Module Positions

Start in the Joomla admin panel: open Content - Site Modules or the corresponding module section in your version of the interface, find the required module, and check its publish status, position, and menu assignment tab. If the module is supposed to appear in the header or footer, compare its position with Fortune documentation. If the module should appear only on a specific page, make sure the menu assignment is not limiting it by accident.

For quick diagnosis, you can enable template position preview in Joomla settings and open the front end with the ?tp=1 parameter, if your configuration allows it. This shows a map of template positions and helps you understand where exactly the template expects the module to appear. After testing, it is best to disable preview mode again.

Typical Module Verification Chain

1. The module is published and not in the trash.
2. The module position exists in Fortune or was added through Layout Builder settings.
3. The Menu Assignment tab allows the module to appear on the required page.
4. The access level does not hide the module from guests.
5. The cache has been cleared after changing the position or assignment.
6. In Helix settings, the module area is not hidden for the current device.

Content Blocks That Make Fortune Distinctive

Fortune includes several blocks that cannot simply be moved into any template without losing their meaning. These include donation and campaign pages, Memory Wall, gallery, events, team blocks, pricing models, and the specialized homepage variations. They should not be treated as decoration. Each of these sections answers a specific visitor question: who the organization helps, how to support the initiative, which services are available, who works with seniors, what events are taking place, and where to see real moments from the life of the center.

Before editing, it is best to create a content map. This is not a table for publication, but an internal team reference: which demo page exists, what real content will replace it, who is responsible for updates, and how to verify that the block has not become empty. Without this map, Fortune can easily turn into an attractive storefront full of demo phrases.

Donation and Fundraising Pages

The official product page presents donation and fundraising as important parts of the template. In a nonprofit scenario, this is not just a button in the hero area. The visitor should understand the campaign goal, see progress, choose a clear action, and receive enough context to trust the page. If your site version uses a donation form, check every field, message, payment method, and legal text based on your organization's rules. If you are not ready to accept real donations yet, it is better to replace that block with a support page or contact page than to leave a non-working form in place.

For a service center, the donation block may be unnecessary. In that case, remove it from the homepage and replace it with a consultation, services page, or contact form. The template does not force you to use every demo section. Its strength is that the blocks can be rearranged and adapted.

Memory Wall and Gallery

Memory Wall and Gallery work as the emotional layer of the site. But this is also where care matters most: photos, names, stories, and publication consent all need to be verified. If the organization does not maintain a section like this, do not fake one for the sake of design. A better alternative is an event gallery, a gratitude page, photo reports, or a team stories block.

Check not only the appearance, but also performance. A gallery full of heavy images can slow down both the homepage and internal pages. Prepare images in advance: compress them, give them clear file names, verify alt text, and do not upload raw camera originals without optimization.

Events and Blog

Events in Fortune are useful for centers that run meetings, volunteer programs, open house days, lectures, or charity activities. Every event should include a date, location, description, contact point, and clear status. If an event has ended, decide whether it should remain as part of the archive or disappear from the active list.

The blog, with its two variations, can become a knowledge base for family members and residents: articles about preparing for care, choosing a program, rehabilitation, psychological support, documents, and schedules. But do not publish random news just to fill the grid. Fewer posts are better if each one answers a real audience question.

Practical Ways to Use Fortune for Different Sites

What makes Fortune interesting is that the same set of template blocks can be turned into different working scenarios. The key is not to mix everything at once. If the site sells services, the first goal is an inquiry or a call. If the site collects donations, the first goal is to explain the campaign and establish trust. If the site helps families navigate care, the first goal is clear navigation and useful resources.

Care Center Website with Services

For a commercial or private care center, make Senior Care the main variation. In the hero area, keep a clear contact-focused call to action, replace donation buttons with a consultation or services page, and use the caregiver blocks for your team. The first-level menu should include services, team, pricing or programs, reviews, blog, and contacts. After setup, test the visitor journey: from the homepage, they should be able to reach a specific service and find a way to get in touch within two or three clicks.

It is especially useful to feature not every service on the homepage, but three to five key offerings. The rest can stay on an internal page. That keeps the hero and first sections from becoming overloaded, while Fortune preserves a clean visual rhythm.

Nonprofit Project or Retirement Home

For a nonprofit scenario, it makes more sense to start with Old Age Home. Use fundraising campaigns, statistics, events, Memory Wall, and gallery. But replace every demo number with a real one, or remove it for now. Donation totals, participant counts, and campaign progress should all be verifiable. If the organization is not ready to update this data regularly, make the blocks more static instead: goals, reports, stories, and transparent contact details.

Checking the result is simple: a new visitor should understand what the organization does, how to support it, where to view active campaigns, and who to contact with a question. If those answers are hidden below the third screen or only in the footer, the homepage needs reworking.

Informational Resource for Families

Fortune can also work as a knowledge-focused care website. In that case, the blog, events, FAQ, gallery, and contacts become more important than donation pages. The homepage should be built around useful paths: how to choose a service, how to prepare a relative, which documents are needed, how to book a consultation, and what events take place at the center.

SP Page Builder makes it easy to create several informational sections with cards and links. But make sure the cards lead to real content, not empty demo pages. A site like this benefits from a clear menu structure and careful internal linking.

Local Website with Events

If the organization runs frequent events, use the events section as a standalone branch of the site. Show the next upcoming event on the homepage, add an archive to the menu, and include quick links to contacts and registration in the footer. For every event, verify the address, map, description, and status. If registration is required, the form should be tested before publication.

Practical Scenario: Launching the Homepage of a Care Center

Below is a specific example you can reproduce on a staging environment. The goal is to create a homepage for a care center where visitors immediately see services, a trust-building section, the team, events, and a clear contact path. This example does not require editing the Joomla core or template files. It relies on Quickstart, SP Page Builder, menu items, and modules.

Goal and Preparation

You need to turn the demo Senior Care variation into a working homepage for an organization that provides care services. Before you start, you should already have either Quickstart installed or Template Pack with pages created manually, access to the Joomla admin panel, a prepared logo, phone number, email, address, three to five services, team photos, and text for the hero section.

Setup Steps

1. Open Menus - Main Menu and assign the required Senior Care menu item as the homepage.
2. Open the page in SP Page Builder and replace the hero heading, subheading, and buttons with real actions: consultation, services, or contact.
3. In the services block, keep only the directions the organization actually provides.
4. Replace the hero, team, and card images with legal photos that have clear alt text.
5. In System - Site Template Styles - Fortune - Template Options, verify the contact details in Contact Info.
6. Open the Our Tagline module in position top1 and replace the tagline or disable the module.
7. Check the footer positions bottom1 - bottom5: remove empty links and configure menus, contacts, and social icons.
8. Clear the Joomla cache and open the site in a private browser window.

Expected Result

The homepage should no longer look like a demo site, but like a real page with genuine contacts and clear user paths. The hero buttons should lead to working pages, the menu should not contain empty items, the footer should help visitors quickly find services and contact details, and the photos should not look like placeholders. If a visitor can understand the center's focus within the first few seconds and quickly find a way to get in touch, the base setup is working.

What Can Go Wrong

If you still see the old text after saving, check whether you are editing the active page that is assigned as the homepage. If a header module disappears, check its position and menu assignment. If the images do not match the demo, remember the licensing restrictions on demo photography. If a button leads to an error page, check the menu item or the link inside SP Page Builder.

Quick takeaway from this scenario: a Fortune homepage is not assembled through a single setting, but through the combination of the Home menu item, SP Page Builder content, Template Options, and Joomla modules. You need to verify all four layers.

Safe Improvements Without Editing the Template Core

Fortune already includes visual controls through Helix Ultimate and SP Page Builder, so code is not always necessary. But sometimes a small CSS adjustment is useful: highlighting a reference block, gently strengthening a button, or styling a notice on a services page. Fortune documentation allows CSS and other custom code to be added through the Custom Code section in template settings, but explicitly warns against using PHP inside template options. So the safe route is a small CSS snippet applied to your own custom class.

The example below does not rely on hidden Fortune classes. You add the fortune-care-note class yourself to a section, column, or addon in SP Page Builder, and then insert the CSS into Custom Code. This approach survives updates better than editing template files directly, and it is easy to roll back by removing either the class or the CSS block.

.fortune-care-note {
  border-left: 4px solid #f05a28;
  background: #fff7f3;
  padding: 18px 22px;
  border-radius: 6px;
}

.fortune-care-note h3,
.fortune-care-note h4 {
  margin-top: 0;
}

.fortune-care-note a {
  font-weight: 600;
}

Where to use it: for example, on a services page section where you explain the consultation process, required documents, or visit conditions. After adding the CSS, clear the cache and check the page on desktop, tablet, and phone. If the style conflicts with the color system, reduce the background intensity or remove the rule. Rolling back is simple: remove the fortune-care-note class from the SP Page Builder block or delete the CSS from Custom Code.

Do not add custom JavaScript unless you actually need it. For a care website, template settings, modules, and CSS are usually enough. Scripts should only be used for a clearly defined task that cannot be solved with Joomla, Helix, or SP Page Builder, and only after testing on a staging copy.

Checking the Result Before Publishing

Reviewing Fortune should go beyond making sure the page opens. You need to confirm that the correct homepage variation is selected, modules are visible on the right menu items, images have been replaced, forms and buttons do not lead nowhere, and the site displays properly on mobile screens. For a template like this, trust and accessibility matter especially much: the visitor may be a senior's family member, a volunteer, or a donor, and unnecessary confusion quickly erodes trust.

Front-End Review

• Open the homepage while logged out and check the hero section, menu, contact bar, and first call-to-action button.
• Go through every main menu item and make sure there are no demo pages with empty content.
• Verify that donation, events, Memory Wall, gallery, and blog are used only where they actually make sense.
• Open a service page and make sure there is a contact path: phone number, form, address, or consultation link.
• Check the footer: menus, social icons, contacts, subscription, and legal links.

Admin Panel Review

In the admin panel, verify the active Fortune style, the homepage menu assignment, module status, and access permissions. If editors will be working in SP Page Builder, give them only the permissions they actually need and explain which blocks they are allowed to change. For small teams, it is useful to create a short internal guide: where to update the phone number, where to edit the hero section, where to update events, and where the blog pages live.

Performance and SEO Review

The template itself does not guarantee fast loading or strong search performance. Results depend on images, caching, extensions, fonts, hosting, heading structure, and content quality. After replacing photos, check file sizes and lazy loading. For every important page, set a title, meta description, readable alias, and one clear main heading in the content, keeping in mind that the site page already has its primary H1.

Do not judge SEO by the fact that a template exists. Judge it by whether the page answers the visitor's intent: care services, visiting rules, pricing or programs, events, contacts, support, donations, and trust-building information.

If Fortune Displays Incorrectly: Symptoms and Diagnostics

Problems with Joomla templates often look similar: the wrong homepage is shown, a block disappears, a module is missing, the demo does not match the preview, or Quickstart hangs during installation. But the causes vary. Below is a diagnostic guide specifically for Fortune, Helix Ultimate, SP Page Builder, and the Joomla module system.

Quickstart Does Not Install or Freezes

Symptom: the installer gets stuck for a long time during table creation, shows a server error, or returns an incomplete site. Possible cause: server limits, unsuitable PHP settings, a database issue, or an attempt to install the package as something other than a new site. What to check: Fortune requirements, memory limit, maximum execution time, database user permissions, and whether the installation directory is clean.

Fix: increase limits on the staging site, create a new database, and confirm that Quickstart was extracted and uploaded as a full Joomla site. If you do not control the PHP settings, send the exact symptom to your hosting provider and ask them to verify the requirements. Rollback: remove the incomplete installation and start over with a clean folder and database instead of fighting with half-imported demo data.

The Homepage Does Not Change After Selecting Another Layout

Symptom: you edit the page or menu item, but the public homepage stays the same. The reason is often that a different Main Menu item is assigned as the homepage, or you are editing the wrong SP Page Builder page. What to check: the Home column in the menu, the alias of the active item, the linked page, and the cache.

Fix: assign the correct menu item as the homepage, save, clear the cache, and check the site while logged out. If your site uses hosting-level caching or a CDN, clear that as well. Rollback: restore the previous homepage menu item.

The Module Is Published but Not Visible on the Page

Symptom: the module exists in the admin panel, but it does not appear on the public page. Possible causes: the wrong position, a restriction on the Menu Assignment tab, access level, a disabled area in Helix settings, or cache. For Fortune, pay special attention to header and footer positions, as well as the additional Content Top and Content Bottom positions if the module should appear near the component.

Fix: switch the module to an existing position, allow it on the required menu item, confirm Public access, and clear the cache. If the module should appear on a detailed article page but is missing from the sidebar, check Helix Options - Blog - Details - Disable Modules; Fortune documentation notes that this parameter must be turned off for sidebar modules to appear in single article view.

The Demo Looks Poorer Because Images Are Missing

Symptom: placeholders appear instead of polished photos, or some images differ from the preview. This is usually not a malfunction. The documentation explains that demo photos may be excluded from the package for licensing reasons. What to check: which images are actually available in the media manager, which blocks need replacements, and where demo placeholders are being used.

Fix: prepare your own images and replace them in SP Page Builder, the gallery, events, and cards. No rollback is needed if you saved copies of the demo pages in advance. If the layout breaks after replacement, check image proportions and file size.

Custom CSS Is Not Applied

Symptom: the CSS has been added, but the appearance does not change. Causes: the class was not assigned to the block, the rule is being overridden by a more specific style, the cache was not cleared, or the code was inserted in the wrong place. What to check: whether the class exists in the HTML, rule order, Joomla cache, browser cache, and the correct path to Custom Code.

Fix: assign your custom class through SP Page Builder, make the rule slightly more specific, clear the cache, and test while logged out. If the site uses security extensions, they may filter some code injections. In that case, it is better to use the standard custom stylesheet file or a dedicated module instead of overcomplicating template options.

When JoomShaper Fortune Is a Strong Choice

Fortune is worth using if you need more than just a visually polished Joomla shell - you need a ready-made subject-specific structure for a care service, retirement home, charity project, or social support website. Its strengths are the two homepage variations, service and trust-oriented pages, donation and fundraising scenarios, Memory Wall, gallery, events, blog, Helix Ultimate, SP Page Builder Pro, and clear documentation for configuring the key areas.

Before launch, check the essentials: the site was installed using the correct package, the active homepage is assigned through the menu, contact details have been replaced, module positions have not been lost, demo photos have been swapped for legal images, and the user journey is clear without administrator guidance. If those conditions are met, you can download JoomShaper Fortune, deploy it on a staging environment, and work through the setup calmly using the steps in this guide.

The best result comes not from an instant demo import, but from careful editorial adaptation: keep Fortune's strong visual rhythm, replace demo blocks with real content, and verify every link in the chain of "setting - module - menu item - front-end result."