MDX is Markdown with JSX components. Use Visual mode for most edits; switch to Source for precise control. Page metadata lives in Page settings, not frontmatter.
Markdown basics
In Source mode (and in mixed Visual/content areas), standard Markdown works:
# headings through ######
Bold and italic
Lists, blockquotes, horizontal rules
Fenced code blocks with language tags
Links [text](url)
Headings in Markdown map to styled typography in the preview.
title / summary / tag frontmatter for editor pages
Page settings panel
Raw HTML layout divs
Row, Column, or catalog components
Unregistered component names
Catalog blocks or ask Quasar to fix
Legal/marketing static files in the repo may use frontmatter differently; site pages in the editor use DB metadata.
Code blocks
Fenced blocks render with syntax highlighting:
Inline code uses single backticks for short snippets.
SmartLink
Prefer SmartLink for internal navigation — resolves site routes correctly in templates:
When to use Source mode
Bulk text find/replace
Paste MDX from Quasar or external docs
Fine-tune props without a customize form
Debug broken blocks
Switch back to Visual to confirm layout.
Once UI 2.0 and older MDX
Aveiro runs on Once UI 2.0. If you paste MDX from older tutorials or a site saved before the upgrade, 1.x prop names such as variant on Tag, isOpen on Dialog, or fill on Media still render on your published URL — Aveiro renames them at render time.
When writing new Source-mode MDX, prefer 2.0 names (scheme, open, stretch, and millisecond values for ShineFx / RevealFx timing). The editor loads legacy names from older blocks but saves 2.0 names when you edit.
