ThemeForest Archibecht - WordPress Theme

How to Use and Customize ThemeForest Archibecht

ThemeForest Archibecht is best understood not as just another WordPress theme, but as a ready-made set of Elementor templates for an architecture studio, construction company, interior design firm, or contractor that needs a polished website structure without a long build process. In this guide, we will break down what is actually included in the kit, how to prepare WordPress before import, in what order to move over global styles, pages, the header, the footer, and forms, and then how to confirm that the site is truly ready for real project content.

This guide does not repeat the short product summary. The practical side matters more here: where the line is drawn between the template, the WordPress theme, and Elementor, why Flexbox Container and the required plugins are critical for Archibecht, how to avoid losing the header when working through ElementsKit, how to insert MetForm forms, and how to replace the demo photography with your own assets without breaking the composition.

If you have already downloaded the archive and want to jump straight to installation, do not skip the preparation section. Most Elementor Template Kit issues come not from the layout itself, but from using the wrong ZIP file type, leaving container markup disabled, running into hosting resource limits, missing an active addon, or trying to install the kit as a classic WordPress theme.

What Archibecht Actually Installs and Where Its Responsibility Ends

The main point to start with is this: Archibecht is an Elementor Template Kit. A kit like this stores design data for Elementor: pages, blocks, forms, global styles, the header, the footer, and individual sections. It does not replace WordPress, it is not installed as a theme through Appearance -> Themes, and it does not include the full server-side logic people usually expect from a large theme or plugin.

The practical takeaway is simple: WordPress runs the site, the theme provides the base framework, Elementor builds the pages, and Archibecht brings the finished layouts and visual language. If you mix up those layers, you will run into familiar issues: a missing style.css message, empty imports, broken styles, or the expectation that the kit will create menus, blog posts, live services, and real project photography on its own.

The Archibecht product page says the kit is optimized for Hello Elementor and compatible with most themes that support Elementor. In practice, Hello Elementor is the best option for the initial setup: it is a lightweight foundation without extra styling, so it is less likely to conflict with imported sections. If you install the kit on top of a complex commercial theme, some spacing, headings, global styles, and containers may look different from the demo page.

Archibecht does not create a complete business website by itself. It gives you the visual framework: the homepage, service pages, project pages, contact pages, blog templates, forms, and global styles. The content is still your job. You need to replace the text, logo, menu, photos, projects, contact details, legal pages, consent forms, and SEO data. That is why the right workflow is not "import and publish," but "import, adapt, review, replace content, test the form, and only then open the site to visitors."

How a Template Kit Differs from a WordPress Theme

A WordPress theme controls the site’s core output: template files, menu support, widget areas, styling for standard pages, and sometimes Customizer or Site Editor settings. An Elementor Template Kit sits on top of that layer. It is imported into the Elementor library and then inserted into specific pages or special areas through Elementor, ElementsKit, or another supported method.

Because of that, the kit should not be installed through the theme uploader. If you upload the Archibecht archive in Appearance -> Themes, WordPress will look for the theme stylesheet file and may show an error. That does not mean the product is broken. It means you used the wrong installation method. Archibecht needs to be imported through Template Kit Import or the corresponding Elementor template import workflow.

What Is Included in Practical Terms

The product page lists the ready-made pieces: Global Kit Styles, Homepage, About Us, Services, Service Detail, Pricing Plan, Projects, Contact Us, Archive Blog, Single Post, Error 404, Header, Footer, Contact Form, and Newsletter Form. For an architecture or construction website, that is a solid starting grid: a company presentation, project showcase, service overview, contact point, and a basic blog structure.

But the value is not just in the number of templates. Archibecht uses a clear visual language that is visible in the reference screenshot: a large construction-focused hero area, warm brown and honey accents, white cards with soft corners, trust-building content blocks, a project portfolio, a video section, and calm typography suited to the construction niche. When adapting it, keep that structure intact: large real project photos, short headings, clear trust signals, a clean service list, and an obvious path to the inquiry form.

Who This Kit Fits Best and When You Should Choose Something Else

Archibecht is especially useful when a website needs to quickly communicate a company’s expertise through visual proof: project photos, portfolio pieces, services, team information, a contact form, and a few trust-building sections. That could be an architectural bureau, interior studio, construction company, engineering contractor, renovation workshop, design office, or a small development team.

For this kind of work, the kit covers the core site structure better than a blank Elementor build. You are not getting a single homepage, but a connected set of pages. You can start with Homepage, build out Projects, link a service to Service Detail, set up contacts through Contact Us, and expand the site with a blog. The main value of Archibecht is a consistent visual system, not unique business logic.

When Archibecht Is a Good Choice

The kit makes sense if the project needs a presentation-focused Elementor website without building everything from scratch. For example, a construction company may already have project photos and a service list, but not the time to design every section manually. Or an architecture studio may want to quickly launch a portfolio page, contact form, and clear navigation while keeping the ability to edit blocks without a developer.

