Project Wrap-Up Ideas 0:00We've sadly reached the conclusion of this long series, as well as our Tweety final project, so again, thank you so much for coming along. However, if you would like to continue on, here are some ideas. Let's sign in. Naturally, there's still so much work to be done, and I've listed some of these ideas I'm about to share with you on the GitHub repo, so feel free to fork this and then work on these on your own as an exercise. OK, first up, on the profile page, although the avatar is dynamic, the banner image and the description is not. So consider making those configurable attributes that you can store and reference from your database. Enhancements to Implement 0:36the description is not. So consider making those configurable attributes that you can store and reference from your database. Next, what about when you publish a tweet? It might be nice to drag and drop an image onto this container here and have it submit an AJAX request to upload the image and then associate that image with the tweet. Have a think on how you would do that. That would be a good exercise. Next, in terms of likes and dislikes, what if I want to remove a like? If I click it right now, it just interprets that as a dislike. It should do the opposite if I click it a second time.If I click it right now, it just interprets that as a dislike. It should do the opposite if I click it a second time. That would be a good exercise. Next, what about when you add a tweet? Maybe we should see a little flash message in the bottom right. Or if you follow a person, like so, again, sometimes it's useful to have a little flash message in the bottom right. Next, again, there's so many things. What about allowing a tweet not to be edited, of course, we gotta keep in line with Twitter, but to allow a tweet to be deleted?What about allowing a tweet not to be edited, of course, we gotta keep in line with Twitter, but to allow a tweet to be deleted? That's something we should afford. So again, there's no shortage of things you could work on, and you can review all of them on the GitHub page. So again, if you're still learning, I highly recommend working on these on your own. Even if you only do one item per week, you'll start to put your skills to the test. Okay, and then beyond Laravel from scratch and Tweety, of course, at LaraCast, there's no shortage of content for you. You can visit the Laravel journey, and again, you don't have to follow these in order. Next Learning Paths 2:02no shortage of content for you. You can visit the Laravel journey, and again, you don't have to follow these in order. They are a recommended guideline you might consider. So you might move on to building another Laravel app. Or if you're not in the mood for that, you could start learning about Vue or a deep dive into Eloquent Relationships, Authentication, Presets, again, you can mix and match however you like. And of course, don't forget to take some time to review tooling like your editor of choice. When you're ready to begin learning about testing, you might start with the Code Kata series.When you're ready to begin learning about testing, you might start with the Code Kata series. I think you'll like that. So there's no shortage of content. Thanks again for coming along.
