JoomlArt Aiga - Joomla Template

A Setup Guide to JoomlArt Aiga for a Joomla Site

JoomlArt Aiga is best approached not as a finished picture you can simply switch on, but as a set of connected solutions for a Joomla site: the template, T3 Framework, JA ACM modules, menus, template styles, and page layouts for different content scenarios. In this guide, we will walk through how to handle the installation without chaos, which settings to check first, how to build the homepage, where to look if a module or layout does not appear, and when the template is actually a good fit for the job.

This guide is aimed at a site owner, webmaster, or Joomla administrator who already understands the basic sections of the admin panel but wants to turn a demo template into a working site: a magazine, model portfolio, fashion blog, editorial showcase, or an image-focused agency page. This is not a repeat of the product sales page. The main focus is on practical JoomlArt Aiga setup after installation and verifying the result on the live front end of the site.

We will also pay special attention to the areas where Joomla templates most often break down: a mismatch between the template style and the menu item, the wrong module position, a missing menu assignment, a cache conflict, a disabled T3 plugin, unprepared images, and copying the demo structure too literally onto a site with completely different content.

What the Template Does and Where It Works Best

JA Aiga is built around visual content. Its strength is not a strict corporate landing page, but pages where imagery, headlines, and the rhythm of sections matter more than a dense reference-style layout. On the official template page, it is positioned as a multipurpose solution for models, fashion projects, portfolios, and blogs. That comes through clearly in the demo: a dark header, a large slider, magazine-style cards, a strong focus on photography, high-contrast grids, and dedicated page variants for models, blog content, and articles.

That is why the first question before installation is simple: what kind of site are you trying to build? If you need a fashion blog, a magazine with curated collections, an agency portfolio, a model directory, an editorial page, or a brand-focused site built around strong photography, JoomlArt Aiga gives you a solid foundation. If, on the other hand, you need a complex store, a member account area, a knowledge base with hundreds of utility tables, or a site where the design should be almost invisible, it is worth evaluating early whether the template will require too much rework.

An important thing to understand about Aiga is that it does not run on template settings alone. The demo pages are assembled through Joomla menus, articles, categories, JA Advanced Custom Module, and module positions. That means the visual result depends on several layers at once: the active template style, the menu item type, the assigned modules, the category parameters, and the content inside the articles. If even one layer is set incorrectly, the page can look empty even though the template itself is installed correctly.

Who This Template Is For

Aiga works best where the editor is ready to work with images, categories, and modules as a publishing system rather than just dropping text into a single page. Good use cases include:

• A model agency site with model profiles, curated collections, an about page, and contact details.
• A fashion magazine or blog where the homepage needs to display different content streams and visual collections.
• A portfolio for a photographer, stylist, creative studio, or editorial team.
• A brand image site where atmosphere, large photos, and clean navigation matter.

When Another Solution May Be Better

The template may be unnecessary if you want an extremely simple site with just a few text pages and no module-based setup. It is also not the best starting point for a project where every block needs to be edited visually with the mouse inside a dedicated builder. Aiga relies on the Joomla approach: articles, menus, categories, modules, and template styles. That gives you control, but it also requires discipline.

A quick check before choosing: if you are ready to build the site structure through categories, menu items, and modules, Aiga works very well. If you need a builder where you can drag sections around visually without understanding Joomla's layers, it is better to look at templates and frameworks with a more pronounced visual editor.

What to Check Before Installation and Demo Import

Preparation matters more than the install button itself. JoomlArt templates typically come with several packages: quickstart, the template itself, T3 Framework, JA ACM, JA Extension Manager, and additional modules. Problems usually happen not because the archive is "bad," but because the administrator installs only the template and expects a full demo site, even though the demo also depends on modules, content, and configured menus.

Choose Your Installation Method

There are two standard paths. Quickstart deploys a site similar to the demo, complete with Joomla, the template, extensions, and demo data. That is convenient for a new project or a local sandbox. Manual installation is better for an existing site where you cannot replace all current content. In that case, you install T3 Framework, the JA Aiga template, the required JA extensions, and build the pages manually.

A safer workflow for a live site looks like this: first make a copy on staging or a local server, then install and configure everything there, and only after that move over the verified changes. Do not deploy quickstart over a production site unless you are prepared to lose the existing structure.

Check the Dependencies

Before installation, make sure you have:

