Hi,
personally I'm a lot into the idea of a frontend component based
Sitebuilder like the one I created a poc for [1]. It is a simple concept
that is very very powerful in my opinion. But it was JSP-based and I
would rather like to have it Angular 2 based and would like to build up
some more Angular 2 knowledge on a project before abstracting from
Angular 2 :-). An other major problem I identified was, that I needed to
use internal (non-API) code to get the script(s) for the page that is
shown. But of course if that changes it wont work for me anymore.
To approach the Angular 2 project, I'm in the process of implementing a
release process to the Google cloud for Sling. It's available for a
single MongoDB but with a very rough and not always working
documentation [2]. Since a few minutes it is also working for a MongoDB
repl set. Documenting that and making some smaller adjustments is the
next step to do. It would be fun to implement the MongoDB sharding as
well but I won't need it in the near future so I have to pull myself up
and care about the things I need :-).
Best,
Sandro
[1] - https://vimeo.com/140369433
[2] - https://github.com/sandroboehme/sample-launchpad
Am 30.03.17 um 23:06 schrieb Daniel Klco:
All,
It seems like creating a Basic Sling CMS is an exciting topic for a lot of
people and something a lot of people are interested in. I've also been
working on something on the side as well for this, and I was wondering if
others would see this potentially as a good base to start with.
The idea here is to be somewhat more developer focused (at least in the
initial version) and somewhat limited in functionality, but to provide
basic functionality for managing web content. It was based on Publick
initially, but I found that was more single-blog focused than I wanted so
it's significantly diverged.
If you have a sec, I'd appreciate feedback and thoughts on the project. I
haven't had a chance to really document much about how it should work and
it's not 100% functional (aka don't try to edit a page) but a lot of the
core functionality is there.
https://github.com/klcodanr/sling-cms
Thanks,
Dan
On Thu, Mar 30, 2017 at 3:45 PM, Chris Millar (JIRA) <[email protected]>
wrote:
[ 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)
