ThemeForest Comuna - WordPress Theme

How to Install and Set Up ThemeForest Comuna for a Coworking Website

Think of ThemeForest Comuna not as a finished website you can simply upload and leave as is, but as a thoughtfully designed set of pages for a coworking space: a hero section that introduces the space, pages for memberships and work options, locations, amenities, events, a blog, FAQs, and two ways to convert interest into action: tour requests and contact inquiries. This guide walks through bringing that system into WordPress, keeping the design cohesive, and turning the demo sections into a working path from a visitor's first look to a submitted inquiry.

There's little value in repeating the kit's product description here. It's more useful to understand the order of implementation: first prepare a safe copy of the site and the WordPress environment, then import global styles and templates, assign pages and navigation, set up the header with ElementsKit Lite, connect the MetForm form, replace the media and copy, and finally test the visitor journey at different screen widths. This order helps prevent a common frustration: the hero looks great, but the menu, form, buttons, and pages function as disconnected pieces.

The kit works well for a small team building its own website, but the business owner still needs to make key decisions. Before opening the editor, agree on which rental options the space offers, which cities or neighborhoods it serves, how tour requests will be handled, and who will keep the events schedule current. With those answers in place, the template becomes more than a set of images: it's a useful foundation for a clear, practical website.

What Comuna Is Designed to Do - and Where Its Limits Are

Comuna is designed for a coworking space, flexible office, business hub, or community that needs to show visitors more than square footage and furniture. The page layouts make this especially clear: the home page guides visitors toward a choice, a dedicated page explains the spaces and membership options, location pages help visitors match the offer to a place, amenity and event sections explain the value of the community, and a tour form turns interest into action. Instead of one long, generic corporate page, visitors get a journey with a clear question at each step.

The template's main strength is the sequence atmosphere -> choice of workspace -> proof of convenience -> action. In the original design, a dark interior with pendant lights creates a calm focal point, while the lighter sections below make room for facts, photos, an accordion, and social proof. Warm orange is used to highlight actions, while deep green anchors headings and key messages. Keep those color roles consistent, and the site will feel cohesive even after you replace all the demo photos and copy.

The kit is a good fit when visitors need to make a relatively simple initial decision: choose a space for a day, a dedicated desk, a private office, a meeting room, or a meeting with a manager. It works for both a single urban location with several ways to work and a network with multiple addresses. It's especially effective when real photos of the space matter more than a complex catalog: Comuna can make a strong emotional impression and quickly follow it with concrete reasons to choose the space.

There are limits, too. This kit isn't a WordPress theme, and it doesn't add its own desk-booking system, availability calendar, online payment, or CRM. A page with a Book a Tour button can lead to an inquiry form, but availability management, lead routing, and follow-up emails need to be arranged separately. Don't promise visitors that they can reserve a desk immediately if your team actually handles requests manually. In that case, use an accurate call to action such as "Request a tour" or "Check availability."

Who the Kit Works Well For

Comuna suits the owner of a single coworking space, a flexible-office operator, a team opening a new location, or an agency building a site for that kind of client. Editors can update images, feature cards, zone descriptions, button copy, and pages without rewriting the markup. Marketers benefit from the built-in content structure: they don't have to work out from scratch where to show testimonials, how to explain membership options, or where to place a call to visit.

The kit is also a good choice when the site needs to speak to different audiences. A freelancer may care about a quiet desk and flexible hours, a small team about a private office and meeting room, and an event organizer about capacity and equipment. Don't try to sell all of them with the same line. Use the main page as a guide, then give each audience its own context, limitations, and next step on the relevant workspace cards.

When a Different Approach Makes More Sense

If the business needs a member portal, automatic time-slot selection, a live availability map, an hourly calendar with payments, or complex memberships with different access levels, Comuna can still serve as a storefront, but you'll need a separate, proven solution for those operations. Likewise, the template doesn't replace a multilingual strategy, legal copy, or a process for handling personal data. It covers the structure and presentation of the public-facing site, not every business process.

A practical rule of thumb: Start by defining one primary action for the home page. For most coworking spaces, that's a tour request. Every other button should either explain the available options or help visitors prepare to make that request.

Before You Import: Prepare to Keep the Design Intact

Importing a template kit can affect more than a single page. Depending on which parts you choose, it may include global styles, saved templates, and content. So it's safer not to start on the site's only live copy. Back up the files and database using your hosting provider's tools or your usual backup solution, and prepare a staging subdomain for major changes. This isn't just a formality: it makes it easier to compare the current site with the imported version, and gives you a way back if you select the wrong parts of the kit.

Make sure WordPress and Elementor are installed and updated to versions supported by your hosting environment. The kit specifies two required add-ons: ElementsKit Lite and MetForm. Install them before importing the kit. Otherwise, pages may load without a header, form, or certain widgets, making it hard to tell whether a module is missing or the import failed. For modern Elementor kits, Flexbox Container mode matters, too: it controls how sections are built, so turning it off can make a sound layout collapse into a disorganized stack of blocks.

Your WordPress theme provides the foundation for the page builder. This kit needs a lightweight theme that works with Elementor. Hello Elementor is a common choice, but you don't have to choose it just because of its name. The important thing is that your current theme doesn't impose its own containers, fonts, and header over the kit's design. If you use another theme, open a blank test page in Elementor first and make sure Elementor Full Width is available. This layout preserves the global header and footer while removing the theme's extra frame and default page title.

