JoomShaper Delacroy - Joomla Template

How to Set Up JoomShaper Delacroy for a Joomla Digital Agency Website

JoomShaper Delacroy is best viewed not as a standalone attractive skin, but as a ready-made foundation for an agency, studio, consulting team, or service portfolio website. In this guide, we will walk through how to prepare a Joomla site for the template, when to choose QuickStart, what to review in Helix Ultimate and SP Page Builder Pro, and how to set up the homepage, menu, modules, portfolio, blog, and contact flow.

This article does not repeat the product's short description. What matters here is the practical logic: which decisions to make before installation, how not to get lost in demo pages, where the visual layout usually breaks, what to do with module positions, how to validate the result on the public-facing site, and when this template may not be the best fit.

We will also cover how to diagnose common problems: sections do not appear, styles are not applied, the menu links to the wrong place, modules are missing from the pages where they should appear, or the page looks different from the demo after editing it in the builder. This approach helps you turn the template into a working site safely, instead of simply importing the demo and leaving it in a half-finished state.

What This Template Is Designed to Do

Delacroy is aimed at websites that need to showcase expertise, visual identity, services, case studies, and a clear way to contact the team quickly. According to the official JoomShaper product page, the template includes ready-made pages for the homepage, services, projects, blog, team, company information, and contacts. This is not a universal corporate template for every possible use case. Its strength lies in its bold promotional structure for an agency or creative team, where the hero section, service sections, and portfolio work together.

The attached visual reference makes Delacroy's character clear: a large hero area with photography, a vivid pink and purple palette, dense color blocks, oversized typography, service cards, portfolio sections, and an art-directed aesthetic. That style can help a website stand out, but it also requires careful adaptation. If you only swap the logo and leave the demo content in place, the page may look impressive, but it will not explain the real business.

The main practical goal is to transfer the demo structure to your own content without losing the rhythm of the sections. For an agency, that means defining 3 to 5 services, preparing case studies, bringing photos and graphics into a consistent visual style, setting up a clear menu, adding a working contact form, and making sure every section leads the visitor to the next action.

When Delacroy Works Especially Well

This template is a strong fit when the site should feel more like an agency presentation than a reference library with dozens of similar entries. It works well for a digital studio, design bureau, content team, marketing agency, creative shop, small consulting firm, freelancer portfolio with services, or a promotional site for a project team.

For sites like these, not only the text matters, but also the sequence of impressions: first the visitor sees the positioning, then quickly understands the services, then looks at the case studies, reads supporting materials, and moves to contact. Delacroy already provides that narrative flow, but you still need to fill it with real proof instead of generic claims.

When Another Option Makes More Sense

This template may not be the right choice if you need a strict portal, a catalog with hundreds of similar cards, an online store centered around product filters, a news site with a dense content grid, or minimalist documentation. The vivid palette and oversized sections will get in the way if the main goal is to help users compare a large amount of data quickly.

Delacroy also depends heavily on visuals. If the team has no visual assets, case studies, work screenshots, or at least polished illustrations, the demo structure will start to feel empty. In that case, it makes more sense to prepare a content package first and install the template afterward.

What to Check Before Installation

Preparation matters because a Joomla template rarely exists on its own. It depends on the CMS version, extensions, demo data, the installation method you choose, access permissions, and the site's existing content. On the official page, Delacroy is listed as a template for Joomla 4, Joomla 5, and Joomla 6, and JoomShaper usually documents server environment compatibility and required extensions separately for its templates. Before installing, do not guess. Check the package contents and the documentation for your exact version.

If the site is new, QuickStart is the fastest path. It is a ready-made Joomla package with demo data, the template, and related extensions. If the site is already live, QuickStart is almost always risky because it deploys a full website, not just a single template. For an existing project, it is safer to install the template package and required extensions separately, then recreate or migrate the demo manually or selectively.

Quick Pre-Launch Checklist

• Confirm that your Joomla version matches the template package and is supported by your hosting environment.
• Create a full backup of files and the database before installing anything.
• Check whether the package includes QuickStart, the standalone template, SP Page Builder Pro, and any additional extensions.
• Decide where you will test the template: a local server, a subdomain, or a staging copy.
• Prepare your logo, brand colors, service list, 3 to 6 case studies, contact details, and homepage copy.
• Make sure the site is not running active optimization that combines and minifies CSS/JS before setup is complete.