• The site needs to be built on WordPress and Elementor.
• The team is ready to replace the demo images with its own licensed materials.
• You need ready-made pages for services, projects, contacts, a blog, and a 404 page.
• The project benefits from a construction or architecture look: large photos, a calm palette, trust sections, and a portfolio layout.
• There is no requirement for complex real estate catalogs, user accounts, cost estimators, CRM integration, or property booking.

When the Kit May Not Be the Right Fit

Archibecht may be too limited if the site needs to function as a service platform rather than a presentation site. For example, if you need property filters with a map, a real estate database, a renovation cost calculator, a customer account area, a complex lead workflow, contractor management, or integration with an internal CRM, the template kit alone will not solve that. Those features will need separate plugins or custom development.

You should also be cautious if the site already runs on a heavy theme with its own page builder, a large set of global CSS rules, and a custom header/footer system. In that environment, Archibecht may import successfully, but the final appearance will depend on conflicts between the theme, Elementor settings, and caching. For a clean launch, it is better to use a staging copy with Hello Elementor first and move the finished result to the live site afterward.

Do not judge Archibecht by the homepage hero alone. On an architecture website, the real value is in how the pieces connect: a service leads to a detailed page, a project proves experience, a form captures leads, and the header and footer keep navigation consistent across the site.

Archibecht Page, Block, and Dependency Map

Before importing, it helps to think of Archibecht as a map rather than a list of files. At the center is Global Kit Styles: colors, fonts, and the site’s core visual rhythm. Around that are the pages and blocks. Separate from them are the required plugins that power certain widgets, along with the MetForm forms that need their own insertion workflow.

Pages That Form the Site Structure

Homepage shapes the first impression. The reference screenshot shows a large construction-focused hero area, a value block, a company story, trust logos, a portfolio, and a video section. That is a strong sequence for a site where the visitor needs to understand the specialization quickly, see examples, and move toward contact.

About Us works best not as a formal biography, but as a trust page: team experience, design approach, work process, geography, core strengths, and photos of the office or completed projects. Services and Service Detail help separate general service categories from detailed offerings. For example, the main services page can present "Architectural Design," "Construction Oversight," and "Interior Solutions," while the detailed page can explain the phases, deliverables, documentation, and limits of a specific service.

Projects is one of the most important pieces for the architecture niche. If you leave the demo cards in place without real case studies, the site may look polished but it will not feel credible. For each project, it is better to prepare a title, object type, client goal, location without unnecessary personal data, several photos, a short process summary, and the outcome. If you do not yet have a deep portfolio, start with 3 to 4 strong examples instead of filling the grid with random images.

Blog Archive and Single Post Templates

Archive Blog and Single Post will not be useful for everyone. If the company is ready to maintain an expert blog, these templates can support posts about materials, construction phases, renovation, approvals, design, or property maintenance. If blogging is not part of the plan, it is better to hide the blog from the menu for now than to publish an empty archive or a few weak updates.

The blog templates should be reviewed separately: how the title looks, how the featured image behaves, how the date and categories are displayed, how wide the text column is, whether related posts work well, and how it looks on mobile. An Elementor template can look great with demo content, but real long headlines and images with mixed aspect ratios will reveal weak spots quickly.

Header, Footer, and Forms as Separate Systems

Header and Footer do not become global automatically just because they were imported. For Archibecht, the product page describes the setup through ElementsKit: you need to create a Header Footer template, choose the display area, enable activation, and insert the imported template. Then, inside the nav element, you need to select the real WordPress menu. If you skip that step, pages may open without a header or with the current theme’s header instead.

Contact Form and Newsletter Form are tied to MetForm. They should not be treated like ordinary text blocks either. The form must be imported, then selected inside the MetForm widget through Edit Form, New, Add Template, My Templates, and Insert. After insertion, update the form and review the fields, recipient address, and test submission.

What to Check Before Importing into a Clean WordPress Setup

Good preparation saves more time than fixing empty pages later. With Archibecht, it is better to start on a staging copy or a fresh test WordPress install rather than on the live site. That matters even more if the main site already has active forms, caching, security plugins, CSS/JS optimization, or another theme with its own global styles.

Platform and System Resources

Elementor needs a current WordPress, PHP, database setup, and enough memory. If the import stops midway, Elementor fails to load its panel, or templates are inserted only partially, check Elementor -> System Info first. Envato’s setup instructions also recommend confirming that the server meets Elementor’s requirements before importing the kit.

In practice, the key is not memorizing a specific number but recognizing the symptoms. If the server runs out of memory or execution time, the import may stop in the middle, some images may fail to load, and Elementor may throw an unexpected error. If PHP Zip is not enabled, the ZIP upload may be rejected. If the domain is in maintenance mode, password-protected, or has SSL issues, external requests and asset imports may behave unpredictably.

Theme, Elementor, and Flexbox Container