Gather Your Content Before You Start Designing

Collect your materials before you begin replacing the demo images. Photos are especially important for Comuna: overall views of the space, desks, a meeting room, a lounge, the team, details of the lighting and materials, and photos of each location. Different shots serve different purposes. A wide shot shows the scale, a medium shot shows the type of seating, and a close-up conveys attention to detail. Don't reuse the same photo across every page: visitors will stop being able to tell what each option actually offers.

For each location, prepare its name, address, access hours, contact channel, a short description of the neighborhood, the available workspace options, and any real distinguishing features. For each option, write down specific details instead of a marketing slogan: who it's for, what's included, its capacity or intended use, whether advance booking is required, and what to do if no spaces are available. This information will appear in the Space & Membership section, on the home page cards, and in the form.

What Not to Copy from the Demo Automatically

A demo kit may include sample names, photos, and figures. Don't leave them in place as a temporary solution if they don't describe your business. Start by replacing the logo, contact details, address, images, calls to action, menu items, and trust signals. If a section isn't ready yet, hide it during launch instead of showing an event that doesn't exist or an invented testimonial. The same applies to the blog: an empty blog page is fine only if the menu doesn't promise regularly updated content.

Check the usage rights for your media separately. Demo images may be licensed for preview purposes only. Use your own materials, licensed photos, or other images your project has the legal right to use. Replacing the demos also helps build trust: visitors see your actual space rather than an attractive but unrelated setting.

Import the Kit in an Order That Preserves Global Styles and Templates

Upload the kit's ZIP archive as provided; don't extract it manually first. In the WordPress admin area, the template kit importer is usually available under Tools → Template Kit. Before uploading, make sure Elementor, ElementsKit Lite, and MetForm are active. If the importer shows a requirements panel, install and activate any missing add-ons first, then return to the import. Otherwise, some of the layout may import while widgets appear as empty spaces or unrecognized elements.

The important order is to import Global Kit Styles first, then the pages and individual templates. The global styles provide the base colors, typography, background treatments, and other settings that make the orange button, green heading, and calm light section feel like part of the same system. If you add pages before importing the global styles, or immediately give them arbitrary local colors, the site can quickly turn into a set of pages that look almost alike but not quite cohesive.

After importing, open Templates → Saved Templates and see which parts are available. Pages don't always get published automatically; sometimes you need to insert them into a new page through the template library. Create a page with a clear name, open it with Edit with Elementor, open the templates folder, and insert the relevant Comuna layout. For a standard home page and internal pages, choose Elementor Full Width in the page settings when you want the global header and footer to appear. Use Elementor Canvas only for special landing pages that don't need the shared navigation.

Create the Pages in This Order

1. Create drafts for the home page, spaces and workspace options, location list, individual location, amenities, community and events, FAQs, blog, contact page, and tour request page.
2. Insert the appropriate templates from the library and give each page a clear, human-readable permalink right away.
3. Don't edit every section of the home page at once. First replace the main header, hero headline, two key buttons, and hero section.
4. Next, fill in the pages those buttons lead to. Work on secondary decorative sections only after that.
5. In Settings → Reading, set a static home page and choose a separate posts page if you'll use the blog.

This order matters because visitors rarely read a site from top to bottom. They click the first clear button, check the details about a workspace option or location, and return to the inquiry form. If you build only an impressive home page and leave the other links pointing to demo pages, you'll lose their trust. The home page is ready only when every prominent action leads to a real, complete visitor journey.

Set Up the Header and Footer with ElementsKit Lite

The kit uses ElementsKit Lite, so set up the global header and footer as separate templates rather than as one-off sections on each page. Open ElementsKit → Header Footer, create or find the imported header template, set its type to Header, set its display condition to Entire Site, and enable it. Then open it in Elementor and choose the actual navigation menu in the menu widget. Repeat the process for the footer, using the Footer type.

If the header imported but doesn't appear, don't rush to duplicate it on every page. First make sure the template is active, its display condition covers the pages you need, and the page itself isn't using Elementor Canvas. Also check whether your active theme is displaying its own header over the global template. A duplicate navigation bar isn't a reason to hide one with a CSS tweak. Instead, keep a single source of control so the menus don't drift apart after the next update.

First Check on the Live Page

After importing, open the published test page in a separate window. Check the visitor-facing version, not just the Elementor canvas. Make sure the fonts, background photos, headings, buttons, header, and footer appear. Then check the editor to confirm that each widget has its expected content rather than a missing add-on icon. It's a simple but critical check: if the import caused a problem, you want to catch it before replacing copy across the site.

Comuna's Design DNA: Keep the Look Cohesive as You Replace the Content

Comuna's signature comes from the contrast between two different rhythms, not from one particular color or photo. The hero section is dense, dark, and atmospheric: an interior photo sits behind a large white headline, a small topical label, two actions, and a sense of depth. After that, a calm, light section opens up, with photos, large green typography, and generous whitespace. The next section may feel open and functional again: a workspace options accordion on the left, with an explanatory photo on the right. This shift between dense and airy sections keeps visitors engaged and stops the page from becoming an endless gallery of cards.

Don't copy the surface treatment without preserving the role of each element. If the new hero image is light, the heading and navigation still need enough contrast. You could add a dark overlay, choose a different part of the photo, or use a separate color panel, but don't place text over an arbitrary bright background. If you replace the orange button with a brand color, keep the same rule: use the accent color for one primary action in each area. When every link and button is equally bright, visitors can't tell which action matters most.

