This is an automated email from the ASF dual-hosted git repository.
dklco pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-app-cms.git
The following commit(s) were added to refs/heads/master by this push:
new 435e679 Update and rename plugins.md to creating-plugins.md
435e679 is described below
commit 435e679767ca9c4ff0474fe22fa38c00295e6afa
Author: Dan Klco <[email protected]>
AuthorDate: Tue Jan 28 12:05:26 2020 -0500
Update and rename plugins.md to creating-plugins.md
---
docs/{plugins.md => creating-plugins.md} | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/plugins.md b/docs/creating-plugins.md
similarity index 97%
rename from docs/plugins.md
rename to docs/creating-plugins.md
index 64d5d2d..e427998 100644
--- a/docs/plugins.md
+++ b/docs/creating-plugins.md
@@ -10,7 +10,7 @@
language governing permissions and limitations under the License. -->
[Apache Sling](https://sling.apache.org) > [Sling
CMS](https://github.com/apache/sling-org-apache-sling-app-cms) >
[Developers](developers.md) > Extending Sling CMS
-# Plugins
+# Creating Plugins
The Apache Sling CMS has a robust extension model for [extending the core
application](extending.md).
This guide will help you structure your extension to ensure upgrade readiness.
@@ -20,9 +20,9 @@ This guide will help you structure your extension to ensure
upgrade readiness.
Unlike custom applications, plugin code should be provided in the /libs path
under names folders.
The recommended folder naming is:
- /libs
- /groupId
- /pluginId
+ /libs
+ /groupId
+ /pluginId
This structure ensures that plugins from different providers do not conflict.
