* Rephrase now that it's in core
* Skip the steps for checking out a custom repo. The code now comes with core.
* Change example paths to be more readable
* Misc copyedit

* Rephrase now that the code is in core
* Fix some links (since the docs are now split from the code)
* Move "Key features" above "General design" since it's quicker to read

1.  Don't describe the `.use-civicrm-setup` protocol.  This is used in one
    place, and it's likely to get inverted in the near future.

2.  When customizing the model, most values shouldn't be passed directly
    into `init()`.  Let `init()` detect its defaults.  Then call
    `$setup->getModel()` and customize that.  (I had tried customizing via
    `init()` when first implementing `cv core:install` and found it less
    useful.  There was also a support issue when someone else tried the same
    thing.) This pattern should work more intuitively.

Update hook_civicrm_entityTypes.md

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Removing reference to the word managed since it is confusing and mixes up entity types and entities

Add template_type

As per: https://github.com/civicrm/civicrm-core/pull/16529/files

Delete v3 api-architecture page

Update to confirm removal of Ubuntu 18.10 install steps.

Remove pass-by-reference from object variable.

Api4 changes for 5.23

Out of date even for v3, and supplanted by v4 architecture page.

Fix table display

colemanw authored 5 years ago and colemanw committed 5 years ago

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Add APIv4 architecture docs

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

Done has been deprecated for some time. Then is functionally equivalent and is forward-compatible with api4.

Reorganze Api4 Usage

Updates requirements

Remove pass-by-reference from form variable

My understanding is it's meaningless for objects

Clarify how to setup automatic publishing