We used it for an extranet for sales people. The company has different
brands, each brands contains different products and then the country is
divided in regions, sectors and target units. The nodes tree was then
convenient for this data structure. We have then different "documents"
(nodes) which contains "pages" and "components" (also nodes, like text
components, images, tables etc). A document is pre-filled by the management
with some data (charts, goals etc.), then for some component each user can
provide its own data (for instance update the text of a text component).
We found Sling useful because we don't have to architecture the data
structure for future components. Let's say we want to provide a Youtube
component that will display a Youtube video in the document, we just create
a new node with Sling:resourceType = myapp/component/youtube, set the video
URL, and add a specific view for this component. Before, it was all stored
in a database and not very flexible.
The front is just an Angular site sending requests to the Sling REST API,
as it's ready to use. Users/groups and privileges management was also a
good point as it's also ready to use and flexible. We didn't develop a lot
of things for content management. I was a complete Sling newbie at the
beginning of the project but with some spamming to the mailing list it
worked pretty well.
As lots of documents have the same skeleton, we just created a tool to do
bulk updates on nodes but that's pretty much it.
On Fri, Jan 13, 2017 at 4:28 PM, Jason Bailey <jason.bai...@sas.com> wrote:
> I know that Sling is used for 2 downstream CMS applications.
> I was wondering if anyone could share other use cases that they have found
> Sling to be useful for.