In various post I see that @fubhy is heading toward gulp as are most of the other leading front end developers and I am happy to see that.

Omega needs better documentation for quite some time.

Some pages are badly outdated and version 4.x needs a split between Ruby/gem (Dusty) and NodeJS/npm stacks (new Default) with clear separation that previous was even more different.

This way people are confused and that may prevent them to see the true potential that this excellent theme has. I even think that good documentation is what drives theme acceptance (at least Zen claims so).

I think there should be some more README.txt or even better README.md in the theme itself along with documentation under Omega Theme Documentation Handbook.

I am currently shifting myself from Ruby based to node based workflow, trying to exchange one set of tools for another while keeping as much as possible from the sass code itself.

I would like to help with documentation unless there is someone else working on the same thing — then we may split and coordinate the work.

Comments

MacMladen created an issue. See original summary.

Staler75’s picture

i would like to see some good documentation as well.
followed the levelup tuts for omega 4, but it's so outdated, i having troubles to set up the right environment and get the whole thing working like it supposed to do.

i am completely new on working with omega 4 and working with sass, i willing to learn, but it's hard to getting started without the right documentation or tutorials

Melissamcewen’s picture

Status: Active » Needs review

I added some info here
https://www.drupal.org/node/2172619
let me know what you guys think. If it looks good we should consider adding it to the Readme maybe?

steinmb’s picture

Great work @Melissamcewen https://www.drupal.org/node/2172619/revisions/view/7812237/9097938
#2537364: Switch current omega sub-theme to LibSass is related to this doc also. Please join in there and test out patch for libsass. I think we should keep the doc https://www.drupal.org/node/2172619 and not commit it to any README, makes is easier to keep up2date without submitting patches.

steinmb’s picture

Version: 7.x-4.4 » 7.x-4.x-dev
mattman’s picture

I wanted to get livereload (via npm/gulp) going with the new libsass version, added some info here #2649860: Adding livereload to gulp tasks