YOOtheme Lilian - Joomla Template

A Guide to Setting Up YOOtheme Lilian for a Joomla Event Website

YOOtheme Lilian should not be treated as just another design archive you enable and forget about. It works better as a ready-made visual foundation for a Joomla event website. In this guide, we will look at how to approach the template after installation: which setup path to choose, where to customize the look and feel, how to adapt the demo logic to a real project, and how to verify that the site still holds together after you replace the text, menus, and images.

This material does not repeat the short description from the product page. The practical side matters more here: how to use Lilian's wedding and event layouts, how quickstart differs from installing on an existing site, which YOOtheme Pro panels matter first, why menus and modules in Joomla often become the source of errors, and how to adapt the template safely to your own page structure.

We will also cover troubleshooting separately. With templates built on YOOtheme Pro, the usual issues are less about a "broken design" and more about the wrong installation package, file permissions, an unavailable builder, JavaScript conflicts, Less/CSS errors, module positions, and incorrect template style assignments for menu items. That is why the final review matters just as much as the installation itself.

What Lilian Is Designed to Do and Where It Works Best

Lilian is built for sites where the goal is not to manage dozens of complex content entities, but to present an event in a calm, elegant way: the date, venue, the story of the couple or organizers, the schedule, location, gallery, partners, and a contact form. The official YOOtheme page describes it as a Joomla template for wedding websites and other event websites, and it also shows a set of ready-made pages: Home, About, Schedule, Location, Gallery, Partners, Contact, Index, and Post. That immediately suggests the right use case: the template works best when visitors need to quickly understand the event, get a feel for the atmosphere, and find practical information.

The main strength of the template is the combination of a polished aesthetic and YOOtheme Pro. Users get more than just a beautiful hero section. They also get page layouts, style variations, an image library, a visual editor, and a full settings system. For a site owner, that means you can start with the demo structure, replace the text, photos, and menu items, and then fine-tune the colors, fonts, and spacing without manually rewriting the template.

Lilian has a clear visual niche. It works especially well for weddings, intimate events, creative gatherings, family celebrations, photo sessions, mini festivals, and small conferences with a soft editorial tone. The reference design shows lots of breathing room, a large hero image, refined typography, muted dusty-pink sections, and a long landing page made up of sequential content blocks. That rhythm helps guide visitors from emotion to detail: first the impression, then the story, then the schedule, venue, gallery, and contact options.

If you need a dense catalog, a filter-heavy portal, a news resource, or a site with many roles and access levels, Lilian should not be your first choice. That does not mean Joomla and YOOtheme Pro cannot handle those tasks. It simply means Lilian's visual package is tuned for event storytelling and will require much more restructuring if you try to turn it into a product catalog, a municipal services portal, or a technical documentation site.

Practical takeaway: Lilian is especially useful when you need more than just "a nice-looking template" and want a ready-made event structure that you can quickly fill with real content and review in YOOtheme Pro's live preview.

Who This Template Is For and Who Should Choose a Different Foundation

Before installing it, it is worth honestly evaluating not just the visual style, but the workflow as well. Lilian fits users who want to build an event site on Joomla without designing the interface from scratch. It works well for a webmaster who already understands basic Joomla logic: menu items, categories, modules, template styles, access rights, and cache. It also suits agencies that need to show a client a wedding or event site prototype quickly and then replace the demo content with real photos, schedules, and contact details.

For a content manager, Lilian is convenient when the administrator has already set up the site structure. After that, the editor mainly needs to update pages, images, schedule items, and text blocks through YOOtheme Pro. But if the editor needs to regularly create new content types, advanced filters, participant directories, or user dashboards, the template alone will not be enough. You will need additional extensions, custom fields, separate output templates, or a different package that is closer to the project's content architecture from the start.

For a developer, Lilian is interesting because it follows the YOOtheme Pro approach: UIkit, the style customizer, child themes, template files, builder elements, and a modular architecture. That gives you room for safe customization, but it also requires discipline. You should not edit the main template files just to tweak a color or margin. It is better to use the settings, the CSS panel, a child theme, or a separate template style so that YOOtheme Pro updates do not overwrite your changes.

