JoomShaper Celestia - Joomla Template

Guide to Setting Up and Using JoomShaper Celestia for a Real Estate Website

JoomShaper Celestia is best viewed not as a standard visual theme, but as a ready-made foundation for a real estate agency, developer, residential complex, or property company site that showcases listings, projects, neighborhoods, news, and contact forms. In this guide, we'll walk through how to approach the template installation, where demo styling ends and real website configuration begins, which parts of Celestia depend on SP Property, SP Page Builder Pro, and Helix Ultimate, and how to verify the result before launch.

This article does not repeat the product's short description. What matters here is the practical path: whether to choose QuickStart or the standard template package, how to prepare the server, which real estate data to enter first, how not to lose module positions, where to find the homepage, how to configure the property filter, what to check on mobile, and which issues come up most often with Joomla templates in this category.

The approach is straightforward: first build a safe test copy, then replace the demo data with real listings, verify the menus and modules, walk through the visitor journey from the first screen to the inquiry form, and only then move the result to the live domain. The most common mistake with templates like this is starting with images and colors before checking the SP Property structure, menus, and module positions.

What Celestia Is Built For and Where This Template Makes Sense

Celestia is designed for websites where a property needs to be presented like a product with full context: photos, price or price-on-request, specs, neighborhood, agent, map, project details, and an inquiry form. That is what sets it apart from a generic corporate template. On the JoomShaper product page, the template is positioned for real estate, construction, development, property management, and related use cases, and the demo relies on SP Property, a component for managing listings, agents, inquiries, and related modules.

If your agency site only has five static pages, Celestia may be more than you need. Its strengths really show when you have a property catalog, filtering, apartment or house detail pages, neighborhood pages, market news, project pages, and dedicated contact forms for agents. In that kind of setup, the template helps you do more than just make the site look good. It creates a clear user path: understand the company's positioning, choose a neighborhood, filter listings, open the details, and submit an inquiry.

That said, Celestia does not replace the work of a content manager, and it will not automatically turn a chaotic set of photos into a polished property database. You still need to prepare solid images, a consistent format for square footage and pricing, listing descriptions, categories, property attributes, statuses, and agent contacts. The template provides the framework and visual logic, but the quality of the result depends on the data you put into it.

It helps to decide in advance what role the catalog will play. In one project, it may be the main sales tool, where each listing page needs to function almost like its own landing page. In another, the catalog may simply support the presentation of a residential development, while the key conversion happens through the project page and consultation form. That choice affects everything: how many fields to show in the filter, whether to display the price right away, how detailed agent profiles need to be, whether news should be maintained, and which menu items belong in the header.

For a real estate agency, speed of choice matters: visitors should be able to narrow down the list quickly. For a developer, confidence matters: visitors should see the scale of the project, the neighborhood, floor plans, consultation timeline, and a clear way to get in touch. For property management, service structure matters: services, properties, requests, contacts, and FAQ should stand out more than decorative sections. That strategic choice is best made before you edit the first hero headline, otherwise you can end up with a beautiful site that does not lead users toward action.

Strong Use Cases

• An agency website with a property showcase, filtering, and listing detail pages.
• A residential development promo site that needs project pages, a gallery, neighborhood content, and an inquiry form.
• A rental or sales catalog with agents and property viewing requests.
• A developer website that needs project pages, news, and dedicated landing pages for apartment types.

When Another Approach Makes More Sense

If you need a minimal brochure-style site without a catalog, it is simpler to use a lightweight Helix Ultimate template or build the page in SP Page Builder without SP Property. If the project requires complex CRM integration, automatic listing import, synchronization with external portals, or agent dashboards, Celestia alone may not be enough. In that case, you will need a separate architecture, a real estate component with the right integrations, or custom development tailored to the business workflow.

What Comes with the Template Stack: QuickStart, Template, SP Page Builder Pro, and SP Property

Before installation, it is important to understand the difference between the packages. QuickStart is not a standard extension that you upload into an existing Joomla site. It is a full demo website: Joomla, the template, demo data, components, modules, and settings assembled to match the demo. This package should be installed into a clean location with a separate database. The standard Template package, by contrast, is just the Helix Ultimate-based design template, without demo content, ready-made pages, or preconfigured module placement.

For beginners, QuickStart is almost always easier to understand. You can see where the positions are, which pages were created in SP Page Builder Pro, how the menu works, where the SP Property modules are placed, and how the listings connect to the public-facing site. But QuickStart should never be installed over a live website. If you already have a working Joomla site with content, install the template separately and migrate the structure carefully: create the pages, menus, and modules manually while comparing them against the documentation and the demo.

