[Mesa-dev] [RFC] - Rewrite mesa website in Sphinx
Emil Velikov
emil.l.velikov at gmail.com
Wed Apr 26 13:32:54 UTC 2017
On 26 April 2017 at 12:56, Jean Hertel <jean.hertel at hotmail.com> wrote:
>>On 2017-04-26 at 08:13, Emil Velikov <emil.l.velikov at gmail.com> wrote:
>
>>Thanks again for doing this Jean. A handful of, mostly trivial, questions.
>>
>> - Is there a website where one can check the output of specific
>>Sphinx markdown.
>
> I have searched for such a thing too, but have not found :(
>
:-(
>> - Any ideas why the page contents are so narrow? It seems theme
>>related, doesn't it.
>
> Yes, it's theme related.
> I have quickly readed the Kernel DRM docs, and it seems they have maded
> a litle fix in the CSS for this. I will provide a fix soon too.
>
No worries - we can always change/polish the theme as needed.
Just checking that there's nothing 'fundamentally broken' there.
>> - Personally I would not bother, yet, with the non-html documents.
>>These are quite picky to format correctly, as you've spotted already.
>
> Well, they are already formated now :)
> I will fix the small issues pointed by Eric.
>
Right - I was skimming through 4.1 where the spacing in the number
lists is still funky.
Either way I'm not saying that we should throw your work there. Just
that those will need closer look (read will take more time) than their
HTML brethren.
>> - The Gallium and NIR documentation might be better suited in the toctree.
>
> Ok, will fix that too.
>
>> - Maybe apply something like the following to the release notes
>>s|Mesa X Release Notes / $date|Overview\n\nRelease date: $date|
>>
>
> Do you mean in all the release notes?
> Please remember that, the first title (the one with ==== at bottom)
> of the file is used by Sphinx when generating the links.
> So I have added two titles in every release note,
> one for the link generation, and another for the original title.
>
To visualise what I'm talking about observe the TOC as you open any of
the [HTML] release notes.
Replacing the second "Mesa ... release notes....$date" with something
like above would be great, but optional.
Thanks
Emil
More information about the mesa-dev
mailing list