finds.dev

formers/former

A powerful form builder, for Laravel and other frameworks (stand-alone too)

View on GitHubHomepage ↗

★ 1,329PHPupdated Apr 2026

// the take

Former is a fluent, Facade-driven form builder for Laravel (also usable standalone) that renders Bootstrap- or Foundation-styled markup through a chainable PHP API, automatically repopulating field values and injecting validation error messages after a failed submission. It's aimed at developers maintaining older Laravel codebases already built around Blade and Facades who want to cut repetitive form/validation boilerplate, not teams building greenfield apps around Blade components or Livewire.

The magic-method attribute setter (__call) lets you set any HTML or framework-specific attribute without the library needing to know about it ahead of time, so the API surface stays small while still being arbitrarily extensible. Automatic repopulation of old input plus inline rendering of validation errors removes a lot of the old()/$errors->first() boilerplate that normally gets copy-pasted into every Blade form. The framework layer is abstracted into separate classes per CSS framework (Bootstrap 3/4/5, Foundation 4/5, plain/Nude), so switching the whole app's form markup is a one-line config change rather than a template rewrite. It works standalone outside Laravel too, with the Laravel integration as a thin service-provider/facade layer on top of a framework-agnostic core.

The __call-based fluent API has no static analysis or IDE autocomplete support, so a typo'd method name silently becomes a rendered HTML attribute instead of a compile- or lint-time error - bugs show up in the rendered page, not before. The whole design is Laravel 4/5-era idiom (global Facades, chained builder calls, a package-wide config file) that predates Blade components and Livewire, which are now the more idiomatic way to build forms in Laravel - adopting this today means layering an older pattern on top of the framework's current conventions rather than working with them. Support for each CSS framework is hardcoded in its own class (separate code paths for Bootstrap 3 vs 4 vs 5, Foundation 4 vs 5), so a new major version of Bootstrap or a different framework like Tailwind needs a maintainer release or a fork, not a config tweak. Heavy use of Facades and static-feeling global config makes form-generating code harder to unit test in isolation compared to plain Blade or component-based form code.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

search the same ground:

// at a glance

Stars
1,329
Forks
200
Language
PHP
Last commit
12 Apr 2026

// nearby

If former isn't quite it.

All repos →