I set up this newsletter a while ago, as Buttondown keeps reminding me, and have yet to do anything with it. So let’s change that.

Firstly, I just want it to be noted that I’m really not good with the whole flowery marketing talk, and I’ve always unapologetically been myself. If you were expecting something else, my apologies.

Hidden & Undocumented

Laravel is often praised for its documentation, with its success owing in part to that very thing. It is, however, not without its issues.

The documentation is a great starting point, but it often fails to go beyond the simple, basic topics, often missing features and functionality entirely. I’m currently working on something to help address this, a place for people that want to go beyond the docs, without spending months digging through every line of code.

This is quite the undertaking, so it’s going to be some time before anything is at a point where you can see it, let alone get value from it. So, in the interim, I’m using the notes and bits from that to create a series of articles that covers topics that are underdocumented, undocumented, or just completely hidden from the public.

The first article in the series covers a feature buried deep in the docs, whose usage barely has its surface scratched!

The second article in the series covers functionality that is almost entirely missing from the documentation. In the spirit of openness, I should add that I actually build this functionality, so it’s probably my fault that it isn’t documented!

The third instalment (todays), is the most complex one so far, and it’s more informational than instructional. In it, we explore the different ways to manually resolve dependencies and services in Laravel, and the differences between them.

Next Week?

Because you lovely people have signed up to the newsletter, I’ll share with you my plans for next week’s article. Very in-depth plans that I didn’t at all come up with literally an hour ago while helping someone in the Laravel discord.

Well, next week I’m going to talk about auth guards in Laravel, how they work, the default options, and how you can use multiple guards at once. This is all something the docs are lacking in. It’s also pretty surprising that I haven’t already covered this topic, especially since my first step into the world of open-source was with a package called Multiauth that added this very functionality to Laravel!

Suggestions? Ideas? Feedback?

If you’ve any ideas for content to cover, suggestions for ways to do things, or even feedback (good or bad) on what has been done so far, please don’t hesitate to get in touch using the links on the site, or at the bottom of this email!

Happy coding!