mirror of
https://github.com/docling-project/docling.git
synced 2025-07-04 07:34:47 +00:00
88948b0bba
Fixed the [Usage] link in architecture.md Changed the usage link in the tip box from "../usage.md#adjust-pipeline-features" to "../usage/index.md#adjust-pipeline-features" as the previous link is not valid. Signed-off-by: Leandro Rosas <36343022+leandrosas101@users.noreply.github.com>
1.2 KiB
1.2 KiB
In a nutshell, Docling's architecture is outlined in the diagram above.
For each document format, the document converter knows which format-specific backend to employ for parsing the document and which pipeline to use for orchestrating the execution, along with any relevant options.
!!! tip
While the document converter holds a default mapping, this configuration is parametrizable, so e.g. for the PDF format, different backends and different pipeline options can be used — see [Usage](../usage/index.md#adjust-pipeline-features).
The conversion result contains the Docling document, Docling's fundamental document representation.
Some typical scenarios for using a Docling document include directly calling its export methods, such as for markdown, dictionary etc., or having it chunked by a chunker.
For more details on Docling's architecture, check out the Docling Technical Report.
!!! note
The components illustrated with dashed outline indicate base classes that can be subclassed for specialized implementations.