I've been refining the Sling CMS example over the last couple months. Recently, I switched it over to use CA Configs rather than the /etc based configurations, made some minor UI tweaks and drastically improved reordering sibling resources.
I also added some more reference components (RTE, lists, rss, sitemap, containers, column control, image block, etc: https://github.com/apache/sling-whiteboard/tree/master/cms/reference/src/main/resources/jcr_root/apps/reference/components/general) and added a default configuration, so you can immediately start using the tool to create something like sling.apache.org. You can see how easy it is to get started with your first page here: https://www.danklco.com/images/Sling-CMS.gif And speaking of which, I re-wrote my personal site to run on Sling CMS. It's running on a very underpowered Google Computer Engine F1-Micro instance, so please be nice to it. I suspect it would run pretty well on a g1-small or equivalent server, but I have not had a chance to validate. You can find the code for my site application here: https://github.com/klcodanr/danklco.com-site/tree/sling-cms Right now Sling CMS is using a number of unreleased dependencies, so the easiest route to check it out is to download the JAR from the Apache Snapshots Repo: https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.cms.builder/1.0.0-SNAPSHOT/org.apache.sling.cms.builder-1.0.0-20180503.214823-11.jar I'm thinking that I'd like to get this moved into the Sling Samples repo or potentially a separate repo shortly. The only one additional thing I'd like to figure out is getting a HTML5 rewriting pipeline. Is anyone aware of a HTML5 Rewriting pipeline implementation? It seems like the default one is HTML4. Regards, Dan On Fri, Mar 2, 2018 at 4:33 PM, Daniel Klco <[email protected]> wrote: > > > On Fri, Mar 2, 2018 at 7:26 AM, Ioan Eugen Stan <[email protected]> > wrote: > >> Hi, >> >> > Yep, indeed. Currently I'm working on building out some reference >> > components like search, lists, column controls, text editors, etc. >> That would be awesome. We would like to use such components in our setup >> and we might help with some development and maintenance along the way. >> That would take some time dough. >> > > Yep. I've made some of these, but it's still pretty basic and some are a > bit clunky. > > >> >> IMO we should be able to make the artifacts available as part of a >> release process. >> > > Absolutely. I'm thinking that these could be a standalone related project > so it can be versioned separately from the CMS as a whole. > > >> Is this part of the apache project or a you private project. I'm asking >> because I would like to do some work in that direction (release as often >> as possible). >> > > It's in the Sling Whiteboard: > https://github.com/apache/sling-whiteboard/tree/master/cms > > >> >> - is there any relationship between sling-cms and Composum? It seems to >> >> me like both projects are heading in a similar direction and a >> >> colaboration might be beneficial. Composum provides Composum assests, >> >> Composum Pages, etc. That functionality could be reused. >> >> >> > Not at the moment, I did add in Compsum for the package and node >> explorer >> > capabilities, but I didn't realize Compsum Pages and Assets were so far >> > along. >> > >> Have you had time to check them out? Can Sling CMS use those compnents? >> Will they be used instead of internal/custom ones? >> > > I've looked through the documentation for Composum Pages / Assets. It > looks like they have taken a different approach, but the assets in > particular is really nice. I'll try to download it soon and check it out. > >
