You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Greetings. I am trying to extend a Laravel app where the developer already has built out the theme that ships with the app at resources/views & public folders. My goal is to provide new themes that can be easily installed for the end user. Otherwise I could just create masterTheme directories, move the default theme files and declare it and the new paths. Following is an example of the existing directory structure as the app ships:
resources/views/auth/
resources/views/banners/
resources/views/brands/
etc.
public/css/
public/fonts/
public/frontend/
etc.
Any ideas? Im trying to avoid having to move the default theme so that future updates from the author won't be a nightmare to install. Also, Im somewhat new to Laravel so I might be missing something obvious to more experienced developers :)
Thanks for your solution!
The text was updated successfully, but these errors were encountered:
Greetings. I am trying to extend a Laravel app where the developer already has built out the theme that ships with the app at resources/views & public folders. My goal is to provide new themes that can be easily installed for the end user. Otherwise I could just create masterTheme directories, move the default theme files and declare it and the new paths. Following is an example of the existing directory structure as the app ships:
resources/views/auth/
resources/views/banners/
resources/views/brands/
etc.
public/css/
public/fonts/
public/frontend/
etc.
Any ideas? Im trying to avoid having to move the default theme so that future updates from the author won't be a nightmare to install. Also, Im somewhat new to Laravel so I might be missing something obvious to more experienced developers :)
Thanks for your solution!
The text was updated successfully, but these errors were encountered: