JoomlArt Space - Joomla Template

How to Set Up JoomlArt Space for a Joomla Portfolio Website

JoomlArt Space is more than just a visual skin for Joomla. It is a ready-made foundation for an agency site, studio site, portfolio, or a small corporate showcase. This guide does not repeat the template's marketing copy. Instead, it walks through the practical process: how to prepare the site, choose an installation method, configure the template styles, build the homepage with modules, publish projects, and make sure the result looks polished across different pages.

This material is intended for users who already understand the basic Joomla workflow: menus create pages, modules are displayed in template positions, and a template style can be assigned to specific menu items. If you are migrating an existing site, do not skip the preparation and troubleshooting steps. JoomlArt Space includes a quickstart package, the T3 Framework, JA Advanced Custom Module, and dedicated positions for hero, section-top, section-bottom, and off-canvas, so a problem in one place can easily look like "the template is broken" when the real issue is an unassigned module or the wrong style being used.

Below is the step-by-step logic: first what to check before installation, then how to choose between quickstart and manual installation, where to find the key settings, how to assemble the homepage, how to present projects using Joomla articles and custom fields, and how to test the mobile menu, cache, contact page, and other common trouble spots. At the end, you will find troubleshooting for frequent issues, an FAQ, alternatives, and a download link.

What Problem This Template Solves and Where It Actually Fits

The main strength of JA Space is that it gives you a fast start for a site where first impressions depend on visual rhythm, portfolio content, and a concise studio story. According to the official JoomlArt page, the template is designed for portfolios, agencies, corporate websites, and business sites. That is also clear from the demo reference: a large hero block, minimal top navigation, a dark visual scene, contrasting teal and coral accents, service cards, sections with circular images, and dedicated project, blog, and contact pages.

In practical terms, this means the template works best when the site needs to answer "who we are, what we do, what projects we have already completed, and how to contact us." It is less convenient if you need a catalog with dozens of filters, an online store with a cart, a learning platform, or a portal with many user roles. Joomla can handle those scenarios, but JA Space should not be forced into being a universal all-in-one solution. It works better as a visual framework for a presentation-focused website, with more complex business logic added through separate extensions only after compatibility has been checked.

Who this template is a good fit for:

• A design studio, agency, developer, photographer, or team that needs to showcase case studies and services.
• A small company where the homepage should quickly guide visitors to the portfolio, blog, and contact page.
• A webmaster who wants a ready-made quickstart package with a demo structure rather than an empty template with no examples.
• A project where dark/light styling, animation, responsiveness, and polished project presentation matter.

Who should think twice:

• Websites where the main workflow is a catalog, booking system, store, user account area, or advanced search.
• Teams that need a visual builder for every section without working with Joomla modules.
• Projects with strict requirements for a modern template framework if the current infrastructure already depends on another stack.
• Sites where the design needs to be as light and text-heavy as possible: a big part of JA Space's character comes from contrast and a large visual stage.

A simple rule of thumb works well here: if you can describe the future website in terms of a homepage, projects, blog, and contact page, the template is probably a good fit. If the structure starts with "we need user roles, filters, many content types, member areas, and integrations," JA Space can only serve as one design layer rather than the foundation of the entire system.

What to Check Before Installation

Before installing the template, you need to understand exactly what you are deploying: a new site with demo data or an existing site where the goal is to change the visual layer. The JA Space documentation describes two scenarios: quickstart for reproducing the demo, and manual installation for installing the template, T3 Framework, and related extensions on an already prepared Joomla site. Choosing the wrong scenario often creates unnecessary work.

Compatibility and Site Health Check

The JoomlArt product page lists JA Space as available for Joomla 4 and Joomla 5, and the changelog shows updates for newer Joomla branches. Older documentation also includes instructions for Joomla 3, because the template has been around for a long time. The safe approach is this: treat the product page and changelog as the current source of compatibility information, and use older documentation as a guide to the logic of T3 and the module structure if the Joomla interface in your version looks slightly different.

Check the following before installation:

