As an open source project, WSO2 API-M welcomes contributions from the community. To start contributing, read these contribution guidelines for information on how you should go about contributing to our project.
-
Accept the Contributor License Agreement (CLA)
You need to Accept the Contributor License Agreement (CLA) when prompted by a GitHub email notification after sending your first Pull Request (PR). Subsequent PRs will not require CLA acceptance.
If the CLA gets changed for some (unlikely) reason, you will be presented with the new CLA text after sending your first PR after the change.
-
Fork this repository, make your changes, and send in a pull request (PR). Make sure you are contributing to the correct branch (for example, if your change is relevant to WSO2 API-M 4.7.0 documentation, you should commit your changes to the 4.7.0 branch).
-
Send multiple pull requests to all the relevant branches.
If your change is relevant to the latest API-M release, please send your change to the respective latest API-M release branch and the master branch, which is the upcoming API-M release documentation branch, as well.
For example, if the latest API-M release is 4.7.0, and if your change is relevant to API-M 4.6.0, 4.5.0, 4.4.0, 4.3.0, and 4.2.0, send PRs to the 4.6.0, 4.5.0, 4.4.0, 4.3.0, 4.2.0, and the master branches.
Check the issue tracker for open issues that interest you. We look forward to receiving your contributions.
If you are using MacOS, you probably already have a version of Python installed on your machine. You can verify this by running the following command.
$ python --version
Python 2.7.2If your version of Python is Python 2.x.x, you also need to install Python 3. This is because the PDF plugin only supports Python 3. Follow the instructions in this guide to install Python 3 properly.
Once you are done, you will have two versions of Python on your machine; a version of python 2 and a version of python 3.
Python 3 is pre-installed in these versions, which you can verify with python3 -V. Use sudo apt install -y python3-pip to install pip and verify with pip3 -V.
INFO
If pip is not already installed on your machine, download
get-pip.pyto install pip for the first time. Then run the following command to install it:$ python3 get-pip.py
Pip is most likely installed by default. However, you may need to upgrade pip to the latest version:
$ python3 -m pip install --upgrade pipFollow the steps below to clone the API-M documentation GitHub repository and to run the site on your local server.
-
Fork the GitHub repository:
https://github.com/wso2/docs-apim.git -
Navigate to the place where you want to clone the repo.
Git clone the forked repository.
$ git clone https://github.com/[git-username]/docs-apim.git
-
Navigate to the folder containing the repo that you cloned in step 3.2 on a terminal window.
For example:
$ cd docs-apim/<Language-folder>/
$ cd docs-apim/en/ -
Install the required pip packages.
This will install MkDocs and the required theme, extensions, and plugins.
-
If you are using Python 2 (legacy support), use the following command:
$ pip install -r requirements.txt
-
If you are using Python 3 (recommended), use the following command:
$ python3 -m pip install -r requirements.txt
-
-
Run the following command to start the MkDocs server and view the documentation locally:
$ python3 -m mkdocs serve
NOTE:
If you want to see changes automatically while editing:
-
Open the
mkdocs.ymlfile. -
Set the following configuration:
strict: false -
Run the server with live reload:
$ python3 -m mkdocs serve --dirtyreload
-
-
Open the following URL in your browser to view the API Manager documentation site locally.
NOTE:
If you use
mkdocs serve --dirtyreload, make sure to reset the configuration before committing: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.