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. Cheers - Andy Schaefer > On Jan 22, 2018, at 2:13 AM, Robert Munteanu <[email protected]> wrote: > > On Sun, 2018-01-21 at 14:08 -0800, Andreas Schaefer wrote: >> Hi >> >> I added the project-archetype to the Sling Whiteboard under a branch >> feature/sling-7276. >> >> It should deploy just fine on the latest Sling (Sling Starter from >> GitHub). >> >> Let me know if I should merge this into ‘master’ or if you want to >> keep the code >> in that branch for the review. > > I personally don't see a point for having different branches in the > whiteboard - it's by definition a staging ground, so feel free to merge > to master. > > Robert
