I removed this sentence because I don't think it's accurate.

We have these review criteria:
https://docs.civicrm.org/extensions/lifecycle/#review-criteria

The criteria do say that you can't use PHP overrides. But there are
other interfaces (like BAO functions for example) that are not in the
"supported methods" list but also not prohibited based on the extension
review criteria.

No content edits here. Just a direct copy paste.

Per discussion in documentation channel I think we need to document what methods are considered supported / expected to be stable. The last 4 items in this list have not been previously documented as a supported way to interact with CiviCRM so may be subject to discussion

Page should not link to itself.

ref:
https://github.com/civicrm/civicrm-wordpress/pull/112

I'm not sure if this has only come about because of my ineptitude (i.e. whether an Entity would always have the same name as the extension), but I found that I couldn't find the files referred to because my Entity and my Extension had different names.

Would that be bad practice on my part? (it would be good to know as I'm very new to coding)

Either way, I think this may be more accurate... rest is up to you.

Cheers,
M.

Find/replace `(?<=\w) {2,}` with ` `

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Previously it read that you only needed to create a release on *subsequent* releases, but my experience was that the extension was not available until the initial release was made also. Rewrote to clarify this.

Also made a few additions to inline docs on the create a release node page. These can be recorded over in CiviCRM.org website repo via Features.

Refs #323.

ref:
https://github.com/civicrm/civicrm-dev-docs/pull/301#issuecomment-324795431

Originally there were different types of extensions - payment processors, reports & modules. For a long time only modules have been recommended and I feel documenting the others only adds confusion.

https://wiki.civicrm.org/confluence/display/CRMDOC/Example+of+creating+a+payment+processor+extension

https://wiki.civicrm.org/confluence/display/CRMDOC/Testing+Processor+Plugins

https://wiki.civicrm.org/confluence/display/CRMDOC/Create+a+Payment-Processor+Extension

https://wiki.civicrm.org/confluence/display/CRMDOC/What+is+a+Payment+Processor

https://wiki.civicrm.org/confluence/display/CRMDOC/Page+Templates

https://wiki.civicrm.org/confluence/display/CRMDOC/Customize+Built-in+Profile+Contribution+and+Event+Registration+Screens

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