I get your point, and for many uses, I'd agree. I may yet go with YAML. One issue is that I'd like this to optionally be part of a pod document - I'll first run Pod::HTML on the text file, then parse the form fields into HTML within that generated document. This will allow the text file to contain things like survey section headings and commentary paragraphs. I'm not sure that would integrate too well with YAML (though I suppose I could mark YAML sections and parse them separately). Maybe by describing my audience as "non-techies" I was misstating my goal. My first goal is to make this something that I can quickly whip up a survey by making the simplest possible podfile and generating from that.

In reply to Re^4: Generating an HTML survey form from simple markup by jZed
in thread Generating an HTML survey form from simple markup by jZed

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.