JoomShaper Giver - Joomla Template

A Setup Guide to JoomShaper Giver for a Charity Website on Joomla

JoomShaper Giver is best understood not as just another attractive template, but as a ready-made framework for a foundation website, charity campaign, volunteer project, or nonprofit organization. In this guide, we will walk through how to prepare Joomla, which installation method to choose, where to edit the home page, how to work with donation, volunteer, statistics, blog, form, and module blocks, and how to verify the result after setup.

This material is intended for a site owner, Joomla administrator, or webmaster who already understands the basic logic of the CMS but wants to turn the demo template into a working organization website more quickly. We will not repeat the product's top-level description, and we will not discuss purchasing or activation. Instead, we will follow the practical path: preparation, installation, configuration, a real-world scenario, verification, troubleshooting, and choosing alternatives.

One important detail: Giver is built around Helix Ultimate and SP Page Builder Pro. That means the site's appearance, page structure, and much of its content are managed not only through standard Joomla articles, but also through the page builder, template styles, module positions, menus, and framework settings. The most common mistake after installing the template is trying to find every home page element only in modules, even though the Giver documentation explicitly states that the home page component area uses SP Page Builder addons.

All recommendations below are phrased carefully: if a specific feature is not confirmed by the documentation or the product page, it is described as a general, safe Joomla practice rather than a hidden Giver capability. Before updates and major changes on a live site, always create a backup of both files and the database.

What Problem This Template Solves

Giver addresses a challenge that almost every charity project faces: a website needs to do more than explain the mission. It also needs to quickly show visitors who needs help, which campaigns are active, how to get involved, who is already participating, and how to contact the organization. With a generic multipurpose theme, these blocks often have to be assembled manually. In Giver, most of that structure is already designed around the charity use case.

According to the official page and documentation, the template is aimed at nonprofits, donation drives, volunteer teams, children's and social projects, environmental initiatives, religious organizations, and community groups. It includes ready-made sections for campaigns, donation forms, volunteer lists, program blocks, testimonials, statistics, a blog, newsletter signup, a photo gallery, a contact page, a registration page, an error page, and a coming soon page.

That does not mean the template solves every operational need of a foundation. It does not replace an accounting system, a full donor CRM, legal documentation, a reporting-enabled payment gateway, or a nonprofit verification workflow. Its real strength is that it lets you quickly build a clear public-facing website where visitors can see campaigns, trust signals, and a path to action.

When Giver Makes the Most Sense

This template is a strong fit if the project needs an emotionally engaging home page with a prominent call to action, dedicated campaigns, and a donation form. It also works well for sites where stories, photos, reports, volunteer profiles, a blog, and a news feed matter. For a new organization, it can be a fast way to get something more useful than an empty Joomla install, namely a nearly complete site with a built-in content logic.

Another strong use case is agency work. If you are building a site for a foundation or an initiative group, QuickStart or demo data gives you a clear starting point for alignment: the client can immediately see where the call to action will go, where campaigns will appear, where volunteers will be shown, where contacts will live, and where reporting elements belong. From there, you can adapt the copy, images, and structure to the real project.

When Another Solution May Be Better

Giver may be excessive for a simple three-page brochure site with no campaigns or donations. It may also fall short if you need a complex donor portal, recurring payments, automatic tax receipts, accounting integration, or detailed CRM analytics. In those cases, the template can still serve as the visual layer, but the core functionality should be built on specialized extensions, with legal requirements checked carefully.

A practical way to think about it: decide early which parts of the site need to function as real workflows and which can remain presentation blocks. Campaigns, forms, contact pages, and volunteer applications all require data validation. Galleries, blogs, and statistics require an ongoing content process.

What to Check Before Installing It on a Site

Preparation matters for any Joomla template, but Giver has a few specifics. It depends on SP Page Builder Pro and Helix Ultimate, and QuickStart installs as a complete website, not as a standard extension inside an existing Joomla setup. If you miss that distinction, you can damage a working site or waste time using the wrong installation path.

Joomla, PHP, and SP Page Builder Compatibility