The template may not be the right fit if you need an extremely lightweight site without a page builder. YOOtheme Pro gives you visual flexibility, but it also adds its own layer of logic. If the project needs to stay extremely minimal, include only a couple of articles, and avoid a visual editor entirely, it may be easier to use a more basic Joomla template framework or a default template with a few custom modules. Lilian delivers the most value when its ready-made layouts and style variations actually save you time.

There is one more important factor: who will maintain the site after launch. If the handoff goes to someone with no Joomla experience, do not leave them with only the visual editor and the assumption that they will "figure it out." For Lilian, it helps to prepare a short map: which pages control the hero section, schedule, venue, and contact information; which modules must not be deleted; which template style is the active one; where the images are stored; and which style variation you chose as the baseline. That kind of map saves more time than complex documentation because most post-launch errors happen not during development, but during routine content updates.

That is especially important for agencies and freelancers. Lilian makes it easy to show a polished result quickly, but the client still needs to understand the boundaries of self-service editing. You can allow them to change text, photos, and schedule items while leaving global fonts, CSS, template styles, scripts, and access permissions to the administrator. The clearer the role boundaries are, the lower the risk that a finished design gets accidentally broken by an ordinary content edit.

Strong Use Cases

• A wedding site with a story, schedule, venue, gallery, and contact details.
• An event landing page where photos, schedule, map, and a quick path to the inquiry form matter most.
• A small creative event site that needs a soft visual style and an editorial tone.
• A fast agency starter when the client needs to see a complete demo flow instead of an empty framework.

Weak Use Cases

• A large catalog with filters, complex item pages, and many content types.
• A project where the design must be fully strict, corporate, or technical.
• A site where the client does not want to work with YOOtheme Pro and expects to use only standard Joomla articles.
• A project with a strict requirement not to use a page builder.

What to Check Before Installing It on an Existing Joomla Site

Preparation matters for more than just formality. YOOtheme Pro has two very different setup scenarios: installing the theme on an existing Joomla site, or deploying a demo package as a full Joomla installation with ready-made content. Getting this wrong leads to a common problem: the user downloads the demo package, tries to install it like a normal template archive, and ends up with confusing results. The official YOOtheme documentation specifically warns that the demo package is a complete Joomla installation, not a package to install over an already running site.

If you already have a site, first make sure you actually need the YOOtheme Pro theme archive for Joomla, not the full demo package. The layouts and styles from demo packages can be loaded into an existing site through YOOtheme Pro, so there is no need to deploy the entire quickstart over your production database. For a new project, by contrast, the demo package may be more convenient because it shows how the pages, images, modules, and menus are assembled into a finished structure. But a package like that should be deployed in a separate directory or on clean hosting, not on a live site.

The second part of the check is server resources and file permissions. YOOtheme documentation links installation problems to limited PHP resources on shared hosting: POST size, upload size, execution time, and memory. For an everyday user, that usually looks simple: the archive does not upload, the installation stops halfway, settings do not save, or the site appears without styles after the template is enabled. Before installation, check the limits in your hosting panel and whether you can change them through PHP settings or hosting support.

The third part is Joomla access permissions. The YOOtheme Pro customizer is available to users who have permission to edit templates. The documentation recommends restricting that permission carefully: not every content editor should be able to change the global template, styles, scripts, and site settings. On a production project, it is better to separate roles: the administrator handles the template style, API key, CSS, modules, and menus, while the editor works only with approved pages and content items.

Before installing, also make sure the project has a safe place for experimentation. The best option is a staging copy of the site or a separate directory where you can open the demo package, study Lilian's original structure, and only then transfer the parts you need to the live site. If you do not have a staging environment, work much more carefully: make a backup first, install next, confirm that settings can be saved, and only then begin replacing content. Do not start by mass-deleting demo pages, because those pages are often the easiest way to understand how layouts, menus, modules, and styles are connected.

Mini Checklist Before Installation

