> For the complete documentation index, see [llms.txt](https://quarkdown.com/wiki/llms.txt). # Pipeline - Post rendering > Main packages: [`core.rendering`](https://github.com/iamgio/quarkdown/tree/main/quarkdown-core/src/main/kotlin/com/quarkdown/core/rendering), [`core.pipeline.output`](https://github.com/iamgio/quarkdown/tree/main/quarkdown-core/src/main/kotlin/com/quarkdown/core/pipeline/output) > > Rendering modules: [`quarkdown-html`](https://github.com/iamgio/quarkdown/tree/main/quarkdown-html), [`quarkdown-plaintext`](https://github.com/iamgio/quarkdown/tree/main/quarkdown-plaintext) After obtaining the translation of the AST to the target format from the [Renderer](pipeline---rendering.md), you might notice that it is not enough to display to the user. Considering the HTML format, that is just the content that would go inside ``, but everything else is missing: metadata, styling, and possibly a runtime. Here comes the *post-renderer*, which programmatically builds the full document around the rendered content. For HTML, this is handled by `HtmlDocumentBuilder` (using the `kotlinx.html` DSL), located in [`html.post.document`](https://github.com/iamgio/quarkdown/tree/main/quarkdown-html/src/main/kotlin/com/quarkdown/rendering/html/post/document). The builder injects all the needed data, such as: - The content itself, placed into `` - The document target (plain/slides/paged/docs). Each target requires different scripts, stylesheets, and body structure - User-defined properties, such as title, page format, and fonts - The need to load certain libraries, such as KaTeX for rendering LaTeX formulas. This is only done if at least one formula is used On top of that, the post-renderer is also responsible for returning the output resources of the compilation. These resources include: - The generated HTML - The group of stylesheets (global stylesheet, layout theme, and color theme) - The group of required runtime scripts These resources are then added to those provided by the [media storage](media-storage.md) and ultimately returned by the pipeline. It is then up to the invoker to handle those resources, which in the case of [CLI](https://github.com/iamgio/quarkdown/tree/main/quarkdown-cli) are saved to file.