Build stunning mobile-friendly forms with no AI

Open source text-based form generator with focus on creating forms that are syntactically-correct, mobile-friendly, accessible & inclusive, look stunning out of the box, and follow best practices that make highly-converting forms (see:
Would you recommend this product?
2 Reviews2.5/5
Hello product hunters, this is my first hunt. I've created this open source form builder after seeing many designers and developers struggling with creating html forms that are done correctly. When I say correctly I mean: * Mobile friendly - the right keyboard for the right field, easy to navigate, etc * Look nice out of the box * Accessible to screen-readers and people with disabilities * Semantically correct - simple HTML that uses the right field types, with CSS for styling, and not bloated with unnecessary divs or classes * Adhere to forms best-practices (see here: I've decided to use simple text editor because I found it funny that with all other form-builders you have to fill-in very complex forms in order to create simple forms. I hope you find this useful, and I would be happy to hear what do you think.
I sympathize with the goals. There seems to be some overlap with Mixxr ( My first thought was that it was trying to do the same and that it was using Pug as well, but then I realized that it wasn't and that it's producing a type of markup that isn't specifically targeting any of the CSS frameworks. Mixxr is aiming an attempt to create a DSL for markup that is trying to abstract from the HTML expected by CSS frameworks, to make sure you can retarget it to any other type of markup at any given time. To that end, rather than creating a DSL, it leverages Pug mixins. The DSL type of approach makes everything a little easier on the eyes. However, the mixing approach allows you to fork the mixins and create slightly altered versions of the HTML generators, to encode your own policies. Here is an example of the HTML getting generated to target Bootstrap: Here is an example of the HTML getting generated to target Bulma:
@wilfredspringer Thanks for the reference, it's interesting. Behind the scenes, there is a JSON representation of the form that is generated from the DSL before the HTML is being generated. So if this would become a requirement I could create different generators that target specific frameworks. For now I tried to avoid it by creating a standalone framework-agnostic form.
Hidden comment