Safe rule: first repeat the installation on a test copy, document the working sequence of steps, and only then move the template to the production site. This is especially important if the site already has users, forms, multilingual content, or custom modules.

What Content to Prepare in Advance

Delacroy is built around strong visual sections. That means content preparation should follow the structure of the future page, not a "we'll replace it later" mindset. For the hero section, you need a short headline, a subheadline, a photo or visual scene, and a clear primary action. For the services section, prepare service names, a brief explanation of the outcome, and icons or cards. For projects, you need work images, project context, and links to details. For the blog, you should have at least a few posts that demonstrate expertise.

If you do not have much content yet, do not try to fill every demo block with random filler text. It is better to disable extra sections in SP Page Builder temporarily than to show visitors an empty or misleading portfolio. In Joomla, that is usually easier to do by disabling rows, hiding modules, or changing menu assignments.

QuickStart or Manual Installation: Choosing the Safer Path

JoomShaper templates usually support two different installation scenarios. QuickStart is for when you want a site that looks almost exactly like the demo, with sample pages, menus, modules, template settings, and related extensions. Manual installation is for when the site already exists and you do not want to overwrite the project structure. A common mistake among Joomla site owners is choosing QuickStart when they actually need the standard template package.

For a new site, QuickStart saves time. You get not an empty shell, but a demo framework that makes the developer's intent easier to understand: which pages are tied together by the menu, which modules are used in which positions, how the homepage is assembled in SP Page Builder, where the blog is used, and how contacts are presented. Still, QuickStart should be treated as a starting copy, not as a finished production site. After installation, you still need to replace the demo assets, verify permissions, configure email, review SEO settings, and check performance.

For an existing site, manual installation gives you more control. First you install the template, then the required extensions, and then you create or import the necessary pages. This approach takes longer, but it does not break existing content, menu items, users, or extensions. It is especially important if the site is already indexed by search engines or receives real form submissions.

QuickStart Scenario for a New Site

1. Create a separate database and a clean site folder.
2. Upload the QuickStart package to the server or local environment.
3. Run the standard Joomla installer and enter the database connection details.
4. After installation, sign in to the admin panel and verify that the demo pages, menus, and template are active.
5. Immediately change the administrator credentials, configure site email, and disable unnecessary demo content.

After QuickStart, do not rush into editing every page at once. Start by opening the homepage, services pages, project pages, blog, and contact page. Note which blocks you need, which ones should be removed, and which ones should be moved to other pages. That review saves time because it keeps you from breaking the layout through random edits.

Manual Installation Scenario for a Live Site

1. Create a backup and make a test copy of the site.
2. Install the template package through System and Joomla's extension manager.
3. Install or update the dependencies listed in the JoomShaper documentation.
4. Open System, then go to the templates section and create a separate style for Delacroy.
5. Assign that style to the appropriate menu items instead of the entire site at once if you are testing the design gradually.
6. Rebuild the homepage in SP Page Builder or manually migrate the sections you need from the demo.

With manual installation, it is useful to create a separate menu item for a test page, block it from indexing while you are building it, and assign the Delacroy style to that page. That lets you compare the new design with the old site without changing the public-facing version too early.

Setting Up the Brand Look Through Template Styles and Helix

Once the template is installed, you need to configure it as a system, not as a single page. In Joomla, the visual result depends not only on the template file, but also on the template style, menu assignments, Helix Ultimate settings, modules in positions, and pages built with SP Page Builder. If you only change the homepage content, you may end up with an attractive hero section and chaotic internal pages.

Open the Delacroy template style in the Joomla admin panel. Depending on the package version and your Helix Ultimate version, you will see settings for the logo, layout, typography, menu, custom code, preloader, social links, and other areas. The tab names may differ, so focus on the logic: start with the core identity, then the layout, then the menu, and only after that move on to extra effects.

Logo, Colors, and Typography

The Delacroy reference shows a strong contrast between dark, purple, and pink blocks, large headings, and calmer body text. Do not change every color at once. Start with the logo, the main accent color, and the font pair. If the official settings do not let you control every section separately, it is better to keep some of the default styling and make targeted adjustments through SP Page Builder settings or carefully scoped custom CSS.

