JoomShaper Justice - Joomla Template

How to Set Up JoomShaper Justice for a Joomla Legal Website

JoomShaper Justice is best treated not as a simple visual refresh, but as a ready-made foundation for a legal website: with a hero section, practice pages, attorney profiles, case studies, a blog, a consultation form, navigation, and a footer. This guide explains how to approach the template after downloading it: which package to choose, what to check on the server, where to edit pages, how to avoid breaking Dynamic Content, and how to confirm that the public-facing site works as a professional storefront for legal services.

This article does not repeat the short product description. The practical side matters more here: how to use QuickStart, how it differs from the standard template package, where SP Page Builder pages are stored, how attorneys, practice areas, case studies, and blog content are organized, which Helix settings control the header, menu, module positions, and footer, and which issues most often get in the way of launching the demo without unnecessary frustration.

This guide is written for a Joomla administrator, webmaster, or agency owner who wants to build a law firm, legal practice, consulting bureau, or similar expert-service website quickly. If you already work confidently with Joomla, some steps will feel familiar, but Justice still requires clear separation of responsibilities: the template controls the overall framework and styling, Helix Ultimate handles shell-level settings, SP Page Builder manages pages and content blocks, and Dynamic Content handles repeatable entities such as attorneys and case studies.

This guide uses exact interface paths where they are confirmed by the documentation, for example: Components > SP Page Builder Pro > Pages, Components > SP Page Builder > Dynamic Content, System > Templates > Site Template Styles, and Content > Site Modules. If your admin panel looks different because of your Joomla version, interface language, or user permissions, follow the meaning of the menu item and verify the result in a test environment.

Where the Template Actually Saves Time

The main value of Justice is not that it looks "blue," "formal," or "legal." Labels like that do very little during implementation. The real strength of the template is that it already breaks a typical legal website into working content zones: a hero section with clear positioning and a consultation button, an about block, a services list, a process section, attorney profiles, successful case studies, publications, FAQ, a subscription form, and a footer with contact details. In the legal niche, that matters more than a pretty set of sections, because visitors often come looking not for inspiration but for a clear answer: who will handle the matter, what experience the firm has in that area, how to get in touch, and whether the site feels trustworthy.

The demo shows a structure built around trust: a high-contrast hero with a justice-themed visual, a managing partner card, large serif-style headings, gold accents, a restrained services grid, and dedicated areas for lawyers, blog content, and FAQ. This layout works well for a law office, legal consultancy, in-house legal department, mediator, corporate law specialist, intellectual property practice, litigation defense, or any other expert practice where experience needs to be shown without aggressive marketing.

Justice is especially useful when you need more than a single promo page and want a set of connected sections quickly. The demo includes Home, About, Practice Areas, Case Studies, and under the More menu you will find Attorney, Blog, Contact, FAQ, Login, Registration, Privacy Policy, 404, and Coming Soon. That does not mean every page needs to be published right away. It means you start with a site map you can trim down to the sections you actually need.

Who This Kind of Starting Point Fits

Justice works especially well for sites where the connection between "service - expert - case study - contact" matters. If a law firm covers multiple practice areas, it is easy to separate them into practice areas. If the team includes several specialists, attorney profiles keep the About page from turning into a long list of names. If there are public case studies that do not reveal confidential details, case studies give readers concrete examples of how the firm works. If the firm plans to invest in content marketing, the blog is already built into the demo logic.

The template is also useful for agencies building a client site and wanting to approve the visual and content model on top of the demo structure first. In that scenario, QuickStart is deployed on a staging subdomain, the team replaces the logo, contact details, menu, core copy, and several Dynamic Content blocks, and then presents the client with an almost finished foundation. That approach reduces the risk that the client sees an empty Joomla site and cannot picture how it will become a real legal resource.

When a Different Path Makes More Sense

Justice may be more than you need if the project is a very minimal one-page site with no service catalog, team, case studies, or blog. For that kind of project, it is easier to use base Helix Ultimate, a single SP Page Builder page, or another lightweight template. Justice is also not ideal if the firm wants a completely custom brand identity where the original legal visual language, large typography, dark blue palette, and gold accents cannot be preserved. It can be adapted heavily, but the further you move away from the original structure, the less value you get from the ready-made demo.

You should also consider the legal and ethical restrictions in your country or region. In some jurisdictions, you cannot freely publish promises of results, win-rate percentages, testimonials, or wording that sounds like a guaranteed outcome. The template gives you visual blocks, but responsibility for the accuracy of the legal content still belongs to the site owner. Demo numbers, names, and case studies should be replaced with real, compliant, and verified content.

What to Check Before Installation

Before installing Justice, it helps to split preparation into two parts: technical and editorial. The technical side answers whether the server can handle QuickStart, while the editorial side defines what exactly you will change after launch. If you start with nothing but the ZIP archive, it is easy to end up in a familiar situation: the demo installs, but it is unclear which images to replace, which pages to disable, where the form lives, why some blocks are not coming from standard Joomla articles, and what to do with the menu items.

