On Fri, 2020-11-06 at 07:24 -0800, Ruben Reusser wrote: > Robert, > > On 11/6/2020 6:07 AM, Robert Munteanu wrote: > > Hi Ruben and thanks for looking into this. > > > > On Fri, 2020-11-06 at 05:36 -0800, Ruben Reusser wrote: > > > Robert, > > > > > > had a quick look at this archetype - for a 1.0.0 release I am > > > missing > > > documentation around this archetype. > > What kind of documentation are you looking for? The archetype is > > referenced at [2], but nowhere else I guess. I find it simple and > > self- > > explanatory, but would be happy to add more information. > > I was hoping for something along the lines of the readme in the > project > archetype [3]
Thanks, added https://issues.apache.org/jira/browse/SLING-9882 . > > > > I am also curious if the Java Use Object it creates in apps is > > > really > > > a > > > good idea? After all, this is just a content archetype. > > The idea behind the archetype was to allow users to quickly > > generate a > > content package. They are free to adjust it how they see fit > > afterwards, e.g. by removing rendering scripts. > > > > Generally, I think it's more useful to bake more stuff in the > > archetype > > and allow users to remove it, rather than give them too many > > options or > > very 'slim' archetypes. And it makes maintenance for us much > > easier. > 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. I'm not saying you're wrong, I am not an expert in HTL. I added an use objects since I usually found it problematic to properly create one. What would say are best practices in this context? Thanks, Robert