For a typical agency site, one primary accent, one dark background, and one neutral text color are enough. If the brand uses a completely different palette, first make sure the hero section, service cards, and buttons remain readable. A bold template is easy to ruin if you replace its high-contrast blocks with tones that have similar brightness.

Layout, Containers, and Responsiveness

Helix Ultimate usually lets you manage container widths, header areas, menus, the page body, and the footer. With Delacroy, the key is not to break the rhythm: a large hero section, then a colored services block, then project and text sections. If you reduce the spacing too aggressively, the template loses its airiness. If you increase it without a system, the page starts to feel stretched out.

Check every major change on a wide screen, tablet, and phone. Pay especially close attention to the menu, oversized headings, portfolio images, and two-column blocks. In SP Page Builder, rows and columns often have separate responsive settings, so a mobile issue is not always fixed in Template Styles.

Menu, Header, and Navigation Behavior

The Delacroy header does more than handle navigation. It is also part of the visual scene. The demo shows a logo, menu items, dropdown sections, a phone number, search, and a contact button. A real site does not need to keep all of that. If you do not have a phone-based contact flow, it is better to remove the number from the header than to leave a demo value in place. If the site only has a few sections, do not artificially force a long menu.

The menu should reflect the user journey: home, services, projects, blog or resources, about, and contacts. For a landing page, you can keep fewer items and make the contact button the main action. The check is simple: from any internal page, the user should be able to understand where they are and how to return to the key sections.

What to Check After Saving the Style

After changing Template Styles, do not open only the homepage. Check a service page, a project page, a blog post, and the contact page as well. If the new style is assigned only to the homepage, internal pages may still use the old template. If the style is assigned to every page, older modules may suddenly appear in places where they were never meant to fit the Delacroy design.

It helps to keep a small change log: what was changed, where it was checked, and what result you got. This is especially useful when both an administrator and an editor are working on the site. One person changes template settings, another edits pages in the builder, and the issue on the public-facing site only shows up after those actions combine.

Which Settings Not to Touch Without a Reason

Do not change the header structure, container widths, global fonts, section order, and custom CSS all at the same time. If the mobile version breaks afterward, it will be hard to find the cause. Start with the settings directly tied to the brand: logo, primary color, contact details, and menu. Leave layout tweaks, custom code, and optimization for later, once the base structure has already been validated.

Content, Blog, and the Contact Path After Importing the Demo

After QuickStart or after migrating the demo structure, the site often looks finished only at first glance. In reality, this is when the most important work begins: replacing the demo content without losing the page composition. Delacroy has a strong visual rhythm, so simply swapping the text without checking length, meaning, and connections between sections can ruin the overall impression.

Start by dividing the content into three groups. The first is the must-have material without which the site cannot be published: the homepage, services, contacts, and policy or legal pages if needed. The second is proof: projects, testimonials, articles, team, and partners. The third is decorative or secondary demo sections that can be removed if there is no real content for them. This approach helps keep you from shipping everything that happened to be in the demo.

How to Replace Demo Text Without Breaking the Structure

Demo text is usually written to fit a specific heading length and column width. If you replace a short English phrase with a long sentence, the block may become taller, the button may drop lower, and the neighboring cards may lose balance. That is why copy should be written to fit the section itself. For a service card, the title, 1 to 2 sentences, and a link to details are enough. For the hero block, one strong statement and a short explanation work better than several lines of generic description.

If a section feels cramped, do not reduce the font size immediately. First shorten the text, split it onto a separate page, or remove an extra card. Large-scale typography is part of Delacroy's character, and text that becomes too small will make the template feel like a compromised corporate site.

Input -> logic -> output for a service section

Input data includes the service name, short description, a link to the service page, and a visual marker. The product logic is that SP Page Builder renders the card inside a row, while the template defines the visual rhythm, colors, and spacing. The expected output is a set of cards with equal visual weight that reads like a group of service areas, not a collection of random promotional blocks. The test is to open the section on desktop and phone, compare card heights, and make sure every link points to a real page. An error symptom is when one card stretches the entire row or a button drops below the visible area. The fix is to shorten the copy, change the number of columns, or move the details to a separate page.