How the Home Page Sections Work Together

The hero section answers, "What is this place, and why should I keep looking?" In Comuna, it's best to answer with a clear combination: the type of space, a promise about work and community, one primary tour button, and a second option for visitors who are still comparing workspace types. Don't overload the hero with rates, a long list of services, and several equally prominent buttons. Visitors don't know the full context yet; they need to get a feel for the space and see a clear next step.

The next trust-building section should show that the promise is more than decoration. Use real photos, a short description of the community, one verifiable fact about how the space works, and, if you have permission, logos of member companies. Then move into the choice of workspace options. The accordion works best when each item describes a real need instead of offering a catchy name: focused work for a day, a regular desk, privacy for a small team, or a meeting with a client.

After that, move from the general atmosphere to real use cases. Don't repeat the hero photos. Show a desk, meeting room, shared table, kitchen, or quiet area where the copy promises that amenity. The final home page sections should bring visitors back to an action: a form or tour button, an explanation of what happens after they submit a request, and a contact option for unusual questions.

Use Global Typography and Colors Instead of Styling Each Block by Hand

In Elementor, start by opening Site Settings and reviewing the global colors and fonts imported with the kit. Keep them as your starting system. Most brands need only a primary dark color, a light neutral surface, a body text color, and one accent. Change them through global settings rather than through dozens of individual widgets. Then updating button or heading colors stays manageable instead of turning into a search for one-off exceptions across the site.

The same applies to fonts. Comuna depends on the contrast between expressive, large headings and calm, readable copy in workspace descriptions. Choose a global font pairing and use it consistently. Use local settings inside individual widgets only when there's a clear reason, such as a small label above a heading or a compact photo caption. If editors manually change the font on every block, making later adjustments for mobile will become difficult and unpredictable.

Don't mix global and local styling without a reason. If one heading uses a global color token while a similar heading has a manually set color, a future brand update will affect them differently. Before launch, open two or three templates and make sure the same kinds of elements really do use the same system.

A Safe Custom CSS Adjustment for Long Russian Headings

Russian copy is often longer than English, so a headline in the dark hero section may wrap awkwardly. If Elementor's settings don't give you enough control, use a small, reversible adjustment. It relies on Elementor's standard option to add a CSS class to a section and doesn't change WordPress files, the theme, or the kit. Assign the class comuna-hero-copy to the hero headline container, then add the rule to the custom CSS field in your child theme or to the theme's additional CSS area, if it provides one.

.comuna-hero-copy .elementor-heading-title {
  max-width: 15ch;
  text-wrap: balance;
}

@media (max-width: 767px) {
  .comuna-hero-copy .elementor-heading-title {
    max-width: 12ch;
  }
}

This is a custom adjustment, not a Comuna feature. It limits line width so a large headline forms a calm, readable block. After saving, check both the desktop and mobile layouts, then check another language version of the site if you have one. If the headline breaks into too many short lines, remove the class from the container or remove the rule altogether. Reverting is safe: the original layout returns without changing the template data.

Map the Pages: Turn the Templates into a Visitor Journey

Having eleven page layouts doesn't mean you need to put all of them in the menu. Start by mapping the actions visitors need to take. Someone choosing a place to work will usually follow one of three paths: look at workspace options first, look for the nearest location first, or check the amenities and atmosphere first. Your menu should support those paths rather than repeat the kit's internal file names.

A practical top-level menu for one location might include "Spaces," "Amenities," "Events," "About" or "Community," and "Contact." Keep "Book a Tour" as a prominent button. For a network, add "Locations" as a distinct path: visitors choose an address, review that space's details, and then send a request. If there's only one location, don't create a complicated directory just because the kit includes a template for one.

The Spaces and Membership Options Page

This page should make the choice feel straightforward. Instead of a general "we have it all" message, show four clear options or fewer. For example, a hot desk for a short work session, a dedicated desk for regular use, a private office for a team, and a meeting room. Give each option a consistent outline: who it's for, what the visitor gets, when it makes sense, and what to confirm before visiting. If rates change or depend on the term, don't put unverified prices in prominent static banners. Explain what information visitors can request through the form and make the form specific enough to capture it.

The accordion in the original layout works well for comparing options. Don't leave its entries blank or fill them with identical descriptions. The first expanded item should represent the option that brings in the most qualified inquiries. Visitors expand the other items themselves, so each heading needs to make sense on its own. After editing, check that the section height changes smoothly when an item opens and that the photo beside it isn't cropped awkwardly.

Location Directory and Individual Location Pages

A locations page is useful when you genuinely have more than one address. Each card should show more than the neighborhood name: include a landmark, the character of the space, and a first action. An individual location page should continue the decision-making process with photos of that specific space, available workspace options, directions, hours, services, contact details, and a way to submit a request. Don't copy the same text across all addresses and change only the street name. Visitors should understand what makes each space different: whether it's quieter, closer to transit, has private offices, or works well for events.

If you embed an external map, check that it works on phones and fits with the site's data privacy policy. If the map isn't ready, an address and written directions are more useful than an empty decorative area. You can use a standard directions tool for the route button, but don't make it look like a booking button. Each action should have one clear purpose.

Amenities, Community, and Events Without the Fluff