• A compatible package for your Joomla branch.
• T3 Framework enabled, because the template is built on it.
• JA Advanced Custom Module if you want to recreate the demo sections and homepage variants.
• Administrator access to menus, modules, templates, categories, and contacts.
• A backup of the files and database before any update or migration.

JoomlArt documentation specifically points out that quickstart is meant to replicate the demo, while manual installation requires T3 Framework and supported extensions. So at the beginning, it is better to decide what exactly you are setting up: "a site like the demo" or "an existing site with a new visual layer."

Prepare Images and Categories

Aiga will not rescue weak imagery. The demo works because it uses strong large portraits, fashion photography, editorial-style visuals, high-contrast cards, and clean previews. If you replace those with random small images, the grid will immediately feel loose and uneven. Before you start configuring the site, create a few test articles with solid images, categories, and short intro text. That way, you will be testing a real future scenario rather than an abstract template.

Installation: Quickstart or Manual Build

Installing JoomlArt Aiga depends on whether you are starting a new site or adding the template to an existing Joomla installation. These two scenarios should not be mixed unless you clearly understand the consequences. Quickstart deploys a complete starter site, while manual installation adds the template and its dependencies to an existing Joomla setup.

Quickstart for a New Project

Quickstart is useful when you want the demo structure first and plan to replace the content afterward. The general sequence is:

1. Create a clean database and a separate site folder or local virtual host.
2. Upload the quickstart package that matches your Joomla branch.
3. Go through the standard Joomla installation wizard: site name, administrator account, and database settings.
4. At the demo data step, choose the option recommended in the package documentation.
5. After installation, delete or rename the installation folder.
6. Open the front end and the admin panel to make sure the demo pages, modules, and template style loaded correctly.

After quickstart, do not rush to delete the demo modules. First, study which sections are responsible for the hero area, cards, blog, models, contacts, and footer. If you remove a module before you understand its role, rebuilding the page structure later will be much harder.

Manual Installation on an Existing Site

Manual installation starts with the dependencies. In the admin panel, install T3 Framework first, then the JA Aiga template itself, then JA ACM and any other extensions from the package that your scenario actually needs. After installation, assign the template style as the default or bind it to specific menu items.

In Joomla, a page's appearance is often determined by the active menu item. So the situation where "the template is installed, but the page still looks the same" usually means the correct template style is not assigned to that menu item, or the site is still using the old default style.

Initial Check After Installation

After installation, do not judge the template based only on the homepage. Check the following:

• Whether the list of template styles opens and the JA Aiga style is visible there.
• Whether the T3 system plugin is enabled.
• Whether JA ACM appears in the list of modules.
• Whether the style is assigned to the correct menu item.
• Whether any PHP errors appear in the admin panel when opening the template settings.
• Whether at least one simple Joomla page renders with the selected style.

If these checks pass, the template is installed. From that point on, the issue is no longer installation, but the build of a specific page: menus, modules, categories, layout, cache, or content.

The Post-Install Settings Map: What to Change First

Configuring JA Aiga should move from general to specific. Start with the active template style, the theme, and the logo. Then move on to layout and responsive behavior. After that, deal with navigation, off-canvas, modules, and pages. If you begin with a small CSS tweak before you even know which style and menu item are in use, it is very easy to fix the wrong page.

Template Style and Menu Assignment

In Joomla, a template style can be assigned to all pages or only to individual menu items. For Aiga, this is especially important because different sections can use the same template but different settings. For example, the homepage can run on a dark variant, while an informational page can use a light variant if you create a separate style and assign it to the relevant menu item.

A practical order looks like this:

1. Open the site styles list in the Joomla admin panel.
2. Find the JA Aiga style and make a copy for testing.
3. Rename the copy based on its purpose, for example, "Aiga - Home dark" or "Aiga - Blog light."
4. Assign the style to a specific menu item.
5. Save it and open that page in a private browser window.

This way, you do not damage the base style and you always have an easy rollback path: just reassign the menu item to the previous template style.

Theme: Dark and Light Variants

The Aiga documentation refers to dark and light themes. This is not just a cosmetic toggle. The dark theme works better for a magazine-style homepage, large photography, and high-contrast cards. The light theme is often more comfortable for About pages, contact pages, long-form text, and article-heavy pages where calm readability matters.

