[
https://issues.apache.org/jira/browse/SLING-6666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949678#comment-15949678
]
Chris Millar commented on SLING-6666:
-------------------------------------
I'm probably speaking out of turn, but I have many thoughts on this.
First, I agree with what everyone is saying. Sling needs some presentation and
branding love. I would break this down into the following buckets:
# Docs - The information architecture of sling.apache.org needs to be
addressed... Raise your hand if you need quick access to Sling 5 docs in the
sidebar.
# Marketing and Polish - Basic things like the site not being responsive or the
logo being woefully out of date.
# Better On-boarding for Developers - Someone who wants to run java -jar
org.apache.sling.jar and start building something. How do you get from 8080 to
443?
# Better On-boarding for Contributors - Someone who wants to start working with
the guts of the project.
# Better On-boarding for Users - A basic CMS...
I really like the idea of everyone rallying around some _basic_ CMS for Sling.
I would argue it should be a pure SlingPostServlet / UserManager solution over
trying to make a tool like Composum or Slick bend to this purpose. Composum is
more of a CRX/DE Lite replacement and Slick is _way_ too opinionated about its
UX.
I'll start adding some more thoughts to the wiki and will attach the logo I
updated for Sling a while ago. I'll also subscribe to the dev channel as
[~bdelacretaz] suggested.
> 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)
