it would be great if it gets the same bells and whistles as the
archetype AEM has at the moment and maybe starts aligning with the split
code and content structure a bit more as well.
Ruben
On 10/8/2021 12:34 PM, Andreas Schaefer wrote:
Hi
I did not work on the Project Archetype for a while but I am going to have a
look into it with respect to FMs.
There were some suggestions on how to improve it a while back and I will try to
find them again.
Cheers - Andy
On Oct 8, 2021, at 8:01 AM, Robert Munteanu <romb...@apache.org> wrote:
On Fri, 2021-10-08 at 08:44 -0400, Cris Rockwell wrote:
Hi
Shall we mark those archetypes as deprecated for now?
Yes. I can make that update to the site (if no one objects). It makes
sense to deprecate broken archetypes, at least temporarily. These
provide an initial starting point for developers looking to try the
framework, so I think they should not only work properly but also
have good documentation if possible. I also understand resource
constraints.
+1 from me.
I would be in favour of just maintaing the sling-project-archetype
and
making sure that a) it works and b) is a reasonable starting point
for
Sling-based apps.
FYI. I used sling-project-archetype two days ago. It worked well for
me. It provided a reasonable starting basis for my new project.
Good to know, thanks.
Robert
