This is the Choreo documentation repository. This repository is open and we welcome your contributions!

To see the Choreo documentation site, go to https://wso2.com/choreo/docs/

Before you contribute, read the following guidelines to understand how you can start contributing:

1. Accept the contributor license agreement (CLA)

   You need to accept the contributor license agreement (CLA) when you are prompted via a GitHub email notification on sending your first pull request (PR). Subsequent PRs will not require CLA acceptance.

   If the CLA changes for some (unlikely) reason, you'll have to accept the new CLA text when you send your first PR after the change.

2. Fork this repository, make your changes, and send in a pull request.

   For an overview of the general voice, tone, content style, and text formatting to follow when contributing to Choreo documentation, see Choreo Documentation Guidelines and Best Practices

We look forward to your contributions.

This repository supports the VS Code dev containers feature, which allows you to create a consistent and isolated development environment inside a Docker container. To use this feature, you need to have the following pre requisites:

• VS Code
• Docker installed on your system
• Remote - Containers extension for VS Code

Once you have these installed, you can open the repository in VS Code and follow these steps:

• Press F1 and select the Remote-Containers: Open Folder in Container... command.
• Select the repository folder and wait for the container to build and start.
• You can now edit, run, debug, and test your code inside the container.

For more information on how to use VS Code dev containers, please refer to the official documentation: https://code.visualstudio.com/docs/remote/containers

To start the server and view the site on your local server, run the following command:

```shell
$ mkdocs serve
```

> **NOTE:**
>
> If you want to make changes and see them on the fly, run the following command to start the server and view the site on your local server:
> 1. Navigate to the `mkdocs.yml` file.
> 2. Set the following configuration:
>     ```
>     #Breaks build if there's a warning
>     strict: false
>     ```
> 3. To start the server, make it load the changes, and display the changes faster, run the following command:
>
>    `mkdocs serve --dirtyreload`

2. To view the Choreo documentation site locally, open the following URL on a new browser window:

   https://localhost:8000/

If you are using macOS, you probably already have a version of Python installed on your machine. Run the following command to verify:

$ python --version
Python 2.7.2

If your version of Python is 2.x.x, you need to install Python3. Follow the instructions in this guide to install Python3.

Once you are done, you should see two versions of Python on your machine; python2 and python3.

Python 3 is pre-installed in these versions, which you can verify using the python3 -V command. Run sudo apt install -y python3-pip to install pip and verify using pip3 -V.

INFO

If pip is not already installed on your machine, run get-pip.py to install pip. Then run the following command to install it:

$ python get-pip.py

Pip is most likely installed by default. However, you may need to upgrade pip to the latest version:

$ pip install --upgrade pip

To clone the Choreo documentation GitHub repository and run the site on your local server, follow these steps:

1. Fork https://github.com/wso2/docs-choreo-dev.

2. Navigate to the locatiion where you want to clone the repo and clone the forked repository.

   $ git clone https://github.com/[git-username]/docs-choreo-dev.git

3. Navigate to the directory where you cloned the repo.

   For example:

   $ cd docs-choreo-dev/<Language-folder>/

   $ cd docs-choreo-dev/en/

4. Install the required pip packages.

   This step installs MkDocs together with the required theme, extensions, and plugins.

   • If you are using Python2, run the following command:

     $ pip install -r requirements.txt

   • If you are using Python3, run the following command:

     $ pip3 install -r requirements.txt

1. To build the code navigate to the en folder and run the following command:

   $ ./serve.sh

This script will check spellings and incorrect links.

Incorrect spellings will be highlighted in red. You can take one of the following resolution paths:

• Choose the suggested correct spelling.
• Proceed with "Ignore" to skip the word and not be prompted about it again during the current run. However, it will reappear if you rerun the command.
• Proceed with "Add to file ignores" to ignore the word in the current file.
• Proceed with "Add to dictionary - case insensitive" to add the word to the dictionary for all files, allowing it to match regardless of case. For example, with the word "Microsoft," both "Microsoft" and "Microsoft" would be considered correct.
• Proceed with "Add to dictionary - case sensitive" to add the word to the dictionary for all files, but only match the exact case used. For instance, with the word "Microsoft," the word "microsoft" would not be considered correct.

All exclusions will be stored in a .spelling file in the directory from which you run the command.

Choose resolutions consciously.

If there are no errors, proceed to the next step.

1. To start the server and view the site on your local server, run the following command:

   $ mkdocs serve

   NOTE:

   If you want to make changes and see them on the fly, run the following command to start the server and view the site on your local server:

   1. Navigate to the mkdocs.yml file.

   2. Set the following configuration:

      #Breaks build if there's a warning
      strict: false
      

   3. To start the server, make it load the changes, and display the changes faster, run the following command:

      mkdocs serve --dirtyreload

2. To view the Choreo documentation site locally, open the following URL on a new browser window:

   https://localhost:8000/

NOTE:

If you are using the mkdocs serve --dirtyreload command to run the MkDocs server, be sure to change the configuration in the mkdocs.yml file as follows before sending a pull request:

strict: true

Licenses this source under the Apache License, Version 2.0 (LICENSE), You may not use this file except in compliance with the License.