From there, you just look at the possible schema keywords, try to understand what they mean for the data, and then how you might represent that in a form.
For example, if a given property is not "required" in the schema, then it is optional - how do you represent an optional property in an object? Maybe a checkbox to indicate whether it's present or not?
Another example: if a schema specifies "enum", then the value has to be one of those exact values. Is there a nice form control that forces you to choose between a set of fixed options? Yes - enums could be a drop-down (<select>), or perhaps a set of radio-buttons.
One thing to note that there are no hard-and-fast rules. If the schema says something is a string, then is it a single-line input, or a multi-line text area? Is an "enum" schema a drop-down or a set of radio-buttons? It's up to the individual library.