PHPackages se7enet/florms - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. se7enet/florms ActiveLibrary se7enet/florms ============== Easy Bootstrap Forms for Laravel v0.5.4(5y ago)021MITPHPPHP >=7.1.3CI failing Since Nov 16Pushed 5y ago1 watchersCompare [ Source](https://github.com/renderse7en/florms)[ Packagist](https://packagist.org/packages/se7enet/florms)[ RSS](/packages/se7enet-florms/feed)WikiDiscussions master Synced today READMEChangelog (10)Dependencies (1)Versions (12)Used By (0) Florms ====== [](#florms) Easy Bootstrap Forms for Laravel -------------------------------- [](#easy-bootstrap-forms-for-laravel) Florms is a Laravel package that enables you to quickly and easily add Bootstrap 4 forms to your application. Input elements are automatically wrapped in the standard containers (such as ``). Labels, validation errors, input groups, and other decorators are automatically built correctly, so you don't have to think about it. HTML attributes and class options are added via chained methods, and most inputs have sensible defaults, so you can quickly and easily knock out your forms and get back to the more important parts of your application. Installation ------------ [](#installation) To install Florms, require the package with Composer by running the following command in your console/terminal: ``` composer require "se7enet/florms" ``` If you're using Laravel 5.5 or higher, that should be it, Laravel will automatically discover the Service Provider and Facade as part of the Composer install. ### Laravel v5.4 and below [](#laravel-v54-and-below) However, if you are on a version lower than 5.5, or if you don't use Auto Discovery, you'll need to add these yourself: Add the Service Provider to the `providers` array in config/app.php: ``` Se7enet\Florms\FlormsServiceProvider::class, ``` And add the Facade to the `aliases` array in config/app.php: ``` 'Florms' => Se7enet\Florms\FlormsFacade::class, ``` ### Optionally Publish Configuration [](#optionally-publish-configuration) You can also optionally publish the config file, if you wish to make any skin customizations: ``` php artisan vendor:publish --provider="Se7enet\Florms\FlormsServiceProvider" ``` Getting Started --------------- [](#getting-started) To get started, simply open a new form. Normally this would be done inside a Blade template, but you can store it in a variable if you'd like. Note that because this inherently returns HTML, if you are using it in a Blade, you should use the `{!! ... !!}` to print the unescaped string. ``` {!! Florms::open()->url('/url/to/route.php')->post() !!} ``` This will return the following: ``` ``` ### Additional Routing and HTTP Verbs [](#additional-routing-and-http-verbs) You can also use the `route()` or `action()` methods instead of `url()`, which accept the same arguments as Laravel's `route()` and `action()` helper functions, respectively, and will automatically turn your route name or controller action reference into a complete URL: ``` {!! Florms::open()->route('route.name', [$model->id], true)->post() !!} ``` Additionally, you can use the `get()`, `put()`, `patch()`, or `delete()` methods, instead of `post()`, to submit the form using those methods. Because HTML doesn't actually support the `PUT`, `PATCH`, and `DELETE` verbs, the form will be submitted using the `POST` verb, but will contain the necessary `_method` hidden input so that Laravel knows what to do for routing purposes. ### Model Binding [](#model-binding) If you want to prepopulate the default values of all fields on your form using an existing model, simply chain the `model($model)` method onto your form opener. The model gets attached to the form, and any inputs you create will automatically receive a `value` attribute by looking up the field's `name` from the model attributes. For example, a `$user` model may have a `$user->first_name` attribute, with a value of "John". If you chain `model($user)` to your form opener, and then create a field such as `Florms::text()->name('first_name')`, that field will automatically receive `value="John"` attribute. ### Additional Options [](#additional-options) You can also disable the CSRF token hidden field, by chaining `csrf(false)`. Adding Form Fields ------------------ [](#adding-form-fields) Once you have opened the form, you can add a new field. For a plain text input, you could do something like the following: ``` {!! Florms::text() ->name('first_name') ->label('First Name') !!} ``` That would get you something like this: ``` First Name ``` As you can see, the field will be automatically wrapped inside a `form-group` div, and the standard Bootstrap classes for labels and inputs will be added for you as well. ### Selects [](#selects) You can make select boxes, too. By default, selects use Bootstrap's "custom" variation to allow for more styling options. ``` {!! Florms::select() ->name("selectname") ->options([1=>'One', 2=>'Two', 3=>'Three']) ->value(2) ->label('Label Goes Here') !!} ``` And you'll get: ``` Label Goes Here One Two Three ``` ### Checkboxes & Radios [](#checkboxes--radios) Like selects, checkboxes and radios use Bootstrap's "custom" style as well. The necessary wrappers to use this are handled for you. Florms also knows that labels come *after* checkboxes and radios, rather than before like most other input types, and that they'll need their own custom class in here. ``` {!! Florms::checkbox() ->name('acknowledgement') ->value(1) ->label('I acknowledge this.') !!} ``` ``` I acknowledge this. ``` ### Input Types & Attributes [](#input-types--attributes) Basically all `` values are supported by using the appropriate static method call from the `Florms` class (`Florms::number()`, `Florms::date()`, `Florms::color()`, etc.), as well as the additional input-related tags (`Florms::select()` and `Florms::textarea()`, for example). Most HTML attributes are supported as well, using camel case. Methods chain onto each other and return the main input object, so you can build a complete input field. The `id` attribute will be automatically added based on the field's `name`, but you can override it with your own ID if you'd like - as you might expect, you would simply chain the `id('your-id-goes-here')` method onto the field. And you can add additional classes before or after the normal Bootstrap `form-control` class by using `appendClass(...)` or `prependClass(...)`. Below you can see a more advanced example using several HTML attributes as we ll as an additional class, all attached to a `number` field type. ``` {!! Florms::number() ->name('quantity') ->id('quantityId') ->label('Quantity') ->data('toggle', 'something') ->rel('last') ->max(100) ->min(0) ->step(1) ->appendClass('another-class') !!} ``` ``` ``` ### Alternative Syntax [](#alternative-syntax) Additionally, if it makes more sense for you, you can pass an array of options into the original method call, similar to how Laravel's built-in form builder used to work before it was removed from the framework. When using the array syntax, you should use spinal case rather than camel case. You can create the same field as above by using the following: ``` {!! Florms::number([ 'name' => 'quantity', 'id' => 'quantityId', 'label' => 'Quantity', 'data-toggle' => 'something', 'rel' => 'last', 'max' => 100, 'min' => 0, 'step' => 1, 'append-class' => 'another-class', ]) !!} ``` More Options ------------ [](#more-options) Input Groups are easy as well, using the `inputGroupAppend()` or `inputGroupPrepend()` methods. Simply pass the text or HTML you'd like to add into the method. You can even use both methods at the same time, and Florms will apply both inside a single outer `input-group` div. ``` ->max(999.99) ->min(0) ->step(0.01) ->inputGroupPrepend('$') ->inputGroupAppend('.00') !!} ``` ``` $ .00 ``` If for some crazy reason you only want to create a plain input field without the standard `form-group` wrapper, you can chain `->formGroup(false)` In Closing ---------- [](#in-closing) To close your form, after all fields have been created, it's about what you would expect: ``` {!! Florms::close() !!} ``` By closing your form, it will clear out any model attachments and other options, setting you back to a *tabula rasa*. Once the first form has been cleared out, you can create another form, with another action, another model, and different fields. Note that the `close()` method is only called by itself; you cannot chain any additional methods to it as you would most other Florms methods, because it simply renders the `` closing tag and returns it as a string. Coming Soon ----------- [](#coming-soon) Florms is still a work in progress. For one, I still need to build complete documentation. This readme really only scratches the surface of all the possible options and attributes you can use. There are some additional features I'd like to build in as well. Right now, you can "chain" method names themselves to call methods on some of the helper elements - for example, `->formGroupAppendClass('another-class')` would call the `appendClass()` method on the field's `formGroup`, resulting in `...`. What you can't do, yet, is chain even further. For example, Input Groups have several child elements inside them, and I'd like to let you use method chaining to go all the way down into them. An example would be something like `->inputGroupInputGroupAppendInputGroupTextPrependClass(...)`, to call the `prependClass(...)` method on the `input-group-text` span, which is inside the `input-group-append` div, which is inside the `input-group` div. I know that looks ridiculous, but right now there is no other way to add custom classes or other attributes onto these child elements, so I'd like to get something working for that. Contributing ------------ [](#contributing) If you'd like to contribute, I'm open to pull requests. This is my first Laravel package, so I'm kind of learning the ropes a little bit, so please bear with me while I get the hang of it. License ------- [](#license) ### MIT License [](#mit-license) Copyright (c) 2019 Jamin Blount Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ### Health Score 23 — LowBetter than 27% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity6 Limited adoption so far Community7 Small or concentrated contributor base Maturity49 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~31 days Recently: every ~40 days Total 11 Last Release 2053d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/dd4e52bfc72490d3db03aa19f72c85c92c4ea78057d504f9846d56b827152822?d=identicon)[se7enet](/maintainers/se7enet) --- Top Contributors [![renderse7en](https://avatars.githubusercontent.com/u/25567567?v=4)](https://github.com/renderse7en "renderse7en (76 commits)") ### Embed Badge ![Health badge](/badges/se7enet-florms/health.svg) ``` [![Health](https://phpackages.com/badges/se7enet-florms/health.svg)](https://phpackages.com/packages/se7enet-florms) ``` ### Alternatives [anourvalar/eloquent-serialize Laravel Query Builder (Eloquent) serialization 11320.2M21](/packages/anourvalar-eloquent-serialize)[namu/wirechat A Laravel Livewire messaging app for teams with private chats and group conversations. 54324.5k](/packages/namu-wirechat)[statamic-rad-pack/runway Eloquently manage your database models in Statamic. 135192.6k5](/packages/statamic-rad-pack-runway) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)