20 lines
1.4 KiB
Markdown
20 lines
1.4 KiB
Markdown
# SonarDesk — Stylist theme integration
|
|
|
|
Stylist is the primary resolver for ordinary frontend and backend Laravel views. The active theme, its parents, the bundled baseline and finally `resources/views` are searched in that order.
|
|
|
|
- Frontend: `resources/themes/sonardesk/views`.
|
|
- Backend: `resources/themes/sonardesk-admin/views`.
|
|
- The bundled themes preserve existing markup, CSS, JavaScript, routes and business logic.
|
|
- `/admin` and `/stylist` use backend; other web pages (including authenticated customer pages) use frontend.
|
|
- AdminOnly middleware protects Stylist operations.
|
|
- Bundled and active themes cannot be uninstalled.
|
|
- Keep `resources/views`: email templates, fallback and compatibility views are required.
|
|
- New theme ZIPs must include all needed templates, layouts, assets and a valid theme.json. Missing views fall back to baseline.
|
|
- The middleware does not change asset URLs. Replacement themes must supply their own asset references and use the existing Stylist asset serving facilities.
|
|
|
|
## Local validation
|
|
|
|
Run `php artisan optimize:clear`, `php artisan migrate`, `php artisan stylist:doctor` (if registered) and `php artisan view:cache` using your configured PHP binary. Test public pages, authentication, checkout, admin, Stylist, and transactional email before deployment.
|
|
|
|
This package has not been executed against your ServBay environment. Do not deploy to production without smoke testing.
|