ThemeForest Lunost - WordPress Theme

How to Set Up ThemeForest Lunost in Elementor

This guide to ThemeForest Lunost will help you prepare a clean WordPress environment, safely import the template kit, configure global styles and content, build a homepage for an automotive project, and check the finished site on real devices. The focus here is not on purchasing an archive or repeating promotional copy, but on the practical path from an empty site to a clear, useful page for an electric vehicle brand, dealership, or clean mobility service.

ThemeForest Lunost is an Elementor Template Kit, not a standalone WordPress theme. That distinction shapes the entire setup process: the kit provides prepared pages and design elements, while WordPress still manages permalinks, homepage assignment, and navigation, and the active theme provides the technical foundation for the public-facing site. According to the product listing, the kit is designed for electric vehicles, sustainable mobility, and automotive projects; it includes a container-based layout, global styling, responsive design, and pages that can be edited in Elementor without coding.

This type of product is especially useful when you do not need to invent a design system from scratch. The original layout already has a recognizable rhythm: a dark forest hero with a road and an electric vehicle, a calm light background for the sections that follow, large high-contrast headings, fine divider lines, cards presenting sustainability-focused ideas, and photographic automotive scenes. Your task is to preserve that rhythm where it supports your brand message, while replacing the demo copy, images, numbers, and visitor paths with your own. If you change everything at once and then try to restore consistency later, the site can quickly start to feel like a collection of unrelated sections.

What the Kit Provides and Where Its Responsibility Ends

It is most useful to think of Lunost as a prepared system of pages and design rules. It includes more than individual blocks: it establishes relationships between the hero section, brand story, principle cards, automotive imagery, calls to action, and secondary pages. The ThemeForest listing for this kit describes ready-made pages, customizable colors, global styling, and support for the free version of Elementor. This means you can edit copy, images, spacing, and blocks in the editor, but you should not expect the import itself to configure your domain, email, vehicle catalog, dealership database integration, or legal documents.

Understanding that boundary prevents disappointment on the first day. The template is responsible for content presentation and layout structure. WordPress stores pages, menus, and reading settings. Elementor assembles containers, widgets, styles, and responsive values. The active theme supplies the basic site shell, public-facing output, and sometimes typography. External plugins handle forms, catalogs, test-drive bookings, caching, or analytics only when you choose and connect them yourself. Do not assign capabilities to Lunost that are not confirmed as part of the kit.

How to Read the Demo Layout Before Editing

Open the demo and the supplied top screenshot not as a gallery of attractive blocks, but as a map of the visitor journey. The hero creates an emotional promise: an electric vehicle moves along a forest road, while a short headline and button suggest the next step. It is followed by an explanation of the brand position, a photographic anchor, three principle cards, and a large vehicle presentation. There is a clear progression here: first, visitors understand the topic and mood; then they receive reasons to trust the brand; after that, they see the product; and only then are they ready to request information, choose a model, or get in touch.

Before editing, write down four things for each visible block: which visitor question it answers, which of your own materials will replace it, what action should come next, and whether the block can be removed without losing meaning. For example, a statement about "zero-emission performance" does not need to remain on the site if your project sells charging stations rather than vehicles. Its role, however - communicating value - should be replaced with a relevant, verifiable message of your own. A photo of a gas station in a smaller block can be replaced with charging infrastructure, a test drive, or a service area if that better fits your organization. Principle cards are worth keeping only when you have real facts for them to illustrate.

Which Projects Are a Good Fit for Lunost

The kit works well for an electric vehicle brand, a local dealership, a model range presentation, a company that designs charging infrastructure, an electric mobility studio, or the corporate site of an automotive service business with a sustainability focus. Its strength is not universal flexibility, but its ready-made combination of automotive imagery, a calm technology-and-sustainability palette, and an editorial composition. If visitors need to see the transportation offering quickly, understand the positioning, and move on to the next action, this visual language feels natural.

For an ecommerce site with a full cart, filters, payments, and customer accounts, the kit alone is not enough: you will need a catalog, ordering rules, and the ecommerce functionality you choose. For a site with dozens of unrelated services, Lunost may be too specialized. Forest and road imagery, a prominent vehicle hero, and an emphasis on sustainable mobility may no longer support the actual content. In that case, it is better to choose a kit with a more neutral structure than to disguise the mismatch through endless edits.

How a Template Kit Differs from a Traditional Theme

A standard WordPress theme is usually activated under Appearance and affects the overall site shell as a software package. An Elementor kit is imported as a collection of layouts and settings, after which individual pages are opened through Edit with Elementor. For that reason, after importing Lunost, do not expect to find one control panel with dozens of options, as you might with some classic themes. The main changes live in three places: the content of a specific page, Elementor's global settings, and standard WordPress settings.

This also explains why copying a page to another site can look incomplete. An individually imported layout does not always bring along its global colors, fonts, images, header and footer template, or required set of supporting components. Importing the complete kit and moving a single template are different operations. If you want to recreate Lunost's recognizable look on a clean test site, first import the connected components, then assign the homepage and menu, and only then evaluate the public-facing result.

A quick rule of thumb: do not treat the demo copy as finished content. Use it as a hierarchy map: hero - arguments - proof - action. That preserves the strength of the composition even after every word and image has been replaced.

What Makes the Lunost Homepage Feel Cohesive

The kit's homepage feels unified not because of one image or one color. It is built from several layers, each of which needs to work with the others. At the top level is the page structure: header, hero, introductory section, principle cards, large automotive image, explanatory metrics, and additional topic-driven sections. The middle level contains recurring elements: a rounded button, narrow dividers, large sans-serif typography, light cards with subtle borders, and concise labels. At the lower level are global colors, fonts, spacing values, images, and written content.

