The code you’re trying to fix only changes the edit component and attributes, the edit component is just the UI in the editor. To make changes to the frontend you’d have to modify the save component, or filter the block via the block rendering filters. But that’s all pointless because you’re trying to reinvent global … Read more
You haven’t set the font in the block editor, instead you’ve added an additional font family option! Instead use global styles instead to style the text: { “styles”: { “typography”: { “fontFamily”: “‘Mulish’, sans-serif” }, } } Now the default will be Mulish, additionally setting fontFamilies to [] in the typography section will remove the … Read more
Server rendered blocks like that can’t have child blocks. The closest you can do is call do_blocks and pass it block markup, but this means pre-creating the block in the editor, and copy pasting it out. It would not be modifiable in the editor, or appear as a block. It would just be additional HTML … Read more
For anyone looking for something similar I came across this in a PR – https://github.com/WordPress/gutenberg/pull/31326#pullrequestreview-781388981 This filter setup has worked for any block that I’ve tried that has allowedBlocks set as an array in the block.json file.
extending a core block doesn’t work inside the editor
How to add more elements to an already existing section in Gutenberg
Since I am working with block attributes, I had to also define my attribute within my block.json file… block.json “attributes”: { “listOrdered”: { “type”: “boolean”, “default”: false } Now with that set in place, I can now run npm start, and see my block variant working well in wp-admin edit page. It allows me a … Read more
It was a long and winding road that led me to a working solution, which doesn’t resemble my above attempts very closely at all. In short: instead of importing the Save component by itself, you run the registration functions from the root JS file of the blocks, and then use createBlock and serialize. The full … Read more
Block content rendered with inline CSS. How do I reuse it in a headless setup?
With me being new to this process, I’m sure there is still room for improvement, but I was able to experiment with some online resources to get the following working for me. An introduction guide on innerblocks and renderAppender details. A WordPress Core article on using innerblockprops From within my plugin directory, in my edit.js … Read more