What functional use case you are trying to implement when you say that there should be parent child relationship between assets ?  

You can add a condition block to check for dialog source property in the event handler and write your logic inside the condition block. Example code - var config = Granite.author.DialogFrame.currentDialog.getConfig(); if (config.src == "<Your dialog path>") { }

The default request rewriter in CQ does not rewrite URLs if they do not have HTML extensions. And therefore the DAM urls are not rewritten. You will have to implement a custom request rewriter to achieve rewriting of DAM urls. The same is mentioned in the article I had shared earlier. You can refer ...

Did you create a custom request rewriter as mentioned in the article  ? 

You can do this by following the steps listed in the following page - http://www.cqblueprints.com/tipsandtricks/serving-static-assets-alt-url.html

Have you checked this thread - http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__rkpw-hi_im_tryingto.html ?

Have you tested this in all browser types? It seems it is a bug for chrome on Mac OS as the registered formatter command isn't invoked when you press ctrl + b. However, it works on Mozilla and IE. Also, I have found the file and the line number where the command should be invoked from the shortcut k...

I think you can achieve this by configuring HTMLRules for your rich text editor. You just have to configure the semantic markup tag for the bold element.  See the documentation link [1] and an example [2][1] http://docs.adobe.com/docs/en/cq/5-6-1/widgets-api/index.html?class=CQ.form.rte.HtmlRules.Do...

What version of AEM you are working on ? From 5.6.1, the variable for workItem is called as "graniteWorkItem". Check the following section "Implementing a Process Step with an ECMA Script" in the documentation link [1].  [1] https://docs.adobe.com/docs/en/cq/5-6-1/workflows/wf-extending.html

You can check the below documentation. Whenever you activate a page the AEM will create a version and store the version in the version history. You can restore that page by click on "Restore Tree" button in the siteadmin in the same location where that page was created originally. https://docs.adobe...