I enriched a bit further with regards to OSGi installer support in https://github.com/apache/sling-site/commit/b0951a5c2fb56b68d036d2e52a5adf488a19d8f0 <https://github.com/apache/sling-site/commit/b0951a5c2fb56b68d036d2e52a5adf488a19d8f0>
> On 8. May 2020, at 16:53, Robert Munteanu <[email protected]> wrote: > > Hi Ruben, > > On Fri, 2020-05-08 at 07:38 -0700, Ruben Reusser wrote: >> Hi Robert, >> >> this is awesome! I think it would be nice to also mention at [1] the >> ability to upload and deploy a content package through the composum >> UI. > > That's a very good point, added in > https://github.com/apache/sling-site/commit/c8a458ec . > . >> Also, should we move [2] from the peregrine repos to the sling >> samples >> instead? > > Sure, just include it in a PR for > https://github.com/apache/sling-samples . > > Robert > >> >> Ruben >> >> ]1] >> https://sling.apache.org/documentation/development/content-packages.html#deploying-a-content-package-at-runtime-1 >> [2] https://github.com/peregrine-cms/simple-sling-vue-example >> >> On 5/8/2020 7:00 AM, Robert Munteanu wrote: >>> Hi, >>> >>> As part of the sling 12 theme of content-package based development >>> I >>> kicked off a page to help users wrap their head around the concept. >>> >>> >>> https://sling.apache.org/documentation/development/content-packages.html >>> >>> I'm talking about things that are not fully familiar to me, like >>> the >>> Sling Project Archetype and the Sling Packager tool, so any input >>> is >>> welcome. >>> >>> Note that it's not supposed to be a comprehensive guide, but rather >>> a >>> starting point. >>> >>> Comments welcome. >>> >>> Thanks, >>> Robert >>> >
