[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954098#comment-15954098 ] Sandro Boehme commented on SLING-: -- I'm happy to see the ideas and improvements. SLING-3987 would also make Sling more shiny but I understand that it's a very big endeavor. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > Attachments: Sling-4x.png > > > https://cwiki.apache.org/confluence/display/SLING/Make+Sling+shiny -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950516#comment-15950516 ] Bertrand Delacretaz commented on SLING-: Thanks [~auniverseaway] for the refreshed logo, I like it! I'm +1 for switching to it once it we have it in vector format with a TM, and we should then credit Chris somewhere on our website. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > Attachments: Sling-4x.png > > > https://cwiki.apache.org/confluence/display/SLING/Make+Sling+shiny -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15950507#comment-15950507 ] Oliver Lietz commented on SLING-: - [~karlpauls], you cannot hijack this issue... 8D _Making Sling shiny_ is a community effort and everyone is welcome. I also started to _fix_ the logo a while ago and therefore picked SLING-2696 to get it done finally – [~auniverseaway], can you provide your logo update in a vector format? [~klcodanr], thanks for starting a discussion on [dev@|https://lists.apache.org/thread.html/3e0841adfb2315ae18afb62769dafdbf1703369ed8906372d395f60a@%3Cdev.sling.apache.org%3E]. Our findings should be collected in the wiki and tasks filed in separate issues. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > Attachments: Sling-4x.png > > > https://cwiki.apache.org/confluence/display/SLING/Make+Sling+shiny -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949785#comment-15949785 ] Stefan Seifert commented on SLING-: --- nice logo proposal! - there is a separate ticket for logo update: SLING-2696 - we also need to add a TM to the logo, see link in the ticket. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > Attachments: Sling-4x.png > > > https://cwiki.apache.org/confluence/display/SLING/Make+Sling+shiny -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15949678#comment-15949678 ] Chris Millar commented on SLING-: - 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- > URL: https://issues.apache.org/jira/browse/SLING- > 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932611#comment-15932611 ] Karl Pauls commented on SLING-: --- [~bdelacretaz] I agree. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932585#comment-15932585 ] Bertrand Delacretaz commented on SLING-: ...it sounds to me like a big part of this conversation belongs on dl-dev instead... > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932582#comment-15932582 ] Dan Klco commented on SLING-: - [~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- > URL: https://issues.apache.org/jira/browse/SLING- > 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932574#comment-15932574 ] Karl Pauls commented on SLING-: --- [~olli], I understand and I think it is a laudable effort and I'm all for it. I think we can and should tread that independently from positioning - again, I didn't want to hijack this issue. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932547#comment-15932547 ] Roy Teeuwen commented on SLING-: Last year when I contacted the devs of composum they also mentioned they were working on a CMS for sling, which will also be in the github of composum as an extra bundle, so I'm very curious on when and how this will work out! > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[
https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932543#comment-15932543
]
Oliver Lietz commented on SLING-:
-
[~karlpauls], let me define *pure Sling*: Sling and any extensions under ASL or
compatible license (e.g. Composum, Slick or whatever).
Most people I've talked to in the past regarding Sling are missing a modern UI
for doing even simple tasks like managing users or resources. We have several
attempts in Sling's repo (samples, attic) for UI but all failed. Having
Composum in Launchpad is a milestone and it makes Sling already some kind of
CMS. In Sling's Karaf Distribution it's only clicking install
{{composum-sling}} and you're done (it's part of Sling Karaf since November
2015). Bringing Sling onto Karaf (providing a better OOTB experience IMHO) and
Thymeleaf to Sling are my personal efforts to _make Sling shiny_.
> Make Sling shiny
>
>
> Key: SLING-
> URL: https://issues.apache.org/jira/browse/SLING-
> 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932495#comment-15932495 ] Karl Pauls commented on SLING-: --- 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- > URL: https://issues.apache.org/jira/browse/SLING- > 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)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932433#comment-15932433 ] Oliver Lietz commented on SLING-: - Of course it makes sense to have sub-tasks. I've added a [page|https://cwiki.apache.org/confluence/display/SLING/Make+Sling+shiny] in Sling's wiki to collect some ideas and tasks. Feel free to extend. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932399#comment-15932399 ] Robert Munteanu commented on SLING-: I fully agree. Maybe it makes sense to have some sub-tasks for this which group general directions? > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932395#comment-15932395 ] Oliver Lietz commented on SLING-: - That means lots of work to be done. 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. Adding Composum to Launchpad or [~sseif...@pro-vision.de]'s effort regarding plugin documentation are very helpful to accomplish that mission. > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SLING-6666) Make Sling shiny
[ https://issues.apache.org/jira/browse/SLING-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15932344#comment-15932344 ] Robert Munteanu commented on SLING-: That sounds good, but what exactly does it mean :-) ? > Make Sling shiny > > > Key: SLING- > URL: https://issues.apache.org/jira/browse/SLING- > Project: Sling > Issue Type: Task > Components: General >Reporter: Oliver Lietz > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