The Blog as Proof of Expertise

The Delacroy product page includes support for a blog page. For an agency, that is useful only if the blog does not turn into an empty news feed. It is better to publish a few strong pieces: a project breakdown, an explanation of your process, a client checklist, or a note on how the team works. Articles like these help visitors understand how the team thinks, not just what its portfolio looks like.

Check how blog posts look both in the listing and on the individual post page. The title, image, date, category, and intro text should all be presented cleanly. If the template's blog card is designed around imagery, do not leave posts without cover images. If you do not have images, adjust the listing layout or prepare simple branded illustrations.

The Contact Path and Inquiry Form

The contact page is not just a technical formality. On an agency site, it closes the entire user journey. Make sure the buttons on the homepage lead to contact, the form includes only the fields you actually need, the message goes to the correct address, and the user understands that the inquiry was submitted successfully. If the form is not ready yet, it is better to leave clear contact details temporarily than to show a broken form.

For a Joomla site, email configuration needs to be checked separately. The template may display the form beautifully, but the actual sending is handled by Joomla or the installed form extension. If messages are not being delivered, review the email settings, recipient address, anti-spam configuration, and server logs, not just the builder page.

Multilingual Setup, Access, and Editorial Workflow

If the site will be available in multiple languages, think that through before publishing. Delacroy as a visual template does not replace Joomla's multilingual architecture. You will need content languages, linked menu items, translated modules, separate SP Page Builder pages, and validation of the language switcher. The most common mistake is translating only the homepage text while leaving the menu, footer, form, and system messages in the demo language.

For a small agency site, you can start with one language and leave a structure that will be easy to duplicate later. Do not mix languages within the same page unless that is a deliberate brand choice. For SEO and usability, each language version should have its own URLs, metadata, menus, and contact wording.

Access Rights for Editors

If the site is maintained by more than one administrator, configure roles carefully. A content editor does not always need full access to template styles and system settings. They can edit content, pages, and images, while Template Styles, modules, and custom CSS are better left to the webmaster. That reduces the risk that changing one section will accidentally change the look of the entire site.

It is also useful to agree on a workflow: who changes the homepage, who publishes the blog, who checks the mobile version, and who owns the contact form. Make changes on a test copy first if they affect the homepage, menu, module positions, or custom code.

Small Responsibility Matrix

This table helps split Delacroy-related work across roles and keeps content edits separate from system-level changes.

The table does not replace the documentation, but it creates a practical boundary of responsibility. If the editor changes the copy, they should not also be adjusting global styles at the same time. If the webmaster enables optimization, they should verify the pages the editor has already assembled.

The Homepage, Services, and Portfolio as One Unified Flow

The Delacroy homepage should not feel like a set of unrelated blocks. It has a clear narrative line: grab attention, explain the specialization, present the services, provide proof through projects, address doubts, and lead to contact. If you change the section order, do it intentionally. For example, for a lesser-known studio it makes sense to show real work earlier, while for an expert team with strong positioning you can start by expanding on the approach first.

In SP Page Builder, editing usually happens through pages, sections, rows, columns, and individual elements. Keep the public page open alongside the admin area. After every major change, save the page and refresh the front end, clearing cache if it is enabled. That makes it much easier to see which setting produced which result.

The Hero Section

The hero section should answer three questions: who you are, who you work for, and what action you want from the user. The template already provides a large visual area, so the text should stay concise. A headline that is too long breaks the composition, and a long description turns the hero block into an article.

For an agency, a strong formula is specialization + outcome + a clear next step. For example, instead of "we deliver end-to-end solutions," say "we build promo websites and content campaigns for tech-forward brands." The button can lead to contacts, a brief form, or a project section. The key point is not to leave demo buttons without a real destination.

The Services Section

Service cards should be symmetrical in meaning. If one service is described in two words while another takes up five lines, the block loses its rhythm. It is better to choose 3 to 4 core directions and describe each one through the result: brand strategy, web design, content, promotion, support. If you offer more services, move the details to a separate page and keep only the most important ones on the homepage.

Make sure every service has a next step: a link to a service page, a contact anchor, a project example, or an inquiry form. Without that, the section becomes decorative.

