Details
-
Type:
Improvement
-
Status: Open
-
Priority:
Trivial
-
Resolution: Unresolved
-
Affects Version/s: 4.4.9
-
Fix Version/s: Unscheduled
-
Component/s: None
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:User and Admin Doc
Description
CiviCRM uses the term "CiviCRM Extensions Directory" to refer to two distinct (but related) things.
At civicrm/admin/extensions?reset=1&action=browse "CiviCRM Extensions Directory" is used in help text to refer to the website at https://civicrm.org/extensions which provides listings of CiviCRM extensions available for download.
At /civicrm/admin/setting/path?reset=1 "CiviCRM Extensions Directory" is used in labels to refer to the filesystem path at which CiviCRM extensions are downloaded for use.
Duplicating terms in related usage makes it unclear to new users what is being referred to, introducing barriers to adoption.
Since "directory" has an established meaning in compsci, I propose that we remove references to https://civicrm.org/extensions as a "directory" within the app. Alternate concepts: repository, library (similarly has established meaning), marketplace (commercial), listings, index.
(Both http://extensions.joomla.org/ and https://wordpress.org/plugins/ are titled "directory", but I don't those projects use duplicated terminology in the software UI.)