On 8 February 2016 at 18:38, Sphinx <
sphinx...@hotmail.fr> wrote:
> Hello all,
>
> While going over the CSS section for localization, I encountered several
> styles for "live samples" and I'd like to be consistent across the fr
> documents.
>
> I propose the following:
> 1. Order of blocks:
> - having the first block with the main language for this sample
> (e.g. if this belongs to the CSS Ref, the CSS block should come first), if
> there is no such "main" language, preferred order would be HTML then CSS
> then JavaScript (SVG or MathML might come after HTML as content).
>
So far, I always used the order HTML, CSS, JavaScript. While I agree it may
make sense to have the code of the main language come first, I don't have a
strong opinion either way. Though I agree that we should decide on one way.
2. Having a "Result" block before {{EmbedLiveSample}}
> - Currently, some samples have a "Result" heading before the macro,
> some others have a "Output" heading, some others have a "Live Sample" but
> most of them don't have anything that separates the result from the code
> which is semantically weird.
>
Strongly agree on that there should always be a heading and that it should
be uniformly named across pages. Whether that's 'Result', 'Output' or 'Live
sample' still needs to be decided. My vote would be for 'Output', though
again without strong feeling about that.
> 3. Headings nomenclature
> - If under "Examples" (most of the cases), headings texts' should be
> "HTML","CSS","JavaScript" only. This would make things easier for
> consistency, l10n and so on.
>
I also agree on that. Note that if there are multiple examples, each
example should still have a heading by itself, but under that heading it
has only 'HTML', 'CSS' and 'JavaScript' as subheading.
One additional point:
If there's only one example, should it still be named 'Examples' with
plural 's'? I'd say no.
Sebastian