[
https://issues.apache.org/jira/browse/SLING-6666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932582#comment-15932582
]
Dan Klco commented on SLING-6666:
---------------------------------
[~olli] I love this idea. I've been tossing the same idea around. Composum does
seem like a good starting place as a foundational framework to work off. Would
it make sense to work towards integrating some sort of basic usable Sling CMS
for Sling 10, given how close we are / should be to Sling 9?
I was thinking the first step would be to decide on a subset of functionality
and implement that. In general, I would think we'd want to support a simpler
use case and try to gear the functionality towards simplicity and convention
over flexibility and complexity. In terms of target, I was thinking it would be
Small / Medium Businesses / Non-Profits which want to implement a fairly simple
content-driven application and would currently use a Drupal, Joomla or
Sharepoint.
I was thinking your structure would be more rigid in how it uses the JCR, ex:
- All "published" content lives under /content
- The first level is a "site" or "collection"
- All "site" content is self-contained, e.g. files, pages, etc
- All "non-published" content / configuration lives under /etc in a similar
folder
Is that somewhat similar to what you were thinking in terms of goals and
objectives?
> Make Sling shiny
> ----------------
>
> Key: SLING-6666
> URL: https://issues.apache.org/jira/browse/SLING-6666
> Project: Sling
> Issue Type: Task
> Components: General
> Reporter: Oliver Lietz
>
> https://cwiki.apache.org/confluence/display/SLING/Make+Sling+shiny
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