When you change one of the lower layers, the visible outcome spreads further through the page. Replacing the global dark color affects the hero, buttons, and high-contrast blocks. Changing the base font changes line length, heading height, and wrapping. A new photograph changes the balance of open space around the copy. The most reliable order of work is therefore this: first preserve a copy and identify what will be imported, then configure global rules, then replace the content in each section, and only at the end fine-tune individual spacing values.

The supplied example clearly shows how the rhythm works. The dark top section does not continue indefinitely: after the strong hero, the page pauses on a light background where the text and vehicle detail can be read more calmly. Then three cards organize the principles into a clean row, while a large SUV image brings visual weight back into the page. If you reduce this rhythm to a series of identical blocks or place several dramatic background images one after another, the sense of controlled progression disappears.

Preparing WordPress: a Test Copy, Theme, and Content Assets

Importing a kit can affect more than a single page. Depending on the installation method, it may add templates, pages, images, and global styles. For Lunost, it is especially sensible to begin with a staging copy of the site or a new project without someone else's headers, footers, and old design settings. Elementor's official guidance also recommends using kits on a clean installation to avoid conflicts between existing data and imported components. This is not a requirement for every experiment, but it makes the consequences easier to understand and reverse.

If you do not have a test environment, create a backup through your hosting provider or your usual backup process before the first operation. Confirm that the backup actually contains both files and the database, rather than simply appearing in a task list. A vague promise to "restore it later" is not a rollback plan. After creating the backup, record the starting state: which theme is active, which page is assigned as the homepage, which menus exist, whether the site uses Elementor, and whether other kits are already installed. These notes will save time if the new design conflicts with the current structure.

A Minimal Environment Without Unnecessary Assumptions

You need a working WordPress installation, Elementor installed, and an active Elementor-compatible theme. The Lunost listing states that the kit is intended for the free version of Elementor and is compatible with Hello Elementor or another Elementor-compatible theme. That does not mean it will automatically work with every plugin on the site. If the current theme forces its own typography, containers, header, or button styles, it may alter the outcome, especially in sections with dark backgrounds and light text.

Check three layers before importing:

• The platform: WordPress should open the admin area without errors, and Elementor should be activated and available for the required page types.
• The site shell: The active theme should not display an old header over the template or force unsuitable fonts and colors.
• The content: Prepare your own copy, vehicle images, logo, contact details, data-processing policy, and real destinations for buttons.

The last point is often underestimated. You cannot replace a demo effectively if all you have is the company name. For the hero section, choose the main message in advance: for example, a specific mobility focus, model range, infrastructure solution, or service. Prepare a short headline, one supporting line, and one action for it. For principle blocks, gather verified facts: service area, vehicle type, in-house standards, and available services. Do not insert sustainability percentages, charging times, or technical claims without real data - an attractive layout does not make an unverified number true.

Why Images Should Be Prepared Before Editing

In Lunost, the image carries much of the first major design decision: a road cuts through the forest, a vehicle becomes a small but clear point of motion, and the copy receives a calm dark area for readability. A random white-background image or a tight crop of a car body cannot fill the same role without rebuilding the composition. Choose materials by their function within the block, not only by appearance: use a wide environmental vehicle shot for the hero, a calmer horizontal image for the brand story, and a close product image for a model range or service section.

Make sure you have the right to use the images on a public site and that the files are large enough for wide sections. Save the original names and intended meaning of the photographs in advance: this makes alt text easier to write and prevents you from confusing a charging-station interior with a vehicle model. If you do not yet have an image library of your own, first build the temporary structure with neutral replacements, but return to real visual evidence of the brand before launch.

Choosing an Active Theme Without Fighting Its Styles

A predictable foundation is especially important for a kit. A lightweight theme designed to work with Elementor usually gives the editor enough control over container widths and page presentation. If you need to keep the site's current theme, first create one Lunost draft page and check four things: hero width, heading appearance, button styling, and header behavior. Do not replace this test with the editor view alone. Open the published or previewed page in a separate window, because theme styles may appear specifically on the public-facing site.

When the current theme colors elements in its own way, you have several measured options. First, review the theme settings that control colors, typography, and content width. Then open Settings in Elementor and assess whether enabled default values conflict with the kit's global rules. Elementor documentation describes settings for disabling default colors and fonts, but apply them only after you understand which system is producing the unwanted style. Do not toggle options at random on a live multi-page site: doing so may alter content unrelated to Lunost.

Checking Compatibility Without Risky Edits

Create a small decision table before importing. It does not replace testing, but it helps keep responsibilities from different systems separate.

After this preparation, you do not have to import immediately. This is a good time to decide whether you need the entire kit or only selected parts. If the project already has a stable homepage and you only need to add one marketing landing page, it is safer to begin with a separate page and leave global settings untouched. If your goal is to build a coherent electric mobility site from scratch, importing the complete kit in a staging environment makes more sense: the header, page rhythm, and shared styles can then be evaluated as one system.

Who Should Avoid a Full Import

Not every site benefits from applying a ready-made kit in full. Avoid a full import if the live site already contains critical header and footer templates, a complex page structure, specific multilingual rules, or a configured store, and you do not have a staging copy. In that situation, use Lunost as a source of individual ideas or move only selected pages after testing. This does not make the kit worse - it simply means the risk of changing the existing system outweighs the benefit of a quick start.

You should also avoid using it as a replacement for technical planning. It does not define catalog structure, editor roles, legal-copy approval, lead delivery, or manager workflows. Before you choose it, define what visitors should do after the hero: submit an inquiry, choose a vehicle, find a dealer, explore infrastructure, or open contact details. If you cannot name that action, design the visitor journey first, then adapt Lunost's attractive sequence of blocks to support it.

