Migrate admin parts to Filament

[driesvints]

Let's try out Filament and move our own admin panels to it. This should provide us with a much more powerful admin backend.

https://filamentphp.com

[ZeeBuilder]

I love this application and am experimenting with filament myself.

[ijpatricio]

@driesvints just for sanity check, do you still need this?

[driesvints]

@ijpatricio yes would love this.

[ijpatricio]

I think I can help!

Replacing these routes only, right?
Any guidance I should follow?

[driesvints]

yes! Well I think /ban and /unban also applies to user profiles so unsure if those can be entirely removed. And the article manipulation actions are also available on the article detail page.

[ijpatricio]

So I started the repo locally.

There's much to grasp, but if you can provide some insights, this shall be somewhat quick!

The Ban/Unban routes are protected by the VerifyAdmins middleware).
I think that what applies to user profiles, must be the Block action. (not Ban).

So, we can outline in topics the features that will kickstart the thing, and then you can review and adjust.
These would guide the testing for the panel.

Already done:

• Install Filament
• Auto-login (pre-filled form) in local environment, for the [email protected] user
• Primary color with Lio-500
• Filament panel access restriction
• Started the firs User resource (automatically generated form and table from DB analysis)
  Feature parity with the current admin views:
• User "module"
  • Index (table)
    • Fields: name, role, joined_on
    • Search
  • Show
    • Profile info: name, joined_on, description, socials
    • Statistics: counts{threads, replies, solutions, articles}
    • Article list
    • Threads posted
    • Replies posted
    • Actions: ban, unban
• Articles "module"
  • Index (table)
    • Fields: author, title, submitted_on
    • Actions: approve, disapprove, decline, togglePinnedStatus\
• Replies "module"
  • [ ]Index (table)
    • Fields: author, thred, content, updated
    • Actions: edit, delete, mark_spam

It's not all explicit on the routes as I thought, so we can iterate on this.
I probably missed some stuff, so this can go iteratively, I think.
What do you think?

Just started #1179

Have some screenshots:

[ijpatricio]

Forgot to say:

As you can check in app/Providers/Filament/AdminPanelProvider.php, I set the admin panel prefix as cp, so we can have both current areas, "/admin" (current) and "/cp" (Filament).

Just temporarily.

[ijpatricio]

Hey @driesvints

Did you receive this notification? #983 (comment)

I forgot to mention you before...

[driesvints]

heya I did. Just struggling to find time to dig into all of this. I'll try to as soon as I find some time. Thanks for your effort!