----------------------------------------------------------------------
This is the API documentation for the gdtest_bibliography library.
----------------------------------------------------------------------


## Functions

Public functions


weave(source: str) -> str

Produce documentation from a literate source.

The literate programming model this implements is due to Knuth
[@knuth1984]; this docstring citation probes whether project-level
bibliography resolution reaches generated API reference pages.

Parameters
----------
source
    The literate program source.

Returns
-------
str
    The woven documentation.

tangle(source: str) -> str

Extract compilable code from a literate source.

Parameters
----------
source
    The literate program source.

Returns
-------
str
    The tangled code.


----------------------------------------------------------------------
This is the User Guide documentation for the package.
----------------------------------------------------------------------

### Citations

Literate programming was introduced by Knuth [@knuth1984], who argued
that programs should be written for human readers first. The approach
interleaves prose and code, and is often typeset with LaTeX
[@lamport1994].

These citations resolve project-wide because `great-docs.yml` sets a
single `bibliography:` key — no per-page frontmatter is needed.

## References

::: {#refs}
:::


### Modular Decomposition

Module boundaries should hide design decisions that are likely to
change [@parnas1972]. Combining that principle with literate
programming [@knuth1984] yields documentation that tracks the modular
structure of the code.

This page lives one directory deep under `user-guide/`, yet the same
project-level `bibliography:` key resolves its citations — no
depth-dependent per-page path is required.

This page deliberately adds *no* manual References heading: Quarto
generates the section automatically and titles it from the document
language (here, the English "References").