Expanded syntax highlighting, list typography that matches your site prose, and validation that ignores component names inside code samples — so docs and API syncs stop failing on legitimate examples.
Fenced code blocks now highlight more languages, list items inherit your site's body typography, and MDX validation skips tags inside code samples — fixing false 422 errors when syncing technical docs through the API or Quasar.
What we shipped
Three improvements landed together for anyone writing docs, tutorials, or API-driven content:
Expanded syntax highlighting
Fenced markdown code blocks and the CodeBlock catalog component now support a wider set of language tags — including go, rust, python, java, kotlin, swift, graphql, yaml, toml, and more alongside the existing ts, tsx, js, jsx, json, bash, css, and html tags.Use fenced blocks for single snippets or the CodeBlock component when you need tabs or multiple snippets with a copy button.
Smarter MDX validation
Aveiro validates MDX to ensure only registered components render on your site. Previously, a fenced block that mentioned a component name — for example a tsx sample showing <Button> — could be misread as a real tag and rejected with 422 INVALID_MDX.Validation now skips fenced code blocks and inline code spans. Component names inside examples stay verbatim; only tags outside code are checked. The same rule applies in the editor, through Quasar, and on the Content API.
List typography matches body prose
Bullet and numbered list items now inherit your site's body type size, line height, and color — the same tokens paragraphs use. Lists look consistent in the editor preview and on published pages instead of falling back to a generic default.
Why it matters
Documentation sites and developer blogs lean heavily on code samples. A validation layer that cannot tell the difference between a rendered block and a fence explaining how to use one creates friction — especially when syncing pages from CI or asking Quasar to draft API reference content.
<Hero>
tsx
These changes keep the safety net (no invented components on the live site) without punishing legitimate technical writing.
Recommended workflow
Use fenced blocks for single-language snippets in Source mode — pick a language tag from the supported set.
Use CodeBlock from the catalog when you need multiple snippets or a copy button.
Sync docs via API with confidence that example JSX in fences will not trip validation — see Create a page for the INVALID_MDX rules.
Preview lists after changing site typography — bullets should match paragraph text automatically.
For MDX conventions and supported languages, see Writing with MDX in platform docs.
What is next
We continue expanding the component catalog Quasar can use safely and tightening validation at the edges — without blocking the code-heavy pages documentation teams depend on.
