No, I am doing this with the snippet above.  I am trying to setup "placeholder" or default text on the text component I have setup already on the page.

Thanks, Scott.  This is not directly related to what I want to do, but I had not seen the boiler plate option before.  I can push default components on page as you suggest or directly embedded in the template jsp.  The issue is adding default content for a given cq:include.  It would be best to have...

<div class="text" > <cq:include path="bodytext" resourceType="foundation/components/text"/> </div> I am embedding foundation components in a page component (see the following) and need to set some default content.   How do I go about this?

We need to set a title on a root folder in the DAM without changing the system name.  I was told that this is not possible on nt:folder nodes.   What can we do?

Thanks.  This actually overlays the help link in the WCM banner area.  We've fixed this withCQ.wcm.HelpBrowser.path = "(our url)"Where is the sidekick configuration?

Hi, our sidekick help button (top right) has a broken link to [author-host]/en/cq/current/wcm.html.  We need this to go to a public help page that we have.  Where do we overlay this config?

If the email pages are "browseable" then yes a link is easy.  We have MCM so this needs to work there.  I will submit doc tickets when I know that a feature exists.  The issue usually is that these things go undocumented for so long that no one knows what is possible in many cases.

Yes.  Not a word about my question.

A basic requirement is for a newsletter to have a "view in browser" option that is persistent.  How does this get setup in AEM?  We definitely need to create and publish once without having to create two versions.

I need to revisit this.  We are using classic UI for page editing and Touch UI for site admin.  The page properties config that we have for templates needs to be visible and usable from both TouchUI and classic UI.  How do we accomodate this?  This must be common.