[Stubs] How to create full Module using laravel-starter-stubs

[DeRaja]

Hello!

I cannot generate a Module properly because it does not use stubs from laravel-starter-stubs directory. Currently, there is one Controller in Modules/Blog/Http/Controllers in the new installation. But there are Controllers in the new installation in Modules/Blog/Http/Controllers/Backend as well as Modules/Blog/Http/Controllers/Frontend. So my question is: How to force a generation of a Module using stubs having seperate Frontend and Backend in different directories?

[nasirkhan]

Can you please elaborate the issue you are referring to? Nasir Khan Saikat https://nasirkhn.com

…

On Wed, Jan 25, 2023, 4:19 AM Deepak ***@***.***> wrote: — Reply to this email directly, view it on GitHub <#380>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADA5O2ALVZGK3XROVX6QVTWUBINLANCNFSM6AAAAAAUFUCGVY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[DeRaja]

Hello nasir!

Vow! I found my mistake.I had wrongly used:

php artisan module:make Blog

Now, I used:

php artisan module:build Blog

This is a learning lesson for everyone in the future:
There is difference in using generation commands with module:make and module:build. They will create Modules with different stubs.

So I will close this issue.

[nasirkhan]

@DeRaja thank you for finding the solution by yourself.

Actually I have plans to build a new module manager and remove the previous one. But unfortunately I could not manage enough time to build a complete module manager package, rather build a partial one. The new package helps to generate new modules with similar structure with the existing modules. I hope I will be able to complete the new package soon.

If you are interested, you may contribute to Laravel Starter and the new package as well.

[DeRaja]

Hello Nasir!

If you are interested, you may contribute to Laravel Starter and the new package as well.

Yes, I will contribute. But it will be limited as a tester and (indepth) reporter. I am not a php coder.

But if you want me to write docs in english and add it to this project, I can.

Actually I have plans to build a new module manager and remove the previous one. But unfortunately I could not manage enough time to build a complete module manager package, rather build a partial one.

What all you have achieved is already gigantic. If that remains as it is, that is fine. But there are other so many areas that also requires more basic features

They are also be very fundamental and extremely necessary for a starter.
Here is my suggestion, although a bit off topic:
1)
One could be theme manager. Multiple thems could be mapped to multiple modules or domains from the admin. The views in every module are there.
But that mapping in admin is missing.
2)
Second could be a domain manager for multisite.
Multisite is a MUST in this project and this could be made available from admin itself. One of the best package on multisite of all other open source, as I have analysed from many aspects is:

https://github.com/gecche/laravel-multidomain

If this could be tightly integrated, that would be beautiful.
NB: I am not looking for any direct or indirect help in this direction. I am developing my own concept.
3)
Third is a Language Switcher in the frontend Blade templates as default.
This is a starter thing and every starter will require, if the installation is language sensitive.
4)
Frondend Menu configurator, to be done from Backend.

There are a few more but above four are very basic things that every starter (like me) will require.

Anyway, I am too happy to use your valuable and amazing work and will support it in the way I can.

Thanks again.

[nasirkhan]

@DeRaja Thanks for your feedback

New feature suggestions are really helpful. I was listing some of the future plans in #269 . I added your suggestions there.

1. Theme manage: I also planned to do this, but could not complete it yet.
2. Multisite: This is a basic starter, I think multi site/ multi tenant is an advance feature. though i added this on the future plan
3. Language Switcher: It is already implemented. You can access this from the backend. There is not much text available and did not implemented there. But as it is available in the core, you just have to use the @lang in the blade files.
4. Visual Menu Manager: I also think it is a useful feature, but again not developed yet.