Required step before importing: test the kit on a copy of the site and prepare your own content. Then any unexpected change remains a learning experience rather than an incident on a public page.

Importing the Kit Without Losing Control of Your Site

Installing Lunost does not begin by opening the first page in Elementor. It begins by choosing an import method. In practice, there are two common paths: importing through the interface and extension recommended by the kit provider, or importing a website kit package through Elementor tools if the archive format and your workflow support it. Specific screen names may differ from the author's instructions, so do not copy a random path from someone else's video. Use the documentation included with the archive and focus on the purpose of the operation: the import should add only the templates, content, and shared settings you actually need.

Elementor's official documentation separates kit import into several parts: templates, content, and site settings. This is a useful model even when a third-party installer displays different buttons. Templates usually include site parts and saved layouts. Content adds pages, posts, or content types when included. Site settings carry global fonts, colors, design theme, layout, background, and related rules. Do not automatically select every option: site settings are the part most likely to change an existing design system.

Full Import Sequence on a Clean Test Site

On a clean project copy, it is convenient to complete a full import and evaluate Lunost as a complete system. First install and activate Elementor. Then open the import method provided by the kit supplier or your working tool. If the interface asks you to upload a ZIP archive, upload the original archive itself without extracting it or replacing files inside it. An error involving an extracted folder or incorrect format often looks like "file not accepted," even though the issue is not the layout itself.

1. Open the test admin area and confirm that Elementor is activated.
2. Go to the theme-kit import area using the method specified in the archive documentation or the importer you are using.
3. Select the Lunost ZIP archive and wait for the tool to validate its contents.
4. Review the dependency list and install only explicitly listed components when the kit genuinely requires them.
5. On a clean site, choose to import related templates, content, and shared settings if your goal is to view the original package as a whole.
6. Do not close the screen until the importer reports completion, then open the page and template lists.

After completion, do not immediately start changing every button. First inspect the import: did the expected pages appear, is the main layout present, are the images in place, and does the styling appear in preview? Open one internal page and confirm that it can be edited through Edit with Elementor. Then locate the header and footer template if they are included. This inventory makes it possible to distinguish a successful import from a situation where only part of the kit reached the library.

What to Do When SVG Permission Is Requested

During import, some tools may request permission to upload SVG files. Elementor warns about this in its general kit-import workflow. An SVG is not an ordinary photograph; it can contain active content, so permission should not be enabled automatically just to complete a step. Continue only when you trust the archive source, understand why the files are needed, and are importing in a controlled environment. If you are uncertain, inspect the package contents first and use a safe site copy.

Do not try to solve the issue by blocking every image or replacing files inside the kit before the initial import. It is more important to understand which elements fail to import and whether your project actually needs them. In some cases, you can replace a decorative icon with your own safe image after the structure has been created successfully. This keeps the workflow reversible and avoids editing the product's internal files.

Partial Import for an Existing Site

On a live site, a full installation may be excessive. If you only need a landing page for a new electric vehicle range, import the page or its connected layouts first without moving global settings unnecessarily. Then create a draft, open it in Elementor, replace the demo blocks, and compare it with the existing header. This route requires slightly more manual work, but older pages will not suddenly receive new colors and fonts.

Be particularly careful with header and footer templates. They may have display conditions, such as applying to the whole site, a specific page type, or one selected page. Do not confirm these conditions until you have reviewed the result on a draft. If the Lunost header should exist only for a particular landing page, limit its display scope using the tools supported by your kit and installed version of Elementor. If those conditions are unavailable or require a feature you do not have, keep the existing WordPress header and adapt the first page section so that the transition feels deliberate.

A partial import is also useful for learning. It lets you understand what belongs to a specific page and what is part of the shared system. A page usually contains containers, widgets, cards, images, and local styles. Global settings contain base colors and fonts. WordPress manages menus and homepage assignment. Once you have separated those responsibilities, issues become easier to fix: you do not need to search every page for a button color if it is global, and you do not need to change a global font when only one heading is styled incorrectly.

Initial Check Immediately After Importing

Run a short check immediately after import, before replacing content. It should take only a few minutes, but it catches most early problems. Open the page in a separate tab and verify that the hero is not empty, images have not become gray placeholders, text is not overlapping buttons, and the page has the expected width. Then open it in the editor: you should see normal Elementor elements in the sidebar, rather than one large inaccessible image. This confirms that you received an editable layout, not merely a static preview.

At the same stage, check that the new pages do not accidentally use the same addresses as older content. Give draft pages clear temporary names and do not publish them until navigation is configured. If a hero button leads nowhere, that is normal for demo content, but it should be added to your work list. Do not leave such buttons as decorative objects: on the final site, they should lead to a form, model, contact page, or another selected action.

Import Checkpoint

A successful first stage is not measured by the number of files added. It is complete when you understand which pages and templates you received, can open them in Elementor, can see the original design on the public-facing site, and can explain whether global settings will apply to the entire project or only the new section. Only then does it make sense to assign a homepage, build navigation, and edit content.

If the Importer Suggests Additional Extensions

Do not install everything simply because a button appears mandatory. Compare the list with Lunost's description and accompanying documentation. Some kits use additional widgets or a demo import mechanism, while others work with Elementor's core capabilities. For every suggested component, ask two questions: which specific section or action will stop working without it, and does your site need that outcome? If you do not have an answer, keep the test installation separate and do not add the extension to the live project.

The same principle applies to updates. Do not update WordPress, Elementor, the active theme, and the kit all at once immediately before importing if you cannot test the changes separately. First create a backup, then update through the project's normal process, and then open the test page. If a problem appears, you will have a clear comparison point. A mixed bulk operation makes it impossible to know what changed the display.

