-
Notifications
You must be signed in to change notification settings - Fork 54
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
Automatically enqueue style.css when creating a blank theme #334
Comments
How can we explain to users that the Stylesheet is used because it is required to provide WordPress with information about the theme, like the theme name and version, not to add CSS? |
Ohh I see. Thanks for clarifying -- limits of my lack of knowledge with themes. I think a comment is a great idea and approach. |
In a way I agree that "if it is there it should work", but in this case it can't be removed even if it is otherwise empty. I also think that if the person knows that the theme needs a functions.php and knows the css file needs to be enqueud, its not too difficult for them to add it. So is it more beneficial to:
|
This came up again with a user in the forum:
I agree very much with @carolinan that it would be much less confusing for users to go with either of these two options. |
I would prefer to use a style.css file than the Additional CSS area in the FSE block editor. The Additional CSS UI and accessibility is dreadful. I find it much simpler to use a style.css file, but to have to enqueue it yourself? Led me down a rabbit hole that I'm finally climbing out of. |
Just ran into this issue and it definitely needs some love. |
I agree. Style.css file for me as well. Definitely should be enqueued already, even if it's not used. It will be there for those who want to. |
Pulling in feedback from the FSE Outreach program's Build A Block Theme exploration:
The text was updated successfully, but these errors were encountered: