Skip to content

Latest commit

 

History

History
189 lines (116 loc) · 6.52 KB

File metadata and controls

189 lines (116 loc) · 6.52 KB

✨ Contributed by Ashish Singh as part of the API Fellowship Assignment

Keploy

Docs Website

Repository for the Keploy documentation website.

git-checkout--b-ashish-readme-update

Note: Issue creation is disabled on this repository. Please visit here to submit an issue. ⚠️ Note: Issue creation is disabled in this repository.
To submit a new issue, please visit the Keploy community forum or the main repo’s issue tracker. main

GitHub contributors GitHub issues by-label Slack Twitter Follow License

Keploy is a no-code testing platform that generates tests from API calls.

Keploy is constantly working to improve and expand its documentation. As Keploy evolves rapidly, you may notice changes in slugs, menu labels, or content organization. These efforts aim to provide the best experience possible.

The documentation in this repository is published at https://docs.keploy.io.

If the information you're looking for seems missing, visit the Keploy Community Forum for help.

Please read the CONTRIBUTING guide and the STYLE guide before submitting a pull request.

Maintainers and contributors to this project are expected to conduct themselves respectfully. See the CNCF Community Code of Conduct as a reference.


🛠️ Technology Stack

We use a variety of technologies to build the web interface and support the community:

We use NodeJS and Yarn to install, test, and build the website. Docusaurus serves as our static site generator. React powers our component-based UI, and GitHub Actions manages CI/CD pipelines.


🧩 Installation

The Keploy documentation site uses Docusaurus 2.

To get started locally:

npm install
npm start


The command starts a local development server and opens a browser window.

> 💡 **Tip:** After running `npm install`, use `npm start` to preview changes live at `http://localhost:3000/`.


## Running Vale Locally for Documentation Linting

To help maintain consistency in our documentation, we use Vale, a syntax-aware linter that checks for spelling, grammar, and style issues.

### Installation

**Step 1: Install Vale**

If you're on macOS, you can install Vale using Homebrew:

```bash
brew install vale

Alternatively, you can install Vale manually:

  1. Download Vale: Visit the Vale Releases page and download the latest version for your operating system.

  2. Install Vale:

  • On macOS and Linux, extract the binary, move it to /usr/local/bin, and make it executable:
sudo mv vale /usr/local/bin/
sudo chmod +x /usr/local/bin/vale
  • On Windows, follow the instructions in the downloaded .zip file.

Step 2: Configure Vale

  1. Ensure you have the .vale.ini configuration file in the root directory.

  2. Check that StylesPath in .vale.ini points to the vale_styles directory (where custom styles are stored):

StylesPath = vale_styles
MinAlertLevel = error

Running Vale

  1. Linting Documentation: To check all markdown files in versioned_docs/version-2.0.0/ for errors, run:
vale versioned_docs/version-2.0.0/**/*.md
  1. Review Errors:
  • Vale will output any issues directly in the terminal. Address these issues in the markdown files to maintain style consistency.

Note: Running Vale locally helps catch issues early, ensuring a smooth review process when you submit a pull request.

Prettier

  1. Fork the repository

  1. Clone the repository with the following command. Replace the {'<'}GITHUB_USERNAME{'>'} with your username
git clone https://github.com/<GITHUB_USERNAME>/docs.git

## Go into the directory containing the project

cd docs

  1. Install all the dependencies
npm install

## Start the development server.

npm start
  1. To reformat:
npx prettier --write '**/*.{js,md}'
  1. Check the build status:
npm run build

Note: if the Build is failing, fix the changes before making PR.

When we merge your PR, a new build automatically occurs and your changes publish to https://keploy.io/docs.

How to Get Involved?

Keploy welcomes contributions to the docs website. If you have an idea for a new feature or a bug fix, please submit an issue or pull request. Our planned features can be found on our Issue Tracker.

Community Support ❤️

🤔 Questions?

Reach out to us. We're here to help!

Slack LinkedIn YouTube Twitter

💖 Let's Build Together!

Whether you're a newbie coder or a wizard 🧙‍♀️, your perspective is golden. Take a peek at our: