Download as
Browse Code »

Commit 66c3e41780e0a5e78d678d96cbf93699f0b37dee

Authored by Evandro Junior
1 parent 6be9287d
Exists in master and in 9 other branches cosmetic_changes_people_and_communities_block, forgot_password, layout_support, profile-blocks-sass, profile_description_block_component, recent-activities, staging, translations, users_profile_page

improve readme.md

Showing 1 changed file with 11 additions and 2 deletions   Show diff stats
README.md
  Diff comments   View file @66c3e41
... ... @@ -55,18 +55,27 @@ See some important folders bellow:
55 55  
56 56 - Create an any scss file into: `app/layout/skins/`
57 57 > **Suggestion:** Create a `sass` file partial. Something like: **`_mycustom.scss`**.
58   -
  58 +
59 59 - Extend your skin css class from `%skin-base` scss placeholder selector. Something like this:
60 60 > **Suggestion:** Use the prefix **`skin-`** to the css class
61 61  
62 62 ```sass
63   -.skin-custom {
  63 +.skin-mycustom {
64 64 @extend %skin-base
65 65 }
66 66 ```
67 67 - Configure application to use the new theme, e.g.:
68 68 `npm config set angular-theme:skin skin-mycustom`
69 69  
  70 +**N.B.**
  71 +
  72 +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.
  73 +
  74 +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`.
  75 +
  76 +Example: _mycustom.
  77 +
  78 +
70 79 - Start the application with `npm start` scripts or make a build
71 80 > **PS:** If the configured skin is invalid, an error message is showed in the terminal.
72 81  
... ...