• The Joomla and PHP versions on the server, along with the hosting requirements for the package you plan to use.
• Whether you have a backup of both the files and the database, especially if the site is already live.
• Whether there are old template overrides that may conflict with the new article output.
• Whether you understand which menus should use the JA Space style and which can stay on another template.
• Whether the site will be multilingual: menus, modules, and template styles are best planned before content migration begins.

Quick preflight check: if the site is already published, deploy a copy on a staging domain or locally first. The template changes more than colors. It also affects module positions, menu styling, article output, and homepage behavior.

Quickstart or Manual Installation

Quickstart is the right choice when you are building a new site and want a structure close to the demo. The JoomlArt documentation explains this directly: quickstart reproduces the demo site, after which you replace the content, images, menus, and contact details with your own. This is a good route for a studio that wants to see a realistic result quickly instead of building the hero, sections, and projects from scratch.

Manual installation makes more sense when the site already has articles, users, menus, SEO-friendly URLs, and extensions. In that case, you install T3 Framework, the JA Space template itself, JA Masthead, and JA Advanced Custom Module, then assign the template style and manually recreate the demo blocks you actually need. This path takes longer, but it is safer for a working site.

Backup and Staging Environment

A Joomla site consists of files and a database. That matters for any template: if you change only the files without preserving the database, you can lose articles, menus, module-to-menu assignments, and template style assignments. Before installation, back up both layers. For a typical site, the built-in hosting tool or a backup extension is usually enough, but do not just verify that the archive was created. Make sure the restore process actually works.

On a staging copy, it is useful to temporarily enable module position preview so you can see where hero, section-top, section-bottom, masthead, footer, and off-canvas are rendered. In Joomla, template position preview uses a dedicated template setting and a URL parameter. Once you finish checking, disable that feature on the live site.

Installation and Initial Verification Without Unnecessary Risk

Installing JA Space should not end with the message "package installed." It should end with a check that the site is actually using the correct template style, that T3 Framework is active, that modules are in the right positions, and that pages open without obvious visual breaks. In Joomla, page appearance depends on the menu item, which means one section can already be using JA Space while another still runs on the old style.

If You Are Using Quickstart

Quickstart deploys as a ready-made Joomla site with demo data. The general flow is similar to a normal Joomla installation: upload the package to the server, extract it, go through site and database configuration, select sample data, and remove or rename the installation folder. The JoomlArt documentation specifically calls out that final step as a security requirement. After installation, do not immediately start deleting demo articles. Study the structure first, because it shows how the template authors connect menus, modules, and positions.

1. Open the homepage and compare it to the demo reference: the hero, the "Nice to meet you" block, the service cards, the studio block, and the lower sections should all be present.
2. In the admin panel, check the list of template styles and confirm that the JA Space style is set as default or assigned to the correct menu items.
3. Open the module list and filter by the hero, section-top, section-bottom, and off-canvas positions.
4. Open the Projects, Blog, and Contact pages to confirm that they do not lead to empty articles.
5. Test the mobile menu: off-canvas should open, and the menu inside it should be published in the correct position.

Once you have done that check, you can start replacing the demo text. If you do it the other way around and mass-delete content first, you lose the built-in clues that make the template logic easier to understand.

If You Are Installing the Template Manually

With manual installation, first install and enable T3 Framework, then the JA Space template package, then the related extensions included in the bundle. The documentation lists JA Masthead Module and JA Advanced Custom Module. JA ACM is used for several homepage sections, so when that module is missing, the result often looks like an empty block on the frontend.

After installation, run a short check:

• T3 Framework is enabled in the extensions list and is not reporting an error.
• The JA Space template style is available in the site styles list.
• At least one test menu item uses the JA Space style.
• The navigation menu module is published in the position used by the main navigation, and a separate Menu module exists for off-canvas.
• Clearing the Joomla cache and browser cache does not produce random changes in the result. If it does, temporarily disable aggressive caching during setup.

First Test Menu Item

For a safe test, create a new menu item such as a Featured Articles or Single Article test page and assign the JA Space style to it. That lets you see how the template renders a standard article without changing the entire site. In Joomla, the style can be assigned either through the template styles list or directly in the menu item form. This is useful for a gradual transition: first one test page, then the homepage, then projects and the blog.

