Just bought the course 🎉 thanks for generous discount! This is my third course I bought from you(git a job, WordPress and now laravel). You are great instructor! Keep up being you!
I work with WordPress and React (obviously I studied your courses on the subject) And I don't think that I plan to work with laravel, but I will still buy the course and watch it because I will learn to program better that's for sure It will be very interesting to see how the same application we built with nodejs and react built with a completely different technology
Thanks for supporting the courses! You bring up a good point, it's the same social media application from the other courses, but I felt much more at ease building it with Laravel because we weren't having to constantly reinvent the wheel. We can sort of relax knowing that Laravel has "already thought of that" for so many details and features (compared to building the back-end from scratch with Node/Express.js).
For sure it's great course! I learned (am still learning) Js, git, Wordpress with your courses. All are great!!! Waiting for SvelteKit + Supabase course. It would be great as those two are getting momentum :)
Dear Brad.. you are our teacher.!! Of course we will buy our teachers lesson ..of course we will master laravel because of you.!! Thanks a lot one more time.!
All I can do is buy it now and learn from Brad, thank you Brad for bringing me what started out as a graphic designer into the professional world of web development!
Just bought the course, thank you for the coupon! I have to maintenance I lot of WP sites built with Laravel and even though this is not a WP Laravel course, I know this is going to be so helpful. I had a 1:1 with my team lead today and I told him how much your WP course has helped me improve in my work . Thank you so much and thanks for the comment regarding the first year, appreciate it.
Didn't even finish the video and already purchased the course 😉Glad that you will be talking about Docker. I think I learned my way around Docker pretty well but I would still love to see a whole Docker course of yours because I alway learn new stuff or how to do things a little bit better when I watch your courses. I think a life without Docker is possible but pointless 😉
This is awesome!! I was literally searching for Laravel courses last night on Udemy. Decided not to purchase any because they didn't fit my needs or were out of date. While there might be a decent amount of review for me in regards to basic CRUD, search, etc, your courses are always so thorough I'm sure it will be very worthwhile. The live chat, docker, and deployment processes look really intriguing too! Those were all the next steps in my journey, so very pumped to take this!!
I'm glad the timing worked out! I don't think I mentioned it in the video, but the course also covers the queue system, events & listeners, automated task scheduling and more. The deployment / devOps / Linux VPS section at the end was a lot of fun for me to build, I'm thinking it will be a fun new skillset for any devs similar to me to pickup (usually more of a focus on front-end dev, JS, etc...).
Can't wait. Coming up on my first year as a junior WP frontend developer. It has been a challenging year, your courses have made a huge difference for me. I have had two not so great lead devs and your courses have really been invaluable. I should be moving onto a new agency within the next 6 months, your WP course has increased my confidence and I am pumped for the Laravel course. Really appreciate you and your work!!
Brought it on blackfriday when i was looking through the old course on wordpress FSE! was surprise to find a new course that you have yet to announce :)
Thanks so much! I noticed that someone had joined before I announced it, that was so exciting for me, really appreciate it. I hope the course is helpful!
Thanks Jeremy! Here's a coupon that's good for another 2 days, and I also plan on releasing a new video on RU-vid soon which will also have updated coupons: www.udemy.com/course/lets-learn-laravel-a-guided-path-for-beginners/?couponCode=EMAILDEAL
Do you recommend to take this course with no PHP experience? Don't worry about the answer. I saw that you already did in previous replies. (I bought the course by the way. I will buy whatever you do. I know the quality is there :) )
Interesting, I watched almost all of your courses. I'm sure this one will be a great addition. I very often see Laravel + Vue stack, is there a big difference between Laravel + Vue and Laravel + React? What are your thoughts on why Laravel + Vue is more popular?
I've also noticed a lot of Laravel + Vue pairings, I believe the community prefers Vue, but the nice thing is that it's more of an "unofficial" preference than an official one. The same way that the community likes TailwindCSS but you can easily use any CSS tool you prefer with the built-in Vite setup. If you checkout the Laravel docs page on "frontend" you'll see their official recommendation is to use Livewire or Inertia instead of Vue or React. They admit that many developers prefer to use Vue or React but end by saying this about maintaining a traditional separate Vue or React front-end: "While these problems are not insurmountable, we don't believe it's a productive or enjoyable way to develop applications." I'd have to agree with them wholeheartedly. If your site just needs tiny bits of interactivity here and there, then Vue or React is perfect, but if you want your entire site to have SPA features and also have perfect SEO and bundle-size I'd probably just use Laravel as the back-end and Next.js as the frontend / proxy. If I had to guess why the community seems to favor Vue over React, and again I'm just guessing, it would be that Vue is simpler to pickup and start getting immediate value out of; whereas React takes more effort to complete even basic tasks. For example, if you don't need an entire site-wide SPA app, and you instead just want bits of interactivity here and there, I think Vue is a really nice pairing with a traditional Laravel monolith site. You use Blade for the majority of pages which gives you excellent SEO, and then just the pages / areas that need interactivity can come to life with Vue, and that's going to require less effort than doing the same thing with React. I'm a big fan of React but I'm the first to admit that it's not always the easiest library to wrap your mind around. I was planning on releasing a video for RU-vid where I show how to integrate Tailwind + React into an existing Laravel project.
Hi, at the end of the course we do learn how to setup token-based API endpoints that let you login, create a post, and delete your own posts. We use Insomnia Rest (you could use Postman) to test the routes. The idea is that you could use those routes to power the data-needs of a mobile app or SPA, but I felt like actually creating a mobile app or SPA in the course was a bit outside the context of staying focused on Laravel itself. Having said that, there is a section in the course where we turn the profile-page links into a SPA that uses client-side JS for fetching and managing the browser's address bar and back button. Perhaps on RU-vid I can do a mini-series on combining Laravel with something more robust like ReactRouter.
Did you think is still worth to learn Wordpress, or maybe better some MERN stack like Strapi? Will you make Woocommerce course like your Wordpress course?
I agree with Ivan. If you are creating brochure type of websites for small / local businesses I think it's impossible to beat WordPress, and I 100% recommend the WordPress path. However, if you want to land a great dev job working on more custom/bespoke apps I think Laravel is a great path. I think it just depends on someone's goal.
Hi Brad thanks for the course. A few questions: version of php? which version of laravel are you using? are you using laravel with mix or vite^? which database? this info should be in What you'll learn section. i will add this course to my wishlist, unfortunately at the black Friday week already bought some others courses, where one of them is about a php framework ( not laravel). Maybe next month or when i finished at least one of the course then i will buy it. And before this course would be more relevant a PHP and SQL course ( dont make any sense to pick this course if you dont know this two languages, which should be requirement). But ok, at least for me. Any plans for a Docker course? thanks.
You're welcome! Hope the PHP framework course goes well! Those are all great questions for a more advanced student, but I think for a beginner (who the course is designed for) the questions don't matter. A beginner doesn't know what Mix and Vite are. A beginner doesn't know the difference between MySQL and Postgres. A beginner just knows they want to learn the newest / current version of PHP & Laravel (my plan is to update the course to cover any new big features in future releases). The main goal of the course is to make Laravel less scary and to encourage people to try it even if they only know HTML & CSS. For most basic queries you don't write SQL, you just call Eloquent methods. And for PHP, an intro to syntax lesson teaches you how to look inside objects for methods and properties and how to call static methods on classes. From there, the framework does most of the heavy lifting for basic tasks. I think there's tremendous value in taking the focus off of the specific languages and instead focusing on understanding how the puzzle pieces of a framework (that exist in all frameworks, not just Laravel) come together. And at the end of the course, if someone wants to go further, and become "intermediate" instead of beginner, they can learn more about PHP and SQL, but the idea is that now they'll have a real-world concrete mental model to plug those skills into. And perhaps they'll already have a new "junior dev" job at a Laravel shop, and can learn those more intermediate skills from the comfort of a new career path. I really like Docker for local dev purposes, and I've deployed low-traffic sites to use Docker containers for Node/Express apps, but I'd still need to learn way more about Orchestration / Kubernetes / auto spinning up more containers to meet traffic demands before I released a full course. Cheers, Brad
@@LearnWebCode Hi my questions are valid, independent of the experience who buy the course. Because When i buy a course i want to know if it is up to date with language or framework. For me would not make sense this course if is using old version php or laravel like php 7 and laravel 7, etc. About vite or mix, make sense the question because mean the course is not up to date with framework last breaking change which affect your front-end or assets and you are not take advantages of new feature like auto refreshing. even on php file changes. And for me, talking by experience, if you dont know the fundamentals of a language you will have bad time with a lib or framework or even worst no one will hire you if you dont pass the practical interview. If you choose to be a full stack dev, you should know the basics of languages on the stack. Even just front-end dont jump into css or js frameworks without basics first, because you find hard time tell which part is from language and which from lib or framework. So jump steps is bad. ;) Docker course, i am talking a course about fundamentals, enough to be able to create a dev env, no need, at least for me, the swarm or Kubernetes ( Orchestration) because majority of students will not use it. Docker and Docker compose would be enough, Some thing like you did with this course for Beginners. And if go to create the course, please dont just use node, use also php containers. Another thing, where is the course about learning css by using tailwind !!!!!! ;)
Yes, it was a course that I was waiting for a lot. But unfortunately it is no longer needed. still many thanks Instead, I'm waiting for React/Next.js course or videos now ehehhe. You are loved. Take care of yourself.
We don't cover it beyond the basics that you can (1) look inside an object for one of it's properties/methods with "->" and (2) that you can look inside a class itself to call one of its static functions with "::" I think that's part of the beauty of Laravel, it can be useful to you at any experience level, and just understanding the above two syntax details lets you work with all of the framework's classes / objects / features.
I think so, yes. There's a lesson early in the course where we're introduced to the very basics of PHP. After that, we do move fairly quickly with PHP, but every time there's a new syntax being introduced I try to point it out and take a moment to not rush over it. There is a bit of an assumption that you're familiar with some programming concepts in general (for example, JS) like strings of text, returning values in functions, etc... but for the most part the idea behind the course was that you don't need to know any PHP to start it! The beauty with Laravel is that for 95% of what we need to do in typical applications, it's really as simple as just looking inside objects and calling methods, or looking in arrays for the item you want, etc...
@@LearnWebCode I had to stop one of your courses on WP on Udemy (Unlocking the Power of Code), after weeks of learning couldn't move further. I must admit you have a deep knowledge on the subject but some stuff must be updated. Would be nice If someone could have a look at the code I wrote. Thanks
Hello My Dear Friends, Laravel is one of my best framework but it has less salary compared to other JS Frameworks. My advice is learn this as hobby not as a job for Professional.
When you mention JS frameworks are you referring to front-end or back-end frameworks? Front-end skills like React or Vue are always in-demand, and Node knowledge is always a plus, but when we're talking about server-side frameworks and salaries I can't imagine that a SailsJS dev is consistently more lucrative than a Laravel dev. If we're talking about JS frameworks like Next.js, I agree that is an amazing and in-demand skill, but it's a great combo with Laravel. You still need something to build your data models, permissions, endpoints, etc... and Laravel can do all of that and then Next.js can just be the proxy / front-end.
