I wish you had done this two years ago! You would have saved me lots of time and money. :)
I have had two WordPress sites and within months both got taken over by hackers. I hated working with it. I will give Statamic a try. I have looked at it a couple of times but the price put me off (among other things).
There are a lot of other Laravel-based CMSes. I am wondering, did you look at others that did not get mentioned here? Your "Other Alternative CMSs" lesson just mentions non-Laravel options (other than Filament).
Anyway, thank you and I am going to go look at Statamic again right now. I agree with you about Filament and am considering working with it for this, although I find its code confusing to figure out and I find its page architecture quite inflexible.
so, all of these options beyond wordpress looked like a pain to use.
I was thinking this series was going to be how to recreate a blog in laravel. but it's all about implementing 3rd party systems which have their own syntax that doesn't look like it would work well with existing laravel app.
so i guess the question is, is a cms in laravel that difficult to build? it still uses database connections and all. Cms just seem to be more like completed applications. granted I wouldn't know how to set up things like a drag and drop builder in laravel, but isn't that similar to components if we were designing ourselves? then I imagine a little javascript? why did all the systems you reviewed seem to use their own view syntax and such? what do those systems do that laravel can't?
Yes, a PROPER CMS is difficult to build. Really difficult. It's mostly about front-end UX for the user to work with text/images conveniently, and WordPress perfected a lot of small "invisible" details that devs don't fully appreciate.
Also, CMS is about ecosystem of plugins/themes, where again WordPress shines.
So, with that review, I was trying to answer the question - if any of those Laravel CMSs gives the user experience of WordPress and the answer is No.
And I can't answer your philosophical questions about "why" systems do this and that. I guess the only way for you to answer your question is if you try to build CMS yourself and see for yourself all those small details.
gotcha... yeah that was the main thing that confused me. cause at the very basic level, a blog appears to be just an article/post model with a few related models for comments and tags. which seems no different than everything else you have built in your videos.
so would you classify a cms as just a completed applications where everything is already configured for the end user?
I'm not doubting it is difficult, i guess I'm just wondering what skills or considerations I would be needing to classify an app as a cms vs a typical laravel app.
is a typical CRUD system not managing content?
themes can be made via differnt tailwind configurations or block utilization. right? not trying to debate, just trying to figure out where the distinction lies.
I always thought the various admin panels were CMS's.
and whether that is customer or content MS just depended on the underlying models
I wish you had done this two years ago! You would have saved me lots of time and money. :)
I have had two WordPress sites and within months both got taken over by hackers. I hated working with it. I will give Statamic a try. I have looked at it a couple of times but the price put me off (among other things).
There are a lot of other Laravel-based CMSes. I am wondering, did you look at others that did not get mentioned here? Your "Other Alternative CMSs" lesson just mentions non-Laravel options (other than Filament).
Anyway, thank you and I am going to go look at Statamic again right now. I agree with you about Filament and am considering working with it for this, although I find its code confusing to figure out and I find its page architecture quite inflexible.
I've looked at more of them but the other ones were worse than the ones I've kept in the review. Which one do you mean that stood out for you?
so, all of these options beyond wordpress looked like a pain to use.
I was thinking this series was going to be how to recreate a blog in laravel. but it's all about implementing 3rd party systems which have their own syntax that doesn't look like it would work well with existing laravel app.
so i guess the question is, is a cms in laravel that difficult to build? it still uses database connections and all. Cms just seem to be more like completed applications. granted I wouldn't know how to set up things like a drag and drop builder in laravel, but isn't that similar to components if we were designing ourselves? then I imagine a little javascript? why did all the systems you reviewed seem to use their own view syntax and such? what do those systems do that laravel can't?
Yes, a PROPER CMS is difficult to build. Really difficult. It's mostly about front-end UX for the user to work with text/images conveniently, and WordPress perfected a lot of small "invisible" details that devs don't fully appreciate.
Also, CMS is about ecosystem of plugins/themes, where again WordPress shines.
So, with that review, I was trying to answer the question - if any of those Laravel CMSs gives the user experience of WordPress and the answer is No.
And I can't answer your philosophical questions about "why" systems do this and that. I guess the only way for you to answer your question is if you try to build CMS yourself and see for yourself all those small details.
gotcha... yeah that was the main thing that confused me. cause at the very basic level, a blog appears to be just an article/post model with a few related models for comments and tags. which seems no different than everything else you have built in your videos.
so would you classify a cms as just a completed applications where everything is already configured for the end user?
I'm not doubting it is difficult, i guess I'm just wondering what skills or considerations I would be needing to classify an app as a cms vs a typical laravel app.
is a typical CRUD system not managing content?
themes can be made via differnt tailwind configurations or block utilization. right? not trying to debate, just trying to figure out where the distinction lies.
I always thought the various admin panels were CMS's.
and whether that is customer or content MS just depended on the underlying models