Laravel demo16 and demo19
Hello KeenThemes,
First, congratulations for Metronic, it seems very nice and well documented.
For a project I'm considering to go with either the demo16 or demo19 layout. However it looks like these layouts are not available as demo for a Laravel app development.
Are you planning to port these demo to laravel anytime soon ?
Or alternatively maybe, do you consider it difficult to adapt an existing demo to use either one of these layouts ?
Thanks a lot for your reply.
Cheers
Replies (7)
I’m amazed at how Sprunki Retake easy it is to make a spooky beat. The controls are smooth, and the sound options are fantastic!
Experience the thrill of a dune buggy ride Dubai! Take on the desert's rugged terrain in a powerful dune buggy, navigating golden sands and exhilarating dunes. Perfect for adventure seekers—book your ride today for an unforgettable desert adventure!
It's possible that KeenThemes does not currently have any plans to release demo16 or demo19 in Laravel. If you are familiar with Laravel and Blade templates, it is not too hard to modify an existing sample for Laravel.
that's not my neighbor
Hi drift hunters, KeenThemes may plan to port Demo 16 and Demo 19 to Laravel, but there's no specific timeline. Adapting an existing demo for Laravel is possible and manageable. You can integrate the HTML, CSS, and JavaScript into Laravel by using Blade templating, Laravel Mix for asset management, and adjusting routes/controllers. It requires some effort but is achievable with the provided documentation.
Hi Sean, thanks a lot for the infos !
Hi,
Thanks for your feedback on Metronic.
Yes, we are planning to implement pending Laravel demos but at the moment we can't confirm the ETA.
You can refer to the Laravel demo1 and integrate other demos into Larave. You can use the layout builder of your selected demo to get the HTML partials exported.
The JS initialization and the webpack mix part is similar for all demos.
Regards
Hello Sean,
Actually I have some trouble adaptating demo16 to laravel.
For the views it's not really a problem but for assets (css/js) built from resources by laravel mix, I have some difficulties know what I should take from demo1 and what I should take from the "sources" of the html bundle of demo5.
The result at the moment is many errors when runing npm run dev (or prod).
Do you have by any chance some hints to start adapting the demo16 to laravel in the right direction ?
Any help is welcome 