Do not choose the theme based only on the administrator's personal taste. Open a test page with real images, headings, and text. If the photos are already dark, a dark wrapper can make the whole page feel heavy. If the content consists of large text blocks, the light variant is usually easier to read.

Layout and Responsive Configuration

Aiga uses one default base layout, but T3 lets you assign a layout to a style and configure the section structure. The documentation refers to layout structure and responsive layout configuration. In practice, that means you can control which module areas are used on the page and how they behave at different widths.

Do not change the layout until you understand what each section is for. First enable preview module positions in Joomla, then see where hero, section-top, spotlight, footer, and off-canvas are located. After that, change only the block you actually need. A correct layout setup is always verified on the front end, not just in the admin panel.

Logo, Background, and Basic Brand Identity

Theme settings in T3 let you configure the color theme, logo, and background. In Aiga, the logo stands out in particular because the header is minimal and dark. Prepare two logo versions: a light one for the dark header and, if you use light pages, a contrasting one for the light style. Avoid using a logo that is too tall, because it can break the vertical rhythm of the menu and hero block.

Homepage and Layout Variants: How Not to Get Lost in the Demo

One of JA Aiga's strengths is its set of different homepage variants. Official sources mention several homepage options: split, columns, minimal, magazine, and classic combinations. But this is also where administrators often go wrong: they see many attractive demos and try to transfer everything at once. It is much better to choose one primary scenario and build it well.

Home Default for a Versatile Starting Point

The Default variant works well when you want to show a large visual block first, then several editorial sections, and then a list of articles below. For a first launch, this is the calmest path because there is less risk that a complex nonstandard grid will demand too much content right away.

Home Split for a Brand-Driven Homepage

Split pages work well for a portfolio, a model agency, and visual projects where the hero screen should feel like a magazine cover. But this layout is demanding when it comes to imagery. If the photos are inconsistent, the split grid quickly starts to feel random. Use a consistent treatment, similar contrast, and intentional cropping.

Home Magazine for a Content Project

The Magazine variant makes sense for a blog or magazine. It depends more heavily on categories, display order, and article modules. Here it helps to plan the section structure in advance: news, lookbook, editorial, interviews, reviews. Then the modules will output meaningful collections instead of random latest posts.

Why Demo Modules May Have the Position NOT USED

In the Aiga documentation, some JA ACM modules for demo pages are marked with the position NOT USED. That is not an error. Some sections are loaded inside an article through the module-loading mechanism rather than directly through a template position. So if you are searching for the module in the hero position and cannot find it, check the article content and the module identifiers.

If a page "like the demo" is not coming together, do not check only the module position. Look at the menu item type, the assigned template style, the article text, load module tags, module status, and module-to-menu assignment.

Models, Blog, and Articles: Which Pages Matter Most in Aiga

What sets JA Aiga apart from a generic template is that it has clearly developed pages for model portfolios, blog grids, and article variations. That does not mean every site has to use every variant. But it is useful to understand which page types form the core of the template.

The Models Page

The documentation describes the Models List page as a menu item of the Articles type with its own menu layout parameters. For a model agency, this is a key section: the visitor should be able to see people quickly, move into a profile, compare the visual style, and never get lost in navigation. It is important to prepare the category, images, short descriptions, and extra fields in advance if your version of the template uses them.

One practical detail: if the models page looks like a regular article list, check not only the category but also the selected menu type, the layout in the menu parameters, and the assigned template style. In Aiga, pages like this depend on a combination of Joomla settings.

Blog Layouts

For the blog, Aiga offers several visual approaches: grid, list, sidebar variants, centered, minimal, mix content, and masonry. The right choice depends on the content itself. If your articles rely on strong imagery, grid or masonry often works well. If the posts are long and readers need to pick an article quickly by headline, a list format may be more useful. A sidebar makes sense only when it contains blocks that actually help: popular posts, tags, login, categories.

Article Variations

Dedicated article variants matter for an editorial project. On an article page, three things need to align: a strong lead image, readable text, and clear navigation to the next piece. If the article page looks broken, check the article parameters, intro/full image, category settings, and enabled plugins. The Aiga changelog shows that some fixes affected contacts, the article page, and module positions, so if you are working with an older package, it is especially important to update the template and its dependencies on a test copy first.

Navigation, Megamenu, and Off-canvas

