ThemeForest Manoir - WordPress Theme

How to Set Up ThemeForest Manoir for a Residential Complex or Single Property Website

ThemeForest Manoir is best approached not as an empty template that simply changes the look of WordPress, but as a ready-made foundation for presenting real estate: a residential complex, a standalone house, apartments, a developer project, a broker listing, or an agency website. In this guide, we will walk through how to approach installation, which parts of the theme are worth configuring right away, where Elementor fits in, and how to work with demo data, menus, widgets, property pages, forms, the store, and final QA.

The biggest mistake with themes like this is importing an attractive demo, swapping out a couple of photos, and immediately treating the site as finished. In real estate, that is risky: visitors are not looking only at visuals, but also at page flow, menu clarity, confidence in the floor plans, how the inquiry form works, gallery load speed, and the polish of the mobile version. That is why this guide is structured as a practical walkthrough, from prep and installation to checking the key user journeys through the eyes of a future buyer or renter.

This article is based on verified Manoir features: Elementor pages, one-click demo import, ThemeREX Addons, the Customizer, per-page Theme Options, Layouts for the header and footer, multiple homepages, property blocks, WooCommerce, Contact Form 7, MailChimp for WordPress, WP Booking System, Slider Revolution, WPML, and the standard server requirements for import. Where a specific option depends on the theme version or the active plugin set, the wording is intentionally cautious and tied to result-based verification.

When Manoir Solves the Job Better Than a Standard Real Estate Theme

Manoir is built for situations where you need to showcase not an endless property catalog, but one strong project or a limited range of offerings. That could be a waterfront residential complex, a single villa, an apartment building, a new office center, a developer project, or a landing page for one property with several unit types. In that setup, the theme's real value is not just the WordPress shell, but its ready-made design language: a bold hero section, architectural photography, benefit sections, available apartment cards, amenities blocks, service pages, testimonials, a blog, and a contact area.

Compared to a general-purpose real estate agency theme, the difference is obvious in how the content is presented. A general agency site usually revolves around search, filters, large listing inventories, and agent roles. Manoir is closer to a project presentation site: first the impression, then the value proposition, then the layouts and contact paths. Manoir is at its best when the property or complex already has visual assets, a clear offering structure, and needs a polished conversion-focused page without building everything from scratch.

The Residential Complex demo page shows exactly that model: a dark hero area with a logo and a hero photo of the building, followed by a large thematic section, benefit cards such as New construction, Fitness facilities, Landscaping, and Recreation, then architecture blocks, available apartments, amenities, testimonials, a blog, and the footer. That sequence matters: visitors first understand the level of the project, then see concrete benefits, and only after that move into the details.

The ThemeForest listing and the ThemeREX website also confirm that the theme is built with Elementor and designed for visual customization of pages, headers, and footers. That is helpful if the site will be maintained by a marketer, a sales editor, or a content manager who needs to update blocks, text, photos, cards, and forms without touching PHP. But that also creates a limitation: if the team prefers the native WordPress block editor and wants to keep plugins to a minimum, Manoir may feel somewhat heavy because of ThemeREX Addons, Elementor, and the additional compatible extensions.

Who This Theme Is a Good Fit For

Manoir makes sense for builders, developers, small agencies, rental property owners, property management companies, and marketing contractors building a site around a single project. The theme is especially useful if you already have strong photos of the facade, interiors, floor plans, grounds, sports areas, parking, leisure spaces, or the surrounding neighborhood. Without that kind of material, the template's visual potential is harder to realize, because the demo images from the live preview are not meant to be used in a finished project without separate licensing.

Another strong use case is a fast launch of a presentation page before sales begin. The site can be built around a few core blocks: a hero section, key benefits, available floor plans, a gallery, a map, an inquiry form, FAQs, and contact details. In that case, Manoir saves time on design because it already offers a residential complex structure and a premium real estate visual style.

When You Should Choose Something Else

The theme may not be a good fit if you need a large portal with agent accounts, a complex property database, user-submitted listings, deep CRM-style workflows, mortgage calculators, a map with thousands of points, or highly customized search across many criteria. The ThemeForest listing mentions WooCommerce, WP Booking System, and various add-on plugins, but that does not turn Manoir into a specialized MLS platform. For a catalog with a large number of listings, it is better to choose a theme or plugin where the real estate database is the actual core of the product.

Manoir is also not the right choice for an overloaded site where dozens of heavy extensions are already active and there is no option to use a staging environment. The official documentation explicitly warns that limited hosting resources can interfere with one-click demo import, and large extra plugins increase memory usage. In that kind of environment, the rollout should be careful: make a backup, use a staging copy of the site, keep the active plugin set minimal, and test step by step.

Feature Map: What to Check in the Theme Before You Start Customizing

Before installation, it helps to break Manoir down into working layers. That makes it much easier to see what needs to be configured and where to look when the result does not match the demo. The first layer is the theme itself and its child theme. The second is ThemeREX Addons, which the documentation treats as required for full functionality. The third is Elementor, which powers the demo pages and layouts. The fourth is the supporting plugin layer: forms, newsletter signup, sliders, store, booking, popups, Instagram, WPML, and other compatible tools. The fifth is the content layer: real photos, floor plans, copy, legal details, contact info, and inquiry terms.

If you mix up those layers, customization becomes chaotic. For example, someone tries to fix the footer in the Customizer even though a Custom Footer Layout is selected and must be edited in WP Dashboard > Layouts. Or they change the global header, but a specific page has a different Header style set in Theme Options. Or they import only part of the demo data and then wonder why the images have been replaced with placeholders and some widgets need to be manually tied to categories or posts.

Main Manoir layers and what to check in each

Layer	Where it lives	What affects the outcome	How to check it quickly
Theme and child theme	Appearance > Themes	Base templates, styles, updates, and the safe place for custom edits	Manoir or Manoir Child is active, and there is no style.css error
ThemeREX Addons	Theme Panel and the plugin list	Layouts, widgets, shortcodes, and some theme-specific settings	The plugin is active, and the theme sections and Layouts are available
Elementor	Page editing and Layout editing	Homepage sections, cards, background images, spacing, animations	Demo pages open in Elementor without errors
Customizer and Theme Options	Appearance > Customize, page settings panel	Header, footer, menus, widgets, colors, typography, per-page overrides	The global setting does not conflict with the setting on a specific page
Real estate content	Pages, posts, properties, images, forms	Trust, conversion, and how clearly floor plans and inquiries are presented	No demo copy, placeholders, or empty links remain on the site

For a real estate site, the connection between visual style and factual information matters especially much. A beautiful hero section does not make up for a missing address, unclear property status, no unit sizes, no floor plans, missing amenities, vague response times, or a confusing inquiry form. Before you get into detailed customization, gather a complete content package: logo, brand palette, section list, photography, apartment or unit data, sales team contacts, a map, floor plan files, buyer questions, and any legal limitations on wording.

Practical pre-check: if you cannot fill out the basic chain of "hero - benefits - floor plans - form - contacts" with real project data in 10 minutes, prepare the content first and only then import and edit the Manoir demo pages.

