Skip to content

Pipeline

Giorgio Garofalo edited this page Feb 25, 2025 · 14 revisions

(This page is work-in-progress. This wants to be a simplification of what is explained in my Thesis (Italian), in which Quarkdown's architecture is thoroughly explained and documented. The thesis is updated to September 2024.

When an input file is supplied to Quarkdown, it undergoes a process of elaboration to transform it into an output resource, such as an HTML document that the browser can display. Under the hood, this process is represented by a sequential pipeline, in which the output of one stage becomes the input of the next one.

  1. Lexing
  2. Parsing
  3. Function call expansion
  4. Document tree traversal
  5. Rendering
  6. Post-rendering

Getting started [NEW!]

Documentation

CLI tools

Markdown enhancements

Functions

Setting up

Multi-file projects

Layout

Charts & diagrams

Scripting & control flow

Utilities

Slides

I/O

Native content

Value types

Built-in libraries

  • Paper: abstract, definitions, theorems, and more

Extra features

Inside Quarkdown

Clone this wiki locally