Laravel vs Buddypress

Watch all related lessons on Laracasts?

Going through them right now, they answered a lot of my questions.

Thanks

Comparing an app to a framework is a bit different.

1. I'd write a list of all the functionality that buddypress has

A. look for a possible app/package that already has most of what you need done B. look for packages that fulfill your check box needs one-by-one

1. fill in the remaining missing pieces with your own code.

I'd also look at http://laraveldaily.com/review-top-5-laravel-based-cmss/ lavalite is rather rough although looks smooth and typi looks rough but is rather more polished but missing all the bells and whistles. Asgard and Typi are rather similar (in general). October and Pyro would be a good match up and I'd say that Oktober is ahead since it's been out for the public longer (Pyro is older but is a recent laravel convert). The last is orchestra which isn't on the list but is a general platform to start with.

Searching through github also helps but lots of repos that are either just an initial commit or were probablymoved to a private repo after a customer saw the first rough version.

You mentioned "the following features" then there was nothing there! I'm familiar with both, and have programmed in both. Quite different worlds.

Older but a good one still

https://laracasts.com/series/build-a-laravel-app-from-scratch

I wouldn't take it as production code as Jeffery uses different ways of doing things as a teaching technique for different patterns etc I think it should be more consistent use of said patterns and style. plus I think it's 4.1. But a base to build off of.

Reason I personally don't care for Wordpress is it takes some knowledge and tweaking imo to make it a bit more secure then a fresh install. Routes and access points are common knowledge for hackers looking to exploit it.

Buddy press is pretty good but highly opinionated and hard to configure time wise. Put take that with a grain of salt. I'm so used to Laravel it's easier and many times more efficent for me to code it myself (or so I think!).