Projects and Proof

In a template like this, the portfolio works best when it shows more than attractive images. It should make the gap between the challenge and the result visible. Add short captions to each case study: the industry, what was delivered, and what the focus was. If you do not have separate case study pages yet, homepage cards are a fine starting point, but over time it is better to create 2 to 3 more detailed project pages.

Use one consistent system for portfolio images: matching proportions, similar treatment, and clear captions. Random images in different sizes quickly break Delacroy's visual discipline.

Modules, Menus, and Positions: Where Joomla Logic Most Often Breaks Down

A Joomla template is different from a static mockup because some visible elements come from modules and menu-item assignments. The header, footer, contact blocks, social links, secondary banners, and some sidebar areas may all depend on module positions. If it feels like "the template is not working" after installation, the problem is often not the template itself, but a module that is disabled, assigned to the wrong menu item, or published in the wrong position.

Start with a map of the current site. Open the module manager and filter the items related to the template, menu, footer, contacts, and social links. Then check which pages they are published on. In Joomla, a module has a publication status, a position, an order, an access level, and menu assignments. All of those settings need to line up for the block to appear where you expect it to.

How to Check a Module Position

1. Open the page where the block should be visible.
2. Find the module in the admin panel by name or type.
3. Check its position field and compare it with the template's available positions.
4. Make sure the module is published and has the correct access level for the current user.
5. Review the menu assignment tab: the module must be assigned to the needed items or to all pages where it should appear.
6. Clear Joomla cache and browser cache if the result does not update immediately.

If a block is needed only on the homepage, assign it only to the main menu item. If it should appear across the entire footer, assign it to all relevant pages. Do not mix those scenarios, or internal pages will either show extra promotional blocks or lose important contact information.

The Menu as a Context Switch

In Joomla, a menu item is not just a link. It can define the page type, the template style, display parameters, and the context for modules. That is why, when moving Delacroy onto a live site, you need to verify not only the URL, but also the menu item type. A page built in SP Page Builder is one scenario, a blog category is another, and a contact page is a third.

A common trap is creating a new page in the builder but not linking it to the correct menu item. The page exists in the admin area, but on the site it looks wrong or does not receive the correct modules. The fix is to create a menu item, assign the right type, attach the page, and verify the template style.

Practical Scenario: Building an Agency Site from the Demo Structure

Below is a working scenario that fits a small digital team. It does not require purchasing extra extensions and relies on the standard logic of Joomla, the JoomShaper template, Helix Ultimate, and SP Page Builder. The goal is to create a homepage that looks like Delacroy while presenting a real agency.

Goal

You need to prepare a site where the visitor sees the agency's positioning, understands the service lineup, can move to projects, read 1 to 2 expert articles, and submit an inquiry through the contact page. The homepage should not become a long catalog of everything at once. It should lead the visitor through a sequence: promise -> services -> proof -> trust -> contact.

Preparation

• The logo, primary accent color, and contact details are ready.
• You have a service list with short descriptions and 3 to 4 images for case studies.
• The template and its dependencies are installed on a test copy of the site.
• Menu items have been created for the homepage, services, projects, blog, and contacts.
• Aggressive minification is disabled during editing so changes are easier to review.

Setup Steps

1. In Template Styles, assign Delacroy as the style for the homepage and test pages.
2. In Helix, configure the logo, base colors, header, menu, and footer.
3. Open the homepage in SP Page Builder and replace the hero heading with your real positioning.
4. Shorten or reorder sections so the homepage does not duplicate the internal pages.
5. In the services block, keep only the core offerings and add links to the detailed pages.
6. In the projects section, replace the images, captions, and links with your own case studies.
7. Set up the contact page and verify that the form or contact details work.
8. Review the module positions for the header, footer, social links, and extra blocks.

Validation

Open the site as a regular visitor. Follow the path from the homepage to the contact form. Make sure the menu does not lead to demo pages, buttons point to real destinations, images are not stretched, text remains readable on colored backgrounds, and the form either sends the message or at least clearly shows how to get in touch.

Then open the site on a mobile screen. Delacroy's large headings can take up too much space if they are not adapted. Check line breaks, hero height, button visibility, and section order. If the main call to action drops too far down on mobile, shorten the text or adjust the responsive spacing in the builder.