The official Justice requirements call for modern PHP versions, increased memory limits, upload size, execution time, MySQL or MariaDB, cURL, OpenSSL, and availability of file_get_contents(). For an administrator, that is not a formality. QuickStart includes not just the template, but also the Joomla core, demo data, Helix Ultimate settings, SP Page Builder, and related extensions. In other words, the installation is closer to deploying a complete site than adding a small extension through the manager.

Technical Checklist Before Deployment

• Check PHP and hosting limits. If the memory limit, post size, upload size, or execution time is below the required level, QuickStart may hang while uploading files, creating tables, or importing demo data.
• Prepare a separate database. For a staging environment, it is better to create a new database and a new user with full permissions for that database. If you use an existing database, use a separate prefix and create a backup first.
• Choose a clean installation folder. QuickStart cannot be installed on top of a live Joomla site through Extension Manager. If leftover files such as index.html or an old configuration.php are still in the root, they may interfere with the installation.
• Confirm file access. You will need SFTP, FTP, or your hosting file manager to upload the extracted QuickStart files and, if needed, check .htaccess.
• Check SSL and the domain environment. If the site will open over HTTPS immediately, configure the certificate before the final form and editor check so you do not run into mixed content or save errors.
• Agree on a staging address. It is better to deploy the template on a subdomain or temporary folder than on a production site with real visitors.

Editorial preparation looks simpler, but it often saves more time. Gather the logo, favicon, phone number, email, address, list of practice areas, specialist names, short bios, real photos or approved placeholders, legally safe case-study wording, the privacy policy, and the consent text for the form. Without those materials, the site may look polished after installation but still remain little more than a demo scene with no real practical value.

Practical check: before installation, write down which demo sections will be published immediately, which will remain drafts, and which should be removed. For a legal website, it is usually reasonable to start with the homepage, practice areas, contact, privacy policy, and 2-3 specialist profiles, then add the blog and case studies once real content is ready.

QuickStart or the Standard Template Package

For Justice, choosing the right package is critical. The official documentation separates QuickStart from the standard Template package. QuickStart is a ready-made demo site: Joomla core, template, components, modules, Helix Ultimate settings, SP Page Builder pages, and demo data. The standard template package is a standalone Joomla template that controls appearance and layout, but it does not include pages, modules, components, or demo content.

When to Choose QuickStart

QuickStart is the right option if you want a site that looks as close to the demo as possible and then plan to replace the content. For Justice, this is the clearest path because the template is tied to a ready-made page structure and Dynamic Content. Right after installation, you can see where the hero section is, where the service cards are, how attorneys are structured, what case studies look like, which modules sit in the footer, and how the off-canvas menu works.

That said, QuickStart is not suitable for installation on top of an existing site. It cannot be uploaded through Extensions like a normal add-on, because it already contains Joomla inside it. If you already have a live site, deploy QuickStart separately, study the structure, and then transfer the pages, styles, content, and settings you need manually or through supported export/import workflows, without overwriting the production project.

When to Choose the Standalone Template

The standard template package makes sense if Joomla is already set up, the page structure already exists, and you only need the visual framework. But with Justice, that approach requires more experience. The documentation explicitly warns that the standalone template does not include modules, components, or demo content, and that SP Page Builder subpages must be created from scratch while articles and modules must be configured manually. For an advanced administrator, that is normal control. For a beginner, it often turns into the question, "Why doesn't the site look like the demo after I installed the template?"

Initial QuickStart Installation Step by Step

1. Download the QuickStart package from the official source and extract the archive locally.
2. Upload the extracted files to a clean folder on the server or staging subdomain.
3. Create a database and user, and save the database name, login, password, and database server address.
4. Open the domain or test path in a browser to launch the Joomla web installer.
5. Create an administrator account with a unique username. Do not use admin as the super user name.
6. Enter the database details and wait for the demo-data installation to finish.
7. After a successful installation, remove any extra index.html file if it gets in the way, and check .htaccess for search-friendly URLs.
8. Sign in to the admin panel at a path such as /administrator and check the homepage on the public side of the site.

After installation, do not rush into changing everything at once. Open the demo in two tabs first: the public site and the admin panel. On the public side, click through the main menu items, check the contact page, a few profiles, practice areas, and case studies. In the admin panel, locate the SP Page Builder pages, Dynamic Content, site modules, and template styles. That quick survey helps you understand which layer controls each specific block.

Initial Helix Ultimate Setup After Installation

Once Justice has been deployed successfully, the first round of setup should move from global elements to local ones. If you jump straight into editing individual sections in SP Page Builder, you may spend time on local tweaks only to discover later that the logo, header, sticky behavior, favicon, layout, or menu is controlled somewhere else. Justice is built on Helix Ultimate, so the core shell elements should be reviewed through the template style and Template Options.

The typical path for template settings is System > Templates > Site Template Styles, then select the Justice style, for example Justice-Default, and open Template Options. Depending on the Joomla interface and language pack, the labels may vary slightly, but the logic stays the same: you are editing the site style, not an individual article.