The best base stack for the first import is Hello Elementor active, Elementor active, and Flexbox Container enabled. The Archibecht product page explicitly says the kit is built on Flexbox Container. Envato’s official instructions also warn that new kits require the container system to be active. If templates look empty or misaligned after import, checking Flexbox Container should be one of the first troubleshooting steps.

In the admin panel, the path is usually Elementor -> Settings -> Features. The exact name and position of the setting may vary by Elementor version, so focus on the features tab and the container status. After changing the setting, clear caches and recheck the affected page.

Permalinks, Roles, and Plugins

Before importing, set permalinks to Post name through Settings -> Permalinks. That does not make the site faster by itself, but it reduces the risk of odd URLs and makes page checks easier. Work under an administrator role: 403 errors, access problems, and failed template imports are often tied to permissions, security plugins, or server rules.

Archibecht requires several free addons: ElementsKit Lite, Gum Addon for Elementor, Skyboot Custom Icons for Elementor, and MetForm. It is best to install them through Plugins -> Add New and activate them before reviewing the finished pages. If the Template Kit installer shows a requirements banner, use Install Requirements and then confirm that every dependency is actually active.

Photos and Demo Image Licensing

The product page notes that the demo images come from Envato and require a separate license or replacement with your own materials. For an architecture website, that is not just a formality. Photos of projects, construction sites, drawings, and the team are part of what builds trust. If you leave the demo images in place, the site may feel generic and create legal risk.

Prepare your own materials in advance: 8 to 12 horizontal project photos, 3 to 5 portraits or team shots, several process images, partner logos only where you have permission, a map or office photo, and image versions sized for the hero, project cards, and background sections. Do not upload giant original files without optimization: it is better to size them for the specific sections so the site does not pay for it in first-load performance.

Import Order: From Global Kit Styles to Pages

The order matters. If you import pages before global styles, some colors, fonts, and linked settings may need manual correction. Envato’s official instructions recommend importing Global Kit Styles first and then adding the templates one by one in the shown order. With Archibecht, that matters even more because the design depends on a unified palette, contrasting buttons, white cards, warm accents, and calm typography.

Uploading the Kit File

The downloaded ZIP does not need to be extracted if you are using the current Template Kit Import workflow. In WordPress, install the import plugin, go to Tools -> Template Kit, and upload the ZIP file. If the system asks you to install requirements, do that and confirm that the needed addons appear.

If instead you see a message saying the ZIP is not a valid kit, make sure you downloaded the actual Elementor Template Kit file rather than the full documentation package, a page archive, a theme ZIP, or a single JSON file. Envato offers several product types, and mixing them up is a common source of installation errors.

Import Global Kit Styles First

Global Kit Styles should be imported before the pages. After the import, open any test page in Elementor and check the base colors, fonts, and buttons. Archibecht visually depends on the combination of a large construction photo, a dark overlay, brown and gold accents, white content blocks, and soft cards. If all buttons turn gray after import, the fonts do not match the demo, and the spacing feels off, the global styles were either not applied or are being overridden by the theme or cache.

Do not rush into recoloring every button manually. First check Elementor Site Settings and the global colors. If you want to adapt the kit to your brand, it is better to change a few global colors and fonts than to edit dozens of individual widgets. That keeps the site manageable: update the accent, and the buttons, icons, lines, and highlights update with it.

Importing Pages and Inserting Them into WordPress Pages

After global styles, import the pages and blocks. The imported template is stored in the Elementor library, but it is not a published page yet. To create a live page, go to Pages -> Add New, set the title, open Edit with Elementor, insert the needed template from the installed kit, and choose the appropriate page layout.

Envato’s official instructions recommend using Elementor Full Width for pages so the global header and footer display correctly and the default theme title does not interfere with the layout. In special cases, you can use Elementor Canvas, but that hides the header and footer, so it is better suited to standalone landing pages or testing than to normal site pages.

Check After Every Major Step

After importing, do not wait until the end to spot a problem. Open the homepage, services page, projects page, and contact page in new tabs. Check whether the images are visible, whether icons are missing, whether the header appears, whether the menu works, whether the hero overlaps the next section, and whether there are huge empty gaps. If a problem appears after a specific template or plugin, it is much easier to fix then than after importing the entire kit at once.

Quick post-import check: the homepage opens without a blank canvas, the header is visible on all key pages, buttons use the accent color, project cards stay aligned, the contact form is inserted through MetForm, and the mobile preview does not break the menu.

Header, Menu, and Footer Through ElementsKit

To visitors, the header and footer look like ordinary parts of the site, but in Archibecht they depend on separate setup. The product page describes the workflow through ElementsKit -> Header Footer. That means importing Header and Footer alone does not guarantee that they will appear on the site.

Creating a Global Header

After importing the header template, open the ElementsKit header/footer area, create a new item, give it a clear name, leave it set to the whole site if you want one shared header, and enable activation. Then open the content editor, insert the imported header template from My Templates, and choose the actual WordPress menu in the nav widget.

