This is the Bijira documentation repository. This repository is open and we welcome your contributions!
To see the Bijira documentation site, go to https://wso2.com/bijira/docs/
This documentation site is built using MkDocs with the Material theme. Follow these steps to set up and run the documentation locally.
- Python 3.12 (required)
- Node.js (for spell checking and link validation tools)
- Git (for version control)
Run the setup script for automatic environment configuration:
./setup-dev.shThis script will:
- Check for Python 3.12+
- Create a virtual environment
- Install all Python dependencies
- Install Node.js validation tools (if Node.js is available)
- Provide next steps
-
Clone the repository:
git clone https://github.com/wso2/docs-bijira.git cd docs-bijira -
Create and activate a Python virtual environment:
python3 -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate
-
Install Python dependencies:
cd en pip install -r requirements.txt -
Install Node.js tools for spell checking and link validation (optional):
npm install -g markdown-spellcheck markdown-link-check
To start the development server with live reload:
cd en
python -m mkdocs serveThe documentation will be available at: http://localhost:8000/bijira/docs/
If port 8000 is already in use, specify a different port:
python -m mkdocs serve --dev-addr localhost:8001If you have the Node.js tools installed, you can run the complete validation script:
./serve.shThis script will:
- Run spell checking on all markdown files
- Validate all links in the documentation
- Build the static site
- List the generated files
To build the static site for deployment:
cd en
python -m mkdocs buildThe built site will be generated in the site/ directory.
docs-bijira/
├── en/ # English documentation
│ ├── docs/ # Documentation source files
│ ├── theme/ # Custom theme files
│ ├── mkdocs.yml # MkDocs configuration
│ ├── requirements.txt # Python dependencies
│ └── serve.sh # Validation and build script
├── devportal-theming/ # Theming assets
└── README.md # This file
- Edit markdown files in the
en/docs/directory - The development server will automatically reload changes
- Preview your changes at the local development URL
- Test links and spelling using the validation tools
- Submit a pull request with your changes
Virtual environment activation issues:
- On macOS/Linux:
source venv/bin/activate - On Windows:
venv\Scripts\activate
Port conflicts:
Use a different port with --dev-addr localhost:XXXX
Missing Node.js tools: The spell checking and link validation are optional. You can still build and serve the documentation without them.
Python version issues:
This project requires Python 3.12. Check your version with python3 --version