README-builds.html update

[Martijn Verburg]

Hi all,

So I started digging into this (just the HTML path to start with) and the
diff got pretty ridiculous. So I'm going to split the work into several
parts:

1.) Fix HTML warnings and convert HTML styling to CSS styling (using
internal stylesheet)

2.) Cosmetic changes to improve readability (change background to white for
contrast, pick a more web readable font etc) and cleaning up any
comments/whitespace in the document.

3.) Structural changes (moving sections around if that seems sensible, I'll
post suggestions first)

4.) Finicky detail changes (the bit that will require the detailed review)

I may combine 1&2 if the diff isn't ridiculously different.

======

If there's further consensus on Markdown then I can give that a go later
(HTML to Markdown converter to start with anyone? ;-)), but I suspect
Markdown readers aren't as ubiquitous as HTML readers and we'd have also
have to include an "export to output type X" step/tool, not sure how much
work that is, where it would get done etc.

Sound reasonable?


Cheers,
Martijn

On 5 February 2015 at 22:43, Omair Majid <omajid at redhat.com> wrote:

> * Magnus Ihse Bursie <magnus.ihse.bursie at oracle.com> [2015-02-03 08:48]:
> > In a somewhat related area: I've been toying with the idea of rewriting
> the
> > build-readme in markdown instead, and just generate the html file.
> Updating
> > proper, consistent html formatting for a document like this is quite
> > painful, and we never seem to get it right. Does it sound like a good
> idea?
>
> I really like this idea! With just the right amount of formatting,
> markdown is both easy to read by humans as plain text and turns into
> pretty good looking html too.
>
> Cheers,
> Omair
>
> --
> PGP Key: 66484681 (http://pgp.mit.edu/)
> Fingerprint = F072 555B 0A17 3957 4E95  0056 F286 F14F 6648 4681
>