Practical Ways to Use Delacroy

Delacroy can be used for more than a classic digital agency website. The key is not to force the template onto a structure that does not fit. Below are several scenarios where its visual logic genuinely helps. Each one uses the same core elements: the homepage, services, projects, blog, contact, and Joomla's module system.

Design Studio Website

For a design studio, the portfolio is the key block. It makes sense to surface projects earlier on the homepage and keep the services section compact. In SP Page Builder, you can keep the large visual blocks but replace the demo work with real case studies and a short explanation of the task behind each one. Result check: the visitor should understand the quality of the work before reaching the detailed company description.

Promo Site for a Content Team

For a content team, it is more important to show process and outcomes: strategy, editing, visual packaging, and promotion. In this scenario, the blog becomes more than a news section. It becomes proof of expertise. The menu can be built around services, case studies, articles, and contact. Result check: after reading the homepage, the user should understand what kinds of work the team handles and where to see examples.

Landing Page for a Project Team

If you need a site for a specific campaign, Delacroy can be reduced to a single long page. In that case, the menu leads to anchors, portfolio blocks become proof points, and the contact section closes the flow. The key is not to leave empty internal demo pages in place. It is better to remove extra menu items and focus on one clear action.

Website for a Consultant or Small Team

For a consultant, Delacroy's bold style can be softened: fewer decorative sections, more explanation of the approach, and a stronger trust and contact block. Projects can be replaced with service-area breakdowns or short client stories, where appropriate. Result check: the site should not only look distinctive, but also answer why someone should contact this particular team.

How to Check the Result After Setup

Result checking should happen not only at the very end, but after each major stage. Delacroy combines template styles, modules, the page builder, and content. If you change everything first and only then open the site, finding the cause of an issue becomes much harder. Work in short iterations: change the logo and check the header, change the hero and check the first screen, move a module and check the page and its menu assignment.

Checking the Visual Layer

• Headings do not spill outside the colored blocks.
• Buttons are visible against the background and lead to real pages.
• Portfolio images are not stretched and do not crop important details.
• The footer contains real contact details, links, and legal information where needed.
• On mobile, the menu opens correctly and the main call to action does not disappear below the first viewport.

Checking Joomla Logic

Open several internal pages and verify which template style is assigned to them. Then check the modules: the header, footer, social links, contact blocks, and any extra promo areas. If one block appears on the homepage but not in services, review the menu assignment. If a block appears everywhere when it should be limited to a single page, tighten the assignment.

Checking Performance and Indexing

A template with bold imagery and large sections can become heavy if you upload files that are too large. Optimize images before publishing, use sensible dimensions, check lazy loading where it does not break the first screen, and enable CSS/JS optimization only after the site is already assembled. For SEO, review page titles, meta descriptions, human-readable URLs, the sitemap, and the absence of demo pages in the menu.

A good test is to open the site as a new visitor and answer four questions within one minute: what does the team do, what services does it offer, where are the work examples, and how do I get in touch? If those answers are not clear, the problem is not the template, but the content structure.

Safe Improvements Without Editing the Template Core

Joomla and Helix let you make small changes without editing the CMS core files or modifying the original template files directly. For Delacroy, that is useful when you need to improve readability slightly, adjust spacing, or apply a more consistent button style. But the code should stay small, reversible, and easy to understand. There is no reason to rewrite the entire design in CSS if the same result can be achieved through SP Page Builder settings or Template Styles.

CSS for a More Readable Service Card

A safe option is to add a custom class to a row or block in SP Page Builder, for example delacroy-service-proof, and then define it in custom CSS. The exact insertion point depends on your setup: it may be a custom CSS field in Helix or the custom.css file inside the template, if your version's documentation recommends that approach.

.delacroy-service-proof {
  border-radius: 10px;
  background: rgba(255, 255, 255, 0.08);
}

.delacroy-service-proof .sppb-addon-title {
  line-height: 1.15;
}

.delacroy-service-proof a {
  text-decoration-thickness: 2px;
  text-underline-offset: 4px;
}

