"Apart from that I find the source to be the best docs out there." Excellent point.

The docs should point to where they are referencing.

Speaking of which, I can't seem to find the link to the github repo within the docs any more.

@andy it's under Community - Github at the top if that's what you are looking for.

@Ruffles UGH! Thanks.

However the github repository is not listed under "# Install Laravel" section. This is a simple fix.

I don't know if it's because I started with Laravel 3 or because I did a lot of research on Object Oriented PHP before trying any framework but I've always found the Laravel Docs to be top notch and extremely easy to understand. As a matter of fact I chose laravel in the beginning because of that, the great documentation.

In my personal opinion I feel that CI and Yii made things outside their scope incredibly difficult and were undocumented. With Laravel I could choose whatever tools I preferred and all I needed to do to acomplish what I wanted was to read the docs.

Laracasts is an awesome resource to learn about best practices and other important concepts and with the 5.1 laravel docs (which you can preview easily choosing 'Master' in the docs page) everything is getting even better.

@sitesense

You right !

But the information over the Internet sometime So Different from each other, only on Laracasts their some good videos in "Archive" because of that . So the last Place to trust :

1. Laravel Docs (Thats why it must to be for newbies too)
2. update videos on Laracasts.com

I believe that Problem significant decrease over time :)

I consider myself a newbie but not so much that I want the documentation to do it all for me and I think that was already mentioned. There is a difference between someone who needs the documentation to be clear and concise vs the person who wants the documentation to both teach and build the app for you.

@sos99 - I hate being that guy but reading this thread it seems you are probably more the latter than former. No patience to learn, just want a copy and paste of code from the docs.

@SCC

I'm Appreciate your honesty , this is not the case if it that case i copy & past all from every source . and ask a lot of specific questions on Laravel.io or Laracasts forum.

If their are sources from you or from any users Please recommend about it.

Honestly, the best place is here. Take a look at the videos, it's really all you need, @JeffreyWay has a great presentation style and assumes little about ability when talking things through.

If you are unable to purchase a subscription there are a good number of free tutorials provided. Also I was just looking at the master docs on laravel.com and quite a few have been updated to be more example driven.

@sitesense - A brilliantly valid and well articulated point and I remember when I was 13, spending my pocket money on a "PHP Cookbook" hehe! Now you can just ask Stackoverflow.

I've been with Laracasts for about 6 months now and I've noticed a deterioration in the average standard of the question on the site; into what I would define as 'more basic'. To myself, that's a sign of the success that Laravel is. That it opens up the door of artisan web development to people who do not have the technical knowledge or expertise that they would have needed say, 2-3 years ago. The things you can accomplish with Laravel are profound!

My advice to people reading the Laravel docs and not understanding them and to people who post questions to which members of the Laracasts community reply to with 1 line of code, is this...Whilst it's quicker to ask a question so you can clear the hurdle you're facing, by not reading about wider PHP development, by not developing the neural pathways that come with 'thinking for oneself', you're just ensuring there will be many more hurdles in your path in future weeks, future months and future projects.

The old adage of what you put in, you get out applies to education and work and especially coding. On rare occasions have I ever read the Laravel docs and not understood the context or the environment within which, I could implement the topic that is being discussed. I am by no means a good programmer. I'm a hobbyist programmer who does it in his spare time and quite frankly is shooting far beyond his reach thanks to Laravel. But I have taken the time to learn PHP, to read books by Taylor, Jeffrey and Dayle Rees (great for beginners!), to watch Jeff's videos from START to FINISH and to think for myself.

If you find yourself disagreeing with myself then I would ask for you to take the time and reflect on whether that may be because you're not investing your time in reading and learning and I've hit a nerve. Or perhaps I'm wildly off the mark.

@sos99 - By asking for sources, you're kinda validating @SCC's point about "No patience to learn, just want a copy and paste of code from the docs"...just google "learn Laravel" or "learn PHP" and take it from there

@olimorris

haha !

Personally I don't care what do you or anybody else thinking about me but i'm promise if i want to copy and past i just send a lot of spastic questions with code and wait for the answers , and i don't doing it . this is not my way. :)

Over the web their is a lot of not relevant or not update staff Only more confusing than helping

If their is any good staff over the web (Except Laracasts) Please recommend about it.

Hello, before laravel, last year, i was on codeigniter, the doc was différent than now ( the project was transfered) and my best doc was a cheatsheet and stackoverflow and a rule "don't touch the system directory".

Now with laravel, all is more clear, the doc, the ecosystem, the community and all great stuff around! So I recommend laracasts, the doc is clear.

