The demo sites have long been an example of how the themes are designed to look, without actually being a food blog themselves. Their layout, design and organization has been a stylistic reflection (with technical and sales content) rather than a practical implementation.
This has led to confusion over why the theme setup tutorials end up with different recommendations from the demo site.
So we've split the demo sites into the "Classic" version of the theme, and the more actual food-blog-style demo style:
Our goal over the next few months is to fill up the Theme + Plugin demo sites with actual recipe content so that it's an accurate, live reflection of our recommendations.
The classic theme sites will reflect the updated version of the themes without the plugin, and the content will remain "sales" and demo-oriented, as they always have.
Will the themes continue to receive updates?
Yes! The themes will continue receiving styling-related updates, to resolve display-related errors in Google Search Console. We consider the overall styling of the themes to be "finalized" and should only require minor tweaks over time.
New functionality that needs to evolve and adapt to changing requirements in PHP, WordPress, Genesis and Google will continue to be built into the Feast Plugin. These new features can be modified and refined through plugin updates without needing to re-install the entire theme.
Both the classic theme sites and the theme + plugin sites will run the most recent version of the themes.