Greg Hurrell

cc @jbalsas — if there's anything you'd like to see included in the content update please add it above.

Many `findDOMNode()` calls (almost 70?) removed in: https://github.com/liferay/alloy-editor/pull/1148

I feel the same way about producing two builds in order to pass validation (what does it mean to have a "valid" output if the thing that's valid isn't the...

And just cross-linking the last existential discussion we had on a related topic, ["What is Clay in relation to DXP?"](https://github.com/liferay/clay/issues/3849).

A lot of the replies on this thread so far have consisted of _"but ... we'll lose [something] if we do this!"_ I tried to foreshadow this — albeit while...

And I can't understand those first two updates because I don't speak latin. 🤦‍♂️ 

There was a comment on here three days ago (now deleted) noting that this still hasn't been updated. I think we should just delete the page as realistically, it is...

Ha, no worries about that @jwanner83. I saw the notification email and came here to comment; I don't think there was anything wrong with your comment — you were just...

@jbalsas: > the initial rationale Good to have a rationale but I think the best rules are the simple. Having three different cases makes it easy for human error to...

@onyii5119: I'm not sure but I'd suggest adding AlloyEditor to the page as described [here](https://alloyeditor.com/docs/use/how_to_use_it.html) via a `script` tag, and then accessing it via the global `window` object without doing...