On the product page, Giver is listed as a template for current Joomla branches, and the changelog notes updates for recent versions of Joomla, PHP, SP Page Builder, and Helix Ultimate. This guide intentionally avoids locking in exact package numbers because they change faster than the article itself. Before installing, check the current download page and the developer's documentation, especially if the site is already running on an older Joomla version or a non-standard PHP version.

The SP Page Builder documentation separately emphasizes PHP, database, memory, upload size, and execution time requirements. For a template with demo content, that is not a formality: QuickStart includes pages, images, template settings, and extensions, so weak hosting may hit upload, extraction, or import limits.

A New Site or an Existing Site

The main decision before installation is whether to use QuickStart or the regular template package. QuickStart is for cases where you want a site that closely matches the Giver demo on a clean domain, subdomain, or local server. The regular template package is for cases where Joomla is already installed and already contains content, menus, users, extensions, and SEO history.

If you are unsure, install QuickStart on a separate test environment. That lets you see the real pages, menu structure, module positions, and SP Page Builder settings without putting the live site at risk.

Backup and Staging Environment

Before installing on an existing site, back up both the files and the database. Giver's update documentation explicitly recommends checking the changelog and creating a backup before major updates. In Joomla, that is not overcautious: the template may include overrides, module positions, styles, Helix settings, and dependencies on other extensions.

The minimum safe preparation looks like this:

• Create a copy of the site on a subdomain or locally if you are changing the live design.
• Verify Super User access and avoid using an obvious admin login for a fresh installation.
• Make sure Joomla folders are writable where the installer needs access.
• Check archive upload, memory, and execution time limits in PHP.
• Document the current module positions, main menu, default page, and any enabled cache plugins.

Installing Giver: QuickStart, the Regular Package, and the First Verification

The installation path depends on whether you are building a new site or applying the template to an existing Joomla installation. The Giver documentation explicitly warns that QuickStart cannot be installed through the extension manager inside an already installed Joomla site, because it is a package that includes the Joomla core and a demo website. It must be installed as a fresh Joomla site.

QuickStart for a New Site

QuickStart is the best option when you want a site that looks close to the Giver demo. The package is extracted to a server or local environment, a database is prepared, the domain or subdomain is opened in a browser, and the standard Joomla installer is completed. After that, you should remove unnecessary installation files, log into the admin panel, and verify the system status.

1. Download the current QuickStart package from the official source.
2. Extract the archive locally, then upload the files into a clean site folder.
3. Create a new database and user with the required permissions.
4. Open the domain in a browser and complete the Joomla installation.
5. Use a unique administrator login instead of an obvious default.
6. After logging into the admin panel, check System and folder permissions.
7. Review the home page, menus, form, campaigns, blog, and contact page.

QuickStart should never be installed over a live site. If you already have content, users, and SEO pages, work from a staging copy or use the regular template package.

The Regular Template Package Scenario

The regular template package is installed through Joomla's standard installer. In the admin panel, the exact path may vary depending on the interface version, but the logic is the same: open the extension installer, upload the ZIP archive, and make sure the template appears in the list of template styles. After that, it needs to be set as the default or assigned to the appropriate menu items.

In this scenario, demo pages, demo modules, and articles do not appear automatically. JoomShaper's template documentation explains that a standalone template controls the design and layout, but does not include the full demo content. That means after installation, you will need to create the pages separately, configure the menus, check module positions, and build the necessary sections in SP Page Builder.

Initial Check After Installation

Right after installation, do not start by changing colors and text. First, confirm that the template works as a system:

• Open the public site in both a regular and a private browser window.
• Make sure the home page is assigned as the Joomla default menu item.
• Open several internal pages, including contact, blog, and a campaign page.
• Check that the donation button leads where you expect it to go.
• Verify the mobile menu and the footer area.
• Clear Joomla and browser cache after the first changes.

Short version: an installation is not truly successful when Joomla shows a green success message. It is successful when you have opened the public home page, menus, key forms, and several internal screens without broken styling or empty sections.

