Posted by Marko B on January 29, 2014 at 1:30pm
As a long time omega 3 user I had to say starting with omega 4 is hard. I just have a feeling that things with drupal are getting more and more complex so I am wondering if we are making things faster or slower to use and build as there is so much of build a crane to build a crane to build a crane ... to build a building instead of just build one good crane to build a building.
Comments
Yes, it's a steep learning
Yes, it's a steep learning curve, because Omega4 comes with many new technologies, all of which mist be learned and assimilated. But the resulting new workflow is well worth the effort: writing CSS via SASS and Compass is so much faster and easier. The ability to declare variables and to break everything down into smaller SASS files is priceless, make changes and maintenance so much easier, even pleasurable. My advice is to realize that you're on a technology learning curve and to stick with it. Once you get a glimpse of what it's all about, you won't want to go back to Omega3 and CSS.
I hear ya.. but it does become easier and more empowering..
I went thru the lessons here: https://www.codeschool.com/paths/html-css#sass for sass and that helped me alot. Good luck. its never ending learning.
Many of us find it more close
Many of us find it more close to our needs, it's not "hard".
Omega 4 let's you play much more easier with templating and organize better your CSS with many best practices.
I'm Agree
i'm new in omega 4 , and i was trying to understand how to make things work in it .
i was trying to Setup Sass in Windows
https://www.drupal.org/node/2204227
but it's failed
i wonder how people work with it !
Setting up O4, the first time
Setting up O4, the first time can be daunting. I don't know of anyone that has successfully set up O4 in windows though I have seen some posts in the issue queue where the steps were listed.
You deserve a proper development environment and my best advice is to set up a virtual environment using virtualbox and ubuntu. I have been working with my local drupal group to create a step-by-step document on a complete local setup. I believe around 10 or so people have followed it with complete success.
Please note* If give this doc a try, follow each step in order. Most of us who put it together can be found in irc #drupal-florida and we can help you.
https://github.com/C13L0/roll-your-own
Cielo
drupal-florida
thanks :)
i will try this thank you very much
You are very welcome. It is
You are very welcome. It is worth the time and tears to learn O4. It follows industry standard best practices. Meaning, its not specific to drupal in any way! You can use the same methodologies in any theme, no matter if it is drupal, jekyll, or wordpress. Not only will it save you time in the future but will make you more valuable for any front-end job that you may apply for.
After you have used O4 for a few times, take some time to start understanding and using BEM and SMACSS. Here is an article that gives an in-depth view http://www.sitepoint.com/bem-smacss-advice-from-developers
Cielo =)
Step by step instructions.
Hi all - I will take a look at the step by step instructions. I hope they are good. I have been having a hard time getting Omega 4 to run on my Linux server. There do not seem to be any clear instructions on how to go about doing it - I've been googling and reading posts about how to make it run, but they seem to presuppose a knowledge of Ruby, Gems, Suzy and other things that I know not of.
Basically, my situation is that I have been using Adaptive Themes as a base theme for a long time, and am familiar with grids and so on (although in reading up about Suzy, I have learned a lot about pushing and pulling columns - things I just did without really knowing why). Anyway - for a while I've only been mucking around with Drupal, but I'm doing a community web site and thought it would be a good opportunity to look at how the cool kids are building Drupal sites these days.
So I thought I'd try Omega. Then I found Suzy and thought 'that's what I've been looking for for a long time', so am trying that.
I guess my approach was to get that stuff working and get on with the theme. But if I see 'Error: File to import not found or unreadable: breakpoint.' I think I am going to ... curling up in the corner and crying isn't out of the question.
I know the strength of Open Source is that there is more than one way to do things, but when trying to fix a problem, it is hard to know what solution actually applies to my set up - there is gulp, drush, bundle, rvm, npm ...
Linux Systems Administrator
Christchurch, New Zealand.