If I have code in ui.frontend that manipulates the DOM that the HTL renders, how should I be writing unit tests to test the interactivity between the ui.frontend and HTL? I could try to copy and paste a small section of HTL template html as a unit test fixture but I can't copy page properties. Seems...

Normally, in web development, it is best practice to use classes on html elements and id's are rarely used. At my organization, seems like id's are being put on authored components a lot and that is used for adding style changes. Is this bad practice or is this regular practice in aem?  

I would like to be able to expose a variety of variables whose values are retrieved after some api calls. Then, these variables should be easily accessible to content author, so I am thinking of something like those Scratch building blocks so that the author can drag into some kind of rich text fiel...

I have a custom component whose htl template uses wcmmode.edit to conditionally render content. When outside of an experience fragment, the wcmmode.edit works. But when I put it inside an experience fragment and link to the XF from a page, wcmmode.edit always resolves to false. Am I using experience...