SP Page Builder Pro is responsible for pages built with the page builder. The Celestia documentation explicitly states that the QuickStart homepage is built in SP Page Builder Pro and assigned in the Main Menu as Home. That means edits to the hero area, neighborhood section, benefits blocks, and other visual sections happen inside the page builder, not in Joomla's standard article editor.

SP Property handles the real estate side of the setup. It is used to create categories, listing properties, agents, inquiries, search modules, and property lists. That is why configuring Celestia cannot stop at menus and colors. You need to populate the real estate component, otherwise the polished template will remain an empty shell.

There is also an organizational nuance. QuickStart is useful as a training environment, but after installation it still contains demo logic: sample menu items, sample pages, sample copy, sample listings, and placeholders. Do not move that directly to a live site without editorial cleanup. Remove unnecessary pages, disable modules you do not need, rename menu items to reflect the real business structure, and verify that utility pages like Login, Sign up, Coming Soon, and FAQ are actually needed. If they are not, it is better to remove them from navigation than leave them empty.

The standard Template package requires more manual work, but it also reduces the risk of bringing demo clutter into an existing site. That path works well for a developer or administrator who already understands Joomla: create a menu item, assign the template style, publish modules, build pages in SP Page Builder, connect SP Property, and verify positions. For a site owner without experience, the safer path is to deploy QuickStart separately first and use it as visual documentation: keep the demo page open next to your working build and reproduce only the parts you actually need.

What to Check Before Installation: Server, Database, Permissions, and Content

Installing a real estate template touches more moving parts than installing a basic theme. What matters here is not just Joomla and PHP compatibility, but also archive upload limits, memory limits, script execution time, folder permissions, cURL availability, a healthy database, and readiness to work with images. The official JoomShaper documentation recommends checking server requirements before installing JoomShaper products, and specifically emphasizes that QuickStart needs a clean environment.

Start by deciding where the test site will be deployed. The ideal option is a separate subdomain or a local environment that you can remove without risk. For QuickStart, create a new database or, if you must use an existing one, at least a separate table prefix. In practice, a fresh database is easier: there is less risk of conflicts from old tables, leftovers from previous extensions, or strange installation errors.

Minimum Technical Checklist

• Check your Joomla, PHP, and MySQL versions against the JoomShaper documentation and the requirements of your chosen site version.
• Make sure upload_max_filesize, memory_limit, and max_execution_time are not too low for a QuickStart installation.
• Verify that cURL is available on the server, since extensions and updates often depend on it.
• Prepare a separate database and a user with the required privileges.
• Make sure Joomla folders will be writable where needed after installation.
• Create a backup if you are not working in an empty environment.

Prepare the content separately as well. Celestia has a strong visual presentation, but the demo photos may not be included in the package because of licensing restrictions. That is not a technical error. JoomShaper's documentation explains that QuickStart may contain placeholders instead of the actual demo images. For a real estate site, that matters a lot: weak or random images immediately break the premium feel of the template.

Put together a short editorial spreadsheet before installation. It should include listing names, categories, statuses, price or reason for hiding the price, address, coordinates, square footage, bedrooms, bathrooms, parking, agent, primary photos, and a short description. Even if you only have one listing so far, a sheet like this will show which SP Property fields you truly need. If the team does not have coordinates yet, do not make the map a key part of the launch. If you do not have quality floor plans, do not promise detailed floor plan content to users.

There is one more point to think about: permissions and access. For a simple launch, a Super User and one responsible editor may be enough, but an agency site quickly starts to require role separation: who adds listings, who edits copy, who reviews inquiries, who manages media. SP Property includes settings related to agent groups, and Joomla itself uses Access and user groups. Do not overcomplicate ACL on day one, but decide early whether the team will work inside Joomla or whether all inquiries will be handled by an external manager.

Before installation, prepare at least one complete test listing: title, status, price or price-on-request condition, neighborhood, square footage, bedrooms, bathrooms, gallery, coordinates, agent, and a short sales-oriented description. That will let you test the full user journey, not just the presence of a homepage.

Installing QuickStart and Running the First Check After Logging into the Admin Panel

QuickStart is installed like a standard Joomla site in a clean location. Extract the archive, upload the files to the server, open the domain or subdomain in your browser, and go through the web installer. During setup, do not use an obvious administrator login like admin. After the installation succeeds, remove any extra index.html file if one remains in the root, rename htaccess.txt to .htaccess if you use SEF URLs on Apache, and log into the admin panel through /administrator.