• Create a backup of the files and database before installing the template or demo package.
• Confirm whether you are installing the theme archive into an existing site or deploying the demo package as a separate Joomla installation.
• Check that the server upload limit is high enough to install the archive without interruption.
• Check directory and file permissions, especially if Joomla settings have failed to save before.
• Decide who will have access to the YOOtheme Pro customizer and template styles.
• Prepare real event photos in a sufficient size, because Lilian's visual impact depends heavily on image quality.

Installation: Standard Template, Quickstart, and the First Builder Launch

Installing Lilian depends on the current state of the site. For an existing project, the practical workflow looks like this: install the YOOtheme Pro theme for Joomla through the standard extension manager, then open YOOtheme Pro from the admin panel and load the required layouts or style package from inside the builder. For a fresh project, you can deploy the demo package and get a site where the page structure, images, and settings are already close to the official demo.

You should not mix these scenarios. The demo package is convenient for learning and fast starts, but it creates a full Joomla installation. If you deploy it over a working site, you can lose control of the current structure. The theme archive, by contrast, does not create all the content for you. After installation, it gives you YOOtheme Pro and the ability to load layouts, but the text, menus, modules, and pages still need to be tied into your real structure.

If the Site Already Exists

1. Open the Joomla admin panel and go to the standard extension installer.
2. Upload the YOOtheme Pro theme archive for Joomla, not the demo package.
3. After installation, open the YOOtheme item in the admin panel.
4. Check whether the customizer opens correctly: the settings panel should appear on the left and the live preview on the right.
5. Save the settings without making major changes so you can confirm that file permissions and configuration writes are working.
6. Load the required layouts through the library if your version and subscription include access to the layout library.

If the Project Starts from Scratch

1. Deploy the demo package in a clean directory and follow the standard Joomla installation process.
2. After signing in to the admin panel, review the homepage, menus, modules, and demo pages.
3. Do not delete the demo pages immediately. First figure out which blocks are responsible for Home, About, Schedule, Location, Gallery, Partners, and Contact.
4. Create a copy of the template style before making major changes so you preserve a rollback point.
5. Replace the demo content gradually: first the text, then the photos, then the menu, and only after that the styles and small CSS adjustments.

Check after the first launch: open the site as a guest, then as an administrator with the YOOtheme Pro preview. If you see different results, check the Joomla cache, browser cache, published modules, and the template style assignment for the menu item.

The First YOOtheme Pro Settings That Affect the Entire Site

After installation, do not start by tweaking every block one by one. Begin with the global settings: site & logo, header & navbar, mobile header, footer, style, pages, templates, menus, modules, and settings. In the YOOtheme Pro customizer, these panels are grouped in the left sidebar, while the live preview appears on the right. The interface is convenient, but that convenience can also create chaos: you can change the style, page structure, modules, and menus all at once, then lose track of which setting caused the result.

With Lilian, it is better to move from the general to the specific. First choose a style variation that matches the mood of the project. The official Lilian page lists six options: Default, White Green, Light Salmon, White Lilac, White Blue, and White Pink. Do not treat them as the final design. They are starting points you can refine through the style customizer by adjusting colors, fonts, and spacing. If you immediately start manually changing every UIkit component, rolling back becomes much harder.

Then check the logo, the main header, and the mobile header. For a wedding or event site, the menu is usually short: story, schedule, venue, gallery, contact. Lilian has a light visual style, so an overloaded menu can ruin the hero section faster than any color choice. If you have too many items, use a dropdown or a dedicated details page, but do not try to force everything into the navbar.

The next step is Settings. That is where you will find favicon, CSS, scripts, consent manager, API key, external services, advanced, system check, and about. On most sites, these settings are touched only once, but they directly affect updates, external services, user consent, and diagnostics. If you use maps, videos, or third-party scripts, review the consent manager and the loading categories. That is especially relevant for an event site: the venue map, video, and external widgets should not break the page or load without the required consent if the project has those requirements.

