Added "View as markdown" button

[mnocon]

This PR adds support for https://llmstxt.org/ (tool helping AI agents navigate webpages), and introduces a Markdown version of the doc.

How it looks:

The "View on GitHub" button is replaced by:

• View as Markdown - fully rendered Markdown content
• Edit on GitHub - for quick contributions

Why Markdown version of the doc, is the content on GitHub not enough?

No, because the macros we use (for example, embedding files) make the content not readable.

Compare:

• Raw Markdown
• Output Markdown
  The output Markdown contains the full code sample, making it easier for the AI agents to understand what's going on.

For more example see the list of cases I had to cover below.

LLMS.txt files

llms.txt file
llms-full.txt file

Pages can be excluded from this by marking them with exclude_from_llmstxt.

The content of these files is autogenerated by mkdocs build is run - no manual changes needed.
For now, HTML files are excluded from this list - I want to tackle API References in a follow-up.

Notes

Release notes page:

HTML: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/release_notes/ibexa_dxp_v5.0/
Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/release_notes/ibexa_dxp_v5.0/index.md (supports badges)

Exclusion of Personalization

Personalization pages are excluded from this solution.
Example page: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/personalization/personalization/

Image alt text

AI agents cannot see the images, similarly as people using screen readers.

HTML: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/infrastructure_and_maintenance/request_lifecycle/
Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/infrastructure_and_maintenance/request_lifecycle/index.md

*[Image: Simplified request lifecycle flowchart]*

Absolute vs relative urls

This is something I'm still considering - I've went with absolute URLs, as these fill safer, but they use more token space of the agents.

Example page with absolute linls: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/discounts/discounts/index.md

Admonition boxes

Converted to blockquotes.

HTML: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/infrastructure_and_maintenance/background_tasks/#start-worker

Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/infrastructure_and_maintenance/background_tasks/index.md

> **Warning: Multi-repository setups**
>
> Doctrine transport works across multiple repositories without issues, but other transports may need to be adjusted, so that queues across different repositories are not accidentally shared.

> **Note: Deploying Ibexa Messenger**
>
> Additional considerations regarding the deployment of Symfony Messenger to production, which you can find in [Symfony documentation](https://symfony.com/doc/current/messenger.html#deploying-to-production) apply to Ibexa Messenger as well.

Tabs

Example:
HTML https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/getting_started/requirements/
Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/getting_started/requirements/index.md

**Ibexa DXP v5.0**

| Name                          | Version    |
| ----------------------------- | ---------- |
| Debian 11 "Bullseye"          | 11.0-11.7+ |
| Ubuntu "Noble Numbat"         | 24.04      |
| RHEL / CentOS / CentOS Stream | 8.1-9.5+   |

If you see a "+" next to the product version, it indicates a recommended version or higher within the same major release. For example, "1.18+" means any 1.x version equal to or higher than 1.18, but not 2.x.

**Ibexa DXP v4.6**

| Name                          | Version     |
| ----------------------------- | ----------- |
| Debian 10 "Buster"            | 10.0-10.13+ |
| Debian 11 "Bullseye"          | 11.0-11.7+  |
| Ubuntu "Focal Fossa"          | 20.04       |
| Ubuntu "Jammy Jellyfish"      | 22.04       |
| Ubuntu "Noble Numbat"         | 24.04       |
| RHEL / CentOS / CentOS Stream | 8.1-9.5+    |

Tables

Tables actually look great 😄 The only problem is tables where a call contains a |: This will be fixed once we start using markdownlint (one of the PR fixes this) - we can't use the | symbol within tables, as it breaks table rendering.
For tables with linebreaks within cells, a comma is used instead.

Examples:
HTML: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/ibexa_products/editions/
Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/ibexa_products/editions/index.md

With linebreaks:

HTML: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/api/event_reference/content_events/
Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/api/event_reference/content_events/index.md

Note the broken row for BeforePublishVersionEvent - this must be fixed in the Markdown source (I do it in one of the Markdownlint PRs).

Cards macro

Converted to a list of links:

HTML: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/ibexa_products/editions/
Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/ibexa_products/editions/index.md

Lists numbering

Example: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/infrastructure_and_maintenance/clustering/clustering_with_ddev/index.md

Edition pills

In content (inline):

• Mutliple badges: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/commerce/shopping_list/shopping_list_guide/index.md

• Single badge:

  • https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/content_management/pages/page_builder_guide/index.md
  • https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/commerce/commerce/index.md

• HTML: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/update_and_migration/from_5.0/update_from_5.0/#form-builder-performance-fix-missing-indexes-on-form-submission-data

• Markdown: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/update_and_migration/from_5.0/update_from_5.0/index.md

## v5.0.4

### Database update (Experience) (Commerce)

Release notes: https://ez-systems-developer-documentation--3161.com.readthedocs.build/en/3161/release_notes/ibexa_dxp_v5.0/index.md

## Google Gemini connector v5.0.7 (Headless, Experience, Commerce, LTS Update, New feature, First release)

2026-04-20

[github-actions]

Preview of modified files

Preview of modified Markdown:

• docs/personalization/api_reference/api_reference.md
• docs/personalization/api_reference/content_api.md
• docs/personalization/api_reference/recommendation_api.md
• docs/personalization/api_reference/tracking_api.md
• docs/personalization/api_reference/user_api.md
• docs/personalization/attribute_search_in_elasticsearch.md
• docs/personalization/enable_personalization.md
• docs/personalization/how_it_works.md
• docs/personalization/importing_historical_user_tracking_data.md
• docs/personalization/integrate_recommendation_service.md
• docs/personalization/legacy_recommendation_api.md
• docs/personalization/personalization.md
• docs/personalization/personalization_guide.md
• docs/personalization/recommendation_integration.md
• docs/personalization/tracking_integration.md
• docs/personalization/tracking_with_ibexa-tracker.md

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dabrt]

There is one and only reservation. While the idea is undoubtly beneficial, I feel like the area around the title has become very crowded. How about we consult the placement with Dawid Z. ?

We could, for example, have icons with hover-on labels, wdys? Or put the section with purely technical buttons at the bottom, after the article itself?

[mnocon]

I've chosen this implementation based on other docs, which is (quickly) becoming the norm.

Other pages using this approach of "buttons under h1":

• https://docs.stripe.com/get-started/account/set-up
• https://developers.cloudflare.com/docs-for-agents/
• https://docs.docker.com/get-started/
• https://docs.payabli.com/guides/platform-payabli-three-ps-overview
• https://developers.openai.com/api/docs/guides/text
• https://buildwithfern.com/learn/docs/getting-started/overview

As the number of action grows, they start using dropdowns:

• https://elevenlabs.io/docs/overview/capabilities/voices
• https://developer.upsun.com/cli/reference
• https://code.claude.com/docs/en/overview
• https://www.mintlify.com/docs/organize/navigation

As we only have 3 buttons right now - I'd keep this as is