Configuring Template Styles, Theme, and Layout After Installation

Setting up JA Space happens on three levels: the template style in Joomla, the T3/JA Space parameters, and the modules that fill the template positions. If you only change one level, the result becomes unpredictable. For example, you can change the theme color and not see it on the page you expect because that menu item uses a different style. Or you can create a hero module and never see it because it was assigned to the wrong menu item.

Template Style as the Page Control Center

In Joomla, one template can have multiple styles. That is especially useful with JA Space because the official documentation mentions different homepage variations and two color directions. The practical approach is simple: do not try to make one style handle every scenario. Create a separate style for the homepage, another for projects if needed, and a separate test style for experiments. Then assign them to the appropriate menu items.

Minimal setup flow:

1. Open System -> Site Template Styles or the equivalent screen in your Joomla version.
2. Copy the JA Space style if you want to experiment without risking the current homepage.
3. In Menu Assignment, assign the style only to the menu items that should use it.
4. Open the frontend page and confirm that only the selected menu item has changed.
5. If you do not see the change, clear the cache and check whether a different style has been assigned directly in the menu item.

Theme Settings: Logo, Color Base, and Background

The JA Space documentation says that Theme Settings let you configure the theme color, the logo as either an image or text, and the background image for a template style. What matters here is that these settings do not have to be global for the entire site: different template styles can have different parameters. That is useful for a project where the homepage should feel dark and expressive, while the blog should look calmer and easier to read.

A better setup order looks like this:

• Upload the logo first and check how it looks on both dark and light backgrounds.
• Then choose the color base without immediately changing every module and CSS rule.
• After that, test the hero and the first sections: the heading, button, and body text should all remain readable.
• Only after the visual check should you transfer the settings to other template styles.

Do not start by editing the template files. First use the style, Theme Settings, modules, and a CSS file for safe customization. Editing the template core makes updates harder.

Layout and Responsive Configuration

JA Space uses a default layout, and the documentation describes two important levels: layout structure and responsive layout configuration. The first controls positions and spotlight blocks, while the second helps disable or resize positions for specific responsive modes. This is not cosmetic. If an important section disappears on mobile, the cause may not be a CSS bug at all, but a position disabled in the responsive settings.

Check the layout in this order:

1. Start with desktop: the hero, content area, section-top, section-bottom, and footer should all be visible.
2. Then test tablet width: cards should not collapse into each other, and large circular images should not overlap the text.
3. Then test mobile width: the off-canvas menu should open, CTA buttons should not run off the edge, and long headings should wrap cleanly.
4. After each change, clear the cache if caching is enabled.

The Homepage: How Demo Sections Turn Into a Real Working Site

The JA Space homepage is not one large page built entirely inside the article editor. The documentation shows that it is assembled from modules: the hero in the hero position, several JA ACM blocks in section-top, and the call-to-action block and clients in section-bottom. That is what makes the template flexible: you can replace one module without breaking the whole page. But it also creates a common mistake: users edit an article and nothing changes because the actual block is stored in a module.

Hero Block and Above-the-Fold Area

In the demo, the hero sets the tone of the site: a large background, a bold headline, a short text block, and a button. For a real project, it should answer three questions: who you are, what kind of work you do, and where the visitor should go next. Do not overload the first screen with a long service list. One strong statement, a short clarification, and a link to projects or contact usually works much better.

Practical hero check:

• The heading is readable against the background and does not break on mobile.
• The button points to a real menu item, not an empty #.
• The background image does not make the text unreadable.
• If animation is enabled, it does not interfere with the first interaction or delay visible content.

Services and Studio Sections

In the demo, you can see cards such as User Experience, Identity Design, and Content Strategy. On a real site, this area works better as a fast route into your services rather than a decorative list. Each card should lead either to a page where the service is explained in more detail or to projects that prove that expertise.

If you are using JA ACM, keep a consistent rhythm: a short heading, a clear icon, 2-3 lines of meaning, and a "More details" link. Do not put long sales copy inside the card. Visually, the template is built for breathing room and bold shapes, not dense paragraphs inside cards.

