https://wiki.civicrm.org/confluence/display/CRMDOC/Contributing+to+CiviCRM+using+GitHub

https://wiki.civicrm.org/confluence/display/CRMDOC/Tarball+installation+testing

https://wiki.civicrm.org/confluence/display/CRMDOC/Smart+group+testing

https://wiki.civicrm.org/confluence/display/CRMDOC/Dedupe+and+merge+testing

https://wiki.civicrm.org/confluence/display/CRMDOC/Manual+testing

mark `<requires>` and `<ext>` as experimental, and link to the PR which
makes them functional.

Why? Because right now there's where lots of other content exists which
is pretty similar to this page. And there's no "reference" chapter. I
think that once we're finished with the wiki migration we might like to
clean up that "framework" chapter a bit by moving some pages around. But
until then, I think it's easiest if we keep content together which is
similar.

Issue 92 Rename API Paramaters to API Options and also port in Custom Data Documentation to help with Issue 92

ref:
https://chat.civicrm.org/civicrm/pl/hpzkpu7ck7g9jnqh1rrqeqh1gw

https://wiki.civicrm.org/confluence/display/CRMDOC/Database+layer

https://wiki.civicrm.org/confluence/display/CRMDOC/Section+elements

https://wiki.civicrm.org/confluence/display/CRMDOC/Notifications+and+Confirmations

https://wiki.civicrm.org/confluence/display/CRMDOC/In-Place+Field+Editing

https://wiki.civicrm.org/confluence/display/CRMDOC/Icons

https://wiki.civicrm.org/confluence/display/CRMDOC/crmDatepicker

https://wiki.civicrm.org/confluence/display/CRMDOC/Buttons

https://wiki.civicrm.org/confluence/display/CRMDOC/Accordions