After the global setup, establish a rule for tracking changes. For Lilian, that can be as simple as a note in an admin document: "updated hero on Home," "added a new Schedule item," "created a template style for Contact," "added the CSS class event-note-card." That kind of discipline feels unnecessary while the project is still small, but it becomes invaluable for rollbacks. If a week later you discover that inner pages have different spacing or that a module disappeared only on Contact, you will find the last relevant change much faster instead of clicking through every customizer panel one by one.

Safe Configuration Sequence

1. Select a starting style variation and save the changes.
2. Set up the logo, site title, and basic header.
3. Trim the main menu down to the key event sections.
4. Check the mobile header to make sure navigation does not break on narrow screens.
5. Replace the hero photo and make sure the focal point does not crop out the important part of the image.
6. Set up the footer: contact details, social links, extra navigation, and legal pages if needed.
7. Open Settings and review favicon, CSS, scripts, consent, and system check.

What to Enable Only When Needed

Do not add custom scripts if the task can be solved through settings or a standard module. Do not change Less variables unless you understand which UIkit components they affect. Do not disable lazy loading for all images: YOOtheme Pro supports eager loading for above-the-fold images, but turning off lazy loading site-wide can hurt performance. Check the visible result first, then move on to deeper settings.

Lilian Layouts: How to Adapt the Demo Structure to a Real Event

The official Lilian page shows 10 ready-made page layouts. For users, that matters more than the abstract phrase "ready-made template." The layouts give you a content map: Home creates the first impression, About tells the story, Schedule explains the program, Location helps people get there, Gallery shows the atmosphere, Partners adds social proof or a list of participants, and Contact closes the loop. Index and Post become useful if the site will also publish news, announcements, or preparation updates.

A common mistake is to leave the demo structure in place and simply swap out the names. The page may still look attractive, but it will no longer answer real visitor questions. It is better to treat Lilian as a scenario, not a static picture. For every block, ask: what information should the visitor get here, what next step should they take, and how will the administrator verify that the block still makes sense after the content is replaced?

Home as a Visitor Journey

The homepage should answer three questions within a few seconds: what is happening, when, and where. After the hero section, it makes sense to provide a short story or context, then the key schedule blocks, the venue, the gallery, and contact details. If the site includes an RSVP form, do not hide it only in the footer. Create a clear path from the homepage to Contact or a dedicated section.

Schedule Without Overload

The event schedule should stay concise. For a wedding, that may mean the ceremony, a walk, dinner, dancing, and the close of the evening. For a conference, it could be registration, opening, core sessions, a break, and the evening program. In YOOtheme Pro, these blocks are easy to build with sections, cards, or a timeline-style layout, but there is no reason to turn the schedule into a full-screen table if visitors are mostly reading it on their phones.

Location and Map

The location section should include the address, landmarks, arrival timing, a map, and a fallback text route. If the map is loaded through an external service, check the consent manager settings and the placeholder behavior if the service requires consent. On an event site, this is not a cosmetic issue: a guest should not lose the address just because the map script failed to load.

Gallery and Photos

Lilian relies on large imagery. YOOtheme Pro can manage image size, focal point, responsive images, lazy loading, and next-gen formats, but the original photo quality still matters. Use images with a clear composition, do not place faces or important details too close to the edges of the frame, and review cropping in both desktop and mobile preview. If the photos vary heavily in color tone, bring them into a more consistent treatment before you start choosing a style variation.

Lilian's Styles, Images, and Visual Identity

Lilian's visual identity is built around a soft editorial presentation. The attached source reference shows white space, a large hero image with a couple on a forest path, a light text block over the photo, dusty-pink compositional accents below, large pale background headings, and careful typography. This is not a generic corporate template. It is a design with a specific mood. If you replace the photography with harsh business imagery and add overly saturated colors, the template will lose its character.

Style variations help you start with a nearby color direction, but the real fine-tuning happens through the style customizer. YOOtheme documentation explains that styles are based on UIkit and Less variables. That means changing buttons, cards, spacing, headings, and colors affects not just one block, but the system's components as a whole. A good practice is to start with global variables and review the UI components preview before moving on to individual components.

