@matjaz thank you for doing that. I appreciate it. I look forward to seeing it added to the standalone version of Pinegrow, as that is where I’d like to use it. My Local Pinegrow locks up when I try to upload my webflow zip. So I tested with a smaller version of my file.
I’d like my Gutenberg FSE styling to match my front-end styling. That is ultimately what I’d like to make happen using Pinegrow. I want my designers to think that they are designing on the front end an dto be able better “visualize” their designs.
Does Pinegrow add code to the functions file that helps to define backend styling?
@smgitner theme.json export will come out in the next release. I posted the dev version of the plugin here to get some validation for the new (highly requested) feature, but so far nobody said anything cc @adamslowe@Emmanuel
is there any way to make it work so that it is compatible with 6.2 so that once the theme.json is defined in pinegrow, the typefaces can then be changed in 6.2’s editor feature? so say for example a user does not have access to pinegrow but wants to make changes to a theme.
Some people might not want this automatically generated, so having an option to disable it would be nice. Although, I suppose you could just choose not to export it with the theme.
It might be nice, although completely unnecessary, to add a GUI to enable/disable some of the more common theme.json settings from the design panel rather than having to create a custom_theme.json file for them. My boilerplate theme.json file is below. I suspect this covers most of the commonly changed settings.
The theme.json seems to work well with FSE themes in my limited testing. And, as I said in a previous post, settings from the site editor override anything that was manually set in theme.json.(as expected)
One suggestion that I do think would be an enormous value-add would be an interface to change the default typography styles; particularly the sizes, weights, and line heights. Bonus points for making them CLAMPS In a regular HTML/CSS project you can set these properties in the design panel, but they don’t seem to come through to the theme.json.
@chipriggs Thanks for your support and for picking up the course. I hope you find it helpful!
@smgitner I’m still feeling that out, as I suspect most people are right now. For block themes, I’m trying to do as much as possible with native WordPress Blocks, supplementing them with Pinegrow or other 3rd party blocks when needed. I’m still using Pinegrow to manage the theme since it takes care of a lot of the logic writing for me. I’m eager to see what Pinegrow has in store for us regarding theme.json and other Block Theme-enabling tools.