added theme support
This commit is contained in:
@@ -0,0 +1,15 @@
|
||||
# SonarDesk Stylist integration — 1.0.0
|
||||
|
||||
- `resources/themes/sonardesk/views` contains the original frontend Blade templates.
|
||||
- `resources/themes/sonardesk-admin/views` contains the original backend Blade templates.
|
||||
- Both are fully editable independent view trees, with application view fallback.
|
||||
- Active theme is selected by existing Stylist SettingsRepository (`frontend_theme` / `backend_theme`).
|
||||
- The `ApplyActiveTheme` web middleware prepends the active theme view directory for each request.
|
||||
- Public pages and authenticated customer pages use frontend; `/admin` and `/stylist` use backend.
|
||||
- Controllers, routes, licensing, payments, APIs and mail templates remain unchanged.
|
||||
- Theme management now requires AdminOnly permissions.
|
||||
- Existing CSS/JS assets remain in place. Replacement themes may provide new layout asset links.
|
||||
- Run `php artisan optimize:clear` and `php artisan migrate` after deployment.
|
||||
- Check `/stylist` as an administrator, then verify public, account, admin, and checkout pages.
|
||||
- If database already contains old `frontend_theme`/`backend_theme` values, activate the new bundled themes from Stylist.
|
||||
- Theme ZIP installation security and the completeness of third-party theme templates require separate review before production use.
|
||||
Reference in New Issue
Block a user