Image handling in Lilian deserves special attention. The YOOtheme Pro documentation covers width, height, focal point, responsive images, WebP/AVIF, lazy loading, media manager, and access to Pro Images, Unsplash, and Pexels. For an event site, that is not just a technical detail. It is how you preserve composition. If the hero uses a portrait image, a poorly chosen focal point can crop out faces. If the gallery loads oversized originals, visitors will end up waiting, even though the template is visually designed to feel light and effortless.

How Not to Damage the Style When Replacing Content

• Keep the sections spacious and avoid crowding the hero with extra buttons.
• Choose photos with natural light and a similar color temperature.
• Check cropping through the focal point, especially for portraits and couple photography.
• Do not replace all fonts at once. First evaluate how the new font affects headings, menus, and captions.
• Use one primary accent for buttons instead of several competing colors.
• After changing Less or CSS, review not just Home, but also Contact, Gallery, Index, and Post.

Template Styles, Menus, and Module Positions in Joomla

For a Joomla template, one of the most important layers is the relationship between the template style, menu items, and module positions. YOOtheme Pro documentation notes that template styles can be duplicated and assigned to different menu items. That is especially useful for Lilian: for example, the homepage can use one style and hero configuration, while the contact page or blog posts can use a calmer template style without the large above-the-fold treatment.

YOOtheme Pro integrates Joomla's Menu Manager and Module Manager into its own interface. In the Menus panel, you can add, edit, and delete menu items without leaving the builder. In the Modules panel, you can see positions and published modules, and the live preview highlights a module when you hover over it. That makes setup much easier, but it does not remove Joomla's rules. A module still has to be published, assigned to the right pages, placed in a suitable position, and filled with actual content.

For Lilian, the positions that matter most are header, navbar, dialog, top, bottom, sidebar, and builder positions. Header and navbar control navigation. Dialog is useful for an offcanvas or modal menu if you need to hide extra items on mobile. Top and bottom work well for additional sections above or below the main output. Builder positions matter when you render modules through the Position element inside the page builder. If a module is assigned to a position that is not rendered on the selected page, it will not appear, even though it is published in Joomla.

Practical Menu Setup

1. Create or review the main Joomla menu.
2. Keep only the sections that visitors actually need for the event.
3. In YOOtheme Pro, open the Menu panel and check the item order.
4. Use dropdown columns or a mega menu for long lists only if they genuinely improve usability.
5. Check the mobile header and dialog/offcanvas behavior so the menu remains usable on phones.
6. Open the site as a guest and make sure the links go to real pages, not demo placeholders.

Practical Module Setup

1. Open the Modules panel in YOOtheme Pro and review which positions are already in use.
2. Hover over the modules in the sidebar to see where they appear in the live preview.
3. If you need a new block, create a Joomla module and assign it to the appropriate position.
4. For a more complex block, use a builder module if a standard Custom HTML module feels too limited.
5. Check Menu Assignment so the module does not accidentally appear on every page.
6. If you need more advanced visibility rules, consider Advanced Module Manager, which YOOtheme mentions in the documentation as an option for extended visibility control.

Key check: if a block is not visible on the page, first verify its publication status, position, menu item assignment, and visibility in the current preview. Only look at CSS after that.

Practical Example: Building a Homepage for a Wedding or an Intimate Event

Below is an example you can adapt for a wedding, anniversary, private party, or small creative evening. The goal is to create a homepage where visitors immediately understand the event, see the date and venue, can review the schedule, browse the gallery, and move to contact or RSVP. The example does not require writing code. It uses Lilian's standard features, page layouts, menus, and Joomla modules.

Goal

Build a homepage on top of Lilian that guides the guest through a clear path: first impression, story, schedule, venue, gallery, contact. The homepage should feel emotional enough without losing practical information.

Preparation

• The YOOtheme Pro theme is installed, or the demo package is deployed on a clean site.
• The YOOtheme Pro customizer opens correctly, and the live preview saves changes.
• Hero, couple or event, venue, and gallery photos are prepared.
• The Home, About, Schedule, Location, Gallery, and Contact pages are created or reviewed.
• The main Joomla menu contains only current, relevant items.

