This repository contains a comprehensive guide to best practices and anti-patterns in AI development.
The documentation is built using MkDocs with the Material for MkDocs theme.
The documentation is automatically deployed to GitHub Pages and can be viewed at: https://aaronsb.github.io/ai-dev-practices-guide/
To run the documentation locally:
-
Clone this repository:
git clone https://github.com/aaronsb/ai-dev-practices-guide.git cd ai-dev-practices-guide
-
Run the setup script:
- On Linux/macOS:
./setup_and_test.sh
- On Windows:
setup_and_test.bat
- On Linux/macOS:
-
Start the local development server:
- On Linux/macOS:
source venv/bin/activate mkdocs serve
- On Windows:
venv\Scripts\activate mkdocs serve
- On Linux/macOS:
-
Open your browser and navigate to
http://localhost:8000
-
When you're done, deactivate the virtual environment:
- On Linux/macOS:
deactivate
- On Windows:
deactivate
- On Linux/macOS:
-
Clone this repository:
git clone https://github.com/aaronsb/ai-dev-practices-guide.git cd ai-dev-practices-guide
-
Create and activate a virtual environment:
python -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate
-
Install the dependencies:
pip install -r requirements.txt
-
Start the local development server:
mkdocs serve
-
Open your browser and navigate to
http://localhost:8000
Contributions are welcome! Please feel free to submit a Pull Request.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature
) - Commit your changes (
git commit -m 'Add some amazing feature'
) - Push to the branch (
git push origin feature/amazing-feature
) - Open a Pull Request
The deployment process works in two stages:
-
GitHub Actions Workflow: When changes are pushed to the main branch, a GitHub Actions workflow builds the MkDocs site and pushes the generated content to the
gh-pages
branch. -
GitHub Pages: GitHub's built-in Pages service then detects changes to the
gh-pages
branch and deploys the content to the public site at https://aaronsb.github.io/ai-dev-practices-guide/.
This two-stage process ensures that your documentation is always up-to-date with the content in your main branch.
This project is licensed under the MIT License - see the LICENSE file for details.