Preparing WordPress and Hosting Before Installation

The official Manoir documentation lists minimum WordPress and PHP requirements along with recommended server limits for demo data import. It is not useful to tie this guide to a single WordPress version, since compatibility changes with theme and plugin updates, but the principle stays the same: older PHP versions, low memory limits, and short execution times are where demo import tends to break. Before installation, check the site in Tools > Site Health, confirm file access, make sure backups are working, and verify that rollback is possible.

If this is a new project, it is better to start from a clean WordPress install. The ThemeREX documentation separately explains the difference between partial import and full import: full import replaces the existing content and is suitable only for a new site or a staging copy, while partial import adds new data to what is already there. Do not run a full import on a live site with real pages, orders, leads, or a blog unless you have a separate backup. That is not just procedural caution, it is direct protection against content loss.

What to Check on the Server

For one-click demo import, the theme needs enough execution time, memory, and upload size. If the hosting setup will not let you raise those limits, the import may stall on media files, stop with a data upload error, or reject the theme archive entirely. In that case, do not keep repeating the import over and over. First identify the limit: archive size, upload_max_filesize, post_max_size, memory_limit, max_execution_time, folder permissions, and WordPress access to the filesystem.

• Make sure WordPress is installed and opens without critical errors.
• Back up the database and the wp-content directory before installing the theme.
• Ask your host about PHP limits if large theme imports have stalled before.
• Disable heavy plugins that are not needed during import, especially on limited shared hosting.
• Have FTP access or your host's file manager ready in case you need a manual install.
• Collect the real property images ahead of time, because the demo clipart usually is not included as licensed content for your site.

Which Plugins to Enable Right Away and Which to Add Later

The Manoir documentation lists bundled and recommended plugins. ThemeREX Addons and Elementor matter most: the first handles the theme extensions, Layouts, and some signature elements, while the second is required to edit the demo pages because the existing demo layouts are built in Elementor. Enable the rest based on the actual project needs. Contact Form 7 handles forms, MailChimp for WordPress handles newsletter signup, WooCommerce is for a store or paid services, WP Booking System is for booking calendars, Slider Revolution is for sliders, and Advanced Popups is for popup banners.

If the site is not selling products and not taking bookings, WooCommerce and WP Booking System do not need to be active just because the theme supports them. Extra plugins increase maintenance scope and may affect performance. For an initial residential complex launch, the theme, ThemeREX Addons, Elementor, a contact form, and only the plugins actually used by the chosen demo page are usually enough. Everything else can be added later, after the base setup has been verified.

Installing the Theme, Child Theme, and Demo Data

Installing Manoir starts with using the correct archive. ThemeForest usually provides both the full package and a separate installable WordPress file. If you upload the full package to WordPress instead of the theme file, you may get the familiar missing style.css error. Envato Help Center describes this as a standard situation: extract the full package and upload the installable theme ZIP, or download the ready-to-install file directly. For Manoir, that means the theme archive itself, not the full folder containing documentation, plugins, and additional materials.

Installing Through the Admin Panel

This is the easiest path if the archive size stays within your hosting limits. Open Appearance > Themes, click Add New, then Upload Theme, choose manoir.zip, and install the theme. Once installation is complete, click Activate. After that, the system will prompt you to install ThemeREX Addons and other plugins. Do not refresh the page during installation, because some archives may take several minutes to unpack.

After the theme is activated, confirm that a Theme Panel section or a similar ThemeREX section has appeared in the admin area. That is usually where theme activation, plugin installation, demo import, and access to the theme dashboard are handled. Do not start editing pages before the base components are finished installing, otherwise you may see empty sections, unavailable widgets, or broken Layouts.

Installing Through FTP or a File Manager

If WordPress will not accept the ZIP file, use the manual method from the documentation: extract manoir.zip, upload the manoir folder to /wp-content/themes/, then activate the theme in Appearance > Themes. This method is useful when upload limits get in the way, but it requires attention to folder structure: the themes directory must contain the actual theme folder with its files, not a nested folder from the full package. If WordPress still says style.css is missing after upload, it almost always means the wrong folder level was used.

Why You Should Activate the Child Theme Before Import

The Manoir documentation recommends installing the child theme before demo data installation if you plan to make changes to template files or functions. That matches standard WordPress practice: a child theme keeps custom changes separate from the parent theme, so updates do not wipe out CSS, PHP snippets, or template files. For editorial customization in Elementor, a child theme is not always mandatory, but for a real real estate site it is almost always helpful, because sooner or later you will want to safely adjust a bit of CSS, footer text, a display template, or the behavior of a specific area.

Install manoir-child.zip the same way you install the main theme, then activate the child theme. Only after that should you import the demo data. If you import the demo into the parent theme first and switch to the child theme later, some Theme Options may reset or need to be reassigned. This is especially noticeable in ThemeREX themes, where page settings, Layouts, and global options can inherit from one another.

Choosing Full Import or Partial Import

In Theme Panel > Theme Dashboard > Demo Data, choose the mode that fits your case. Full Import creates a copy of the demo site with media, pages, theme settings, and plugin settings, but it may replace existing data. Partial Import adds individual pages or data sets while keeping the current site, but the documentation warns that pages may be imported with placeholder images and may require manual mapping of categories, posts, or widgets.

For a new residential complex website, full import on a staging domain is usually the most convenient approach, followed by cleaning up extra pages and replacing the content. For an existing site, partial import of a specific homepage or selected blocks is safer, but less automatic. Immediately after import, open both the public site and the page admin screens instead of moving into design changes blindly: you need to verify that the menus, Layouts, images, forms, and plugins are actually in place.

How to Choose a Demo Structure That Fits a Real Property

Manoir includes several demo homepages: Residential Complex, Property Showcase, Real Estate Agency, Residency Showcase, and Apartments. They are similar in niche, but they solve different communication goals. Do not choose a page based only on the hero section. Look at the full sequence of blocks: what visitors see after the hero, how benefits are presented, where property cards appear, whether there is room for floor plans, how easily an inquiry form can be integrated, and whether the structure leaves enough room for the neighborhood, infrastructure, team, and FAQ.

Residential Complex is a strong fit for a developer or a project with a strong architectural identity. In the reference demo, you can see a high-contrast hero: a dark left-hand area with a logo and large heading, and on the right an image of a multi-story waterfront complex, followed below by a mission block and amenity cards. That structure works when the goal is to create a premium property feel and showcase not just the apartments, but the lifestyle around them. For a site without strong visuals, this option may be too demanding: weak or empty photography will undermine the first impression.

Property Showcase is more useful when the priority is presenting floor plans, available options, unit specs, and the path to inquiry or purchase. The demo page includes a Properties menu, property card styles, statuses such as Ready for occupancy, Pre-selling, For sale, and Under construction, along with sizes and property types. That is a good choice when the visitor's main question is not "Is this complex visually impressive?" but "Which unit fits me, and where do I submit an inquiry?"

Residential Complex: A Strong Hero and Amenity Storytelling