Navigation in Aiga is built around Joomla menus and T3 features. In the template structure, it is not a separate "magic" panel, but a combination of menu items, template style, Megamenu, and off-canvas positions. When everything is configured carefully, the user gets a clear desktop header and usable mobile navigation. If not, some items may disappear, duplicate, or show up in the wrong place.

Megamenu for Large Sections

Megamenu is worth enabling when the site has several major sections: Models, Blog, About, Contact, magazine categories, portfolio. In T3 settings, you can enable Megamenu, choose the menu, and open the configuration. Do not overload the dropdown with decorative blocks. For Aiga, it is better to keep the structure clean: major sections, one or two levels of nesting, short labels, and logical grouping.

What to Check After Enabling Megamenu

• The menu item opens correctly on the front end and leads to the intended section.
• The dropdown does not overlap the hero slider incorrectly.
• At narrow widths, the menu does not appear twice as both collapse and off-canvas if you selected one primary mobile pattern.
• On a multilingual site, each language has its own menu and template style if required.

Off-canvas for Mobile Navigation

The Aiga documentation describes enabling off-canvas through Add-ons settings and creating a Menu module in the off-canvas position. This is a common failure point: the administrator enables off-canvas but never assigns a menu module to that position. As a result, the button appears, but the panel is empty.

The check is simple: create or open a menu module, assign it to the off-canvas position, publish it, set the menu assignment, and save. Then open the site on a narrow screen or through your browser's developer tools. If the menu is still empty, clear the Joomla cache and the browser cache, then check whether the module is restricted to a specific menu item.

The Aiga Content Model: Articles, Categories, Modules, and Positions

If you want a JA Aiga site to stay intact after the first round of edits, you need to understand in advance where each content fragment actually lives. In a typical landing page, an editor often thinks in blocks: "top screen," "three cards," "form." In a Joomla template, that picture breaks into entities: an article stores the text and images, a category groups content, a menu item defines the page type, a module outputs an extra block, a template style changes the visual shell, and a position determines where the module appears. Aiga uses this model heavily, so chaotic editing of the demo quickly leads to empty areas and duplicated sections.

For a working project, it is better to create a short content map before you start deleting demo content in bulk. That is not bureaucracy, it is protection: you will know which block can be replaced with text, which depends on a category, and which is better left alone until the menu setup is done.

This table helps prevent a typical mistake: the editor changes an article even though the block is actually a module; the administrator changes a module even though the page opens through a different menu item; the developer edits CSS even though the real issue is the wrong template style. With Aiga, you almost always need to identify the owner of a block first and only then change how it looks.

How to Prepare Categories for a Magazine

If the site is being built as a fashion magazine, the categories should reflect the editorial logic rather than just the demo structure. Create sections that will actually be updated over time: Cover, Lookbook, Editorials, Interviews, News, or their localized equivalents. For each section, check the intro image, full image, alias, and article order. Then configure the modules so they pull content from the correct categories rather than from one generic "Blog" bucket.

A good test is to remove one test article from the selection or move it into another category. If the module reacts as expected, the link is configured correctly. If nothing changes on the page, you are looking at the wrong module or the wrong content source.

How Not to Break the Models Page

For the model section, consistency matters: similar photography, short names or titles, clean teaser text, and a clear path to the detail page. Do not turn Models into a generic blog. Even if it is technically built on Joomla articles, the user experiences it as a people directory or portfolio. That means every card should feel visually comparable to the ones around it.

If the project does not have real model profiles, the section can be reinterpreted: it can become a directory of authors, team members, stylists, collections, or shoots. But if you do that, rename the menu, categories, and text so the site does not retain demo leftovers. In particular, check image alts, breadcrumbs, page title, and links inside the Megamenu.

How to Handle Editorial Changes After Launch

Once the site is live, agree on a simple workflow. The editor creates content, selects a category, adds images in the proper size, and checks the card on a test page. The administrator changes modules, layout, and template styles. The developer handles overrides and CSS. If everyone edits everything at once, within a few weeks nobody understands why the hero is pulling an old article, the sidebar is empty, or the mobile menu is showing the wrong section.

For a smaller site, a simple text change log is enough: the date does not need to appear in the site article itself, but inside the internal project files it is useful to note which module was changed, which category was connected, and which style was assigned. That speeds up troubleshooting after updates and helps move settings safely between staging and production.

The Minimum Editorial Set for the First Launch

