1. An [[!inline directive cannot be turned into a <pre> through markdown
indentation, nor can it be inserted inside a <pre>. Plus either <pre> or
white-space indentations properties insert an extra new line on top of
the section.

2. ikiwiki interprets <tails@boum.org> as an email address so we have to
escape < and >.

We'll generate this at release time. This will remove all possible
ambiguity on the date, possible replay attacks, very quick emergency
releases, etc.

Source Code appears a bit bigger and darker than Courier at equal size,
so we can actually make it a bit smaller in our CSS. This will allow us
to put longer command lines and command line outputs in our page without
wrapping.

Conflicts:
	wiki/src/install/expert/usb.mdwn

Conflicts:
	wiki/src/install/mac/clone.mdwn

We're merging the current state of web/assistant in order to test some
parts of it live, especially the new download page.

We can add it back once we get there.

Conflicts:
	wiki/src/download.inline.mdwn

We will have to revert it for production.

According to http://blog.axe-net.fr/noindex-nofollow-robots-txt-attention-erreurs/ we need noindex on each page. Robot.txt does not prevent google to link.
We probably will have to put this directive on each page.

Because ikiwiki compile our <p class="pre"> as <p><p class="pre"> inside
instructions steps.

We have to using <p class="pre"> here instead of <pre> because ikiwiki
directive inside <pre> are not interpreted.

The default width for <pre> is a bit short for the command lines in this
scenario, so let's try to:

  - Remove the left margin as we don't have infography for the expert
    scenario anyway.
  - Increase the width of <pre> paragraphs at the maximum.