Choose this base if the project has a visually distinctive facade, courtyard, grounds, pool, lounge area, fitness spaces, landscaping, or another compelling environment. In that setup, the homepage should answer the question "Why would it feel good to live here?" rather than simply listing square footage. Sections like New construction, Fitness facilities, Landscaping, and Recreation can be turned into real advantages: facade materials, landscaping, gated grounds, sports areas, playgrounds, management company services, and transport access.

When replacing the content, do not leave short labels unsupported by evidence. If you mention landscaping, add a courtyard photo, a list of zones, construction status, and a connection to the site plan. If you mention fitness, clarify whether it is inside the complex, nearby, or part of partner infrastructure. Manoir gives you a polished container, but trust comes from specifics.

Property Showcase: Floor Plans and Availability Status

This option works well for properties where buyers compare several apartment or unit types. The card should show more than an image: it needs clear parameters such as status, size, type, room count, floor level, availability, and a link to a detail page or inquiry form. If that data does not exist yet, do not create a fake catalog. Build at least a minimal floor plan reference first, then populate the blocks.

One of Manoir's strengths is that the property grid can look like a gallery, but for real estate it has to function as navigation. That means every card needs a verifiable destination: a property page, a PDF floor plan, an inquiry form, a map, or a manager contact. If a card leads to an empty page with demo text, users lose trust faster than they would on a simpler but honest page.

Real Estate Agency and Residency Showcase

If the site belongs to an agency rather than a single property, a more corporate structure may make more sense. In that case, the homepage should explain who handles the transaction, what services are offered, how consultation works, which properties or projects are represented, and why the visitor can trust the team. Pages such as About Us, Our Services, Our Team, Blog, Contacts, and an inquiry form fit naturally here.

Residency Showcase is a better fit for projects where the property is only part of the story and the lifestyle matters just as much: grounds, services, club-style infrastructure, surroundings, architecture, events, and construction updates. That type of site requires ongoing updates: news, progress photos, answers to common questions, and status changes. If the team is not ready to maintain the content, it is better to choose a more compact structure, otherwise those sections will quickly go stale.

Configuring the Header, Menu, and Hero Section

In Manoir, the header and hero section set the tone for the entire site. In the reference design, the header is minimal: a logo on the left, cart, search, and menu icons on the right, while the hero splits the screen between a dark text area and a large property image. That is not a random decorative composition. It keeps the focus on the building while preserving space for a short promise, a CTA, and navigation. When adapting this for a real project, the key is to preserve that hierarchy: first the property and its message, then the actions.

The Global Header vs. a Page-Specific Header

In the Customizer, the Manoir documentation describes a Header section where you choose the style, position, and related settings. A custom header layout requires ThemeREX Addons to be active, and editing happens through WP Dashboard > Layouts. That distinction is important. If the site uses the Default header, some settings are controlled in Appearance > Customize. If a Custom header is selected, find the relevant layout in Layouts and edit it in Elementor.

Individual pages can also have their own Theme Options panel. The documentation notes that page-level settings can override the global Customizer values. So if the header behaves strangely, check two places: the global Header setting in the Customizer and the Theme Options panel on the specific page. The symptom of a conflict is simple: on one page, the logo, header color, or menu type looks correct, while on another page it looks different even though the global settings did not change.

Header Position: Default, Over, and Under

Header position affects how the header interacts with the hero area. Default keeps it as a separate area, Over places it on top of the next block and is often used with a slider or hero image, and Under places it behind the content area while scrolling. For Manoir, the Over approach makes the most visual sense on pages with a strong hero section, but it requires careful contrast: the white logo and menu need to remain readable against a dark or darkened background, and on mobile the menu must not blend into the photo.

Checking the result is simple: open the homepage without being logged into the admin area, scroll through the hero section, resize the window, and make sure the header is not covering the heading, button, form, cart counter, or image. If it is getting in the way, temporarily switch Header position to Default and see whether the issue disappears. That helps you separate a layout problem from a content problem.

Menus and Full-Width Dropdowns

The Manoir documentation describes Main Menu, Mobile Menu, and Footer Menu locations, along with the ability to edit menus in Appearance > Menus. For complex dropdowns, it also references CSS classes such as .columns-X, .trx_addons_stretch_window_boxed, and .trx_addons_stretch_window, which are applied to top-level menu items. That is useful if the menu needs to present several grouped areas: apartment types, infrastructure, documents, contacts, blog content, and commercial units.

Do not use a stretched menu just for visual impact. On a real estate site, it makes sense only when the site has enough sections that visitors genuinely benefit from grouping. If the menu has five items, a compact version is better. The main menu should lead to visitor actions: view floor plans, explore amenities, open contacts, submit an inquiry, or move into the purchase or rental section.

A Hero Section Without Promotional Noise

Keep the hero focused on one clear message. Do not try to squeeze every selling point of the complex into the headline. A strong Manoir hero usually contains the project name or a short category label, one or two lines of context, a button leading to floor plans or the inquiry form, a high-quality image, and, if needed, a small visual accent. If the project is still under construction, do not hide that fact: the status can appear in the property cards or in a separate progress block rather than being obscured by vague language.

If you have a video, panorama, or 3D tour, check load speed first. Manoir supports visually rich blocks, but the hero section should not be so heavy that visitors are left staring at an empty area. For the initial version, an optimized image plus a button leading to the video farther down the page is usually the safer choice. After launch, measure the load on a mobile connection and make sure the interactive elements are not breaking the menu.

Customizer, Theme Options, and Layouts: Where to Change Different Parts of the Site

Manoir uses several configuration layers, and understanding that is one of the most important steps after installation. The global look and feel is controlled through Appearance > Customize: logo, Site Identity, general settings, Header, Footer, Mobile, Menus, Widgets, Blog, Shop, Typography, Colors, Background, and plugin settings. An individual page can have its own Theme Options panel, where you control settings for that page only, including header/footer style, widget set, body style, content, colors, and other overrides. Layouts are separate templates for the header, footer, sidebar, and special areas, and they are edited in Elementor.

This approach gives you flexibility, but it also requires discipline. If changes are made in different places without documentation, after a month no one will understand why the homepage uses one footer, the property card uses another, and the mobile version uses a third. For a working project, keep a short configuration map: global header, global footer, the Layouts in use, pages with overrides, widget areas, and forms. A simple project document is enough for that.

Global Settings Worth Reviewing First

Start with Site Identity: logo, site title, and site icon. Then move to Typography and Colors. The ThemeREX page highlights flexible colors and typography, and the documentation explains the related Customizer sections. There is no need to change every color immediately. Manoir already has a premium palette built in: deep charcoal tones, white space, a warm golden-terracotta accent, architectural imagery, and bold modern typography. Work with that base and replace only the accent if the project brand requires a different color.

After colors, review Header, Footer, Mobile, and Menus. For mobile, the documentation provides separate header and footer layouts, which is useful for performance: hidden elements can still load, so a dedicated compact mobile layout is often better than one overloaded desktop layout with many hidden blocks. In practice that means: on mobile, keep the logo, menu, phone number, or inquiry button, and move heavy decorative elements farther down the page.