This change does not depend on any hidden template API. It only affects the places where you added the class yourself. Check the result by opening the services section, confirming that only the intended block changed, and then validating the page on mobile. Rolling it back is simple: remove the class from the block or delete the CSS.

Language Overrides Instead of File Edits

If you need to change a Joomla system phrase or extension text, use the built-in language overrides instead of searching template files for the string. That is safer during updates. In the Joomla admin panel, open the language overrides area, find the needed constant, and assign your own translation. This approach is especially useful for contact forms, interface messages, and small system labels.

Do not edit the Joomla core or extension files directly. Updates may overwrite your changes, and troubleshooting becomes harder. For template-related work, Template Styles, SP Page Builder, modules, menus, custom CSS, and language overrides are usually enough.

If Delacroy Does Not Look Like the Demo: Symptom-Based Troubleshooting

Problems after template installation usually do not come from a single cause. In Joomla, the result depends on the installation package, the active template style, SP Page Builder pages, menus, modules, cache, and optimization. That is why it is best to troubleshoot by symptom: what exactly does not match the expected look, and where in the chain it may have broken.

The Homepage Is Empty or Shows the Wrong Layout

Symptom: the template is installed, but the homepage looks like a standard Joomla page or shows only part of the demo.

A likely cause is the wrong menu item, the required template style not being assigned, demo data not being installed, or the homepage not being linked to SP Page Builder. Check the menu item type, the active template style, and the page that is assigned to the homepage. If you did not use QuickStart, the demo pages may not have appeared automatically.

Fix: assign Delacroy to the correct menu item, create or select a page in the builder, and verify the module positions. If the site is live, do not enable the new style across all pages at once. Test it on a single page first.

Styles Did Not Apply or the Colors Look Broken

The cause is often cache, CSS/JS combination, or conflicts with older files. Disable temporary optimization, clear Joomla cache, browser cache, and any third-party extension cache. If the style looks correct after that, re-enable optimization gradually and check at which point the visual layer breaks.

Also check whether your custom CSS is overriding important template rules. If you added custom adjustments, disable them temporarily and compare the result.

A Module Does Not Appear in the Intended Position

Check four parameters: the module is published, the selected position actually exists, the access level matches the current user, and the menu assignment includes the correct page. If any of those do not match, the module will not appear. In Joomla, that is normal behavior, not a template bug.

When it makes sense to roll back a setting: if you moved a module to a new position and that broke the header, footer, or mobile layout. Restore the previous position and first find the template's position map or review the demo structure.

After Editing in SP Page Builder, the Section Rhythm Is Gone

This usually happens when a column is deleted, a row width is changed, or the responsive spacing is thrown off. Go back to the last working version of the page, compare the section structure, and review the row, column, and element settings. If the problem appeared after replacing an image, check its aspect ratio and size.

To restore the page, do not try to rebuild everything by eye all at once. Fix one block first, save it, check the public version, and then move on to the next one.

The Contact Form or Button Does Not Lead to an Inquiry

If a button in the hero or services section still points to a demo URL, users will not be able to contact you. Check the links on all buttons, the contact menu item, Joomla email settings, and the form itself. If the form is handled by a separate extension, review its sending settings and recipient configuration.

When it makes sense to roll back: if email stopped arriving after you changed the form. Restore the previous working configuration, then test changes one by one: recipient address, sending method, form fields, anti-spam settings, and the email template.

When JoomShaper Delacroy Is a Good Choice

JoomShaper Delacroy is worth using if you need a visually distinctive Joomla site for an agency, studio, project team, or service portfolio, and its actual demo structure matches your goals. The template gives you a strong starting point: visual rhythm, ready-made pages, integration with Helix Ultimate and SP Page Builder Pro, and a foundation for services, projects, a blog, and contact.

Before publishing, walk through a short final checklist: verify the installation scenario, the template style assignment, the menu, modules, homepage, contact flow, mobile version, cache, and demo content. If everything works on the test copy, you can get the Joomla version, prepare the archive for installation, and repeat the validated sequence of steps on the live site.

If what you really need is a strict catalog, a news portal, an online store, or a documentation site, do not try to force Delacroy into something unrecognizable. In that case, it is better to choose a template with a different structure. Delacroy's real strength is bold presentation of services and work, and that is where it performs best.