The amenities section will be more convincing when every item has a concrete, observable benefit. Don't say "fast internet"; say "a stable connection for video calls in the meeting room" only if you can actually provide it. Instead of "friendly atmosphere," describe a regular way for members to meet, the presence of a host, or how the shared spaces work. Include events if the space runs them and someone can keep the calendar current. Otherwise, show the community through real activities: morning meetups, private sessions, sharing expertise, or partner events.

The blog shouldn't be there just for decoration. It's useful when someone can publish material about working practices, events, locations, or advice for members. If there's no content plan, remove the blog from the menu until the first posts are ready. An empty blog filled with demo cards damages the sense of a living community more than having no blog at all.

Set Up the Hero, Buttons, and Menu After Installation

Once the pages are in place, return to the hero section. Its job isn't to fit everything about the business into one area. It should quickly answer three questions: Where am I? What can I do here? Where should I go next? The original Comuna layout uses a small topical label, a prominent promise, a short explanation, and two buttons. Keep those levels of information. Move longer descriptions farther down the page rather than shrinking the text until it's hard to read.

The primary button should go to the tour request page or to a form on the same page. Use the second button to direct visitors to the workspace options or location pages. Set both links in the Elementor button settings and test them after publishing in a private browser window. A common mistake is to test a link while logged into the editor, where cached pages and drafts can hide the real issue. If the link opens a blank page, first check whether the destination is published and has the right permalink, then reselect the page in the link field.

Set up the menu in WordPress as a navigation menu, not as text inside the header. Create one primary menu, add only real, published pages, and select it in the header's menu widget. Then check the mobile version. On a narrow screen, menu items shouldn't wrap into two lines inside one button. If the labels are too long, shorten them without changing their meaning: use "Options" instead of "Spaces & Membership," or "Locations" instead of "Our Office Locations." Visitors should recognize the section, not have to read a document title.

Connect Global Styles to What Visitors See

When updating the brand, start with the global palette. In Comuna, the important thing isn't the number of colors, but the role each one plays. A dark background supports immersive photo sections, an almost-white surface gives the content room to breathe, deep green anchors headings and key copy, and the warm accent highlights actions. If the brand calls for a different button color, use it in place of the accent and check the text contrast. Don't turn every heading, line, and icon into an accent color at once.

After the global colors, adjust the global fonts. Different Elementor widgets may have their own local styles, so changing a global value doesn't always update a widget that's already been overridden. Don't assume something is broken. Open the specific heading, go to the Style tab, and check whether its color or typography is set manually. If so, decide whether the exception is justified. For headings of the same type, it's usually easier to restore the global value than to maintain dozens of local variations.

Make the Layout Responsive Without Just Shrinking Everything

Switch between desktop, tablet, and mobile views in Elementor before publishing, not after visitors complain. Settings at narrower widths usually inherit values from larger layouts, so build the desktop version first, then change only what needs to be different. On a phone, preserve the order of information: label, heading, short explanation, primary button, secondary action. Don't try to squeeze the entire desktop composition into half the height.

In Comuna, pay particular attention to the hero background, side-by-side buttons, text-and-photo pairs, workspace options accordion, and header. Make sure text doesn't land on the brightest part of a photo, buttons don't run together, images don't crop out the main subject, and cards have enough padding. If a photo makes text harder to read on a phone, change its position or the container height instead of reducing text contrast.

A Quick Check After Each Major Change

• Open the home page as a logged-out visitor.
• Test the primary action and the second button.
• Expand each item in the accordion.
• Open the menu on a narrow screen and visit each top-level page.
• Return to the home page and make sure the header and footer aren't duplicated.

This quick sequence catches most problems before they spread across a dozen pages. Don't leave mobile testing until the last day. Once you've made a lot of local changes, it's harder to work out which setting shifted a section.

Build the Tour Form in MetForm and Turn a Button into a Useful Inquiry

Comuna includes templates for a tour request form and a contact form. They're meant to be more than decorative white cards: they're places where visitors can share the minimum information your team needs to give a useful response. Don't add ten fields to the first form. A tour request usually needs only a name, preferred contact method, workspace option, preferred day or time, and a short comment. If the space operates in several cities, add a location selector. Every field should have a clear reason to be there, or visitors may abandon the form.

To insert an imported MetForm layout, open the page in Elementor, find the form widget, and use Edit Form. In the form panel, create or select a saved template, open My Templates, insert the imported layout, and save the page. Then replace the demo labels and button copy, and set which fields are required. A clear button label could be "Request a tour." Don't promise a confirmed booking if the request goes to a manager for manual handling.

After setting up the form, decide where submissions go. Check the recipient address, sender name, any confirmation email to visitors if one is actually needed, and how inquiries are stored. Don't put personal data in random editor notes or leave a test email address in place. If the site's email delivery is unreliable, first set up a dependable WordPress email delivery method approved for the project, then submit a test inquiry. A form that appears to send successfully doesn't necessarily mean the team received the message.

How to Test the Form Properly

Test the form from the published page, not from the Elementor panel. Submit realistic but test data, check required fields, make sure error messages are correct, and verify the status shown after submission. Then confirm that the email reaches the right person and clearly includes the selected workspace option, location, and contact details. If there's a visitor confirmation email, check that as well: it should say the inquiry was received, not give the impression that a space has already been booked.