Logo, Favicon, and Header Behavior

In the Helix Ultimate Basic section, you usually review the logo, retina logo, mobile logo, favicon, logo alt text, logo height, and sticky header. This is especially noticeable in Justice because the demo header sits on top of a strong hero area. If the logo is too tall, the header starts crowding the first screen. If the logo color does not contrast with the dark blue area, the brand disappears. If there is no separate mobile logo, the mobile menu can look noticeably weaker than the desktop version.

A good default approach for a legal website is to upload a proper primary logo first, then check it against the dark hero background, and then set an alt text such as Organization Name logo or a concise equivalent without keyword stuffing. It is also worth preparing the favicon separately and checking it not only in the browser tab, but in the search snippet as well if the site is already indexed.

Colors, Typography, and a Sense of Trust

The official Justice product page mentions multiple color variations, global typography, and styling controls, but that should not be treated as an invitation to change the palette at random. The demo has a recognizable base: deep blue, gold accents, white space, large serif headings, and restrained cards. For a legal website, that works because the visual language supports the content instead of competing with it. If you replace it with neon colors or an overly decorative font, the site loses its sense of seriousness.

The best sequence is this: first lock in 1 primary brand color, 1 accent color, and 1 neutral text palette. Then review the homepage, practice areas, attorney details, contact page, and footer. If a change improves one block but breaks another, restore the original logic and make the adjustment more selectively. Global settings should improve the system as a whole, not just one attractive screen.

Layout Builder and Module Positions

Helix Layout Builder runs on a Bootstrap grid, where rows, columns, and module positions can be rearranged. In the Justice documentation, header, layout, and footer positions are shown separately. That means part of the site does not live inside page content at all, but inside positions. For example, the footer uses an SP Page Builder module in the footer1 position, while the copyright note is tied to the bottom2 position. If you are editing a page in SP Page Builder and still cannot find the footer, look for the module and its position rather than a text block on the page.

Before changing the layout, create a copy of the template style or at least record the original positions. In Helix, it is easy to drag a row, change a column layout, hide a position on phones, or remove a block entirely. That is convenient, but a layout mistake can affect several pages at once. On a legal website, it is especially important to check the header, off-canvas menu, footer contacts, and privacy links, because those elements repeat across the entire site.

Dynamic Content for Attorneys, Practice Areas, Case Studies, and the Blog

One of the key features of Justice is its use of Dynamic Content in SP Page Builder for Attorneys, Attorney Details, Practice Areas, Practice Areas Details, Case Study Listings, Case Study Details, and Blog pages. That changes how editing works. If you see a list of attorneys or practice areas on the site, you do not always need to look for a standard Joomla article. In many cases, the correct move is to open Dynamic Content, find the collection, review the fields, and edit the item.

In the SP Page Builder documentation, Dynamic Content is described as the central mechanism for collections, fields, items, index pages, and detail pages. In the context of Justice, that translates cleanly into the language of a legal website: the attorneys collection stores people, practice areas stores service categories, case studies stores examples of work, and the blog may connect to publications and expert content. The core idea is that design and data are separate. You update the attorney's data, and the card and detail page use a prebuilt output template.

How to Find and Edit Pages

For standard Justice pages, use the path Components > SP Page Builder Pro > Pages. That is where pages created through SP Page Builder Pro should appear. Select the page you need and open it in the back-end editor or front-end editor, if the user has permission and access is enabled. This is how you edit homepage sections, text blocks, buttons, images, and decorative areas.

For Dynamic Content, use Components > SP Page Builder > Dynamic Content or the matching item in the SP Page Builder dashboard. There you can look for the default collections, add new items, and update fields. If you need to add a new attorney, the more reliable approach is to create a new item in the appropriate collection, fill in the name, role, photo, bio, contact details, and related fields, and then verify whether the item appears in the list and whether its detail page opens correctly.

The "Data - Template - Result" Chain

For Justice, it helps to keep a simple chain in mind:

1. Input: you add or update an item in Dynamic Content, for example an attorney profile or a practice area.
2. Product logic: SP Page Builder uses collection fields and prepared dynamic addons to insert the data into a card, list, or detail layout.
3. Output: the attorney card, practice area page, or case study changes on the site.
4. Verification: you open the list and the detail page, then check images, headings, links, breadcrumbs, SEO copy, and the mobile view.
5. Failure symptom: the item does not appear, the card is empty, the image is missing, the link goes to the wrong place, or the detail page still shows old data.
6. Fix: clear the cache, check required fields, publication status, collection-to-page binding, the menu item, and the dynamic addon settings.

This chain matters because the problem may not be design-related at all. For example, a practice area card may look empty not because of CSS, but because a field was left blank. Or a new attorney may fail to appear not because the template is "broken," but because the item is unpublished, filtered out, not linked to the correct page, or hidden by stale cache.

What to Check When Adding an Attorney

