-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathreadme.txt
More file actions
36 lines (26 loc) · 2.4 KB
/
readme.txt
File metadata and controls
36 lines (26 loc) · 2.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Copyright (c) 2010, Wellfire Interactive
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.
Now that that's out of the way...
h1. Overview
So why ordered lists for forms? If you think back to all the forms you've filled out: census, doctors visit, drivers licenses, even those annoying bubble sheets that you had to use a number two pencil on for your standardized tests in grade school, the form you filled out was set in a certain order that the publisher believed was the best way for you to fill it out. The same thought is put into forms on the web. The developer builds the form in the order that they believe that it should be filled out.
Normally, we all very linearly fill out a form. Yet, nothing necessarily stops us from bouncing around the form and filling it out as we see fit. Ultimately, we shouldn't look at an ordered list as a constraint on how we move through the form. We should only as a guide to the default way to do so. At most by filling out the form in a non-linear way, we'll get a look of consternation from the old schoolmarm.
What we are defining here is a framework to what we've found to be a great way to set up forms on the web. The ordered form is a great scaffolding for mobile, large screen, accessibility, and print; translating to all media well. Over the past few years, we've come to the framework as a go-to solution for laying out the form and insuring it functions correctly in various browsers and media.
h1. Usage
h1. Extension