The Laravel News site has a quick tutorial posted showing you how you can use Eloquent functionality to help prepare your URLs and make them easier to maintain across the application. The key is in the use of "presenters".
It’s not uncommon to have tens, if not hundreds of views in a Laravel application. Something that soon gets out of hand is the various references to routes. [...] If for whatever reason we have to make a change to either the route alias or default query string values you’ll soon find yourself doing mass string replacements across your entire application which brings the risk of breakage within many files.
What can we do to possibly better handle this? There are a couple of different approaches.
They provide two approaches, one being slightly more complex (but flexible) than the other. The first makes use of only Eloquent to define a
getUrlAttributes method in the model. The second method abstracts this functionality out to a "URL Presenter", a class that defines methods for each of the CRUD actions and returns the correct route for each. The
getUrlAttribute then returns an instance of this instead, making it easy to reference the method and route required in the Blade template.