For a specialist profile, prepare more than just a name and photo. A legal website needs the person's role, specialization, a short experience summary, a contact CTA, links to relevant practice areas, and careful wording that avoids unsupported promises. If the page includes social links, do not leave empty demo URLs in place. If the QuickStart photos were replaced with gray placeholders or are missing for licensing reasons, that is an expected limitation: the documentation warns that QuickStart may not include the actual photos shown in the demo.

After adding the profile, open the attorneys list, the detail page, the mobile menu, and site search if it is enabled. Check that the job title is not cut off, that the name still has enough contrast on the card, that the image is not too heavy, and that the text does not include legally risky phrasing. On a live site, a specialist profile should help users choose the right person for a consultation, not simply fill space in a visually pleasing grid.

The Homepage as a Trust-Building Flow

The Justice homepage is built as a sequence of arguments. The first screen sets the tone, the About block explains positioning, Services lead into practice areas, How it Works shows the process, Lawyers connects the service to real people, Blog adds authority, FAQ removes some objections, and Newsletter plus the footer complete the contact journey. If you rearrange that order at random, you can end up with a page that still looks good but feels less convincing.

It is better to start editing the homepage not with colors, but with the question: what path should a potential client follow? For example, a corporate law firm may need to highlight corporate advisory, contract drafting, mergers and acquisitions, compliance, and a dedicated consultation CTA. A litigation practice may care more about defense, case evaluation, court representation, and privacy. Justice gives you sections, but you still need to turn them into a real trust funnel.

Practical Example: Set Up the Homepage for a Legal Consultancy

Goal: create a homepage where a visitor understands within 1-2 scrolls what services the firm provides, who handles consultations, and how to send an inquiry.

Preparation: QuickStart is installed, the admin panel is available, and you already have a logo, email, phone number, 3-5 core practice areas, details for at least one lead specialist, and copy for the consultation form.

1. Open Components > SP Page Builder Pro > Pages and select the homepage.
2. In the hero section, replace the generic heading with wording that describes the service without promising a result. For example, not "we win every case," but "legal support for businesses and private clients."
3. Check the consultation button. It should lead to contact, a form anchor, or another clear CTA, not a demo link.
4. In the Services block, keep only the real practice areas. If you currently offer only three, do not stretch the list to six just to fill out the grid.
5. In Dynamic Content, add or edit the responsible attorney profile so the homepage card is not still showing a demo person.
6. In How it Works, replace generic legal benefits with your actual process: initial review, strategy, documents, support.
7. In the Blog block, keep published only the posts that are genuinely ready. Demo posts should be hidden or replaced.
8. In FAQ, answer questions about booking, what documents to bring to the first meeting, response times, and the consultation format.

Verification: open the homepage in a private window, click the main CTA, follow several practice links, check the attorney card, submit a test message through the form, and view the site at phone width. If everything works, clear both Joomla and browser cache and then do one more quick pass.

One nuance: do not try to perfect every block immediately. First make the route feel coherent: the hero offers clear help, the services lead to relevant pages, the profile confirms expertise, the form accepts inquiries, and the footer shows contacts and legal links. Once that works, you can come back to fine typography, imagery, and micro-animations.

Header, Menu, Module Positions, and Footer

In Joomla templates, one of the most common mistakes is editing the wrong layer. A user sees the header and assumes it belongs to the homepage. But in Justice, the header, menu style, off-canvas menu, and part of the layout are controlled through Helix Ultimate and the template style. The footer may be tied to a module position. That is why navigation setup is best handled as its own step, otherwise it is easy to leave demo links in place, break the mobile menu, or lose the footer entirely.

Menu Builder and Off-canvas

The Justice documentation points to System > Templates > Site Template Styles > Select Justice-Default > Template Options, then the Menu tab. Inside, you will find Menu Builder, Mega Menu, and Off-canvas Menu. In Justice, the mega menu is not enabled by default, but it can be enabled at the menu-item level. Off-canvas controls the slide-out mobile menu, and in the default template setup it is configured for the right side with left alignment.

For a legal website, the menu should stay short. There is no need to place every demo page at the top level. A good starting structure is: Home, About, Practice Areas, Attorneys, Case Studies, Blog, Contact. If you have many services, use a submenu for practice areas. If the firm is small, you can keep only the core directions and contact.

Module Positions and the Footer

The official documentation notes that Justice modules can be found under Joomla Admin Panel > Content > Site Modules. There you can also see which modules are published and unpublished. For the footer, it is important to check the footer1 position, which uses an SP Page Builder module, and the bottom2 position for the copyright note. If you updated contact details on the homepage but the old email still appears in the footer, that means you edited the wrong source.

Footer review should include the email, phone number, address, quick links, privacy policy, social links, copyright, and the tone of the wording. On a legal website especially, you should not leave demo links to random company pages or test social profiles in place. The footer often seems secondary, but it is exactly where users often go looking for contact and legal information.

Responsiveness and Hidden Positions

