Merge branch 'master' of https://github.com/civicrm/civicrm-dev-docs

docs/extend.md

 # Creating CiviCRM Extensions
 
-**CiviCRM Extensions** are packaged pieces of functionality that extend
-CiviCRM's out-of-the-box functionality, independent of CMS plaform.
-
-This section covers writing extensions, submitting extensions to the public
-extensions directory, and the review process for extensions submitted to the
-directory.
+This page is moving. See [writing extensions](/extensions/basics).
 
+<!--
 TODO:
-
--   General overview: Use APIv3 and hooks. Package code in Civi extensions or CMS extensions (w/trade-offs).
--   Assimilate: http://wiki.civicrm.org/confluence/display/CRMDOC/Create+an+Extension
--   Assimilate: http://wiki.civicrm.org/confluence/display/CRMDOC/Publish+an+Extension
--   Assimilate: https://wiki.civicrm.org/confluence/display/CRMDOC/Extension+Review
--   Create a CiviCRM extension developer's guide to best practices (Nicolas?)
--   Reference this page from the wiki and also https://civicrm.org/extensions (in the header).
+- delete this page after redirection in place
+-->

docs/extensions/basics.md

+# Writing Extensions
+
+Todo:
+
+- Use APIv3 and hooks. Package code in Civi extensions or CMS extensions (w/trade-offs).
+- Create a CiviCRM extension developer's guide to best practices (Nicolas?)
+
+## Introduction
+
+**CiviCRM Extensions** are packaged pieces of functionality that extend
+CiviCRM's out-of-the-box functionality, independent of CMS plaform.
+
+This section covers how to write extensions. See the [extension life cycle
+page](/extend-stages) for background on the publishing and review process for
+[published extensions](https://civicrm.org/extensions).
+
+## General overview
+
+If you haven't already, you need to configure a local directory to store
+extensions.
+For instructions, see
+[Extensions](https://wiki.civicrm.org/confluence/display/CRMDOC/Extensions)
+You may also want to review the
+[Extension Reference](https://wiki.civicrm.org/confluence/display/CRMDOC/Extension+Reference) page for technical details.
+
+### 0. Decide
+Writing an extension is a great way to implement a new feature – but it may be
+unnecessary if someone else has already implemented that feature. If you're not
+sure, you can do a couple things:
+- Search the [Extensions Directory](http://civicrm.org/extensions) for an existing extension.
+- Post about your planned extension in the [Extensions Channel](https://chat.civicrm.org/civicrm/channels/extensions).
+
+Extensions provide a native, portable way to extend CiviCRM, but there are
+other ways to extend CiviCRM – such as implementing Drupal modules or Joomla
+plugins. If you're considering another way, look at the
+[Add-on Formats](https://wiki.civicrm.org/confluence/display/CRMDOC/Add-on+Formats)
+to help decide.
+
+### 1. Install civix
+Some tasks in the process of writing an extension require boiler-plate code. To
+reduce the amount of work required to find, understand, and adapt the
+boiler-plate code, one should install the CiviCRM extension builder, civix.
+Civix is a command-line tool which generates code for some common development
+tasks.
+
+>> See [https://github.com/totten/civix/](https://github.com/totten/civix/)
+
+### 2. Develop
+To get started with development, one should usually follow the steps in
+"[Create a Module
+Extension.](https://wiki.civicrm.org/confluence/display/CRMDOC/Create+a+Module+Extension)"
+A module extension is the most flexible type of extension – it can define any
+mix of new reports, custom search screens, payment processors, and web pages;
+it can listen for hooks, override page-templates, and more. The coding
+conventions closely resemble those of CiviCRM Core and of CiviCRM-Drupal
+modules. Module extensions are fully supported in CiviCRM 4.2+.
+
+### 3. Publish
+The CiviCRM Extensions Directory provides a way to publicize your extension –
+and it even provides easy, in-app distribution.
+
+See: [Publish](http://wiki.civicrm.org/confluence/display/CRMDOC/Publish+an+Extension),

docs/extensions/civix.md

+Coming soon!

docs/extensions/config.md

+Coming soon!

docs/extensions/create-page.md

+Coming soon!

docs/extensions/custom-api.md

+Coming soon!

docs/extensions/custom-reports.md

+Coming soon!

docs/extensions/custom-searches.md

+Coming soon!

docs/extensions/customize-screens.md

+Coming soon!

docs/extensions/files.md

+Coming soon!

docs/extensions/payment-processor.md

+Coming soon!

docs/extensions/permissions.md

+Coming soon!

docs/extensions/storing-data.md

+Coming soon!

docs/extensions/using-hooks.md

+Coming soon!

mkdocs.yml

@@ -23,6 +23,20 @@ pages:
 - Hooks:
    - How to Use Hooks: hook.md
    - All Available Hooks: hooks-db.md
+- Writing Extensions:
+  - Basics: extensions/basics.md
+# - civix: extensions/civix.md
+# - Anatomy of Files: extensions/files.md
+# - Using hooks: extensions/using-hooks.md
+# - Customizing Screens: extensions/customize-screens.md
+# - Creating Pages: Forms/extensions/create-page.md
+# - Storing Configuration: extensions/config.md
+# - Storing Data: extensions/storing-data.md
+# - Setting Permissions: extensions/permissions.md
+# - Custom API Functions: extensions/custom-api.md
+# - Custom Reports: extensions/custom-reports.md
+# - Custom Searches: extensions/custom-searches.md
+# - Payment Processors: extensions/payment-processor.md
 - Miscellaneous:
    - Extension Lifecycle: extend-stages.md
    - Markdown: markdownrules.md

redirects/wiki-crmdoc.txt

 Documentation+Infrastructure+Canary develop
-The+developer+community basics/community
\ No newline at end of file
+The+developer+community basics/community
+Create+an+Extension extensions/basics
\ No newline at end of file