The Home Page: Replacing the Demo with the Foundation's Real Story

Giver's home page is built around an emotional first screen, a clear call to action, and a sequence of sections: statistics, a mission explanation, a video or visual block, campaigns, volunteers, blog content, contacts, and bottom modules. Based on the local visual reference, the template uses a dark photo background with a burgundy overlay, large typography, a top menu, a Donate Now button, and social links. Below that comes a white statistics block, followed by a lighter section about the project.

It is best to edit this page not as a set of random sections, but as a trust-building journey. Within a few seconds, visitors should understand who you are, who you help, what they can do next, and why the site is credible. The demo slogan and demo photography should be replaced as early as possible, because they shape the first impression.

The First Screen and the Donation Button

The first screen needs three things: a short mission statement, a clear call to action, and an obvious path forward. If you leave a beautiful but generic message in place, the site will still feel like a template. For a foundation, it is better to be specific: who the project helps, where it operates, what results already exist, and what the visitor can do right now.

The donation button deserves separate attention. It may lead to a form page, a campaign page, or an external payment flow if that flow is set up legally and technically. Do not leave the button pointing to an empty anchor or a demo page. In the top-level menu, that button stands out immediately, so a broken link will be noticed right away.

Statistics and Proof of Impact

Giver includes dynamic statistics such as the number of people helped, geographic reach, and visual indicators. This is a strong trust block, but only if the numbers are verifiable. Do not use demo figures as temporary placeholders on a public website. It is better to show smaller but real numbers and link to a report page or blog posts that explain where the figures come from.

If statistics are not available yet, you can replace them with more honest indicators: the number of active programs, open fundraising campaigns, volunteers, published reports, or partners. The key is not to promise more than the organization can support.

Video, Story, and the Trust Block

The visual reference includes a video block with a darkened image and a play button. For a foundation, this is a good place not for a promotional clip, but for a short explanation of the mission: who is speaking, who the organization helps, how funds are used, and where reports can be found. If you do not have your own video yet, it is better to use a photo with a clear caption than a random video.

The text next to the video should answer the questions visitors usually ask before donating: who is behind the project, which programs are active, how else they can help besides giving money, and where they can verify results. This kind of block works best when it sits next to links to reports, contacts, and volunteer registration.

Campaigns, the Donation Form, and the Visitor Journey

The campaign block is one of Giver's most product-specific features. According to the official template page, it can display campaigns in a centralized list, show key metrics, and present a campaign page with the amount raised, the target amount, the end date, a description, and statistics in separate tabs. The donation form is presented as a dedicated workflow where visitors can act as individuals or on behalf of an organization.

For a real website, it is not enough to simply enable these pages. You need to design the visitor journey. People rarely begin with the form. First they see the home page, then choose a campaign, read the description, check trust signals, and only then click the donation call to action. If there is a break anywhere in that path, for example a button points to the wrong campaign or the form does not explain what the payment supports, conversion drops.

Campaign List

The campaign list should help visitors choose a cause, not turn into a decorative grid of cards. For each campaign, prepare a short title, a clear photo, a fundraising goal, the current progress, and a deadline if a deadline is genuinely part of the campaign. Keep the card description short, and move the details to the campaign page.

If you have several active fundraisers, it helps to create an internal rule: show only priority campaigns on the home page, and keep the full list on a separate page. That keeps the first screen from feeling overloaded and helps visitors avoid getting lost among similar appeals.

The Campaign Page

Use the campaign page to provide context: the problem, who needs help, what will be done, what budget is required, how the foundation verifies the outcome, and where the report will appear later. If the template outputs tabs for description and statistics, do not treat them as a formality. Use them to separate meaning. One tab can tell the story and define the goal, while another can hold numbers, stages, and evidence.

What to Check on Every Campaign Page

• The campaign title does not look like a demo placeholder and makes sense without extra context.
• The donation button leads to the correct form or the correct external flow.
• The photos are legally usable and relevant to the project.
• The amounts, targets, and percentages do not contradict the campaign text.
• The page loads properly after cache is cleared and on a mobile screen.