Page-Level Theme Options

Each Manoir page can have its own Theme Options panel. That is useful when the homepage needs a transparent header over the hero section, while standard pages use a regular header on a light background. It can also assign different widget sets, footer styles, body style, and color schemes. But it is also the reason "mysterious" differences between pages often appear. If a change made in the Customizer is not visible on a specific page, open that page in the admin area and check Theme Options: it may be using a specific value instead of Inherit.

A good rule is to use overrides only where they are actually necessary. For the homepage and property pages, that is normal. For dozens of standard pages, it is usually better to keep global inheritance in place, otherwise maintenance becomes expensive.

Layouts for the Header, Footer, and Utility Areas

Custom header and footer layouts are available when ThemeREX Addons is active. The documentation notes that custom footer area elements are edited in Dashboard > Layouts, and menus can be added using the Elementor widget Layouts: Menu. That opens up a practical workflow: create a dedicated header for the property landing page, a dedicated footer with sales department contacts, a separate blog sidebar layout, and a compact mobile layout.

When editing Layouts, think in terms of reuse. For example, a "Sales Department Contacts" footer can be applied to the homepage, the floor plan page, and the contact page. A blog footer can be simpler and focus on content navigation. If every page gets its own unique footer, the site will start to feel visually inconsistent.

A Post-Change Verification Routine

After every major change, run a short verification cycle. First review the page in the editor, then open the public version in a private window, then check the mobile width, and then clear cache if caching is enabled. If the display still looks wrong, ask yourself four questions: was the change made in the Customizer or in Layouts, is there a page-level Theme Options override, is the required plugin active, and could cache be interfering? That routine is faster than changing everything at random.

Property Pages, Apartment Cards, and Amenity Blocks

The most product-specific part of Manoir is the way it presents real estate through visual cards, floor plans, amenities, and dedicated pages. The demo shows an Available apartments section with cards that include a floor plan name, status, size, and type. On a real site, that block should be more than decoration, it should become the center of navigation. Visitors should not have to hunt through paragraphs for essential details: if they are comparing options, the card should surface the basics quickly and lead them to the full information.

What a Property Card Should Include

For a residential complex, the minimum set is usually this: floor plan or unit name, status, size, type, an image or plan, a button leading to the detail page, and an inquiry link. If you also have floor level, price, building section, view, or estimated readiness date, add them only when the information is confirmed and publishable. Do not make the card look like a classified listing if local rules or legal restrictions prevent you from publishing a specific price or status. In that case, use a neutral label like "Check availability" and route the visitor to a contact form.

Manoir makes it easy to separate the visual and factual parts of the card. The image attracts attention, and the short parameters help visitors compare options. Make sure every card is filled out consistently. If one floor plan includes size, status, and type while another shows only a title, the grid feels unreliable. Consistent data across cards matters more than decorative effects.

How to Build an Individual Property Page

On a property page, visitors expect more detail: a gallery, floor plan, description, benefits, availability, location, contact terms, documents, and a form. In Manoir, you can build that page in Elementor using the theme's built-in styling, sections, imagery, spec tables, and contact blocks. If the theme imported ready-made property layouts, use them as a starting point, but replace the demo content completely.

Check that there are no clickable elements leading nowhere. Demo sites often include many links such as Read More, Learn More, About Us, and Go to Shop. After moving to the live site, every one of those should have a clear destination: an inquiry form, floor plan, gallery, terms section, contact page, or store. An empty button on a real estate page looks unfinished and reduces trust.

Amenity Blocks Without Generic Claims

Manoir presents benefits attractively through amenities and services cards. But standard labels such as Security 24/7, Social spaces, Maintenance, and Parking do not actually explain much on their own. On a real project site, every benefit needs specifics: where the parking is located, whether there are guest spaces, how security works, which recreation areas are available, who maintains the grounds, which services are included, and what restrictions apply to visitors.

If a benefit cannot be verified, do not place it on the homepage. Five honest blocks are better than ten polished promises. That matters especially in real estate, because a buyer or renter may make a decision based on those stated conditions. If the project is subject to legal advertising rules, have the wording reviewed by the appropriate specialist.

Galleries, Plans, and Media

Manoir supports visually rich pages, but real estate imagery should be optimized before upload. Use consistent aspect ratios for cards, separate large images for the hero section, compressed versions for previews, and meaningful alt text. If the floor plans are detailed, do not insert them only as tiny decorative images. Provide a link to a larger version or a PDF, add a caption, and explain what the visitor is looking at.

Videos and panoramas are best placed below the hero section rather than used as the only proof point. Not every visitor will play a video, and search engines and assistive technologies do a worse job with information that exists only inside a video. Key property details should always have a text-based equivalent.

Practical Workflow: Build a Project Homepage Without Losing the Message

Imagine a common task: you need to quickly prepare a website for a new residential complex in Manoir. The team has a logo, several building renders, a list of benefits, 6 floor plans, sales department contacts, a neighborhood map, and an inquiry form. The goal is a homepage where visitors can understand in one pass what the property is, why it is compelling, which options are available, and how to contact a manager.

Goal and Preparation

The goal of this workflow is not to recreate the demo pixel for pixel, but to keep its strong structure and replace it with real project data. Before you begin, the theme, child theme, ThemeREX Addons, Elementor, and the minimum required set of recommended plugins should already be installed. The demo data should already be imported into a staging site. The homepage should be assigned through Settings > Reading or Appearance > Customize > Homepage Settings.

Prepare a separate project folder: logo files in several sizes, the hero image, 4-6 benefit images, floor plan images, section copy, phone number, email, address, social links, legal notes, the privacy policy file, and the consent text for the form. It is the least exciting part of the process, but it speeds up the actual Elementor work dramatically.

Homepage Setup Steps

1. Open the selected demo page in Elementor and save a copy so you always have a version to roll back to.
2. Replace the logo and Site Identity in Appearance > Customize, then check the header on both the homepage and an internal page.
3. In the hero section, replace the building image, headline, short supporting text, and button. Point the button to the floor plans block or the form, not to an empty section.
4. In the benefits block, keep only the real advantages of the complex. For each one, add a photo, a short title, and one or two sentences with verifiable substance.
5. In the Available apartments section, replace the cards with real floor plans. Include status, size, and type if that information can be published.
6. Add a Contact Form 7 form or another chosen lead method. Verify that the email goes to a working address and that the user sees a clear confirmation message after submitting.
7. Configure the footer through Layouts or the Customizer: contacts, address, menu, document links, social media, and business hours if they are actually needed.
8. Open the page in incognito mode and test every link, button, form, map, mobile menu, and the hero section load speed.

Expected Outcome

After setup, the homepage should feel like a cohesive project page rather than a demo with a swapped logo. Visitors see a real property, understand the core offer, can move to the floor plans, see the main benefits, find the contact details, and submit an inquiry. In the admin area, the team should clearly understand where to edit each layer: text and sections in Elementor, global styles in the Customizer, the header and footer in Layouts or Header/Footer settings, and the form in Contact Form 7.

