Panel: Simpler way of distributing custom themes

[tenten8401]

Can we have an easier way of distributing themes? Like a 1-folder solution instead of extracting to 2 different places and adding an entry to themes.php?

[MatthewSH]

It's not that complicated in my opinion.

Layouts, modules, pages > resources/themes/
CSS, JS, etc > public/themes/

Then you allow people the use of the theme in the config. I'm trying to understand how this is complicated.

Maybe there's just a lack of tutorials out there. If this is the case, then maybe we can get something going for that.

[OzairP]

I don't think it's about complexity, but more of a single source of truth type deal.

For example, if you had removed a themes CSS but not it's pages. It would make sense if they stayed in one folder with each theme having its own style and markup subfolders.

[DaneEveritt]

Theres no other way to do this currently with the way Laravel works. The entire point of the public folder is that anything in there can be accessed by users, while the actual template files are stored privately since users should not be able to see them.

[OzairP]

Perhaps using a build tool like Laravel Mix/Elixir?

[MatthewSH]

@OzairP I'm not sure what you're trying to get at? That doesn't really make sense with the rest of the conversation thus far.

We're discussing theme distribution, not the development of themes.

[OzairP]

@MatthewSH I meant using a build tool to move files, preprocess files, etc. Makes distribution easier.

That way users only need to deploy their files in one location and the build tools can distribute them however. No need to learn what goes where, Similar to how Laravel 5.4 handles it.