Install

Works with Drupal: 8.x

Using Composer to manage Drupal site dependencies

Alternative installation files

Download omega-8.x-5.0-alpha4.tar.gztar.gz 436.46 KB
MD5: cd1d9cf034a3368503f59c4f9c6f1788
SHA-1: 007ee1eb1e08727c4ddf3a14c63f5efabb743902
SHA-256: d443a88a01a9305edc9a72a92a38c4c9eee00df2c1e02775ab632f58bbf003f3
Download omega-8.x-5.0-alpha4.zipzip 616.99 KB
MD5: 7d7acbb2dcedd57ec16a4f36997fec71
SHA-1: 988919c3109231a17a1cf33eaf9b1a77cd927cc2
SHA-256: 362303c9fb81842d8a9fdc4f79afee3378d2c498006be5195c9bc045a7cb0e23

Release notes

Lots of updates, but primarily an update to provide the OmegaExport class that handles the cloning of, subtheming of Omega Five themes from the Interface.

To get started, enable Omega, and go to the settings page. This will allow you to create a clone of one of the default Omega Starterkits. You could also subtheme a starterkit, however when creating a 'real' theme, and not just testing, you wouldn't want the starterkit as a base theme of anything in your theme inheritance chain.

Once you've cloned a theme, you can then alter, adjust, etc. and then create a clone or subtheme of that theme as well.

When creating a subtheme, various logic is considered and a few options present to provide a theme-settings.php file, empty js/css library, theme file example functions, etc. This functionality will be further hashed out/debated later in what we want exactly to be able to do when using this feature.

I've already used the feature extensively in testing creating multi level deep subthemes, and can see the feature being nice to handle making a clone of your subtheme that will allow you to test an internal patch against a theme/subtheme.

Created by: himerus
Created on: 11 Jan 2016 at 15:58 UTC
Last updated: 22 Feb 2016 at 18:08 UTC
Bug fixes
New features

Other releases