After the form, add a short explanation of what happens next, such as "Our team will follow up to confirm a convenient time." This helps visitors know what to expect without requiring extra fields. You can also show another contact channel nearby if someone actually monitors it. Don't list a phone number, messenger, or address that nobody responds to.

Don't edit the plugin core, kit files, or WordPress templates when changing the form. MetForm lets you edit fields in its own editor, and Elementor lets you adjust the section's placement. This approach is more likely to survive updates and is easy to undo: restore the previous form template or disable the new field if it causes problems.

A Practical Example: Launch a New Location Page with a Tour Request

Imagine a coworking operator opening a new space in a business district. The website's goal is to get tour requests for that specific location, not just collect general inquiries. Comuna can support this without copying every section from an existing page. The key is to distinguish what applies to the whole network from what applies only to that address.

Prepare the Page

The new location needs five kinds of information: a photo of the entrance or a distinctive interior, a short description of what the space is for, a list of available workspace options, real amenities, and visitor policies. Don't fill in unknown details with demo content. If the meeting room isn't ready, don't list it on the cards. If access hours are still being confirmed, the form should collect an inquiry rather than offer visitors a nonexistent time slot.

Create a new page based on the Location Single template. Save it as a draft first, then add the heading, address, main photo, and hero copy. Replace the amenities and photos with details that apply only to this location. Then configure the tour button so the form either has the correct address selected or states it clearly. That way, the manager won't have to guess which location the visitor meant.

Build the Page Step by Step

1. Duplicate or insert the individual location template and give the page a clear name.
2. Add a real, wide photo to the hero section, preserve the contrast overlay, and replace the generic heading with a specific promise about this location.
3. Include only confirmed amenities in the feature section: a meeting room, private offices, a kitchen, a quiet area, parking, or transit access, depending on the facts.
4. Link the location card on the main locations page to the new page, and add it to the menu if the site is already accepting visitors there.
5. Configure the form so visitors can see which location they've selected and your team receives that information.
6. Check the page on desktop and mobile, then follow the journey from the home page to a submitted form as a new visitor would.

The result should be a working journey, not just an attractive page. Visitors see the right neighborhood, learn about the available workspace options, understand what the space is like, click to request a tour, submit a useful inquiry, and receive a clear explanation of what happens next. If you can't tell which location the page describes during testing, it looks too much like a general storefront and needs more specific details.

What a Successful Test Looks Like

Open the page in a regular browser without signing in to WordPress. Make sure the header doesn't cover the heading, the primary button is visible above the fold, all photos belong to this location, the map or written directions make sense, and the form passes along the location. Then narrow the browser window. If the photo takes up too much space for the button on a phone, reposition the background or move some of the visual content farther down the page. The test should answer this question: "Can someone complete the intended action without needing a manager to explain anything?"

Set Up the Header, Footer, and Navigation States Separately

Comuna's header is visually light, but that doesn't make it unimportant. In the hero section, it helps visitors understand where they are, navigate to key pages, and keep the tour button in view. On the dark hero background, light menu labels and a white or light-colored button serve as clear landmarks. The same header needs to remain legible on light interior pages, so compare it against every type of background before publishing, not just the home page.

Open the imported template in ElementsKit → Header Footer with Edit with Elementor. Don't change the design right away. First check what's there: the logo, navigation menu, primary button, and, if present, mobile menu button. Then set the content sources. Link the logo to the home page, and select one WordPress menu for the navigation instead of adding separate links to each menu item. The button should lead either to the tour form or to a page with the form. Don't give the logo and button two different routes to the same unclear destination.

If the coworking space's name is longer than the demo name, first check how much room the logo has. Don't solve a long name by shrinking it to tiny text in the header. A brand mark, shortened name, or more compact horizontal logo prepared by a designer is a safer choice. Then check the mobile breakpoint: the logo, menu button, and any additional button shouldn't compete for the same line. Sometimes the best option is to keep only the mark and menu button in the mobile header and put the main call to action on the hero section.

Set Display Conditions Without Creating Surprises

The header template works across the site because of its display condition. Entire Site is usually the right choice for a primary website header. If you need a special version, such as minimal navigation for a standalone ad landing page, create a separate template and assign it a narrower condition. Don't turn the main template into a mix of full navigation and a stripped-down utility bar. Two deliberate versions are easier to test than a dozen exceptions buried in page settings.

After changing the conditions, write down a short map. The shared header serves the home page, spaces, locations, events, FAQs, and contact pages. A special header, if you really need one, serves only the agreed page. Then the team can tell where to update the menu without opening every page in Elementor. If the special template is no longer needed, remove its display condition and check that the page has returned to the shared navigation. Don't delete the template right away; first confirm that it's not used elsewhere.

Use the Footer to Reinforce Trust, Not to Store Every Link

The Comuna footer completes the visitor journey. It can include concise contact details, a link to the main contact channel, the address, secondary navigation, and required legal pages if they're ready. You don't need to repeat every menu item, every social network, and every marketing claim. The more utility links you add, the harder it is for visitors to find what they need on a phone.

The footer is also a useful trust check: the business name, address, and contact details should match the main pages. If the hero shows one phone number, the contact page shows another, and the footer shows a third, visitors won't look for an explanation. Use one source for these details or add them to the editorial checklist. Copyright text, privacy policy, and consent language should reflect the project's actual legal requirements, not be copied blindly from the demo.

Test the Mobile Menu

