From e43bf641b71430a12a05f58860fa8460f12f54b8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Frank=20J=2E=20G=C3=B3mez?= <frank@ginkgostreet.com>
Date: Sun, 8 Jan 2017 23:07:19 -0500
Subject: [PATCH] The removed language is out of place for the following
reasons:
1) This seems like a site admin task, not a developer task. If you're reading this page, I assume you
already know how to do this. I'd argue this belongs in the user guide (if it's not already there).
2) It doesn't seem right to me that one should configure their extensions directory before
deciding whether or not to write an extension. First check the extensions directory to
see if someone has already built the thing. If not, only then does make sense to start
playing with your environment config.
3) If we keep it in the developer guide, I'd put it at the beginning of the instructions
for creating a module extension (https://wiki.civicrm.org/confluence/display/CRMDOC/Create+a+Module+Extension).
These are currently undergoing migration from the wiki to mkdocs, so I'm blocked from making such
an update at this time.
---
docs/extensions/basics.md | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/docs/extensions/basics.md b/docs/extensions/basics.md
index 198cb856..6effd4c5 100644
--- a/docs/extensions/basics.md
+++ b/docs/extensions/basics.md
@@ -45,15 +45,6 @@ different short-name, but that requires extra work.
by the www-data user. You will need to make this file readable by
your development user account for civix to work.
-## General overview
-
-[]( fixme paragraph this section into above notes )
-
-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).
-
### 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
--
GitLab