Result check: ask someone who was not involved in the setup to open the homepage and answer three questions within 60 seconds: what is being sold, which options are available, and how to get in touch. If they cannot answer, the problem is not the design, it is the information structure.

A Common Pitfall

After demo import, some images may be replaced with placeholders because the clipart from the live preview is not included as a ready-to-use licensed package. That is a normal limitation, but it cannot be left in a published site. If real photos are not ready yet, use neutral temporary project renders, schematic floor plans, or carefully chosen neighborhood imagery, but label them honestly. Do not present demo photos as if they show the actual property.

Forms, Leads, Booking, and Store Features: Enable Only What the Project Needs

The ThemeForest page and the documentation mention compatible plugins such as Contact Form 7, MailChimp for WordPress, WooCommerce, WP Booking System, Slider Revolution, and others. For a real estate website, that does not mean every workflow should be enabled immediately. A good setup starts with one question: what action should the visitor take? For a single complex, consultation requests, floor plan review, and phone calls are often enough. Rentals may need a booking calendar. Selling related services may justify WooCommerce. Construction updates may justify a newsletter signup form.

Contact Form 7 for Lead Capture

Contact Form 7 works well for simple forms: name, phone, email, floor plan of interest, comments, and consent to data processing. The plugin's official documentation shows the standard workflow: create the form in Contact > Contact Forms, then insert it into the page with a shortcode. In Manoir, that form can be added to an Elementor section, a contact page, a popup, or a block below the floor plan cards.

Do not test the form only visually. Submit a test lead, check the admin email, review the on-page confirmation text, confirm spam protection, and verify required fields. If messages are not arriving, the issue is usually not the theme but WordPress email delivery. On a production site, use an SMTP plugin or a mail service, but do not store email account secrets in places that a contractor can see unless that access is actually required.

WP Booking System for Rentals or Viewings

WP Booking System can be useful if the site is promoting rentals, property viewings, short-stay apartments, or an availability calendar. But for apartment sales in a residential complex, a calendar is not always necessary. If booking is not part of the real business process, do not add it just because the theme supports it. A "Schedule a viewing" form handled by a manager may be the better option.

If you do use a calendar, check three things: whether open dates are easy to understand, whether it connects properly to the inquiry form, and whether the manager receives the right notifications. On the property page, visitors should clearly understand what they are booking: a viewing, a consultation, an apartment, or a service. Do not combine those into a single confusing block.

WooCommerce for Services and Related Offers

WooCommerce makes sense in Manoir if the site is actually selling additional services, bookings, consultations, design packages, parking spaces as standalone products, or another true e-commerce workflow. But if the only goal is to collect inquiries for a property purchase, a full store may complicate the journey. WooCommerce adds a cart, checkout, transactional emails, order statuses, account pages, and its own settings. That is useful for sales, but unnecessary for a standard interest form.

If the store is needed, configure it separately: currency, taxes, shipping or the lack of it, payment methods, emails, cart and checkout pages, return policy, and a test order. Then check how the WooCommerce elements render within Manoir's styling. The theme claims compatibility, but the exact result still depends on your WooCommerce version, active extensions, and any template changes you have made.

MailChimp and Newsletter Signup

Newsletter signup can be useful for construction updates, sales launches, new floor plans, or open house events. MailChimp for WordPress can be connected to a signup form, but do not turn every form into a subscription form without explicit user consent. On a real estate site, it is better to keep forms separate: one for consultation requests and one for updates. That way users understand what will happen after they submit.

Mobile Performance and SEO Without Unrealistic Promises

Manoir advertises a responsive and mobile-friendly layout, retina image support, optimized performance, and an SEO-friendly approach, but those qualities do not remove the need for testing. The theme gives you a strong base, but the final speed depends on images, sliders, active plugins, hosting, caching, fonts, embedded maps, video, and the number of Elementor sections. On a real estate site, visuals matter, but they are also the most common source of heavy page loads.

Treat Mobile as Its Own User Journey

Do not test the mobile version only by narrowing a desktop browser window. Open the page on a real phone or at least in developer tools. Check how the hero looks, whether the menu covers the heading, whether the floor plan cards are readable, whether the inquiry button is easy to tap, whether the form is too long, whether images are getting cropped, and whether horizontal scrolling appears. The Manoir documentation specifically describes Mobile settings and mobile header/footer layouts, so use them if the desktop header is too heavy.

For the mobile hero section, it often helps to shorten the copy, reduce decorative elements, highlight one primary button, and move secondary links lower on the page. If the desktop hero feels like a premium editorial spread, the mobile version should still function as a clear entry point into action.

Speed: What to Optimize First

Start with images. Compress the hero, cards, gallery, and background images to a reasonable size, use modern formats where your site supports them, and do not load full-size renders into small cards. Then review sliders and popups. Slider Revolution can be useful for a visually dramatic project, but for a straightforward homepage, a static hero with one strong button is often faster.

The next layer is plugins. Disable anything that is not part of the current workflow. If the store is not in use, do not keep WooCommerce and related add-ons active across the site just for some hypothetical future use. If there is no calendar, disable booking. If there is no newsletter yet, do not load a signup form in the footer. Manoir's speed depends not only on the theme, but also on how disciplined the site build is.

SEO: Structure Over Keyword Stuffing

Since this guide will sit below an existing H1 and a short description, the live product or property page should avoid repeating the same name in every heading. On a real estate site, SEO is supported by clear sections: property overview, benefits, floor plans, infrastructure, map, FAQ, documents, contact details, and construction updates. Manoir can present those blocks beautifully, but the actual search value comes from factual content.

Images should have meaningful alt text. Do not repeat the same generic word like "image" or the theme name in every alt attribute. For a real property, describe what the image shows: facade, courtyard, floor plan, recreation area, neighborhood map, sales office. If it is a generated illustration for a guide, the alt text should explain its instructional purpose.

A Safe Custom CSS Tweak for the CTA

If the CTA button in the hero section is hard to read against the dark half of the screen after setup, a small reversible CSS adjustment can help. The basis here is not a hidden theme API but standard WordPress and Elementor behavior: in Elementor, you can assign a custom CSS class to the button in the Advanced section, then add CSS in Appearance > Customize > Additional CSS or in the child theme. First assign the button the class manoir-hero-cta, then add:

.manoir-hero-cta .elementor-button {
  box-shadow: 0 14px 32px rgba(0, 0, 0, 0.24);
  border: 1px solid rgba(255, 255, 255, 0.18);
}

.manoir-hero-cta .elementor-button:hover,
.manoir-hero-cta .elementor-button:focus {
  transform: translateY(-1px);
}

This tweak does not modify parent theme files and is easy to roll back by removing the class or the CSS. After adding it, check the hero section on desktop and mobile, verify keyboard focus, text contrast, and the absence of layout shifts. If the button already has its own built-in hover effects from the theme, do not add extra transforms without testing, or you may create conflicting animations.

Final Review Before Publishing

