Unable to view layouts after Laravel integration in Metronic Tailwind

Hi Kanmani,

Understanding

You followed the Laravel integration guide but the layouts aren't displaying correctly after setup. This is a common issue for first-time Metronic v9 users — the GitHub starter kit provides the scaffolding, but the actual Metronic design assets need to be copied separately.

Solution

The GitHub starter kit (metronic-tailwind-laravel) contains the Laravel project structure, controllers, routes, and Blade templates — but not the Metronic CSS, JavaScript, or media assets. Those come from your ThemeForest download.

Step 1: Copy Metronic assets

After cloning the starter kit, copy the assets from your ThemeForest download:

# From the ThemeForest zip, copy the dist/assets folder
cp -r /path/to/metronic-tailwind-html/dist/assets public/

This provides the compiled CSS (styles.css), JavaScript (core.bundle.js, layout scripts), icons, and media files that the Blade templates reference.

Step 2: Install dependencies and build

composer install
npm install
npm run dev

Run npm run dev in a separate terminal — Vite needs to be running for asset compilation during development.

Step 3: Access the layouts

The 10 demo layouts are available at:

• /demo1 through /demo10

Each demo is a different layout style (sidebar, header, minimal, creative, etc.).

Step 4: Environment setup

cp .env.example .env
php artisan key:generate

Important Notes

• Tailwind version: Metronic v9 uses Tailwind CSS 3.x. Do not upgrade to Tailwind 4 — it has breaking changes and is not yet supported.
• Asset paths: The Blade templates expect assets at public/assets/. If you see unstyled pages, the assets are likely missing or in the wrong location.
• Vite dev server: Both php artisan serve and npm run dev need to be running simultaneously during development.

Sources

• Laravel Integration Guide
• GitHub Starter Kit
• ThemeForest Download

Next Steps

If the layouts still don't display after copying the assets, please share:

1. The browser console errors (F12 → Console tab)
2. Whether public/assets/css/styles.css exists in your project

This will help us pinpoint the exact issue.

This reply was generated by AI. A human will follow up if needed.