Keelan Fadden-Hopper

Should we include `localgov_sa11y` in the default install profile?

Related issues: https://github.com/localgovdrupal/localgov_eu_cookie_compliance/issues/2 https://github.com/localgovdrupal/localgov_guides/issues/85 Some instances of bootstrap classes: https://github.com/search?q=org%3Alocalgovdrupal+%22+col-%22+-repo%3Alocalgovdrupal%2Flocalgov_theme_croydon+-repo%3Alocalgovdrupal%2Flocalgov_theme+-repo%3Alocalgovdrupal%2Flocalgov_base_croydon&type=code @markconroy

It would be fairly easy to remove these from the wysiwyg profile for new installs, and that wouldn't have any impact on existing installs. I think that would be the...

I have an open PR for some changes to the wysiwyg config which I will update to include this.

Interesting, thanks Andy. We could potentially make all unpublished content visible, but then again I'm not sure whether we'd want to do that. I suppose we could also do something...

To note, this is specifically about increasing the text size, not zoom.

@andybroomfield If you don't select any of the content types, it defaults to being enabled for all content types. So I don't think that would require ongoing changes.

@andybroomfield that's interesting that it doesn't work for /node/add, I was not aware of that.

~Also seeing an intermittent issue here - in the above situation, the 'correct' error appears very briefly, but then disappears, the 'from' path is cleared and a new, unhelpful error...

Agreed, this would be a good thing to bring to content then backlog! I've moved up to the top of the product backlog list, I considered bringing it up last...