Documentation. Support. Contribute. Contributors. Repositories.
- visite web side on view
| Command | Description |
|---|---|
| npm run start | start the application locally |
| npm run gh-page | publish the application and stores the result in docs folder automatically |
| npm run e2e | to run end to end test of the application |
- Create new branch or fork
- Clone the Code or pull all*
- Switch to your branch from 1.
- Run command (if needed) --> npm install
- Run script start --> npm run start
- Make your change
- Run the script gh-page success? --> npm run gh-page
- Run the batch file deploy.cmd sucess? npm run deploy
- Commit with Issue number (Create a new one if number not exists)
- Push it
- Merge only with review!
Contributors and feedback are encouraged and welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contributors Guidelines. By participating in this project, you agree to abide by its Code of Conduct at all times.
- @idrice24
- @Ghislain1
The following channels are available for discussions, feedback, and support requests:
| Type | Channels |
|---|---|
| General Discussion |  |
| Concept Feedback | |
| Backend Issue | |
| Other Requests |  |
You can find the architecture overview here, which will give ou a good starting point in how the backend services interact with other services, and purpose the serve.
- Angular CLI version 10 or higher
- Understand scripting for Automation
- Understand Markdown for documentation