Migrate from Marp

The converter can migrate an existing Marp file into a Remarp project. Migration prepares source; it does not guarantee complete visual or behavioral equivalence.

python3 plugins/aws-content-plugin/skills/reactive-presentation/scripts/remarp_to_slides.py migrate old-talk.md -o /var/tmp/remarp-talk

Before the project build, create or update /var/tmp/remarp-talk/_presentation.md with the desired global language, and keep any block-level lang overrides consistent:

---
remarp: true
lang: en
---

Copy other shared metadata from the original deck as needed. Migration preserves source prose; setting lang does not translate it. Project builds and sync read frontmatter, not the single-file --lang flag.

python3 plugins/aws-content-plugin/skills/reactive-presentation/scripts/remarp_to_slides.py validate /var/tmp/remarp-talk
python3 plugins/aws-content-plugin/skills/reactive-presentation/scripts/remarp_to_slides.py build /var/tmp/remarp-talk

Review the mapping

Change the deck marker to remarp: true; move global metadata into _presentation.md when splitting blocks; replace legacy slide comments with supported @type, @layout, background, and timing directives; convert speaker guidance into :::notes; and inspect column/layout blocks.

Ordinary headings, lists, code, and images usually remain recognizable Markdown. Interactive quizzes, tabs, Canvas steps, and fragment behavior need deliberate authoring and browser checks. Preserve required note markers and existing published links.

Incremental migration

Keep the original as a reference, migrate one block, validate/build, compare its render, then continue. Use .md with Remarp frontmatter for new source; .remarp.md remains supported. Check asset paths, theme compatibility, notes, navigation, and exports before replacing the old deck.