A common mistake is inserting the header template but never creating the menu itself in Appearance -> Menus or never selecting it in the navigation element. As a result, the header may still show demo structure, an empty list, or incorrect links. For an architecture website, a minimal menu usually includes home, about, services, projects, blog or articles, and contacts. If there are many services, do not overload the top level: it is better to use a Services item with an overview page and link detailed services from the content itself.

The Footer as a Navigation and Trust Block

The Archibecht footer should be treated not as decorative page-end filler, but as a second orientation point. It should keep the contact details, a short company description, links to services and projects, the privacy policy, and social profiles if they are genuinely active. If the site collects leads, make sure the phone number and email in the footer match the form and the contact page.

After setting up the footer, open several pages: the homepage, a service page, a project page, a blog post, and the 404 page. The footer should stay readable everywhere, should not collide with content, and should not lose its colors. If the footer is missing on one page, check the page layout and the ElementsKit display conditions.

Sticky Header and Complex Menus

If ElementsKit or the current setup allows sticky behavior, use it carefully. For a construction website, a sticky header works well when the menu is short and the header is not too tall. If the header contains many items, a large logo, and dropdown menus, the sticky mode may take up too much space on mobile devices. Review desktop, tablet, and mobile previews first, then enable it on the live site.

For complex services, you do not always need a mega menu. In many cases, it is better to create a clear Services page where the categories are shown as cards and each card leads to Service Detail. That keeps the header clean and preserves Archibecht’s architectural look.

MetForm: Contact and Newsletter Forms Without Breaking the Design

Archibecht includes Contact Form and Newsletter Form. These blocks rely on MetForm, so after importing the page, the contact form may not work automatically. You need to import the form templates themselves and connect them to the widget on the page. If you skip that step, the user may see an empty space, a broken block, or a form without the intended styling.

How to Insert the Imported Form

Open the page where the form should appear in Elementor. Turn on Navigator, find the MetForm widget, and choose Edit Form. Then create a new form, open its editor, click the gray folder icon, go to My Templates, choose the imported form template, and insert it. If the system asks whether to apply page settings, it is usually safer not to apply them to the form so they do not conflict with the page settings. After insertion, click Update & Close, then update the page.

After that, configure the recipients, email subject, required fields, success and error messages, and spam protection if you are using it. MetForm supports different types of forms, but for Archibecht the usual needs are a contact inquiry and a newsletter signup. Do not turn the form into a long questionnaire in the hero area: for an initial inquiry, a name, email or phone number, subject, and message are usually enough.

What to Review Before Publishing the Form

Form testing needs to be real. Submit an inquiry from a separate email address and verify email delivery, entry storage, the on-page message, required fields, mobile width, and error behavior. If you use reCAPTCHA or another protection method, test it not only inside the admin panel but also on the public page in incognito mode.

A form is only considered configured after a successful test submission. A good-looking form that never delivers the email does not solve the website’s core job. For a construction company, a lost lead can cost more than an extra hour of setup.

Newsletter Form and User Expectations

The newsletter form should lead to a process the visitor actually understands. If the company does not publish regular content, it is better not to promise a newsletter. You can replace that block with "Request a Consultation," "Get a Project Portfolio," or "Discuss Your Project" if that type of communication fits the business better. In Elementor, that is usually easier than maintaining a signup flow that serves no real purpose.

If the newsletter form connects to an external email marketing service, do not guess your way through the integration. First confirm that the MetForm setup you are using supports the required delivery method, then test double opt-in, consent, and the notification text. The product article itself should not promise a specific integration unless it is confirmed by the sources.

Global Styles, Content, and the Architectural Presentation Style

Archibecht feels convincing when it is used as a system rather than a set of randomly imported attractive sections. The reference shows a clear composition: a large hero with a construction scene, an accent button, a trust block, company story, a card-based portfolio, and a video section. If you replace that with random stock imagery and long promotional text, the kit loses its strongest advantage.

Colors and Fonts

Start your adaptation with Elementor’s global colors and fonts. In the construction niche, a calm base usually works best: dark text, light surfaces, a warm accent for buttons and markers, and photo-driven sections with a careful overlay. If the brand uses a different color, change the global accent and review how it looks on buttons, icons, lines, and cards.

Do not change every heading locally. Elementor Global Colors and Global Fonts exist so the site keeps a consistent look. If the brand color changes a month later, a global setting will let you update the design system faster and more safely.

Project Photography

With Archibecht, photos matter more than decorative icons. Prepare images based on their role: the hero needs a strong wide shot, the portfolio needs a series of consistently processed cards, the about page needs team or process imagery, and service detail pages need focused visuals for each stage. Ideally, every project card should have not only an image but also a clear point: what the project is, what the task was, and what outcome it produced.

