[UPDATE] Genesis Framework Version 2.5 Released – Big Changes

StudioPress has just released its new version 2.5 of the Genesis Framework 2.5 for download. I was using the beta version on a test blog and lot’s of good changes happened. Thousands of people are on the framework so beta testing is crucial when releasing a flawless product to the public and now it is here.

UPDATE 4/26/2017: Today marks the final release to the public, I have updated the changes listed below to what was actually changed.

I am testing this on a test blog myself.

There are some big changes coming and they are setting things up to be a more organized framework and object-oriented direction, making use of the WordPress API’s.

Warning:
If your Framework theme is not html5 enabled, have it converted before the final framework released

My favorite changes are that this version will better support the WordPress Title Tag feature, accessibility improvements and new filters plus more helper functions. Thus making it easier to figure things out when editing your theme.

As mentioned, the next version is going to have big changes and already in this beta version, you can see below all of them. Keep in mind this is the first beta version and there will be bugs found to take care of. Expect more changes before a final release which right now has no set date.

Genesis Framework Additions

• Added instances of markup API use in several locations where it was previously not used
• Added any missed XHTML markup to the XHTML markup filter
• Added Genesis_Contributors and Genesis_Contributor classes
• Added views directory and extracted output to organized view files
• Added full support for the new WordPress title tag
• Added slashing for user script input fields
• Added primary category support when Yoast SEO is on, but breadcrumb feature is off
• Added support for multiple layout types depending on context
• Added script loader class
• Added ability to specify location of entry scripts via a second option
• Added filter for capability required to use CPT archive settings
• Added filter to disable layout settings on CPT archive settings page
• Added sanitizer for layout settings on CPT archive settings page
• Added a posts page check to genesis_do_blog_template_heading()
• Added filter for entry content display options in the customizer
• Added terms back to terms array in our terms filter
• Added genesis_strip_p_tags() function
• Added center alignment option to featured image alignment setting
• Added more filters to breadcrumb class

Genesis Framework Changes

• split featured post and page widget entry header markup gave markup API context for each
• Restored adding tab index via JavaScript when a11y is on
• Prevention of smushed offscreen accessible text
• Reorganized init.php
• Stripped tags from filtered credits text to avoid paragraph nesting
• Standardized the context naming in widget markup
• Flagged entry markup as is_widget via the params array so it can be modified without affecting other entries
• Restored new line between admin screen buttons
• Improvements to composer, PHPCS, and unit tests
• Switch all schema.org URLs to https
• Formally deprecate genesis_get_additional_image_sizes()
• Improved CSS
• Improved code optimization and documentation
• Ensure skip links filter returns an array
• Improved randomness of search form ID
• Fixed potential issue with footer scripts filter
• Moved aria-label to the element so screen readers will announce it
• Added capability check to CPT archive settings link in the toolbar
• Refactored and improved archive headings
• Fixed typo in comments feed setting

What has been removed

• Removed semantic headings SEO option, with fallback for backward compatibility
• Disabled back to top output if HTML5 is on
• Removed output buffering on search form
• Removed unnecessary title on skip links

I am excited about all these changes already and this is the first beta release. Can’t wait to see what bugs are squashed and perhaps new features added. The beta version of the Genesis Framework is for developers and plugin developers to test their themes and plugins out to find the bugs and report them or make suggestions to the framework. Overall, themes may have to be tweaked when the final version is out.

I’ll update this blog post when something has changed in regards to the beta version or when I get wind of a potential final release date.

What changes mentioned already are you excited about?