<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 5, 2008, at 6:09 PM, Steven Jones wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>Showing the last updated time doesn't show you that the page is up to date, it only shows you how out of date it could be. If I fix a typo on a page, then having that date displayed will make it look like that was the last date that the content was checked for accuracy.<br> <br>So while on the surface a good idea, I'm not sure how misleading the information could be.<br></blockquote><div><br></div><div>Hi,</div><div><br></div><div>If this were me—and I do realize I'm probably not a very good example of a typical user persona—and I read a page that was somewhat out of date but saw a recent last-modified time stamp on the page, I would check the revisions tab to see what the last couple of revision log messages are. Hopefully there will actually be some revision log message there that just says "Fixed typo", so I'd be able to quickly see what the latest major update/change was. If not, I'd probably run a diff.</div><div><br></div><div>Since, (if I understand correctly) all visitors logged in with a d.o user account (doc team members or otherwise) have access to the revisions tab, I don't think it's too misleading in these cases to add a last-modified time stamp. The information is in the worst case *somewhat* misleading but in the best case *very* helpful, so I think adding this time stamp seems like an overall net win for visitors. Plus, if users get upset about seeing mismatched time stamps to out of date pages, perhaps they will be encouraged to add more issues that notify us of this fact!</div><div><br></div><div>My two cents….</div><div><br></div><div>Cheers,</div><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>--</div><div>-Meitar Moscovitz</div><div>Drupal: <a href="http://drupal.org/user/265715">http://drupal.org/user/265715</a></div><div>Personal: <a href="http://maymay.net">http://maymay.net</a></div><div>Professional: <a href="http://MeitarMoscovitz.com">http://MeitarMoscovitz.com</a></div><div><br></div></div></div></div></div><blockquote type="cite"><div class="gmail_quote">On Thu, Jun 5, 2008 at 12:47 AM, Nathaniel Catchpole <<a href="mailto:catch56@googlemail.com">catch56@googlemail.com</a>> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The idea came up in this thread on the development list: <a href="http://lists.drupal.org/pipermail/development/2008-June/030088.html" target="_blank">http://lists.drupal.org/pipermail/development/2008-June/030088.html</a> (which is more about documentation than development).<br> <br>I think it's a good one - display last updated information on all handbook pages. It'd be one line to add in Bluebeach, and it immediately helps with evaluating whether a page is up to date or not.<br><br>Is there any reason not to do this?<br> <br>Nat<br> <br>--<br> Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br> List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br></blockquote></div><br><br clear="all"><br>-- <br>Regards<br>Steven Jones --<br>Pending work: <a href="http://drupal.org/project/issues/documentation/">http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</a></blockquote></div></body></html>