Unlimited WordPress themes, graphics, videos & courses! Unlimited asset downloads! From $16.50/m
by
Lessons:9Length:41 minutes
Laravel400
  • Overview
  • Transcript

4.1 Conclusion

That's it! Just a few finishing touches and our site is ready to launch.

Thanks for following along. My name is Jason Lewis, and from all of us here at Envato Tuts+, thanks for watching.

4.1 Conclusion

So this has been a short course on how to build a functional website in Laravel. We've looked at quite a few things and in the process,we've covered several important topics. We now have a good understanding of how we can use Blade to create templates and have other views extend from this templates. We can use sections to yield contents from one view inside of another. We also looked at how we can set up our routes, and how we can use named routes to make linking and redirecting easier and more feature proof. In this course, we didn't look at using controllers instead, we did all of our routing logic within our route closures. For small and simple websites or applications, this is perfectly fine. However, once you start developing more complex applications. You may want to extract all of your logic to controllers. That way, you don't end up with a huge routes file. We then looked at creating a contact form, which introduced us to using the request instance to fetch input data, and how we can validate that incoming data. For this course, we used a fairly traditional and easy way of validating our data by instantiating a validater and passing in our input and our rules. If you were to use controllers, there's actually a nicer way of doing it by using method dependency injection. By taking advantage of this method dependency injection, we can use what's called a form request. And it might sound a bit scary but it's actually not. Basically, all it is, is a class where you define rules. And then you simply type into it as a method dependency for your route. Laravel is pretty smart, and it will automatically validate the request input against the rules before any of the code within that method is even executed. The benefit here is that you would have abstracted your validation logic outside of your controls which helps keep them thin and easy to follow. Finally, we implement emailing. And emailing in Laravel has always been fairly bloated in that you had a bunch of closures within your routing logic, and it wasn't very pretty. Most people had some sort of abstraction layer around it to make it a little bit more bearable. Since Laravel 5.3 is coming out, we've seen that we could now use what's called a mailable. And it's just a class, but it let's us build and configure emails in an isolated environment. Again, this keeps our controllers thin and allows us to easily reuse mailables throughout our web applications. So there you have it, we've achieved a lot in a very short amount of time. And there's obviously a whole lot more that we could've done but hopefully, this short course has given you some ideas and some inspiration to develop something awesome. Once again, my name is Jason Lewis. I've been your instructor on this course and I hope you've learned something.

Back to the top