Statamic or Filament as CMS, and maybe more, for my App
Hey. I'm thinking of using Statamic or Filament with an app I'm building to supplement it by acting as a CMS for things like creating and updating plans/tiers, and other content the app could use. I don't want to have to manage this information on the backend and would like to involve other team members in the management of this kind of data.
Recommendations?
9 Replies
Statamic is an amazing CMS that already has all the main features you might need, and you should probably use their paid version.
Filament is a nice tool to create the features you need, but you have to create them yourself or use third-party plugins.
Probably the best option to create a CMS is not to reinvent the wheel. And the most fun way with Filament, the interesting thing about this tool is that it will be easier for you to add features outside of what concerns the CMS.
So...Filament is shitty? I'm probably biased, but I think it's pretty great, to be honest 😉
Honestly though, I think both Statamic and Filament are great solutions for handling backend administrative work. Obviously I'm going to say that I'd use Filament for this any day of the week over Statamic, but as long as you're productive, I think you could get to the same place with both tools as far as a CMS goes.
One thing I'm admittedly not entirely sure about Statamic (though someone who has used it more might be able to tell me) is how it scales to functionality that isn't part of a CMS. I do know that Filament is fantastic for use-cases outside of a CMS as well, having built a lot of admin workflows separate from a CMS in the past. You could even split these features (CMS and anything else) into multiple panels with Filament, depending on who would need access, logical groupings, etc. etc.
Filament is incredible, I would personally choose it over any other panel, I don't know how you came to that conclusion.
Maybe it's because my English is bad and I express myself poorly.
What I'm getting at is if you want a CMS ready for your project, Statamic or Twill CMS, even WordPress, are options that solve your problem from the root.
Filament, while it has good plugins for creating incredible CMSs, you will have to work more, it will be more fun, and you will achieve results more similar to what you imagine.
In the end, Filament is flexible and prepared to create any system, I think that's the difference with Statamic.
Not to mention it's fully open-source!
Questions I would personally ask myself:
Do we want to quickly resolve something as simple as a CMS? Use a CMS.
Do we want to add functionalities outside of what would be a CMS, such as CRM, workflows, etc.? Use Filament.
I figured that wasn't what you actually meant–no worries 👍
I agree with your questions though–if you need a CMS and only a CMS, Filament is a great tool, but so is Statamic!
Alex, haha, I have no words, I understood the meaning, that wasn't the word I wanted to use.
Typos sneak up on all of us 🤣
For what it's worth, your english is really great! Better than most who speak english as a first language 😅
I only rely on AI, which has also betrayed me.
I want more than what a CMS has to offer, I want to build more of a CRM and some custom views for our internal team.
By the way, what's the fastest way to make an actual CRM out of laravel, i.e., no manual migrations and being able to add fields and their type from a UI. Is that possible with Filament?
It’s possible, but it will definitely require a lot more manual setup on your part. Filament is still just laravel under the hood, so anything you can do with laravel can be utilized with filament.