 |
 |
Frossie, > - The model used by the people who seemed happiest with their solution involved schemes like plain-text (typically Markdown) documentation in git repos, pulled together (eg. as submodules in a Docs repo), and then turned into a website through a static page generator (of which Jekyll was one example) by the “docs person”. My strongest pro-wiki argument is that it provides a place for end-user questions and discussions (and perhaps volunteer contributions). I can see that the contributions can be treated as pull requests, but do the questions and discussions have to go to a (distinct, separate) stackexchange like site, or are there good ways of integrating them (kind of like php.net/manual/en/)? -- Kian-Tat Lim, LSST Data Management, [log in to unmask] ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1