[capiedge]

Many thanks Victor!

I found an even easier way to accomplish it:

//Remove selectively the site-inner wrap
add_filter('genesis_structural_wrap-site-inner', '__return_null');

Regards.

[capiedge]

Hi Sridhar! A pleasure to talk with you!

A preference? Perhaps Bulma and TailwindCSS are the trendiest options right now, don't you think?

But in any case, how to prevent the interaction with native Genesis (or WP) classes? I think that the best option is to selectively use only some utilities and not the entire framework (that for sure will cause problems with standard classes declared in Genesis), and maybe taking this in consideration, some frameworks are better than others...

And, one more doubt, what do you do when you need this kind of utilities? Have you any recommendation?

[capiedge]

By the way, here is the solution:

add_action ('genesis_meta','reordenar_meta_en_archivos');
function reordenar_meta_en_archivos() {
	if ( is_front_page() || is_archive() ) { # comprueba si es front page o es archivo
		remove_action( 'genesis_entry_content', 'genesis_do_post_image', 8 );
		add_action( 'genesis_entry_header', 'genesis_do_post_image', 8 );
		remove_action( 'genesis_entry_header', 'genesis_post_info', 12 );
		add_action( 'genesis_entry_header', 'genesis_post_info', 9 );
		remove_action( 'genesis_entry_footer', 'genesis_post_meta' );
		add_action( 'genesis_entry_header', 'genesis_post_meta', 9 );
	}
}

[Author]

Posts