Adobe Experience Manager Sites & More

alexander_petit · 10/15/15

what about : http://www.sightly.io/ ? still down :-/

smacdonald2008 · 10/15/15

Here is a good topic that explains Sightly:

http://dev.day.com/content/docs/en/aem/6-0/develop/sightly.html

As far as this URL - www.sightly.io - it does not appear valid.

View solution in original post

smacdonald2008 · 10/15/15

Here is a good topic that explains Sightly:

http://dev.day.com/content/docs/en/aem/6-0/develop/sightly.html

As far as this URL - www.sightly.io - it does not appear valid.

gabriel_walt · 10/15/15

We did initially setup sightly.io with some info about Sightly, but finally decided to rather centralize everything on the docs. The link you provided is indeed the place to go now.

And btw, there are several blog posts on that topic:

alexander_petit · 10/15/15

thx so far... - but - how do I integrate slightly in my maven build (do I have to extract your jars ??) and - is there any support for eclipse ide ?

gabriel_walt · 10/15/15

Here you go for building Sightly:
Java Doc: http://docs.adobe.com/content/docs/en/aem/6-0/develop/ref/javadoc/com/adobe/cq/sightly/WCMUse.html
Public Maven Repository: http://repo.adobe.com/nexus/content/repositories/releases/com/adobe/aem/aem-api/6.0.0.1/

Basically, following blog post also explains how to setup the AEM Maven dependencies: http://experiencedelivers.adobe.com/cemblog/en/experiencedelivers/2014/05/aem6-maven-dependencies.ht...

All of this is currently being added to the official documentation and should be published very soon.

Concerning the Eclipse Support, we are currently finishing a plugin that we try to make available within the next weeks. Thanks for your patience, stay tuned! ;)

The first version of that Eclipse plugin though will not have yet any special support for Sightly. For now, only the Brackets plugin that we intend to release in the next couple of days has some Sightly support (highlighting + code completion). But both plugins will offer a similar workflow that will allow you to work on your AEM project on the file system and the plugin automatically pushes changed files (or .content.xml files) to your running dev instance for checking out what changed. In addition to that, the Eclipse plugin will also have the capability to update bundles on your instance if some changes were performed in their code, and it will even be capable of hot code replacement if debug mode is turned on (i.e. skipping the bundle restart that can trigger various events).

Also following forum post might be of interest to you: Getting started with Sightly.

Hope that clarifies.

gabriel_walt · 10/15/15

FYI, we've just released the plugin for Brackets and Eclipse:
http://docs.adobe.com/docs/en/dev-tools.html

ryan_donovan · 10/15/15

Using the eclipse plugin / slightly example, I notice that the sidekick is not coming up for the pages. e.g. The 'English' page using the maven archetype7. Straight install.

Is there a reason sidekick doesn't work?

ryan_donovan · 10/15/15

The templates/examples don't seem to have the init for the sidekick from global.jsp. what is the slightly tag for such a trigger?

eglistefan · 10/15/15

Ryan Donovan wrote...

The templates/examples don't seem to have the init for the sidekick from global.jsp. what is the slightly tag for such a trigger?

Good point indeed! The example lacks this inclusion.

To work around this - until we have a new archetype released - you can add the following line to /apps/myexample/components/page/page/page.html right before the existing head-tag:

<head data-sly-include="/libs/wcm/foundation/components/page/head.html" data-sly-unwrap/>

Report · 10/15/15

Hmm, I assume you meant this (but Sidekick still didn't appear) .. any ideas ? :-

<html lang="en" data-sly-use.clientLib="${'/libs/granite/sightly/templates/clientlib.html'}"> <head data-sly-include="/libs/wcm/foundation/components/page/head.html" data-sly-unwrap/> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <meta http-equiv="keywords" content="<%= WCMUtils.getKeywords(currentPage) %>"> <meta name="viewport" content="user-scalable=no"> <title>${properties.jcr:title}</title> <output data-sly-call="${clientLib.css @ categories='adobearchetypetest1'}" data-sly-unwrap> </head>

...