If you need to store any kind of content, Sling is a great option. To that extent, it's hard to imagine what Sling /couldn't/ be used for. It's very flexible.
I think recent contributions by Adobe to bring Oak and HTL (formerly Sightly) to Sling makes it even easier to build out a fully functioning web application. Best of all, it's enterprise grade since it sits on top of Java and OSGi. As Robert mentioned, Slick is a good example of how one developer can build out a fairly robust application. It just happens to be focused on blogging. There's nothing preventing a social network, a digital asset manager, really anything you can think of. There's been rumblings that McDonald's used Sling to power their nutrition information on their site. This is a good distinction between a monolith like AEM, and leveraging a lighter weight framework like Sling. Lastly, because JSON is a first class citizen in Sling, it makes for a great engine to power modern day applications that may be based on Angular, Handlebars, or even native mobile applications. I'm definitely bias, but with Sling I can run a single jar and get authentication, data storage, elegant templating, etc. all rolled in. No MySQL connectors, no PHP vulnerabilities, no NPM headaches. It just works. With the SlingPostServlet, you don't even have to know Java. You can build a couple web forms and start running. -- View this message in context: http://apache-sling.73963.n3.nabble.com/uses-for-Sling-tp4069596p4069624.html Sent from the Sling - Users mailing list archive at Nabble.com.