I wouldn't say the Laravel Docs are lacking, it's completely fine for a basic [setup] of things. Rather people want more in-depth examples and tutorials of the section they are stuck on. I'd say that laracasts and (a bunch of) other miscellaneous websites offer a variety of examples to look through, it's just that it's not in one central location, so finding a solution for some things seem near impossible (which it isnt)

Overall the only problem people "should" be facing is having to update to a major or semi-major update, because you then don't know what has changed within the API, which leaves room for broken implementations. Then again Laravel does tell you what methods isn't found, which leads you to build an alternate method (or sometimes a new method they add will allow you to extend your method rather than use it, which is also good)

Hopefully, this comment can be seen as constructive, as that is it's intent. The problem I believe most people have with Laravel docs when coming from a CI background is that the instruction and examples often lack context. There will be some example code, but little indication of where the example code is supposed to go. And then, if you ask someone, you get an answer like, "You can put it pretty much anywhere," which is pretty much a non-answer.

The 5.1 docs are a great improvement (THANKS!), but perhaps it would be wise to consider that many of us are coming from years of experience in other environments, and though we understand the concepts, we're still trying to get a handle on how things fit together. And, we just want to get a working app coded quickly, instead of learning the inner workings of the framework before we can begin.

@BrianH781

you get an answer like, "You can put it pretty much anywhere," which is pretty much a non-answer

From documentation...First paragraph.

By default, this directory is namespaced under App and is autoloaded by Composer using the PSR-4 autoloading standard. - http://laravel.com/docs/5.1/structure#the-app-directory

Maybe people have different ways they learn and remember things, but honestly if you're (general you) having issues after watching free videos provided by Laracasts + Official Docs + All the rest of the resources from people like Matt Stauffer you might reconsider all of this.

Bitching and moaning. That's all this is.

In my opinion the problem is that extensive code samples of the kind people expect become inherently opinionated. The docs need to show you what laravel is, what it can do, and (hopefully) give you a decent understanding of how it works. What the docs can't do is tell you how to structure and build your application. That's a decision you have to take, and if you need guidance on that, it's available all over the laravel community of blogs and tutorials.

I usually use Laravel docs as a reference and refresher. Laracasts and Google help me grasp the concepts and the documentation helps refresh/extend upon those concepts. It's so damn easy (in my opinion) to find what you need to know because the laravel community is so big!

90% of the times the docs will tell me what I need to know otherwise... "crtl + t", "laracasts.com", "ENTER"

:)

Not bitching and moaning... just stating what I hear from others and what I've experienced myself. I guess you failed to read the first sentence of my post.

Even if there were more examples, there would still be complaining about how they aren't the right examples.

The best examples are the code itself. If you haven't opened up your code editor and gone through the source, you can't blame anyone but yourself for not know what is going on.

Maybe we can get Taylor to go ahead and just code our apps for us as well...

The examples have slowly gotten better. However, many should be gone over to see if a better example could be used instead.

Going to the code as the ultimate reference is actually really a good but having experience as an educator that method doesn't fit everybody. We all have different ways and speeds that we learn. I personally prefer digging into a well coded app and learn from other's put-in-practice efforts.

I'm a complete noob when it comes to coding. I started helping out a couple years ago on a gaming clan website because they needed help. So I learned what I could of php and went from there. What I coded was complete spaghetti garbage code (as I've come to learn now). At the time, I had no idea what OOP is (I still have a hard time grasping it sometimes), and yet when I stumbled upon Laravel about a year or so ago I was inspired to unlearn all my old bad coding habits and start fresh. I wanted to completely redo the clan's website properly and make it better, easier to use, and easier to maintain. Overwhelmed myself a bit. Still plugging along at that project, but it's slow. However, getting back on point. I've not seen other frameworks docs, as everything else I searched for just looked a bit too overwhelming, but when I found Laravel, their docs just clicked and made sense to me. I subbed to Laracasts to get a better idea of what's going on and to learn better practices. So while maybe the docs could use better examples, the examples they have get right to the point and show you exactly what is being described to you. It's not meant to show you every possibility. That would be a monumental task to put in the docs. Thankfully, that's why there's the API docs as well. So you can follow the path of code and learn. I still have a hard time understanding all the API stuff there, but man, it's been a fun ride learning so far. :D I'm actually glad the docs don't have complete examples so you can C&P into your project. That defeats the whole purpose of learning. If you're not willing to learn the framework you are using, there's no amount of change to the docs that will help you. ::drops his two cents in the jar::