I'd much rather see a drop-down that lets the user select the format they were writing, and "Classic PM" would be one of the options, along with Markdown, and maybe WSYIWYG. The default would come from user settings. The database table would consist of "ContentType" and "Content", and ContentType would select the rendering module which converts it to HTML,

(or anything else, like XML)

I strongly feel this is the "right way" to handle it.

I had that in mind, too, but lacked the time to write it down. Having a "Classic PM" renderer would allow copying all content nodes from the existing PerlMonks to PM 2.0 in source form, no conversion needed, no complex interaction between PM 1.0 servers and PM 2.0 servers needed. Once all data is migrated to PM 2.0, PM 1.0 can be shut down.

Looking at very old nodes, it might perhaps be useful to have an "Ancient PM" renderer in addition to the "Classic PM" renderer, because obviously the PM approved HTML subset has changed over time. But having just the "Classic PM" renderer would already be a great migration helper.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

In reply to Re^7: Ideas for PerlMonks 2.0 by afoken
in thread Ideas for PerlMonks 2.0 by jdporter

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.