Skip to content
This repository was archived by the owner on Mar 4, 2025. It is now read-only.

Commit 2096723

Browse files
committed
Merge pull request #10 from appirio-tech/readme-updates
Update readme
2 parents ef888c4 + d42d174 commit 2096723

File tree

1 file changed

+11
-13
lines changed

1 file changed

+11
-13
lines changed

README.md

Lines changed: 11 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -13,23 +13,22 @@ Install dependencies by running the following in the root of the project:
1313
- npm install
1414
- bower install
1515

16-
## Guide to the Gulpfile
16+
## Gulpfile Commands
17+
18+
- Run `gulp` to get a list of commands
1719

1820
- To run locally without minification: `gulp serve`
1921

20-
- To build dist folder
21-
- `gulp build`
22+
- To create the build: `gulp build`
2223

23-
- To serve the build
24-
- `gulp serve-build`
24+
- To serve the build: `gulp serve-build`
2525

26-
- To run the test runner and view specs.html
27-
- `gulp serve-specs`
26+
- To run the test runner and view specs.html: `gulp serve-specs`
2827

2928
### Testing
3029

31-
Running `gulp test` will perform a single run of the unit tests with karma.
32-
Running `gulp autotest` will keep the server running and watching files.
30+
Running `gulp test` will perform a single run of the unit tests with karma in the command line.
31+
Running `gulp autotest` will keep the server running and watching files in the command line.
3332

3433
## Contributing
3534

@@ -47,12 +46,11 @@ SCSS Files
4746
- Use SCSS syntax (nesting)
4847
- Use variables and mixins as much as possible
4948
- Store new variables and mixins in the appropriate file in `assets/css/partials`
49+
- Since a class with the current state name is added to the ui-view (see the Creating New Views/Pages section), wrap your .scss file with this class, in order to write specific scss in its own file for that page.
5050

5151
JS/ES6
5252
- Follow this [AngularJS style guide](https://github.com/johnpapa/angular-styleguide)
5353

5454
Creating New Views/Pages
55-
- Todo - change the following to be relevant to this particular repo:
56-
- To add a new page, create a folder in the app directory and a new state in app.routes.coffee
57-
- Name the new folder the same as the state name
58-
- In order to keep the SCSS files modular, a class is automatically added with the name of the state to the ui-view div in index.jade. For example, if you create a new `/feature1` state and navigate there, the div with the content will look like this: `<div class="view-container feature1">`. This allows you to have your own feature1.scss file. Use the landing.scss file as an example, where you can see how all the styles are nested in `.landing`.
55+
- To add a new page, create a folder in the app directory and follow the naming conventions found elsewhere, e.g. login.controller.js, login.jade, login.spec.js, etc. Make sure to add a new state in the module's routes file.
56+
- In order to keep the SCSS files modular, a class is automatically added with the name of the state to the ui-view div in index.jade. For example, if you create a new `/feature1` state and navigate there, the div with the content will look like this: `<div class="view-container feature1">`.

0 commit comments

Comments
 (0)