The "Let’s work together" Block and Lower Sections

The documentation shows a Custom HTML Module example for a CTA button. This is a good example of a place where you can safely replace the demo text with your own call to action: "Discuss a project," "View case studies," or "Request an estimate." The key is to connect the button to a real destination. If it leads to the contact page, verify the contact component itself and the Joomla mail settings.

Projects, Galleries, and Joomla Custom Fields

For a portfolio site, project pages are especially important in JA Space. The official page mentions a polished project page, grid layout, image gallery, and Joomla custom fields. The documentation adds that the project page is created through the menu and that project articles use category settings and extra fields. In practice, this means the portfolio is better built through a clear project category and repeatable fields rather than as a random set of unrelated articles.

Project Category and Fields

Create a separate category for projects. Then decide which attributes matter to visitors: client, industry, and year do not have to appear in the article if the date is not important, but you may want work type, team role, result link, service set, and gallery. Joomla fields let you store this data in a structured way, and JA Space uses it for the project specification. If a field is not assigned to the category, the editor may not see it when creating the article.

Working project flow:

1. Create a projects category.
2. Create or verify the field group for the project specification.
3. Add a project article to that category.
4. Fill in the fields, images, and main case-study text.
5. Create a project menu item or a project list and assign the JA Space style.
6. Check that the fields appear on the frontend and are not empty.

The Gallery as Proof of the Work

A project gallery should show stages of the work or the final result, not just fill a grid with attractive images. For a studio, that might mean "initial challenge," "interface screens," "brand applications," and "final page." For an architecture or interior project, it could be the overall view, details, layout, and final result. Structure the images so the visitor understands the work without needing a long explanation.

If the gallery does not switch properly or the thumbnails do not work, do not start with CSS. First check the article type, whether the images exist, whether the correct layout is loaded, the cache state, and JavaScript errors in the browser.

Navigation, Megamenu, and Off-Canvas Without Confusion

JA Space supports multiple menu systems: a megamenu on desktop and off-canvas navigation for mobile. The documentation states that the megamenu is enabled in the Navigation setting panel, while off-canvas requires both the option to be enabled and a separate Menu module in the off-canvas position. That is an important detail: if the mobile menu does not open or appears empty, the problem is often the menu module, not the template itself.

Megamenu for a Compact Structure

For an agency website, the megamenu should not turn into a catalog of every article on the site. Use it only where there is real hierarchy: services, project types, or blog content. If the site is small, a standard menu with items such as Home, Projects, Pages, Our Blog, and Contact Us is often better. The fewer items you place in the first screen, the more effective the visual character of the template becomes.

Off-Canvas for the Mobile Journey

The mobile menu should mirror the main navigation path, but without unnecessary items. Create a Menu module, assign it to the off-canvas position, and check its publication status, language, access level, and menu assignment. If the module is assigned to only one page, the mobile menu may open empty everywhere else.

Off-canvas checklist:

• The menu module is published.
• The position is exactly off-canvas, with no extra spaces.
• The module access is not restricted to a user group if the menu is supposed to be public.
• The menu assignment includes the required pages.
• Both the Joomla cache and browser cache have been cleared after changes.

Blog, Contact, and Utility Pages in a Consistent Style

JA Space is not only about the homepage and portfolio. The official page also mentions Blog and Contact pages, as well as styling for standard Joomla pages such as Contact, Search, Offline, 404, and others. That matters on a real website because visitors rarely move only through the polished first screen. They may open an article from search, land on the contact page, see a 404 page, or use internal search. If those pages look like they belong to a different site, trust drops much more sharply than it does from a minor mismatch in the hero section.

The Blog as Portfolio Support

For an agency, the blog does not have to be a news feed created just to increase the number of posts. It works better as an explanatory layer for the projects: breakdowns of challenges, design approach, technical notes, and answers to client questions. In the JA Space documentation, the blog page is created through a Category Blog menu item and the ja_space - Default style assignment. So first prepare the blog category, then create 3-5 starter articles, and only after that add the menu item to the public navigation.

