W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2015

Re: Proposed Final Design for W3C Technical Reports style in 2016

From: Shane McCarron <shane@aptest.com>
Date: Fri, 6 Nov 2015 10:33:14 -0600
Message-ID: <CAOk_reFGzVtyFRBJ1kFZTYwq9n55bK5OZhrRgsWer+iqTrZdjQ@mail.gmail.com>
To: Richard Ishida <ishida@w3.org>
Cc: "fantasai (fantasai@inkedblade.net)" <fantasai@inkedblade.net>, "spec-prod@w3.org Prod" <spec-prod@w3.org>, "team-rdf-chairs@w3.org" <chairs@w3.org>, w3c-ac-forum@w3.org
+1 - sometimes the examples are just too wide!

On Fri, Nov 6, 2015 at 10:25 AM, <ishida@w3.org> wrote:

> On 29/10/2015 18:14, Coralie Mercier wrote:
>
>> A sample document is also available:
>>    http://fantasai.inkedblade.net/style/design/w3c-restyle/2016/sample
>>
>
> looking good. I like the h1 and logo (which i hadn't seen during TPAC).
>
> during TPAC we agreed that the main body of the text should not be centred
> – rather there should be some fairly fixed width of white space to the
> left, and that the white space to the right would expand with the window
> once the maximum body width was reached.
>
> this was to allow more room for wide tables, code samples, and diagrams.
> When they flow to the right of the body text width limit, half of the
> available space for overflow is soaked up by the left margin at the moment.
> Making the body 'left-aligned', as it were, would free up more overspill
> space to the right.
>
> can we fix that?
>
> thanks,
> ri
>
>
>


-- 
Shane McCarron
Managing Director, Applied Testing and Technology, Inc.
Received on Friday, 6 November 2015 16:33:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:21 UTC