We ha one "Generating a skeletal extension" and one "Add features"

Add health warning about running Docker on OSX

Per https://en.wikipedia.org/wiki/Uniform_Resource_Identifier#URI_references
it seems that something like `/foo/bar.md` isn't technically a "URL".
So to be more accurate with our language, this commit changes the meta
docs to refer to internal "links" instead.

This is a significant revision of the PHPUnit documentation. This specifically:

* Adds concrete examples of writing tests in various styles (`CiviUnitTestCase`, `CiviEndToEndTestCase`, `civix`)
* Adds reference documentation for classes/traits/interfaces provided by Civi's test library
* Imports key information from Testapalooza docs (#389)

Changed `civix generate:custom-data` to `civix generate:custom-xml` as the former is incorrect. Also corrected grammar in subheading "Extending a subtype".

There are usually a few branches to choose from when picking a base-branch.
This breaks out a table to differentiate them.

Include Survey in the list of pre and post entities and alpha sort the post entities like the pre entities

We really don't need such an exhaustive list of examples in this context.
That material is better handled in the User Guide, which is hyperlinked.
All we need to do is demonstrate the basic idea of a token.

These documents are misleading -- they talk about CiviMail because, *historically*,
much of this grew out of CiviMail. However, *today*, tokens are used more generally.
Also, in `civicrm-core`, `TokenProcessor` is *not* used by CiviMail. (You have to
install FlexMailer to use it.)

The old section signal a few things:

1. "CiviMail design needs to handle HTML/Text" - but this can be more concisely stated as part of he requirements summary. Added a blurb there.
2. "The `{action.unsubscribe}` is used differently in each context" - but this is better explained as part of the *User Guide* for CiviMail.

Arguably, in the context of CiviMail developer docs, we should also signal "How to manage token content with text-vs-html", but this section
doesn't actually do that, and that's already signalled in the examples of extending the token system.

Discussed on `dev` with Seamus and Mathieu.  None of us could make any sense
of it.  It feels like an old spec pre-dating the actual writing of CiviMail.

totten authored 7 years ago and colemanw committed 7 years ago

* CRM-20981 - Call `useApp()` instead of stringing together fiddlybits.

https://issues.civicrm.org/jira/browse/CRM-20981

* Fix inline monospace broken across two lines

MkDocs was displaying this without the space between div and ng-app.

* Custom ng base pages - re-arrange content

* loader.md - Put the load() call in the right spot