Skip to content

docs: fix invalid since-badge placement and clarify guidance (#5713) (CP: v25.2)#5740

Merged
peholmst merged 1 commit into
v25.2from
cherry-pick-5713-to-v25.2-1782369922346
Jun 26, 2026
Merged

docs: fix invalid since-badge placement and clarify guidance (#5713) (CP: v25.2)#5740
peholmst merged 1 commit into
v25.2from
cherry-pick-5713-to-v25.2-1782369922346

Conversation

@vaadin-bot

Copy link
Copy Markdown
Contributor

No description provided.

Fixes `since` badges that were authored with invalid AsciiDoc and never
rendered. A `since` badge is an inline role that must be immediately followed by
a formatted text span (e.g. `#...#`); a span-less badge renders as literal
`[since:...]` brackets or silently produces nothing.

- Correct 7 broken usages across 7 articles: a badge trailing a heading
  (`== Title [since:...]`) and badges alone on their own line, rewritten to the
  span form (`== [since:...]#Title#`, or wrapping a phrase in body text).
- Update the CLAUDE.md "Version References" guidance to document the correct
  form so future docs use it.
Comment thread CLAUDE.md
```asciidoc
// Correct — on a page title or section heading:
= [since:com.vaadin:vaadin@V25.1]#Slider#
== [since:com.vaadin:vaadin@V25.2]#Hierarchical Data#

@jouni jouni Jun 25, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The recommended way to annotate a section heading is to place the role/class on the heading instead of a span inside it. For example:

[role="since:com.vaadin:vaadin@V25.2"]
== Hierarchical Data

The only exception is the main/top-level heading, which doesn't allow it, so there you need to wrap it in a span.

I won't stop us from unifying everything one way or the other. But it’s not great to keep using both styles for 2nd and 3rd-level sections.

@peholmst
peholmst merged commit 4eb5c99 into v25.2 Jun 26, 2026
5 checks passed
@peholmst
peholmst deleted the cherry-pick-5713-to-v25.2-1782369922346 branch June 26, 2026 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants