The Elucid Team would like to thank you for your interest in helping to maintain and improve Elucid!
There are 3 npm actions you need to run before working:
- First go to website within demo and run
npm install
- Second run
npm run build
within the same directory - Third use
npm run develop
to launch the website
Optional for server-side changes:
- Go to server within demo and run
npm install
- Navigate to elucid folder and run
npm install
to download dependencies
All code changes happen through Github Pull Requests and we actively welcome them. To submit your pull request, follow the steps below:
- Fork the repo and create your branch from
main
. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the tests pass.
- Make sure your code lints.
- Submit a pull request.
Note: Any contributions you make will be under the ISC Software License and your submissions are understood to be under the same that covers the project. Please reach out to the team if you have any questions.
We use GitHub issues to track bugs. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue. 4. Ensure the test suite passes. 5. Make sure your code lints. 6. Issue that pull request!
Note: Any contributions you make will be under the MIT Software License and your submissions are understood to be under the same that covers the project. Please reach out to the team if you have any questions.
2 spaces for indentation rather than tabs 80 character line length
By contributing, you agree that your contributions will be licensed under Elucid's ISC License.