Right after logging in, do not start changing the design. First, check the technical state of the site. In Joomla, open system information and folder permissions. If some directories are not writable, fix the permissions through your hosting panel or SFTP. Then confirm that the Helix Ultimate framework plugin, SP Page Builder Pro, and SP Property are installed and enabled. In QuickStart, those parts should already be present, but verifying them will save time when troubleshooting.

First Pass Through the Admin Panel

1. Open System and check site status, folder status, and updates.
2. Go to System - Site Templates or Site Template Styles and make sure the Celestia style is assigned as default.
3. Open Menus - Main Menu and find the Home item.
4. Open Components - SP Page Builder Pro - Pages and locate the page assigned as the homepage.
5. Open Components - SP Property and verify that listings, categories, and agents are present.
6. Go to Content - Site Modules and filter the modules related to menus, search, and SP Property.

After that, open the public site in a separate tab. Check that the homepage loads, the menu opens, the off-canvas icon works, sections are not broken, and links to property listings lead to real pages. If you see gray placeholders or empty images in the demo, that does not mean the template was installed incorrectly. It simply means you need to replace the media with your own licensed assets.

The first review should end with a short observation log. Write down which pages already work, which modules are unclear, where demo data is displayed, which images need to be replaced, and which menu items can be removed. That may seem unnecessary while the site is still small, but Celestia has many connected parts. After several hours of edits, it becomes easy to forget which module controlled a specific block or why one filter was disabled. A simple list saves you from rediscovering what you already found.

The Homepage: Two Home Concepts, Menus, and Section Editing

The official Celestia documentation highlights two home concepts: Smart Home and Residential. In practical terms, these are different entry scenarios. Smart Home feels calmer and works better for a premium residential development where atmosphere, a large first screen, services, listings, and news matter. Residential is more dynamic, with sliders and visual motion, which may make it a better fit for an agency with a large number of listings and a frequently updated showcase.

In QuickStart, the homepage is created with SP Page Builder Pro and assigned in the Main Menu. That is a key detail: if you are editing a Joomla article and nothing changes on the site, you are probably editing the wrong source. You need to find the builder page under Components - SP Page Builder Pro - Pages, open the correct page, and edit the sections there.

How to Work Through the Homepage Without Creating Chaos

Do not try to rewrite the entire landing page in one pass. Break the work into logical blocks: hero section, neighborhood selection, property showcase, projects, news, trust section, contacts. Each block should have its own job. The hero explains the offer, the neighborhood section helps users start searching, the property showcase drives them into the catalog, projects show the scale of the company, news reinforces expertise, and contacts provide a quick path to an inquiry.

When editing the page in SP Page Builder Pro, preserve the original spacing logic. Celestia relies on generous whitespace, large images, and refined buttons. If you replace calm sections with dense cards, the template will lose its character. It is better to keep fewer sections, but make sure each one leads to action: choose a neighborhood, browse apartments, open a project, learn about the company, submit an inquiry. Visual discipline matters more here than the number of blocks.

Hero Section

The local visual reference shows Celestia's character clearly: a large architectural photograph, dark overlay, slim header, minimalist menu icon, elegant oversized headline, and a neat button. When replacing the content, keep that rhythm. Do not overload the hero with multiple buttons, a phone number, a form, and a long block of text. One strong message, a short explanation, and a clear next step works much better.

Menu and Off-Canvas

Celestia promotes a stylish off-canvas menu. Check not only the desktop menu, but also how it opens on mobile. If the menu does not appear, inspect the menu module, position, page assignment, and template settings. In Joomla, the menu shown on a page often depends on the module, not just the structure under Menus. That means a menu item can exist but still not be visible in the position where you need it.

Neighborhood and Apartment Blocks

The "Select your Neighbourhood" section from the reference sets a strong pattern: text area on the left, a large architectural visual on the right, and calm spacing around it. A block like that should not turn into a list of every neighborhood in the city. It is better to highlight 3 to 6 key neighborhoods and move the rest into the catalog filter.

SP Property as the Core of the Real Estate Catalog

Celestia's defining strength is not just its visual style, but its connection to SP Property. The component lets you create listings with categories, statuses, agents, prices, galleries, coordinates, features, floor plans, and videos. That is the layer that turns the template into a working showcase where visitors can search, compare, and submit inquiries.