Check the blog not only on the listing page but also on individual articles. The listing may look great while a single article reveals the real issues: images that are too wide, incorrect headings, missing alt text, an old override conflict, or weak contrast in blockquotes. If the blog is meant to support your expertise, each article should have a clear title, an intro image, a proper H2/H3 structure inside the content, and a link to a relevant project or contact page.

A Contact Page Without Demo Placeholders

The Contact page in JA Space is built through the standard Contacts component and a Single Contact menu item. In quickstart, such a page may already exist, but it should not be left as demo content. Check the contact name, address, map, email, phone number, contact form, consent text, and mail delivery. If the form does not send email, the issue may not be the template at all: check the global Joomla mail settings, hosting restrictions, captcha, system messages, and spam filters.

For a presentation-focused site, the contact page should resolve the question "what do I do next?" Add a short explanation of the inquiry format, the expected response, and the types of projects you take on. Do not promise an instant reply unless you can actually guarantee one. It is better to provide a clear next step: request a consultation, send a brief, write by email, or use the form.

404, Search, and Offline Page

Standard Joomla pages are often remembered only after launch. With JA Space, it is better to check them in advance, because the strong contrast of the template makes unfinished system pages especially obvious. Open a nonexistent URL, the search page, the login page, and the offline state on a staging copy. Make sure the logo, fonts, background, and buttons do not look like leftovers from the base template.

If a system page needs work, look for a Joomla or template style setting first. If the markup really needs to change, use an override. That approach is safer than editing component files directly. After making the change, always check updates: utility pages are rarely opened manually, and an error can go unnoticed for a long time.

Editorial Pass Before Publishing

Before launch, make a dedicated pass through the text content. The demo structure includes short English labels, temporary phrases, and placeholder links. They do a good job of showing the template rhythm, but they work poorly on a real site. Go through every module and article: hero, services, studio, mission, case studies, clients, footer, project articles, blog, and contact. For each block, answer four questions: why it exists, where it leads, what the visitor should understand, and how to verify the result.

The final sign of readiness is simple: you should be able to show the site to someone who has never seen the demo, and they should immediately understand the specialization, the examples of work, and the next step. If you still have to explain that "projects will be added later" or "this button does not go anywhere yet," publication should wait.

Practical Example: Building a Studio Homepage

Imagine you need to launch a website for a small design studio. The goal is a homepage with a strong hero section, three services, an about-the-studio block, a link to projects, and a working contact page. This example does not rely on invented features. It is based on the JA Space demo structure, modules, template styles, positions, and standard Joomla logic.

Goal

Create a homepage where the visitor understands the studio's specialization within the first screen, can move to the projects, and sees that the site is not just an empty demo. In the admin panel, the modules should be clear enough that an editor can update them without editing template files.

Preparation

• JA Space, T3 Framework, and the required JA modules are installed.
• A template style for the homepage has been created or selected.
• There is a Main Menu with Home, Projects, Blog, and Contact items.
• There is a Projects category and at least one test project article.
• Aggressive page cache is temporarily disabled during setup, or there is a fast way to clear the cache.

Steps

1. Create a Home menu item of type Featured Articles, or use the demo item if the site was deployed via quickstart.
2. Assign the ja_space - Default template style to that item, or use a copied version for the homepage.
3. Set up the hero module in the hero position: heading, short subheading, and a link to Projects or Contact.
4. In the section-top position, keep 2-3 meaningful blocks: services, mission, and about the studio. Remove sections that are not needed for the first launch.
5. In the section-bottom position, add a call to action and, if you have real client logos, a clients block.
6. Create the Projects page through a Single Article menu item or a suitable article list, as described in the documentation for the project page.
7. Open Contact through the Contacts component and verify that the form works with your Joomla mail configuration.

Checking the Result

Open the homepage in a private browser window. Is the hero visible? Does the button go where it promises? Do the sections appear in the correct order? Does the mobile menu work? If you open a project, do the images and fields appear? If you fill out the contact form, does the email arrive or at least submit without an error?

A Common Detail That Gets in the Way

