This project was generated with Angular CLI version 1.0.0.
These guidelines are for contributors to understand and navigate around the Board (added via ZenHub Extension).
| Github/Zenhub Term | Agile Mapping | Explanation |
|---|---|---|
| Issues | User Stories | The title of each issue is a user story: it is a high-level feature description that helps the developer focus on the business value of the product. The format of an issue's title is: As a <usertype>, I want to <task> so that <goal>. For example: As a student, I want to store a useful link quickly so that I can view it later or share it with my friends |
| Milestones | Sprint | This represents a fixed length of time during which all developers and designers agree to produce a certain chunk of work. |
| Epics | Epics | They are big user-stories (higher-level, more abstract issues) which focus on the big picture |
| Pipeline | The columns in the Board (similar to Trello format), that shows the stages of each issue as it progresses through the development cycle |
Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.
Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.
Run ng test to execute the unit tests via Karma.
Run ng e2e to execute the end-to-end tests via Protractor.
Before running the tests make sure you are serving the app via ng serve.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.