Lauris,

BTW do you have any channel where we can submit suggestions in regard to ASP.NET Core build you provide? Specifically, related to how folders are structured to make it easier for us to apply updates when you release them.

Thanks

Hi,

You can leave your suggestions here I will create a task in our backlog and we will consider implementing it in upcoming Metronic releases.

Regards,
Lauris Stepanovs,
Keenthemes Support Team

Hi Lauris,

Here are my suggestions:

FIRST SUGGESTION
Currently in the folder structure Starterkit\_keenthemes contains two folders src and tools. These folders contain source files for node modules and Javascript & CSS that then being compiled into wwwroot if I understand correctly.

I will suggest moving these folders to the root, same level with StarterKit folder, as these files are not related to ASP.NET project at all and are unnecessary.

So basically you will have:
build\src
build\tools
Starterkit\_keenthemes\config
Starterkit\_keenthemes\libs

Let me know if you have any questions in regard to the above. From what I understand only 2 lines will need to be change one in gulp.config.js and one in webpack.config.js.

SECOND SUGGESTION
It will be good, if Starterkit\Views will contain CSHTML files of only the demo that was used when calling gulp --demo1 rather than both Demo1 and Demo30 files. Regardless other one is not going to work as JS and CSS files will be compiled only for one of these, so it is unnecessary to have these files at all. Same applies to not having extra nested folder as well, so instead of, for example, Starterkit\Views\Pages\Auth\Demo1\NewPassword.cshtml it will be Starterkit\Views\Pages\Auth\NewPassword.cshtml, this way it will be cleaner.

THIRD SUGGESTIONS
It will be really good if you can make KTTheme a NuGet package.

Hopefully this was descriptive enough to make it happen in next version.

There are more suggestions, but these are more complicated and related on how the project is structured and maybe I will write it in another reply.

Thanks
Hayk

Hi Hayk,

Thank you very much for your suggestions.

1. Generally, it's good practice to include project assets and build scripts within the ASP.NET project and some users prefer to import JavaScript files directly from the _keenthemes folder into their cshtml files. If you prefer to keep assets and scripts outside the Starterkit folder, you can use the mentioned structure - just remember to update the output paths in the Gulp and Webpack configuration files accordingly.
2. Previously, our downloaded packages included only one demo. We decided to include two demos in one package to allow users to test both without downloading a similar codebase. Users can build assets for demo1, update the configuration, and test demo1, then repeat the process for demo30. We appreciate your suggestion, but we will likely maintain this approach in future releases. However, we will simplify the process so that by executing a single command, you can build assets and switch between demos more easily.
3. We are considering making KTTheme available as a NuGet package. If there is sufficient demand, we will implement this in feature releases.