Move the multisite installation from the SysAdmin guide

See merge request !22

Timestamp mismatch warnings link to this doc - make it more useful.

See merge request !23

Add historical PHP & MySQL compatibility info

See merge request !24

Remove the section on clean URLs in WordPress

Closes #7

See merge request !20

This is being migrated to the SysAdmin guide as it is no longer required
for new installations

Docs for how to use unicode fonts for pdf output

See merge request !19

Change some broken absolute links to relative links

See merge request !18

sysadmin#3 - Rework "Get the code" and "Run the installer"

See merge request !15

General themes/changes:

* Rewrite as a standalone page. This was previously content in the D8 page.
* Include the `curl ... cv.phar ...` command.
* Move discussion of the `core:install` options and common problems into collapsed admonitions.
* The "next level" docs for `cv core:install` are in the Dev Guide. Add links.
* Add a section for "Configure the site".
* Add a "Limitations" section.

* Use simpler language
* For optional commands, link to relevants docs.

* There are a lot of details that can live inside collapsed sections.
* Several of the asides are basic gotchas that would affect any effort to
  run composer on D8. Combine these into one collapsed section,
  "Quick and dirty introduction to D8 with composer"
* The headings "Expert mode"/"Guided mode" are weird to me -- because
  (1) "Expert" identifies the most common/easiest variation of the command,
  and (2) "mode" suggests software-mode, but it's actually a different
  presentational style for the documenter. Instead, just give one
  procedure - and provide drill-down options for explanation.

* As in the previous commit (D7/BD), there are two workflows, web-based an CLI-based.
  Put them in collapsible admonitions.
* Reorganize the warnings for the web-based workflow.
* The D8 section had more discussion of the CLI steps. Move these over to the `cli-cv.md` file.
  They'll still need more editing, but it makes sense for this more advanced+verbose
  use-case to have a separate file.

* There are two distinct workflows, web-based and CLI-based. Put them in collapsible admonitions.
* For web-based flow, use "activate-first" / "civicrm-setup" workflow instead of
  the `sites/all/modules/civicrm/install/yaddayadda` workflow
* Remove older warning module-activation. It's no longer a bad thing if an admin
  activates on their own accord.

* Make it easier to skip past the stuff about the developer guide
    * Change the header "Similar alternatives" to "Alternative: Civibuild for developers"
    * Mark the section collapsible (default closed).
* To make the styling of the front-matter more consistent, update "About this document"
  to also be collapsible (but default open).

requirements.md - Add a "Summary" section

See merge request !12

Add note about composer compile plugin and update to use version 1.1 of the asset plugin

See merge request !16

Boatload of header cleanup

See merge request !14

OK, so you go through a bunch of steps and come to these instructions:

> There should now be a CiviCRM link in your Drupal menu.  Click that link and
> the CiviCRM Menu, Shortcuts, Search and New Individual Blocks should appear.
> You can now explore CiviCRM end-user features and begin configuring CiviCRM
> for your site/organization needs.

This should be the end of the installation guide. But, if you skim the TOC,
it keeps on going!

I *think* what's going on here is that people wanted to add some sections
which are sort of independent of the main flow of installation.

These probably should be moved/referenced in some other way, but I don't
really want to think too hard.  This commit just mitigates the confusion
a bit by setting the subsequent sections (re:MySQL encryption and troubleshooting)
under the heading "Addenda".