I'm here in a brand new, fresh Laravel application, which I just installed, but that's the only thing I did here already. And before we can start, we need to define our scope. What are we going to build? You have already seen a little bit of the end result, but we need to break the separate tasks down. I like to create a Todoist markdown file for those tasks. At work, you probably get some information from your clients about what users can or cannot do, but today we have to define all of them ourselves. Since we're building an app where we have guests to check some of our courses, and we

cannot do, but today we have to define all of them ourselves. Since we're building an app where we have guests to check some of our courses, and we also have members to consume courses. And that's why I like to separate our Todoist in first what the guest can, and then later what a member can. So a guest can see the course's overview. That's what we want to show on the homepage. But a guest can also see course details, so there will be a detailed page for every course. And then most importantly, a guest can purchase a course. And then next we have a member, so a logged in User.

And then most importantly, a guest can purchase a course. And then next we have a member, so a logged in User. And first, of course, the member needs to be able to log in. And then when he's logged in, he should see purchase courses. So this is also an overview of the courses, but only the ones he purchased. And then, of course, he also needs to be able to watch a course that he bought. And last, we also have an admin, and the admin can, in our case, tweet about the new course release. So these are our Todos, and I really like to split them up in thinking about what a user can.

So these are our Todos, and I really like to split them up in thinking about what a User can. A GuestUser or a MemberUser, because these are all the things that a client likes to think of. So this is a very good approach and will also help you for your work. And of course, such Todos are crucial for every project, but it's even more crucial when we want to follow TDD. We can't just start coding with TDD. We need to think about specific tasks and how to test them. And what I also noticed, what helps me here is when I mark Todos when they are about a

We need to think about specific tasks and how to test them. And what I also noticed, what helps me here is when I mark Todos when they are about a specific page. So course overview is our homepage. Then we have a details page, so this is also about a page. Purchase course is something different, because this can be done from the course details page, probably. Login is about a specific page. See purchase courses, it's a page. And watch our courses is also a page.

See purchase courses, it's a page. And watch our courses is also a page. Then the last thing here, probably this will be a comment, but I'm not really sure yet, so let's leave this empty for now. But this will give us an overview of what of our tasks will end up in a specific page. And of course, this Todos list here is a work in progress. We might change it because, yeah, as always with such projects, Todos and things can change. But with this list, I think we are prepared and ready to move on.