July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.
SOLVED
Exception in AEM 6 following creating (slightly) component
1 Accepted Solution
wrote...Is the reason for working with templateSlightly.jsp (extending foundation/components/page) to be able to use Sidekick in Classic UI? In other words does the side kick only appear if the page component is JSP?
Hi Jason,
The reason you use the super type is so it will inherit the main parts of the base page component, so you do not have to re-create these yourself. You do not have to work with a JSP in order to get the side kick to appear. This can be accomplished by making your page component, into a sightly component. For example, if you replace your templateSightly.jsp with a templateSightly.html file, you could use sightly to accomplish the same task. Here is an example:
<html> <div data-sly-include="/libs/wcm/core/components/init/init.jsp"></div> <body> <h1>Here is where your Touch UI component will go</h1> <div data-sly-resource="${ @path='par', resourceType='foundation/components/parsys'}"></div> </body> </html>By using the above code, you will get the same result. The div data-sly-include line will allow you use the side kick in the Classic UI. You can find an example of a page component that is built using sightly in the following location "/libs/wcm/foundation/components/page" in your instance of AEM. Also, you can find a tutorial on building a simple page component using sightly here: http://scottwestover.blogspot.com/2015/04/aem-tutorial-on-building-sightly-page.html
If you are interested in learning more about sightly, there are some great examples here: http://blogs.adobe.com/experiencedelivers/experience-management/sightly-intro-part-1/
wrote...Is the reason for working with templateSlightly.jsp (extending foundation/components/page) to be able to use Sidekick in Classic UI? In other words does the side kick only appear if the page component is JSP?
Hi Jason,
The reason you use the super type is so it will inherit the main parts of the base page component, so you do not have to re-create these yourself. You do not have to work with a JSP in order to get the side kick to appear. This can be accomplished by making your page component, into a sightly component. For example, if you replace your templateSightly.jsp with a templateSightly.html file, you could use sightly to accomplish the same task. Here is an example:
<html> <div data-sly-include="/libs/wcm/core/components/init/init.jsp"></div> <body> <h1>Here is where your Touch UI component will go</h1> <div data-sly-resource="${ @path='par', resourceType='foundation/components/parsys'}"></div> </body> </html>By using the above code, you will get the same result. The div data-sly-include line will allow you use the side kick in the Classic UI. You can find an example of a page component that is built using sightly in the following location "/libs/wcm/foundation/components/page" in your instance of AEM. Also, you can find a tutorial on building a simple page component using sightly here: http://scottwestover.blogspot.com/2015/04/aem-tutorial-on-building-sightly-page.html
If you are interested in learning more about sightly, there are some great examples here: http://blogs.adobe.com/experiencedelivers/experience-management/sightly-intro-part-1/
