I have added a lot since the original post, and since this tread is getting so long, the current code is a gist on GitHub Gist. I have not written for every possible HTML tag, only the ones I use (or got interested in while writing).

The problem is that many HTML elements have names that conflict with Perl's built-ins (tr, map, etc).

There are only five HTML elements (six when HTML5 is ready) which have names in conflict with Perl's built-ins, and it is an easy fix. Make the HTML element subroutine names semantic or expand them to do more.

• link - I wrote a sub called links which gets fed an array of hashes for many link elements within the head sub as an option.

  html(0, {
    head => {
      title => 'Section 2',
      links => [
        { rel => 'Index', type => 'text/html', href => 'index.html' },
        { rel => 'Prev',  type => 'text/html', href => 'Section_1.html' 
  +},
        { rel => 'Next',  type => 'text/html', href => 'Section_3.html' 
  +}
        { rel => 'stylesheet', type => 'text/css', href => 'my_style_she
  +et.css' },
      ]
    },
    body => [ sub {
      heading(2,1,'Section 2');
      paragraph(3,'Section 2 is great!');
    }]
  });
  [download]

• map - You could name the sub image_map.
• select - I renamed it selection.
• sub - Once I get the inline elements worked out, I will be able to do something like SUB<text>, hopefully.
• tr - I named the sub row, which is more semantic.
• time - new element for HTML5 which we will have to deal with some day. Since it is an inline element, I may be able to treat it like I would sub like TIME<20 April 2013>

Note: I treat all inline elements differently than I do block elements, except a which is anchor when I am writing one alone.

The great thing about writing this in Perl is the HTML element tag names do not hold us hostage. We can name the subroutines whatever we want. So, for h1 through h6 I wrote a sub called heading. For ul and ol, I wrote list (with li being item).

I added your module to my SEE ALSO. :)