Docs Sites: Translation API, Media Import, and MCP Tools
End-to-end docs automation: translation linkage, locale-scoped publish, media import from URL, layout and chrome strings, plus public-site locale fixes.
Docs sites now work end-to-end through the Aveiro API and MCP: translation linkage, locale-scoped publish, translation-aware page lists, SSRF-safe media import, layout and chrome string tools, plus public-site fixes for locale lang attributes and navigation.
What we shipped
Teams running Magic Docs (or any localized MDX site) from Cursor Cloud Agents or custom CI no longer need dashboard-only steps for translations, media, or chrome copy.
Translation-aware content API
Create variants — translation_of + locale on POST /api/v1/sites/{siteId}/pages (and aveiro_create_page)
Link existing locale files — POST …/pages/link-translation when MDX already lives under /de/…
Audit gaps — untranslated_for and stale_translations filters on list pages
Publish deliberately — locale_scope on publish (default locale only unless you opt in)
Media and chrome for agents
import_media_from_url — server-side HTTPS image fetch into the site library (SSRF-guarded) when agents cannot PUT bytes
update_site_layout — header CTA and footer columns in draft settings
Chrome strings API — list and set per-locale header/footer labels (GET/PUT …/strings)
Collection labels — per-locale display_name and position on collections
Visitor-facing docs polish
Public docs sites now keep <html lang> in sync with the content locale, localize updated/published bylines (including German and Chinese), fix prev/next card overflow, wrap long MDX table cells, and keep internal links locale-prefixed without ?published=1 in visitor URLs.