Result check: after importing, you should see not only a list of new templates, but also one real editable page where the hero, images, button, and base grid preserve the original hierarchy.

Global Styles: Preserving Lunost's Design Language After Replacing Content

The most common reason an imported page quickly loses its character is making isolated edits without a shared system. One editor changes headings one by one, another person applies different button shades, and a third chooses a font for every section. The pages may still function technically, but the hero, cards, and large photograph no longer feel like parts of the same story. With Lunost, this relationship is especially clear: a dark natural scene at the top, light informational surfaces, nearly black text, a muted red-terracotta accent, and fine neutral borders create a disciplined rather than flashy image for a technology-focused automotive brand.

In Elementor, the Site Settings panel controls system-level rules from within the editor. Elementor documentation describes a design system with global colors and fonts, along with shared styles and settings. The location of menu items may shift slightly between releases, but the principle remains the same: define repeated values first, then connect specific widgets to those values. This is the approach to use when adapting Lunost, rather than creating dozens of local shades and sizes.

Define the Palette First, Not the Shade of Every Section

Open the original page and identify color roles rather than trying to copy every pixel exactly. The layout can be described through a dark base tone for the hero and text, a light neutral background for the main sections, a warm accent color for the main button or small numerical accents, muted gray for secondary copy, and a fine border color for cards. Those five roles are enough to begin. They can receive your own brand values, but their functions should remain stable: the accent still marks one action, secondary labels do not compete with the heading, and a light block creates breathing room after a dark photograph.

In Site Settings, create or review global colors. Name them by purpose rather than by an arbitrary shade: Primary Dark, Surface Light, Action Accent, Muted Text, Line. The names in the panel can remain in English because they are internal interface labels, but it is helpful to describe them in a project note for your team. Then review the hero, buttons, cards, and text widgets. When an element should inherit the system, choose the global value using the relevant color-setting icon instead of entering a similar manual shade.

A global palette does not make every part of the site look identical. It creates predictability. For example, a principle card on a light background may use a dark heading, fine border, and understated label, while the main call to action in a dark section uses light text and an accent button. The roles differ, but they belong to one system. After this is in place, changing the brand accent color no longer means searching through every page.

How to Keep Hero Contrast Intact

Lunost's hero is built around a photograph with different brightness zones: dense forest on the left, a road and light shoulder on the right, and a small-scale vehicle. If you place text over a randomly selected replacement image, it may disappear even with the correct font color. Check more than the color setting; examine the actual area around the heading. You may need to adjust the crop, choose another photo, add a dark overlay provided by the container, or move the text into a calmer part of the image. Do not turn this into a battle of dozens of effects: the main goal is for the heading and button to be readable without effort.

Compare the result on a standard monitor and a smaller device. If the headline falls across a light road surface, a decorative shadow will not always restore readability. It is better to adjust the text-container width, spacing, or background-image position. After every change, open a preview instead of relying on the editor view. A readable hero matters more than an exact match to the demo.

Typography as a Hierarchy Tool

The supplied example uses large neutral sans-serif typography without decorative attempts to imitate automotive advertising. The hero heading is brief, oversized, and broken into two lines; section subheadings use a different density; small labels and explanations create rhythm without competing with the main message. Preserve that hierarchy when replacing the font. If the brand uses a custom typeface, first check that it supports Cyrillic and the required weights, then assign it through global fonts. Otherwise, Russian sections of the site may fall back to another font and break line lengths.

Elementor lets you work with global fonts and apply them to widgets through the styling panel. Instead of setting a size in every card, define at least four roles: large hero text, section heading, body copy, and compact supporting label. For each role, choose the family, weight, size, and line height, then test them with real text. A demo line in English is often shorter than a Russian explanation. If you simply replace the words, a strong heading may expand to three or four lines and overpower the photograph.

Do not solve Russian line wrapping by shrinking every piece of text. First rewrite the heading more concisely, then check the container width, and only afterward carefully adjust the size. Text explaining a sustainability promise or test-drive service should remain readable. On mobile, the scale can be adjusted through responsive settings, but do not turn the first message into tiny supporting copy.

How Sections, Global Rules, and the Final Page Work Together

This is where the useful mechanics of Elementor kits become visible. The editor does not change one complete "site image"; it changes individual containers and widgets. Those elements can inherit global color and font settings. The page template determines the order of containers and the display conditions for a header or footer. WordPress assigns the homepage and connects it to navigation. The visible outcome appears only when these levels are aligned: the page has the correct layout, global rules suit the brand, the right page is selected in reading settings, and navigation leads to existing destinations.

If your button changes color on every page, you probably edited a global role. If only one hero loses its background, the issue is in that container or image. If the new homepage opens by direct link but does not appear at the site root, check the static homepage assignment in WordPress. Separating the levels this way is the best diagnostic method: do not repair a global style for the sake of one object, and do not copy a local color into ten elements when the cause is system-wide.

Configuring Buttons and Cards Without Visual Noise

In Lunost, buttons and cards should not become a separate collection of effects. One prominent button in the dark hero leads visitors to an important action. The light cards below organize short facts. Preserve that distinction. For the main button, use one accent background, contrasting text, adequate internal spacing, and a clear action label. For a secondary button, use a quieter solution: an outline, neutral surface, or link - but only when it is genuinely secondary.

Principle cards work well for three specific points, not long marketing paragraphs. Keep a short title, one explanation, and, if needed, a small visual marker in each. If you need to say more, move the detail into the next section or a separate page. A card overloaded with long copy no longer supports the page rhythm and begins to feel like a compressed article.

