Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Typeform alternative, turns Markdown to forms

blocks.md

Post reply on HN
Print view View original

11–20 of 79 posts

Re: Show HN: Typeform alternative, turns Markdown to forms

#11

Post by bthallplz »

rafram wrote: post #6

This is more like a DSL with Markdown embedded for the textual parts, but still cool. An actual Markdown syntax extension for forms would be interesting. [_____] for text fields?

Yeah, is anyone familiar with other DSLs for form/survey building and logic?

For my work, where we produce lots of surveys and reuse parts of them/run near duplicates monthly, I've been curious to see if there's any dual code and GUI options out there to allow for survey programming to be version controlled and forked, etc.

Re: Show HN: Typeform alternative, turns Markdown to forms

#14

Post by notpushkin »

steve_adams_86 wrote: post #8
mg wrote: post #7

It looks like it could be made leaner. This: name* = TextInput( | question = What is your name? | description = Let's get started with the survey. First, please tell us your full legal name according to your passport. ) Could be just this: name* = TextInput # What is your name? Let's get started with the survey. First, please tell us your full legal name according to your passport.

But then how would you support choices or conditions for example?

Maybe something like this for choices?

    fruits = MultiChoiceInput
        # What are your favourite fruits?
        - [ ] Apples
        - [ ] Oranges
        - [ ] Bananas
Personally I'd prefer good old MDX though:

Re: Show HN: Typeform alternative, turns Markdown to forms

#15

Post by lukasb »

rafram wrote: post #6

This is more like a DSL with Markdown embedded for the textual parts, but still cool. An actual Markdown syntax extension for forms would be interesting. [_____] for text fields?

Yeah I'm curious if the Markdown form syntax here is totally new or if other people have done something similar. I'm building an app that extends Markdown with Excel-like formulas (think function calls, not arithmetic) and have considered having formulas that instantiate form elements.

Re: Show HN: Typeform alternative, turns Markdown to forms

#16

Post by mg »

steve_adams_86 wrote: post #8
mg wrote: post #7

It looks like it could be made leaner. This: name* = TextInput( | question = What is your name? | description = Let's get started with the survey. First, please tell us your full legal name according to your passport. ) Could be just this: name* = TextInput # What is your name? Let's get started with the survey. First, please tell us your full legal name according to your passport.

But then how would you support choices or conditions for example?

Well, you can define the syntax however you like in a new DSL, right?

I like the syntax notpushkin proposed and would extend it a bit like this:

    fruits* = MultiChoiceInput
        # Pick two out of three fruits
        Fruits are healthy, so let's pick two fruits
        you will eat every morning for the coming week
        - [ ] Apple
        - [ ] Orange
        - [ ] Banana

Re: Show HN: Typeform alternative, turns Markdown to forms

#17

Post by codersfocus »

Why are you using Paddle? Using a MoR for a product like this is really dumb.

MoRs are common in very shady areas (gambling, adult, etc.) where getting credit card processing approval is difficult.

Yet some marketing genius has decided he can hoodwink indiehackers into giving him 12% of his revenue, while also hurting the indiehacker's sales.

Re: Show HN: Typeform alternative, turns Markdown to forms

#20

Post by diggan »

mmastrac wrote: post #5

This style of form is aggravating to fill out, but kudos on making it beautiful. If you want to be kind to your users, allow them to scroll through the entire form, see it on one screen and ideally skip ahead without filling out required options but block submission.

> This style of form is aggravating to fill out,

In what sense?

I suppose for me it kind of matters how many questions are being asked. I'm fine with this UX if it's a specific question or two, but for a whole questionnaire with 14 questions or more, then I'd also prefer to be able to get an overview first.

Post reply on HN