Update project page recommendation on Omega 3.x branch

Yeah. No idea how that happened. Brought it back to the project page. We are not working on 3.x at all anymore. If any security issues will arise in the future, we are going to fix them though. All new sites should be built on 4.x by now though.

Big thanks @fubhy! With 10 websites made ​​in Omega 3, I'm also really happy to hear that the 3 version is still supported .. :) In the future I will definetly use the 4.x version but really glad there will still be security fixes for the 3 branch..

P.S. Thanks for an awsome theme framework! Keep up the good work! /Mats

My question is about the Project Page description for who should use 3.x--those who prefer to work through the User Interface, like me. There is no mention about building that functionality into the 4.x branch.

Does this mean that Omega is abandoning site builders that want to do most of the theme work through the UI and contrib modules, with only minimal work on a CSS file?

With the right stack of contrib modules you will still not need to touch the CSS too much. There are modules that provide sophisticated Panels (and Panels Everywhere) layouts that are responsive (e.g. https://drupal.org/project/panopoly_theme [Note: Despite the name, that is a module, not a theme]). Omega comes with a couple of layouts too... However, yes, there are no plans (at least from my side) to bring a layout editor to Omega. That clearly belongs to the module space. Omega is now a pure themeing framework. However, with the right tools you can drastically reduce the amount of CSS you need: Panels, Panels Everywhere, Views, Panopoly layouts, Display Suite, etc.

Keeping the issue open until the Project Page is updated to change the "who should use 3.x" section with appropriate advice not to start new sites in it ... if indeed that is the path of Omega.

Currently I use Omega 3.x to esItablish the zone/region layout; I use Views to create blocks to place into those zones/regions; I use a few modules for certain menu or jQuery-type features; then I do basic CSS in the subtheme to set basic coloring, font sizes, image management, and to correct various CSS choices that Omega or other modules make.

Your suggestion to add a layer of modules that include Panels is not the direction I hoped to go; are you saying that Panels or Display Suite functionality is replacing the zone/region layout functionality in Omega 3.x? Or is that functionality still in Omega 4.x, just handled in template files?

I am willing to put the time into learning the installation and management of Omega 4.x if that is the way to go, but I don't want to have to learn it in order to decide whether to use it--if that makes sense.

Earlier this week my Omega 3.x showed up in red and said I had to upgrade to 4.x but that it was not backward compatible. I ignored it for a few days and now it is back to green.

If I understand the above this was an error? I am safe to keep it the way it is?

Thanks,

Beth

Yes. The removal of Omega 3 was not intended. No need to worry. If you want to upgrade and have the budget and time to do so, feel free to do it.. Otherwise wait for the next project to play with Omega 4.