When the page looks finished in Elementor, the work is not done yet. You still need to review it as a user, an administrator, and a site owner. The user checks whether the offer is clear and whether it is easy to submit an inquiry. The administrator checks where key blocks are edited and whether they will survive updates. The owner looks at legal wording, contact details, performance, analytics, and the risk of outdated content.

Public-Facing Review

Open the homepage without logging into WordPress. Walk through the path: hero section, benefits, floor plans, property page, form, contact details, footer. Click every button. Test search if it is enabled. Open the cart if WooCommerce is in use. Check for demo addresses, lorem ipsum, other people's names, random links, empty Read More buttons, and watermarked images. In real estate, small details matter: a single outdated email address or someone else's address in the footer can damage trust.

Administrative Review

Open the page in Elementor and make sure the editor is not reporting errors. Then check Appearance > Customize, Theme Panel, Layouts, Appearance > Menus, Appearance > Widgets, and the form sections. Document which Layout controls the header and footer, which pages have their own Theme Options, which forms are in use, and where their emails are sent. That will help later during theme updates, contractor handoffs, or site migration.

Technical Review

Test the site in multiple browsers, at mobile widths, with cache enabled and disabled. If WPML is in use, check language switching, menus, and forms in every language version. If WooCommerce is enabled, place a test order or at least go through checkout without real payment if payments are not connected yet. If a calendar is in use, test both available and unavailable dates. If a popup is enabled, make sure it does not cover the inquiry form and does not appear too aggressively.

Minimum launch standard: a visitor can open the site, understand the property, compare options, submit an inquiry, and receive a clear confirmation, while the administrator knows where every key block is edited.

Replacing Demo Content Without Breaking the Design

In themes like Manoir, demo content often serves two roles at once. It shows what the site can look like, and it acts as a technical starting point for Elementor sections, Layouts, menus, widgets, and cards. The problem starts when the site owner treats the demo text as generic filler and changes only a few words. For a residential complex, the meaning structure has to be more precise: one block explains the project, another covers the available options, a third presents the living environment, and a fourth builds trust and connects the visitor to the sales team.

Start by replacing not the text itself, but the role of each section. In the Manoir reference, the hero says "Welcome to Our Exquisite Residential Complex," followed by a mission section, amenity cards, a "Discover the area of luxury" block, then available apartments and amenities. On a real site, that can become a sequence like this: "Project name and key value" - "What makes this property different" - "Infrastructure and living environment" - "Floor plans and statuses" - "How to schedule a viewing" - "Answers to common questions" - "Contact details." If a section does not support that flow, it is better to remove or move it than to keep it for looks alone.

How to Rewrite Copy in Large Sections

For the hero section, use a short headline that can be understood at a glance. Do not overload it with legal details, a list of benefits, or every apartment type. The subheading should provide context: the neighborhood, property format, site purpose, or stage in the customer journey. The button should lead to the next useful action: floor plans, the form, the map, or contact details. If you use two buttons, they should clearly differ in purpose, for example "View Floor Plans" and "Schedule a Viewing."

For the mission and benefits sections, avoid broad claims like "a new level of comfort" unless they are backed by evidence. Manoir visually leans toward premium language, but that is not a reason to fill the page with empty formulas. Replace generic emotion with verifiable features: a gated courtyard, waterfront views, underground parking, a club area, a playground, energy-efficient materials, management company services, or transit access. If a fact cannot be published yet, leave it out of the live page.

For floor plan card blocks, define a consistent status vocabulary in advance. The demo uses labels such as Ready for occupancy, Pre-selling, For sale, Reserved, and others. On an English-language site, you can use terms like "Available," "Pre-Sale," "Sold," "Under Construction," or "Check Availability," but they need to match the actual sales process. Do not mix a marketing status with a legal transaction status. If a sales team updates this data manually, create an internal rule for who changes statuses and how often.

Photography and Visual Proof

In Manoir, images carry a huge share of the site's trust. When replacing demo graphics, stick to a coherent direction: the facade, courtyard, floor plans, interiors, infrastructure, map, and team should all look like parts of the same project. If you mix photorealistic renders, random stock interiors, old construction photos, and different color treatments, the site loses its cohesion. It is better to use fewer images temporarily and bring them into a consistent treatment than to fill every card with mismatched illustrations.

Also review image rights carefully. Official ThemeREX sources warn that clipart from the live preview belongs to its respective copyright holders and is not included as free content for your website. That means demo photos cannot remain as the final property images after import. For publication, use your own developer materials, purchased photography, licensed renders, or specially prepared visuals. You cannot build trust in a real estate project using someone else's imagery that does not belong to the property.

How to Clean Up Extra Demo Pages

After a full import, WordPress will usually contain more pages than you need for the first launch: multiple homepages, services, team, pricing, FAQ, contacts, blog layouts, shop pages, and other examples. Do not delete them randomly right after import. First open the page list and mark which ones are used in menus and which are assigned as the homepage, posts page, WooCommerce pages, or Layouts. Then move the unnecessary pages to draft. Delete them only after you confirm that no menu, button, card, or widget still points to them.

For a single-property site, the essentials are usually the homepage, a floor plans or properties page, a contact page, a privacy policy page, FAQ, and a few utility pages. A blog makes sense only if the team is ready to regularly publish construction updates, neighborhood articles, status changes, and useful content. An empty blog with four demo posts looks worse than having no blog at all.

Content QA After Replacement

Once all text and images have been replaced, do a separate content audit. Go through the page from top to bottom and list every promise: "underground parking," "24/7 security," "park nearby," "ready for move-in," "premium finishes," "installment plans," "schedule a viewing." Every one of those promises should have a source inside the project: a document, photo, map, floor plan, internal policy, manager confirmation, terms page, or approved wording. If there is no source, replace the claim with more cautious language or remove it.

This approach may feel slower, but it protects the site from the main weakness of template-based real estate pages: polished design paired with inaccurate or empty information. Manoir gives you a strong form. Your job is to fill it with facts that stand up to scrutiny from both visitors and the sales team.

Updates, Maintenance, and Safe Long-Term Use

A premium theme is not a one-time install. Manoir has a changelog on ThemeForest, receives ThemeREX updates, includes bundled plugins, and depends on WordPress, Elementor, WooCommerce, and other extensions. That means a live site needs a simple maintenance routine after launch. It does not have to be complicated, but it should be regular: backup, staging copy, update, verification, and deployment to the live site.

The ThemeREX documentation describes the ThemeREX Updater and the ability to create backups before updating if that option is enabled. It also explains the difference between updating through the updater and uploading the installable file through the WordPress uploader. You do not have to update manually every time, but you do need to understand where theme and bundled plugin updates come from. Third-party plugins from WordPress.org follow their own update paths, while bundled premium plugins may come with a new theme release or require a separate license for direct updates from the plugin author.

How to Update the Theme Safely

Before updating, back up both the files and the database. If the site is receiving leads, create a staging copy and update that first. After the update, check the homepage, property cards, forms, menus, Layouts, Customizer, mobile version, and WooCommerce workflows if they are in use. Only then should you push the update to the live site. If the update affects Elementor, ThemeREX Addons, or WooCommerce, the review should be broader because those components affect both visual blocks and user actions.

