Conclusion

This being my first unguided Laravel project, it has forced me to plan my application and visualise a flow of data through the application, from a route to a controller, to a blade document, to sending a request.

Though with the beginning stages of any language there is a lot to learn from the process.

Weddit has been a wild ride, but very enjoyable. I have learned a lot about Laravel, MVC architecture, php, and frameworks as a whole.

I have learned that making a database structure before you make an application is very, very valuable. that being said, for beginners like me, its hard to get the structure perfect, but that doesn't matter.

I have also learned to read the docs. It's almost a joke how every StackOverflow article reply contains 'its in the docs.' or 'per the documentation'.

Well, there's a reason.

Once you familiarise yourself with them, Laravel has some of the most user-friendly docs out there, and have saved me from insanity quite a few times over this project.

lastly, take things one step at a time. I have the tendancy to give up on something after it doesn't work and drift on to another thing - leaving a trail of unfinished jobs around my project (seriously, my github updates contain about 50 things I half worked on). Take something, stick with it, tough it out.

in terms of future steps, there are A LOT of things I would like to implement that I didn't have the time to.

  • polymorphic likes
  • user profiles
  • follow users so they appear in your timeline
  • add video support
  • subweddit tags
  • user flairs
  • 'top' and 'hot' filter for timeline for trending posts.
  • search feature
All of these features excite me, so I will continue to work on this in my free time. 

Again, all updates can be tracked on my github - https://github.com/ConvertToInt

Thanks for reading.




Comments

Post a Comment

Popular posts from this blog

Final Database Design

Image
This is a view of the tables at the end of the project: Subweddit: Subweddit includes an id, name, bio and logo for display and information purposes as well a mod_id, the moderator of the subweddit (the subweddit creator by default right now) Post: Post has a title and body, as well as an optional img field. slug is created from the title field being 'slugified' with underscores (_). As well as this, the author of the post is saved as user_id, and the subweddit the post belongs to is also present. Follow: The follow table is the simplest in the database. apart from the laravel created_at and updated_at fields, this table simply holds the user id and the subweddit id of the subweddit the user follows. Comment: Comment holds one text field as 'body', as well as the author (user_id), and the post it belongs to (post_id). Finally, there is a nullable parent_id column which would be used if the comment is a reply, holding the id of the comment being replied to.
Read more

Views and Policies

Image
Although maximum functionality is achieved by being a logged in user, it is important to think of guest users browsing the site. Baring that in mind lets run through the abilities guests and users: Guest: Home feed showing most recent posts from all subweddits view subweddit and contents view post and comments sign up User: Log in Personalised home feed Create subweddit Follow Subweddit Create Post Post comment/reply to preface: guest and user views could have been achieved in a cleaner way by creating seperate routes in web.php and stating if the user is logged in, redirect to 'logged-in' views, or otherwise 'guest' views. As my AWS instance is running on micro I chose to slim my application down so as not to overload my tiny server. Thusly, I opted for utilising @auth and @guest in the blade file. Not very clean, but effective and 'cost' efficient Starting with the index page: if the page is viewed by a guest, then display all posts from all subweddits, filter...
Read more

Validation

Image
validation, both serverside and clientside, is essential  for a satisfactory user experience, and for security.  This application makes use of several forms, so it is important that the site be completely tamper-proof. Thankfully, Laravel takes helps the cause, with the @csrf tag, which prevents csrf attacks, or cross-site request forgery. (explain this). validation on the registration is handled largely by the livewire auth package, the only tweak made is validation for the username, which was covered in the auth blog post. which leaves 5 forms to validate: create subweddit create post edit post create comment create reply Client side, all of the validation can be handled by laravel's @error directive, which will quickly determine if there is a validation error in an attribute. The message can be displayed by calling the array $errors. With our Bulma framework, we can make things look a little prettier for the user by changing the form border to red and displaying the red err...
Read more