Helix Layout Builder lets you change the grid for different screen sizes and hide positions on phone, tablet, desktop, or large desktop. That is useful, but it has to be tested. If you hide an important CTA on phones, mobile users will not be able to book a consultation. If the logo is too wide, the off-canvas button may shift out of place. If the footer contains too many columns, they need to collapse into a readable order on mobile.

After changing the menu and layout, open not only the homepage but also the inner pages. Make sure the menu active state works, the submenu does not overlap important text, the consultation button leads where it should, and the off-canvas menu shows the real site structure rather than the demo set. Navigation is not truly configured until the public user path has been tested, not just saved in the admin panel.

Consultation Form and Trust Blocks

The Justice demo includes consultation CTAs, contact elements, and a newsletter section. For a legal website, the form is not decorative, it is a working entry point. If it is configured incorrectly, the site owner can lose inquiries even when the page looks perfect. The SP Page Builder Contact Form documentation specifically warns that the contact form does not store submitted messages, so if the mail server or email configuration is wrong, messages can be lost.

That affects the setup order. First define the recipient, sender, fields, and consent text. Then check CAPTCHA if it is required. After that, send a test message from a real external address, review the inbox, spam folder, hosting mail logs, and the administrator's response flow. Only after a successful test should the form be considered ready.

Which Fields to Keep

For an initial legal consultation, it is usually enough to ask for a name, email, phone number, inquiry subject, and a short description of the issue. It is better not to ask visitors to upload documents or describe confidential circumstances in detail right away if the site and data-processing policy are not fully ready yet. A clearer approach is to provide a simple hint about which documents to prepare for the first meeting and how quickly the team will respond.

If you use a consent checkbox, its text should lead to a real privacy policy, not a demo page. If you enable CAPTCHA, make sure it works on the production domain and does not block submissions. If the site serves multiple languages, confirm that the form labels and error messages are localized through the standard Joomla, SP Page Builder, or language-override mechanisms.

Trust Blocks Without Risky Promises

In the legal niche, it is easy to go too far with numbers and claims. The demo may show stats, testimonials, successful cases, and client satisfaction, but on a real site you should use only verified information. Do not publish a case win percentage unless it is both substantiated and allowed under the rules of your jurisdiction. Do not publish case studies with details that violate confidentiality. Do not use testimonials without consent.

It is safer to show the process, areas of specialization, team structure, documents needed for the first meeting, contact methods, and working principles. Those blocks also build trust, but they do not create the impression of a guaranteed outcome. Justice works well for this approach: its sections can be filled with calm, verifiable explanations rather than loud promises.

Safe Improvements Without Editing the Core

Justice can be adapted selectively, but safe changes should go through settings, modules, SP Page Builder, Helix Template Options, or Joomla overrides, not through unnecessary edits to the Joomla core, SP Page Builder core, or template files. Helix Ultimate explicitly provides a Custom Code section for CSS, JS, and meta settings, and the documentation warns that custom PHP should not be placed in template options.

For most tasks, three levels are enough: first, configuration in the interface; second, custom CSS; third, a careful template override or addon override only for a developer who understands the consequences. The closer a change is to the component core, the higher the risk that an update will overwrite it or create a conflict.

A Small CSS Fix for Problematic Fixed Backgrounds on Mobile

SP Page Builder troubleshooting describes a known Mobile Safari issue where a section background using background-size: cover and background-attachment: fixed scales incorrectly. In Justice, this can be noticeable in visually dense sections with background images. If you actually see that symptom on mobile, you can add a safe CSS snippet that disables fixed attachment on narrow screens.

Apply it in Template Options > Custom Code or in another standard custom CSS area available in your environment. Before adding it, save your current settings and confirm that the issue is reproducible.

@media screen and (max-width: 820px) {
  #sp-page-builder .page-content .sppb-section,
  #sp-page-builder .sppb-section,
  .mod-sppagebuilder .sppb-section {
    background-attachment: scroll !important;
  }
}

Verification is simple: open the page on an iPhone or in Safari, scroll through the section with the background image, and confirm that the background no longer "jumps" or scales strangely. Rolling it back is just as simple: remove the CSS from custom code and clear the cache. Do not add this snippet in advance "just in case" if you are not actually seeing the issue.

When Template Overrides Are Needed

Joomla template overrides are useful when you need to change the output of a specific component or module without editing the core. In Justice, that may matter if you are deeply customizing the blog, article cards, or standard Joomla views. But for Dynamic Content and SP Page Builder pages, it is usually more correct to change the structure in the builder, collection fields, or addons rather than going straight into PHP files. If the error points to an override addon inside the template folder, use the official SP Page Builder diagnostic process and do not delete files at random.

A practical rule is this: if the change can be made through Template Options, module assignment, the SP Page Builder editor, or Dynamic Content fields, make it there. If an override is necessary, create a backup first, document the file, check update implications, and plan your rollback. A law firm website should be predictable to maintain, not dependent on random edits inside files.

Multilingual Setup, SEO, and Accessibility for the Legal Niche

