Hi Oliver, As Bertrand said in his reply in this thread, we haven't seen much interest in Sightly beyond Sling / AEM users. While there are two plugins that hint at Sling specifics (data-sly-resource / data-sly-include) we actually think that these functionalities exist in various other web frameworks, under different names:
* data-sly-resource merely includes a resource from somewhere in your web app * data-sly-include provides a way to render a part of the output with a different view / controller combo in the context of the current request If in the future we see the interest of Sightly increasing outside of the Sling / AEM community we can always start a new project under the ASF umbrella and then provide a bridge for Sling. The specification will be hosted at https://github.com/Adobe-Marketing-Cloud in a few days. BTW, Brackets is an open-source code editor so it has nothing to do with Sightly, except for the fact that we've also developed an extension for it to ease web app development with Sightly in AEM. Cheers, Radu On Sat, Sep 27, 2014 at 3:23 PM, Oliver Lietz <apa...@oliverlietz.de> wrote: > Good to see one more modern alternative to JSP and ESP, welcome Sightly! > > The open-sourcing is really an important step in the right direction, but I > think there are better places for Sightly as template language. > Do not tie Sightly to close to Sling (AEM) when it could also be useful for > others in different projects and environments and prevent its proliferation > unnecessarily. > > A templating language/engine like Sightly could reach momentum like > Angular, > Bootstrap, Font Awesome, Markdown or Brackets. > > Adobe has already some places where they host successful open-source web- > related projects, e.g.: > http://html.adobe.com/opensource/ > https://github.com/adobe > https://github.com/adobe-webplatform > http://brackets.io > http://topcoat.io > > So +1 for hosting the integration but -1 for hosting the language > implementation. Which clearly means +1 for Sightly in general. >
