docsub 0.6.0

Embed text and data into Markdown files

docsub

Embed text and data into Markdown files

[!WARNING]

• With docsub, every documentation file may become executable.
• Never use docsub to process files from untrusted sources.
• This project is in research stage, syntax and functionality may change significantly.
• If still want to try it, use pinned package version docsub==0.6.0

Use cases

• Manage docs for multiple targets without duplication: GitHub, PyPI, Docker Hub, ...
• Embed dynamically generated tabular data:
  • Models evaluation results
  • Dependencies summary
  • Test reports
• CLI user reference

Features

• Insert static files and dynamic results
• Plays nicely with other markups
• Invisible markup inside comment blocks
• Idempotent substitutions
• Custom user-defined commands
• Configurable

[!NOTE] This file uses docsub itself. Dig into raw markup if interested.

Docsub is not a...

• documentation engine like Sphinx or MkDocs
• templating engine like Jinja
• replacement for Bump My Version
• full-featured static website generator like Pelican

Installation

Development dependency

The most flexible recommended option, see Custom commands

# pyproject.toml
...
[dependency-groups]
dev = [
  "docsub==0.6.0",
]

Global installation

Works for simple cases.

uv tool install docsub==0.6.0

Basic usage

$ uv run docsub -i README.md

$ uvx docsub -i README.md

Get this

# Title
<!-- docsub: begin -->
<!-- docsub: include info.md -->
<!-- docsub: include features.md -->
> Long description.
* Feature 1
* Feature 2
* Feature 3
<!-- docsub: end -->

## Table
<!-- docsub: begin -->
<!-- docsub: include data.md -->
<!-- docsub: lines after 2 -->
| Col 1 | Col 2 |
|-------|-------|
| Key 1 | value 1 |
| Key 2 | value 2 |
| Key 3 | value 3 |
<!-- docsub: end -->

## Code
<!-- docsub: begin #code -->
<!-- docsub: include func.py -->
<!-- docsub: lines after 1 upto -1 -->
```python
def func():
    pass
```
<!-- docsub: end #code -->

From these

README.md # Title <!-- docsub: begin --> <!-- docsub: include info.md --> <!-- docsub: include features.md --> ... <!-- docsub: end --> ## Table <!-- docsub: begin --> <!-- docsub: include data.md --> <!-- docsub: lines after 2 --> | Col 1 | Col 2 | |-------|-------| ... <!-- docsub: end --> ## Code <!-- docsub: begin #code --> <!-- docsub: include func.py --> <!-- docsub: lines after 1 upto -1 --> ```python ... ``` <!-- docsub: end #code -->

info.md > Long description. features.md * Feature 1 * Feature 2 * Feature 3 data.md | Key 1 | value 1 | | Key 2 | value 2 | | Key 3 | value 3 | func.py def func(): pass

CLI Reference

$ docsub --help
Usage: docsub COMMAND [ARGS] [OPTIONS]

Update Markdown files with embedded content.

╭─ Arguments ──────────────────────────────────────────────╮
│ *  FILE  Markdown files to be processed in order.        │
│          [required]                                      │
╰──────────────────────────────────────────────────────────╯
╭─ Commands ───────────────────────────────────────────────╮
│ --help -h  Display this message and exit.                │
│ --version  Display application version.                  │
╰──────────────────────────────────────────────────────────╯
╭─ Parameters ─────────────────────────────────────────────╮
│ IN-PLACE --in-place  -i  Process files in-place.         │
│                          [default: False]                │
╰──────────────────────────────────────────────────────────╯

Syntax reference

Substitution block

<!-- docsub: begin -->
<!-- docsub: help docsub -->
<!-- docsub: include CHANGELOG.md -->
Inner text will be replaced.
<!-- docsub: this whole line is treated as plain text -->
This text will be replaced too.
<!-- docsub: end -->

Each block starts with begin and ends with end. One or many commands come at the top of the block, otherwise they are treated as plain text. Blocks without producing commands are not allowed. Block's inner text will be replaced upon substitution, unless modifier command lines is used.

