<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Yet, The Linux Documentation Project did it successfully .<div id="message"></div><br id="br3"><div id="signature"></div><div id="content"><br> ---- On Mon, 19 Jul 2021 12:53:37 -0400 <b> tim@rowledge.org </b> wrote ----<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); padding-left: 6px; margin-left: 5px;"><div>We tend to obsess about making tools -big surprise! - whilst forgetting that the key problem is *content*. If we have some content in a digital form somewhere, we can move, reformat and present in in a myriad ways. No content, no presenting it.<br><br>Of course the problem tends to be that very few people in the world of software think of documenting things as interesting, important, or even worthy of consideration.<br><br>tim<br>--<br>tim Rowledge; <a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>APATHY ERROR: Don't bother striking any key.<br><br><br><br></div></blockquote></div></div><br></body></html>