A Safe Order for Changing Shared Styles

1. Save the original values on the staging copy or capture screenshots of key pages.
2. Change one global color role and open the hero, a card, and a button on the public-facing site.
3. Configure global font roles using real Russian copy.
4. Fix only the widgets that do not inherit the intended rule.
5. Repeat the check on wide and narrow screens before moving to the next group of changes.

This order is slower than repainting everything at once, but it shows where each visible outcome came from. If a change does not work, restore one global role or local setting rather than deleting the page or starting the import again. Once the shared system is configured, you can move on to the most important work: replacing the demo content with a real visitor journey.

Checkpoint: Lunost keeps its character when you edit roles rather than individual pixels: a dark hero atmosphere, a light pause for meaning, one clear action accent, a strong heading hierarchy, and restrained cards.

How to Turn an Electric Vehicle Demo into Your Own Customer Journey

After importing and configuring shared rules, the most meaningful part of the work begins. Lunost already has a convincing visitor journey, but it belongs to the demo brand. If you replace only the logo, visitors will encounter someone else's promises, placeholder numbers, and nonfunctional buttons. If you delete everything until the page is blank, you lose the strong progression that made you choose the kit. The right approach is to preserve the purpose of each block while replacing it with your company's real materials.

Start with one primary purpose for the homepage. For a dealership, it may be "learn about models and book a test drive." For a charging-station operator, it may be "understand our service area, solution type, and submit an inquiry." For an automotive service business, it may be "see our specialty and contact us." One page does not need to sell vehicles, explain industrial infrastructure, collect job applications, and publish news at the same time. Choose the main route, then move other areas into navigation or separate pages.

Breaking Down the Hero: From an Attractive Phrase to a Specific Action

In the original composition, the top section consists of a header, concise menu, large message, small button, and automotive photograph. Fill in these parts in that order when adapting it. First update the headline. It should name a clear benefit or focus, rather than repeat the company name. Then write one short supporting line that clarifies the promise. After that, define the button: its label should match a real next page or form. Only then select the image and check whether the text remains visible against it.

Below is a practical meaning framework, not copy to duplicate:

• Headline: States one main focus, such as choosing an electric vehicle, charging infrastructure, or service.
• Supporting copy: Adds one verifiable detail - region, audience type, service range, or operating principle.
• Button: Leads to a form, model list, solution map, or contact destination that already exists.
• Photograph: Shows real equipment and an environment connected to the promise, rather than a generic transportation image.

In Elementor, open the first container through Edit with Elementor and move through its elements using the Navigator or directly on the canvas. Do not remove the background before you have chosen a replacement. First replace text widgets, then the button link, then the image or container background. Update the page and open the preview. This sequence makes it immediately clear whether the hero needs a new height and where the photograph's focal point falls.

Do Not Repeat the Same Call to Action on Every Button

The hero should contain one primary task. A model section can logically link to a model description. A service section can link to booking or contact details. A principles section can link to more detailed information. If every button says "Learn More" and opens the same homepage, the visitor journey disappears. Use more specific action labels instead: "Choose a Model," "View Stations," "Request a Consultation," or "Find a Service Center." The text should be brief, but visitors must understand what will happen when they click.

Replacing Brand Blocks Without Inventing Claims

After the hero, Lunost includes a calm light section where large copy and two supporting columns establish the brand position. This is a good place to answer "why should visitors trust us," but not for broad, empty slogans. Use it for the founding story, technology focus, service area, vehicle-selection criteria, real service capabilities, or your approach to charging infrastructure. The proof should be specific: not "we are changing the world," but what the organization genuinely does and can support on the next page.

In the short columns, you can split the content into two roles. The first explains the customer's problem: choosing equipment, lacking clear infrastructure, maintaining a vehicle, or navigating a model range. The second describes your practical response: consultation, selection, maintenance, design, or ongoing support. Do not repeat the headline word for word. If the copy becomes too long, shorten it and link to a detailed site section rather than reducing the font to an unreadable size.

Three Principle Cards as Evidence, Not Decoration

In the layout, three adjacent cards create an orderly pause before the large vehicle image. Keep the number of cards only if your project truly has three distinct reasons to choose it. Good examples include a clear support service, transparent vehicle-condition checks, and an infrastructure plan. Three variations of the same marketing promise do not work. Each card should answer a different visitor question and end with a clear takeaway.

When editing, first replace the headings with factual categories. Then rewrite each paragraph as two or three short sentences. Check that the card lengths are comparable: one overloaded card next to two nearly empty ones disrupts the vertical rhythm. If you only have two real points, do not invent a third. You can rebuild the section as two wider cards or assign the third to a helpful path, such as service contacts. Test any grid change on a wide screen first and then on a narrow one.

Automotive Photography and Metrics Blocks

The large vehicle image in Lunost gives the page physical proof of its subject. It is especially important after more abstract discussion of principles. Choose the photo by meaning: if the site represents compact urban vehicles, do not use a random large SUV; if the service concerns charging, show a station and real context. Do not stretch a small image across the page width. On a wide section, every flaw and distracting background detail becomes visible.

Short metrics may appear beside or after the photograph. Treat them strictly: these elements look like facts, not atmosphere. Keep a number only when it is supported by a source within your organization or a document you can keep current. If a metric is debatable, replace it with a truthful qualitative description of the process. For example, instead of an unsupported percentage, you can show "Solution Planning" or "Maintenance Plan" with an explanation later on the page. Visitors notice an incorrect number more quickly than the absence of a decorative counter.

Menus and the Homepage: Where Elementor's Role Ends

