[
https://issues.apache.org/jira/browse/SLING-6666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932495#comment-15932495
]
Karl Pauls commented on SLING-6666:
-----------------------------------
First of all, I completely agree that Sling could do with some polish and it
would be great to get more adoption. Furthermore, I think all the points listed
on the wiki page are spot on in that regard.
However, I'm not sure about the mission statement on that page namely,
"Users should be able to run pure Sling in production with good experience
(compare to django CMS or Drupal) for small to enterprise size websites or
applications. Besides Sling itself it means improving documentation and Sling's
website (not only content but appearance also) to attract more users and bring
it out of the shadows."
At least until now, Sling is positioned as a (content-driven) web framework.
Above statement seems to somewhat reposition it as a CMS or at the very least
as also being able to use it as a CMS out of the box. Not saying I don't think
that is a worthwhile goal or a good idea but it feels like it warrants a
discussion.
Personally, I think it would be very valuable to have a more clearly defined
target audience for Sling in order to increase adoption. I just think it should
be a conscious choice - partly because we don't have that many resources and
partly because we have such a weak target to begin with.
In other words, if we would be able to pitch Sling to "user-type" X, what
reasons Y would we use why Sling is a perfect fit for them. IMO, that is needed
to, subsequently, define the measures Z we need to take to make that a reality.
Again, don't get me wrong, I think this a great initiative and my comments are
not meant to delay it in any way (as I said, the tasks list looks great already
and I think we need to address all of them regardless of positioning). Just
wanted to point out that we might also want to think about who we want to
attract and a how we can do a better job at doing so.
> 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)
