Forum Replies Created
1) My experience, like that of @jmrallen, was that the upgrade itself didn't require any changes. I only needed to worry about those when I enabled HTML5.
2) When I enabled HTML5, I used the cobaltapps.com converter @SDesign refers to, and it worked perfectly. There were still some minor things to clean up afterward that a converter can't catch. (For example, a class I had attached styling to in the footer was no longer there. Per a comment I found in the Genesis 2.0 code, this was an intentional change.)
I'm sure there will soon be lots of great information like the guides that FAT Media (above) will be preparing. In the meantime, here's what worked for me on a site I just upgraded in case it's helpful.
The site uses Outreach with some additions & modifications to widget areas (and, of course, lots of modifications to style.css).
I updated Genesis and, like advertised, the site looked fine afterward.
I then added "add_theme_support( 'html5' );" to my functions.php, after which, as expected, the site looked like a bomb had hit it.
Then I ran style.css through the wonderful converter at http://cobaltapps.com/genesis-xhtml-to-html5-css-converter/, after which things looked much better. There was one problem remaining: some of my widget area divs had now become children of other widget area divs--with decidedly unpleasant results.
At that point I looked through the Genesis 2.0 code. In widgetize.php I found defaults that indicated that when laying out widget areas using genesis_widget_area, one now needs to specify "aside"s instead of "divs". So in home.php I changed my "div"s to "aside"s--and my site was back to looking exactly as it had before the upgrade!
Whether it be the idea for a "Y/N" box suggested above or some other approach, I think something is needed to help alleviate the confusion that's going to occur when people assume a "2.0x" child theme has been updated to fully support Genesis 2.0. Thanks.