Do not start with dozens of listings. Start with the data model. Define the categories: apartments, houses, commercial spaces, new developments, rentals, or sales. Then standardize the statuses: Sale, Rent, Sold, Pending, Under Offer, or your own local equivalents. After that, prepare the list of attributes that actually help users filter: number of bedrooms, bathrooms, parking, square footage, neighborhood, floor, year built, balcony, view, finish type.

Creating the First Listing

The SP Property documentation describes the listing creation path as Joomla Dashboard - Components - SP Property - Properties - + New. The Basic Tab is where you set the unique ID, title, alias, category, status, agent, description, primary image, gallery, and coordinates. The Price Tab is used to configure the price, currency, and display format. The Location Tab contains the country, city, address, and ZIP code. The Details Tab is where you add square footage, bedrooms, bathrooms, garages, floor, features, video, and floor plans.

For a real site, the goal is not to fill every field just because it exists, but to fill the fields that support the buyer's decision. If you are selling luxury real estate, the price may be hidden behind a request, but then the listing page needs to make up for that with a strong gallery, floor plan, neighborhood context, and agent contact. If you are selling mainstream apartments, the price, square footage, room count, and neighborhood should be visible immediately, otherwise the filter becomes purely cosmetic.

A strong Celestia listing page should answer five questions: what the property is, where it is located, how much it costs or how to request the price, which attributes matter for the decision, and who to contact. Everything else is secondary. If you write a long description but forget the agent and coordinates, users will still go looking for contact information. If you upload a beautiful gallery but leave categories empty, the filter will lead nowhere. So do not enter data tab by tab in order. Enter it according to user logic.

Agents and Inquiries

SP Property supports agents and inquiries. An agent profile needs a name, title, phone number, email address, social links, and profile image. Inquiries record which listing interested the user, the inquiry type, name, email, phone, comment, and status. It is not a full CRM, but for basic lead handling inside Joomla, that layer is enough if the process is simple.

Useful check: create a test listing, assign an agent, open the listing on the public site, and submit a test inquiry. Then verify whether the inquiry appears in the admin panel and whether the team receives the required contact details.

Property Filtering, Maps, and Menus: Where Users Actually Search for Real Estate

In Celestia, search cannot be left as a decorative block. Users do not come just to admire a polished hero section. They come to filter listings by neighborhood, price, square footage, status, number of rooms, and other criteria. The SP Property Search documentation describes settings that let you show keyword, status, location, category, price range, area range, bedrooms, bathrooms, parking, and ZIP code. The field set should reflect the real business logic.

If the site is selling apartments within a single residential development, filtering by country and city may be unnecessary, while building section, floor, square footage, room count, and availability status matter much more. If it is an agency covering multiple neighborhoods, location and category become the first fields. If the listings are premium and pricing is often discussed individually, do not overload the filter with price, but do include status, neighborhood, and property type.

SP Property Modules and Celestia Positions

SP Property modules are assigned like standard Joomla modules through Content - Site Modules - +New. The documentation reminds you that JoomShaper template positions are listed under the template name, and active positions help you understand where modules are already in use. This matters in Celestia: a module can be published and still not appear if it is assigned to a position that does not exist in the current template style, or if it is linked to the wrong menu items.

How to Choose Filter Fields

• Keep only the fields on the first screen that visitors immediately understand without explanation.
• Do not enable advanced filtering until the matching property attributes have actually been filled in.
• Make sure the filter values match real listing data instead of returning empty results.
• Use consistent names for neighborhoods and cities, otherwise the search will feel broken.
• For maps, verify the coordinates and the selected mapping service in the SP Property settings ahead of time.

SP Property menu items are created through Joomla's standard menu manager. You can output a property list, agents, a gallery, and other content types by choosing the appropriate Menu Item Type. After saving the menu item, check not only the link itself, but also the modules around the page: the filter, side blocks, breadcrumbs, and contact elements should appear where they help, not on every page by default.

Post-Install Settings: Template Styles, Helix Ultimate, and Safe Customizations

Once the site loads properly and the catalog responds, move on to appearance settings. Celestia is built on Helix Ultimate, so part of the configuration lives in the template style. In Joomla, a template style can be assigned as the default or attached to specific menu items. That is useful when the homepage should look different from the catalog, listing pages, or news pages. But do not create multiple styles without a reason. Every additional style makes the site harder to maintain.