Steps

1. Open the Home layout in YOOtheme Pro and keep the original structure as your reference.
2. Replace the hero photo with a real event image. Check the focal point so people or the key subject are not cropped out.
3. In the first text block, keep only the event name, a short descriptor, and the date or a brief contextual line without clutter.
4. In the About block, replace the demo story with 2-3 paragraphs about the event. Do not write a long biography if visitors care more about the venue and schedule.
5. In Schedule, keep 4-6 key stages. For each stage, include the time or order, a short description, and the location if different stages happen in different areas.
6. In Location, add the address, a map or map link, a fallback text direction, and a short arrival note.
7. In Gallery, upload photos with consistent visual quality. For portrait-oriented shots, check the mobile preview crop.
8. In Contact, add a contact method or form. If the form is handled by a separate extension, test the submission with a sample message.
9. Open the Menu panel and connect the menu items to real pages rather than demo links.
10. Save the changes and review the homepage in guest mode.

Result Check

After setup, open the homepage in three states: desktop, tablet, and phone preview inside YOOtheme Pro, then in a separate browser without signing in to the admin panel. Check that the hero image does not crop people, the menu opens on mobile, the schedule is readable without horizontal scrolling, the map or address is accessible, the gallery is not loading overly heavy images, and Contact leads to a real action.

A Common Detail That Gets in the Way

If some modules disappear after you replace the homepage, do not rush to blame the template. Check whether the modules are still assigned to the old demo page menu item. In Joomla, the menu item often determines which template style and which modules are visible. If you created a new Home page but did not reassign the modules and template style, the site may look "broken" even though the real issue is in the assignments.

Practical Ways to Use Lilian Beyond a Wedding Website

Although Lilian is positioned around wedding websites, its event-oriented structure can work more broadly. The key is not to invent features that are not supported by the sources, but to use the confirmed elements well: ready-made layouts, style variations, images, the page builder, menus, modules, contact details, schedules, and location blocks. Below are several scenarios where the template can work without a major rebuild.

Intimate Festival or Creative Evening

Home introduces the overall concept, Schedule becomes the program, Partners becomes a list of organizers or venues, Gallery shows the atmosphere of past events, and Contact leads to an inquiry or subscription. The validation is simple: a visitor should understand in a single scroll what will happen, where it will take place, and how to reach the organizer.

Family Celebration or Anniversary

About can become the story of the family or the event's central person, Location can become a detailed guide for guests, Gallery can become a curated photo collection, and Contact can become a feedback form. Here it is especially important not to overload the menu: most guests will come for the address, time, and photos.

Photo Story or Editorial Landing Page

Because of its soft typography and large imagery, Lilian can also work as a base for a visual narrative. In that case, Schedule can become a story path, Gallery can become the primary section, and Partners can become acknowledgments or contributors. But if you need a full photo blog with a large archive, it is better to extend the template with categories and post output templates.

Small Ceremony with Registration

If the site needs an RSVP form, Lilian itself should handle the visual shell, while the form submission is better handled by a separate Joomla extension. The important part is making sure the form does not conflict with the styles, successfully sends messages, shows errors correctly, and stays readable on mobile. The template helps you create a welcoming page, but it does not replace a dedicated form solution.

Checking the Result: Appearance, Speed, SEO, and Safe Changes

After configuring Lilian, it is not enough to say, "the homepage looks nice on my end." Review the result as a user, a search engine, an editor, and an administrator. For an event site, a few things are critical: the first screen should be clear, the menu should work, the photos should not destroy performance, the contact details and map should be accessible, and changes made in YOOtheme Pro should save without errors.

YOOtheme Pro includes device preview buttons. Use them not only at the end, but after every major change. That is especially important with Lilian: hero photos, dusty-pink sections, large background headings, and overlay blocks can look perfect on desktop and then fall apart compositionally on mobile. If a portrait photo is cropped badly, go back to the focal point or replace the image with a frame that gives the main subject more space.

