-
Notifications
You must be signed in to change notification settings - Fork 117
Remove obsolete block CSS #168
Comments
I also believe most of it can be removed but it was unclear why it was in Seedlet. We have not started testing or working with individual blocks yet. "Some of it could be submitted to core" I did not understand. Did you mean that we need to create issues for changing blocks in Gutenberg? |
There are some cases where this CSS does actually fix an issue in Gutenberg blocks. In those cases we should keep the CSS temporarily, but also submit it to Gutenberg as a PR so that the fix can live in the block itself. e.g.: |
Yes, it was the core part that I wanted clarification on. |
The action needed here is to go through the block styles here Check if there are any unnecessary duplicate styles -styles that are already in WordPress core where the theme styles are overriding it even though it is not needed. Optionally check if there any styles here that fixes a problem where an issue should be opened in Gutenberg. @scruffian Did you have any specific block code in mind that needs to be removed? |
As far as I can see the scss included is all theme specific. If @carolinan agrees I would like to close this issue. |
An example is the Pullquote block. We have been able to remove a lot of this CSS in other themes, as the base styles from Gutenberg are already doing most of the work. |
Since the theme needs to be compatible with WP5.3 I don't think there's lots of things we can clean-up here. |
I hadn't thought of that. Good point. I think we can close this. |
There is a blocks directory inside scss. A lot of this code is from when Gutenberg block appearance in core was much less stable. However much of this code is now obsolete, and should be removed. Some of it could also be submitted to core if it's not there.
For example: Automattic/themes#2503
The text was updated successfully, but these errors were encountered: