Aveiro upgraded to Once UI 2.0. Pages saved with 1.x prop names still render on live sites — no manual migration. New Source snippets should use 2.0 prop names.
Aveiro now runs on Once UI 2.0. Pages you saved with 1.x prop names still render on your live site — Aveiro translates those props at publish time. New Source snippets should use the 2.0 names below.
What changed
The Aveiro platform upgraded from Once UI 1.x to Once UI 2.0 (@once-ui-system/core 2.0). The editor, published visitor sites, and dashboard all use the new component APIs.You do not need to bulk-edit existing pages. Content saved before this upgrade keeps working.
Backward compatibility on published sites
When a visitor loads a published page, Aveiro runs stored MDX through a legacy prop upgrade layer. Common 1.x prop names are renamed to their 2.0 equivalents before components render.Examples:
Component
1.x prop
2.0 prop
Tag / Pulse
variant
scheme
Dialog
isOpen
open
Media / Carousel / Swiper
fill
stretch
Input / Select
hasPrefix / hasSuffix
prefix / suffix
Switch / Checkbox
isChecked
checked
RevealFx
trigger
revealed
ShineFx / RevealFx
speed / delay in seconds
milliseconds
If both the old and new name appear on the same tag, the 2.0 name wins — so content written after the upgrade is untouched.The editor also reads legacy names when you open an older block (for example a Tag saved with variant) and writes the 2.0 name (scheme) when you save.
What you should do
Existing sites — publish as usual. No migration project required.
New Source-mode MDX — prefer 2.0 prop names when you copy snippets from Once UI docs or Quasar output.
Effect timing — ShineFxspeed and RevealFxdelay are milliseconds in 2.0. Aveiro converts small numeric values that look like seconds when rendering older content.
Read next
Writing with MDX — Source mode conventions and the Once UI 2.0 note