Check speed in a real browser and with performance tools. YOOtheme Pro generates responsive images and supports lazy loading and next-gen formats, but that does not remove the need to control the source files. If you upload dozens of heavy photos without curation, the landing page will still become slow. For the hero area, use a high-quality but reasonably prepared image, and for the gallery, use a consistent size and careful compression.

The SEO review for Lilian should not turn into a keyword exercise. An event site needs a clear title and description, a logical H heading structure inside the content, text-based addresses, and meaningful image descriptions. If part of the information exists only inside an image, search engines and users with accessibility limitations may miss it. That is why the date, location, schedule, and contact details should also appear in text.

Post-Setup Checklist

• The homepage answers the questions "what," "where," and "how do I get in touch" without making visitors hunt for the answer.
• All menu items lead to real pages, not demo placeholders.
• The template style is assigned to the correct menu items and does not conflict with other pages.
• Modules are published in the correct positions and appear only where they are needed.
• Hero, Gallery, and Location have been reviewed in desktop, tablet, and phone preview.
• Forms, maps, and videos have been tested with external-service consent in mind, if they are used.
• Joomla cache, browser cache, and image cache have been cleared after major changes.
• PHP and JavaScript errors have been checked in logs and the browser console if the page looks empty or does not respond to clicks.

Safe Enhancements Without Editing the Template Core

You can strengthen Lilian's visual presentation without touching the main template files. YOOtheme Pro documentation offers several safe paths: CSS/Less in the Settings panel, a child theme for project-specific files, custom.css and custom.js inside the child theme, as well as Joomla template overrides and module positions. For most site owners, the CSS panel or a child theme is enough. There is no need to edit YOOtheme Pro core files.

Below is a small CSS example for an event information card. It does not depend on Lilian's internal classes. You add the event-note-card class yourself to a block, Custom HTML module, or HTML element in the page builder, and then define its appearance in Settings - CSS or in the child theme file css/custom.css. This approach is reversible: remove the class or the CSS, and the block returns to its default appearance.

.event-note-card {
  padding: 28px;
  border-radius: 0;
  background: #d8c2bf;
  color: #3b3331;
}

.event-note-card .event-note-title {
  margin-top: 0;
  font-size: 1.35rem;
}

.event-note-card a {
  color: inherit;
  text-decoration: underline;
}

This tweak works well for a short note next to the schedule or location block, for example, "arrive 20 minutes before the start" or "parking is located behind the main entrance." It is based on standard CSS practice and the custom CSS workflow documented by YOOtheme Pro in the Settings panel. There are no invented hooks, no template file edits, and no dependency on Lilian's internal markup.

The verification after adding it is simple: open the page in live preview, then in guest mode, then in mobile preview. If the text becomes hard to read on the chosen style variation, adjust the color or background. If the block disrupts Lilian's overall rhythm, reduce the padding or switch back to a standard YOOtheme Pro component. Rollback should take less than a minute: remove the CSS or remove the custom class from the block.

For deeper customization, use a child theme. YOOtheme Pro documentation for Joomla describes creating a separate child theme folder next to the main yootheme template, automatic loading of css/custom.css and js/custom.js, and the ability to add Less styles and builder elements. That is the better path for an agency or developer who wants to move changes between projects and keep them safe through updates.

Why Lilian May Display Incorrectly and How to Diagnose It

With Joomla templates built on YOOtheme Pro, problems often look the same: the site is blank, styles are missing, the builder is unavailable, a module does not appear, a menu points to the wrong place, or changes fail to save. But the causes vary. Below is a diagnostic map that helps you move from simple checks to more complex ones instead of trying to fix CSS when the real issue is menu assignment or file permissions.

The Builder Says It Is Unavailable on the Page

Symptom: the page opens, but the YOOtheme Pro builder reports that it is unavailable. YOOtheme documentation lists several possible causes: the Joomla session has expired, or a third-party plugin is interfering, such as a security plugin, email processing, or Cloudflare RocketLoader. Start by signing out and back in to the admin panel. Then disable suspicious JavaScript optimizations on a test page and check the browser console.