If you do not have many real photos, do not fill the whole site with lookalike stock construction shots. It is better to build an honest short portfolio and strengthen the services page with process details, workflow explanation, and testimonials. People trust architecture websites not because they have more pictures, but because the proof feels coherent.

Services and Project Storytelling

The Service Detail template should be adapted to the specific service. For "Architectural Design," the structure might include an introduction, project phases, required inputs, the client outcome, timelines expressed as a range rather than a promise, documentation, limitations, and an inquiry form. For "Construction Oversight," the needed blocks are different: work supervision, contractor communication, site visits, reporting, and photo documentation.

A project page should answer practical questions: what the task was, what the team did, what challenges were solved, and what outcome is visible. If a project card contains only a beautiful photo and a title, it works as a gallery item, not as proof of expertise. Archibecht gives you the grid and the visual tone, but the meaning of the case study has to be added manually.

Practical Example: An Architecture Studio Website with a Portfolio and Lead Forms

Let us look at a concrete example. A small architecture studio wants to launch a website quickly: a homepage, services section, 6 projects, a contact form, and a blog for expert content. The team already has a logo, project photos, service copy, and a contact email. The goal is to create a site that can be shown to prospective clients now and expanded gradually over time.

Goal and Preparation

The goal is to build a homepage with clear navigation, replace the demo blocks with real materials, connect the inquiry form, and verify the live result. Before starting, Hello Elementor, Elementor, Template Kit Import, ElementsKit Lite, Gum Addon, Skyboot Custom Icons, and MetForm are active. Flexbox Container is enabled, a WordPress menu has been created, and the Home, About, Services, Projects, and Contact pages are ready.

Step 1. Homepage and Hero Area

Create the Home page, open it in Elementor, and insert Homepage. Replace the hero headline with wording that reflects the real specialization, such as private home design, public interiors, or commercial spaces. Do not use a generic slogan just because it sounds polished. The hero area needs to answer three things for the visitor: who you are, what kinds of projects you handle, and why they should keep reading.

Replace the background image with a strong project or process photo. Make sure the text stays readable on top of it. If the contrast is weak, adjust the overlay in Elementor rather than inflating the text to an oversized scale. The button can lead to projects or the contact form, but it is better not to leave an abstract Discover More label in place. For a Russian-language site, that might become "View Projects" or "Discuss Your Project."

Step 2. Menu, Header, and Navigation

Build a short menu in Appearance -> Menus. Then open the header template through ElementsKit and select that menu in the nav widget. Make sure the menu items point to real pages rather than demo links. In the mobile preview, open the burger menu and confirm that the items are not cut off and do not overlap the logo.

Step 3. Projects and Services

Insert Projects on the portfolio page. Start with 4 to 6 projects, but make them meaningful. For each one, prepare a title, project type, and short caption. If you have full case studies, create separate pages for them with a suitable template or regular Elementor pages. In the services section, use Services as an overview and Service Detail for one priority service the studio wants to highlight.

Step 4. Contact Form

Open the Contact page, find the MetForm widget, insert the imported Contact Form, and configure the recipient. Adjust the field labels to match the site language if they are part of the visible form text, but leave the system UI labels in the admin panel unchanged. After updating, send a test inquiry and check the email. If the email does not arrive, review not only MetForm, but also WordPress mail delivery, the domain’s SPF/DKIM configuration, and any hosting restrictions.

Step 5. Final Review

Open the site as a normal visitor would: homepage, menu, projects, services, contacts. Check desktop, tablet, and mobile. Make sure the hero is not too tall on a laptop, project cards keep their captions, buttons lead to the right places, the form submits successfully, and the footer shows current contact details. If a visitor cannot understand the specialization and find a path to the inquiry form within 10 to 15 seconds, the homepage still needs work.

How to Review the Site After Setup

After importing and adapting Archibecht, the real question is not "Does the page look nice inside Elementor?" but "Does the site work for the visitor?" The visual editor can show one thing while the public page shows another, especially when caching, CSS/JS optimization, security plugins, or a nonstandard theme are involved.

Desktop, Tablet, and Mobile

Elementor lets you preview the page on different device types. Review every key template: the homepage, services page, project page, contact page, blog post, and 404 page. On desktop, look at hero width, headline readability, card balance, and spacing between sections. On tablet, three-card grids often start to break down. On mobile, the menu, hero height, buttons, forms, and block order matter most.

Do not fix the mobile version only by shrinking the font size. Sometimes the better solution is to rearrange column order, hide a decorative element, reduce the height of a background block, or shorten a long headline. Elementor’s responsive controls let you set different values for different devices, but every change still needs to be checked on the real public page.

Navigation and Internal Links

Make sure every button on the homepage leads to the right place. One of the most common post-import issues is leftover empty links, demo anchors, or buttons that still point to #. On an architecture site, the important paths are usually "Projects," "Services," "Contact," and "Discuss Your Project." If the site includes a video or presentation section, do not leave the play button in place without real content behind it.

