dillonkearns/elm-form 
Live Ellie demo: https://ellie-app.com/mzjFg6BWmMta1
elm-form is built around the idea
of managing a single Form.Model value as an unparsed set of raw field values and FieldStatus (blurred, changed, etc.).
This Form.Model can even handle form state of more than one form on a page, or even across multiple pages.
The package manages all of the unparsed state for you with a single Msg, a single Model entry, and then
uses your Form definition to run its validations against the unparsed values (Model),
and to render the form fields along with any validation errors.
If you use elm-form with elm-pages, the wiring is built into the framework so you don't need to wire in update or Model
yourself, and the framework manages additional Form state for you such as in-flight form submissions. The ideas in this
package originally came from elm-pages, but they are useful in a standalone context as well so this was split into
a separate package.
Some of these underlying ideas were discussed in the Elm Radio episode Exploring a New Form API Design.
Core Values
- Progressive Enhancement - to make things more robust, and to leverage existing standards to get features for free instead of re-inventing them for every app. Forms are great for sending data to servers, lets use them! Let's go back to our Web fundamentals - it's worth reading the MDN docs on form submissions to understand the core building blocks.
- Accessibility - using standards to provide an experience that supports a broad range of users and use cases
Core Ideas
Form.Validationlets you build up validations and parse fields into a combined value in the same pass (if you wanted to, you could even parse into aJson.Encode.Valueor some payload to send to an APIonSubmit)Form.Fieldlets you declare the fields (in the applicative pipeline in the Form definition)- You can pass an input value when you render the form which can be used in rendering the view, and for getting initial values (
withInitialValue)
Opinions
- Forms are always rendered within a
<form>element for accessibility, and to enable progressive enhancement - Fields are always rendered within a form field element of some kind ( or