If you edit a module but nothing changes on the frontend, check three things: the module's page assignment, the module position, and the cache. In Joomla, a module can be published and still not appear on the current menu item. This is especially important on the JA Space homepage, where the sections are modules rather than parts of a single article.

Practical Ways to Use JoomlArt Space

JA Space does not have to remain a copy of the design-studio demo. It can be adapted for different presentation-oriented scenarios as long as you do not break the core logic: the homepage as a showcase, projects as proof of experience, the blog as a source of authority, and contact as the next step. Below are ideas based on the template's confirmed features and standard Joomla practice.

Agency Website With Service-Based Case Studies

Use the section cards as entry points into services: branding, development, content, support. In projects, create fields such as "work type" and "team role" so the case studies explain not only the result but also the studio's contribution. The check is simple: each service should lead to 2-3 relevant projects.

Freelancer or Small-Team Portfolio

Use fewer modules on the homepage, but make the project page stronger. In the hero, state the specialization. In section-top, show 2-3 focus areas. In the blog, publish solution breakdowns. For a freelancer, trust matters more than effects: real work images, clear case studies, contact details, and no leftover demo placeholders.

Corporate Showcase Without a Complex Catalog

If the company sells services rather than products, JA Space can work well as a compact corporate site: homepage, services, projects, blog, and contact. In this scenario, do not overload the megamenu. Clear menu items and homepage blocks used as navigation bridges usually work better.

Landing Page for a Separate Service Line

Create a separate template style and assign it to a single menu item. That style can have its own logo, background, color theme, and module set. This is useful if the studio has a dedicated service or campaign. Just make sure changes to that style do not affect the main site.

Checking the Result: Design, Speed, SEO, and Usability

After setting up the template, do not stop at a visual comparison with the demo. The demo shows the potential, but a working site needs a technical review as well: menus, modules, contact forms, responsiveness, cache, metadata, 404 pages, and accessibility. Pay extra attention to pages that do not look like the homepage: blog, contact, search, offline, and project article pages. The official JA Space page says that default Joomla pages are styled to match the template, but your content and extensions can still create inconsistencies.

Visual Check

• There is no demo text left in the hero, cards, buttons, or footer.
• More details links and CTAs go to real pages.
• Project images have a consistent visual quality and do not stretch.
• There is no horizontal scrolling on mobile.
• Text contrast on the dark background is strong enough for comfortable reading.

Technical Check

• The template style is assigned to all required menu items.
• Modules in the hero, section-top, section-bottom, and off-canvas positions are published and use the correct access settings.
• The cache clears after changes, and page cache does not keep showing an outdated version of the page.
• The contact form works with your Joomla mail configuration.
• The project page displays fields and the gallery rather than empty labels.

SEO Check Without Overpromising

The template itself does not guarantee better rankings. It helps with visual structure, responsiveness, and ready-made page layouts, but SEO still depends on content, speed, internal linking, metadata, indexation, and page quality. With JA Space, it is worth checking article titles, meta descriptions, readable URLs, alt text for project images, the contact page, and the correctness of the 404 page. The JoomlArt changelog has included fixes related to structured data and the contact page, so after updates, it is worth revisiting those specific areas.

Safe Improvements Without Editing the Template Core

After installation, it is common to want quick adjustments such as spacing, button color, CTA appearance, or a small card detail. Do not edit the Joomla core, T3 Framework, or the template source files unless there is no other option. The T3 documentation specifically describes the path of using custom CSS: such a file is loaded last and should not disappear during LESS compilation as long as you are not editing the compiled CSS directly. For JA Space, the exact path may vary depending on the package, but the practical logic is the same: use custom CSS or a safe override instead of editing system files directly.

A Small CSS Tweak for a CTA Module

Suppose you added a Custom HTML Module to the lower section and want to make the button a bit more noticeable. Add your own class to the module container or to the HTML inside the module, for example space-cta-clean. Then add CSS to the template's custom file that loads after the main styles. This is safer than changing the template's built-in CSS.

