Here I have a basic example of an input element with the type attribute set to button. For this example I am just using the click event to step a value stored in the input tag by way of the dataset property of the element. So then there is creating an input element, assigning an id for it, making sure that the type of the input element is set to button, and the setting an initial value for a count property in the data attribute for the element. There is then also the value attribute of the element that is of importance when making a button, and many other input elements. For buttons the value attribute will be the display name for the button. For this example I am using a draw function to set the value of the input element.
Another type of input element typically used for forms would be the text type input element. This is one way of creating a way to allow a user to input some text, but with input elements of type text it is more for the sake of inputing data for a field of data, and not so much a large body of text. In the event that I want to have an element that will be a a large body of text it is generally better to go with a text area element.
Here I have an html file with just a form element and a single text input element in it, and a submit button. I am setting the action attribute of the form element to the search path and the method to get. This way when the submit button is clicked the user will be directed to the search path with the query string set to the values given in the text input field.
So then when this example is up and ruining it is serving up the single html file at the root path, and the search path which at this time is just displaying the query in the browser window. Nothing major at this point but the basic idea is all ready there and working it is now just a matter of what I do with that query in the back end system.