From 66c3e41780e0a5e78d678d96cbf93699f0b37dee Mon Sep 17 00:00:00 2001 From: Evandro Junior Date: Tue, 28 Jun 2016 11:15:03 -0300 Subject: [PATCH] improve readme.md --- README.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 747cf00..342202a 100644 --- a/README.md +++ b/README.md @@ -55,18 +55,27 @@ See some important folders bellow: - Create an any scss file into: `app/layout/skins/` > **Suggestion:** Create a `sass` file partial. Something like: **`_mycustom.scss`**. - + - Extend your skin css class from `%skin-base` scss placeholder selector. Something like this: > **Suggestion:** Use the prefix **`skin-`** to the css class ```sass -.skin-custom { +.skin-mycustom { @extend %skin-base } ``` - Configure application to use the new theme, e.g.: `npm config set angular-theme:skin skin-mycustom` +**N.B.** + +1-The full name of the scss class should be used as the parameter for the command `npm config set angular-theme:`, like in _skin-mycustom_. DO NOT use the file name of the skin as the parameter. + +2-The skin's file should be the named as the scss class without the word `skin`, preceded by an underline. Otherwise it will raise an error during `npm install`. + +Example: _mycustom. + + - Start the application with `npm start` scripts or make a build > **PS:** If the configured skin is invalid, an error message is showed in the terminal. -- libgit2 0.21.2