The Donation Form

The form in Giver is designed as an important part of the template, but it still needs to be checked for the specific site. Look at which fields are collected, which are required, where the data goes, whether administrators receive notifications, how consent is handled, and how the user understands the next step. If payments go through an external system, make sure the visitor does not lose the campaign context during the transition.

Do not turn the donation form into a long questionnaire unless there is a real reason to do so. For the first action, fewer fields and clearer wording are usually better. Additional data can be requested later if required by law or by the foundation's internal process.

Volunteers, Programs, Testimonials, and the Blog as a Trust System

Giver includes several sections that support trust rather than direct donations. These include volunteer and team member listings, program showcases, testimonials, a photo gallery, a blog, and a newsletter. If used randomly, they make the site feel like a demo. If connected into a content system, they show visitors not just an appeal, but the organization's real activity.

Volunteers and Team Members

The volunteer page is useful when the organization is genuinely ready to present people: coordinators, regional helpers, specialists, partners, or public representatives. The official page notes that Giver can display the name, role, and social links for each person, and can also use a registration form for new volunteers.

For a foundation website, it is better to separate the team from the volunteer group. The team is responsible for operations, documentation, and communication. Volunteers show the scale of participation. If you mix them into one block without explanation, it becomes harder for visitors to understand whom to contact about official matters.

Programs and Areas of Support

The program showcase on the About page should explain what the organization actually does. Avoid using it as a list of vague values such as "help," "care," or "future." It is better to name real areas of work: food assistance, education, healthcare, family support, animal welfare, disaster recovery, or environmental actions, if those are genuinely part of the project.

Each program block should lead to a page that includes a description, photos, reports, or related campaigns. That makes the site structure easier to understand: the program explains the organization's work, the campaign raises resources for a specific goal, and the blog and reports show the outcome.

Testimonials and Social Proof

A testimonial slider on a charity website requires careful judgment. Testimonials should be ethical, verifiable, and appropriate. If the content involves children, medical stories, or vulnerable groups, do not publish personal data without consent. It is usually better to feature testimonials from partners, volunteers, donors, or public representatives, and present private stories in an anonymized way.

The Blog, Gallery, and Newsletter

Giver's blog is described as a grid with featured articles and multiple columns. It is a strong place for reports, campaign updates, volunteer stories, and explanations of how donations are used. The gallery works as visual proof of activity, and the newsletter helps maintain communication with volunteers, donors, and participants.

For newsletters, the official page mentions support for different newsletter systems. In a real setup, do not stop at the signup form itself: check where the address goes, whether consent for data processing is collected, how users can unsubscribe, and who is responsible for sending updates regularly.

Template Styles, Module Positions, and the Footer Area

After installation, many users edit only the pages built in SP Page Builder and forget about Joomla's template layer. With Giver, that is risky: the documentation separately describes layout module positions, the header, bottom and footer areas, and custom code. That means part of the site's appearance and service areas is controlled through template styles, Helix Options, module positions, and menu settings.

Template Style and Menu Assignment

In Joomla, a template style can be assigned to all pages or to specific menu items. That matters if, for example, you want a separate style for the home page, campaign pages, or blog. Assigning styles through menus also helps diagnose cases where one page looks correct while another unexpectedly uses a different style.

Check not only the default style, but also its menu assignments. If a page is created in SP Page Builder but is not connected to the correct menu item or hidden menu item, some modules, breadcrumbs, titles, and SEO settings may behave differently from what you expected.

Module Positions

The Giver documentation explains that the main module positions are used in the current layout, and that Helix Ultimate Layout Builder lets you move positions, change column widths, and add rows and columns. There are also extra positions that are not visible in Layout Builder but can be used above and below the component area.

In practice, that means the following: if you add a newsletter module, menu, contact block, language switcher, social links, or HTML block, first choose the correct position and page assignment. If the module is not visible, do not blame the template immediately. Check publication status, access, language, position, menu assignment, and cache.

Checking an Invisible Module