If docsub substitution block leis inside markdown fenced Code block, it is not substituted (examples: fenced code blocks right above and below). To put dynamic content int fenced code block, place begin and end around it and use lines after 1 upto -1 (example: Basic usage section).

For nested blocks, only top level substitution is performed. Use block #identifier to distinguish nesting levels.

<!-- docsub: begin #top -->
<!-- docsub: include part.md -->
<!-- docsub: begin -->
<!-- docsub: include nested.md -->
<!-- docsub: end -->
<!-- docsub: end #top -->

Commands

• Block delimiters: begin, end
• Producing commands: exec, help, include, x
• Modifying commands: lines, strip

begin

begin [#identifier]

Open substitution target block. To distinguish with nested blocks, use #identifier starting with #.

end

end [#identifier]

Close substitution target block.

exec

exec arbitrary commands

Execute arbitrary commands with sh -c and substitute stdout. Allows pipes and other shell functionality. If possible, avoid using this command.

Config options:

• workdir — shell working directory, default '.'
• env — additional environment variables dict, default {}

help

help command [subcommand...]
help python -m command [subcommand...]

Display help for CLI utility or Python module. Use this command to document CLI instead of exec. Runs command args --help or python -m command args --help respectively. command [subcommands...] can only be a space-separated sequence of [-._a-zA-Z0-9] characters.

Config options:

• env — additional environment variables dict, default {}

include

include path/to/file

Literally include file specified by path relative to workdir config option.

Config options:

• basedir — base directory for relative paths

lines

lines [after N] [upto -M]

Upon substitution, keep original target block lines: first N and/or last M. Only one lines command is allowed inside the block.

strip

strip

Strip trailing whitespaces on every line of substitution result; strip initial and trailing blank lines of substitution result.

x

x <custom-command> [options and args]

Execute custom command declared in docsubfile.py in project root, see Custom commands for details and examples. The naming is inspired by X- HTTP headers and x- YAML sections in e.g. Docker Compose.

Custom commands

When project root contains file docsubfile.py with commands defined as in example below, they can be used as docsub: x ... commands. User commands can be defined as cyclopts, or click, or whatever commands. If using cyclopts, there is no need to install it separately, docsub uses it internally and it is always available to its Python interpreter.

<!-- docsub: x <custom-command> [options and args] -->

The x command can be regarded as a shortcut to

{sys.executable} docsubfile.py <custom-command> [options and args],

where {sys.executable} is python interpreter used to invoke docsub. This has important consequences:

• If docsub is installed globally and called as e.g. uvx docsub, user commands in docsubfile.py are allowed to use cyclopts and loguru, which are installed by docsub itself.

• If docsub is installed as project dev dependency and called as e.g. uv run docsub, user commands also have access to project modules and dev dependencies. This allows more flexible scenarios.

Example

$ docsub -i sample.md

sample.md

<!-- docsub: begin -->
<!-- docsub: x say-hello Bob -->
Hi there, Bob!
<!-- docsub: end -->

docsubfile.py

from cyclopts import App

app = App()


@app.command
def say_hello(username: str, /):  # positional-only parameters
    print(f'Hi there, {username}!')


if __name__ == '__main__':
    app()

Configuration

Configuration resolution order

• environment variables (to be documented)
• .docsub.toml config file in current working directory
• pyproject.toml, section [tool.docsub] (to be implemented)
• default config values

Environment variables

(to be documented)

Example

All config keys are optional.

[command.exec]
env = {}  # default
workdir = "."  # default

[command.help]
env = { COLUMNS = "60" }

[command.include]
basedir = "."  # default

[logging]
# level = "DEBUG"  # default: missing value

[!WARNING] In future releases config keys will be moved under [tool.docsub] root, this will be a breaking change.

Logging

Docsub uses loguru for logging. Logging is disabled by default. To enable logging, set config option log_level to one of logging levels supported by loguru.

(logging is rudimentary at the moment)

History

This project appeared to maintain docs for multipython project. You may check it up for usage examples.

Authors

• Michael Makukha

License

MIT License

Changelog

Check repository CHANGELOG.md