Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Style Book #656

Closed
masteradhoc opened this issue Dec 19, 2024 · 3 comments
Closed

Style Book #656

masteradhoc opened this issue Dec 19, 2024 · 3 comments
Labels
feature Features, refactoring, enhancements, improvements triage Awaiting review

Comments

@masteradhoc
Copy link

Description

Hey Tom and Team

The Style Book is an amazing overview for us to see how our general setup of fonts, colors and sizes look like in the various blocks in gutenberg. Sadly this isnt available for GeneratePress. As in the new gutenberg version 19.9 it was made available even for classic themes this could now be integrated into GP.

Thanks for checking

Greets

References

https://wptavern.com/gutenberg-19-9-introduces-style-book-to-classic-themes#respond

@masteradhoc masteradhoc added the feature Features, refactoring, enhancements, improvements label Dec 19, 2024
@github-actions github-actions bot added the triage Awaiting review label Dec 19, 2024
@diggeddy
Copy link
Collaborator

The styles book in classic themes is not baked into WordPress core ( yet )
You need to install the Gutenberg plugin to add the Appearance > Menu > Design options.
NOTE - I would not recommend using Gutenberg plugin on production sites, as its in constant state of beta and may cause issues.

@masteradhoc
Copy link
Author

@diggeddy that will be integrated in WP 6.8 in April - so definately a topic GP should take a look at.
Will you use this option or not? or will there be something similar coming up so this issue gets closed?

@diggeddy
Copy link
Collaborator

add_theme_support( 'editor-styles' ); seems to be the only requirement for the Style Book to display, which GP does already declare. And I have yet to see if it can be disabled independently. So it looks like it will be there whether a user wants it or not.

In the meantime we do have our own plans for a similar feature that will assist with site customizing .

Feel free to re-open if core changes direction on its implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Features, refactoring, enhancements, improvements triage Awaiting review
Projects
None yet
Development

No branches or pull requests

2 participants