1. Open the module in the Joomla admin panel and check its publication status.
2. Check the Position field and select a position from the active template.
3. Open the Menu Assignment tab and make sure the module is assigned to the correct page.
4. Check Access and Language if the site is multilingual.
5. Clear Joomla cache and reload the page while logged out.

Header and the CTA Button

In the visual reference, the header includes the logo, navigation, and a donation button. The header documentation notes that this area uses the logo and related elements. For a real site, check three things: the logo remains readable on a dark background, the menu does not break with long menu labels, and the donation button stays prominent on mobile.

If a localized version makes menu labels longer than the original English ones, it is better to shorten them. Do not cram every page into the top menu. On a charity website, a short path to action matters more than a complete catalog of sections.

Bottom and Footer

The Giver documentation states that the lower part of the template is built through one bottom row and four module positions together with menus and SPPB modules. This is a good place for contact information, a short menu, links to reports, legal pages, newsletter signup, and a repeated invitation to get involved.

The footer should be practical. Add the organization name, contact methods, links to your data processing policy, and the key pages. If the site accepts donations, it is useful to have a separate transparency or reports page and link to it from the footer.

Detailed Setup After the First Launch

Once the site opens and the basic installation has been verified, move on to configuration. This stage works best in a clear order: first the structure and menus, then the home page, then campaigns and forms, then modules, styles, SEO, cache, and responsiveness. If you start with colors and animations, you can spend hours on the visual layer only to discover later that the form points to the wrong place or a module appears on the wrong page.

Step 1. Menu and Home Page

Check which menu item is assigned as the home page. In the Giver documentation, the Home Page section separately shows the frontend and backend editors, as well as home page menu setup. The home item should point to the right page and have the correct title, alias, language, and template style.

For a foundation website, a useful starting menu structure looks like this:

• Home - a short path through the mission, campaigns, and participation.
• Campaigns - a list of active fundraisers and projects.
• About Us - programs, team, documents, and operating principles.
• Reports or Blog - news, outcomes, stories, and publications.
• For Volunteers - participation terms and the registration form.
• Contact - address, contact form, map, organization details, and social media.

Step 2. SP Page Builder Pages

Giver's home page and main pages are prebuilt with SP Page Builder Pro. The SP Page Builder documentation covers both the backend and frontend editors, page settings, access, language, SEO, custom CSS, and Open Graph. In Giver, this is the central working tool: it is where you edit sections, images, text, buttons, and many of the visual blocks.

A practical editing order:

1. Create a page copy or save a backup version before making major changes.
2. Open the page in the editor and replace the demo copy with real content.
3. Replace the images with your own legally usable materials.
4. Check buttons and links in every section.
5. Configure the page SEO fields if they are available in your version of SP Page Builder.
6. Save the page and review the public result in a private browser window.

Do not delete a complex section immediately if you are not sure how it was built. Disable it first, duplicate it, or create a test page. That makes it much easier to roll back if an important layout disappears.

Step 3. Campaigns and Forms

For each campaign, verify the full path from the card to the form. If you use a dedicated donation page, give it a clear heading, a short explanation, the right fields, and a clear next step after submission. If the form connects to an external payment flow, check the user's return path back to the site and the administrator notifications.

From a UX perspective, the form should answer three questions: who am I helping, what happens after I submit, and how will the foundation confirm receipt. Even if part of the payment flow happens outside Giver, the text on the template page should prepare the user and avoid creating uncertainty.

Step 4. Modules, Bottom, and Footer

Check the footer modules, menus, newsletter, social links, contacts, and copyright. The Giver documentation notes that the copyright note is based on template settings. If your organization has a legal name, it is best to use it in the footer together with links to documents and contact details.

Step 5. SEO, Open Graph, and Access

SP Page Builder lets you manage basic page parameters including title, status, language, access, and SEO fields. For a charity website, that matters not only for search engines but also for social sharing: when users share a campaign, they need to see the correct title, image, and description.

Check at minimum:

• Each important page has a clear title and a human-readable alias.
• The meta description describes the specific campaign or page, not the template in general.
• The Open Graph image works well when shared on social platforms.
• Hidden or test pages are not accidentally published.
• The correct language is selected for each page if the site is multilingual.

Step 6. Performance and Cache

SP Page Builder pages generate HTML and CSS dynamically, and Joomla Page Cache may continue serving an older version of the page until cache is cleared. The SP Page Builder documentation explicitly explains that under full caching, changes may not appear immediately. That is why after editing the home page, form, or campaign, you should clear Joomla cache, any optimization extension cache, and the browser cache.

Be careful with page cache on sites that include donation and contact forms. Joomla documentation warns that full-page caching can be problematic in scenarios where content depends on the user or on the state of a form. Static pages can be cached, but forms, private areas, and dynamic workflows should be excluded or tested separately.

A Practical Example: Building a Foundation Home Page in One Working Pass

Imagine the task: a foundation is launching a website for three active programs, wants to feature its main fundraiser, attract volunteers, and give visitors a path to reports. Giver is a strong fit for that scenario because it already includes the core structure for the home page, campaigns, forms, volunteers, statistics, blog, and footer modules.

Goal

Create a home page where the user immediately understands the mission from the first screen, sees the donation button, then finds statistics and programs below, and can continue to campaigns, the volunteer form, the blog, and contact information.

Preparation

Before starting, install Giver in a test environment, verify SP Page Builder Pro, assign the home page, and make sure the top menu and footer are visible. Prepare real materials: a logo, 3 to 5 photos, a short mission statement, campaign descriptions, contact details, social media links, and the consent text for the form if it is required.

Steps

1. Open the home page in SP Page Builder and replace the hero text with the foundation's actual mission.
2. Configure the Donate Now button so that it points to the main campaign or donation page.
3. Replace background images with legally usable project photography or neutral illustrations if real photos cannot be published.
4. In the statistics block, use verifiable numbers and label exactly what they represent.
5. In the programs block, keep only the real areas of support and add links to detailed pages.
6. In the campaign list, keep 2 or 3 priority cards and move the full list to a separate page.
7. Set up the volunteer page and registration form: name, contact details, city, availability, and preferred area of involvement.
8. Publish at least one report and one news post in the blog so the grid does not look empty.
9. In the footer, add contact details, report links, the data processing policy, and a short menu.

Verification

Open the site as a regular visitor. Follow the path: home page - campaign - donation - contact - report. Make sure the user does not land on demo pages, empty links, or English-language placeholders. Then check the mobile view: the menu, first screen, donation button, campaign cards, and form should all remain clear without horizontal scrolling.

A Common Detail

If the page looks correct in the admin panel after saving but the public version still shows the old content, the first thing to check is almost always cache. Clear Joomla cache, temporarily disable page cache for troubleshooting, reload the page while logged out, and test again in a different browser.

Practical Ways to Use Giver in Different Projects

Giver does not have to be used only for a classic foundation website with a single donation form. The template's confirmed elements, including campaigns, forms, programs, volunteers, a blog, a gallery, statistics, a newsletter, and ready-made pages, let you build several closely related scenarios. The ideas below are based on the actual template type and its real blocks, not on imagined features.

A Foundation Website with Multiple Programs

Use programs as the top level of the structure, and campaigns as the specific fundraisers within each area. For example, the "Education" program can lead to several campaigns: school supplies, scholarships, or equipment. The result is easier to verify: the program page explains the work, the campaign page shows the goal and progress, and the blog contains the report.

A Volunteer Project Without Ongoing Donations

If the project needs people more than money, shift the emphasis from the donation CTA to volunteer registration. The first-screen button can lead to the participation form, while campaigns can be used for events or actions. It is important not to hide the financial section if donations are still accepted, but the order of priorities should reflect reality.

An Environmental or Local Initiative

For local initiatives, the gallery, blog, and statistics are especially useful. Show not only the request for support, but also the map of action: how many events have taken place, how many participants joined, which areas were covered, and which reports were published. Campaigns can be used for concrete goals such as fundraising for equipment, a cleanup event, or an educational meeting.

A Campaign Website with a Short Lifespan

If you need a site for one major campaign, the home page can direct most traffic toward a single goal page. The remaining blocks then work as proof: team, testimonials, blog, contacts, and reports. After the campaign ends, do not remove the page immediately. Update it with the outcome and guide users toward the next step.

Result Check: What Should Work Before You Publish

Before opening the site to visitors, check not only the appearance but also the working logic. For a charity template, three things are critical: trust, a path to action, and the absence of technical gaps. A beautiful hero section does not make up for a broken form, an empty footer, or a module that disappears on the page where it is needed.

The Public Site

• The home page opens without errors in both regular and private browser windows.
• The top menu does not wrap awkwardly at common screen widths.
• The donation button leads to a working flow, not to a demo link.
• Campaign cards open the correct pages.
• Photos are not overly heavy and make sense for the specific project.
• The footer contains contacts, legal links, and clear navigation.

The Admin Panel and Editor

• Editors understand which pages are edited through SP Page Builder and which are edited through Joomla modules or template options.
• Access permissions do not allow accidental users to edit system pages.
• On multilingual sites, pages and modules are assigned the correct language.
• The template style is assigned correctly and does not conflict with specific menu items.

Forms, Notifications, and Security

Test every form: contact, volunteer registration, newsletter signup, donation, or any external redirect. Submit test data and make sure the administrator receives a notification and the user sees a clear message. If a form collects personal data, review the consent text and the policy page.

Do not publish test email addresses, phone numbers, demo addresses, or someone else's photos. It may seem minor, but these placeholders are exactly what most often remains on sites after a quick demo template installation.

SEO and Social Media

For the home page, campaigns, and reports, check the title, description, Open Graph image, and human-readable URLs. In SP Page Builder, some of these parameters are available at the page settings level, while others may depend on the Joomla menu item and global settings. If social previews do not update, check both cache and the tools provided by the social platforms themselves.

The key pre-launch test: ask someone who was not involved in the setup to open the site and figure out how to donate, how to become a volunteer, where to view reports, and how to contact the organization. If they get lost, the problem is not the design, but the route.

Safe Improvements Without Editing the Template Core

Giver allows for small, safe improvements through Joomla, Helix Ultimate, and SP Page Builder tools. The Giver documentation explicitly mentions Custom CSS, JS, and Meta code fields in the template settings. That means minor presentation changes are better made there, or through standard Joomla mechanisms, rather than by editing the template core files.

Strengthen the Donation Button with a Custom Class

If the CTA button is important to the site but gets lost in the menu, you can add your own CSS class to the button or block in SP Page Builder, for example giver-donate-cta, and style it through custom CSS. That approach is safer than hunting for some random template class and overriding it globally.

.giver-donate-cta {
  font-weight: 700;
  letter-spacing: 0;
  box-shadow: 0 10px 24px rgba(170, 18, 58, 0.22);
}

.giver-donate-cta:focus,
.giver-donate-cta:hover {
  transform: translateY(-1px);
  text-decoration: none;
}

How to use it: assign the class to the specific button or section through the addon settings, then paste the CSS into the template's custom CSS field. Verification: refresh the page, clear cache, and make sure only the intended button has changed. Rollback: remove the class from the addon or delete the CSS from the custom CSS field.

Language Overrides Instead of Editing Files

If some Joomla or extension system strings need to be renamed, use language overrides. This is Joomla's built-in mechanism, and it survives updates much better than editing language files directly. For text inside SP Page Builder sections, it is usually easier to edit the page itself, while system strings, modules, and components are better handled by finding the appropriate language constant.

Template Overrides Only for a Clear Purpose

Joomla template overrides are useful when you need to carefully change the output of a component or module without editing the core. But in Giver, they should be used only when the task is clear and after confirming that the output in question actually comes from a Joomla component or module rather than an SP Page Builder addon. If a block was built in SP Page Builder, first look for the solution in the page and addon settings.

