Custom Styles
If you'd like to customize the look and feel of your form, there are classes you can hook into.
View exampleThe ET Application form gives our members the ability to collect information about emerging technologies by providing a way to create challenges and general questionairres. All of the questions are configurable, as is the overall user-experience and style. The documentation below is intended to provide a reference for how to customize the forms for any website.
To create a new ET Application form, first login to the Member's Admin Area to create new forms. Click "Create a Form", give the form a simple title and description, upon completion, provide the required API_KEY
and FORM_ID
to your development team who will be implementing the form. Not to worry, you can always get this later by looking at the form summary. Additional information may be found in the Member's Admin Area FAQ.
Please reference our official documentation on Github. Feel free to fork, and extend as needed - our simply source the latest version from our CDN.
What to fully customize the look and feel of your form? Don't want pagination? Need custom fields? By changing some config settings and adding your own CSS, the possibilities are endless...
If you'd like to customize the look and feel of your form, there are classes you can hook into.
View exampleNot all forms need to be a multi-step process. Pagination is automatic based on your config.
View exampletitle
String. Optional line of text above the form, below the step navigation.
confirmation
String. Confirmation text displayed once the form is completed. (Default: Thank you for submitting your information. We'll be in touch!)
steps
Array. The number of objects in the steps
array dictate the number of pages in your form. Pagination is automatic.
fields
Array. Each object in this array is a form field.
id
String. Input ID.
input_type
String. The type of input/form field. Input types are listed below:
text
Basic text input.
textarea
Basic textarea input, for blocks of text.
url
URL field; expects URL formatting, with validation.
email
Email field; expects email formatting with validation.
multi_select
Dropdown select menu with options. Requires the options
object, with value
and label
keys.
select
Dropdown select menu with options. Requires the options
object, with value
and label
keys.
people_list
Custom input collection made of multiple fields; allows the user to add/remove rows.
db_field
String. Database field; usually the same as id
.
input_label
String. Optional placeholder text for the input element.
txt_label
String. Optional label text for the input element.
help_label
String. Optional helper text below the input element.
required
Boolean. Mark the input as required.
required_label
String. Validation text if the required field is left blank.
layout
Object. Contains grid options (see below):
grid
String. Controls the width of the element, either full
(full-width) or half
(50% width).
options
Array. Required for multi_select
input type. These are the options that appear in the select menu. Each object needs value
(string) and label
(string) keys.