You do not need to fill the entire site before publishing a test version. It is enough to prepare one strong set that validates all the key Aiga mechanisms: a homepage with a hero block, one blog category with several posts, one model or portfolio page, an About page, and a Contact page. That set shows how images, cards, menus, module positions, the article template, and the contact page behave.

After that, you can expand the structure gradually. Add a new category and check whether it appears in the menu and modules. Add a new card type and check image cropping and title behavior. Create a copy of a template style and make sure it is assigned only to the menu items it was intended for. This pace is slower than bulk-copying the demo, but it keeps the site manageable and makes it easier to maintain after updates. That matters especially with a visual template: one bad change in the content source can be more visible than an error in a plain text-oriented theme.

Practical Example: Building a Homepage for a Fashion Blog

Let us walk through a scenario that fits JoomlArt Aiga well: a fashion blog homepage with a large hero block, cards for current content, a path into the blog, and basic navigation. This is not the only way to use it, but it clearly shows the template's logic: the menu defines the page, the template style defines the look, and the modules and articles fill the sections.

Goal

The goal is to create a homepage that feels like a magazine entrance: a dark header with the menu at the top, then a large visual block, followed by a curated set of articles and links into the main sections. The user should immediately understand the tone of the project and be able to move to Models, Blog, or Contact.

Preparation

• T3 Framework is installed and enabled.
• The JA Aiga template and the required JA modules are installed.
• Categories for the content are created, for example Lookbook, Cover, and Editorials.
• Several test articles with large images have been added.
• A copy of the template style has been created for experimentation.

Steps

1. Create the homepage menu item. For a content-stream variant, use the type that matches the selected demo scenario: Featured Articles, Blog List, or Single Article with loaded modules.
2. Assign a JA Aiga style to that menu item, for example ja_aiga - Default or your own copied version.
3. Open the template style and choose the right theme: dark for a magazine-cover effect or light for a calmer page.
4. Create or configure the hero module. If you are using JA ACM, choose the content type, images, titles, and links.
5. Assign the module to the position specified in the documentation for the selected home variant, or load it through the article if that scenario works through a module id.
6. Add blocks with recent content: categories, order, quantity, images, and intro text.
7. Configure the menu: Home, Models, About Us, Blog, Contact. For major sections, check Megamenu; for the mobile scenario, check off-canvas.
8. Clear the cache and open the front-end page in a private browser window.

Verification

After saving, do not check only whether it "looks nice." Check for specific signs:

• The homepage is using the correct template style.
• The hero block renders in the correct position and does not overlap the menu.
• The content cards pull images from the correct articles or categories.
• Card links open the correct articles.
• At smaller widths, the menu remains usable and the cards do not become too narrow.
• If you disable the test module, the page does not collapse and only loses the corresponding section.

A Common Detail That Gets in the Way

If a demo section does not appear, do not rush to reinstall the template. In Aiga, it is common for a module to be published but not assigned to the right menu, assigned to the wrong place, loaded from an article through a different id, or hidden by cache. Troubleshooting should move from the menu item to the template style, then to the module, and only after that to the code.

Practical Use Ideas Without Rebuilding the Template from Scratch

Aiga does not need to be used only as a copy of the demo. It is far more useful to take the finished visual system and adapt it to clear editorial scenarios. Below are ideas based on confirmed template capabilities: homepage variants, model pages, blog layouts, article pages, modules, dark/light themes, and navigation.

Model Agency

Use Models List as the central section. The homepage shows a hero and several featured profiles, Models leads to the list, About explains the agency, and Contact contains the contact form. The result is successful if a visitor can get from the homepage to a model profile in one or two clicks, and the menu does not hide the main path on mobile widths.

Fashion Magazine

Choose a magazine or grid-oriented variant. Create sections, configure content output modules, and use different blog layouts for different areas of the site. For example, the homepage can show fresh covers and curated collections, while the Editorials section opens as a category blog. Verification: the cards pull the correct images, the article order matches the editorial logic, and the sidebar does not overload the reading experience.

Photographer or Stylist Portfolio

Minimal home variants and large imagery work well for a visual portfolio. What matters here is not the number of sections, but the rhythm: one strong hero, a collection of works, a short about block, and contacts. If the blog is not needed, do not leave it in the menu just because it exists in the demo.

Brand Page with Editorial Stories