The template header may be built in Elementor, but the menu itself relies on WordPress capabilities. Elementor documentation specifically notes that menus are created in the WordPress admin area and then selected for display in the appropriate widget. First create or edit the list of menu items under Appearance and Menus, if that screen is available in your configuration. Then return to the header template and connect the navigation element to the needed menu. Do not try to change page names only inside the widget if the real issue is the WordPress menu structure.

Check every route in a published preview. A "Models" item should lead to an existing page, not a demo destination. An "About Us" item should not unexpectedly open a draft. If pages are not ready yet, temporarily leave them out of the primary menu or prepare a tidy intermediate page. The key is not to create the appearance of working navigation when visitors will reach a dead end.

When the homepage is ready, assign it in WordPress reading settings as a static page if it should open at the root address. The route to this setting depends on your administrative configuration, but the result is always checked in the same way: open the site address in a new window without an additional path and confirm that the correct page appears rather than the posts list or former homepage. If you use caching, clear only the available and understood cache according to the project process, then verify the result again in a separate browser session.

Checklist for One Completed Section

Repeat this short cycle for each section rather than trying to write the entire site in one pass:

1. Define the visitor question and the expected action after the section.
2. Replace the demo heading, copy, image, and links with real materials.
3. Check global color and font settings without creating a new local style for no reason.
4. Open a preview and assess the block between its neighboring sections.
5. Check the narrow-screen view, then return to the next block's content.

This produces a more reliable outcome than replacing all text during one long session. You can see how each new photograph affects spacing, how buttons continue the visitor journey, and where demo meaning has not yet been replaced. Once key blocks have their own content, you can move on to a complete practical homepage-building example.

The main adaptation rule: preserve the role of a section, but do not preserve someone else's claim. The template provides composition, while visitor trust comes from your verifiable content, working actions, and honest path forward.

Practical Example: a Homepage for a Local Electric Mobility Center

To keep the setup from becoming a set of disconnected tips, let's build a concrete working example. Imagine that you operate a local electric mobility center: it helps visitors choose vehicles, serves owners, and explains where charging solutions are available. The goal of the homepage is not to replace the full catalog, but to show the business focus within a minute, guide visitors to the right section, and provide a clear way to contact the team. Lunost suits this example because its original sequence already leads visitors from a strong automotive image to supporting arguments and an action.

Prepare the following before editing: an approved logo, four or five high-quality photographs of your own vehicles or service operation, one hero image, a short center description, three verifiable operating principles, the addresses of required pages, and a contact form or contact details. If you have fewer photographs for now, do not imitate a large image gallery. It is better to keep one strong cover image and reduce secondary placements than to repeat the same vehicle from different angles in every section.

Step 1. Build the Page Structure Before Working on the Menu

Create WordPress drafts for the areas visitors genuinely need to reach. In this example, five are enough: home, models or vehicle selection, service, charging solutions, and contact. If the company story is useful, add a separate "About the Center" page, but do not force the hero to explain every detail. Keep the names short and clear because they will become navigation labels and browser titles.

Then decide which material belongs on the homepage and which should remain on an internal page. The homepage should contain the promise, a brief explanation, three reasons to trust the business, one visual example of a vehicle or service, and guiding actions. The models page can contain a detailed catalog. The charging-solutions page can include a coverage map, service types, and an inquiry process. The contact page can contain contact methods, business hours, and a form. This separation is not a Lunost feature, but it helps you use the design as intended: the homepage rhythm does not become bloated into a reference manual.

Step 2. Rewrite the Hero

Open the imported homepage through Edit with Elementor. Locate the first container with the background image and text column. First replace the logo or text-based brand mark, then check the header links. After that, update the main heading. For an electric mobility center, it can promise help with choosing and servicing a vehicle, but it should not promise technical specifications you do not have. Keep one supporting line beneath the heading about the region or service format.

Point the hero button not to a random anchor but to the page where the user genuinely takes the next step. If you already have a consultation form, assign it there. If only the model list is ready, the button can lead to that page. After choosing the text, open the link in a separate tab. This simple check catches the most frustrating omissions: a link to the demo site, an empty address, a draft page, or a route to a nonexistent section.

Choosing a Background Without Losing the Composition

Select a wide photographic image where the vehicle or infrastructure occupies a clear, though not necessarily central, position. Leave a calm area for text. Then set the background-image position and size through the container rather than by chaotically adding many separate pictures. On a wide screen, check that the vehicle is not cropped awkwardly; on a narrow screen, make sure the main subject remains recognizable. If one image does not work at both sizes, it is better to prepare an alternative narrow-screen background when your kit and editor let you assign one intentionally, or to change the hero composition.

Do not place a button, logo, or long copy inside the background image itself. Those elements do not adapt like normal widgets, are difficult to read, and are unavailable to search and assistive technologies. The photograph should provide atmosphere and tangible proof, while HTML elements provide content and action.

Step 3. Configure the Brand Story and Three Reasons to Trust You

Move to the light section after the hero. In its large heading, state the center's position without relying on a marketing cliché. For example, explain that the organization brings vehicle selection, maintenance, and charging solutions together in one path. In the two short text columns, describe which questions are solved before purchase or contact and how a visitor receives an answer. The copy must be your own: demo claims about company founding, manufacturing materials, or recycling percentages should not remain without confirmation.

Use the three cards below like this: the first describes vehicle selection or consultation, the second describes service diagnostics and maintenance, and the third describes charging solutions or corporate services. Keep a heading and clear outcome in each card. Instead of "Innovation," write something clients can verify, such as "Route-Based Vehicle Selection" or "Pre-Service Inspection." Briefly explain the method in the description. Add a button or link only if the corresponding page exists; otherwise, the card can remain informational.

Step 4. Connect the Large Vehicle Block to a Useful Page

