Create a dedicated working branch and snapshot the current Mix-driven Materialize theme so existing builds remain reproducible while Sneat work proceeds in parallel.
Unpack sneat-bootstrap-html-laravel-admin-template-v4.0.0.zip into a staging area, for example resources/themes/sneat, and catalogue its Laravel-specific pieces: helpers, configuration, resources/assets, Vite setup, Blade layouts, and sample controllers.
Compare Sneat helper/config files with project files such as app/Helpers/Helpers.php and related menu/setting configs to preserve current feature flags while adopting new Sneat options.
Choose an asset pipeline approach: migrate the project to Vite to align with Sneat, or adapt Sneat assets to the existing Laravel Mix workflow by restructuring resources/assets and updating webpack.mix.js.
Scaffold Sneat layouts within resources/views/layouts, wire required partials, and adjust providers/menu builders if Sneat expects different data structures.
Migrate critical pages incrementally, starting with a Sneat-powered dashboard route, mapping Blade includes to live data and progressively replacing legacy Materialize views while validating Livewire and JavaScript interactions.
Align frontend dependencies, removing unused Materialize libraries once Sneat equivalents are live; update localization files and Tailwind/Sass assets accordingly.
Run full build/test passes with php artisan test, npm run build or vite build, and browser-test responsive states.
Update deployment docs and ensure production Docker commands continue to use sudo docker exec logidav-app php artisan ....