Test the menu on a phone by tapping it, not just by narrowing a browser window. Open it, go to a page, navigate back, and open it again. Make sure it doesn't remain over the page content after navigation, menu items have enough room to tap, and the close button is visible on every background. If the menu has nested items, don't bury the main tour action deep inside them. Comuna works best with clear, direct actions rather than complicated tree navigation.

Edit Comuna Pages Without Losing Their Structure

In Elementor, every block can seem easy to replace, so the temptation to rearrange everything can come quickly. But Comuna's sections already have a meaningful order. A useful way to work is to identify each container's role before changing its contents. For example: "this is the trust section," "this is where visitors choose an option," "this shows the space," or "this is where they submit an inquiry." Once the role is clear, you can change the copy, photos, number of cards, and order of details without breaking the visitor journey.

Start editing with Navigator. It helps you see the container tree and distinguish the shared background from the text column, or the card grid from an individual card. Instead of clicking around on the canvas, select the container by its name and make changes intentionally. Rename important containers to something recognizable, such as "Hero," "Options," "Locations," or "Tour Form." These names don't affect the public site, but they make it much faster to return to a page weeks later.

Replace the content before adjusting the layout. Add the real heading, description, photo, and link. See which lines have become longer, which cards have lost their balance, and where the button no longer fits. Only then adjust the container width, padding, image height, and breakpoints. If you fine-tune everything around the demo copy first, every later content update will throw it off.

Work with the Hero Container

The hero section usually consists of a background container, a darkening overlay, a header, a text column, and sometimes a media element. The background has two jobs: establish the setting and add depth. The overlay makes the text readable. The copy states the promise. The buttons start the visitor journey. Don't make one element do another's job. If the text is hard to read, adjust the overlay or the background position. If the space doesn't come through, choose another photo. If the promise is unclear, rewrite the heading instead of adding three more paragraphs.

A single strong image with some clear space for text works better than a collage of small photos on a dark hero background. Comuna's original design uses interiors, glass, lamps, brick, desks, and people to convey an active workspace. Your photos can be different, but they should serve the same purpose: show the scale and leave enough contrast for the text. Check your photo inside the container, not just in the media library. The same image may look great in a wide layout and crop poorly in a tall mobile layout.

Cards, Accordions, and Repeating Sections

Repeating elements in a template should follow a consistent content pattern. For location cards, use a name, a short benefit, a photo, and an action. For amenity cards, use an icon, a concise label, and a concrete benefit. For workspace options, include the name, use case, limitation, and next step. Write that pattern down as an editorial rule, and don't add a fifth line to one card when the others have two. Consistent card rhythm is part of readability, not a matter of decorative fussiness.

Text length matters especially in an accordion. A good expanded item should take only a few seconds to read: a label, one short paragraph, three specific conditions, and an action. If you find yourself adding a long company history, move it to a dedicated page or a section farther down. Also avoid putting links inside accordion headings; on a mobile device, it can be hard to tell whether tapping the heading expands the item or opens another page.

What to Do with Sections You Don't Need

Don't publish an unused section "for later." If you don't have permission to use testimonials, hide the testimonial section. If you're not running events yet, don't promise an event calendar. If the blog will launch later, remove it from the menu. A coworking site earns more trust by being concise and honest. Save an unused section as a template or draft if you plan to return to it, but don't make visitors judge an unfinished part of the project.

Local Search, Accessibility, and Speed: What to Improve After the Initial Build

Comuna can help make a page distinctive, but design alone doesn't improve search visibility or usability. For a coworking space, local search intent needs to be clear. On each location page, use the real neighborhood or city name naturally in the heading, opening copy, address, directions, and alt text for relevant photos. Don't repeat the same phrase in every section. People and search engines should get the same useful information: where the space is, who it's for, and what visitors can do.

Each page should have its own purpose. The home page introduces the overall offer, the workspace options page helps visitors compare, a location page answers practical questions about that place, the amenities page explains what's available, and the contact page completes the journey. Don't create several nearly identical pages with the paragraphs rearranged. That makes the site harder to use and maintain without giving searchers a better answer.

Headings and Images

Use one main heading on each page that describes what the page is about, rather than relying on a slogan with no context. Then build a clear hierarchy of subheadings. In Elementor, this means choosing the appropriate HTML tag in the heading widget, not just making the text large. Bolding a paragraph for visual emphasis doesn't replace document structure. This matters especially on long Comuna pages with accordions, cards, and photos: good headings give readers clear points of reference.

Add alt text to photos when they convey information. Describe what's actually in the photo and why it matters: "quiet work area with individual desks," not "best coworking office rental." Decorative textures and background elements don't need artificial lists of keywords. If an important photo is used as a container background, convey its meaning in nearby text as well, since assistive technologies may not treat backgrounds as regular content images.

Media Size and Perceived Speed

Large interior photos are part of Comuna's story, but oversized files can make a visitor's first page load slow. Prepare each image to match the size it will actually appear in the layout, and don't use a huge file for a small card. Keep the image quality high, but don't upload an unprocessed camera original. Check more than the file size: make sure the photo isn't too blurry and that dark interiors and gradients don't show noticeable artifacts.

Don't use a video background in the hero just to add motion. For a coworking site, it's more important that visitors can quickly read the offer and find the button. If video genuinely helps tell the story, choose an appropriate poster image, make sure it works on mobile, and preserve access to the main message when playback isn't available. A strong still photo often gives Comuna enough atmosphere with less risk to speed and readability.