In Lunost, the large vehicle image serves as the climax of the first part of the page. In this example, it can become a preview of a model selection, service diagnostics, or infrastructure project. If the image leads to models, it should have a clear link or "View Models" button beneath it. If it tells the service story, use different copy and destination. One photograph should not promise a catalog, warranty, charging, and corporate leasing at the same time - that makes the page harder to read.

Check the image alt text in the media-file or widget settings. It should communicate the image's role: "Electric vehicle from the center in an urban setting" or "Electric vehicle charging area," not a list of keywords. Alt text is useful when the image is unavailable and for assistive technologies, so do not duplicate the neighboring heading if the picture adds no new information.

Step 5. Build the Menu, Assign the Homepage, and Test the Visitor Journey

Create a WordPress menu from the prepared pages, place the most important areas first, and assign it to the header. Then open the homepage not only through editing, but as a new visitor would: from the site's primary address, through a menu item, from the hero button, from a card, and through the contact form. The path should be continuous. If a button leads to a form, there should be a clear on-screen outcome after a test submission. If the form is not configured yet, do not publish a "Book Now" call to action as though it works.

After that, assign the page as the static homepage in WordPress settings and update permalinks only through the established process for your site if addresses do not open. Do not impulsively change the permalink structure on a working site: that is a separate decision with consequences for existing addresses. For a new test project, it is usually enough to confirm that every button uses the intended path and that the site root opens the homepage you built.

Responsive Testing Without Guesswork

The Lunost listing describes a responsive layout, but that does not mean every new Russian text and every photograph will automatically look perfect on every device. In Elementor, enable the preview modes for wide, medium, and narrow screens, then review the page from top to bottom. Check meaning first: is the main heading visible, has the button disappeared, is the menu clear? Then review composition: has the hero become too tall, has the vehicle been cropped, have three cards turned into a cramped column with excessive gaps?

Elementor documentation notes that many settings can have values for different devices and that some values are inherited. This means edits should be intentional: if you change a heading size in narrow mode, confirm that it is a narrow-screen value and that it has not broken the wide version. Do not create a separate version of every block for the sake of two text lines. Usually it is enough to adjust the heading size, text-container width, vertical spacing, column order, or background position.

Responsive Testing Order

1. Check the hero: heading, button, text readability, and visible subject.
2. Check the header: menu items, action button, and absence of horizontal scrolling.
3. Review long section headings and confirm that Russian copy does not overlap neighboring elements.
4. Open cards and large photographs, then assess spacing and content order.
5. Test forms, contacts, and all real links in a separate browser window.

If a section looks worse on a narrow screen, do not start by shrinking every font. First determine why: the text may lack width, the image may have the wrong focal point, internal spacing may be too large, or two columns may not yet have collapsed into one. Fix the cause at the container or responsive-setting level, then repeat the test. This lets you preserve Lunost's large typography without sacrificing it to one unsuccessful section.

Example result check: a visitor arriving at the site root sees your own hero, understands the center's focus, receives three different reasons to continue, opens an existing section, and can complete the journey through contact details or a form without encountering demo dead ends.

Checking the Result: More Than an Editor Preview

A site that looks polished in Elementor is not necessarily ready to publish. The editor displays the page structure in its own working environment, while visitors follow a different path: the active theme, public styles, cache, WordPress menu, real links, images, and form. Lunost should therefore be checked from the most visible outcome down to the details. First open the root address as an ordinary visitor, then follow the key routes, and only afterward return to individual styles and settings.

Start by opening the homepage in a new private browser window. This session avoids some local login state and can help reveal stale cache or hidden draft pages. Confirm that the static homepage opens rather than WordPress posts. Look at the hero without the editor panel: is your heading readable, does the button lead to a real section, does the header cover the first line, has the photograph disappeared? If the public result differs from the editor, do not change the whole page at once. Identify which layer is responsible: the theme, Elementor global styling, cache, or a local container.

Visitor Journey Testing

A useful test is to follow the path as if you had arrived on the site for the first time. Do not jump straight into the editor. Click the first hero button, go back, open a principle card, use the menu to visit the contact page, then check the mobile menu. Record not only obvious errors but also moments of uncertainty: a button promises a test drive but opens a general page; a card mentions service but offers no next step; the menu contains an item that duplicates the hero. These observations matter more than a minor difference in a card shadow because they affect how understandable the journey is.

Check links in four places: a standard page section, the hero, navigation, and the footer. Demo destinations should not remain even in hidden buttons. If part of the site will be ready later, either send visitors to an honest intermediate page where they can make contact or temporarily hide that route. False activity damages trust more than a compact menu.

Checking the Page Rhythm on a Long Page

Scroll through the page from beginning to end without stopping at individual widget settings. In Lunost, transitions are especially important: the dark hero should give way to a calm light block, cards should open the path to strong automotive proof, and later sections should not suddenly introduce unrelated colors or photographs. If the page feels like several different websites, the cause is often content rather than CSS: inconsistent copy tone, repeated photography, random icons, or unnecessary decorative blocks.

Ask yourself about every section: does it continue the previous idea or begin a new one without preparation? Does it show a vehicle, service, or infrastructure item that genuinely belongs to your offering? Is there enough breathing room around the large heading? Has one primary action accent been preserved? This type of review evaluates both design and content. It is better than an automatic checklist because it helps you see the page at a visitor's natural pace.

Checking Copy, Images, and Basic Accessibility

Every image should have clear alt text where it carries meaning. A decorative hero background does not need to become a long image description if the text already conveys the same idea, but an important photograph of a vehicle or charging area needs a concise explanation. Do not stuff the alt text with every key phrase in the article. Its job is to communicate the image's purpose to someone who cannot see it.