Justice will often be used not only by local law offices, but also by firms serving multiple languages, international clients, or different practice areas for different regions. The demo uses an English-language interface, but the real site may be Russian, English, Ukrainian, German, or multilingual. In Joomla, that cannot be solved by simply translating visible text on a single page. You need to understand which elements belong to menus, which belong to SP Page Builder pages, which belong to Dynamic Content items, which belong to modules, and which belong to language files and overrides.

If the site will be single-language, the task is simpler: replace the demo text, button labels, form text, footer, privacy policy, and system messages. If the site will be multilingual, first configure the Joomla languages, language switcher, menu associations, and page structure. Then decide whether Dynamic Content items will be shared across all languages or whether each language will have its own set of profiles, practice areas, and case studies. For legal websites, a separate set is often the better choice, because service names, disclaimers, legal wording, and documents may differ not only in language but in meaning.

How Not to Lose SEO When Replacing Demo Content

SEO in Justice starts not with a pile of keyword phrases, but with a clean structure. Practice areas should have clear URLs, strong headings, unique copy, and internal links. Attorney pages should explain the person's experience rather than repeating the same bio with a different name. Case studies should be anonymized if confidentiality rules require it, but they should still communicate a subject: the issue, the approach, and the result in wording that is allowed. The blog should publish real material, not demo posts with dates and authors unrelated to the firm.

When configuring SP Page Builder pages, check the page title, meta description, canonical logic, Open Graph image, and heading structure. Do not turn every page into a set of identical H2 headings filled with words like "lawyer," "attorney," and "services." It is better to have fewer pages, each of which satisfies a real intent: corporate support, contract work, intellectual property, family disputes, criminal defense, mediation, or another actual practice area. A strong legal SEO page answers a specific client question and makes the boundaries of the service clear.

Justice already includes visual blocks that are easy to turn into SEO spam: service cards, statistics, FAQ, case studies, testimonials, and blog posts. Do not fill them with repetitive phrases. For example, a practice area page is more useful when it explains which documents are needed, how the first consultation works, which matters the firm does not take, which timelines depend on the court or the counterparty, and which stages the team controls directly. That is much more valuable than repeating "legal services" in every paragraph.

Accessibility and Trust

A legal website needs to be readable for different users. Check text contrast in the dark blue hero section, font sizes in the service cards, keyboard focus in the menu, link clarity, image alt text, and the form. Helix Basic specifically mentions logo alt text; apply the same principle to all meaningful images. Alt text should not read like a stack of promotional keywords. For an attorney photo, it is enough to identify who is shown and in what context, if that matters. For decorative graphics, a neutral description or template-level handling may be enough if the image carries no meaning.

Check the FAQ and form on mobile. A common problem on legal websites is that long questions and answers may look fine on desktop but turn into a hard-to-read block on a phone. If a potential client opens the site on mobile after a referral, they need to find the phone number, email, address, form, and core services quickly. That is why the mobile menu, footer, contact page, and CTA matter more than decorative animation.

Policies, Consent, and Legal Restrictions

The Justice demo includes a Privacy Policy page, but the real policy must match your site, your jurisdiction, and your data-processing practices. If the form collects a name, email, phone number, and a description of the situation, that is personal data. If you use analytics, CAPTCHA, maps, external fonts, or a CDN, that may also need to be disclosed in the policy. Do not leave a template page untouched without review by a lawyer or the responsible specialist.

For CTAs and trust blocks, use careful language. "We will review your documents and suggest possible next steps" is better than "we guarantee victory." "Experience in corporate disputes" supported by real examples is better than "the best lawyers in the city" with no source. Justice helps present expertise, but it should not push you toward unverified promises.

A Practical Workflow for Moving from Staging to Production

Most careful Justice implementations begin on a staging address. That is the right approach, but it creates a separate task: how to move the finished site or finished changes to the main domain without losing data. There is no universal one-click step here, because projects differ in hosting, database setup, languages, mail configuration, SSL, cache, and installed extensions. What you can build, however, is a safe transfer process.

The first option is to move the entire finished QuickStart site as a new project. This works well if there is no live Joomla site on the main domain yet. You configure Justice on a staging domain, then move the files and database to the main domain, update the configuration, and verify paths, SSL, mail, cache, and robots settings. The second option is to use the staging QuickStart as a reference and bring only the template, pages, modules, and settings into an existing site. That approach is more complex, but safer when the site already has users, content, and indexing history.

What to Document Before the Move

• Page list. Record which SP Page Builder pages are published, which are hidden, and which are assigned to menu items.
• Dynamic Content collection list. Document the attorneys, practice areas, case studies, blog-related structures, and required fields.
• Modules and positions. Record important modules, especially anything header-related, plus footer1, bottom2, contact/newsletter, and any positions that affect all pages.
• Template style. Save which Justice style is used by default, which Helix settings were changed, and whether custom CSS is present.
• Form and mail. Record the recipient email, SMTP settings, CAPTCHA, consent checkbox, and post-submit message text.
• SEO and access. Check aliases, canonical behavior, robots, sitemap, blocking of the staging domain from indexing, and opening production after the move.

