---
title: "AEM Release 4.69.0 to 4.69.2"
description: "AEM Release 4.68.0 - News: Find out about our latest Features, Enhancements, and Bug Fixes."
path: https://www.eonshowroom.eon.com/en/about-foundation-2020/aem-release-notes/aem-release-4-69-0-2.html
lastModified: 2026-10-07T12:36:04.423Z
---

# AEM Release 4.69.0 to 4.69.2

![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/GettyImages-906577952-1%3A2-1?qlt=50&fmt=webp)

## AEM Release 4.69.0 to 4.69.2

Release Date: 30.09.2026 - 06.10.2026

Build-Version:

- 4.69.0-16718498
- 4.69.1-16800583
- 4.69.2-17100743

[Release Scope 4.69.0](https://confluence.agile.eon.com/wiki/spaces/ddsmbfoun/pages/1084621392/AEM+Release+4.69.0+30.09.2026)

[Release Scope 4.69.1](https://confluence.agile.eon.com/wiki/spaces/ddsmbfoun/pages/1101332621/AEM+Release+4.69.1+30.09.2026)

[Release Scope 4.69.2](https://confluence.agile.eon.com/wiki/spaces/ddsmbfoun/pages/1100464651/AEM+Release+4.69.2+xx.10.2026)

[Register to our Release Notes](https://www.eonshowroom.eon.com/en/about-foundation-2020/aem-release-notes/release-notes-newsletter-registration.html)

with UI-Kit

## 5.1.0

## Unlock Markdown Rendering for Enhanced Content

Activate Markdown support and enrich your experience!

Markdown rendering is now available and can be easily activated! If you are using custom components, we recommend integrating Markdown support to ensure smooth functionality. Check out our Markdown Integration Documentation for Custom Components to get started.

[Markdown & LLMs Documentation](https://confluence.agile.eon.com/wiki/spaces/ddsmbfoun/pages/1102419143/Markdown+LLMs+-+Public+access)

## Default UI-KIT Version

##### Default Version for Release: eon-ui-kit v_5.1.0

Any AEM releases is tested against a default UI-Kit version, which is set in CAC MultiBrandMainConfig as **fallback**. If CAC MultiBrandMainConfig is not set manually, then this version will be set for your website.

Solutions having their own UI-Kit (e.g. Suewag, Energiewacht) will always have to update manually.

[Release Documentation in Git](https://git.eon-cds.de/repos/eon-is/frontend/eon-ui/eon-ui-components/-/releases/5.1.0)

### Features

All features will be documented in the Foundation Showroom **no later than three weeks after the release**.

![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/features%3A1-1?qlt=50&fmt=webp-alpha)

#### 1.1 Brand-specific Font Loading Configuration

It is now possible to configure the new UI Kit brand-specific font loading centrally via the existing FoundationNG Multibrand Main CAConfig.

[EONWCMS-1510](https://jira.agile.eon.com/browse/EONWCMS-1510)

#### 1.2 Custom SVG for the standalone Pictogram component

It is now possible to use pictograms that are not part of the standard UI Kit library by pasting custom SVG code into the Pictogram dialog.

[EONWCMS-1330](https://jira.agile.eon.com/browse/EONWCMS-1330)

#### 1.3 GEO AI / LLMS Content Accessibility (MVP) llms.txt & .md

We enabled AEM websites to expose structured, AI-readable content with minimal editorial effort.

As part of the **GEO AI / LLM Content Accessibility MVP**, the supported components can now provide their content as a dedicated **Markdown (.md) representation**. This gives AI agents and LLM-based crawlers direct access to the relevant page content without relying on JavaScript rendering.

In addition, websites can maintain an **llms.txt file** to provide AI agents with guidance and relevant entry points to the available content.

The MVP covers a broad set of editorial components, including:

- **Core content:** text, tables, specifications, Q&A, quotes, numbers and accordions
- **Teasers & cards:** Basic Teaser, Card Teaser, Text Teaser, Tile Teaser, Answer Tile and related content
- **Stages & headers:** Hero Section, Content Header, Campaign Stage, Multi Content Stage and Blog Header
- **Media:** standard images, AI-generated images, clickable images and video
- **Interactive content:** carousels, tabs, option pickers, steps, modals and forms
- **Articles & contacts:** Article Meta Bar, Related Articles and Business Card variants
- **Structured / special content:** Content Aggregator, Project Map, badges, Free HTML and Experience Fragments
- **Accessibility for visual elements:** editorial Markdown descriptions for icons and pictograms
Overall, the MVP covers the main content types required to make typical AEM pages meaningfully readable in Markdown for AI agents and LLM crawlers.

[EONWCMS-1087](https://jira.agile.eon.com/browse/EONWCMS-1330)

[EONWCMS-1730](https://jira.agile.eon.com/browse/EONWCMS-1730)

[EONWCMS-1509](https://jira.agile.eon.com/browse/EONWCMS-1509)

[EONWCMS-1508](https://jira.agile.eon.com/browse/EONWCMS-1508)

[EONWCMS-1764](https://jira.agile.eon.com/browse/EONWCMS-1764)

[EONWCMS-1328](https://jira.agile.eon.com/browse/EONWCMS-1328)

[EONWCMS-1327](https://jira.agile.eon.com/browse/EONWCMS-1327)

[EONWCMS-1326](https://jira.agile.eon.com/browse/EONWCMS-1326)

[EONWCMS-1325](https://jira.agile.eon.com/browse/EONWCMS-1325)

[EONWCMS-1324](https://jira.agile.eon.com/browse/EONWCMS-1324)

[EONWCMS-1322](https://jira.agile.eon.com/browse/EONWCMS-1322)

[EONWCMS-1321](https://jira.agile.eon.com/browse/EONWCMS-1321)

[EONWCMS-1320](https://jira.agile.eon.com/browse/EONWCMS-1320)

[EONWCMS-1319](https://jira.agile.eon.com/browse/EONWCMS-1319)

[EONWCMS-1318](https://jira.agile.eon.com/browse/EONWCMS-1318)

[EONWCMS-1317](https://jira.agile.eon.com/browse/EONWCMS-1317)

[EONWCMS-1316](https://jira.agile.eon.com/browse/EONWCMS-1316)

[EONWCMS-1323](https://jira.agile.eon.com/browse/EONWCMS-1323)

[EONWCMS-1138](https://jira.agile.eon.com/browse/EONWCMS-1138)

[EONWCMS-1098](https://jira.agile.eon.com/browse/EONWCMS-1098)

[EONWCMS-1708](https://jira.agile.eon.com/browse/EONWCMS-1708)

[EONWCMS-1714](https://jira.agile.eon.com/browse/EONWCMS-1714)

[EONWCMS-1750](https://jira.agile.eon.com/browse/EONWCMS-1750)

[EONWCMS-1745](https://jira.agile.eon.com/browse/EONWCMS-1745)

[EONWCMS-1187](https://jira.agile.eon.com/browse/EONWCMS-1187)

Furthermore, we added a **Main Site CAConfig option** to control Markdown rendering for the entire website. By default, Markdown output is **disabled** and must be explicitly enabled for a site.

In addition, a **page-level property** allows editors to exclude individual pages from Markdown output when needed.

To support extensions beyond the standard components, we also created **Markdown Integration Documentation for Custom Components**, explaining how custom components can provide their content in the .md output.

### Enhancements

Enhancements improve existing features, usability, and overall platform quality.

![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/enhancements%3A1-1?qlt=50&fmt=webp-alpha)

## 2.1 No-JS Fallback: Update

We now only render the *<noscript>* redirect if a valid No-JS fallback page is configured.

[EONWCMS-1835](https://jira.agile.eon.com/browse/EONWCMS-1835)

## 2.2 CTA: Allow Editors to Override Automatic Link Icons

It is now possible to have no Icon on CTA.

[EONWCMS-1713](https://jira.agile.eon.com/browse/EONWCMS-1713)

## 2.3 Additional parsys for the toolbar navigation

We added additional parsys for the toolbar navigation next to the logo.

[EONWCMS-1678](https://jira.agile.eon.com/browse/EONWCMS-1678)

## 2.4 Rename seotag to brandHeadlineSeoTag

We changed the seotag of Brand Headline to brandHeadlineSeoTag. With that change we have more clarification of the purpose of the property.

[EONWCMS-1274](https://jira.agile.eon.com/browse/EONWCMS-1274)

## 2.5 Map - Add Min/Max Zoom Fields to Map Component Dialog

We now support the new zoom configuration options for Map Component to configure minimum and maximum zoom levels.

[EONWCMS-1027](https://jira.agile.eon.com/browse/EONWCMS-1027)

## 2.6 Reusable Dialog Atoms & Button Dialog: CTA (Button) Dialog

We are now having the same button dialog for any component, so that editors have all button features available for teaser including a button.

[EONWCMS-134](https://jira.agile.eon.com/browse/EONWCMS-134)

[EONWCMS-1673](https://jira.agile.eon.com/browse/EONWCMS-1673)

## 2.7 MT-CAPTCHA: Expand Accessibility with Multi-Language Screen Reader Support

We enhanced the accessibility of the MT-CAPTCHA component by introducing robust multi-language support for screen reader functionality.

[EONWCMS-1821](https://jira.agile.eon.com/browse/EONWCMS-1821)

### Bug fixes

Bug fixes improve stability, resolve known issues, and ensure a more reliable platform experience.

![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/bugs%3A1-1?qlt=50&fmt=webp-alpha)

## 3.1 Teaser Components: Issue with Alignment

The text alignment configuration was no longer available in multiple teaser components. We made it work again.

[AEMPS-1136](https://jira.agile.eon.com/browse/AEMPS-1136)

## 3.2 Leading Icon option has no effect on Button component

When 'leading icon' option was selected for Button dialog, the icon position was still in trailing position and the selection had no effect. This is fixed now.

[EONWCMS-1852](https://jira.agile.eon.com/browse/EONWCMS-1852)

## 3.3 Blog Header | Content inside Box Component is not rendered when Blog Header is enabled

When the Blog Header had been configured and rendered via Press & Event Details, content placed inside a Box Component was no longer displayed. The Box Component itself was rendered, but its inner content was missing.

This is solved now.

[EONWCMS-1819](https://jira.agile.eon.com/browse/EONWCMS-1819)

## 3.4 Issue with Info Icon at Radio Button Group

The dialog of Radio Button Group allows configuring an info icon for both the question and the answer options. However, the rendered component only displayed the info icons for the answer options. This is fixed now.

[EONWCMS-1748](https://jira.agile.eon.com/browse/EONWCMS-1748)

## 3.5 Grid Control: Prevent Components in Layout Container

We fixed an authoring issue in the Grid Control.

[EONWCMS-1721](https://jira.agile.eon.com/browse/EONWCMS-1721)

## 3.6 Businesscard Contact | Twitter/X Icon not Rendered on Page

The Twitter/X icon inside Businesscard Contact was not rendering on Page. This is solved now.

[EONWCMS-1658](https://jira.agile.eon.com/browse/EONWCMS-1658)

## 3.7 Image | Hide Image on Mobile configuration breaks linked image behavior across viewports

After enabling "Hide image on mobile" and configuring a Link URL, the Image component did not behave as expected as on mobile nothing was rendered. This is fixed now.

[EONWCMS-1935](https://jira.agile.eon.com/browse/EONWCMS-1935)