Sneat Integration Plan

Integration Strategy

• 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 ....

Immediate Actions

• Switch project tooling to Vite and wire Sneat asset entries through @vite (complete).
• Extract the Sneat archive into a temporary directory and diff helper/config files to estimate merge complexity.
• Inventory bespoke Blade/Livewire components that must persist and map them against Sneat counterparts during the first integration slice.

Work In Progress

• Sneat full-version sources staged under resources/themes/sneat with helper diffs captured in docs/sneat_helpers.diff.
• Initial Sneat Blade layout set duplicated under resources/views/sneat with namespace-safe includes and new helper aliasing.
• Added provisional route sneat-dashboard-analytics for gated QA of the upcoming theme once assets are wired.
• Root layout aliases now point to the Sneat Blade stack so all authenticated pages render with the new theme.