Do not keep custom edits inside the parent theme. If you added CSS in Additional CSS or in the child theme, updating the parent theme should not erase those changes. But if you edited files in the parent theme directly, they may disappear with the next update. The WordPress Developer Handbook clearly explains the value of a child theme: your customizations remain separate and parent updates do not overwrite them. That matters especially in Manoir because the theme makes active use of its own folders and framework layer.

What to Do With Bundled Plugins

The Manoir documentation explains that bundled plugins may work functionally without separate activation with the plugin author, but direct updates and support from the plugin team are usually available only to direct buyers. That is not a problem if you understand the model. In a production project, keep track of which plugins came with the theme, which were installed from WordPress.org, which were purchased separately, and which ones the site actually uses.

If Slider Revolution is being used only for one decorative hero area, consider whether a standard Elementor section could replace it. If WooCommerce is enabled but the store is not in use, disable it after checking dependencies. If WP Booking System is needed on only one page, confirm that it is not adding unnecessary load across the whole site. That kind of audit reduces conflict risk and improves performance.

ThemeREX Support and Where Their Responsibility Ends

The ThemeREX Support Center states that support covers theme installation, theme functionality, compatibility with included plugins, and obvious theme bugs, while third-party customizations and integrations are more limited. That matters for setting expectations. If you changed templates in the child theme, added a non-standard caching layer, connected a third-party builder, or rewrote WooCommerce templates, not every issue automatically becomes a Manoir issue.

Before contacting support, prepare a precise report: page URL, screenshot of the symptom, active plugin list, reproduction steps, what has already been checked, whether cache was disabled, whether the issue appears in both the child and parent theme, and whether there are errors in the browser console or server logs. The more exact your request is, the better your chances of getting a useful answer.

Multilingual Setup, Localization, and Legal Pages

Manoir advertises translation readiness, WPML compatibility, and RTL support without separate RTL demo content. For a real estate project, that may be critical: buyers, investors, renters, and partners often use different languages. But multilingual support in a theme is not just about translating page copy. You also need to translate menus, forms, emails, buttons, Layouts, widgets, WooCommerce pages, theme strings, error messages, cookies, the privacy policy, and SEO metadata.

What to Translate First

Start with the user journey. In every language, the hero section, floor plans, inquiry form, contacts, FAQ, privacy policy, and post-submit confirmation should all work correctly. If WooCommerce is in use, translate the cart, checkout, emails, and system messages. If WP Booking System is active, review the calendar and notifications. If the site uses separate header/footer Layouts, make sure they are either translated or correctly display the right menus and contact details.

Do not translate technical admin UI labels for editors if the team works in an English-language WordPress backend. But all public-facing labels for visitors should match the page language. That matters especially for forgotten demo labels such as Read More, Learn More, View More, Send Brief, Go to Shop, and similar text that often remains after import.

RTL and Manual Section Adjustments

The Manoir documentation states that RTL text direction is supported, but without separate RTL demo content, and that page content may require manual adjustments in Elementor, such as icon alignment. That is an honest limitation. If the site is planned for a right-to-left language, do not stop at enabling the language in WordPress. Check every key section: hero, menu, cards, forms, sliders, icons, gallery, floor plans, footer, and popup.

For RTL, it is best to create a separate QA checklist. Make sure the card order feels logical, icons are not pointing the wrong way, slider arrows do not confuse navigation, form fields read properly, and numeric values for sizes and statuses do not break the grid. If one section is especially complex, it is often easier to rebuild it manually for RTL than to try to mirror the whole design automatically.

Legal Pages and Form Consent

A real estate website collects leads, phone numbers, email addresses, and possibly preferences related to floor plans or viewing times. That means forms should be tied to the privacy policy and a clear consent statement. Contact Form 7 allows you to add a checkbox and consent text, but the wording still needs to match the legal requirements of your region and business. Do not copy legal text from a demo or another site without review.

If the site uses cookies, analytics, ad pixels, newsletter forms, or CRM integrations, add the appropriate notices and documentation. The theme may support Cookie Information or a similar plugin, but the plugin does not solve the legal side by itself. It only displays the consent interface. The content of the policy and the data handling process remain the responsibility of the site owner.

An Editorial Workflow for the Team After Launch

After launch, a Manoir site often ends up in the hands of a content manager, marketer, or sales team. Without a simple operating guide, a polished design can fall apart within a few weeks: inconsistent image sizes, overlong card titles, new sections with broken spacing, random colors, outdated statuses, duplicated buttons, and forms going to different recipients. In a theme with a strong visual composition, those problems are especially noticeable.

What to Put Into a Short Internal Document

The document does not need to be long. One page is enough if it covers the rules: which image sizes to use for the hero and cards, where the homepage is edited, where floor plans are updated, who owns status changes, which buttons are allowed, which colors are used, where the inquiry form lives, who checks the incoming emails, how often information is updated, and who approves new blocks before publication. Also note which pages must not be deleted because they are assigned as the homepage, checkout, privacy policy, or are used in menus.

For Elementor, document one core principle: do not create a brand-new style for every section. Use existing Manoir blocks as the base. If a new section is needed, duplicate a similar one, replace the content, and only then adjust the details. That helps the site preserve the rhythm of the original template: bold headings, wide imagery, warm accents, clean cards, and generous spacing.

How to Update Property Statuses

If the site includes an Available apartments block or something similar, statuses should be updated through a clear process. For example, the sales manager reports the change, the editor updates the status on the card, verifies the public page, and logs a screenshot or note in a change record. If a unit is no longer available, do not leave the inquiry button unchanged without explanation. You can replace it with something like "Ask About Similar Options" or send the user to a matching-request form.

Do not use too many different statuses. The more variants you have, the greater the chance of confusion. For most sites, 4-5 clear states are enough. What matters is that the visitor understands what to do next. A status like "Reserved" ends the journey if nothing else is offered. A label like "Check Availability" keeps the conversation going.

Quality Control for New Content

Before publishing a new article, service page, or floor plan, check four things: visual consistency, factual accuracy, link behavior, and mobile usability. Visual consistency means the new page does not clash with Manoir in fonts, colors, spacing, or imagery. Factual accuracy means sizes, statuses, addresses, phone numbers, and terms match the internal data. Link behavior means buttons lead where they promise. Mobile usability means visitors can read the page and submit the form without zooming.

That kind of workflow turns Manoir from "a nice-looking template after import" into a manageable website. That matters especially in real estate, where information changes, but trust in the project needs to remain stable.

Troubleshooting Common Manoir Issues

Most problems with premium WordPress themes do not come from one single "broken" point, but from a combination of the archive used, file permissions, server limits, plugins, cache, and page-level overrides. Below is a practical troubleshooting guide for Manoir and similar ThemeREX themes.

WordPress Says the Theme Does Not Have style.css

Symptom: uploading the ZIP through Appearance > Themes > Add New > Upload Theme ends with an error saying style.css is missing. A likely cause is that the full ThemeForest package was uploaded into WordPress instead of the installable theme ZIP, or the archive contains an extra folder level. Envato and the Manoir documentation both describe this as a standard installation mistake.

