Hi, I was thinking about converting the Slingshot sample [1] to a content package build.
The advantages would be: - we demonstrate how to use content packages with Sling - better supported by the IDE tooling - remove the need for code that alters the repository on startup such as [2] - increased validation for content package tooling as part of the starter The main disadvantage that I see would be a more complex repository structure ( reactor build with bundle + content package + (probably) apps package ). Thoughts? Robert [1]: https://github.com/apache/sling-samples/tree/master/slingshot [2]: https://github.com/apache/sling-samples/blob/47388d327fd19b629448192a9692dd3ac01ddab5/slingshot/src/main/java/org/apache/sling/sample/slingshot/impl/SetupService.java
