Michael Kelly

Thanks, @creativecoder for getting your PR out quickly! I also did some testing and I found the following: - Existing Atomic site: fixed - WoA site created yesterday: still has...

Hi @Robertght, the spacing change was intentional - see @creativecoder's comment [here](29-gh-Automattic/custom-colors#pullrequestreview-1051775728). The issue with the background change was not though. My view would be to create a separate issue...

> Sure @mpkelly ! Created one here: https://github.com/Automattic/wp-calypso/issues/66518 > > Thank you! Thanks!

I just now tested this on Simple and Atomic, the latter with and without CoBlocks blocks on the page. I am not seeing any issues. @edwinho89 do you think we...

I like this idea of making template editing distinct by using different colours. The menu could also be updated so you can see the pages that inherit from the template,...

Using the result of atob did not work for me. I was able to convert from base64 using the following function though ```JavaScript function _base64ToArrayBuffer(base64) { var binary_string = window.atob(base64);...

Hi @CameronAckermanSEL, I use `componentDidCatch` in production as it is necessary whether using Slate or not. However, it feels like Slate is the source of _too many errors_ and that's...

@karlludwigweise my fork wasn't intended to fix #3575 per se but only stop Slate from raising errors for things my app does not care about, like clicking on some structural...

I couldn't reproduce this specific issue but after trying a bunch of temples via Appearance > Editor > Templates and then going to Editor > Pages I got a blank...

I changed the status to "Needs core / 3rd party fix" as we're blocked here.