I've been spending a lot of time with Omega and my own subtheme, and I've got to say, this theme is a work of beauty. Thanks so much to the dev team for their work. I'm planning to move all my themes to this framework.
I just wanted to share a few observations and suggestions, and a bug or two. (which I'll post as issues)
1) Omega plus Delta has allowed me to do some pretty cool stuff so far. I was surprised to discover that the Delta module is "features aware" which is critical. With so much layout logic embedded in the database, it's essential that themers have a way to package up all that logic in a theme that is disconnected from a specific website or database. Features provides a way to store Delta "templates" and Context layouts in a distributable package.
For purposes of discussion, I wonder if it would make more sense to store Delta templates in the dot.info file, since the Drupal community is not accustomed to installing feature sets in order to use themes. Feedback?
2) I've run into some glitches with Delta and Context. (potential issue here) Sometimes the Delta options do not show up in the Context "reactions" dropdown. Sometimes Delta takes the place of the blocks element in the dropdown, and sometimes everything works fine. There might be a cache issue somewhere that needs investigating.
3) Being able to add CSS classes to a zone and region on the setup page is fantastic! That way, I can embed special CSS styling that only applies in certain Delta templates and not others. Unfortunately, there seems to be several instances where those custom styles fail to show up. In other words, I add a custom style to a region on the setup page, but that style never gets added to the html at rendering time. This issue (yes, another one) seems to happen most often with the region embeds. Just a heads up.
4) I have found myself wanting to add extra divs to certain zones and regions in order to accommodate certain graphical elements. Is there any plan to add this functionality? Sort of like the custom styles? I know there is the option to add an extra wrapper to zones, but sometimes you need more than one. I realize I could accomplish this in a custom php template, but I love staying with the "php template free paradigm" that Omega has provided.
5) I've had a few issues with Omega and the Fontyourface module, because FYF needs to be the last CSS file in the import order. However, the Omega subtheme base has several CSS files with quite large weights which tend to load after FYF. I've mentioned this to the FYF dev, but can these weights be adjusted safely in Omega?
Just some feedback on an exciting new direction for Drupal theming. As a weak php coder, it's great to see a theming solution that can be accomplished without coding. I'm building a theme that is just about the worst case scenario for Drupal, and Omega is handling it with grace. In conjunction with the CSS3PIE module, I will soon have a theme that is HTML5, responsive, contains png transparencies, is built with CSS3 elements, and is still compatible with most legacy browsers. I'll be future proofed.
Many thanks!