This is an automated email from the ASF dual-hosted git repository.
rombert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new c8a458e SLING-9434 - Add documentation for content-package based
development
c8a458e is described below
commit c8a458ec6537cfe4d9c59ddb0d84a7aed31a0a0e
Author: Robert Munteanu <[email protected]>
AuthorDate: Fri May 8 16:52:13 2020 +0200
SLING-9434 - Add documentation for content-package based development
Add section on composum UI, enhance notes.
---
.../content/documentation/development/content-packages.md | 13 ++++++++++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git
a/src/main/jbake/content/documentation/development/content-packages.md
b/src/main/jbake/content/documentation/development/content-packages.md
index 212460a..d26c754 100644
--- a/src/main/jbake/content/documentation/development/content-packages.md
+++ b/src/main/jbake/content/documentation/development/content-packages.md
@@ -66,12 +66,19 @@ After starting up Sling, the resulting file can then be
deployed with
$ npx slingpackager upload <content-package.zip> -i
+### Composum UI
-### Notes
+The Composum package manager allows performing multiple operations through its
user interface. To access the package manager, ensure that you are logged in to
the Sling Starter and then navigate to the Composum Package Manager at
[http://localhost:8080/bin/packages.html](http://localhost:8080/bin/packages.html).
+
+Some of the possible operations are:
-Inspecting the content package reveals that is is just a ZIP file with
additional metadata.
+- building content packages from existing content
+- uploading and installing existing content packages
+- uninstalling existing content packages
+
+### Notes
-After deploying the content package, ensure that you are logged in to the
Sling Starter, and then navigate to the Composum Package Manager at
[http://localhost:8080/bin/packages.html](http://localhost:8080/bin/packages.html).
You will see the content package as listed and will be able, for instance, to
uninstall it.
+Inspecting the content package reveals that is is just a ZIP file with
additional metadata. Of definite interest are the manifest -
`META-INF/MANIFEST.MF` and the filter definition - `META-INF/vault/filter.xml`.
The [Sling IDE Tooling](/documentation/development/ide-tooling.html) has
support for exporting and importing content incrementally to a Sling instance,
and can be used alongside the Maven-based tooling.
