I'm thinking the next video will be a deep dive into how the CSS works, but basically it's making a folder called wp-content/block-styles. That's filterable though so you could have your save in your theme folder if you wanted.
@@BrianCoords makes sense but makes me think, perhaps is better to move it to wp-content/uploads/block-styles. Usually, on migrations, backups, etc, is better to keep default folder structure and ad as many subfolders as you want. Just a suggestion, of course. You are doing a great job here and it's super easy to come and trow an advice. The hard part is what you are doing.
Great work. Though if you're a developer use to a CLI interface, the code UI will feel cramped. Panel options being.. draggable width size, extended width with toggle, or optional modal popup (mini IDE playground).
Yeah that's an overall complaint about the block editor - those sidebars are not very flexible, you can't make them bigger or smaller. Maybe I'll come back to adding a modal so you can have an optional 'expanded view' when trying to write the code.
That's a great point that I should follow-up on in the next video- why separate files? The CSS will ultimately get parsed through the Style Engine API and much of it will actually end up as inline Style tags, rather than as separate files. developer.wordpress.org/block-editor/reference-guides/packages/packages-style-engine/
Amazing progress! Good idea on moving the Manage style panel to the right.
Thanks- we'll see if works out
It's looking really good, i can't wait until we can use it! great work
Thank you- looking forward to getting real-world feedback.
Looks fantastic so far.
Thanks!
Hey Brian. This is getting better. I like it. Where are the CSS files being saved? in the theme, plugin or in wp-content/uploads/... ?
I'm thinking the next video will be a deep dive into how the CSS works, but basically it's making a folder called wp-content/block-styles. That's filterable though so you could have your save in your theme folder if you wanted.
@@BrianCoords makes sense but makes me think, perhaps is better to move it to wp-content/uploads/block-styles. Usually, on migrations, backups, etc, is better to keep default folder structure and ad as many subfolders as you want. Just a suggestion, of course. You are doing a great job here and it's super easy to come and trow an advice. The hard part is what you are doing.
Great work. Though if you're a developer use to a CLI interface, the code UI will feel cramped. Panel options being.. draggable width size, extended width with toggle, or optional modal popup (mini IDE playground).
Yeah that's an overall complaint about the block editor - those sidebars are not very flexible, you can't make them bigger or smaller. Maybe I'll come back to adding a modal so you can have an optional 'expanded view' when trying to write the code.
@@BrianCoords just in case you don't already know, Bricks auto-expands CSS box quite nice.
I haven't played with Bricks but I really should.
@@BrianCoords panel resize may arrive in 6.6. according to GitHub.
So many request will be slowdown your website I highly suggest create only one main css file
That's a great point that I should follow-up on in the next video- why separate files? The CSS will ultimately get parsed through the Style Engine API and much of it will actually end up as inline Style tags, rather than as separate files. developer.wordpress.org/block-editor/reference-guides/packages/packages-style-engine/