We will create a artisan command called "unusual:create:theme" that will use our sass theme template, and copy this theme file boilerplate under laravel resources/modularity/themes with a "--name" parameter. This parameter is required and will be the name of new theme. the theme folders under resources/modularity/themes will move synchronously on runtime of "unusual:dev" and "unusual:build" commands with chokidar-cli as being resources/js/unusual/*.vue files.
As second, We'll create a "unusual:make:theme" after this processes completed. This command will move this completed theme under modularity/vue/src/sass/themes for generalize this theme for our modularity system. You can think that the command is as for local development of modularity. it mustn't be used on production case.
We will create a artisan command called "unusual:create:theme" that will use our sass theme template, and copy this theme file boilerplate under laravel resources/modularity/themes with a "--name" parameter. This parameter is required and will be the name of new theme. the theme folders under resources/modularity/themes will move synchronously on runtime of "unusual:dev" and "unusual:build" commands with chokidar-cli as being resources/js/unusual/*.vue files.
As second, We'll create a "unusual:make:theme" after this processes completed. This command will move this completed theme under modularity/vue/src/sass/themes for generalize this theme for our modularity system. You can think that the command is as for local development of modularity. it mustn't be used on production case.
┆Issue is synchronized with this Teamwork task by Unito