Hello again,
I hope the Sitebuilder is of any interest.
Let me tell you what I personally like the most about it:
o Nested Frontend Components
o Being able to change the page with the Page Editor and with an
external editor interchangeably.
o The Frontend Components needing only a minimum amount of requirements.
Static HTML only needs a component CSS class and a component type
attribute.
And components that use repository content only additionally need the
component JSP tag or the JavaScript client library to load the component
resource data.
o The component JSP tag provides an own scope for proper isolation.
o Having a generic editor for the repository content. It should still
not be too hard to make it possible for component developers to provide
own editors for their content.
o Being able to mangage the component resource for the component
developers. They don't need to create, move or delete it. If the
component is moved to or from a script included with <sling:include/>
it's resource that delivers the content of the component is moved from
one parent resource to the other. (Does not yet work for nested
components but should not be hard to do.)
o At no time having any preview code in the final script that would need
to be removed before deployment.
I noted a lot to do's that have to be done until it's a releasable
version. Beside a general cleanup, error handling, avoiding page
refreshs and so on I would also like to make it possible to create
Sightly based components.
Best,
Sandro
Am 25.09.15 um 01:08 schrieb Sandro Boehme:
Hello,
as announced in my adaptTo() 2014 talk I worked on creating a CMS. What
I've got now is a proof of concept for a Sling Sitebuilder and a
frontend component API.
To see it in action and get an understanding of how it works I created a
demo video that you can find here (available in 0,5-1,5 hours):
https://vimeo.com/140369433
It gets more and more into the details so you might not need to see the
complete video.
My basic questions are:
o Is such a Sitebuilder actually something you and people you know want?
o Do you see special technical risks?
o Are you willing to cooperate on a Sling implementation or do you know
of people who are willing to?
o Do you know of a product that would benefit from the Sitebuilder and
whose company would want to collaborate on that in some way?
Thanks for any feedback!
Best,
Sandro