Basic Accessibility Checks for Interactive Elements

Check contrast for headings and buttons, especially if you change the original palette. Make sure button copy is clear outside its surrounding context: "Learn more" works only when it's obvious what visitors will learn more about; "See workspace options" is clearer. Form fields should have visible labels, not just placeholder text that disappears. The success message should be easy to notice, but it shouldn't be the only confirmation of what happened.

Test the accordion with a keyboard. Its trigger should have a clear name, keyboard focus should be visible, and the content shouldn't become inaccessible because of an unusual animation. Exact behavior depends on the widget and add-on version, so after an update, run a quick manual test instead of assuming everything still works as before.

Prepare for Updates and Hand Off the Site

The template kit shouldn't become a black box for the next editor. Before handing off the site, note where global colors and fonts are managed, which template controls the header, where to edit the footer, which page is set as the home page, where the tour form is, and who receives inquiries. A short internal guide with the names of the relevant admin sections is enough. It saves time later and helps prevent a new team member from deleting a working global template because they think they're editing a single page.

Make a separate list of dependencies: Elementor, ElementsKit Lite, MetForm, and any tools that are actually used for backups, email delivery, or optimization. Don't install dozens of add-ons "just in case." Each one adds updates, settings, and potential conflicts. If you don't need a widget after setup, don't leave it active just because it was once part of the demo.

A Safe Update Routine

Before a major update to WordPress, Elementor, the theme, or an add-on, make a fresh backup and test the update on a staging copy if the site accepts real inquiries. Then run through a short checklist: home page, menu, location page, accordion, form, and mobile layout. If everything checks out, schedule the update for the live site. That's less stressful than waiting for a visitor to report that the header or form disappeared.

After an update, don't immediately rewrite styles if you notice a small shift. First identify what's affected: an Elementor container, global style, ElementsKit widget, or cached version. Compare the staging and live copies, review the settings that changed recently, and then adjust only the necessary layer. That process keeps Comuna manageable even after it's been in use for a long time.

Hand Off Content Editing

Editors don't need access to every technical setting just to update an event announcement or a location photo. Give them a short list of rules: don't change global colors without approval, don't delete labeled containers, test the link after changing a button, don't publish demo photos, and submit a test form after making a significant change. With WordPress roles set up correctly, regular editors can update content without accidentally changing plugins or the site's structure.

It's useful to review the site periodically as a new visitor. Are the events real? Does the address work? Are inquiries coming in? Are the workspace photos up to date? Does the description match the options available? This kind of review does more to keep Comuna useful than a cosmetic background change. The template provides a sound layout; current content builds trust.

Content and Editorial Roles: Keep the Template in Shape Over Time

A site can look great on launch day and gradually lose its shape after a few rounds of updates. The problem isn't Elementor; it's the lack of boundaries: each editor changes colors, font sizes, padding, buttons, and photos according to personal taste. For Comuna, assign a few simple roles. One person manages page structure and global styles, another updates copy and events, a third reviews photos, and a manager checks inquiries. This isn't bureaucracy; it helps keep content editing separate from changes to the design system.

Write a short internal content guide. Each workspace card gets a heading, one paragraph, three or four verifiable points, and one next step. Each location gets a photo, address, distinguishing feature, available workspace options, and contact details. An event gets a date or status only if the responsible staff member will keep it current. The hero section gets one primary action. These guidelines preserve Comuna's rhythm as you add content over time.

Prepare photos before uploading them. Give each file a clear name, write alt text that describes the image, reduce the file size without making it hard to see, and check the crop. Alt text shouldn't repeat the company name or list keywords. Describe what the photo shows: "meeting room with a large table and natural light" or "shared coworking area with individual workstations." That helps people using assistive technology and keeps the media library organized.

When to Make a Local Change and When to Use Global Styles

A local change makes sense for something unique to one page: a photo of a particular location, a long headline, event copy, or the state of one button. Use a global change when it applies to all similar elements: the primary call-to-action color, heading font, default card radius, or link style. Before making a change, ask yourself, "Should this affect the other pages, too?" If so, look for a global setting. If not, change the widget or its container.

If you're unsure, duplicate the page first or save a template as a draft. Elementor lets you work with saved templates, but changing a shared block that's already in use can affect many pages. Testing significant changes on one page first helps prevent a fix for a new location's menu from unexpectedly breaking existing landing pages.

Before Publishing: Make Sure the Page Works as a Journey, Not Just a Layout

The final Comuna review has three parts. Start with the content: are the photos, addresses, workspace names, contact details, and promises real? Next, check the interface: do the menu, buttons, accordions, form, header, and footer work? Then check responsiveness and how quickly visitors can make sense of the page: does anything overlap, is there enough contrast, does the page load promptly, and does a large photo push the main action out of view?

Test visitor journeys, not individual widgets. The "I want to visit" journey starts in the hero section, goes through a location page, and ends with an inquiry. The "I'm choosing a workspace option" journey goes to the spaces page, opens the accordion, and returns to the form. The "I want to know I can trust this place" journey moves through amenities, community, and FAQs before reaching the contact page. For each journey, check that a useful action is no more than three clicks away. If it takes longer, consider whether important information is buried too deep.