This list may look bureaucratic, but it prevents common issues. For example, after the move the site may load, but the form may stop sending mail because the domain changed. Or the pages may exist, but the menu may still point to staging aliases. Or the footer may show outdated contact details because the wrong module was migrated. The more clearly you document the staging state, the faster you can spot differences later.

Final Verification After the Move

After the move, do not stop at the homepage. Open all main menu items, several Dynamic Content detail pages, the form, the privacy policy, the 404 page, and the mobile menu. Clear Joomla cache, browser cache, CDN cache, and hosting cache. Check that the staging domain is not still present in links, images, canonicals, form emails, or live-site settings. If SSL is used, make sure there is no mixed content.

For a legal site, also verify confidentiality separately. Make sure the demo case studies are deleted or rewritten, test names are replaced, random demo emails are gone, the newsletter does not collect data without the proper consent, and hidden drafts are not accessible through the menu. Publishing a law firm website is not only a design release, but also a trust check.

How to Split Responsibilities Within the Maintenance Team

One of Justice's advantages is that not every task has to be handled by a developer. But that benefit appears only when roles are clearly separated. If every team member changes template options, Dynamic Content, modules, custom CSS, and forms without rules, the site quickly turns into a collection of random edits. For a small legal website, a simple model is enough: the administrator is responsible for Joomla itself, a designer or editor handles SP Page Builder pages, a content manager handles Dynamic Content items, and a technical specialist oversees hosting, cache, updates, and diagnostics.

What Can Be Safely Delegated to an Editor

An editor can be given access to page text, blog posts, attorneys, practice areas, and case studies, as long as they have clear instructions on fields and publishing rules. They should understand which fields are required, which images are needed, which types of wording are not allowed, how to review the card after saving, and when to escalate to the administrator. For a legal website, approval is especially important: an editor should not publish a case study or a promise of results without review by the responsible lawyer.

What Should Stay with the Administrator

The administrator should control template styles, module positions, menus, permissions, updates, backups, cache, and forms. That is not because an editor could not handle the interface, but because those changes affect the entire site. For example, changing a footer position or a layout row can affect every page. Disabling a module can remove the contact details from the footer. Incorrect form settings can stop inquiries completely.

Updates and Process Discipline

Before updating Joomla, SP Page Builder, Helix Ultimate, or the template, create a backup and test the site on a copy. Updates can change editor behavior, cache behavior, front-end output, or addon override compatibility. After the update, open the editor, save a test page, and check Dynamic Content, the form, the menu, and the footer. If custom CSS or overrides are in use, test them separately. That kind of process takes less time than restoring a site after an unexpected conflict.

Troubleshooting Common Justice Issues

Most Justice problems are caused not by the template itself, but by the wrong package, server limits, cache, permissions, optimization conflicts, or confusion about which layer controls the block you need. Below is a practical symptom-based troubleshooting guide. Start with safe checks and do not edit files until you understand the cause.

QuickStart Hangs or Never Finishes Installing

Symptom: the installation sits for a long time while creating tables or importing demo data, or it ends without a clear result. Likely cause: the server limits are below the required values, PHP is configured incorrectly, or the database and user permissions are not suitable for installation.

What to check: PHP version, memory limit, post size, upload size, max execution time, MySQL or MariaDB, cURL, OpenSSL, and availability of file_get_contents(). If you are installing on a local environment, review the Apache/Nginx settings and restart the server after changes.

How to fix it: bring the server in line with the current Justice requirements from the documentation, increase execution time through the hosting panel, or ask hosting support to do it. If you are unsure, do not edit SQL files manually. It is better to create a new clean staging environment and repeat the installation after fixing the limits.

After Installation, the Site Does Not Look Like the Demo

Symptom: the template is installed, but the pages, modules, hero section, attorneys, case studies, or footer do not look like the demo. Likely cause: the standalone Template package was installed instead of QuickStart, or the demo data was not imported.

What to check: which archive was used, where it was installed, whether pages appeared under Components > SP Page Builder Pro > Pages, and whether Dynamic Content collections and modules exist under Content > Site Modules. If those objects are missing, switching the template style alone will not create the demo site.

How to fix it: for a new project, deploy QuickStart into a clean folder and database. For an existing site, use a staging QuickStart install as a structural reference and transfer only the elements you need manually.

A New Attorney or Practice Area Does Not Appear

Symptom: the item was added, but its card does not show up in the list or the detail page is empty. Likely cause: the item is unpublished, a required field is missing, the page uses a different source, the collection filter excludes the record, or cache is showing an older version.

What to check: the Dynamic Content collection, item status, image and title fields, the dynamic addon on the page, the menu item, language association, and Joomla and browser cache. If the site has multiple languages, verify that the item belongs to the correct language or is available to all.

How to fix it: fill in the required fields, publish the item, clear the cache, and then open the list and detail page in a private window. If the issue remains, create a temporary test item with the minimum required fields and see whether it appears.

