So What is SliMpoGrine?

SliMpoGrine is about how far we can get with existing open-source solutions on self-hosted Sling. The Sling Starter already comes with Composum applications on top, developed by IST, that provide basic functions like Nodes-Browser (think crx/de), User-Manager and Package-Manager for import/export of content.

And with this groundwork, others were able to develop their own CMS's on top. Here we leverage Sling's OSGi Feature Model to glue together two of them and this silly example into our own application server.

This is not software on it's own but rather a combination of quite a lot open-source software developed by others into something new.

SliMpoGrine Participants

The participating CMS's are Composum's Pages+Assets as well as Peregrine-CMS. They both provide a WYSIWYG editor for websites, but with radical different approaches. The first one generates good old HTML, Peregrine renders a vue.js Single-page application. Both share the same repository and just live next to each other within the same Micro-Service / docker-image.

Noteable CMS's not included:
The offical Sling CMS App because like with most of Sling it lacks a bit of visual bling. But for general concepts it's worth a look, especially for cloud-deployment pipelines. There is WebSight, with a free community edition but not open-source. And there is Adobe's Experience Manager which is not free at all but actually powers the development of Sling.

SliMpoGrine Benefits

The shown content should explain the 'how did we get here' in form of text-components with code-blocks and diagrams in future. Content can be synched back into sources on github after creation and become part of the SliMpoGrine server.

SliMpoGrine Requirements

Required is a general interest in Java middleware... tbc