Posted by letrotteur on January 24, 2012 at 10:04pm
Would it be a good practice to store omega sub-theme settings inside a feature using the features module? From what I can see, all the settings can be stored inside the .info of the subtheme using omega tools. We are building a pretty huge website right now and are looking for the best practices in link with the omega framework.
Any tips and advice on this topic would be much appreciated.
Comments
IMHO, subtheme is best
Since Omega provides a "theme standard" way of storing default settings in the info file, I fail to see any advantage to placing those settings in a feature, which only duplicates the functionality of the subtheme placement. That's one extra piece of code you've got to keep up with.
HOWEVER, if you are using the Delta module, then Features becomes an invaluable tool, because it allows you to store several Omega configurations, which isn't currently possible in the Omega subtheme. But the default settings should/will still be in the Omega subtheme info file.
If you haven't experimented with the Delta module (plus Context) I highly recommend it. It's amazing the power and flexibility you gain for customizing your website. It really comes close to being "panels in a theme."
+1 on leveraging Delta &
+1 on leveraging Delta & Context to unleash the full potential of Omega. Please see http://drupal.org/node/1298616 for the full list of additional recommended modules.
There are plans for a drag-drop UI aka http://drupal.org/project/omega_ui. ETA is TBD.
"Hmmmmmm, try I will, happy I
"Hmmmmmm, try I will, happy I will be!" -- yoda