We use the Genesis Framework to develop all of our websites for the reasons I outlined in this post: Why I use the Genesis Framework.
Genesis 2.2 has just been released and here is a summary of what has been changed:
Genesis 2.2 adds new accessibility options for child themes, compatibility with WordPress’s Title Tag and Site Icon features, more Schema.org microdata improvements, and many small fixes to make the Genesis experience even better.
Allow child themes to enable accessibility features for web users with disabilities.
Thanks largely to the work of Rian Rietveld, Genesis now has accessibility features built in which can be enabled. These features have been available in Rian’s Genesis Accessible Plugin (which we use on all our websites), but these features are now built into Genesis.
Things like better colour contrast, keyboard navigation, and better screen reader support make make Genesis 2.2 more usable for your visitors with disabilities. For more information go the Genesis accessibility website.
Improvements to the Schema.org microdata Genesis outputs.
Microdata is a way of labelling your website structure and content so that Search Engines such as Google understand it.
Genesis is one of the few WordPress themes that fully utilises Schema.org microdata and HTML5 in the markup. But there are always improvements to be made, and these improvements have been implemented based on the changing recommendations.
And the great thing is, you don’t have to do a thing. Just upgrade, and the improvements go live.
Compatibility with WordPress’s new Site Icon feature.
WordPress added the Site Icon feature in 4.3 which allows administrators to easily upload an image to be used as the favicon and app icons for a site. Genesis already had this option built in so this has been disabled in Genesis 2.2 to prevent having 2 icons in your code.
Entry meta is the”administrative” information you provide to viewers about a post. e.g. This entry was posted on 3rd September by Angie Vale. This is great for blog posts but when you create a custom post type such as “Portfolio” this information isn’t really relevant.
In the past, if you registered a Custom Post Type, the display of that CPT entry meta on the front end was inconsistent and difficult to remove. This has been fixed in Genesis 2.2 so now, if you want to remove entry meta from a CPT, you simply remove post type support for the entry meta that would normally be displayed before and after entry content by using this code in your functions.php:
As always make sure you have a back up of your site before you upgrade. Genesis 2.2 needs WordPress 4.3 to run so make sure you upgrade WordPress at the same time. Any theme customisations made in the Child Theme (the correct place for them) will not be overwritten so you can upgrade without worrying.