This repository contains the source code for WSO2 Micro Integrator documentation. We welcome your contributions!
- Getting Started
- How to contribute
- Setting Up Your Development Environment
- Running the Project Locally
- Troubleshooting
- Legal
The WSO2 Micro Integrator documentation provides comprehensive guides, tutorials, and reference materials for working with the WSO2 Micro Integrator platform.
- Documentation Website: https://mi.docs.wso2.com/
- Repository Structure:
-
docs-mi/en/docs/
: Contains all the.md
files with content.Tip :
docs-mi/en/docs/
directory is reffered by {{base_path}} through out the documentation.e.g. <a href="{{base_path}}/assets/img/develop/mi-for-vscode/mi-vscode-extension.png"><img src="{{base_path}}/assets/img/develop/mi-for-vscode/mi-vscode-extension.png" alt="Mi VS Code Extension" width="80%"></a>
-
docs-mi/en/docs/assets
: Contains all the resources (images/attachments/videos) used throughout the documentation -
docs-mi/en/docs/mkdocs.yaml
: The configuration file used by MkDocs, a static site generator that's geared towards project documentation. It defines the structure, theme, plugins, and other settings for building and deploying the documentation site.Tip : You have to update
nav
section inmkdocs.yaml
for new pages you add.nav: - Home: index.md - Get Started: - Introduction: get-started/introduction.md - Key Concepts: get-started/key-concepts.md - Quick Start Guide: get-started/quick-start-guide.md
-
docs-mi/en/docs/requirements.txt
: This file lists all the Python dependencies required to build and run the documentation site locally. These dependencies include MkDocs and its plugins, which are essential for generating and serving the static site.
-
For small changes like fixing typos, updating links, or adding short sections:
- Navigate to the page you want to edit on GitHub
- Click the edit (pen) icon in the top right corner
- Make your changes to the
.md
file - Add a descriptive commit message
- Click "Commit changes" to open a Pull Request (PR)
- Fill in the PR details and submit
For significant modifications like adding new pages or replacing images:
- Fork and clone the repository
- Create a new branch for your changes
- Make your modifications in the
docs-mi/en/docs/
directory - Test your changes locally (see Running the Project Locally)
- Commit and push your changes
- Open a Pull Request
If you encounter any issues, check the Troubleshooting section.
You'll need:
- Python 3.x.x (Recommended : 3.8.x, 3.9.x, or 3.10.x )
- pip (Python package manager)
macOS:
# Check if Python is installed
python3 --version
# If not installed, download from python.org or use Homebrew
brew install python3
Ubuntu/Debian:
# Python3 is usually pre-installed
python3 --version
# Install pip if needed
sudo apt install -y python3-pip
Windows:
- Download Python from python.org
- During installation, check "Add Python to PATH"
- Verify installation:
python --version
orpython3 --version
-
Fork the repository
Go to https://github.com/wso2/docs-mi and click the "Fork" button.
-
Clone your fork
git clone https://github.com/YOUR-USERNAME/docs-mi.git cd docs-mi
-
Install dependencies
cd en/ pip3 install -r requirements.txt
If you face any installation issues, see Troubleshooting.
-
Start the local server
# From the docs-mi/en/ directory mkdocs serve
If this command fails, see MkDocs Command Issues.
-
View the site
Open http://localhost:8000 in your browser
-
For faster development (to see changes immediately):
# Edit mkdocs.yml and set strict: false mkdocs serve --dirtyreload # Remember to set strict: true before submitting PR
When adding new content, check Image and Page Updates for important configuration steps.
-
If you get an error that MkDocs is not found, try:
python3 -m mkdocs serve
-
When Adding New Images or Pages
-
Open
mkdocs.yml
-
Update
base_path
tohttp://localhost:8000/en/latest
base_path: http://localhost:8000/en/latest #base_path: https://mi.docs.wso2.com/en/4.4.0
-
Revert this change before submitting your PR
-
-
- Refer to the Markdown Cheat Sheet for styling your content
You'll be prompted to sign the CLA via GitHub when submitting your first PR. For any changes to be accepted, the CLA must be signed.
This project is licensed under the Apache License, Version 2.0.