You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Loops that are build with the Query Block currently output the post_class on each li element in the frontend, which is great! This allows me as a theme developer to style the query block differently depending on which post type is being queried, or inherit styles I'm using for traditional archives.
However, the post_class is not output within the editor, meaning the content manager/admin will not see any of my custom styles when they are editing their content.
What is your proposed solution?
Dynamically output the post_class when the content manager/admin selects a post type to display in the Query Block, so that the editor styling can match the frontend styling
The text was updated successfully, but these errors were encountered:
What problem does this address?
Loops that are build with the Query Block currently output the
post_class
on eachli
element in the frontend, which is great! This allows me as a theme developer to style the query block differently depending on which post type is being queried, or inherit styles I'm using for traditional archives.However, the
post_class
is not output within the editor, meaning the content manager/admin will not see any of my custom styles when they are editing their content.What is your proposed solution?
Dynamically output the
post_class
when the content manager/admin selects a post type to display in the Query Block, so that the editor styling can match the frontend stylingThe text was updated successfully, but these errors were encountered: