If someone would like (for some reason) to look stuff up by either the ID or the slug, this fella works fine. Just add it to your model file.

(NOTE: It overwrites the default route resolver logic for the model!)

Tried that out of curiosity and it seems to work :)

class Article extends Model
{
    /**
     * Retrieve the model for a bound value.
     *
     * @param  mixed  $value
     * @return \Illuminate\Database\Eloquent\Model|null
     */
    public function resolveRouteBinding($value)
    {
        return $this->where('id', $value)
            ->orWhere('slug', $value)
            ->first()
    }
}

My routes:

Route::get('/articles', 'ArticleController@index');
Route::get('/articles/create', 'ArticleController@create');
Route::get('/articles/{article}', 'ArticleController@show');
Route::get('/articles/{article}/edit', 'ArticleController@edit');
Route::post('/articles', 'ArticleController@store');
Route::put('/articles/{article}', 'ArticleController@update');

Works with both /articles/1234 as well as /articles/lorem-ipsum.

If there are some caveats to this, please, let me know :P

Leverage Route Model Binding

Updated Series Available