On Monday 22 September 2014 10:59:59 Radu Cotescu wrote: > Hello, > > On behalf of Adobe Systems Inc. I'd like to contribute two modules to > Apache Sling: > > - org.apache.sling.scripting.sightly > - org.apache.sling.xss > > > Sightly is the new web templating language shipped with Adobe Experience > Manager 6.0 [0]. Our contribution to Apache Sling is a Java-based > implementation, fully compliant with the language's specification. However, > the language's specification is and will be owned by Adobe. > > For Sightly's contextual-based automated XSS escaping feature we're also > donating the org.apache.sling.xss bundle that provides two useful services > meant to help escaping or filtering user-submitted content that might be > prone to XSS attacks. > > While the XSS module contains a decent amount of unit tests, the Sightly > implementation was tested using a proprietary (for now) UI testing > framework. I'm currently working on porting those tests into a test runner > that will be made available under an Apache License on Maven Central; this > runner could easily be integrated into Sightly's build process in the near > future. > > SLING-3959 [1] has been opened to track the donation progress and the > bundles are attached there. If the Sling community finds this donation > interesting we can carry on with the IP clearance.
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. What about sightly.io and GitHub (which could be a place for the language's specification also)? Regards, O. > Thanks, > Radu > > *Sightly Credits:* > Senol Tas, Honwai Wong - initial language specification and implementation > Gabriel Walt - product manager, language specification > Marius Dănilă, Radu Cotescu, Sameer Charles - Java implementation and > JavaScript Use-API support > Cătălin Buzoiu - engineering manager > Feike Visser, Florin Iordache - early adopters implementing projects with > Sightly, who provided valuable feedback during Sightly's development > process > > [0] - http://docs.adobe.com/content/docs/en/aem/6-0/develop/sightly.html > [1] - *https://issues.apache.org/jira/browse/SLING-3959 > <https://issues.apache.org/jira/browse/SLING-3959>*
