Apply the new design to the guidebook

[deniak]

@lcarcone @vivienlacourba, I'm starting this PR to redesign the guidebook.
I've redesigned 2 pages for the example:

1. the documentreview with a HTML to markdown conversion. That method will take a while unless we can find a good tool to convert the markdown but it can be tricky as some parts of the page may still require HTML (you will see I left some tags, e.g. details/summary, dl/dt/dd)
2. the standards-track index page where I kept most of the initial HTML

Happy to schedule a call to discuss the details with you

[deniak]

/cc @caribouW3

[TallTed]

It would be far easier to review this if there were a pr-preview or similar. What are the chances such could be instituted?

[deniak]

It would be far easier to review this if there were a pr-preview or similar. What are the chances such could be instituted?

@TallTed it might be difficult to integrate this with pr-preview. pr-preview works for specs that use a generator such as respec and bikeshed and it's meant to preview a single file.
In that particular case, jekyll generates pages for the whole repository which could represent a lot of files.

[TallTed]

pr-preview works for specs that use a generator such as respec and bikeshed and it's meant to preview a single file

OK, pr-preview isn't a suitable tool, here. That possibility is why I said "or similar".

[TallTed]

This is a HUGE change to the document. It's near impossible to coherently review, made worse by the apparent mix of markup and content changes. I cannot recommend strongly enough that this PR be re-attempted as multiple PRs, breaking it into at least changes to content and changes to markup, if not into multiple PRs comprising each of these. Lacking such breakup, it is all but certain that unintended changes will go undetected.

[TallTed]

Editorial. Typos and such.