<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <style type="text/css" style="display:none;"></style> </head> <body dir="ltr"> <div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;" dir="ltr"> Hello Emil, I'm not sure if you have read the full conversation, but I changed my mind about this. I have shifted focus to use Sphinx for website generation along with documentation. As far as I can tell, there is already documentation about NIR and Gallium writen in ReStructured Text, which Sphinx can use. The last two week I'm very busy at work, so I haven't made much progress on the website itself. My hope is to release a new repository on github this weekend, with the initial website in a ReStructured Text format. Best Regards, Jean Hertel. <div style="color: rgb(0, 0, 0);"> <div> <div id="x_divRplyFwdMsg" dir="ltr">De: Emil Velikov <emil.l.velikov@gmail.com> Enviado: quarta-feira, 29 de março de 2017 12:32 Para: Brian Paul Cc: Jean Hertel; mesa-dev@lists.freedesktop.org Assunto: Re: [Mesa-dev] [Request for Comments] - Port documentation to Markdown <div> </div> </div> </div> <div class="PlainText">Hi Jean, On 8 March 2017 at 16:12, Brian Paul <brianp@vmware.com> wrote: >> >One thing that I would prefer so not see if heavy things like >> Bootstrap. >> >We definitely don't need it, I think writing our own few lines of CSS >> >(which can be inspired by anything you want) is better. We have more >> >than enough people who know how to do it (myself included), it will >> be >> >cleaner (we won't need to include the whole forest to get our tree) >> and >> >much easier to fix when there's a bug. >> >> >> I would tend to agree but I don't care too much about those details so >> long as it's maintainable. My primary concern is that while a lot of >> random developers in the community are liable to have brushed into CSS a >> time or two, most probably won't know bootstrap. > > > Yeah, I can's stress that too much. The site has to be easily maintainable > by the developers. I, for one, don't know much about websites beyond html > and a little CSS. If you create a new website infrastructure and then > disappear after a few months we need to be able to take over. Also, we > can't funnel documentation updates through a handful of people that know a > complex system. > Have you had some time to look into this ? It would be great if we can get things rolling, even if not perfect. Thanks Emil </div> </div> </div> </body> </html>