When checking different devices, look at the actual reading order. On desktop, a photo and text may sit side by side; on a phone, they stack vertically. Make sure the important information comes first after the layout changes, not a decorative image. Test keyboard access as well: can you see focus on buttons, open the menu, and reach the form? Full accessibility depends on the theme and installed add-ons, so don't assume it's automatic; check the basic interactions manually.

Ready-to-launch check: A new visitor on a phone can understand what kind of space this is, find an option that fits, see the actual location, and submit an inquiry without having to search through messaging apps for more details.

Cache and the Updated Page

If visitors still see the old version after you save, don't edit the section again at random. First open the page in a private window, clear the cache in the optimization plugin or at the hosting level according to the project's usual procedure, and check the CDN if there is one. Then make sure the changes weren't saved only as a draft. Repeatedly editing the page just to get around the cache can create a real second problem: you may change a working element while trying to see the updated version.

Troubleshooting Comuna: Symptoms, Checks, and Safe Fixes

Most problems with a template kit come from a gap between the import, a required add-on, the page layout, and the cache, rather than from one hidden error. Good troubleshooting starts with identifying the exact symptom. Don't try reinstalling Elementor, the theme, every add-on, and the cache all at once. After a batch of changes, it's hard to identify the cause, and the chance of a conflict only increases.

The Page Imported, but Widgets Look Empty or Broken

Symptom: Some of Comuna appears, but the header, form, accordion, or individual sections are blank, or the editor warns about an unknown element. Likely cause: Required add-ons weren't active before the import, or the import didn't finish. Check: Open the plugin list and confirm that Elementor, ElementsKit Lite, and MetForm are installed, then find the affected widget in the editor. Fix: Install and activate the missing add-on, return to the importer, and import only the affected template or section again. Then open the published page in a separate window. Revert: If activating the add-on causes compatibility changes, deactivate only that add-on on the staging copy and restore a backup point. Don't delete data on the live site.

The Header Is Missing or Appears Twice

Symptom: Some pages have no navigation, while others show two headers. Likely cause: The ElementsKit template has no display condition, the page uses Elementor Canvas, or the active theme displays its own header alongside the template. Check: In ElementsKit → Header Footer, check the template type, activation status, and Entire Site condition. Then open the page settings and check Page Layout. Fix: Choose Elementor Full Width for regular pages, activate one global template, and configure the theme so it doesn't duplicate the navigation. Revert: Save the theme settings before changing them. If the change makes things worse, restore the previous layout and investigate the duplicate on a test page.

The Hero Looks Good in the Editor, but the Text Is Hard to Read on a Phone

Symptom: On desktop, the heading sits over a dark part of the photo, but on mobile it wraps onto a light area or covers the button. Likely cause: The smaller layout inherited the desktop font size, container height, or background position. Check: Switch Elementor to mobile view, inspect the container and heading's Style and Advanced tabs, then open the live page on a phone. Fix: Change the background position, reduce the section height, shorten the copy, and keep one primary button above the fold. Don't just shrink the font if the problem is contrast. Revert: Reset the mobile-specific value so the element inherits the desktop setting, then adjust it again with a clear purpose.

The Button Works in the Editor but Leads Visitors to a 404 Page

Symptom: The link opens the wrong page or an error page. Likely cause: The demo link is still in place, the destination page isn't published, or its permalink has changed. Check: Open the button settings, verify the selected page, and open its address manually in a private window. Fix: Publish the destination, select it again in the link settings, and save the page. If the site's permalinks changed after a migration, save the WordPress permalink settings without changing their structure to refresh the routing rules. Revert: Remove the incorrect link until the destination is ready instead of leaving visitors with an error.

The Form Shows a Success Message, but the Team Never Gets the Inquiry

Symptom: A success message appears after submission, but the email never reaches the shared inbox. Likely cause: The recipient address is wrong, the server isn't delivering mail, or the notification landed in spam. Check: Submit a test from the published page, compare the recipient address, check the form log if available, and look in the spam folder. Fix: Set a real recipient address, configure a reliable WordPress email delivery method for the project, and test again. Revert: Until delivery is confirmed, keep an alternative contact channel visible and don't promise an immediate response.

Changes Are Saved, but Visitors Still See the Old Design

Symptom: The editor shows the updated section, but the live site still shows the old one. Likely cause: The browser, optimization plugin, hosting, or delivery network is caching the page. Check: Use a private window and another browser, then clear the cache according to the project's usual process. Fix: After clearing the cache, check the page while logged out of the admin area. If nothing changes, make sure you edited the published page rather than a copy. Revert: Don't make random additional changes just to refresh the cache, or you'll lose a clear history of what changed.

When Comuna Is a Good Foundation for Your Website

ThemeForest Comuna is especially useful when a coworking space needs more than a generic corporate site: visitors should get a feel for the place, compare workspace options, learn about a specific location, and send a clear inquiry. Success depends less on how many templates you import than on how carefully you put them to work: import the global styles first, keep global rules separate from local exceptions, replace demo content with real information, and test the header, form, and visitor journey on a phone.

If your content and photos are ready, someone is responsible for inquiries, and you have a staging environment, you can download ThemeForest Comuna and start with a safe import on a copy of the site. Then build from the home page toward real destinations, not from one decorative section to another. That way, the kit can do what it does best: present a real workspace in a calm, clear, and convincing way.

ThemeForest Comuna Setup Video

This product video complements the guide. Watch it after the initial setup to compare the interface and sequence of steps.