Skip to content

Conversation

@adityakedawat
Copy link
Contributor

@adityakedawat adityakedawat commented Aug 10, 2025

Description

  • Added generate_api_docs.py script for automatic API documentation generation.
  • Updated .gitignore to exclude the site/ directory.
  • Modified Makefile to include commands for building, serving, and deploying documentation.
  • Created mkdocs.yml for documentation configuration.
  • Added various documentation files including guides, API references, and examples.
  • Established requirements-docs.txt for documentation dependencies.
  • Implemented a setup script for the documentation environment.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Testing

  • Unit tests pass
  • Integration tests pass
  • Manual testing completed
  • Documentation updated

Checklist

  • Code follows the style guidelines
  • Self-review of code completed
  • Code is commented, particularly in hard-to-understand areas
  • Corresponding changes to documentation made
  • Changes generate no new warnings
  • Tests added that prove fix is effective or feature works
  • New and existing unit tests pass locally
  • AI assistance (e.g., Cursor, ChatGPT, Claude) was used in making these changes (please specify tools in the PR description)

Additional Context

  • Link to related issues: Fixes #123
  • Screenshots (if UI changes)
image
  • Performance impact analysis
  • Breaking changes explanation

- Added `generate_api_docs.py` script for automatic API documentation generation.
- Updated `.gitignore` to exclude the `site/` directory.
- Modified `Makefile` to include commands for building, serving, and deploying documentation.
- Created `mkdocs.yml` for documentation configuration.
- Added various documentation files including guides, API references, and examples.
- Established `requirements-docs.txt` for documentation dependencies.
- Implemented a setup script for the documentation environment.
- Added new features to the MkDocs configuration, including additional content tabs and code selection options.
- Replaced the deprecated `mkdocs-mermaid2-plugin` with `mkdocs-mermaid` in the requirements.
- Removed the obsolete README.md file from the documentation directory.
- Enhanced user guide with sections on custom protocol handlers and distributed testing.
- Updated API documentation filters to exclude specific internal modules and improved overall structure.
@adityakedawat adityakedawat self-assigned this Aug 10, 2025
…ture diagram

- Added `mkdocs-mermaid2` to `requirements-docs.txt` for enhanced diagram support.
- Updated the architecture diagram in `index.md` to reflect changes in the configuration flow and components.
- Expanded the Request Configuration section to clarify support for both HTTP and WebSocket requests across multiple documentation files.
- Updated prerequisites in the Quick Start guide to require Python 3.9 or higher.
- Enhanced user guide and configuration reference with detailed examples for WebSocket requests and a new plugin feature in development.
- Improved overall clarity and consistency in documentation regarding request handling and configuration options.
- Corrected the links to the API Reference in the Development Guide, Examples, and User Guide to point to the updated path (/gradual/api/overview/).
- Ensured consistency across documentation for easier navigation and access to technical information.
Copy link

@subhamagrawal7 subhamagrawal7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we modify the generate_api_docs.py or some automated way to ensure markdown consistency such as extra newlines so that at all places the steps numbering which should be at different lines is automatically fixed? Else we would have to manually modify all the docstrings as well for the functions.

- Updated flowchart styles in the configuration reference documentation to include font size specifications for better readability.
- Added new styles for additional nodes in the ramp-up flowcharts to maintain consistency and improve visual clarity.
@adityakedawat
Copy link
Contributor Author

Can we modify the generate_api_docs.py or some automated way to ensure markdown consistency such as extra newlines so that at all places the steps numbering which should be at different lines is automatically fixed? Else we would have to manually modify all the docstrings as well for the functions.

This will take good amount of efforts. I have created a github issue, to address this separately if we think this is causing too much trouble.

@adityakedawat adityakedawat merged commit 0cbde90 into main Aug 24, 2025
3 checks passed
@adityakedawat adityakedawat deleted the docs_setup branch August 24, 2025 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants