On Wed, 2020-11-11 at 18:03 +0100, Radu Cotescu wrote: > Hi, > > > On 6 Nov 2020, at 16:24, Ruben Reusser <[email protected]> wrote: > > > > I totally understand the idea behind why to put a simple html > > component into the content package. I however struggle with the > > fact that Java Use Objects are probably not a best practice for > > sling projects or other upstream projects. Maybe I am wrong here. > > Ruben is right - Java Use Objects in the resource tree are not the > best idea. With HTL it’s better to use Sling Models for the Use API, > albeit these are not content structures. However, I’d really avoid > encouraging people to still use Java Use Objects, even though they’re > still supported.
Ack, thanks. Then I guess there would be no need to bundle anything like that in the archetype. We _could_ use a Sling Model, but I don't think we have anything OOTB in the Sling Starter, and that's probably best left to comprehensive archetypes like [1]. Thanks, Robert [1]: https://github.com/apache/sling-project-archetype
