Extracted Markdown converter to a separate package

[mnocon]

Extracted the Markdown converter so that it can be reused in the user doc.

Follow-up to github.com//pull/3161
User doc PR: ibexa/documentation-user#414

[github-actions]

Preview of modified files: no change to preview.

[mnocon]

Moved from hooks.py with minimal changes

[mnocon]

Same here

[github-actions]

Summary

Status	Count
🔍 Total	761791
🔗 Unique	15026
✅ Successful	6426
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	755364
❓ Unknown	0
🚫 Errors	1
⛔ Unsupported	0

Errors per input

Errors in site/templating/twig_function_reference/recommendations_twig_functions/index.html

• [ERROR] https://content.raptorservices.com/help-center/user-tracking-understanding-soft-ids-hard-ids-raptor-identity-matching#:~:text=IDs%3A-,UserId%20%28Website%20ID (at 14439:29) | Cannot find fragment

Full Github Actions output

[mnocon]

Explanation from Claude for this change:

Prompt: Explain the "-e ." change

The -e . line in requirements.txt (requirements.txt:11 after the diff) tells pip: install the package defined by the pyproject.toml in this directory, in "editable" mode.

Here's why it's there:

Why a package install is needed at all

The refactor made hooks.py and friends into thin shims:

from llms_txt.hooks import on_config, on_page_content

For import llms_txt to work, Python needs llms_txt to be an installed package on sys.path — it's not enough for tools/llms_txt/ to just exist as a directory in the repo, because nothing adds tools/ to sys.path by default. The old code manually did sys.path.insert(0, ...); the new code relies on the package being properly installed instead.

pyproject.toml declares where that package physically lives:

[tool.setuptools]
package-dir = {"" = "tools"}
packages = ["llms_txt"]

So pip install . (run from the repo root, where pyproject.toml is — that's what the bare . means) installs the tools/llms_txt/ directory as the top-level importable module llms_txt.

Why -e (editable) instead of a plain install

A normal pip install . copies the package files into your Python environment's site-packages. If you then edit tools/llms_txt/hooks.py, your installed copy is stale until you reinstall.

pip install -e . instead installs a pointer back to tools/llms_txt/ in the repo. Editing the source is picked up immediately — no reinstall needed. That matters here because this is source code actively being edited (docs build hooks), not a third-party dependency.

Why it's in requirements.txt (not just requirements-dev.txt)

hooks.py is required for every mkdocs build, not just for running tests — so whatever installs dependencies for a real doc build (local, CI, ReadTheDocs) also needs llms_txt importable. Since requirements-dev.txt does -r requirements.txt, adding it to the base file covers both.

[mnocon]

Same here