<h1 align="center"> lazydocs </h1> Generate markdown API documentation for Google-style Python docstring. <a href="https://pypi.org/project/lazydocs/" title="PyPi Version"><img src="https://img.shields.io/pypi/v/lazydocs?color=green&style=flat"></a> <a href="https://pypi.org/project/lazydocs/" title="Python Version"><img src="https://img.shields.io/badge/Python-3.6%2B-blue&style=flat"></a> <a href="https://www.codacy.com/gh/ml-tooling/lazydocs/dashboard" title="Codacy Analysis"><img src="https://app.codacy.com/project/badge/Grade/1c8ad486ce9547b6b713cce7ca1d1ec3"></a> <a href="https://github.com/ml-tooling/lazydocs/actions?query=workflow%3Abuild-pipeline" title="Build status"><img src="https://img.shields.io/github/workflow/status/ml-tooling/lazydocs/build-pipeline?style=flat"></a> <a href="https://github.com/ml-tooling/lazydocs/blob/main/LICENSE" title="Project License"><img src="https://img.shields.io/badge/License-MIT-green.svg?style=flat"></a> <a href="https://gitter.im/ml-tooling/lazydocs" title="Chat on Gitter"><img src="https://badges.gitter.im/ml-tooling/lazydocs.svg"></a> <a href="https://twitter.com/mltooling" title="ML Tooling on Twitter"><img src="https://img.shields.io/twitter/follow/mltooling.svg?label=follow&style=social"></a> <a href="#getting-started">Getting Started</a> • <a href="#features">Features</a> • <a href="#documentation">Documentation</a> • <a href="#support--feedback">Support</a> • <a href="#contribution">Contribution</a> • <a href="https://github.com/ml-tooling/lazydocs/releases">Changelog</a>

Lazydocs makes it easy to generate beautiful markdown documentation for your Python API (see this example). It provides a simple command-line interface as well as a Python API to get full-fledged API documentation within seconds based on all of the Google-style docstrings in your code. This markdown documentation can be pushed to Github or integrated into your MkDocs site.

Highlights

⏱ Simple CLI to generate markdown docs in seconds.
📋 Supports Google-style Python Docstrings.
📚 Compatible with Github Markdown and MkDocs.

Getting Started

Installation

Requirements: Python 3.9+.

pip install lazydocs

Usage

To generate Markdown-based API documentation for your Python project, simply execute:

lazydocs path/to/your/package

The path can be either a python package (folder) or a specific script. You can also specify one or multiple module-, class- or function-imports:

lazydocs my_package.AwesomeClass

With the default configuration, the Markdown documentation will be generated inside the ./docs folder in your working directory. You can find additional configuration options in the documentation section.

Support & Feedback

This project is maintained by Benjamin Räthlein, Lukas Masuch, and Jan Kalkan. Please understand that we won't be able to provide individual support via email. We also believe that help is much more valuable if it's shared publicly so that more people can benefit from it.

| Type | Channel | | ------------------------ | ------------------------------------------------------ | | 🚨 Bug Reports | <a href="https://github.com/ml-tooling/lazydocs/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Abug+sort%3Areactions-%2B1-desc+" title="Open Bug Report"><img src="https://img.shields.io/github/issues/ml-tooling/lazydocs/bug.svg?label=bug"></a> | | 🎁 Feature Requests | <a href="https://github.com/ml-tooling/lazydocs/issues?q=is%3Aopen+is%3Aissue+label%3Afeature+sort%3Areactions-%2B1-desc" title="Open Feature Request"><img src="https://img.shields.io/github/issues/ml-tooling/lazydocs/feature.svg?label=feature%20request"></a> | | 👩‍💻 Usage Questions | <a href="https://stackoverflow.com/questions/tagged/ml-tooling" title="Open Question on Stackoverflow"><img src="https://img.shields.io/badge/stackoverflow-ml--tooling-orange.svg"></a> <a href="https://gitter.im/ml-tooling/lazydocs" title="Chat on Gitter"><img src="https://badges.gitter.im/ml-tooling/lazydocs.svg"></a> | | 🗯 General Discussion | <a href="https://gitter.im/ml-tooling/lazydocs" title="Chat on Gitter"><img src="https://badges.gitter.im/ml-tooling/lazydocs.svg"></a> <a href="https://twitter.com/mltooling" title="ML Tooling on Twitter"><img src="https://img.shields.io/twitter/follow/mltooling.svg?style=social"></a>| | ❓ Other Requests | <a href="mailto:team@mltooling.org" title="Email ML Tooling Team"><img src="https://img.shields.io/badge/email-ML Tooling-green?logo=mail.ru&logoColor=white"></a> |

