Clarified when the backtrace is displayed, i.e. calling &backtrace=1 does not trigger an immediate backtrace unless an error occurs.

Update docs to reflect semver changes.

The phrase originated in one context (i.e.  discussing a change in the
version-numbering pattern).  In the context of `info.xml` docs, it seemed
helpful to use more concrete wording ("Because 4.7.x and 5.x are
substantively the same series...").

Updating docs to reflect changes made here: dev/release#1 (comment 2843)

add money/time estimate

publish.md: Add a section about extension translation

Added and improved civilint examples

Create hook_civicrm_alterAngular.md

colemanw authored 6 years ago and colemanw committed 6 years ago

See https://github.com/civicrm/civicrm-core/pull/10085
@totten I've added docs for this hook.

Update Doc For New API Action 'getunique'

Embed video walk-through for PR review

ref: https://jameshfisher.com/2017/08/30/how-do-i-make-a-full-width-iframe.html

Add docs for hook_civicrm_alterLocationMergeData

Create interacting-with-core

GitLab for issue tracking

Also:

- Clarify that PRs don't need to have associated tickets
- Clean up some language here and there

trivial: remove layer of quotes

Resolve #491 Reference hook_civicrm_coreResourceList in the advanced …

Docs style guide changes and improvements

Two arrows were being interpreted as two layers of quotes. I removed one of them. Then I thought, actually, these are not quotes. Maybe we should remove move. And maybe just having them on their on paragraph without any quotes is good enough. I am shying away from using boxes for this since to avoid box fatigue but would be interested in some opinions on the house style.

Add pointers to civix upgrade instructions