I've elaborated many times that we need a Dev environment.

Convincing the gods of new features by wording is often a futile endeavor. Being able to show the POC OTOH is far more effective and less frustrating.

Furthermore did we already see carefully crafted JS POCs fiddled into Nodelet hacks which where mostly ignored by the gods.

Like tobyinks responsive design or my so called wikisyntax, which can be easily adapted to implement BBcode or markdown.

There is also a long-standing vulnerability report including patches for everything which haven't been dealt with.

Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery

In reply to Re^5: Ideas for "fixing" PerlMonks 1.0 by LanX
in thread Ideas for "fixing" PerlMonks 1.0 by etj

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.