What to Check

• Whether the Joomla administrator session is still active.
• Whether third-party plugins are altering HTML or JavaScript in edit mode.
• Whether aggressive script optimization is enabled at the CDN or cache level.
• Whether the builder opens on another page of the same site.

If the builder works on one page and not on another, look for differences in page type, assigned modules, template style, and scripts that load only there.

The Site Opens Without Styles or Settings Will Not Save

Symptom: the public-facing site looks "unstyled," CSS does not load, or the customizer cannot save its configuration. In YOOtheme documentation, those signs are tied to file permission issues. Check directory and file permissions, file ownership on the server, and whether Joomla can write to the template and cache directories. YOOtheme documentation provides typical permission values for directories and files, but on a real host, those should still be aligned with the provider's security policy.

How to Fix It

1. Check Joomla system information and identify the directories that are not writable.
2. Compare file and directory permissions with your hosting provider's recommendations.
3. Clear the Joomla cache and YOOtheme cache after fixing the permissions.
4. Save a simple setting in the customizer and check whether it appears on the public site.

If fixing permissions requires recursive changes on the server, create a backup first and do not apply overly permissive settings just for a quick result.

The Module Is Published but Not Visible

Symptom: the module exists and is published, but it does not appear in the expected Lilian block. Likely causes include the wrong position, incorrect menu item assignment, an empty module, a template style that does not render the needed position, or a module that should be inserted through a Position element inside the builder layout. In YOOtheme Pro, use the Modules panel: it shows module positions, gray dots, and highlights in the live preview.

Start the fix with Joomla logic: publication, position, access, language, and menu assignment. Then review the YOOtheme Pro settings. If the module needs to appear inside a specific page builder section, simply publishing it in top or bottom may not give the expected result. Use the appropriate builder position or a builder module instead.

The Style Customizer Stopped Working After Changing Colors

Symptom: after entering a value in the style settings, a Less error appears, part of the customizer fails to compile, or the CSS no longer updates. YOOtheme documentation explicitly describes cases where invalid Less values trigger a compilation error. Go back to the component you changed and reset the setting using the gray dot or the reset option in that component. If you added CSS in Settings, temporarily remove the last snippet and save again.

The Homepage Looks Correct but Inner Pages Look Different

Symptom: Home matches Lilian, but Contact, Gallery, or Post looks different. The cause is usually template styles and page assignment. Check which template style is assigned to the menu item, which page is currently open in preview, whether a style copy was created only for the homepage, and whether the inner pages are still using a different style. If you duplicated a style for experiments, give the copies clear names. Otherwise, a few days later it will be hard to tell which version is the working one.

Animation or Menus Stopped Responding

Symptom: clicks do not work, the mobile menu does not open, or effects stop working. YOOtheme documentation recommends checking JavaScript errors in the browser console. The cause may be a third-party script, an optimization layer, an extension conflict, or a custom script inserted incorrectly. Disable changes one by one: first the custom script, then optimization layers, then third-party plugins that interfere with HTML or JavaScript.

When YOOtheme Lilian Is the Right Choice

Lilian is worth using if you need a Joomla event website with a ready-made visual narrative: a strong first screen, a story, a schedule, a venue, a gallery, partners, contact details, and a soft wedding or editorial atmosphere. It is especially strong when you are ready to work inside YOOtheme Pro and want to do more than simply enable a template. The real value comes from carefully adapting the demo logic to your own content.

Before the final launch, walk through three checks: the correct installation type, the correct relationship between template styles and menu items, and the real result on the public-facing site. After that, you can go to the product file and download the YOOtheme Lilian archive for testing in your own environment. Do that only after creating a backup, and do not replace a working site with the demo package without separate preparation.

If you need a strict corporate portal, a catalog, or a news site with many content entities, consider other YOOtheme packages or more universal Joomla frameworks. But if the goal is to assemble a warm event page quickly and then refine it through YOOtheme Pro, Lilian gives you a strong starting structure and a clear setup path.