The SP Page Builder Editor Does Not Open or Shows a White Screen

Symptom: the builder page does not load, the save button does not work, or you see a runtime error or white screen. Likely cause: cache after an update, JS compression, CDN, Cloudflare, ModSecurity, Akeeba Tools, an SSL/redirect issue, or an access conflict.

What to check: clear Joomla cache, browser cache, hosting cache, and CDN cache. Try another browser and a private window. Temporarily disable aggressive JS compression for the editor. Check for CORS errors in the browser console and confirm that no security extension is blocking editor URLs.

How to fix it: start with cache and by disabling optimization for editor routes. If you get a 403 while saving, review the security extension settings or ask the host to check ModSecurity for SP Page Builder URLs. Do not blindly disable protection for the whole site; a targeted exception is the safer solution.

The Consultation Form Does Not Send Email

Symptom: a visitor submits the form, but the administrator never receives the message. Likely cause: the recipient email is wrong, SMTP is misconfigured, the message lands in spam, CAPTCHA blocks submission, the domain is not configured for sending, or the form does not store messages.

What to check: Contact Form addon settings, recipient email, From Email, CAPTCHA, consent checkbox, Joomla mail settings, SMTP, SPF/DKIM/DMARC for the domain, and hosting mail logs. Send a test from an external email address and check the spam folder.

How to fix it: configure SMTP, use a domain-based sender, verify CAPTCHA, and send another test. For important legal inquiries, think through a fallback channel as well: a phone number, an email in the footer, and a clear post-submit confirmation.

The Footer or Copyright Does Not Change After Page Edits

Symptom: everything on the homepage has been replaced, but the old email, a demo link, or the copyright line still remains in the footer. Likely cause: the footer is output through a module position rather than page content.

What to check: Content > Site Modules, the footer1 and bottom2 positions, published SP Page Builder modules, and the language and menu assignment of those modules.

How to fix it: edit the correct module, review its position and assignment, clear the cache, and open several pages, not just the homepage.

Checking the Result Before Publishing

After configuring Justice, you need to test not only the visual presentation, but the working user flow. A good check simulates both the path of a real visitor and the path of an administrator. The visitor opens the site, understands the specialization, chooses a practice area, reviews an attorney, reads a case study or article, submits a question through the form, and finds the contact details. The administrator updates an item in Dynamic Content, updates a page in SP Page Builder, edits the footer module, clears the cache, and sees the result.

Mini Visitor Route

1. Open the homepage in a private window and check the first screen, CTA, and menu.
2. Go to Practice Areas, open 2-3 service areas, and confirm the copy is not still demo text.
3. Open an attorney profile and check the photo, title, description, links, and mobile view.
4. Go to Case Studies, if the section is published, and make sure there is no confidential or fictional data left.
5. Submit the consultation form, check the email, and review the post-submit message.
6. Open the footer, privacy policy, and contact links.

Mini Administrator Route

1. Change one test item in Dynamic Content and check the list and detail page.
2. Edit a short text block in SP Page Builder and save the page.
3. Edit the footer module and check several pages.
4. Clear Joomla and browser cache, then repeat the public-side review.
5. Check the mobile menu and sticky header on an actual phone.
6. Enable standard analytics and SEO tools only after the core user flow is working.

Check the images separately as well. Demo photos may be missing from QuickStart or replaced with placeholders. Prepare your own images with publication rights. For a legal website, it is better to use real photos of the office, team, or documents without confidential data, or clean professional illustrations. Do not leave random stock portraits in place if they could create a false impression of the team.

Test site speed after replacing the images. The hero section and attorney cards often become heavier because of custom uploads. Compress images before uploading them, use sensible dimensions, apply lazy loading where appropriate, and do not overload the homepage with animations. Justice already provides visual rhythm; extra effects will not make a legal website more convincing.

When JoomShaper Justice Is the Right Choice

Justice is worth using if you need a Joomla template for a legal website where not only the hero section matters, but the full structure as well: services, team, case studies, blog, FAQ, contact flow, footer, and clear navigation. It is especially strong when used as a combination of QuickStart, Helix Ultimate, SP Page Builder, and Dynamic Content. That stack lets you get to a working foundation quickly and then replace the demo data with real material from legal practice.

Before publishing, verify the server requirements, choose the correct package, configure the logo and header, bring the menu in line with the real site structure, fill out Dynamic Content, test the consultation form, and walk through the site as a visitor. If the project is new and you need the demo structure, start with QuickStart in a clean staging environment. If the site already exists, use Justice carefully as a template and do not try to install QuickStart on top of a live production project.

Once the core checks are complete, you can download the ZIP archive and deploy it in a test environment. Do not move the template straight to production without checking the form, Dynamic Content, module positions, menu, footer, mobile view, and cache behavior. A good Justice installation is not a one-click action, but a short controlled cycle: install, replace the demo content, test the user path, fix the issues, and only then publish.