<!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;'>Thanks Eliot<br><br><br>When Roassal3 side project is done, my attention turns to either porting Pillar, or , more likeky, writing our own markdown parser with XTreams grammar and various actor backends to duplicate the Pillar output (including HelpBrowser, xhtml, latex, morse code...)<br><br><br>What I see being different is the source document living entirely within squeak classes, and storeable, distributable via monticello, with git being a secondary source of input to the monticello. Ergo, any squeak user can contribute by editing simple markup, or modifying existing templates.<br><br><br><br>The Array example is in my list of things to cover .<br><br><br>So, suppose a couple of booklets exist covering Common Patterns and Idioms, Cool Code Snippets, Arrays, etc...<br><br>A query to the in image documents for 'Array' will show those titles, edit and save in place, view in place, save via monticello, voila, every image has the documentation.<br><br>Squeak does not have a documentation problem, it has a documentation aggregation problem. <div><br></div><div>Cheers</div></div><br></body></html>