What to check: extract the full package locally and locate either manoir.zip or the manoir folder with style.css inside it. If you are installing through FTP, /wp-content/themes/manoir/ should contain style.css directly, not another nested folder. The fix is to upload the correct archive or the correct folder. Rollback is simple: delete the incorrectly uploaded theme folder through the file manager and repeat the installation carefully.

Demo Import Freezes or Does Not Import Media

Symptom: the import stalls on one step, shows a data upload error, does not import images, or finishes with an incomplete site. Likely causes include a low memory_limit, small upload_max_filesize, short max_execution_time, slow hosting, heavy extra plugins, or the demo archive being unavailable.

What to check: PHP limits, active plugins, hosting error logs, and the chosen import mode. The Manoir documentation suggests disabling Import Media if the import is stuck on media and importing the rest of the data first, and it also notes that if the data upload fails, the demo folder may be transferred manually into wp-content/themes/manoir/demo. The fix depends on the cause: raise limits, disable large plugins, rerun the import without media, contact the host or ThemeREX support. Rollback means restoring the backup before attempting another full import.

Global Settings Do Not Affect a Specific Page

Symptom: the header, footer, widgets, or colors were changed in the Customizer, but the homepage or a property page still looks the same. The cause is often the page's own Theme Options, since the documentation notes that those settings override the global values.

What to check: open the page in the admin area, find Theme Options, and inspect the Header, Footer, Widgets, Colors, and Content values. If a specific layout or style is set there, temporarily switch it to Inherit and check the result. The fix is to keep overrides only where they are actually needed and return the rest of the pages to inherited settings. Rollback means restoring the page's saved values or a copy from before the change.

A Custom Footer Does Not Update in the Customizer

Symptom: the user changes the footer in Appearance > Customize, but nothing changes on the site. A likely cause is that a Custom Footer Layout is selected, which is available only when ThemeREX Addons is active and is edited through Dashboard > Layouts, not through standard Footer widgets.

What to check: in the Customizer, look at Footer style, then open Layouts and find the assigned footer layout. If ThemeREX Addons is disabled, custom layouts may not work. The fix is to edit the correct layout in Elementor or switch Footer style to Default if you need a normal widget-based footer. Rollback means restoring the previous layout or selecting Inherit at the page level.

The Form Looks Fine, but Leads Never Arrive

Symptom: Contact Form 7 shows a successful submission, but the message never reaches the manager. In most cases, the cause is not Manoir but WordPress email delivery, Mail field settings, SPF/DKIM domain policy, spam filtering, or an incorrect recipient address.

What to check: submit a test lead, inspect the spam folder, review the form settings, sender and recipient addresses, and the SMTP plugin log if one is installed. The fix is to configure delivery through a reliable SMTP setup or mail service, align the From address with the site domain, and add SPF/DKIM records to the domain. Rollback means returning to the previous form settings and testing delivery against a known test address.

The Mobile Menu Covers the Hero Section

Symptom: the hero looks good on desktop, but on mobile the menu, logo, or button covers the heading and image. The reason is usually that one heavy header layout is being used for every screen size, Header position is set to Over, and the hero spacing has not been adapted.

What to check: Mobile settings in the Customizer, the assigned mobile header layout, section padding in Elementor, and the page's Theme Options. The fix is to create a compact mobile header, reduce the hero copy, add top spacing, or change the header position for the affected page. Rollback means restoring the previous header layout and rechecking the page after clearing cache.

Questions Worth Settling Before Launching Manoir

Can Manoir Be Used Without Elementor?

You can create new posts and simple pages in Gutenberg, but the Manoir documentation makes it clear that the existing demo pages and layouts are built in Elementor and are meant to be edited there. If you want the demo look and an easy way to manage homepage sections, Elementor effectively becomes part of the working setup.

Do You Have to Import All Demo Data?

No. Full Import is convenient for a new staging install where you want a full copy of the demo site. On an existing site, partial import or manual page building is safer. With partial import, you will still need to replace placeholder images and reconnect widgets to real categories, posts, or properties.

Why Are the Same Images From the Demo Missing After Import?

The ThemeForest page and ThemeREX documentation state that live preview clipart and images belong to their respective copyright holders and are not included as a ready-to-use package for your website. That is a normal limitation of premium themes. Use your own photography, licensed images, or project renders instead.

Is WooCommerce Necessary for a Residential Complex Website?

Only if the site actually includes a store, paid services, paid booking, or another real checkout flow. For a standard apartment inquiry workflow, WooCommerce may be unnecessary. Start with a contact form and floor plan cards, and add the store only when there is a confirmed business need.

What Should You Do if Demo Import Fails on Shared Hosting?

Check the PHP limits, temporarily disable heavy plugins, try importing without media, and contact your host if the limits are below the recommended values. Do not rerun a full import on a live site without a backup. If the error is tied to the demo file upload, the documentation describes a manual demo-folder placement method, but it is best done on a staging copy.

Can You Edit the Parent Theme Files Directly?

For safe long-term maintenance, no. WordPress and the Manoir documentation recommend using a child theme for file-level changes. For small visual adjustments, start with the Customizer, Elementor, Theme Options, Layouts, and Additional CSS. Keep the parent theme update-safe.

Is Manoir Suitable for a Multilingual Website?

The ThemeForest listing states WPML compatibility, and the documentation mentions translation readiness and RTL support without separate RTL demo content. For a real multilingual site, check the translation of menus, forms, theme strings, Layouts, WooCommerce pages, and Elementor sections. Do not stop at translating the standard pages.

How Do You Know the Site Is Ready to Publish?

Publish only after the homepage, property cards, forms, contacts, mobile menu, footer, legal links, and hero section speed have all been checked on a staging copy. If demo copy, non-working buttons, or an untested inquiry form are still present, the site is not ready, even if it visually resembles the demo.

When ThemeForest Manoir Is the Right Choice

Manoir is a strong choice if you need a visually distinctive WordPress theme for a residential complex, a single property, apartments, rentals, or a developer project, and the team is ready to work with the combination of WordPress, Elementor, ThemeREX Addons, the Customizer, and Layouts. The theme's main strength is its ready-made visual structure for premium real estate: a hero section, architectural blocks, benefit sections, floor plan cards, forms, a footer, a blog, and compatibility with widely used plugins.

Before publishing, do not stop at importing the demo. Adapt the structure to the real property, replace every image and every piece of copy, and test the forms, mobile version, header, footer, cards, links, and performance. If you need a large real estate portal with agent roles and a complex property database, compare Manoir with more specialized solutions. If you need a site for one project where visual presentation, clear navigation, and a fast WordPress launch matter most, the theme is a practical option.

Once the project materials are ready and the site workflow is clear, you can move to the download section and download the latest version of ThemeForest Manoir, then install it on a staging copy first. That sequence gives you room to test, protects the live site, and helps turn a beautiful template into a clear, useful page that actually helps visitors make a decision.