On episode 28 of the North Meets South Web Podcast, Jake and I were discussing packages that we always pull into our Laravel projects. Jacob mentioned that he still uses the Laravel Collective HTML package, which was forked from the functionality that was present before Laravel 5, which is something I suggested I hadn't done for a long time.

If this is how you want to go about things, there's nothing wrong with that but I personally feel there's no real benefit in pulling in yet another package, just to handle writing HTML for me. This is largely because I can handle that kind of stuff with a combination of Emmet and/or snippets in Sublime Text.

Jacob went on to explain that a big part of using the form package is because it handles binding form data directly to the forms for you, allowing you to separate form inputs from the create / edit components themselves.

Using the HTML package

// resources/views/users/edit.blade.php
{!! Form::model($user, ['route' => ['users.update', $user->id], 'method' => 'put']) !!}
    // Your cancel / update buttons
{!! Form::close() !!}

// resources/views/users/_form.blade.php
<div class="form-group">
    {!! Form::label('first_name', 'First Name') !!}
    {!! Form::text('first_name') !!}

This will generate HTML for you that looks something along the following lines:

<form method="POST" action="" accept-charset="UTF-8">
    <input name="_token" type="hidden" value="somegeneratedtoken">
    <input name="_method" type="hidden" value="PUT">
    <div class="form-group"> 
        <label for="first_name">First Name</label>
        <input name="first_name" type="text" value="Michael">

Passing the $user variable along to the form's model method will pre-populate your form inputs, meaning that if the user had a first_name, it would automatically be assigned to the value parameter of the corresponding input.

Using vanilla Laravel and Blade

I suggested that you can go about this simply enough in your applications by using a combination of the old() helper method and an empty model.

class UserController extends Controller
    public function create()
        return view('users.create', ['user' => new User]);

    public function edit(User $user)
        return view('users.edit', ['user' => $user]);

This way, you can still extract the form parts into their own Blade template, and delegate display of the existing values to the model instance, leaving Eloquent to return null where the value doesn't exist i.e. in the blank User model.

// In resources/views/users/_form.blade.php
<div class="form-group">
    <label for="first_name">First Name</label>
    <input type="text" name="first_name" value="{{ old('first_name', $user->first_name) }}" class="form-control">


As I mentioned at the top of this post, it is entirely optional if you want to take this approach. I personally feel that I'm not gaining anything by bringing in another package just to handle generating HTML on my behalf when it's just as fast to use the tools available to me in my editor. It also means there's no implied knowledge of a now non-standard external package, should a new developer be brought on to the projects that I've worked on. HTML is HTML, after all.

I will concede that I miss the HTML package making things like <select> fields simpler, taking into account selected values but a simple @foreach loop and inline conditional aren't too bad in this instance, either.

How do you go about handling your HTML forms, do you have another approach? I'd love to hear about other options.