SEO Basics and Performance

A template kit does not replace SEO work. Every page still needs a proper title, meta description, readable URL, one main H1 on the page itself, alt text on important images, compressed photos, and a logical heading structure. Archibecht helps shape the page, but it does not guarantee indexation or create a content strategy.

Performance depends heavily on the photography. Large construction photos create impact, but they can also slow down the site. Before publishing, compress your images, use the correct dimensions, review lazy loading, and do not enable unnecessary animations just for effect. If a cache or optimization plugin is installed, turn settings on gradually and check after each change to make sure Elementor styles have not disappeared.

Icons, Service Cards, and the Kit’s Decorative System

Archibecht’s look is not built on large photos alone. The reference screenshot also shows smaller but important details: benefit icons, trust cards, line markers, soft accent buttons, decorative labels, and project cards with clean captions. Those details seem secondary until they stop working. But if icons disappear after import or a card breaks, the page immediately starts to feel unfinished.

That is why the list of required plugins should not be treated as a just-in-case recommendation. ElementsKit, Gum Addon, Skyboot Custom Icons, and MetForm each cover a different layer. ElementsKit handles part of the Elementor extension set and the global header/footer workflows, Gum Addon provides widgets and decorative options, Skyboot expands the icon library, and MetForm powers the forms. If one of those layers is disabled, Archibecht may not collapse completely, but it can lose specific pieces of the composition.

Skyboot and the Icon Library

Skyboot Custom Icons for Elementor expands the icon set available in Elementor. For Archibecht, that matters because architecture websites often use icons for short value points: certified team, trust, quality, services, workflow stages, and contact methods. If icons appear blank after import, turn into squares, or the selection panel does not open, check not only the widget but also the library settings in Skyboot -> Settings.

Do not enable every icon pack blindly on the live site if you only need a small part of them. First make sure the imported template displays correctly, then disable clearly unnecessary packs on staging and review the result. Disabling too aggressively can remove icons from already assembled sections, while enabling every pack can add unnecessary load. A practical approach is to preserve the working state, record it in the project notes, and change things only after a visual check.

Gum Addon and Visual Widgets

Gum Addon for Elementor includes widgets such as slideshow, heading, pricing table, recent post, image box, post widgets, and site menu. According to the Archibecht product page, it is a required dependency. That does not mean every section in the kit is built entirely on Gum Addon, but disabling the plugin can affect specific decorative or content blocks. If a slide, custom heading, image box, or menu element disappears after import, check whether Gum Addon is active before rebuilding the section by hand.

When adapting the design, do not replace a widget just because it is unfamiliar. First open Elementor Navigator and see which widget type is being used. Then adjust the content, spacing, colors, and images with the built-in controls. Swapping in a different widget may visually solve one issue while creating another: the HTML structure, responsiveness, hover state, or container behavior may change.

Benefit and Trust Cards

In the reference screenshot, the benefits block appears as a wide warm-toned panel under the hero. It is not just decorative. It addresses the moment of doubt right after the hero area: why the company can be trusted, what it is responsible for, and how it demonstrates quality. In a Russian adaptation, do not leave vague labels like "Best Service" or "Creative Team" if there is no real fact behind them. It is better to use specific but careful wording such as "Design and Author Supervision," "Residential and Commercial Projects," or "Stage Documentation and Photo Reports" if those statements are true for the company.

The cards should be close in length. If one heading takes one line while another stretches across three, the grid starts to jump visually. In Elementor, that is fixed not only with CSS but also with editing. Shorten the headings, move the detail into the caption, and check the mobile view. A good value card communicates one fact, not the entire sales pitch.

When It Is Better to Remove a Decorative Block

A template kit includes more sections than a specific company may actually need. That is normal. If the client logo block is empty, the pricing section does not fit the business model, the video is not ready, or the newsletter is not supported, it is better to remove or hide those blocks for now. An empty section looks worse than no section at all. Archibecht works best with breathing room and a clear layout, so there is no need to fill every demo area with weak content.

Before publishing, walk through the page and ask what job each block does for the visitor. The hero explains the specialization. The benefits remove doubt. The about section presents the experience. Projects prove outcomes. Services show what can be ordered. Contact captures the inquiry. If a block does not fit any of those roles, it should be reworked or removed.

Projects, Services, and Content Replacement Without Breaking the Structure

The biggest mistake people make with architecture template kits is replacing only the logo and hero photo while leaving the demo content logic in place without any real substance. Archibecht looks like the site of a company that knows how to present its work, but that credibility still has to be filled with real content. The structure helps, but it does not write case studies or know which services your team actually provides.

How to Turn Projects into Proof of Experience

The projects page should not be a storage area for attractive images. It should be a catalog of proof. For each project, prepare at minimum a title, project type, short task summary, 1 to 2 outcomes, and visual material. If you expand the project into a detailed case study, add the initial situation, the constraint, the solution, the stages, and the final outcome. That can be done even within a regular Elementor page if the kit does not include a dedicated project post type.

