Keploy is a no-code testing platform that generates tests from API calls.
This README guide provides an overview of the color palette used in the project, along with their respective purposes and usage.
| Color Name | Purpose | Color Patch | Hash Value |
|---|---|---|---|
| Primary Color | Primary headings, primary buttons, main elements | #FF914D |
|
| Secondary Color | Backgrounds, borders, subtle accents | #00163D |
|
| Neutral Colors | Backgrounds, borders, subtle accents | #F5F5F5 #FFF #E6E2D4 |
|
| Accent Colors | Success messages, notifications, progress indicators | #16704C |
|
| Highlights, icons, creative sections | #5F3131 |
||
| Attention-grabbing elements, notifications, important highlights | #EF546B #D9CD9C |
||
| Gradient Colors | - | #F5F5F5 #E35134 #FF914D #BE2C1B #6F0A0D |
This README guide provides a quick reference to the colors in the palette and their intended purposes. Use this guide to ensure consistent usage of colors throughout the project and to maintain a cohesive visual style.
Feel free to discuss and customize the README guide further based on your project requirements and additional details you'd like to include.
We'd love to collaborate with you to make Keploy great. To get started:
Please read the CONTRIBUTING guide and the Color Palette guide before you submit any pull requests.
Maintainers and contributors to this project are expected to conduct themselves in a respectful way. See the Code of Conduct as a reference.
We use a variety of technologies to build the web interface and support the community. They include:
If you wish to contribute, we highly recommend following the guidelines mentioned below.
1. Fork this repository.
2. Clone your forked copy of the project.
git clone https://github.com/<GITHUB_USERNAME>/website.git
npm install
npm run dev # or npm run build8. Stage your changes and commit.
git add .
git commit -m "<your_commit_message>"
9. Push your local commits to the remote repo.
git push
10. Create a PR
To contribute to this project, you must agree to the Developer Certificate of Origin (DCO) for each commit you make. The DCO is a simple statement that you, as a contributor, have the legal right to make the contribution.
See the DCO file for the full text of what you must agree to and how it works here. To signify that you agree to the DCO for contributions, you simply add a line to each of your git commit messages:
Signed-off-by: Jane Smith <jane.smith@example.com>
In most cases, you can add this signoff to your commit automatically with the
-s or --signoff flag to git commit. You must use your real name and a reachable email
address (sorry, no pseudonyms or anonymous contributions). An example of signing off on a commit:
$ commit -s -m “my commit message w/signoff”
To ensure all your commits are signed, you may choose to add this alias to your global .gitconfig:
~/.gitconfig
[alias]
amend = commit -s --amend
cm = commit -s -m
commit = commit -s
To maintain a safe and inclusive space for everyone, to learn and grow, contributors are advised to follow the Code of Conduct and also go through Guidelines for Contributing atleast once.
This project needs a ⭐️ from you. Don't forget to leave a star ⭐️