Features

<a href="#source-code-linking">Source Code Linking</a> • <a href="#api-overview">API Overview</a> • <a href="#mkdocs-integration">MKDocs Integration</a> • <a href="#docstyle-validation">Docstyle Validation</a> • <a href="#print-to-console">Print to Console</a>

Source Code Linking

Lazydocs is capable to insert a badge on the right side of every module, class, method or function with a link the correct source-code file and line number. The default configuration will create relative paths to navigate within the Github Repo. This is useful if the documentation is hosted within the same repository as the source-code. If, the documentation is hosted outside of the Github repository, it is recommended to set the src-base-url:

lazydocs --src-base-url="https://github.com/example/my-project/blob/main/" my_package

The src-base-url is used as a prefix for all source-code linkings in the documentation.

API Overview

An API overview might be very useful in case your project has a large number modules, classes and functions. You can specify an overview-file with the lazydocs command to activate the generation of an API overview:

lazydocs --overview-file="README.md" my_package

The API overview will be written as markdown to the specified file with separated lists for all modules, classes, and functions of your project:

MkDocs Integration

The markdown documentation generated by lazydocs can be easily integrated into your mkdocs documentation site:

Generate the markdown documentation into a subfolder (e.g. api-docs) inside your mkdocs documentation. We recommend to use the overview-file option and set the source-code URL via src-base-url, otherwise the source-code linking would not work:

lazydocs \
    --output-path="./docs/api-docs" \
    --overview-file="README.md" \
    --src-base-url="https://github.com/example/my-project/blob/main/" \
    my_package

Install and apply the awesome-pages mkdocs plugin. This enables mkdocs to automatically discover and include all markdown files. The alternative would be to manually include all generated markdown files in the navigation section of the mkdocs.yaml. In order to use the awesome-pages plugin you need to 1) install the plugin via pip 2) Include it in the plugin section mkdocs.yaml and remove the navigation section (needs to be handled with .pages files).
If you used the overview-file option, a .pages file will be automatically created. You can also manually create the .pages file within the api-docs subfolder (e.g. api-docs) with the following content:
```
title: API Reference
nav:
   - Overview: README.md
   - ...
```

Once you run or deploy your mkdocs documentation, you will see the API Reference section with all of your API markdown documentation.

Docstyle Validation

Lazydocs can only parse valid Google-style docstring. To prevent the generation of invalid markdown documentation, you can use the validate flag:

lazydocs --validate my_package

This will run pydocstyle on your docstring and cancel the generation if an issue is found.

Print to Console

To get the markdown documentation as console output instead of the file generation, specify stdout as the output-path:

lazydocs --output-path=stdout my_package

Documentation

CLI Interface

lazydocs [OPTIONS] PATHS...

Arguments:

PATHS...: Selected paths or imports for markdown generation. [required]

Options:

--output-path TEXT: The output path for the creation of the markdown files. Set this to stdout to print all markdown to stdout. [default: ./docs/]
--src-base-url TEXT: The base repo link used as prefix for all source links. Should also include the branch name.
--url-line-prefix TEXT: Line prefix for git repository line url anchors #{prefix}line. If None provided, defaults to Github style notation.
--overview-file TEXT: Filename of overview file. If not provided, no API overview file will be generated.
`--remove-package-pre

Lazydocs

Install / Use

README