For an architecture studio, it is useful to separate projects by type: private homes, public spaces, interiors, renovation, and commercial properties. If the kit does not include confirmed widgets for filtering, do not invent a complex filter from scratch. A simpler structure with sections or separate category pages can work just fine. The important thing is that the visitor can find a project similar to their own need and see that the team has already handled a comparable task.

The project images should be processed consistently. If one card is bright, another is too dark, a third is vertical, and a fourth uses a tiny drawing, the grid starts to feel random. Prepare the crop to match the intended aspect ratio, check the image center, and review the caption. For hero project slots, use the strongest shot; keep drawings, plans, and detail images inside the full case study.

Services and Service Detail as a Clarity Funnel

The services page should not read like a price list copy. Archibecht includes a general services template and a separate detail template. Use them as a funnel: the overview shows the categories, and the detailed page explains one actual service. For example, "Architectural Design" on the overview page may be a single card, while the detailed page can explain the work scope: site analysis, concept development, space planning, visualization, working materials, and approval support, if those are truly included in the service.

For each detailed service page, a useful chain is: who needs the service, what input data is required, what the team does, what the client receives, how to evaluate the quality of that outcome, and what limitations apply. That structure helps the reader make a decision and also reduces the number of mismatched inquiries. If the service depends on region, permitting procedures, or project type, phrase those points carefully and do not promise a universal outcome.

Pricing Plan: Use It or Remove It

Archibecht includes Pricing Plan, but construction and architecture services do not always fit neatly into fixed packages. If the company genuinely sells standard consultations, project audits, or entry-level design packages, a pricing page may be helpful. If cost always depends on square footage, complexity, documentation scope, and travel requirements, it is better to replace pricing with a block such as "How Pricing Is Determined."

That kind of block can explain the factors without giving exact numbers: project type, size, project stage, available source materials, level of detail, urgency, and whether author supervision is needed. That is more honest than artificial packages the manager then has to explain away. It is also useful for SEO and trust: the visitor understands why an exact price cannot be quoted before the task is reviewed.

Blog as a Knowledge Base, Not a News Dump

If you use Archive Blog and Single Post, turn the blog into a knowledge base. In the architecture niche, useful topics include "how to prepare for a design project," "what belongs in a technical brief," "how to choose facade materials," "common renovation mistakes," and "how to read a floor plan." Content like that supports the services and projects instead of living in isolation.

The blog does not have to be mandatory. If the company is not ready to publish regularly, it is better to hide the menu item and keep 2 to 3 strong expert pieces in a resources section. An empty blog with one "Hello world" post or an outdated news item hurts trust more than having no blog at all.

404 and Technical Pages

Error 404 is often ignored, but for a site with projects and a blog, it is useful insurance. Set the page up so the user can return to the homepage, projects, or contacts. Do not leave the demo text in place. For an architecture site, a calm message works well: the page was not found, but you can browse projects or send an inquiry.

Also remember the standard technical pages: privacy policy, consent to data processing, company information, and anything else your site requires. Archibecht does not create the legal foundation, but it gives you a clean place to link those pages from the footer.

Safe Customization Without Editing Product Files

For small visual tweaks, there is no need to edit Elementor files, the theme, or plugins. The safest route is to use Elementor settings, global styles, Additional CSS in the Customizer, or a child theme. With Archibecht, that is especially useful when you want to make project cards more consistent or make portfolio captions more stable with longer Russian titles.

Custom CSS Adjustment for Project Cards

The following example does not rely on hidden Archibecht classes. It is safe because you assign the CSS class yourself to the needed container in Elementor: open the project card, go to Advanced, and add the class archibecht-project-card. Then place the CSS in Appearance -> Customize -> Additional CSS or in the child theme stylesheet.

.archibecht-project-card {
  min-height: 100%;
}

.archibecht-project-card img {
  aspect-ratio: 4 / 3;
  object-fit: cover;
}

.archibecht-project-card .elementor-heading-title {
  overflow-wrap: anywhere;
}

What this adjustment does: it keeps the card height stable, crops project photos cleanly to a consistent ratio, and prevents long titles from spilling out of the block. This is a custom adaptation based on standard CSS practice and a publicly assigned class, not an edit to the product code. The test is straightforward: open the projects page, replace 2 to 3 titles with longer Russian examples, and review desktop and mobile. Rollback is just as simple: remove the class from the containers or delete the CSS where you added it.

Do not edit the core files of the theme, Elementor, ElementsKit, MetForm, or the kit package itself. Those changes are hard to maintain, may disappear after updates, and often create more problems than they solve.

When the Import Succeeds but the Page Still Looks Wrong