Check contrast. Small light text over a complex photograph may look effective in one crop and disappear in another area on a narrow screen. A button needs enough difference between its background and label, while thin gray supporting text needs to remain readable on a light surface. Do not test only on the brightest monitor image: reduce brightness, open the page on another device, or ask a colleague to read the hero without context. If the meaning is not clear immediately, change the composition or color role.

Contact-form text belongs in the check as well. A field needs a clear label or visible caption, and users should see an understandable message after submitting it. Do not test a colleague's real address without approval: use a safe test process approved by your organization and make sure the action does not create false leads. If the form is handled by a separate extension, troubleshoot delivery through its documentation rather than trying to solve it inside Lunost.

Performance and Maintenance: What to Monitor After Launch

A template kit does not replace normal performance discipline. In Lunost, large automotive photographs and dark full-width blocks matter to the overall impression, but they can also increase page weight if original heavy files are uploaded without preparation. Before publishing, review your media files: use sensible dimensions, avoid uploading the same image repeatedly in several variants, and do not use a hero image far larger than necessary for the chosen width. Keep the original in the project archive, then prepare an optimized copy for the site through your established process.

Do not assume that a smaller file always means a better page. Aggressive compression can turn a vehicle and fine text into a blurry patch, which is especially noticeable in Lunost's premium composition. Compare the original image with the final version on a wide screen. If body details, the road scene, or button outlines lose clarity, use more conservative optimization. The goal is balance: the page should load quickly while its main visual argument remains convincing.

Caching and Elementor Changes

After editing a page, it can sometimes seem that Lunost is ignoring new values: everything looks right in the editor, while the public site still shows old colors, styles, or images. Do not rush to import the kit again. First open the page in a private window. Then determine whether the site uses caching at the plugin, hosting, or content-delivery-network level. Clear cache only through a tool you know and are authorized to use under the project process, then check the specific page again. This distinguishes an old page copy from a genuine styling problem.

If the public styling still does not match, return to the global values. Elementor stores a significant part of the design configuration in the site kit, so changing a global color or font can appear beyond one page. Compare whether the affected widget uses a global role or a local manual value. Fix the smallest possible scope: one widget, one container, or one global role. Reinstalling everything after one incorrect button introduces new variables and makes diagnosis harder.

Updates and a Change Log

Maintaining the site after launch requires one simple habit: before meaningful updates, create a backup and check the Lunost homepage on a copy. The most sensitive areas are the editor, active theme, additional widgets, and caching mechanism. Do not claim that a specific version is compatible without checking with the provider and in your own environment. Instead, keep a short internal log: the date of the change, what was updated, which page was tested, what was observed, and how to return to the prior state if a problem occurs.

This type of log is more useful than a long technical report. If the hero becomes taller after an ordinary update, you can compare it with its previous state. If a font disappears, you can see whether global values or the theme connection changed. If some editors accidentally alter button colors, agree on responsibilities: one designated person edits shared roles, while content authors replace only materials inside approved sections. This reduces the risk of the design system gradually falling apart.

A Safe Improvement Without Editing Kit Files

For Lunost, the safest improvement is not a code snippet but a disciplined reuse process. Create a saved Elementor template or preserve a reference section if your working configuration supports that process. For example, after approving a service card, save it as a reference for editors. A new page can then be assembled from typography, buttons, and spacing that have already been tested, rather than from randomly copied blocks. This is not an official Lunost-specific feature, but a careful Elementor template practice.

Before saving, make sure the reference does not contain someone else's URLs, temporary photographs, demo contacts, or hard-coded local colors. Then explain to editors which parts they may change: heading, paragraph, image, and button destination. Separately note that shared styles and container structure may be changed only as part of an approved task. Testing the improvement is simple: build one new test section from the reference and compare it with the original homepage. To roll back, delete the test template or restore the previous section from a copy without touching WordPress core, Elementor files, or the Lunost archive.

A Practical Integration with the Standard WordPress Menu

A useful Lunost setup is to use Elementor for the header's visual presentation and WordPress for menu structure. The builder's role is to place navigation in the right container, preserve button styling, and manage responsive behavior. WordPress stores the menu items and their destinations. The setup order is straightforward: first create pages, then build the menu in the WordPress admin area, then select it in the header navigation element and check the public-facing site.

The main risk in this arrangement is having two independent sources of truth. If an editor manually writes link labels in a decorative block while the site owner changes the WordPress menu, the routes will drift apart. Keep critical navigation in one menu, and use the same approved destinations for the hero and cards. The check is simple: open the menu and every primary button after each major change. The rollback is to restore the previous menu or remove the new header template assignment, not to delete the imported kit as a whole.

Practical outcome: a maintainable Lunost homepage is not a page people are afraid to open after publication. It has clear content responsibilities, verifiable links, one source for navigation, controlled global styles, and a copy for safe changes.

When Lunost Can Become a Strong Site Foundation

ThemeForest Lunost is a good choice when a project needs a clear, visually cohesive presentation of an electric mobility topic and the team is prepared to replace demo materials with its own facts, photography, and visitor journeys. The kit saves time on composition: the hero, light pauses for meaning, cards, and automotive proof already form a sequence. Its value, however, appears only after thoughtful configuration of global styles, the menu, homepage, and responsive presentation.

Start with a staging copy, import a clearly defined scope, and complete one homepage use case. Then check the visitor journey on the public page, not only in the editor. If that review succeeds and the content supports the brand's promises, you can download the ZIP archive and continue with an implementation plan that is already prepared.

ThemeForest Lunost Setup Video

This video complements the guide: a product video. Open it after the basic setup to compare the interface and sequence of actions.