Start with the logo, typography, core colors, header, navigation, off-canvas menu, footer, and mobile behavior. Then review any custom code. The Helix Ultimate documentation recommends using the Custom CSS field or a separate custom.css file for small changes instead of editing template.css and other core template files. That is the right strategy: a template update should not wipe out your changes.

What to Configure First

1. The logo and the company's core visual identity.
2. The main menu and mobile off-canvas behavior.
3. Heading typography that preserves Celestia's refined character.
4. Accent colors for buttons, links, and property statuses.
5. The footer, contact details, and social links.
6. Template style assignments for the homepage, catalog, and utility pages.

A Small, Safe CSS Adjustment

If the filter buttons or property cards feel too weak after replacing the content, you can add a short tweak through Custom CSS or the /templates/shaper_celestia/css/custom.css file, if that path matches your installation. This is not a core template edit, but an external styling layer. The selectors below are examples only, so check the actual classes in your browser inspector before using them on your site.

.sp-property-search .btn,
.sppb-btn {
  border-radius: 0;
  letter-spacing: 0.02em;
}

.sp-property .property-item,
.sp-property-properties .property-item {
  box-shadow: 0 14px 34px rgba(15, 40, 38, 0.10);
}

The check is simple: clear the Joomla and browser cache, open the catalog page, and make sure the buttons and cards look cleaner without breaking the text layout. Rolling back is simple too: remove the snippet from Custom CSS or temporarily rename custom.css. Do not add PHP, third-party analytics scripts, or a long set of rules here unless you understand how they affect listing pages and the filter.

A safe rule for Celestia: adjust the design through Helix Ultimate settings, Custom CSS, template styles, and Joomla overrides, not through direct edits to template files that may be overwritten by updates.

Practical Example: Build a Residential Development Landing Page and Test the Inquiry Flow

Let's say you need to launch a residential development page with a showcase of available apartments. The goal is not just to present a beautiful hero section, but to guide the visitor from the core idea to specific listings and an inquiry request. This scenario fits Celestia well: the reference design is already oriented around architecture, neighborhoods, apartments, and a premium visual presentation.

Goal

Create a homepage with a large hero block, a neighborhood section, an available apartments block, a parameter-based filter, a specific listing page, and a working inquiry form. In the end, the manager should see the test inquiry in the admin panel, and the visitor should see a clear path without empty pages or broken links.

Preparation

• QuickStart is installed on a test subdomain or separate copy.
• You have 3 to 5 test listings with real or prepared images.
• At least one agent has been created with contact details.
• Categories, statuses, currency, and core listing fields are configured.
• The SP Property search module is confirmed to be published in the correct position.

Setup Steps

1. Under Components - SP Property, create a category for the residential development or listing type.
2. Add test listings through Properties - + New, filling out the Basic, Price, Location, and Details tabs.
3. Assign an agent to each listing and upload at least one main image plus a gallery.
4. Create a Properties menu item through Menus - Main Menu - +New and choose the SP Property type for the listing list.
5. Open the Home page in SP Page Builder Pro and replace the hero headline, text, button, and neighborhood section.
6. Link the hero button to the catalog menu item or to a specific page section.
7. Check the search module and keep only the fields that are actually filled in on the test listings.
8. Open the public site, apply the filter, go to a listing page, and submit an inquiry.

Verification

After submitting the inquiry, return to the SP Property admin panel and check the Requests section. You should see the test inquiry there, including the listing, inquiry type, name, email, phone, and comment. If the record exists but emails are not being delivered, that is a separate mail configuration issue involving Joomla and your hosting setup. If no record exists, first inspect the form on the listing page, captcha settings, required fields, and browser console errors.

After a successful test, repeat the scenario from another device and in a private browsing window. That way, you are testing not only the logged-in administrator experience, but also the experience of a regular visitor. Pay attention to listing Access, content language, page caching, and module visibility for guests. An administrator often sees more than a public user, so testing only from an admin session can create false confidence.

Important Detail

If the filter returns a blank page, do not rush to blame the template. First check whether the filter fields match the populated listing data. Very often, the cause is a filter field that is enabled even though no listing has that attribute filled in, or listings that are published in the wrong language, in the wrong category, or with restricted Access.

Usage Ideas for an Agency, Developer, or Property Management Company

Celestia can be used in different ways if you move beyond simply copying the demo. The key is not to invent features that are not there, but to combine the capabilities that are actually supported: SP Page Builder pages, the SP Property catalog, agents, filtering, maps, project pages, news, FAQ, Coming Soon, Sign up, and Login. Below are a few scenarios that fit the template structure especially well.