Most Archibecht issues happen at the boundary between WordPress, Elementor, Template Kit Import, the required addons, and caching. This is not a generic "everything is broken" panic list, but a practical diagnostic guide: symptom, cause, how to check it, how to fix it, and when it is better to roll back a change.

WordPress Shows a style.css Error

Symptom: when uploading the archive, WordPress says the theme has no stylesheet. Possible cause: the kit is being uploaded as a theme through Appearance -> Themes. Archibecht is an Elementor Template Kit, so it needs to be imported through the template kit tool, not through the theme installer.

Check which file was downloaded and which installer you are using. Fix: activate Hello Elementor as the regular theme, install Elementor and Template Kit Import, then upload the kit ZIP through Tools -> Template Kit. If you already tried to install the archive as a theme, simply remove the failed entry from the theme installer and start over with the correct workflow. In most cases, there is no need to roll back the database unless theme files were moved manually.

Templates Imported, but the Page Is Empty or Unstyled

Symptom: Elementor opens, but the imported templates look empty, broken, or very different from the demo. Possible causes: Global Kit Styles were not imported, Flexbox Container is disabled, required plugins are missing, the active theme is overriding styles, or the cache is serving old CSS files.

Check the Flexbox status in Elementor settings, review the list of active plugins, import Global Kit Styles first, clear the browser cache, optimization plugin cache, server cache, and Elementor -> Tools -> Clear Files & Data. If the issue disappears on Hello Elementor, the current theme is conflicting with the styles or layout.

The Header or Footer Does Not Appear on Pages

Symptom: the pages exist, but the global navigation is missing or the header from another theme is showing instead. Possible cause: the header/footer template was imported but not activated through ElementsKit, or the selected page layout hides the global header.

Check ElementsKit -> Header Footer: is there a created header, is activation enabled, is it set to display site-wide, and has the imported template been inserted? Then open the page and review Page Layout. If it uses Elementor Canvas, the header and footer may be hidden by design. Fix: switch the page to Elementor Full Width or create separate logic for a landing page.

Icons and Certain Widgets Look Different

Symptom: service cards have no icons, decorative elements are missing, or some widgets do not render. Possible causes: Skyboot Custom Icons or Gum Addon are inactive, icon libraries are disabled in Skyboot settings, or a specific widget depends on an addon that did not install through the requirements banner.

Check the plugins list, then review the Skyboot settings. The Archibecht product page specifically says to enable the libraries in Skyboot -> Settings. If Elementor becomes unstable after enabling the libraries, disable the packs one at a time and test the conflict on staging rather than on the live site.

The MetForm Form Was Not Inserted or Does Not Send Email

Symptom: the contact page shows an empty block, the form displays without design styling, or the inquiry never arrives. Possible cause: the page template was imported, but the form template was not imported and selected inside the MetForm widget. Another possible cause is email configuration, hosting restrictions, or missing SMTP.

Check the workflow through Navigator and Edit Form, insert the template from My Templates, update the form and the page, then submit a test inquiry. If the form submits but the email never arrives, check the logs, recipient address, spam folder, and WordPress mail delivery. For production sites, it is better to configure SMTP through a reliable dedicated method, but that should be handled separately from the template kit import itself.

Changes in Elementor Are Not Visible on the Public Page

Symptom: everything looks updated in the editor, but visitors still see the old color, old image, or broken layout. Possible causes: browser cache, plugin cache, server cache, CDN, CSS/JS minification, or outdated generated Elementor CSS files.

Check by opening the page in incognito mode, temporarily disabling optimization, clearing caches, and then running Elementor -> Tools -> Clear Files & Data. If everything works once optimization is disabled, re-enable the rules one by one. There is no need to roll back the design until caching and optimization have been ruled out.

Demo Images Cannot Be Left As-Is

Symptom: the site looks visually ready, but it still contains someone else’s construction photography. Cause: the template kit uses demo images as part of the presentation, and the product page warns that they require licensing or replacement. Fix: replace the images with your own materials or properly licensed assets. If you cannot replace the full visual set quickly, it is better to delay publishing than to launch the site with unverified imagery.

When ThemeForest Archibecht Is the Right Choice

ThemeForest Archibecht is a strong option if you need a clear Elementor starting point for an architecture or construction website: the homepage, services, projects, contacts, blog templates, header/footer, and forms are already assembled in one consistent visual style. It is especially useful when the team is ready to replace the demo content with real photography and handle the import carefully, rather than expecting the kit to behave like a full theme or business platform.

Before publishing, check three things: the correct import method, working dependencies, and the real public-facing result. If Global Kit Styles were applied, the header and footer are output through ElementsKit, MetForm sends the inquiry, Skyboot icons work, and the mobile version does not break the hero or menu, the kit can be considered technically ready for content population.

If you are ready to test the kit on your WordPress site after that, move on to the download section and download ThemeForest Archibecht. Run the first setup on a staging copy, keep a restore point before import, and publish the site only after replacing the images, testing the form, and reviewing every key page as a normal visitor.