.space-cta-clean .btn,
.space-cta-clean .btn-primary {
  border-radius: 28px;
  padding: 12px 26px;
  font-weight: 700;
  letter-spacing: 0;
}

.space-cta-clean .btn:hover,
.space-cta-clean .btn-primary:hover {
  transform: translateY(-1px);
}

Check the result by opening the page with the CTA, refreshing the cache, and confirming that only the intended block changed. To roll back, remove the class from the module or delete the CSS snippet. This change does not depend on hidden JA Space APIs and does not require modifying the template core.

When You Need a Template Override

If you need to change the output structure of an article, contact page, or module, use a Joomla template override. Joomla documentation makes it clear that extension source files should not be edited, because updates may overwrite them. An override is appropriate for targeted HTML output changes, but it requires a real understanding of PHP and Joomla structure. If CSS can solve the problem, do not create an override for one minor visual detail.

Why JA Space May Display Incorrectly and How to Check It

Most Joomla template issues are not caused by "broken design" but by the combination of template style, menu assignment, module position, cache, and a missing extension. Below is a troubleshooting map for JA Space and similar T3-based templates.

The Homepage Is Empty or Does Not Resemble the Demo

Symptom: the template is installed, but instead of demo sections you see a standard article or an almost empty page. A likely cause is that you used manual installation and did not create the demo homepage modules, or the Home page is using a different template style.

What to check: the Home menu item, the assigned style, whether JA ACM is installed, the modules in the hero, section-top, and section-bottom positions, and the menu assignment for those modules. Fix: assign the JA Space style to the homepage, publish the required modules, and clear the cache. If you expected a full demo copy, use quickstart on a clean site or manually recreate the demo structure.

The Module Is Published but Not Visible

In Joomla, a module must match several conditions at once: position, publication state, access level, language, and menu assignment. For JA Space, the hero, section-top, section-bottom, and off-canvas positions are especially important. If the module is assigned to "Only on the pages selected" but the current menu item is not included, it will not appear.

The Mobile Menu Opens Empty

Check whether a Menu module has been created for the off-canvas position. In the JA Space documentation, off-canvas is enabled in the Add-ons settings, but that alone is not enough: you also need a published menu module in the matching position. Also verify Public access and assignment to all required pages.

Style Changes Do Not Appear After Saving

There are usually three causes: you are editing the wrong template style, caching is enabled, or the custom CSS is not connected or stored in the wrong location. Start by checking the page in a private window, then clear the Joomla cache, then confirm that the menu item is using the exact style you edited. If the change was made in compiled CSS, it may disappear after LESS recompilation.

Project Fields Do Not Appear on the Page

Joomla fields must be created, assigned to the correct category, and filled in inside the article. If a field is empty, it may not render at all. If the project article is stored in the wrong category, the editor may not show the required fields. Check the category setting, field group, and the article layout itself.

The Contact Page Does Not Work

The JA Space changelog has included a contact page fix, so if you run into problems, first verify that you are using the current package. Then check the Contacts component, the Single Contact menu item, the template style, the Joomla mail settings, and the system messages shown when the form is submitted. If everything works on the staging copy but not on the live site, compare cache settings, mail transport, and overrides.

When JoomlArt Space Is the Right Choice

JoomlArt Space is worth using when you need a visually expressive Joomla template for an agency, studio, portfolio, or a small corporate showcase. It is especially strong if you are comfortable working with Joomla logic: template styles, menus, modules, positions, custom fields, and cache. In that case, the template stops feeling like a "closed design" and becomes a clear system: one style controls the page, modules fill the sections, fields structure the projects, and T3 provides layout and theme settings.

If the scope is broader, such as a store, a complex catalog, member areas, many roles, and multiple integrations, first check whether a different base template or builder would be a better fit. JA Space can still be used for presentation-focused pages, but it should not be forced to solve problems it was not designed for.

Before launching the final version, run one short check: the backup exists, demo text has been replaced, the homepage is built from understandable modules, projects use a category and fields, the off-canvas menu works, the contact page has been tested, the cache has been cleared, and the template style is assigned to the correct menu items. After that, you can get the Joomla version and safely test it on a site copy or a clean installation.