As I debugged points with the brand new block hole characteristic added in Gutenberg 11.4 final week, I discovered the ticket introducing it. And, there was already a new ticket for one downside I had hit. Nevertheless, there was some dialogue over whether or not themes needs to be allowed to opt-out, rolling their very own resolution. There was no approach to do it on the time.
It felt like a no brainer, one thing I’d not assume twice about. I rapidly chimed in:
Ought to theme authors be capable to choose out? If that is ever a query that comes up, the reply is at all times: Completely, 100%, sure!
The entrance finish of a web site is the theme writer’s area. In the end, they outline how issues work there. No less than, that is the way it has at all times been. Earlier than the appearance of the block system, there have been instances the place WordPress added its personal spin to front-end options, corresponding to types for the gallery shortcode and emoji JavaScript-image substitute. Themes have at all times had strategies for disabling these.
With the introduction of the Gutenberg venture and its evolving characteristic set, WordPress continues entering into front-end design. This carries the advantage of standardizing the connection between the platform, themes, and customers. It makes issues like block patterns common, and it’ll proceed doing in order we get into extra superior structure instruments. This can be a future that I’m desirous to witness as a result of it would make theming a lot simpler.
Nevertheless, inside the in-ticket dialogue, I got here throughout one of many elementary rifts between some individuals engaged on Gutenberg and third-party builders:
I disagree with this take. Which means that every part needs to be elective in WordPress and goes in opposition to the choices not choices. some issues have to be choices however not every part…I don’t assume it needs to be a rule to have an opt-out for every part personally. As an illustration for structural types, I’d relatively have the themes depend on Core at all times as a substitute of reinventing their very own. Themes are right here to convey character and design however to not outline what “horizontal alignment” means for example.
If such a stance turns into one of many cornerstones of block theme development, it would flip many conventional themers away.
I agree with the precept that this needs to be the inspiration, the default method that theming works in WordPress going ahead. The extra items that we will standardize, the higher. However, as a rule of thumb, theme authors ought to be capable to choose out of any design-related characteristic. Then, we make uncommon exceptions to that rule when the necessity arises.
No matter what Gutenberg and, finally, WordPress does, theme authors will discover a method round it. Allow us to fake that “horizontal alignment” is outlined by CSS flexbox in core. I assure that somebody will come alongside and use CSS grid.
Within the case of the “block hole” characteristic launched in Gutenberg 11.4, it’s basically a elaborate title for a worldwide high margin that will get utilized to blocks (to not be confused with the precise CSS hole property). In essence, it’s a system for outlining a part of the default vertical rhythm.
This characteristic has lengthy been on my want listing, however the concept of mandating it by no means crossed my thoughts. If you wish to see a heated dialogue, throw a handful of net designers in a room and have them focus on the myriad methods of dealing with vertical spacing between components. I’m within the high margin camp.
Luckily, theme authors will be capable to allow or disable the block hole characteristic. However, that’s merely one battle.
I had deliberate to answer in-ticket, however I didn’t need to get too far off-topic. I additionally wished to offer some consideration to the opposite aspect. Nevertheless, I may consider few situations the place WordPress ought to at all times be the deciding issue on front-end design.
From that place, I envision little greater than theme authors creating workarounds for what they’ll see as a damaged system. There may be nothing flawed with WordPress defining the defaults. Nevertheless, it ought to at all times be from the mindset that builders will need to enterprise out. One of the best ways to maintain them pleased is to not get in the way in which. Construct a system that they need to make use of, not that they should use. And, for individuals who resolve to go a distinct route, make it straightforward. Even when we expect these insurgent designers are making a damaged consumer expertise, that’s OK. It’s their venture to make or break.
What makes WordPress so uniquely WordPress is that the platform has at all times catered to those that need to lengthen it in nearly any possible method. If it begins creating obstacles that needn’t be there, we now have executed a poor job as stewards of the software program.