Forking Genesis

OK, let’s go back to the Genesis fork discussion :slight_smile:

quote=“zulfgani, post:72, topic:2106”]
My first change was to remove the Customizer redirection - Done!
Question: Should the Customizer options be removed altogether or should they be left in place?

After the rebranding I’ll be looking at the following in more detail to see what should/has to stay and what can go without breaking the theme.

1: The SEO module is a priority must go for me - but I’ll take your views into consideration.

2: Nags like the “install and activate Genesis Connect for WooCommerce” will have to go - support for Classic Commerce will be built into either the parent theme or one of the child themes.

3: Google AdSense plus Header/Footer script options will go - these can added back by an addon plugin or a child theme that requires them.

4: The meta tag clean up maybe completely removed or toned down - for me these are plugin territory.

After that we’ll have a core framework ready for beta testing and hopefully move it on to a full production ready release.
[/quote]

If Genesis options are on the Genesis settings page, there is no need to leave it in Customizer.

I vote for leaving Header/Footer script options. AdSense should go.

What you mean by “meta tag clean up”?

Genesis 2.10.1 acts the same, as 2.10, but, maybe, fixes a bug?