Moonshine in a custom Cms

[stevebrainng]

Hi everyone, nice work here.

So this is simple, We're building a custom cms, with multi-plugin support and filter hooks system and all the cool stuffs. The choice of an Admin back-office for this kind of platform is obviously build from scratch.

But considering the time limitations I have to release the first version originally went ahead with Filament and to an extent it serves our use case Because plugins could just use the plugin provider from filament and register panel namespaces but with some limitations.

I love the UI MoonShine has and level of customization + design philosophy, but I'm still considering how different plugins should use MoonShine when they need to individually need to work independently. My first thought was cloning MoonShine and taking over from there, but since the project is still relatively new, there might be breaking changes in the nearest future.

NB: plugins are designed in away that they could be uninstalled and the system still function and plugins are in plugins path, packages may also use the panel in packages path. plugins are installed from Admin panel, zip or marketplace.

What do you guys think, any thought on this?

I have not used the MoonShine project yet, still just exploring it, but I like it more than Filament because it API for resources seem more simpler

[lee-to]

Hi! Thanks! MoonShine is highly customizable. We have Laravel as a separate package, so the data can be anything, and the framework as a whole can be anything! MoonShine works with primitive data, but we already have Eloquent support for Laravel, but you can retrieve data via API, even sockets! If you choose MoonShine, you won't have any problems with the architecture! Any other admin panels will be a hassle. If you have sufficient development experience, you can easily create a CMS based on MoonShine! If you have any issues, you can write to the issues or discuss them, and I'll help you or fix them.

[stevebrainng]

Thanks for your response.

I'm trying to understand what you mean by Laravel as a separate package.

I also tried looking into the source code to see how I could start the installation, generally I wouldn't use composer require because it's not on the Laravel default installation, our CMS removed the app/ we extended the Laravel application container, and using moonshine would be installed in our vendor/panel package and we make all the implementations from there.

I'm still thinking about how we can make use of our filter/action hooks system within the panel for plugin extensibility.

[lee-to]

Thanks for your response.

I'm trying to understand what you mean by Laravel as a separate package.

I also tried looking into the source code to see how I could start the installation, generally I wouldn't use composer require because it's not on the Laravel default installation, our CMS removed the app/ we extended the Laravel application container, and using moonshine would be installed in our vendor/panel package and we make all the implementations from there.

I'm still thinking about how we can make use of our filter/action hooks system within the panel for plugin extensibility.

https://github.com/moonshine-software/symfony

Here’s an example of MoonShine based on Symfony — all you need to do is resolve everything required in the container.

[stevebrainng]

Hi, Thanks for the info you shared, I tried setting up the Moonshine in our cms with just using the composer require and doing everything from scratch and I'm having some issues spinning up a working prototype.

@lee-to Please can you come up with a Laravel installation with a minimal dashboard up and running?
I got the idea for the Symfony repo you shared, but some how I just couldn't get it to work on Laravel.

The idea is to use Moonshine under the hood, and extends it's classes from our cms vendor/panel so other plugins could easily use classes from vendor/panel. while Moonshine run under the hood.

Another thing is that we don't use the App\ namepace. that folder is completely useless to the cms.
And individual plugins or packages will need to be able to register thier own namespaces for loading panel resources, pages or crud-resources.

[stevebrainng]

It's based on Laravel, but we've extended the default Laravel 12.x application kernel, so we don't use the App/ at all.

[lee-to]

It's based on Laravel, but we've extended the default Laravel 12.x application kernel, so we don't use the App/ at all.

Well then I don't understand your questions. Moonshine is a default Laravel app. Install it as described here: https://github.com/moonshine-software/app and customize it further. Moonshine can be located in any directory and under any namespace. This requires minimal developer skills.

[lee-to]

You can put Moonshine in src and put each Resource/Page in its own module or domain.

[lee-to]

Unfortunately, I can't provide textual advice on super fundamental basic things in development.

[stevebrainng]

Moonshine is not tied to namespaces, all information is in the documentation

I guess because I'm thinking about MoonShine the Filament way, I will try looking further at using it in a first-party Laravel application.