Configuration
Most of uLanding is configured visually inside the admin panel — you almost never need to touch files. After installing via Plugins → Add Plugin and enabling the plugin, everyday settings live in the Theme Customizer and content modules.
Tip Non‑technical users can skip this page. Use Plugins → All Plugins to enable/disable uLanding, and the Customizer for colors, logos, and layout.
Environment (.env) settings
These live in your project's .env file (for developers / advanced hosts). After changing them, run php artisan config:clear.
| Setting | Default | What it does |
|---|---|---|
ULANDING_ENABLED |
follows install | Optional env override for the plugin feature flag when used by your host config |
ULANDING_THEME_MODE |
light |
Default color mode fallback (light or dark) when nothing else is set |
ULANDING_HOME_PAGE_SLUG |
home |
Which page acts as your homepage. The page with this slug is shown at / |
Note Day-to-day activation is controlled in Plugins → All Plugins (Enable / Disable). Prefer that over editing
.envunless your developer instructs otherwise.Example To default the site mode toward dark until the Customizer overrides it:
env ULANDING_THEME_MODE=dark ULANDING_HOME_PAGE_SLUG=home
The config/ulanding.php file
This file holds default values and lists. You rarely need to edit it, but here's what each section controls.
| Setting | What it controls |
|---|---|
enabled |
Reads ULANDING_ENABLED. The master switch. |
theme_mode |
Reads ULANDING_THEME_MODE. Default light/dark. |
mega_menu |
Default mega‑menu behavior (max columns, badges, thumbnails, CTA). Usually overridden in the Customizer. |
auth_buttons |
Default text and links for the Sign In and Sign Up / Let's Talk buttons. |
topbar |
Default top‑bar content (announcement, email, phone, etc.). |
footer_bottom |
Default footer bottom bar (copyright, payment icons, legal links). |
home_page_slug |
Reads ULANDING_HOME_PAGE_SLUG. Your homepage slug. |
frontend_assets |
The CSS and JS files loaded on every public page. Do not change unless you're a developer. |
reserved_slugs |
A list of page slugs you are not allowed to use (because they're used by the system). See below. |
blog_sidebar_cta |
The default content of the blog sidebar call‑to‑action widget. |
page_builder_addons |
The list of blocks shown in the page builder's widget library. |
Reserved slugs
You cannot create a page using any of these slugs, because the system already uses them:
theme-preview, _assets, admin, login, logout, register, password,
install, update, debug, account, dashboard, api, storage, vendor,
terms-of-use, privacy-policy, faqs, languages, lang, blog
Warning If you try to save a page with a reserved slug (for example
adminorblog), uLanding will reject it. Choose a different slug. Note thatblogis reserved because it powers your blog archive automatically.
The config/themes.php file
This file defines the 10 themes and their default header, footer, menu and container settings. It is read‑only for most users — you change a theme's appearance through the Theme Customizer, not this file. Developers can use it to register custom themes.
See Themes for the per‑theme breakdown.
Choosing your homepage
By default, the page with the slug home becomes your homepage and is shown at your root URL (/). Visiting /home automatically redirects to /.
To use a different page as your homepage:
- Make sure the page exists and is Published.
- Set
ULANDING_HOME_PAGE_SLUGin.envto that page's slug. - Run
php artisan config:clear.
Note When you import demo content, uLanding automatically sets the
homepage as your homepage. You usually don't need to change this.
Light, dark and automatic mode
There are three ways the site's color mode is decided, in order of priority:
- Theme Customizer → General → Theme Mode (highest priority) — set to Light, Dark or Auto.
- The
ULANDING_THEME_MODEvalue in.env. - The config default (
light).
Auto means the site follows each visitor's device setting (if their phone is in dark mode, they see your dark theme).
You can also override the mode on a single block in the page builder — see Page Builder.
Caching
uLanding caches rendered pages for 6 hours to keep your site fast. This is automatic.
- Saving a section in the page builder clears that page's cache immediately.
- Activating a theme or importing demo content clears all theme caches.
- If a change ever fails to appear, clear all caches:
php artisan optimize:clear
Console commands (for administrators)
uLanding adds three command‑line tools. You'll rarely need them, but they're documented here for completeness.
| Command | What it does |
|---|---|
php artisan ulanding:audit-translations --locale=en |
Scans for missing or unused translation keys in a language. Useful when adding a new language. |
php artisan pagebuilder:migrate-sections-to-rows --page={id} |
Upgrades a page's layout from the simple grid to the advanced row/column system. |
php artisan pagebuilder:rollback-layout --page={id} |
Reverts a page back to the simple grid layout. |
Warning The page‑builder migration commands change how a page is stored. Back up your database before running them on a live site.
Continue to the Quick Start Guide.