Add TOC of ebook / videos

[brendt]

1. Domain oriented Laravel
2. Data as a first class citizen
3. Functionality as a first class citizen
4. Improving models
5. Testing domain code
6. The state pattern
7. Entering the application layer
8. View models

Would there be room to add more chapters afterwards? There might be one or two I'd like to add, but I don't have a concrete plan for those yet. In other words: not sure if the topics I have in mind are worth a chapter on their own.

[freekmurze]

Would there be room to add more chapters afterwards?

Certainly.

I think the TOC above is a little bit dry. I think what's missing are some details and especially when this is useful for my project. For example:

• improving models: could be rewritten as "Keeping your models small and clean".
• entering the application layer: what are we going to do in this chapter? What problems are we solving?

In general I think the TOC needs some more body and should be a bit more appealing to someone who doesn't know anything about the course.

[brendt]

Domain oriented Laravel

• The basic principles of domains, and ways to apply them in a Laravel project
• Thinking of "data" and "functionality" as two first-class citizen of your codebase
• Enriching model functionality, while keeping model classes small and clean
• The state pattern to model complex, state-specific, flows

Testing domains

• Testing actions, DTOs and model-related classes
• Using enhanced test factories to improve your test workflow

Entering the application layer

• The difference between application- and domain code
• A better project structure when dealing with hundreds of application classes
• View models: the missing link between controllers and domain code

[brendt]

How about this?

[freekmurze]

I would give it some more body still. You could split each item into more stuff.

For example "The basic principles of domains, and ways to apply them in a Laravel project" can be split into:

• The benefits of using domains
• When using domains makes sense
• Using PhpStorm refactoring to easily move classes around
• Exploring alternative code organizations

[brendt]

Maybe @willemvb should tell me how he's going to style this TOC, because if it's the same as https://laravelpackage.training/, there's little room for more body I think?

I believe it'd be easier to come up with fitting copy when I know how it should look 🙂

[freekmurze]

there's little room for more body I think?

We'll adapt the layout to the amount of content 🙂

[willemvb]

how he's going to style this TOC

Added a section for the TOC, but you can have all the room you need!

[brendt]

How about I split every point in the list into its own subsection, with one or two sentences of background information. Would that be ok, or would it be too much?

[freekmurze]

I think it would be ok. We want to wow people with the amount of things that we'll cover.

[brendt]

I'll write something down!

[brendt]

Wat denken jullie hiervan?

---

Domain oriented Laravel

Based on paradigms like DDD and hexagonal architecture, we rethink a Laravel application from the ground up. Our goal is to make our codebase maintainable within a team of developers, for years to come.

Data and functionality

We treat them as the two pillars we'll build the core of our application with: data and functionality are the elementary building blocks to model business functionality. We'll discuss patterns to handle these core concerns.

Enriching model functionality

We'll embrace Laravel's rich model functionality, and discuss ways to improve on them to keep our code maintainable and concise: query builders, collection classes, event driven models, projected data and the state pattern are solutions we'll look at in depth.

Testing domains

Tests are a given in these kinds of applications, we'll dedicate a whole topic on them, I'll show you that all the work we've done before will pay off immensely in our test suite.

Entering the application layer

It's worth understanding the difference between application- and domain code, and I'll explain our thinking in depth on this topic. I'll show you common pitfalls of how code can grow out of hand very quickly in large projects, and how to prevent this.

View models

The missing link between controllers and domain code: we'll discuss the view model pattern in depth, and you'll learn all its benefits.