Hey johna91​ I wouldn't worry about the `>` symbol. I think thats just an artifact from the new version of core components. In chapter 3 styles are added to format it.Also just a heads up we are going to publish a 6.5 version (w/ 2.3.2 version of Core Components) shortly so be on the look out for th...

Hi you should have the "First Article" as a child of the Home page, in your screenshot you have it as a sibling. It should created beneath the Home page:

Hey no problem!So in your source code look at: ui.content/src/main/content/jcr_root/conf/wknd-events/settings/wcm/policies/.content.xml this is the node representation of all the policies for that templateYou should see an XML node like the following:<default  jcr:lastModified="{Date}2017-12-07T15:4...

Hi! Are you using AEM 6.5? I believe the Template Editor Support is only available in AEM 6.5+. The SPA Editor works in 6.4.2, 6.4.3 but does not have Template Editor Support ( the policies would need to be manually updated at the node level...)

Hi @aem_marc,There are two WKND tutorials one for traditional AEM sites and then another set for developing with the SPA editor. The traditional sites one includes some steps to use AEMFED: Getting Started with AEM Sites Chapter 3 - Client-Side Libraries and Responsive Grid AEMFED could also be used...

I'm assuming that you see the Text component in the AEM UI and that you can add it to the page, but when you do it disappears?It may be a JS / client lib caching issue: Adobe Experience Manager Help | Set up a Local AEM Development Environment there are some steps to invalidate the clientlibs and th...

Live demo example of multiple layout containers: Pinnacle Finance (view the source and search for the class fsi-container--highlight to find the outer layout container and cmp-layout-container--fixed for the nested fixed width layout)

Hi matthewr46705702 Another approach is to actually have two layout containers. The outer layout container is the full-width w/ colored background and the inner layout container is a fixed-width (no background). The inner layout container will have the grids appropriately and you won't have to have ...

I agree with Arun, the easiest work-around is to ensure that the parsys nodes are pre-created when a new page is created by adding the nodes as part of the page template or cq:template if they are included as a component.

Hi @chgovind ,To make sure I am understanding the use case:During development, you are using a webpack dev server and any calls to your external service you are using the Proxy features of the webpack dev server and thus passing in a relative URL. However, when you create your production build and d...