<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 6 Jul 2013, at 15:33, Ashish Agarwal <<a href="mailto:agarwal1975@gmail.com">agarwal1975@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Sat, Jul 6, 2013 at 6:37 AM, Florent Monnier <span dir="ltr"><<a href="mailto:monnier.florent@gmail.com" target="_blank">monnier.florent@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
IMHO, the above idea won't replace the advantages of a real wiki.<br></blockquote><div><br></div><div>I agree. I think the current goal is to use GitHub as a pseudo-wiki. They'll handle the user accounts and server for us. We get static text files in the backend, which can be processed in custom ways as needed. But yes, it's not perfect. There is some extra indirection before you actually get to edit the file and that's enough of a deterrent if you just wanted to fix a spelling error. The next step might be to integrate an editor directly into <a href="http://ocaml.org/">ocaml.org</a>, with authentication via GitHub or OpenID.</div></div></blockquote><div><br></div>I like the idea of using the Github wiki as a frontend to editing the Markdown -- it solves the immediate problem, and still doesn't lock us into the Github workflow too tightly.</div><div><br></div><div>The ocaml-github bindings are pretty easy to integrate into Javascript authentication (I'll release the RWO commenting code shortly that does that). We're planning to extend this to other identity formats such as Persona and OpenID in the future.</div><div><br></div><div>-anil</div></body></html>