If Something Does Not Display or Work Correctly

It is best to start Giver troubleshooting by identifying the layer involved: Joomla menu, template style, Helix layout, SP Page Builder page, module position, form integration, or cache. If you jump straight into editing CSS or reinstalling the template, you may hide the real cause and make rollback harder.

The Page Does Not Look Like the Demo

Symptom: after installation, the site opens, but the home page does not look like the expected demo.

The likely cause depends on the installation scenario. If the regular template package was used, demo content does not appear automatically. If QuickStart was used, check whether the installation completed fully, whether the home page is assigned, and whether any demo data was removed.

What to do: check the default menu item, template style, the presence of SP Page Builder pages, and the modules. If this is an existing site, compare it to a test QuickStart copy and migrate the structure intentionally.

The Module Does Not Appear in the Expected Position

Symptom: the module is published, but it is not visible in the header, sidebar, bottom, or footer.

Check the position, menu assignment, access, language, publication status, and cache. Giver includes positions used in the layout, as well as additional positions above and below the component area. If the wrong position is selected or the module is assigned to the wrong menu item, it will not appear where you expect it.

SP Page Builder Changes Are Not Visible on the Site

Symptom: a section is updated in the editor, but visitors still see the old text or image.

The common cause is cache. SP Page Builder generates HTML and CSS dynamically, while Joomla page cache may continue serving an older page. Clear Joomla cache, disable page cache temporarily for troubleshooting, check optimization extensions, and reload the page in a private browser window.

The Donation Button Leads to the Wrong Place

Symptom: a user clicks the CTA and lands on an empty page, an old demo campaign, or an external flow with no context.

Check the link in the menu, the button addon, the campaign card, and the form. If the button should lead to a specific campaign, do not use a generic anchor without testing it. After making the change, walk through the flow as a new user: home page - campaign - form - confirmation.

The Form Submits, but the Notification Never Arrives

Symptom: the user sees a successful submission, but the administrator does not receive an email.

Check Joomla mail settings, the recipient address, the spam folder, hosting restrictions, and SMTP. If a third-party newsletter system or external form is used, check its logs and settings. Do not consider the issue resolved until you submit a real test from a real address and receive the notification.

The Site Breaks After an Update

Symptom: after updating the template, Joomla, SP Page Builder, or Helix, the layout changes, styles disappear, or pages stop opening.

First restore or compare against a staging copy. Check the changelog, extension compatibility, overrides, custom CSS, and cache. If the issue appeared after a specific update, do not roll back blindly. Use the backup and record the package version in the project notes.

Video About Giver and What to Watch For

On the Giver launch page, JoomShaper included an overview video specifically for this template. It is useful not as a substitute for setup, but before you start assembling the site in practice: the video helps you see the overall block structure and understand which parts of the demo belong to campaigns, the form, volunteers, statistics, the blog, and built-in pages. After watching, go back to the documentation, because installation and update steps are best verified against written instructions.

Watch the video as a visual map of the product: the first screen, the campaign block, the donation form, volunteers, statistics, the blog, and the ready-made pages. For real setup work, one useful step after the video is to make a list of which demo blocks you will keep, replace, or remove.

When JoomShaper Giver Is the Right Choice

JoomShaper Giver is worth using if you need a Joomla template with a ready-made charity logic: a first screen with a strong call to action, donation campaigns, a form, volunteers, programs, statistics, a blog, a gallery, a newsletter, contacts, and built-in service pages. It is especially useful when a project needs to move quickly from an empty CMS to a clear website for a foundation or civic initiative.

Before publishing, check the installation scenario, SP Page Builder, template styles, module positions, the donation form, cache, SEO fields, and the mobile view. If the template covers your main sections after test setup, you can download the latest version of JoomShaper Giver and build the working version on a safe copy of the site.

If the project needs a complex donor CRM workflow, automated reporting, accounting integrations, or a multi-level user portal, treat Giver as the visual and content foundation rather than the full functional system. In that case, design the extension architecture first, and only then choose the template for the presentation layer.