Agency with a Large Catalog

For an agency, the main focus is fast search and trust in the agents. The homepage should drive users to the catalog, the filter should be short and useful, and the listing page should include agent contact details, a gallery, a price or price request, the neighborhood, and key specs. News can be used for neighborhood guides, legal explainers, and curated listing roundups.

Developer or Residential Complex

For a developer, emotional presentation, projects, and floor plans matter more. Use the hero section, neighborhood section, gallery, project pages, and the Sustainability page if the company genuinely presents environmental practices. The catalog does not need to be huge, but it does need to be precise: apartment types, square footage, status, floor plan, floor, and inquiry form.

Property Management Company

For property management, service pages, news, FAQ, and direct team contacts are especially useful. The property catalog may be smaller, but inquiry structure, agent profiles, and clear navigation for owners and tenants become more important. If you need private content, use Joomla's built-in Access mechanisms, but do not try to turn Celestia into a full client portal without a separate technical project.

If the company serves multiple audiences, do not mix them into one menu. A potential buyer needs the catalog and a viewing request form. A property owner needs partnership terms. A tenant needs support contacts. An investor needs projects and documents. Celestia lets you build those routes through pages, menus, and modules, but route clarity is still an editorial responsibility. One beautiful template does not replace information architecture.

Landing Page for a Single Property

If you are selling one major property, Celestia can be used as a premium landing page: hero, neighborhood, gallery, floor plans, map, benefits, FAQ, and inquiry form. SP Property is still useful as the source of structured property data, but the menu and filter can be simplified.

Checking the Result: Responsiveness, Speed, SEO, and Listing Data

Celestia should be tested along the user journey, not by clicking through a list of admin screens. Open the homepage, catalog, listing page, agent page, news, FAQ, and contact forms. Check desktop, tablet width, and mobile width. The template's visual style depends on large photography, generous spacing, and delicate typography, so low-quality images or overly long text will break the composition quickly.

Responsiveness

Check the menu, off-canvas panel, sliders, listing cards, filter, and inquiry form. On mobile, the filter should remain easy to understand instead of turning into a long wall of fields. If there are too many fields, keep the essentials at the first level and move advanced parameters further down.

SEO and URL Structure

For real estate pages, clear aliases, unique titles, good listing descriptions, and the absence of duplicates are important. In SP Property, the Title Alias field can be generated automatically from the title, but for a public site it is better to review the final URLs manually. In Joomla, also check SEF settings, the .htaccess file, breadcrumbs, the sitemap solution if one is used, and indexing rules for utility pages like Login or Coming Soon.

Do not try to optimize everything around keywords. Every page should have a clear purpose. The homepage explains the company and leads into the catalog. The catalog helps users choose a property. The listing page presents the details and leads to an inquiry. A news post answers a specific market or neighborhood question. FAQ removes doubt. When the structure works like that, SEO becomes more natural: headings do not read like a pile of search queries, and internal links help visitors continue their journey.

Speed and Images

Celestia depends visually on large photos. Compress images to a reasonable size, use meaningful alt text, and do not upload dozens of heavy files to a listing page unless they are actually needed. If sliders, menus, or the filter break after enabling optimization or caching, temporarily disable the questionable minification setting and test the conflict one parameter at a time.

Data and Localization

Check the currency, price format, area units, field labels, statuses, and language. SP Property uses Joomla language files. For clean localization, it is better to use language overrides or separate language files instead of editing the extension's original strings directly. That is especially important if the site will be updated.

When JoomShaper Celestia Is the Right Choice

Celestia is worth using if you need a visually strong Joomla real estate site where the homepage design is tightly connected to the property catalog, agents, filters, maps, and inquiries. The template works especially well for projects where architectural atmosphere, a calm premium presentation, neighborhood pages, and a clear path from the first screen to the listing page all matter.

Make the final decision after a real test workflow, not after looking at a beautiful demo. If the listing, filter, menu, inquiry flow, and mobile version work together, then the template is genuinely ready for further configuration.

Before launch, keep your focus on three things: a clean installation or safe test clone, properly populated SP Property data, and a verified public user journey. If those three layers work, then you can move carefully into colors, typography, SEO details, localization, and speed optimization.

Once the structure is clear and you are ready to test the template in your own environment, you can download the installation package, deploy it in a test setup, and walk through the scenario from this guide: install it, add a listing, configure the filter, open the listing page, submit an inquiry, and verify the mobile view.