Hi Andy, On Tue, 2018-07-31 at 16:22 -0700, Andreas Schaefer wrote: > Hi > > I wanted to rekindle this discussion as my project-archetype (in the > sling-whiteboard git repo) is still open and nothing has happened for > the past 5 months. > > Someone mentioned that we should start a discussion about which > archetypes should be part of Sling and maybe merged and which one > should be retired. > > Headwire’s Peregrine CMS is using this archetype to generate user > packages but for the IDE Tooling (the last time I checked) content > can only be edited if it is part of a package rather than a bundle. >
We have not set any limitations to the sling whiteboard, so feel free evolve it as you see fit. I do believe that we should decide which archetypes we want to support. Already IMO we have too many and besides the usual arguments related to documentation and maintenance, it can be confusing for users to see many, potentially overlapping, archetypes. So the fewer the better, and if can achieve this with only one archetype - the one you propose - that's fine. But please start a dicussion with a concrete proposal on what archetypes to use. Thanks, Robert