For a brand, you can combine About, Blog, and Contact, and replace Models with a collections page or a team page if the content structure supports that. The main thing is not to promise store functionality unless you are adding a separate e-commerce component. Aiga itself handles the template and content output, not the cart, payments, or inventory.

Verifying the Result: Design, Responsiveness, Speed, and SEO

Once the homepage and key sections are assembled, the next stage is just as important: verification. With a Joomla template, the result is not finished simply because the page opens. You need to make sure the content is readable, modules load where they should, navigation works across screen sizes, and technical settings do not interfere with indexing or performance.

Design Check

Open the homepage, Models, Blog, one article page, About, and Contact. On each page, review the following:

• Whether there is a clear first screen.
• Whether important faces in photos are being cropped.
• Whether card titles are too long.
• Whether a consistent style is maintained between dark and light pages.
• Whether modules are duplicated in the sidebar and the main area.

Responsive Check

T3 and Bootstrap provide the foundation for responsiveness, but the actual result depends on the images, headings, modules, and layout settings. Check the page at several widths. Pay special attention to the hero block, menu/off-canvas, article cards, and the contact page. If an image becomes too tall or an important object is cropped, it is better to prepare a different image than to break the CSS trying to force it.

Performance Check

For a visual template, the main risk is heavy photography and unnecessary modules. Optimize images before upload, do not place too many large cards on the homepage, and disable demo modules you are not using. T3 includes CSS and JS optimization settings, but it is better to enable them only after the design has been checked. If enabling optimization causes an animated block to disappear or the menu to stop working, roll the setting back and check for a script conflict.

SEO Check Without Promises

The template alone does not guarantee ranking gains. But it can help present content cleanly if you configure article headings, alias, menus, metadata, images, and internal links correctly. For an editorial site, it is especially important to have solid article titles, readable intro text, image alts, and a logical category structure.

Safe Improvements and Careful Customization

It makes sense to customize Aiga visually, but it is better to do it in a way that does not turn template updates into repair work. The T3 documentation warns that compiled CSS files may be overwritten when LESS is recompiled. So for small changes, it is safer to use the template's custom CSS file or the built-in Theme/ThemeMagic settings, if they are available in your version.

When Settings Are Enough

Do not write CSS if the task can be solved through the template style, Theme, logo, background, layout, module suffix, or module parameters. For example, a light contact page is better handled through a separate style and menu assignment than through a pile of CSS exceptions layered on top of the dark theme.

A Small CSS Tweak Through a Custom Suffix

If you need to highlight one JA ACM block slightly, it is safer to assign a custom suffix to that module and write CSS for it than to modify the template's global classes. The example below does not rely on any hidden Aiga API: you add the suffix to the module yourself and then describe the appearance. The proper place for it is the template's custom CSS file, which should not be overwritten during compilation.

.aiga-feature-focus {
  padding-top: 32px;
  padding-bottom: 32px;
}

.aiga-feature-focus .module-title {
  letter-spacing: 0;
  text-transform: none;
}

.aiga-feature-focus img {
  object-fit: cover;
}

Verification: assign the suffix to only one test module, clear the cache, and compare the page before and after. Rollback: remove the suffix from the module or delete the CSS block. Do not change Joomla, T3, or JA Aiga core files for a minor tweak like this.

Overrides and Updates

A template override makes sense when you need to change the HTML output of a Joomla component or module rather than just color and spacing. But with Aiga, first check whether an override already exists inside the template. If it does, copy it and document the change in version control or at least in the project's notes file. After a template update, compare the changed files through JA Extension Manager or another safe method.

When JoomlArt Aiga Is a Good Choice

JoomlArt Aiga is worth using if you want to build a visual Joomla site with an editorial feel: large imagery, models, a fashion blog, magazine-style collections, a portfolio, or a brand-focused page. The template is especially strong when you are ready to work with the Joomla system itself: menu items, categories, modules, template styles, and T3 settings.

Before launch, verify that the package is compatible with your Joomla branch, install the dependencies, build the page on a test copy, configure the template style, and make sure the result works on your primary devices. If the scenario matches the needs of the project after that, you can download JoomlArt Aiga and move on to assembling the site carefully.

If, however, you need a visual builder without understanding modules, a store out of the box, or an extremely neutral corporate theme, it is better to compare Aiga with alternatives first. The right choice here is not which template looks better in the demo, but which template is easier to turn into a maintainable working site.