I recall a number of people wishing for a better idea of what was updated in a given node. Obviously, implementing some kind of revision control on nodes would be a lot of work, despite its niftiness. Besides, there's something to be said for making such revision tracking optional.

However, I think I may have stumbled on an idea that might not be a ton of work (note: despite asking, I'm still not a pmdevil, so I can't be sure), but would make it easy for users that are so inclined to add helpful information about their updates.

Basically, I suggest adding a short text form field to the node-updating form that allows one to add a brief note about what the update entailed. The number of updates could be displayed in all node views, with a link to the update history. Couple this with a user preference to always display the history notes in-node, and this could be very nifty.

I know it isn't dirt-simple, as it would likely involve adding a DB table; however, it's not nearly as hard as adding RCS-like capabilities, and it remains optional and up to the user.

Not well formed, I know, but something to discuss? I'm willing to do as much of the work as I can if I ever get a response to my pmdev request for access...

<-radiant.matrix->
Larry Wall is Yoda: there is no try{} (ok, except in Perl6; way to ruin a joke, Larry! ;P)
The Code that can be seen is not the true Code
"In any sufficiently large group of people, most are idiots" - Kaa's Law

In reply to PM Feature Idea: optionally add short comment on update by radiantmatrix

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.