Bryce Osterhaus

You're right, looks like we aren't generating the snippets correctly. We need to replace the hard coded quotes with `quoteType` Would you mind sending a PR for this fix?

@n1ru4l I'm not totally sure what would need to be done on their side vs dunegon-revealer side. I can look into it though and follow up here. Thanks for the...

> creating and maintaining two different mental models leads to higher costs This thought intrigues me, should we expect that both Clay and Lexicon have the same mental models? I...

I remember this being brought up before, the idea of lexicon, clay-css, and the react components all living together and being sync'd in terms of docs and features, and I...

> we could even somehow do nightly PRs just to check that whatever's been merged (even if not released) is working fine or detect issues early before we release and...

If we think it's helpful, I have no issues adding some sort of script to validate our custom css. Personally I don't have a huge preference. I did see [this...

**TLDR; I'm not fully opposed, but I also think we might be trying to fix our problems with the wrong solution. I would vote to keep them separate and focus...

Another reason why we might want to consider merging to DXP is so that we can update markup in both components and tags at the same time. Or maybe there...

> One additional benefit I see is that it would be easier to get contributions on issues like ClayPanel: The page is refreshed after click on the Header, inside a...

Just gonna chime in on the CI portion. I think CI is my biggest concern and perhaps the most difficult of these challenges to overcome since it effects time, people,...